KinetiK

Oh no! The cd only install didn't help things much I'm afraid... infact, it appears to have messed up my HD really really badly. I have a 20GB IBM Deskstar that is showing up in the W2K install screen as an 82GB monster. I take it that this isn't normal. /me the NT/W2K newbie hides from the Gods of NTdom

Hi, I currently have the hard drive plugged into the ATA66 IDE controller (that is, the NON-ATA100 one). I installed win98se on the ata66 controller, and then started an install of W2K. It crashed a number of times as i have indicated above. As an experiment, I changed the drive over to the ATA100 controller and tried to install w2k from there. w2k would say that it couldn't find the install files etc and crash. I had to go back to ATA66. I'm at a total loss now. =( Thanks for your help thusfar, though! KinetiK

Hello! I have been struggling to install W2K on my friends PC for a number of days now and have yet to find a solution. I have a bare bones installation of Win98SE on the c: partition and I want to install W2K on the D partition. The problem is this: Whenever I get to the W2K installation blue screen, and the PC tells me that it is checking hardware, i keep getting the same error: "STOP -- (a whole mess of error numbers) -- INACCESSIBLE BOOT DEVICE". The MB, as you know, has a Promise ATA100 controller on the MB. With the 1004C bios, I am able to disable the BIOS checking and I have. But I am still getting this error, even if I press F6 during startup to detect the external SCSI / RAID controller. Has anyone else had a problem with W2K installs and the 1004C bios update? Looking forward to your responses, KinetiK