From: "Glenn Meadows" 

Todays update (and question).

First, I converted the existing drive to NTFS. No problem.  Works fine,
like one would expect.

Ghost that, no joy on new HD.

Boot into recovery console, try fixmbr and newmbr.  NO joy.

Try REPAIR installation, files deleted, re-copied, at reboot, just blinking cursor.

Do NEW install to different location on the drive.  Files copy, system
comes around for reboot, blinking cursor.

Notice that when the XP Install options are presented, it lists OS/2 Boot
Manager Partition!!!  AHA!!!

How TF do I remove that these days?

1). Boot with a DOS (Win98 Emergency Disk) and use FDISK to delete the BM
partition, and set the NTFS as active partition?

2). Do I need a copy of the OS/2 FDISK to use that to remove the Boot
Manager Partition?

It seems that BM does not like something, as I've done this EXACT scenario
on other laptop HD's, with XPPro, XPHome, Win2k, putting larger HD's in
place, and NONE have given me the grief that this turd has done.

I need to DESTROY the Boot Manager partition,and make this original drive a
CONVENTIONAL HD again.

AARRRRGGGHHHHH!!!!!!

--
Glenn M.


"Glenn Meadows"  wrote in message
news:3fbb64c6$1{at}w3.nls.net...
> I'll give that a try, but I think this may be more on point:
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;314057&Product=winxp
>
> The Boot Manager/switcher software is Win/Dos based (when you boot to the
> IBM Rapid Restore, you get the Windows 98 logo as the DOS program boots).
>
> The drive is still FAT32, was originally installed with Win2K, and then
> WinXPPro installed over that as an upgrade install.  All was OK, until now
> when the drive geometry changed.  What I think I'm going to try next, is
> convert the existing drive to NTFS, and then re-ghost and see what
happens.
> It's possible that the drive was originally formatted using a DOS format
> command, and as the article says, when copying the drive as an image file,
> there are drive geometry issues.
>
> Thoughts on the KB article?
>
> --
> Glenn M.
>
>
> "Geo."  wrote in message
news:3fbb50bc$1{at}w3.nls.net...
> > Do a recovery reinstall and tell it to fix the boot files, either that
or
> > install W2K to a temp location then point boot.ini to the right folder
and
> > remove the temp install. That should get the boot files back and pointed
> at
> > each other. I believe the NTLDR error is still the boot sector but it
may
> be
> > NTLDR is just missing or boot.ini is seeing something different.
> >
> > Geo.
> >
> >
> > "Glenn Meadows"  wrote in message
> > news:3fbaba2d$1{at}w3.nls.net...
> > > Here's the problem.  I've got a Laptop HD that's about full.  It's a
> 20gig
> > > HD, with IBM's Rapid Restore woven into it.  It presents the
"Press
F11
> to
> > > access recovery console", so there's some boot mangling
going.  If you
> > don't
> > > press F11, the computer boots normally. (This is on the original
drive).
> > >
> > > Need to migrate the whole machine to a new 40 gig HD. (The old one is
> > still
> > > Fat32).
> > >
> > > Process is use GHOST with both drives installed on a desktop PC, one
on
> > the
> > > primary IDE, and other on the Second.  Ghost sees both drives
properly,
> > and
> > > will clone both the regular C as well as the hidden partition.  That
> being
> > > done, when I put the 40gig drive back in the laptop, I get the error
> NTLDR
> > > is missing, in other words, the drive won't boot.
> > >
> > > Using the XP Pro Install CD, and booting to the recovery console, I'm
> able
> > > to run the various command line options.  I've tried FIXMBR, NEWMBR,
> etc.,
> > > all to no avail.
> > >
> > > I'm open to suggestions here.
> > >
> > > --
> > > Glenn M.
> > >
> > >
> > >
> >
> >
>
>

--- BBBS/NT v4.01 Flag-5