Leaderboard

Hi Isolar, long time no see. About your question: there are two possibilities, or their combination. 1) Your HD Audio controler needs a nosnoop bit set, you can check with WPCREdit. 2) The parser of WDMHDA identified some verbs you didn't use in your HDAICOUT.HDA. Possible candidates: 'opening' inputs (mixer?), EAPD or GPIO. Search in this thread for verbs.

Hi Drew, With initial help from Deomsh over at the 'Audio driver for Realtek HD Audio' thread, I have been using Watler's driver to get HD Audio working on Windows 98 laptops for a while, and came across one that I had some trouble with. Currently I have managed to get SoundMax AD1981HD working on a HP6710b laptop, IDT 92HD75B3X5 working on a HP 6550b laptop, and Realtek ALC272 working on a Lenovo S10-3 laptop with Watler's. Attempting a Lenovo S20-30 proved difficult as the codec was identified as 10EC 0280 of which I could not locate a datasheet for. I used HDAICIN responses to identify all NID's/CAPS and found the connection path to be the same as ALC 272 (and most other Realtek codecs from the looks of things) with $01 = AFG, $02 = DAC, $0C = Audio Out connected to NID $14, and NID $14 = Line Out. I managed to create a working HDAICOUT.HDA file but no sound. I had stumbled across your driver (great work I can see this being invaluable in the future!) and trialed v16, but sadly no sound to start with. So I re-installed Watler's to try some other options. What I notice is that your driver, although removed from device manager and 're-installed' to Watler's, is maybe still using the registry entries, so when I go to multimedia settings I can see the WDM driver still listed as an option, along with the midi/volume control, however Watler's is selected and installed. The HDA.SYS driver file still exists in windows\system32. The veeeery interesting thing here is that this combination has helped me to get sound working (although buggy) on the S20-30 laptop! I have no idea how or why this works but hoping you could shed some light on it, or I can provide you some more info that may be able to help you with development? I did try to rename HDA.SYS to HDA.BAK and rebooted but got no sound at reboot which indicates to me that although Watler's driver is installed it is still somehow using HDA.SYS in combination with HDA2.DLL to route the sound to the speaker - I am good with verbs but not with codec initialization, CORB, RIRB etc. To note: HDAcfg.ini from Watler's driver shows codec index $2 is active, which is incorrect (this is the HDMI audio out, whereas the 10EC 0280 codec is on index $0) so how I am getting any sound at all is a mystery.. At boot I get a high pitched squeal through the speakers until the initial windows start sound finishes, then I can go to sounds and play the sound samples. DirectX 9C is installed and runs the tests all okay. Happy to assist here with any information I can provide to get you further and help me understand why sound works with this combination, just let me know if anything is required. All the best and I will be following your progress. Cheers!

I'm setting the PCI config flags based on vendor and device ID, and 8d20 is currently in the list while 10F0 isn't. The white list from mpxplay probably wasn't updated for 10 years. Need to find the most up to date version of that list of device IDs. Snd-HDA-Intel doesn't seem to use that approach anymore. Alternatively I should set nosnoop on all unknown Intel device IDs and only enumerate the devices that don't need it (ICH 8 and 9 and what else?), and also add a registry config option to force it on or off. Unlike Microsoft I only need the driver to function on x86, if someone is dedicated enough to get it working for Win2k on Alpha I'm not really sure what hardware exists to use it on. Video cards with HDMI audio that won't have drivers anyway and maybe one Terratec pro audio card? I did manage to find an official description of the caching policies of the UAA driver: https://learn.microsoft.com/en-us/windows-hardware/drivers/audio/data-copying-and-caching-policy Just don't know a good way to get the audio buffer to be MmWriteCombined on Win98 while still using PortCls WaveCyclic. Could add an extra bounce buffer and do a third buffer copy? Could also discard the whole framework of PortCls and write a Stream driver instead which would save a buffer copy anyway, or make a VxD driver, or fix Watlers?

I agree as a general off-topic observation that while you do, of course, need to have a general awareness of security and privacy issues when working online, there's really no need to be paranoid about it.