Which packs do I need for these soundchips?

First off, why not start with posting HWID's?

then extract Sound A/B; then search for your specific HWID in the files "*.inf" including VENdor, DEVice, and SUBsystem.
  eg:  VEN_1102&DEV_0004&SUBSYS_00401102.
Results from this search should be more likely to specifically support your HW.
   if that yields no results, search for the VENdor & DEVice ID's.  eg:  VEN_1102&DEV_0004

This should generate a 'short-list' of candidates.  Test the drivers (backup important data, 1st).
  I like using the D-P-C checker to potentially reveal poor-performing drivers
    before & after updating drivers (especially Atheros WiFi)

  A similar solution may apply to the Graphics drivers you mentioned in your other post.

PS:  self-help is encouraged here.  we can help point the way, yet you must do the 'heavy lifting'.
          speaking of "pointing the way";  who's logo is on the audio chip upon the 'Intel 82801AA' board?
PPS:       Don't forget to read mr_smartepants' "Driverpacks Tutorial" linked in his sig.
PPPS:       The HW you mention may be prone to Bad Capacitors,
                  depending upon the capacitor manufacturer.

Last edited by TechDud (2012-04-17 17:51:53)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

Normally I would but I don't have access to the hardware in question (except for when I visit the owner every couple of weeks), so I'm relying on the Aida32 reports I've got, which unfortunately don't seem to list the HWIDs. I'll check them next time I'm there and have a look at the logo on the Intel board audio chip. It's an HP Vectra VL400 and I've found a manual for it that says "The Crystal® integrated PCI audio solution (not upgradeable) in your PC is a CrystalClear™ CS4299 Audio Codec ‘97 version 2.1. The CS4299 interfaces directly with the South Bridge chip and performs all digital operations, such as sample rate conversions and synthesis, as well as mixing and processing all the analog signals." I've never heard of CrystalClear!

I've been using DriverPack Chipset checker for a while and LatencyMon more recently and as you say, they are essential tools for checking that some device/driver isn't causing problems.

Thanks for the warning about bad caps.

Thanks very much. I'll try those XP drivers to check if one/both work.

Once I've done that, I'll be happy to start a new REQ topic as you advise, although there doesn't appear to be a separate Sound_B section, so I guess it'll just go in this section.

Thanks for the pointers (Ah, Vacuum Tubes, they used to keep me nice and warm!)

I'm actually working on replacing the 20GB HDD with a 4GB CF card and IDE adapter, although it wouldn't boot from that when I tried the other day (although it worked fine once XP was booted and another PC I tested it on boots from it no problem), so I might have to get an IDE card for that to work. Maybe PLOP would help, but then I'd have to leave the HDD connected to run that first, which kinda defeats the point of reducing noise and power usage (although it will still work a lot faster than the knackered old HDD).

To be honest I didn't have enough time to test it much and only tried to boot grub4dos from the HDD and then boot the CF card from there. That works on another PC, but perhaps booting directly to the CF card will work on the VL400, which I'll try next time I get access to it.

I think the ATA mode would depend on the IDE-CF adapter rather than the actual CF card and I'm not sure what that is, but probably ATA133.

If there's a chip it's invisible! It's basically one of these http://www.ebay.co.uk/itm/DUAL-CF-to-40 … 5ad6ed8a6d

I've generally found in the past that ATA133 devices will just run at ATA100 on older hardware (as with PC133 RAM running at PC100, despite all the manufacturer's info telling me it's not compatible). I formatted it as FAT32 anyway to keep things as simple as possible