Another A7V ATA100 Win2K boot problem?

[geoffdawson]

I have been trying to set up Win2k on a new A7V with an ATA100 connected disk and had various problems which I have overcome using info in the newsgroup. The final problem I can't get past (and can't find any postings for) is that, although the disk will boot fine when ATA66 connected, I get the error message 'Error loading operating system' when on ATA100. The error comes up before I even get up the loader menu. Any information I have found on the error suggests that it is produced by the MBR when it has found the active partition but can't start the operating system.

If I boot from floppy I can see the C (FAT) drive which has ntldr etc. with no problem.

I initially tried building Win2k (including service pack and Promise drivers) on ATA66 and then switching to ATA100 but got the error. I was then using bios 1004d and Ultra bios 2.01 (Build 28).

I then built again with the drive connected to the ATA100 and adding the Ultra 1.60 (build 33) drivers during the setup so that setup could see the disk. This was fine up to the point at which setup re-boots when I got the error. I connected the disk back to the ATA66 and finished the setup but then when I put it back on the ATA100 I got the error again.

I have tried using the command mode in Win2k recovery and have run fixmbr and fixboot and have copied ntldr from the setup CD.

I have upgraded the bios to 1005c and have even moved my PCI cards from slots 1&2 to 3&4.

Anybody got any suggestions? Is anybody using Ultra bios 2.01 (Build 28) successfully? (It's about the only thing I haven't changed)

GeoffD

[Cunning Linguist]

I can't boot via the ATA100 either, I have to put my harddrive on the 66 controller to it to boot and run. When I switch it to the 100 controller it tells me something about a boot configuration and to read the windows 2k manual.

I have all the latest BIOS updates and 3 different versions of the ata100 drivers. Any ideas?

[geoffdawson]

It sounds like you are getting further than me. What is the error message you are getting and at what point in the process?

[racpuc]

Try loading win2k directly..if you have the problem of win2k not finding your hd use a disk to manually load the drivers. files for the ata 100 can be found in your a7v cd. This will enable win2k to see your hd, and load win2k.

[Cunning Linguist]

I get past the Promise BIOS load, and it looks like its starting to load w2k, but then the error pops ups. You can ctrl+alt+del and it'll reboot so it doesn't freeze, but it get any further.

The problem is, it found the BUS, but I think I installed an older version of the driver.

[geoffdawson]

Cunning Linguist,

Sounds like you are failing when the Win2k drivers are taking over. Did you build on ATA100? If not are you sure you have the Promise drivers loaded?

BTW you have said your Ultra bios is 1.60 (build 33) but I suspect you don't mean bios but drivers. What Ultra bios are you using (displayed at load time). I am using 2.01 (build 28) and until very recently haven't found an alternative but now the Promise site has an upgrade to 2.01 (build 27)!!!

[Cunning Linguist]

Thats right, its 2.02 33!
Well, I uninstalled the BUS Master thats listed in my device manager, I'm going to reboot tonight, reinstall the drivers and see what happens.

[geoffdawson]

Where did you get bios 2.02 (33) from?

[OldFrog]

It's part of all BIOS 1.005* on A7V Mobos

[Cunning Linguist]

I installed the 1005C bios.

Latest update:
I uninstalled the controller and installed the drivers on the CD, still no go.

The error message is such (paraphrasing) Please check you Windows 2000 Professional Manual for disck configuration information...

[Europe]

Perhaps you may want to try the following:

Enter BIOS setup. Go to BOOT. Click for drop down menu. Wait a few seconds for Booe sequence to show.
Try setting the sequence to mimic the following;

1. Removable Device [Floppy]
2. Other Boot Device [Onboard ATA100 Boot]
3. ATAPI CD-ROM [Your CD-ROM drive]
4. IDE Hard Drive [Disabled]


Plug and Play O/S [Yes]
...
...
...
...
SCSI/ATA100 Boot Sequence [ATA100 /SCSI]
Load Onboard ATABIOS [Auto]

N.B. ... = do not change the settings in these lines.

Hope this helps.

[Cunning Linguist]

Originally posted by Europe
Perhaps you may want to try the following:

Enter BIOS setup. Go to BOOT. Click for drop down menu. Wait a few seconds for Booe sequence to show.
Try setting the sequence to mimic the following;

1. Removable Device [Floppy]
2. Other Boot Device [Onboard ATA100 Boot]
3. ATAPI CD-ROM [Your CD-ROM drive]
4. IDE Hard Drive [Disabled]


Plug and Play O/S [Yes]
...
...
...
...
SCSI/ATA100 Boot Sequence [ATA100 /SCSI]
Load Onboard ATABIOS [Auto]

N.B. ... = do not change the settings in these lines.

Hope this helps.

I tried that, it didn't work. I'm not sure if its the driver or the mbr... and to my knowledge you can't "fdisk /mbr" Windows 2000

[Beaver]

Enter BIOS, goto BOOT
Set Boot Virus Detection: Enabled
It works for me under W98/2000.

[geoffdawson]

CL,

The way you rewrite the MBR on Win2k is to use the command line option in recovery mode and use the fixmbr command but if you are getting beyond the initial boot menu (which it sounds like you are doing) then your MBR is OK. It sounds more like it is Win2k that is not seeing the disk which points to the Promise drivers. Are you certain they are installed?

[Cunning Linguist]

Beaver: Been there done that


Geoff: Reasoning behind me thinking its the MBR is that the error message states it can't find the boot path or something.