Dave-H

Sorry for any confusion, but the slider was not moving in the Sound Recorder. The play button greyed out as expected when pressed, and a static waveform then appeared in the window with some files, but the slider did not move across. It could be manually dragged and the waveform then displayed, but nothing else. Now I have made those changes, the slider does move across when I play a file, and shows the playing waveform, but still no actual sound. "HDA Sound" has returned to the playback settings option. Here's what "Audio for HDA Sound 2017" now shows.

Oops, I spoke too soon! I've just booted into Windows 98 again, without having changed anything, and the "HDA Sound" option has gone again! As you can see, there is an option there, but it is blank.

@ABCDEFG Thanks, I do seem to remember trying all that when the conflicts first appeared, and I didn't have any luck resolving them. As they didn't seem to be causing any problems, I didn't pursue it. If they are now causing issues I will have another go though! @deomsh I tried just rebooting, and yes the "HDA Sound" option in the Multimedia Properties does seem to have stuck. However the system sounds option has its test play button greyed out again. The Sound Recorder doesn't seem to want to play some WAV files at all, but for others it just produces a stationary waveform in its display, and playing produces nothing.

OK, I tried that, and was rewarded with the Control Panel "Sounds" applet actually coming to life, in that the test facilities weren't all greyed out, and I could push the test play button on all the system sounds. Sadly, although they all went through the motions of playing, there still wasn't a peep from the loudspeakers! My HDARUN.EXE window looked exactly like your grab, with the same numbers in the windows. What actually is the writing under the windows? Mine looked exactly the same, with the windows covering the lettering. Should I put the "Mytimer" setting in HDACFG.INI back to as it was before now, or leave it at 0? There is still absolutely no sound from the speakers at all on Windows 98, even when I boot up or shut down. There isn't even the quietest of clicks or pops. I would have thought that there would be something at least as the driver was being loaded, but nothing.

OK, not XP, but POSReady 2009 still going strong in my local Marks and Spencer store today, obviously oblivious to its imminent demise!

Thanks for sticking with this @deomsh, I really appreciate it! This is the Device Manager details of the Audio Driver, which shows no conflicts. As you can see there are other conflicts in the system, which have always been there, both on the "Direct memory access controller" and the "System timer". I have never been able to resolve these conflicts, I assume they're just because I'm using a motherboard that just isn't designed to work with Windows 98. They have never seemed to cause any problems, perhaps until now! This is the "Direct memory access controller" problem - And this is the "System timer" problem - They don't seem to be conflicting with each other, but with "Motherboard resources". Could this have any bearing on why the sound still isn't working? If so, I fear that it won't be resolvable.

Thanks, I tried changing both those options in HDACFG.INI, but still not a peep of sound. I guess the driver just isn't talking to the hardware. There are no audio related entries in the BIOS.

Strange that the extension didn't work for you, but as you say you don't actually need it anyway unless you want to switch between locales regularly.

Sorry for the delay, I've been busy today! The contents of my HDACFG.INI file are here - [ALLHDA] $00D8=$269A8086 $0101=$0BE910DE [HDA] TSR=TSR Found PCI_VID=$8086 PCI_DID=$269A [BUSMASTER] myPCIHI=$0012 myPCILO=$1000 myPCI=$00121000 aPCIHI=$0011 aPCILO=$1000 aPCI=$00111000 [HDA_269A8086,948015D9] cardmemregistersLO=$0000 cardmemregistersHI=$DE80 Mytimer=1 Verbinterface=$1 wait1=$100 wait2=$100 pcipatchB=$0000 PCI_BUS=$00 PCI_DEVICE=$1B PCI_FUNCTION=$0 GCAP=$4401 VMIN=$00 VMAJ=$01 GCTL=$0001 CODEC BITMAP=00000100 CODEC Index=$2 CODEC_VID=$10EC CODEC_DID=$0883 CODEC_REV=$100002 CODEC_NODEINFO=$010001 CODEC_AFG_GPIO_CAP=$40000002 CODEC_AFG_SUBSYSTEM_ID=$15D99480 CODEC_AFG_PM_SUPPORT=$0F CODEC_AFG_PCM_DEFINITION=$E0560 CODEC_AFG_F000B=$01 SleepingWidget=$02 VolumeWidget=$14 OutputWidget=$02 [Volume] PCM=$FFFFFFFF I've attached the memory file you asked for too. I hope this gives some clue as to what's going on! Cheers, Dave. HDADAVEH.TXT

Understood. The driver is listed. The small window is what pops up when you select its settings. After dismissing that, it then appears as an option as a playback device. Unfortunately, selecting it doesn't work, there is still no sound, and on a reboot it disappears as an option again, and as before there is only one option in the dropdown to select playback devices, and it's blank. The device ID is PCI\VEN_8086&DEV_269A&SUBSYS_948015D9&REV_09.

Tried changing the system.ini entry, but no difference I'm afraid. Should there be an entry for this in the Device Manager "Sound, video and game controllers" section?

HDA2.DLL is in my C:\Windows\System folder. (In fact my Windows folder is C:\WIN-98, but that shouldn't make any difference.) HDA2.DLL is listed as a loaded module in msinfo. These are the relevant sections from my system.ini - [386Enh] device=*COMBUFF device=TURBOVCD.VXD device=*dynapage device=*vpd device=*int13 device=*enable device=convmem.vxd device=c:\programf\afterdar\adw30.386 ebios=*ebios woafont=app850.fon keyboard=*vkd display=*vdd,*vflatd mouse=*vmouse,msmouse.vxd device=dva.386 MinSPs=16 ConservativeSwapfileUsage=1 Paging=on PagingDrive=C: ;Entry MaxPhysPage=40000 limits memory use to 1024MB EMMExclude=C000-CFFF [Drivers] wavemapper=*.drv MSACM.imaadpcm=*.acm MSACM.msadpcm=*.acm Adwrap=c:\programf\afterdar\adwrap.drv MSVideo.VfWWDM=vfwwdm.drv MSACM.lhcodec=lhcodec.acm Voice=C:\UTILITIE\EXTERNAL\BITWARE\is101.drv VIDC.YV12=ATIYUV12.DLL VIDC.VCR1=ATIVCR1.DLL VIDC.VYUY=ATIVYUY.DLL VIDC.YVU9=IYVU9.DLL wave=mmsystem.dll midi=mmsystem.dll wavehda=hda2.dll As you can see, I'm using the ConservativeSwapfileUsage=1 option. I have never needed in recent years to use a swapfile on Windows 98, as it can access over 3GB of RAM! I did try changing it to ConservativeSwapfileUsage=0, and rebooting, but no difference. Cheers, Dave.

@deomsh There is a "High Definition Audio Controller" entry in the "System Devices" section of Device Manager, but nothing in the "Sound, video and game controllers" section. There is no "Multimedia Devices" section, is "Sound, video and game controllers" what you meant? There is definitely no sound at all coming from the speakers during startup. I did reboot after copying Hdaicout.hda to the C:\Windows folder (not C:\Windows\System?) I'm getting a message from autoexec.bat on startup which say "TSR loaded", I assume this means it has correctly loaded. @Destro Yes, that is my fallback intention if the Windows 3.1 driver won't work for the onboard hardware. I only need sound at a basic level as I'm not a gamer and I don't use the PC to watch movies. I haven't used a Soundblaster card since my first Windows 3.1 PC back in 1993! Are there any Windows 10 64 bit drivers for them though?

@deomsh I've followed your instructions, and everything seemed to go OK, with no crashes or error messages. I now have an entry called "High Definition Audio Controller" in my Device Manager "System Devices" section. It says it's working but has no driver files loaded, I assume that's correct. The relevant entries seem to be there in autoexec.bat and system.ini. No sound so far though. I copied the Hdaicout.hda file you linked to to my Windows folder, but no difference. Does this mean that the contents of that file need modifying somehow?

Wow, thank you so much! I never thought for a moment that the answer to this might be a driver designed for Windows 3.1! I will try this out later on and let you know how it goes, I'm working in Windows 10 at the moment. Cheers, Dave.

Not yet, but I have downloaded the necessary files. I'll have a go with them later this evening, I'm working in Windows 10 at the moment! I'll let you know how it goes, but I'm very optimistic that it will be fine. Having the interface in US English isn't the end of the world for me of course, but if it's possible to get 52.9.1 to be in British English that will be really good, even if it needs another extension installed to do it. EDIT: I've now installed 52.9.1 with the language pack and the locale switcher. All seems to be working fine!

Thanks guys! I guess this is just too big an ask, even for the geniuses here. I could just do without sound on Windows 98, but an alternative might be just to fit a cheap PCI plugin sound card, and use that for Windows 98. I can free a slot for it. I would want to connect the speakers just to that to avoid having to switch the source when I change operating systems (I do this with my dual graphics cards, using the input switching on a multi-input monitor, but I'd rather not have to do this with the speakers as well!) It would be great if I could use the PCI plugin card just for the actual listening audio, but use the HD onboard hardware for the microphone and line input on Windows XP and Windows 10. Would that be possible? It works OK with the graphics cards, Windows XP is the only OS that both cards have drivers for, and they are both installed and seem to coexist (one card is ATI, the other Nvidia needless to say!) I would hope to find a sound card that has drivers for all three operating systems. There are drivers for all three for the old motherboard's AC'97 sound system, so if I could find a card based on that I would have thought it would do the job. I've had a look, and I found a couple of possibles, but none of them seemed to have Windows 10 drivers, which also have to be 64 bit! Any advice gratefully received. Cheers, Dave.

I just had to change my motherboard, as the old one developed a fault. It was a Supermicro X7DAL-E server board. I was very lucky to find someone selling two of them which turned out to be unused, but they are X7DAL-E+ boards. The only major difference between the X7DAL-E and the X7DAL-E+ is that the former has a Realtek AC'97 onboard sound system, and the latter has a Realtek ALC883 HD onboard sound system. I've got one of the new boards up and running fine, and I found audio drivers for Windows 10 and Windows XP, but I'm having trouble finding a driver for Windows 98SE. There are many listed online which claim to work on Windows 98, but they don't, the installer just says it's not compatible with the OS. Is there any answer or workaround for this? I only want basic sound on Windows 98, nothing fancy. BTW I have absolutely no idea why Supermicro thought that is was necessary to put a 5.1 HD audio system on a server board! Thanks, Dave.

You'll feel at home where I live, in Ealing in West London, there's a huge Polish community here!

It's not even available in different versions of English. US English only.

I assume you've tried a clean startup using the system configuration editor? Is the problem still there if you do a clean startup?

I got a free "upgrade" from Windows 8.1 after the original offer ended before I decided to bite the bullet, by saying I needed Windows 10 for its accessibility features. That was a limited time offer supposedly though, so whether you can still do that I don't know. There was certainly no check on whether you genuinely needed it for that reason or not!

I wonder if MS will restart the free (and perhaps automatic) "upgrade" to Windows 10 "offer" for Windows 7 users when it approaches EOS? If that extends to Windows 8.1 as well, I'll have to be on my guard again on my netbook, as any update to Windows 10 will hose it as there are no compatible graphics drivers for it!

@VistaLover I tried that UA string too, and I got past the first incompatibility error message, but then got a WebGL error message instead. Switching over to my other graphics card, which is much better than the ancient one I normally use on XP, made that error apparently go away, but I've now just got a static picture which appears to have no embedded links, so I'm not sure what you're supposed to do with it to try and go any further.

Thanks, that's very interesting and good to know, but I think I'll stick with the extension, I can see more quickly and easily how that's set, and it doesn't seem to be causing any performance problems.