12 replies
by gmichaels
by gmichaels
by gigelul
by gigelul
by gigelul
Try to remember how was installed your system. Which OS was first installed and on which HDD and post comments.
I will try to give you the correct solution.
by gmichaels
by shanghai sam
This is the way I would do it, (and have done a few).
Firstly, have all disks ready, drivers available, etc. Win2K can seldom be reclaimed after a motherboard change, due to reliance on the Hardware Abstraction Layer, (HAL), during installation! Win9x is easier to do.
Change the drive order, put the slave as master and the master as slave, by moving the jumper on each drive, and setting the BIOS to Auto detect all drives. After the BIOS startup screen shows the drives properly, let Win 9x start. Copy the contents of the Win9x directory from the CD to somewhere on the HD, (normally Windows\Options\Cabs). Rename or move the folder Windows\INF\Other\ so that the wrong drivers are not found again. "Other" contains the INF files for devices not built-in to Win9x.
Restart in Safe Mode, open Device Manager, and one at a time, delete every device. Yes, each and every device, remove. Shut down to Power OFF, then restart the machine and Win9x will "find new hardware", lots of it, but IDEis third level, so CD drives are unavailable for awhile, and that's why we copy the CAB files to into Windows\Options\Cabs. Normally, I make a folder named Drivers\ under Windows\Options and copy the install files for each device into it's own folder, (ie: NIC\, MDM\, etc.).
Once Win9x is stable again and all the devices are working, start the Win2K setup from CD while running in Win9x. This will insure that the CD is working, and that Win2K will make it "Dual Boot". Use Win2K setup to removeand recreate the partition on the second drive, then do a fresh install of Win2K.
After this fix is made, Win9x sees C and the CD becomes D, Win2K will see Win9x on C, itself on D, and the CD becomes E, this is normal and expected.
by gmichaels
by gmichaels
by thechas
I suspect the W2K crashed because the second drive was missing, and caused errors.
Without using special switches, fdisk only accesses the master drive in a multi-drive setup.
Mount just the slave, and use fdisk to disable the active partition.
Another MAJOR problem could be that you do not have a driver capable of accessing your drives from W2K.
You did remove all hardware from device manager before removing the old motherboard???
If you just swapped motherboards, then I think your best bet is to wipe the drive and re-install W2K.
You might want to boot from the W2K CD, and give recovery console a try before re-installing the OS.
Chas
by gmichaels
by gmichaels
This discussion is closed to new replies.
Trending Hardware posts
Sort by Trending