Thanks Paul, good to still have you on the case.
But I'd appreciate starting with the real basics please before focusing on
finding the Creative driver.
I'm wondering if you saw my last two paras? Maybe I should have started
with those instead of describing the driver aspects, sorry.
That's why I can't simply do the obvious.
And FWIW here again is the screenshot from the previous 'standstill'
thread showing all 4 of the ancient CDs I turned up as potentially
relevant:
https://dl.dropboxusercontent.com/u/4019461/Old-CDs.jpg
--------------------
https://dl.dropboxusercontent.com/u/4019461/Athlon-Onboard-PCI-Audio.jpg
I've worked with it in both Disabled and Enabled states. That
image was an old, pre-crash photo, when the PC was running OK, including
audio.
--------------------
So in summary I'm badly in need of a methodical approach that essentially
starts from scratch. A reassuring starting point would be getting a beep
out of my PC speaker!
Should I be able to achieve that with NEITHER 'Onboard PCI Audio' enabled,
NOR an independent sound card installed? If so, how?
When buying my refurbished HD last week from my local High Street computer
shop I learned that he occasionally refurbishes old PCs too. I'm guessing
he rarely has the original setup CDs. So he must tackle it with the sort
of grass roots approach I'm seeking.
Possibly. I've had a couple reports in the past, where a Creative
card actually burns a couple pins on a PCI slot. That's not the
likely cause in this case. That kind of thing happens when first
plugging a card in, and there is a problem with the design. Your
system was working for eons, so it's not the likely reason.
*******
Mike's got some good advice.
The equivalent to Linux "lspci" in Windows, is to use a copy of Everest.
Everest will list all the PCI devices it sees, even if Everest
does not have a name string in its internal database for the card.
The program still provides useful info, via the vendor and device
hex values.
http://www.majorgeeks.com/files/details/everest_free_edition.html
Download link (4MB file):
(
http://www.majorgeeks.com/mg/getmirror/everest_free_edition,1.html )
The vendor and device info is available for each card. If you
enabled the onboard sound, and it was on the PCI bus, it should
show up with its own entry. If the Creative card is present, it
should show up. You can have two sound cards enabled at the same
time, and the Windows sound panel will allow you to select one
or the other as an output devices.
When I had a PCI sound card, where one gold contact
was not making a good electrical connection, then an <unknown> entry
showed up, and the ven/dev info was corrupted in one bit position.
It was a bit tricky in that case, to look up the value and make
sense of it. But because I knew my sound chip was CMI8738, I could
compare the known value for it, to the everest value.
Here, I'm showing a sample chip, just to show how to read it.
http://imageshack.us/a/img844/5241/everestpci.gif
You then compare the ven/dev to this list, if you don't know what
the card is. Doing this, is to verify what the card actually is.
In the example, Everest listed 1106-3044 for the device and
1043-81FE for the subsystem. If ten cards are all based on the
same chip (1106-3044), they will each be given a different subsystem
to make them unique. There are too many cards to list all possible
subsystem values, so my instance is not shown. But that is not
important. At least I know I have "VT6306/7/8" as a chip, in
this example
http://pciids.sourceforge.net/pci.ids
1106 VIA Technologies, Inc.
3044 VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
0010 0001 IEEE 1394 4port DCST 1394-3+1B
1025 005a TravelMate 290
103c 2a20 Pavilion t3030.de Desktop PC
103c 2a3b Media Center PC m7590n
1043 808a A8V/A8N/P4P800 series motherboard
1043 81fe Motherboard
1458 1000 GA-7VT600-1394 Motherboard
1462 207d K8NGM2 series motherboard
1462 217d Aspire L250
1462 590d KT6 Delta-FIS2R (MS-6590)
1462 702d K8T NEO 2 motherboard
1462 971d MS-6917
I don't have a PCI soundcard in the machine, to make a
good example from it, so I just picked my Firewire chip
as an example.
Your onboard sound is supposed to be a CMEDIA 8738 of some sort.
If you cannot read the motherboard CD, then the CMEDIA site
might still have a driver. CMEDIA had to stop shipping the driver
for a while, because Creative bought a company that provided
a licensed technology to CMEDIA, would not renew the license
(to upset a competitor's business), and CMEDIA had to rewrite
old drivers. Took about a year, during which you could not
download a driver. From memory, at least for my two old CMI8738
cards, seeing these numbers would prove the card was fitted in the
slot OK, or otherwise properly detected (as it's soldered to
your motherboard).
13f6 C-Media Electronics Inc
0111 CMI8738/CMI8768 PCI Audio
A rather daunting list.
http://www.cmedia.com.tw/EN/DownloadCenter_Detail2.aspx?Serno=118&pserno=0&dtype=ALL
And the article here, doesn't really help us tell them apart.
http://en.wikipedia.org/wiki/C-Media
So you'd better hope the motherboard CD is readable.
*******
There are applications for scavenging optical discs. And
you could try your CD collection in more than one PC, use
an application like the free Imgburn, make an ISO9660 out
of the scratchy original, burn a new CD, and carry that out
to the shed PC. (You could do the same kind of thing with
Nero.)
http://en.wikipedia.org/wiki/Imgburn
*******
You could try the Asus download for a7a266-E sound.
http://support.asus.com/Download.aspx?SLanguage=en&m=A7A266-E&p=1&s=10
Audio
Windows XP Audio Driver V5.12.01.0638
3,48 (MBytes) 2002.07.03 update
http://dlcdnet.asus.com/pub/ASUS/misc/audio/c-media/cm288b_xp.zip
In there, is "CMAUDIO.INF" file. Using Notepad, there are many
lines in there, indicating which devices the driver supports.
I think "1043" is the subsys for an Asus motherboard. Each
motherboard ("8035") may have a unique entry. The main chip
number remains 13F6 and 0111.
CMI8738.DeviceDesc%=PCI13, PCI\VEN_13F6&DEV_0111&SUBSYS_80351043
So you've got a driver right there, if you need one. Or, want
to compare it to the INF inside one of the Win2K/WinXP drivers
on the CMedia site.
*******
So while I wandered off in usual fashion, Everest is where
you start, to enumerate the PCI bus and see what is
present. If your card is not making good contact, you
may see an <unknown> entry. And then, you use the pci.ids
file on the web, to figure out what you've got.
A Linux LiveCD and "lspci" will enumerate the bus as well.
It's not easy to explain this stuff over USENET, or
successfully pick a driver for you at a distance. Too
much can go wrong.
Paul