Okay... I did something dumb... HELP!

[GeoffS]

Granted, the following events occured this morning *before* my first coffee...

I have a Tyan Tiger 133 and a VP6. I planned to migrate from the Tiger to the VP6, so I wanted to run a test. I Ghosted the drive in the Tiger, took the backup and dropped it into the VP6. Everthing went great. Some time passes, and it's time to do the real migration. I take the hd from the Tiger and put it in the VP6. However, this time, there is no CDROM in the VP6 containing the Win2K Pro CDROM. I don't remember this being a big deal, so I power up and the VP6 starts detecting new hardware... most notably the VIA IDE controllers... and can't find the software to load the required drivers. Naturally, upon rebooting, I get the BSOD with an inaccessible boot drive

So, how do I get the VIA drivers onto that drive?

Thanks in advance!

Geoff

 

[serialb]

Can you boot in Safe-Mode? Also, what kind of IDE controller (HighPoint, Promise etc) are you using?

 

[GeoffS]

Nope... can't even get into Safe mode. The chipset on the VP6 is VIA, and I'm not using the raid. There was nothing additional that I needed to set up when originally installing Win2K Pro.

 

[mee987]

it doesnt seem like a via driver issue to me, it seems like your boot.ini file is referring to an invalid drive. on boot, it doesnt refer to a drive letter (like c: ) to boot from, it refers to a device and partition #, like multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

you will need to change the "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS" to point to the actual location of your windows installation

i hope im not way off, it will make me look like an idiot

edit: i hate the stupid auto-smileys

 

[GeoffS]

hmmm... where is boot.ini?

 

[mee987]

should be on the root of your c: drive

 

[GeoffS]

umm... don't see it... oops.. there it is... looks the same on both drives (I've taken a second hd and installed Win2K Pro onto it and am in the process of transferring data between the drives).

 

[mee987]

what im saying is that while it was device 0, drive 0, etc on one system, it might not still be device 0 drive 0 when you put it in another system.

 

[Stanman]

If you still have the WIN2K CD, put it in and boot from it. it will tell you to press a key to install ide or scssi drivrs. If that doesn't work it will give you the option of repairing the win instalation. Do not use the repair console option, there is a repair boot option, that should work. If it doesn't you can do an install OVER your current win2k, but make sure it goes in same directory. I have taken a win2k install from one rig that was on "D" partition and restored it as a primary on another drive with Drive Image, and then used the fix-boot option and it worked. By the way, boot ini is a hidden file.

 

[mee987]

<< Do not use the repair console option, there is a repair boot option >>


do you know if this option is available with winxp? and if so where can I find it? i dont really need it at the moment but ive been wondering about it