Dave-H

I'm not taking about the old XP Windows Defender, but the one that comes with Windows 10. A very different animal, but it may still share the same definition files with MSE.

Silly question I'm sure, but the latest definition for Windows Defender on Windows 10 is 1.293.45.0. I presume that can't be used in MSE? I only very recently started using MSE on the XP side of my netbook because its original AV stopped supporting the last XP compatible version of its program. I don't know much at all about how its updating system works, but surely it's not just a matter of copying files across to make MSE think it's got the latest version?

This is what I get if I try to access Sourceforge - Github access is OK, although the pages look a bit of a mess!

Here you are. HDAICIN.TXT HDALOG.TXT

I tried the new file, and it seems to work fine. Strangely, the quality on some of the system sounds seems a bit rough now, but I don't know if that's worse with the new file or not. Playing music tracks, both MP3 and WAV, sounds fine though. I'll have to try and do a comparison. I'm definitely not using HDARUN, which doesn't sound like a good idea from what you were saying! EDIT: I tried reverting to the older hdaicout.hda, and the sound quality is exactly the same. It's mainly the system sounds like the ringing tones and chimes which sound rough. One thing I have noticed is that with the old file there are two "pops" from the speakers as the desktop loads, with the new one there's only one!

I just downloaded this and ran it, and although apparently nothing happened visually, it did work. I thought those files didn't work on XP any more? Anyway, I guess that's the last one. Microsoft Update offered a definition update, but always failed with error 0x800700F, which is something to do with failing a licence check. MSE itself goes through the motions and then fails with an unspecified "network problem". The definition being offered by MS Update was 1.293.20.0, which is later than the one I just installed, which is 1.291.2489.0. I don't know which one is actually current (there seems to be a big gap between them!) but MSE seems happy at the moment that it's up to date.

Thanks. I don't think I've got HDARUN.EXE actually running now. Mytimer is set to "1" in hdacfg.ini. Is it actually what the driver readme files refer to as "activate.exe"? Was its name changed perhaps?

@deomsh Just a quick question. I'm making a zip file up containing all the necessary files for this in case I ever need to reinstall it again from scratch, with an installation instruction note. The documentation for the driver refers to a file called "activate.exe", which doesn't appear to exist. The file in the "Activate" folder is called "Hdarun.exe". Is that the same file? I'm not actually running it, I assume that it's not needed? Also, do I need the HDA2.MAP file, or is that also part of the source code?

@deomsh Of course Watler should have every credit for originally writing the driver, initially for Windows 3.1, but as far as I'm concerned your skill was in porting the Windows 3.1 driver to Windows 98, writing the INF file which made the installation easy to do. Also of course doing the necessary analysis and work to produce the Hdaicout.hda file that worked with my hardware! I wouldn't have even known where to start with any of that! There are so many brilliant and talented people here on this forum, I sometimes feel that I'm not worthy. However if my problems and their resolutions can help others in the future I'm delighted with that. As I mentioned earlier I had a similar problem getting a driver for my onboard Ethernet port to work on Windows 98, which resulted in a thread even longer than this one! That also used a driver designed for a much earlier operating system (DOS in that case, Windows 3.1 in this case) and it also proved that "where there's a will, there's a way", especially here on MSFN! Yet again, I salute you all!

Thanks again! The only reason I asked about the files in the folder with WAVEOUT.EXE was because I'm making up a zip installation package for this in case I ever have to install it again, and I wanted to make sure that I did have all the necessary files included.

@bearwindows Great to see you here again, you gave me a driver for an Nvidia graphics card some years ago which I had all but given up on getting to work with Windows 98! @ruthan Don't be worried, just try it!

Thanks, rather stupidly I hadn't realised that waveout.exe is a program for changing the volume, much more convenient than editing the ini file! Does it need any of the *.dpr, *.opt, *.res, *.dfm, or *.pas files that are in the installation folder with it? It seems to work fine without them. Also, what is the item marked with the arrow? Is it something to do with having multiple devices? I'm still slightly confused about the graphic that ABCDEFG posted. If I set Left : 65280, Right : 0 I get 0000FF00. If I set Left : 0, Right : 65280 I get FF000000. The graphic says the channel levels can go to FFFF, but FF00 seems to be the actual maximum, which is 65280 in decimal. Not a worry, but I'm puzzled!

Fair enough. Worth a try though if you can't get a driver that works for your onboard hardware and you need that PCI slot back!

Well KB4462223 certainly is, as it contains an XP-incompatible version of MSO.DLL. Not sure about KB4462177. According to its security bulletin, it only replaces graph.exe, a file that doesn't seem to exist on my system except in the MSOCache folder, which I think is just a store of Office update files. Maybe it's part of one of the Office components that I don't have installed?

@ruthan Have you considered using a USB LAN adapter? I don't know what the speed restrictions might be, but presumably you have a free USB port, and the adapters are fairly cheap. Might be worth considering if you can't get a driver to work.

KB4462223 is the only update that I still have to keep hidden. I assume that the others were superseded by it.

Strange, I just tried again changing VolumeWidget=$0C and it worked! I don't know what I did wrong the first time, but it seems to be OK now, and I can control the level. BTW is the above graphic posted by @ABCDEFG on April 2nd actually correct? My testing indicated that it's the first four characters that control the left volume, and the last four that control the right volume, which is actually more what I would expect. The Windows Media Player volume control works fine. It was actually rather good to remind myself that I can play MP4 HD videos on Windows 98 with it, thanks to K-Lite, and they look and sound great, even in full screen! There's a bit of a delay with a series of pops from the speakers before anything plays, but I guess that's normal. So, the only outstanding anomaly is that the "HDA Sound" entry doesn't "stick" in the "Multimedia" Control Panel applet. When it's not there, I can't use the test facility on the "Sounds" applet, the test play button is greyed out, although the sound is actually working. The way to get it back, which is still very hit or miss, is to go to the "Devices" tab on the Multimedia applet, open up the HD audio entry, click on settings, and click OK in the settings box. This usually, but not always, returns the HDA Sound entry in the playback devices, after closing the applet and reopening it. Very strange! Anyway, I now have sound on Windows 98 with HD Audio hardware, and for that I'm extremely grateful. Yet again this forum has proved that what was thought to be impossible, is in fact completely possible!

No, Sourceforge doesn't work with Opera 12.02 on Windows 98. It's fine with Opera 12.18 on Windows XP.

Is this the post you were referring to? I tried changing VolumeWidget=$14 to VolumeWidget=$0C, and there was no sound at all!

Thanks, I will try that later on. I did try changing PCM=$FFFFFFFF to PCM=$AAAAAAAA in the [volume] section of HDACFG.INI and it didn't seem to make any difference to the sound level. Do I need to change anything else as well?

Have a great Easter break, whatever you're doing!

I just tried with the new version of Hdaicout.hda, and - IT WORKS!! Thank you so much, I now have sound! It's a little bit distorted, but not badly so, and there is no control of course, but at last it's there. Presumably I can alter the volume by adding the appropriate entry in HDAcfg.ini. Here are the two files you asked for if you need to do more analysis. HDAICIN.TXT HDALOG.TXT The "HDA Sound" entry in the Multimedia control panel item is still sometimes missing, with a blank entry instead, but even when it's blank the sound still works. Thank you, thank you, thank you!!

Those two videos don't work for me as well, but they actually don't work in Opera 12.18 on Windows XP either! The HTML5 test sites say that the browser doesn't support H.264/MP4, which is strange because that's what I thought new videos were, and they work but older ones don't!

Have you got an example of an older video that won't work for you, so I can try it?

I do get the "snow" with the "no formats supported" message sometimes, but when I try another video it usually plays. Here is an example - How much of a "major achievement" that is I don't know!