Win2k Ghost Experiment...

[Entity]

I just ghosted an IDE machine over to a SCSI box with an Adaptec 29160 card and a 160 drive in it. After ghosting, I get the dreaded INACCESSIBLE_BOOT_DEVICE BSOD, whether I'm in safe mode or anything else. I'm assuming the problem is that the original box (the IDE that I ghosted from) didn't have SCSI support on the installation, since it wasn't a SCSI computer. Is there any way I can remedy this, so that I can boot the SCSI box?

Rob

 

[vash]

You are probably out of luck in this situation -- without the even base installed support for these kinds of devices, you probably won't get Win2k to boot onto that box. Your best solution is to modify the boot.ini. This is currently mine:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional"
/fastdetect

This is for my SCSI drives and devices. If someone would post their boot.ini from an IDE installation, you could try to mod boot.ini to see if Win2k will even boot off of it. They key line is the "multi..." This may not work, but its the best chance you have, ihmo.

vash

 

[Entity]

I just booted the box on an IDE drive, and now can edit the contents of the SCSI drive. If worse comes to worse, I can probably add SCSI device support by adding the drivers when I boot the IDE drive, then re-image it, right?

Rob

 

[Entity]

Ok, I'm screwed. This isn't working.

How would I do this from scratch? I'm bored at work and this is a good experimentation for me. I have an IDE drive, completely ready to go; if I, for example, installed W2k onto the SCSI drive (doing it from scratch right now), what should I do to make sure I can ghost the programs, etc., but not screw up booting? Or is it possible?

Rob

 

[speed01]

I would tend to agree with vash here, unless the OS was installed to the SCSI drive from the beginning I don't know of any way to get the machine to recognize it as the boot device. I ran into a similar situation when I tried changing to an ATA controller card from on board IDE. No matter what I tried it would not boot from the add-on controller.

 

[bignick]

you'll need to use sysprep. get it from microsoft.com

look in the samples folder of the archive when you unzip it. i personally merge the scsi and ide sysprep.inf files so that win2k will work for all the different mass storage controllers. also you may have to execute sysprep with the "-pnp" flag to get win2k to identify all the hardware correctly

 

[Entity]

Thanks for the help. I'm giving sysprep a try right now.

Rob