A7V333 IDE not working?

Joined
Dec 27, 2000
Messages
693
Ok, got my brother's A7V333 (yes, I know it's old) here. For some reason, I can get the RAID controller to work just fine in windows, but the IDE doesn't work at all. This means he can't have a CD-ROM drive or anything. The CD is detected in the BIOS (V1017, the latest), and we've got the latest Hyperion drivers installed. However, in device manager, there's just a VIA bus master IDE controller with no primary or secondary channel. Also, no CD-ROM in disk management. There's also a 'PNP Bios Extension' that is not working in device manager, and I think that's part of it. What could I be doing wrong?
Edit: Specs:
Windows XP Sp2
AXP1800+
768MB RAM
Various Optical drives tried.
 
Check the operating mode of the Promise Controller <could be wrong about the brand> in the Bios, make sure it is set to ATA instead of Raid.


Novensu
 
Novensu said:
Check the operating mode of the Promise Controller <could be wrong about the brand> in the Bios, make sure it is set to ATA instead of Raid.


Novensu
That's probably not gonna help him. It's his native 8233a/8235 controller that's gone wonky, not the promise controller. Odds are that the promise controller doesn't support optical ATAPI devices well, if at all.

Stealth5325, have you tried killing those latest Hyperion drivers via Driver Cleaner or the like and installing the older 4.43 4-in-1's? Those are supposed to offer better compatibility for older VIA chipsets.

edit: You could also try a bootdisk with CD-ROM support ( www.bootdisk.com ) and test disc access in DOS mode...if you can read files, it might just be your chipset drivers that are fucked up. if you can't, you might try another CD-ROM drive to verify that your onboard controller is in fact bad.
 
If the drive shows up during POST, and also shows in CMOS, then I think you have a Windows problem rather than a motherboard problem. Nylint's suggestion sounds like a good one. Also, I'd double check the CMOS settings, making sure that the primary and secondary IDE controllers are set to default, rather than some manual setting that is causing problems. If in doubt, try clearing CMOS.

When did this problem begin?
 
nylint said:
That's probably not gonna help him. It's his native 8233a/8235 controller that's gone wonky, not the promise controller. Odds are that the promise controller doesn't support optical ATAPI devices well, if at all.

Stealth5325, have you tried killing those latest Hyperion drivers via Driver Cleaner or the like and installing the older 4.43 4-in-1's? Those are supposed to offer better compatibility for older VIA chipsets.

edit: You could also try a bootdisk with CD-ROM support ( www.bootdisk.com ) and test disc access in DOS mode...if you can read files, it might just be your chipset drivers that are fucked up. if you can't, you might try another CD-ROM drive to verify that your onboard controller is in fact bad.

I didn't think of that.
 
It was apparently fixed by changing from an ACPI uniprocessor PC to an ACPI Computer HAL. Dunno wtf was going on, but I WILL try the 4.43 4-in-1's, thanks for the suggestion!
 
Back
Top