Hi All !
During a Win98SE installation on an ECS P4S5A mobo, I have inadvertently installed the wrong PCI-IDE device driver off the mobo support CD.
This caused the system to hang before the 98 splash screen appears.
I started up in safe mode, intent on deleting the primary and secondary IDE devices along with the parent device but was only able to delete the parent device.
However, when 98 restarts and the hardware manager kicks in, it finds the reference to the device I deleted and reinstalls the unwanted drivers. If I try to cancel or bypass this step , the system hangs; if I try to find other drivers, I can't because I can't "see" either the DVD or CD-RW drive.
I had this happen with another system (an "in use" system which I was updating the drivers for) and I ended up reinstalling windows - a rather inelegant solution, IMHO .
I realise that I could modify the boot routine to include DOS drivers for the "first-pass" of installation but I was hoping for some help in finding an easy non-DOS solution to fixing this problem; something along the lines of a Registry hack of some description.
Regards,
zaphod38
During a Win98SE installation on an ECS P4S5A mobo, I have inadvertently installed the wrong PCI-IDE device driver off the mobo support CD.
This caused the system to hang before the 98 splash screen appears.
I started up in safe mode, intent on deleting the primary and secondary IDE devices along with the parent device but was only able to delete the parent device.
However, when 98 restarts and the hardware manager kicks in, it finds the reference to the device I deleted and reinstalls the unwanted drivers. If I try to cancel or bypass this step , the system hangs; if I try to find other drivers, I can't because I can't "see" either the DVD or CD-RW drive.
I had this happen with another system (an "in use" system which I was updating the drivers for) and I ended up reinstalling windows - a rather inelegant solution, IMHO .
I realise that I could modify the boot routine to include DOS drivers for the "first-pass" of installation but I was hoping for some help in finding an easy non-DOS solution to fixing this problem; something along the lines of a Registry hack of some description.
Regards,
zaphod38