Archived from groups: comp.sys.ibm.pc.hardware.storage (
More info?)
Steve <sas@sasonsite.com> wrote in message
news:kqhl605skk0fcce9bcurs2e42e9p6fjisu@4ax.com...
> You know... come to think of it... I believe I did test it in the
> desktop system but can't recall if the source drive was still
> connected when I did so. If the source wasn't in the desktop
> and I didn't blow it there.... would having started the cloned
> drive in the desktop after ghosting been a problem being
> that it was intended to land up in the notebook ?
Nope, that approach is fine. The important thing is that
BOTH the original and the clone cant be visible to XP
on the first boot after the clone has been made. You're
welcome to boot with either drive visible alone to XP.
> Also, being that I ran FIXMBR and FIXBOOT, what
> else should I try doing from the XP installation CD ?
Boot the XP CD and use the repair option that shows up early.
That does a lot more than fixmbr and fixboot, it effectively
does a reinstall but preserves the various settings etc.
If the problem is that the desktop drivers for the hard drive
subsystem arent suitable for the laptop, that will replace
them with drivers suitable for the chipset in the laptop.
> Thanks for your comments and any followup you can offer.
> On Wed, 31 Mar 2004 16:44:53 +1000, "Rod Speed" <rod_speed@yahoo.com>
> wrote:
>
> >
> >Steve <sas@sasonsite.com> wrote in message
> >news:bjnk60d1rbml2j18ouifflr5dcn7e2p01q@4ax.com...
> >
> >> Tried ghosting an XP notebook drive to a larger notebook
> >> drive. Used my desktop system to do it. Used IDE adapter
> >> cables and connected source drive to Primary Ide controller
> >> and new drive to secondary controller. Ghosting went well.
> >
> >Should be fine, plenty do it that way successfully.
> >
> >> Took new drive and placed it into the
> >> notebook. Got NTLDR error messages.
> >
> >What did you do about booting the desktop system after
> >the clone had been done ? Its crucial to not let XP see
> >both the original and the clone on the first boot after the
> >clone has been done, otherwise it will produces a rather
> >mangled boot config that uses files on both drives and
> >that wont continue to work once you try booting off
> >just the clone with the original no longer visible.
> >
> >Safest to do the clone from a dos floppy so you
> >can be sure that it wont boot until you have unplugged
> >the clone and will only boot off the clone in the laptop.
> >
> >> Could see files on drive when I booted from
> >> XP Installation CD in recovery mode. Ran fixmbr
> >> and fixboot to no avail from recovery console.
> >
> >You should be able to fix it by repairing the installation.
> >
> >> What went wrong. Used Ghost 7.5.
> >
> >Most likely the above. Just do it again correctly.
> >
> >> Is is a geometry problem.
> >
> >Thats possible.
> >
> >What did you actually clone ? You should have
> >cloned the physical drive, not just a partition.
> >
> >Its also possible that the hard drive controller is
> >different enough in the laptop that the wrong driver
> >is being used and thats what stuffs the boot.
> >
> >> Maybe I should have noted the hard drive parameters of the
> >> original drive while in the notebook via cmos setup and plugged
> >> those into my desktop's setting for that drive prior to cloning ?
> >
> >Its generally best to use an AUTO drive type setting
> >all the time, but that isnt always possible with laptops,
> >particularly if they are a bit long in the tooth.
> >
> >> Any ideas on how to do this WINXP notebook cloning thing ?
> >
> >Do it like I listed, and if that doesnt work, repair the
> >installation in the laptop after booting from the XP CD.
> >
> >That last should fix a driver problem if thats the problem.
> >
>
Facebook
Twitter
Instagram