Problem with Promise Ultra66 and Win2K

antipodean

Junior Member
Jan 28, 2000
24
0
0
I have win2K (SP1) with PromiseU66 (not hacked) running the latest Promise BIOS (from their website) and the drivers that ship with win2K. I have a couple of odd problems:
1) Event viewer gives me error occasionally telling me that my promise controller has old or out of date BIOS.
2) When I try to update my win2K drivers with the ones from the promise website (1.6 build 19 or something like that) win2k says the drivers cannot be used in win2k and refuses to install them. I know they are win2K drivers, so what's up?
Possibly related to the above, I want to know whether to disable the SCSI drive options in device manager drive properties tab. My drives are IBM 75GXPs, but win2k treats the PromiseU66 as a SCSI controller, so thinks the IBM drives are SCSI. Do I need to disable sync transfers and the like? I have not done this yet, could this explain the "out of date firmware error", maybe win2k thinks the SCSI controller has out of date BIOS because the drives attached are not operating like SCSI drives. It's just a hunch, but I wanted to run it by you guys. As ever, all help appreciated.
 

Alphacowboy

Senior member
Oct 11, 1999
482
0
0
Weird... I have no idea, my promise U66 works fine in win2k with the default drivers on the O/S! It will see it as a mass storage device and catogorizes it with the SCSI controllers
 

antipodean

Junior Member
Jan 28, 2000
24
0
0
Thanks Alphacowboy, do you see any i/o warnings etc, in event viewer (particularly anything about old or out of date BIOS)? Also have you disabled the SCSI drive settings (sync transfers, etc)? I would just like to know what's going on with my system.
 

Alphacowboy

Senior member
Oct 11, 1999
482
0
0
I didn't play with any of the settings at all, I just left it alone... are you running w/ SR1? unfortanately I couldn't tell you what my currents settings would be because I don't use it anymore but do you have the system set for PNP or manual in the BIOS? Just some ideas, if I think of anything else I will let you know... also make sure it isn't sharing an IRQ... I had that problem until I swapped it around and I think it worked fine in PCI Slot 2 without problems... It really didn't like Slots 4-6 and Slot 1 next to the AGP bus Try Slots 2-3