Win2k - no Promise ATA100?

G

Guest

Guest
I have been using win2k prof. for about 2 weeks now, and have had nothing but problems. One problem that keeps arising is with win2k not recognizing the promise ultraATA100 controller on my ASUS A7V mobo. I have my HDD connected to it and have had to re-install win2k several times now, because I kept getting corrupted files and was unable to repair them because win2k was not detecting a hard disk drive (connected to the promise controller).
now I can not get win2k to boot at all. I downloaded the latest promise ultra 100 driver (build33)from another computer (as I can not boot up win2k) and tried to install it using the the win2k set up CD. Pressed F6 at first blue screen to "install scsi or raid drivers" and then pressed "s" to "specify additional devices". I popped in the floppy diskette with the promise driver on it and selected the driver I wanted installed. Then during installation I receive this error message:

"File \Win2000\Ultra.sys caused an unexpected error (18) at line 1211 in D:\nt\private\ntos\boot\setup\oemdisk.c.

Press any key to continue."

I repeatedly receive this error everytime I tried installing the driver. I even dl'ed older promise drivers (build 25 and 32) and still receive the exact same error during installation.

Help?

Thanks in advance!
 

TheAntipop

Distinguished
Dec 31, 2007
1,315
0
19,280
that is certainly odd, is your win2k cd a copy or an original?
the only other option i can think of is to start with your HD in the ata66 slot and then move it to the 100 after you install the ata100 drivers, i know its a bitch but its what a lot of people used to do

If at first you don't succede, skydiving isn't for you.
<font color=blue>Intel Inside</font color=blue> = Idiot Outside
 
G

Guest

Guest
thanks antipop. I eventually tried this method after unsuccessfully trying everything else possible, but now it will not even boot in the ata66 slot. I get a blue screen with this message after windows finishes loading:

"Registry file failure
The registry cannot load the hive <file>:
\SystemRoot\System32\config\software
It is corrupt, absent or not writable"

This is really upsetting me because this randomely happened. I did not install any new hardware or drivers or anything, just when I booted up the next day it wouldn't boot.

Thanks for trying anyway.
 

TheAntipop

Distinguished
Dec 31, 2007
1,315
0
19,280
have you tried doing a repair on your windows 2000 installation? its one of the options you get instead of reinstalling when you boot off the cd, this sounds like it will solve your problem if you can get it to boot off the cd
btw, when do you get these error messages? is it at the black and white loading screen?

If at first you don't succede, skydiving isn't for you.
<font color=blue>Intel Inside</font color=blue> = Idiot Outside
 

hypnotic_kumquat

Distinguished
Dec 31, 2007
80
0
18,630
What version of the bios & driver are you using? I'm running BIOS v 2.00 Build 17 & driver version 1.60 Build 19 on an Asus P2B with no problems. If you're seeing errors on install & can't see drives ever since you've had the card, I'd say it's likely it's a bad card. Have you called Promise?

"Let's take the warning labels off everything and let natural selection clean the gene pool!"
 

TheAntipop

Distinguished
Dec 31, 2007
1,315
0
19,280
its not a card, its built into the motherboard. and if it WAS the controllers fault then he should have no problems using the ATA66 controller, hmm still cant think of anything

If at first you don't succede, skydiving isn't for you.
<font color=blue>Intel Inside</font color=blue> = Idiot Outside
 
G

Guest

Guest
yeah i've tried repairing it (connecting the HDD to the ata66 controller since win2k doesn't detect a HDD when its on the ata100). I can only do the Recovery Console repair and I don't see any option that would allow me to repair that error, the only command I see that would maybe help is the chkdsk command which I used, it detected 1 or more corrupted files. I guess it repaired them, because when I ran chkdsk again it said that my HDD was clean. But when i tried to boot win2k again I got the Registry file failure blue screen error again (it appears after win2k fully loads, with the load bar, then the blue screen appears).

I can't run the ERD repair because I don't have an ERD disk. If you don't have the ERD disk it will try to locate win2k installation for you but then it says that set up cannot find win2k installation to repair? I don't know how that is possible. I do have a copy of win2k set up disc, but I have tried 2 different ones, so I don't think thats the problem.

hehe no worries, I've stumped every other board that I've posted this problem to as well. hmmm maybe I might just have to bring it into a shop. I hate paying for these kinds of things though.
 

hypnotic_kumquat

Distinguished
Dec 31, 2007
80
0
18,630
OK, I'm blind.... AND still don't have any answers. I'm assuming you haven't had anything similar happen in any other OS?

"Let's take the warning labels off everything and let natural selection clean the gene pool!"
 
G

Guest

Guest
Mr. Rider,
I dont think the problem is in your OS or its driver support. Esp if you have reinstalled multiple times and the same errors occur. Here is my best advice:
When I first started integrating to Win2k, I smoked about 6 hard disks, all on different systems, in about a week. It is possible that, even if its a good name brand, you really screwed up your hard disk with all of the installation tasks you have demanded from your disk during your Win2k tests. Try another hard drive. Maybe even go out and buy a brand new drive, I recommend the new 30G IBM U100's, and try a fresh fdisk and install. If you are using a valid copy of Win2k, you shouldnt have any problems with finding the correct configs for your mobo and drive controller support. Good luck.
piersonk_2001@yahoo.com
 
G

Guest

Guest
I know you are probably getting tired of all the suggestions with this problem, but you might try using a utility to format the harddisk, writing zero's across the entire drive. Most drive manufacturers have a disk available for download on the internet. Go to the site for your drive and run the test on thedrive to verify it is all OK, than let it do the read and write test clearing the hard drive, then as you install Win2k, you the utility in the setup to create partitions on the disk and format in the setup of Win2k.
 

doczenith1

Distinguished
Dec 31, 2007
144
0
18,680
I have your answer!! Win2k doens't like ata100...yet. SP2 will fix this. I have a WD ata100 drive that would not install win2k when hooked up to the VIA 686b (native ata100) chipset on a SOYO K7VTA-B mb. After two unsuccessful attempts, getting similiar errors to those you listed, I used the wd utility to switch my drive to ata66 mode. When booting the drive listed as ata66 in POST and win2k installed just fine and is running great. Hope that helps.

Doc
 
G

Guest

Guest
Everyone,
Its not a safe thing to say that Win2K doesnt like ATA100 yet because of the service pack. I have an UATA100 IBM 30G disk on a ASUS CUSL-2 Mobo and everything works fine... Its all in the driver support. I cant remember exactly but, I think Win2k even loaded the U100 support by default when I installed. Take it for what its worth..
 

doczenith1

Distinguished
Dec 31, 2007
144
0
18,680
Maybe I should be more specific. It must be a win2k/via/ata100 thing. And I must also admit that when I tried I was using the first mb bios release. Soyo has since released a bios update that says "Changes: Enhance IDE performance." So maybe this would have made a difference. Since the ata100 support is part of the 686b southbridge a bios update sounds like it may have fixed the problem.

See MS KB Article ID: Q260233

I've updated my bios but am too chicken to take the risk and set my drive back to ata100 for fear of data loss. When the drive was set to ata 100 I did get win2k to install, but it ran slow as molasses due to the fact that I believe is was running in PIO mode as KB Article ID: Q269555 suggest. Even though the article says it should have still been running in udma mode, my system was very slow. So, yes I agree that it is most likely a driver issue.

Doc