Problem restoring ghost image to VPC

[Daern's Instant Fortress]

Picture the scene...

I have a Dell desktop PC (an old GX150, as it happens) which has been built
with Win2k, O2k3, patches and other corporate clutter. I have taken an image
of this box using Ghost 8 (corporate edition) and sysprep and tested that I
can re-image the box with this ghost image.

I now want to restore this image to a Virtual PC 2004 session. After having
a few problems with DOS based ghost floppy images, I decided to use the 32
bit version in WinPE. Fired it up, downloaded the image and all looks well.
Reboot and it starts to load Windows 2000...

Unfortunately, it BSODs almost immediately, with an "Inaccessible Boot
Device" error message. I'm assuming this is because of a difference in mass
storage drivers even though both the physical and virtual boxes use IDE
controllers.

Can anyone make some suggestions as to what I can try to get this working.
It's not a critical thing, but it would make my life easier as I have far
more virtual PCs than physical ones ;-)

Thanks

DIF

[Paul Adare - MVP - Microsoft Virtual PC]

In article <eXLtrA#kEHA...@tk2msftngp13.phx.gbl>, in the
microsoft.public.virtualpc news group, Daern's Instant Fortress
<da...@hotmail.com> says...

> Can anyone make some suggestions as to what I can try to get this working.
> It's not a critical thing, but it would make my life easier as I have far
> more virtual PCs than physical ones ;-)
>
>

Try an upgrade in place install in the VPC. Boot from the Windows 2000
CD, when prompted, choose to install Windows 2000 (don't choose repair
here, or that will put you into the Recovery Console), when it find your
existing install, choose to repair it.

--
Paul Adare
This posting is provided "AS IS" with no warranties, and confers no
rights.

[Daern's Instant Fortress]

> > Can anyone make some suggestions as to what I can try to get this
working.
> > It's not a critical thing, but it would make my life easier as I have
far
> > more virtual PCs than physical ones ;-)
> >
> >
>
> Try an upgrade in place install in the VPC. Boot from the Windows 2000
> CD, when prompted, choose to install Windows 2000 (don't choose repair
> here, or that will put you into the Recovery Console), when it find your
> existing install, choose to repair it.

Thanks Paul. I'll post my actual solution here, as I suspect many others
will be intrested:

As you've probably discovered, you can't restore a ghost image of a PC to
Virtual PC without causing horrid problems. Likewise, if you have a standard
core build, which you distribute using Ghost (or equiv), this will blow up
big time if you try it using Virtual PC.

This was (for me anyway) because the mass storage (i.e. IDE) driver on the
physical PC is not the same as the Virtual PC and when the image boots up in
Virtual PC, it BSODs immediately with "INACCESSIBLE_BOOT_DEVICE". The only
solution is to do a repair build as Paul suggested. There is, however,
another way.

Introduced in Sysprep 1.1, Windows now has the ability to redetect mass
storage controllers when a syspreped image boots up for the first time. This
allows Windows to sort out the mess and get booted up. To do this, you need
to add a list of all additional PnP IDs which you wish Windows to check in
sysprep.inf a bit like this:

[SysprepMassStorage]
PCMCIA\*PNP0600=%systemroot%\inf\mshdc.inf
PCMCIA\KME-KXLC005-A99E=%systemroot%\inf\mshdc.inf
PCMCIA\_-NinjaATA--3768=%systemroot%\inf\mshdc.inf
PCMCIA\FUJITSU-IDE-PC_CARD-DDF2=%systemroot%\inf\mshdc.inf
*AZT0502=%systemroot%\inf\mshdc.inf
PCI\CC_0101=%systemroot%\inf\mshdc.inf
PCI\VEN_10B9&DEV_5215=%systemroot%\inf\mshdc.inf
PCI\VEN_10B9&DEV_5219=%systemroot%\inf\mshdc.inf
PCI\VEN_10B9&DEV_5229=%systemroot%\inf\mshdc.inf
PCI\VEN_1097&DEV_0038=%systemroot%\inf\mshdc.inf
PCI\VEN_1095&DEV_0640=%systemroot%\inf\mshdc.inf
PCI\VEN_1095&DEV_0646=%systemroot%\inf\mshdc.inf
PCI\VEN_0E11&DEV_AE33=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_1222=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_1230=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7010=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7111=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2411=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_2421=%systemroot%\inf\mshdc.inf
PCI\VEN_8086&DEV_7199=%systemroot%\inf\mshdc.inf
PCI\VEN_1042&DEV_1000=%systemroot%\inf\mshdc.inf
PCI\VEN_1039&DEV_0601=%systemroot%\inf\mshdc.inf
PCI\VEN_1039&DEV_5513=%systemroot%\inf\mshdc.inf
PCI\VEN_10AD&DEV_0001=%systemroot%\inf\mshdc.inf
PCI\VEN_10AD&DEV_0150=%systemroot%\inf\mshdc.inf
PCI\VEN_105A&DEV_4D33=%systemroot%\inf\mshdc.inf
PCI\VEN_1106&DEV_0571=%systemroot%\inf\mshdc.inf

Believe it or not, this is the complete list of build in IDE IDs for Windows
2000 and as I can't remember the last time I had to use a third party IDE
driver on a desktop box, it'll do me nicely.

Once you've added this list to sysprep.inf, simply run sysprep.exe, reboot
with Ghost, take your image and restore it back into Virtual PC. It will
boot up, redetect the IDE controller, run mini setup and it's ready to go.
Total time is about 5 mins from first boot to the login screen :-)

This is great for me as it's not great grief to add these entries to all of
my images. I can now test them in Virtual PC and my life is suddenly much
easier.

Questions? Post 'em up!

DIF