VOGONS


First post, by BaronSFel001

User metadata
Rank Newbie
Rank
Newbie

...my 20th century time machine PC, that is. While I may replace/upgrade some of the existing components in time, right now I have all the function I would like save for this one final issue.

Ever since I bought it (new in the box) my Aureal SQ2500 has refused to install in Windows 98 SE. I have tried everything from resetting IRQ assignments in the BIOS, to trying different PCI slots, to formatting the hard drive and attempting to reinstall it from scratch as the only PCI device (besides the necessary graphics card, of course). No matter what the exact same thing happens: Windows has no problem detecting the sound card's presence but then totally locks up at every attempt to add it to the driver information database. Attempts to install manually have also been unsuccessful as the driver information database step appears to be necessary for Windows to make use of the card, judging by the fact that every time I restart the computer Windows keeps going back to the first step of the hardware installation wizard even though the driver itself is already in the Windows folder.

I have heard of other people having this problem but steps to compensate vary. What alternatives have I missed so far?

System 20: PIII 600, LAPC-I, AWE64, S220, Voodoo3, SQ2500, R200, 3.1-Me
System 21: G2030 3.0, X-fi Fatal1ty, GTX 560, XP-Vista
Retro gaming (among other subjects): https://baronsfel001.wixsite.com/my-site

Reply 1 of 11, by soviet conscript

User metadata
Rank Oldbie
Rank
Oldbie

I know this doesn't help but Ive had the same issue with Vortex cards, specifically the Diamond Monster card. some PC's it just locks up on me when I'm triyng to install it, other machines it installs with no problem whatsoever.

Reply 2 of 11, by PhilsComputerLab

User metadata
Rank l33t++
Rank
l33t++

Try the INF driver tweaks from VOGONS driver archive. There is one for PCI detection. Though when I had to do this, I always got an error message on the screen.

YouTube, Facebook, Website

Reply 3 of 11, by stuvize

User metadata
Rank Member
Rank
Member

I have had Aureal chips do this usually it is a hardware conflict for IRQ or no PNP in the BIOS. What motherboard are you using? if it is not plug and play you will have to set IRQ manually in the BIOS but it sounds like you've tried that. Make sure PNP OS option is turned on in your BIOS you could also try turning PNP OS off it seems to vary on the motherboard

Reply 4 of 11, by BaronSFel001

User metadata
Rank Newbie
Rank
Newbie

Motherboard is AX6BC with the standard Intel i440 chipset: a very popular and ideal setup from back in the day which is how I cannot conceive why there would be such a critical motherboard compatibility issue. All BIOS settings are set to PnP though I tried tweaking them a bit with no change in the results. This problem seems to never have been officially-documented by Aureal or Microsoft, another unpleasant surprise considering how I am far from the only person to experience it. I tried a reverse approach by installing the driver without the card inserted, and that step worked; but as soon as I inserted the card (surprise) Windows locked up, and when I restarted it went back to square one with PnP hardware detection as if the driver never got installed in the first place.

System 20: PIII 600, LAPC-I, AWE64, S220, Voodoo3, SQ2500, R200, 3.1-Me
System 21: G2030 3.0, X-fi Fatal1ty, GTX 560, XP-Vista
Retro gaming (among other subjects): https://baronsfel001.wixsite.com/my-site

Reply 5 of 11, by BaronSFel001

User metadata
Rank Newbie
Rank
Newbie
philscomputerlab wrote:

Try the INF driver tweaks from VOGONS driver archive. There is one for PCI detection. Though when I had to do this, I always got an error message on the screen.

Not sure I am finding what you are referring to. What exactly is it called and how does it work?

Meanwhile I will make another attempt with the Aureal support drivers from the archive; thus far I have been attempting the install using the supplied Aureal support CD which may not be providing the most current set.

System 20: PIII 600, LAPC-I, AWE64, S220, Voodoo3, SQ2500, R200, 3.1-Me
System 21: G2030 3.0, X-fi Fatal1ty, GTX 560, XP-Vista
Retro gaming (among other subjects): https://baronsfel001.wixsite.com/my-site

Reply 6 of 11, by firage

User metadata
Rank Oldbie
Rank
Oldbie

Haven't had this problem. What's the graphics card you're running it with? Suppose it could still be a specific IRQ one of your components is super protective of. If you didn't do it yet, one of the first things I'd try is toggling the PnP OS setting as suggested already.

Edit: Read the manual for that thing. The BIOS options are a little different. A little arduous, there's probably some IRQ that you need to reserve manually. Noticed there's a toggle for ACPI, which you might look into disabling for your next 98SE installation.

My big-red-switch 486

Reply 7 of 11, by ZanQuance

User metadata
Rank Member
Rank
Member

Now that my semester is wrapping up (finals this week) I'm getting more time to spend supporting these cards.

If you can, make sure the card itself is okay by installing it into an XP or Windows7 machine and use this attached driver. If it works then it's most certainly a hardware conflict on your retro machine, since you've tried the obvious solutions it also might be the driver version you're attempting to install, so try with the 2041, 2048 and 2050 drivers.

Attachments

  • Filename
    AU8830.7z
    File size
    243.13 KiB
    Downloads
    51 downloads
    File license
    Fair use/fair dealing exception

Reply 8 of 11, by BaronSFel001

User metadata
Rank Newbie
Rank
Newbie
firage wrote:

Haven't had this problem. What's the graphics card you're running it with? Suppose it could still be a specific IRQ one of your components is super protective of. If you didn't do it yet, one of the first things I'd try is toggling the PnP OS setting as suggested already.

Edit: Read the manual for that thing. The BIOS options are a little different. A little arduous, there's probably some IRQ that you need to reserve manually. Noticed there's a toggle for ACPI, which you might look into disabling for your next 98SE installation.

Yes, tried that already; the BIOS frontend and documentation make it abundantly clear it was designed with Windows 95/98 in mind, and while it defaults to PnP OS being on, for compatibility purposes I would prefer it off. In any case, while I had it on I checked and Windows 98 was set to handle IRQ bridging which conceivably should have kept things from happening (that is, if IRQ conflict is the actual cause here). Doubt the graphics card is the issue: getting the same results whether I use a Voodoo Banshee in the AGP slot or ViRGE 325 in a PCI slot.

Where do you seen an ACPI option? I could not find one.

ZanQuance wrote:

If you can, make sure the card itself is okay by installing it into an XP or Windows7 machine and use this attached driver.

Not an option, my modern desktop has only PCIe bus, while my XP-era machines are all laptops.

System 20: PIII 600, LAPC-I, AWE64, S220, Voodoo3, SQ2500, R200, 3.1-Me
System 21: G2030 3.0, X-fi Fatal1ty, GTX 560, XP-Vista
Retro gaming (among other subjects): https://baronsfel001.wixsite.com/my-site

Reply 10 of 11, by firage

User metadata
Rank Oldbie
Rank
Oldbie
BaronSFel001 wrote:

Where do you seen an ACPI option? I could not find one.

'ACPI Function' at the top of the Power Management Setup menu, if the manual can be trusted.

My big-red-switch 486

Reply 11 of 11, by PhilsComputerLab

User metadata
Rank l33t++
Rank
l33t++
BaronSFel001 wrote:
philscomputerlab wrote:

Try the INF driver tweaks from VOGONS driver archive. There is one for PCI detection. Though when I had to do this, I always got an error message on the screen.

Not sure I am finding what you are referring to. What exactly is it called and how does it work?

http://www.vogonsdrivers.com/getfile.php?file … =443&menustate=

YouTube, Facebook, Website