Can't Get Audio On This Pavillion 700

[roger]

Before I give up, I thought I'd at least ask what anyone might think
is wrong here.

I am trying to resurrect this HP Pavilion 700 System # P8564A.
Only had to download and install two drivers, audio and video to
satisfy Device Manager. Specifically 'sp35461.exe' for audio and
'sp26446.exe' for video. The audio driver is said to be 'Realtek AC97
WDM Audio Driver by HP'.

I have VLC V2.1.3 and MediaPlayer Classic V6.4.9.0 installed.
Neither will produce sound from an audio CD of .cda files that I know
has good music on it. VLC shows the tracks playing with no audio,
but Media Classic only shows a warning window that in brief says:

Could not render some of the pins in the graph, you may not have the
needed codecs or filters installed on the system.
Audio Switcher:: Out
Media Type 0.
etc

and a button that says 'look for codecs on the net'. Which I tried
without success - may be my fault on that.

Anyway, I am wondering if the on-board audio is bad. If so, I am
wasting my time. The BIOS shows audio to be enabled.

Thanks

Big Fred

 

[Paul]

Before I give up, I thought I'd at least ask what anyone might think
is wrong here.

I am trying to resurrect this HP Pavilion 700 System # P8564A.
Only had to download and install two drivers, audio and video to
satisfy Device Manager. Specifically 'sp35461.exe' for audio and
'sp26446.exe' for video. The audio driver is said to be 'Realtek AC97
WDM Audio Driver by HP'.

I have VLC V2.1.3 and MediaPlayer Classic V6.4.9.0 installed.
Neither will produce sound from an audio CD of .cda files that I know
has good music on it. VLC shows the tracks playing with no audio,
but Media Classic only shows a warning window that in brief says:

Could not render some of the pins in the graph, you may not have the
needed codecs or filters installed on the system.
Audio Switcher:: Out
Media Type 0.
etc

and a button that says 'look for codecs on the net'. Which I tried
without success - may be my fault on that.

Anyway, I am wondering if the on-board audio is bad. If so, I am
wasting my time. The BIOS shows audio to be enabled.

Thanks

Big Fred

Have you looked in Device Manager ?

Try Start : Run : devmgmt.msc

Then look for an audio device. Chances are, it lists a problem
with starting the driver you've installed.

If an audio device had "registered" with the OS, those
errors probably wouldn't be showing up.

Now, normally with computer hardware testing, I'd be telling
you to test with a Linux LiveCD. But getting sound to work
there, can be every bit as miserable as Windows, so you're
no more likely to get a squeak out of it in Linux, than
in Windows. Sometimes, it's a mute control or ALSA Mixer
or some Gnome equivalent of the ALSA Mixer. I don't want
to "double your pleasure", by giving you another
seemingly dead end to testing. Stick with Windows for now.

Audio solutions can have a control panel of some sort.
With a "test" button to apply a test tone to the speakers.
If you can't even find the control panel, that would be
a clue the driver didn't install. I've even had my CMI8738
PCI audio cards, refuse to put up the control panel, due to
a driver installation issue. So things kinda work, but no
convenient panel to set the configuration with (stereo or 5.1
etc). RealTek has in the past, provided such control panels,
even in situations where the audio is pitiful. For example,
my laptop has stereo in and stereo out only (two jacks), and
there is still a control panel to look at, to tell you
what a poor solution you bought

Looks kinda like this, same color scheme perhaps...

http://social.microsoft.com/Forums/getfile/37053/

This is another example of a Realtek panel. The manufacturer
name overwrites where the word Realtek should be.

http://www.nitroware.net/images/stories/realtek/realtek_xp5.png

If you sort the driver problem out, and there is still no sound,
remember that front panel jacks and cabling, can be part of the
problem. The Line-out is routed through the front panel jacks
(side-contact switch closure). If the internal cable to the
front panel gets disconnected from the motherboard, that can
"break" the Line-Out signal on the back of the computer. If you
remove that cable assembly, two jumper plugs have to be placed
on the appropriate locations on the audio 2x5 header or similar.
In a "strange" machine, it's just better to put the cabling back
as it's supposed to be. If you don't have the documentation for
the machine. While there is a standard for AC'97, it didn't exist
initially, and various pinouts were tried by the manufacturers.

Paul

 

[roger]

Have you looked in Device Manager ?

Try Start : Run : devmgmt.msc

Then look for an audio device. Chances are, it lists a problem
with starting the driver you've installed.

If an audio device had "registered" with the OS, those
errors probably wouldn't be showing up.

Hi Paul. As I said above, Device Manager seems okay:

Only had to download and install two drivers, audio and video to
satisfy Device Manager. Specifically 'sp35461.exe' for audio and
'sp26446.exe' for video. The audio driver is said to be 'Realtek AC97
WDM Audio Driver by HP'.


Now, normally with computer hardware testing, I'd be telling
you to test with a Linux LiveCD. But getting sound to work
there, can be every bit as miserable as Windows, so you're
no more likely to get a squeak out of it in Linux, than
in Windows. Sometimes, it's a mute control or ALSA Mixer
or some Gnome equivalent of the ALSA Mixer. I don't want
to "double your pleasure", by giving you another
seemingly dead end to testing. Stick with Windows for now.
ok

Audio solutions can have a control panel of some sort.
With a "test" button to apply a test tone to the speakers.
If you can't even find the control panel, that would be
a clue the driver didn't install. I've even had my CMI8738
PCI audio cards, refuse to put up the control panel, due to
a driver installation issue. So things kinda work, but no
convenient panel to set the configuration with (stereo or 5.1
etc). RealTek has in the past, provided such control panels,
even in situations where the audio is pitiful. For example,
my laptop has stereo in and stereo out only (two jacks), and
there is still a control panel to look at, to tell you
what a poor solution you bought

Looks kinda like this, same color scheme perhaps...

http://social.microsoft.com/Forums/getfile/37053/

I have a funny-looking display on the screen called AVRACK by Realtek.
It even has a recorder panel and a mixer panel. It shows the tracks
on the audio CD, and I can select them. But the play indicator does
not move - hence no sound that way either. The play indicator should
at least move I would think. The play indicator at least moved in
VLC.

This is another example of a Realtek panel. The manufacturer
name overwrites where the word Realtek should be.

http://www.nitroware.net/images/stories/realtek/realtek_xp5.png

If you sort the driver problem out, and there is still no sound,
remember that front panel jacks and cabling, can be part of the
problem. The Line-out is routed through the front panel jacks
(side-contact switch closure). If the internal cable to the
front panel gets disconnected from the motherboard, that can
"break" the Line-Out signal on the back of the computer. If you
remove that cable assembly, two jumper plugs have to be placed
on the appropriate locations on the audio 2x5 header or similar.
In a "strange" machine, it's just better to put the cabling back
as it's supposed to be. If you don't have the documentation for
the machine. While there is a standard for AC'97, it didn't exist
initially, and various pinouts were tried by the manufacturers.

Paul

Thank you for response.

Big Fred

 

[philo]

Before I give up, I thought I'd at least ask what anyone might think
is wrong here.

I am trying to resurrect this HP Pavilion 700 System # P8564A.
Only had to download and install two drivers, audio and video to
satisfy Device Manager. Specifically 'sp35461.exe' for audio and
'sp26446.exe' for video. The audio driver is said to be 'Realtek AC97
WDM Audio Driver by HP'.

I have VLC V2.1.3 and MediaPlayer Classic V6.4.9.0 installed.
Neither will produce sound from an audio CD of .cda files that I know
has good music on it. VLC shows the tracks playing with no audio,
but Media Classic only shows a warning window that in brief says:
X

Make sure sound is not set to "mute"

 

[Paul]

Thank you for response.

Big Fred

If you have multiple audio solutions (RealTek on
motherboard, PCI sound card as well), make sure
you've selected one of the two as your default
audio output.

http://img.brothersoft.com/screensh...efinition_audio_driver-491703-1334801266.jpeg

The AVRack should have some sort of Test button,
to put a tone onto the speakers.

http://www.nf7sextreme.lvcoyote.com/images/SpeakerTest.jpg

Also, your PC uses an un-amplified Polk Audio set of
stereo speakers. It means the PC has something like
a 2W amp on each channel, to drive the speaker. So
it's not the same division of labor, as a regular
PC. On a regular PC, you use an amplified speaker,
and connect that to the Line-Out.

But your symptoms seem to be related to software
communications to the driver. I know of at least
one "hole" you can fall into with HDAudio, but
I haven't heard of any for the AC'97 you're working
with. That should work, as long as the manufacturer
driver gets installed. Maybe malware could mess it up,
but it should be relatively rugged under normal
circumstances.

Paul

 

[roger]

Make sure sound is not set to "mute"

Good Point!
But I did check that.

Thanks

Big Fred

 

[roger]

If you have multiple audio solutions (RealTek on
motherboard, PCI sound card as well), make sure
you've selected one of the two as your default
audio output.

http://img.brothersoft.com/screensh...efinition_audio_driver-491703-1334801266.jpeg

Aha! Under Default Device it says 'no playback devices'.
Something is awry here.

The AVRack should have some sort of Test button,
to put a tone onto the speakers.

I've looked. I'll look again.

http://www.nf7sextreme.lvcoyote.com/images/SpeakerTest.jpg

Also, your PC uses an un-amplified Polk Audio set of
stereo speakers. It means the PC has something like
a 2W amp on each channel, to drive the speaker. So
it's not the same division of labor, as a regular
PC. On a regular PC, you use an amplified speaker,
and connect that to the Line-Out.

But your symptoms seem to be related to software
communications to the driver. I know of at least
one "hole" you can fall into with HDAudio, but
I haven't heard of any for the AC'97 you're working
with. That should work, as long as the manufacturer
driver gets installed. Maybe malware could mess it up,
but it should be relatively rugged under normal
circumstances.

I am connected to a set of earphones.

Thanks again Paul

Big Fred

 

[roger]

Aha! Under Default Device it says 'no playback devices'.
Something is awry here.

In Device Manager, under Sound, video and game controllers I see:

Audio Codecs
Legacy Audio Drivers
Legacy Video Capture Devices
Media Control Devices
Multimedia Audio Controller <====this one is flagged yellow! Must be
the problem?

Big Fred
Video Codecs

 

[Paul]

In Device Manager, under Sound, video and game controllers I see:

Audio Codecs
Legacy Audio Drivers
Legacy Video Capture Devices
Media Control Devices
Multimedia Audio Controller <====this one is flagged yellow! Must be
the problem?

Big Fred
Video Codecs

Do Properties on the yellow entry.

There is a Device Status box.

What is the code ? Code 10 ? Look it up.

Mine right now, says "This device is working properly".

Paul

 

[roger]

Do Properties on the yellow entry.

There is a Device Status box.

What is the code ? Code 10 ? Look it up.

Mine right now, says "This device is working properly".

Paul

code 28

 

[philo]

es.

code 28

Interesting, but I have a machine on my bench now...an HP

and I got the sound drive directly from HP and I had a device manager error.

Fortunately I have AC97 drivers from other sources and one of them worked.

I did end up using one labeled as Realtek but did not get it from
HP...it was on a universal driver CD I downloaded a while back.

 

[roger]

Interesting, but I have a machine on my bench now...an HP

and I got the sound drive directly from HP and I had a device manager error.

Fortunately I have AC97 drivers from other sources and one of them worked.

I did end up using one labeled as Realtek but did not get it from
HP...it was on a universal driver CD I downloaded a while back.

Sure wish I had a copy to try. Don't lose it.

Big Fred

 

[Paul]

Sure wish I had a copy to try. Don't lose it.

Big Fred

Realtek are available from the RealTek site. Tick the Accept
box here, and the driver page should show up. If you're running
WinXP, look for the WinXP one.

http://www.realtek.com.tw/downloads...=23&Level=4&Conn=3&DownTypeID=3&GetDown=false

I take it, Windows 8 doesn't show there, because the RealTek
driver is built-in or something.

Paul

 

[roger]

Realtek are available from the RealTek site. Tick the Accept
box here, and the driver page should show up. If you're running
WinXP, look for the WinXP one.

http://www.realtek.com.tw/downloads...=23&Level=4&Conn=3&DownTypeID=3&GetDown=false

I take it, Windows 8 doesn't show there, because the RealTek
driver is built-in or something.

Paul

Thanks anyway.

I downloaded and installed three variations of the Realtek AC'97
drivers (A406) on the XP machine. All installed okay seemingly, but
the Driver Agent Sound Controller - Multimedia Audio Controller
remains flagged yellow with the code 28. Weird.

Big Fred

 

[Paul]

Thanks anyway.

I downloaded and installed three variations of the Realtek AC'97
drivers (A406) on the XP machine. All installed okay seemingly, but
the Driver Agent Sound Controller - Multimedia Audio Controller
remains flagged yellow with the code 28. Weird.

Big Fred

Something has got to be broken in the OS for that to happen.

I wonder if the RealTek installer left a log file somewhere ?

Paul

 

[roger]

Something has got to be broken in the OS for that to happen.

I wonder if the RealTek installer left a log file somewhere ?

Paul

A Google of 'Realtek code 28' shows several forums concerning this
problem (suggests I am not alone for sure). I will have to check each
one I guess:

http://www.windowsanswers.net/articles/fix-code28?tid=code28goog&gclid=CM77i7LG1bwCFTHNOgodLEYAVQ

http://en.softonic.com/s/realtek-97-ac-code-28

http://www.tomshardware.com/forum/261364-45-code-driver-ac97-realtek-soundcard

http://en.kioskea.net/forum/affich-18394-no-sound-no-audio-device-and-unknowns

http://forums.majorgeeks.com/showthread.php?t=159281

https://www.google.com/search?newwi...15.0....0...1c.1.35.hp..1.14.2127.5cNADV5uFkM

http://tutorial.downloadatoz.com/download/code+28+driver+download.html

http://www.techsupportforum.com/forums/f23/solved-realtek-wont-install-167845.html

http://social.technet.microsoft.com...ation-network-controller-sub-via-realtek-wlan

I subscribe to DriverAgent, and have downloaded and tried the Realtek
driver suggested (sp35461.exe) by them. It is for the AC97 WDM audio
driver. It failed identically.

Thanks

Big Fred

 

[Paul]

A Google of 'Realtek code 28' shows several forums concerning this
problem (suggests I am not alone for sure). I will have to check each
one I guess:

http://www.windowsanswers.net/articles/fix-code28?tid=code28goog&gclid=CM77i7LG1bwCFTHNOgodLEYAVQ

http://en.softonic.com/s/realtek-97-ac-code-28

http://www.tomshardware.com/forum/261364-45-code-driver-ac97-realtek-soundcard

http://en.kioskea.net/forum/affich-18394-no-sound-no-audio-device-and-unknowns

http://forums.majorgeeks.com/showthread.php?t=159281

https://www.google.com/search?newwi...15.0....0...1c.1.35.hp..1.14.2127.5cNADV5uFkM

http://tutorial.downloadatoz.com/download/code+28+driver+download.html

http://www.techsupportforum.com/forums/f23/solved-realtek-wont-install-167845.html

http://social.technet.microsoft.com...ation-network-controller-sub-via-realtek-wlan

I subscribe to DriverAgent, and have downloaded and tried the Realtek
driver suggested (sp35461.exe) by them. It is for the AC97 WDM audio
driver. It failed identically.

Thanks

Big Fred

There is a claim here, it can be solved by changing a setting
for a Windows Audio Service in Services. I have no way of
verifying this.

http://www.pchell.com/support/no_active_mixer_devices_available.shtml

( link from http://en.kioskea.net/forum/affich-18394-no-sound-no-audio-device-and-unknowns )

This is the audio service I see in WinXP. Mine is working.
But my system is HDAudio and not AC'97, so not quite the same.

http://i61.tinypic.com/2i7a8ms.gif

Paul

 

[roger]

There is a claim here, it can be solved by changing a setting
for a Windows Audio Service in Services. I have no way of
verifying this.

http://www.pchell.com/support/no_active_mixer_devices_available.shtml

( link from http://en.kioskea.net/forum/affich-18394-no-sound-no-audio-device-and-unknowns )

This is the audio service I see in WinXP. Mine is working.
But my system is HDAudio and not AC'97, so not quite the same.

http://i61.tinypic.com/2i7a8ms.gif

Paul

Mine is set properly to automatic.

Thanks

Big Fred

 

[Paul]

Mine is set properly to automatic.

Thanks

Big Fred

I've been trying to find some info on what components
(regsvr32 type stuff) might be involved, but I'm having
no luck in a search engine. I don't know how to reset
the sound system part that connects to the driver.

As far as I know, your Pavilion 700 uses an Asus OEM motherboard
A7M266-M. It is not similar to A7M266 Retail motherboard (for which
the Asus site has driver support). The motherboard is Bermuda/BoraBora,
implying perhaps more than one model of the same thing. It uses an
AMD761 Northbridge and a VIA 686B Southbridge (split-brand chipset).
Since sound is off the Southbridge, we pretend it's a "VIA Chipset".

(23 page pseudo-manual for your motherboard - more than Asus would
normally prepare for end-user consumption, but still inadequate)

http://www.elhvb.com/mboards/OEM/HP/manual/bermuda_manual.pdf

The way AC'97 works, is a driver combines support for the AC'97
Codec details (3 or 6 jack config, PNP 12 bit number for CODEC
declaration), as well as for the Southbridge end. So something
on the Southbridge end is also custom, and the driver sets it up.

<---- driver ---->
Southbridge ---- RealTek --- 3 jacks, to amplified speakers
AC'97

I downloaded this file (since you suggested it, and I couldn't
find it in the Pavilion 700 driver section), and it does use
a naming convention consistent with multiple Southbridge support.
So it probably has VIA support for the Southbridge end of the link.

ftp://ftp.compaq.com/pub/softpaq/sp35001-35500/sp35461.exe

First, I stumbled on a 64 bit INF file, for a later OS.

[SourceDisksFiles]
ALCWDM64.SYS=222
SOUNDMAN.EXE=222
ALSNDMGR.CPL=222
ALSNDMGR.WAV=222
RTLCPL.EXE=222
RtlCPAPI.dll=222
CPLUtl64.exe=222
Alcrmv64.exe=222

[DestinationDirs]
AC97AUD.CopyList=10, system32\drivers

[Realtek.NTamd64]
%ALCVIA.Desc%=AC97VIA, PCI\VEN_1106&DEV_3058&CC_0401

As far as I can figure out, VEN 1106 is VIA, and
DEV 3058 is a common device identifier for VIA Sound
in old Southbridges. Since there is a match in the file,
it does appear that the INF is intended for this class
of hardware.

But I can't offer any other insights as to what is
supposed to happen. As I can't find any info on what
OS sound files connect to these things, and might benefit
from some sort of repair.

I do know from personal experience, all it takes is installing
a second sound card, a card with a bad driver design, to
shoot the sound in the first device in the foot. I had a driver
that abused a registry entry (by removing it), which prevented
the other device from working. And even if that bad driver was
removed, the registry entry wasn't coming back. And the first
driver did not have the common sense to create a new registry
entry. I think the registry entry was created by the OS. After
I made a registry entry for it manually, it started working
again. So I do know of that one example.

And a "driver cleaner" wouldn't have helped in a case like that.

A "Hail Mary" approach to fixing it, would be "sfc /scannow",
which is supposed to check and replace system files. But since
that never seems to get mentioned in a resolution to this problem,
I'm guessing it doesn't help.

I tried an ident on ALCWDM64.SYS, and it says it is for a
64 bit OS, and is a .NET assembly. So that tells me the
first INF file I tried, is for a 64 bit OS. Pretty strange
to offer such a driver package, for your vintage of computer.
There's probably one guy out there in the world, using
that combination of hardware and OS

The install folder is chock full of .inf files, and another
one of interest might be alcxau.inf

[SourceDisksFiles]
ALCXWDM.SYS=222
SOUNDMAN.EXE=222
ALSNDMGR.CPL=222
ALSNDMGR.WAV=222
RTLCPL.EXE=222
RtlCPAPI.dll=222
Alcrmv.exe=222

[DestinationDirs]
AC97AUD.CopyList=10,system32\drivers

So maybe that's what it would copy on your 32 bit system.

When I check ALCXWDM.SYS, it says it is for a 32 bit OS and is
not a .NET assembly. It's a plain executable. And that's more
consistent with older OSes. As is the accompanying ALCXWDM.cat
file with the security information.

You can look in the setupapi.log file, to see an entry around
the time the sound driver was installed.

When an INF file is used for installation, a copy is
put in the INF folder in the system folder. But, the idiots
rename the file to "OEM23.INF", as a means of preventing
name collisions (OEMxx). If the INF file contains a reference to
its own name, you can then see if the INF made it to the
INF folder. It's just an indicator that the driver installation
attempt got part way along. Of course, in the Device Manager,
you can also use the tab that shows the driver files, to
get some idea whether they got installed or not.

I don't have any concrete advice to go on now - I would
be "picking over the scraps" to try to figure it out

Paul

 

[roger]

I've been trying to find some info on what components
(regsvr32 type stuff) might be involved, but I'm having
no luck in a search engine. I don't know how to reset
the sound system part that connects to the driver.

As far as I know, your Pavilion 700 uses an Asus OEM motherboard
A7M266-M. It is not similar to A7M266 Retail motherboard (for which
the Asus site has driver support). The motherboard is Bermuda/BoraBora,
implying perhaps more than one model of the same thing. It uses an
AMD761 Northbridge and a VIA 686B Southbridge (split-brand chipset).
Since sound is off the Southbridge, we pretend it's a "VIA Chipset".

(23 page pseudo-manual for your motherboard - more than Asus would
normally prepare for end-user consumption, but still inadequate)

http://www.elhvb.com/mboards/OEM/HP/manual/bermuda_manual.pdf

The way AC'97 works, is a driver combines support for the AC'97
Codec details (3 or 6 jack config, PNP 12 bit number for CODEC
declaration), as well as for the Southbridge end. So something
on the Southbridge end is also custom, and the driver sets it up.

<---- driver ---->
Southbridge ---- RealTek --- 3 jacks, to amplified speakers
AC'97

I downloaded this file (since you suggested it, and I couldn't
find it in the Pavilion 700 driver section), and it does use
a naming convention consistent with multiple Southbridge support.
So it probably has VIA support for the Southbridge end of the link.

ftp://ftp.compaq.com/pub/softpaq/sp35001-35500/sp35461.exe

First, I stumbled on a 64 bit INF file, for a later OS.

[SourceDisksFiles]
ALCWDM64.SYS=222
SOUNDMAN.EXE=222
ALSNDMGR.CPL=222
ALSNDMGR.WAV=222
RTLCPL.EXE=222
RtlCPAPI.dll=222
CPLUtl64.exe=222
Alcrmv64.exe=222

[DestinationDirs]
AC97AUD.CopyList=10, system32\drivers

[Realtek.NTamd64]
%ALCVIA.Desc%=AC97VIA, PCI\VEN_1106&DEV_3058&CC_0401

As far as I can figure out, VEN 1106 is VIA, and
DEV 3058 is a common device identifier for VIA Sound
in old Southbridges. Since there is a match in the file,
it does appear that the INF is intended for this class
of hardware.

But I can't offer any other insights as to what is
supposed to happen. As I can't find any info on what
OS sound files connect to these things, and might benefit
from some sort of repair.

I do know from personal experience, all it takes is installing
a second sound card, a card with a bad driver design, to
shoot the sound in the first device in the foot. I had a driver
that abused a registry entry (by removing it), which prevented
the other device from working. And even if that bad driver was
removed, the registry entry wasn't coming back. And the first
driver did not have the common sense to create a new registry
entry. I think the registry entry was created by the OS. After
I made a registry entry for it manually, it started working
again. So I do know of that one example.

And a "driver cleaner" wouldn't have helped in a case like that.

A "Hail Mary" approach to fixing it, would be "sfc /scannow",
which is supposed to check and replace system files. But since
that never seems to get mentioned in a resolution to this problem,
I'm guessing it doesn't help.

I tried an ident on ALCWDM64.SYS, and it says it is for a
64 bit OS, and is a .NET assembly. So that tells me the
first INF file I tried, is for a 64 bit OS. Pretty strange
to offer such a driver package, for your vintage of computer.
There's probably one guy out there in the world, using
that combination of hardware and OS

The install folder is chock full of .inf files, and another
one of interest might be alcxau.inf

[SourceDisksFiles]
ALCXWDM.SYS=222
SOUNDMAN.EXE=222
ALSNDMGR.CPL=222
ALSNDMGR.WAV=222
RTLCPL.EXE=222
RtlCPAPI.dll=222
Alcrmv.exe=222

[DestinationDirs]
AC97AUD.CopyList=10,system32\drivers

So maybe that's what it would copy on your 32 bit system.

When I check ALCXWDM.SYS, it says it is for a 32 bit OS and is
not a .NET assembly. It's a plain executable. And that's more
consistent with older OSes. As is the accompanying ALCXWDM.cat
file with the security information.

You can look in the setupapi.log file, to see an entry around
the time the sound driver was installed.

When an INF file is used for installation, a copy is
put in the INF folder in the system folder. But, the idiots
rename the file to "OEM23.INF", as a means of preventing
name collisions (OEMxx). If the INF file contains a reference to
its own name, you can then see if the INF made it to the
INF folder. It's just an indicator that the driver installation
attempt got part way along. Of course, in the Device Manager,
you can also use the tab that shows the driver files, to
get some idea whether they got installed or not.

I don't have any concrete advice to go on now - I would
be "picking over the scraps" to try to figure it out

Paul

Thanks for all the research. I luckily found a PCI sound card, stuck
it in, and found a driver for it in DriverAgent, which I installed.

I have sound now.

Thanks again

Big Fred