deomsh

Still Mapped to 0xF0020000, but read is no longer 0xBDF7 but seems to be normal (to me) after forced install of ACPI and Q233017. It's all in the latest log's.

I had a long conversation with Google AI on this, could possibly be noise in combination with timing/ chipset/ WIN98FE issues. The probabilities in the statistics of the LLM predicted things will become better if I used ACPI on WIN98FE. After a longer process this was really the case for Wave. Only MIDI is not working anymore after Disabling/ Enabling hda.sys. Interesting are the Read-outs of WPCREDIT ('Idea' from Google AI). Some comments are above my level, maybe you can use it. I also tried 'Low' DMA (set to max 16MB), but no difference. More clear for me now. This would be VERY nice, in the past I tried VDMSound with Watler's HDA2.DLL, but Prince of Persia 1 never played me Midi. Not from your driver, or do have you plans to rename to hda2.dll? This was an inactive registry entry mentioned in DxDiag report: 20 43 61 72 64 20 6E 61 6D 65 3A 20 B0 03 0D 0A 20 20 20 20 44 72 69 76 65 72 3A 20 48 44 41 32 2E 64 6C 6C 0D 0A 0D 0A Card name: ° Driver: HDA2.dll I removed the inactive entry before current tests. WIN98FE_ACPI_DX7.0_DUT_WDMHDA_021.zip Google AI on STATESTS and ACPI with WDMHDA.021 on WIN98FE.ZIP BTW conversation is mainly in Dutch, I asked my AI-Agent to translate to American English. Dutch readers can (try to) read both versions. If someone cannot read md-files, just use Total Commander (No-nag-shareware) with the md-Lister Plugin. Note on 'Google AI': still now and then hallucinating, but if asked if 'something' is 'true' or so, the LLM is correcting earlier statements. Seems things are becoming a little bit better.

Without Audio driver: no error if running DxDiag (empty log). I tested with DirectX 8.0 and DirectX 8.1 both. Only difference found: DirectX 8.0 gives no blue screen, general HResult error only. No problems with Playback or Volume noticed. I found no special WDM-related updates in case of Windows 98FE. The two you mentioned before won't install on Windows 98FE. WIN98FE_Wdmhda.021_DX5.1_DX8.0a_DX8.1a.zip Edit: after initial problems I succeeded to install DirectX 7.0a on Windows 98FE. Everything is, or seems to be fine! BTW DxDiag_WDMHDA.txt doesn't log tests as OK, but ALL tests on both DirectSound and DirectMusic where good! However, no Kernel mode mentioned with DirectMusic? WIN98FE_WDMHDA.021_DX7.0a.zip

As such Volume Control initiliazed without problems during install and worked for me (WinPlay3 has no volume slider). Good idea, I will try to test. But to me it seems DirectX related, not there in the N68 log's with the original DirectX 5 on that board (as far as I can see). I will try to install higher DirectX versions one by one on the N68 installation, to see if there is a version-relation. Or is your driver not supposed to support Windows 98 FE? In that case my testing makes no sense. Just thought it could be of some use to you. Personally I was interested to see if your Headphone polling was working with HDAWDM.021

I tested v021 on my three boards. All Windows 98 First Edition (I am currently working on Windows 98 FE for other reasons). On ACER I can see switching my Headphones-jack from Back to Front is logged (see the log of playing mp3 with WINPLAY3). On two boards DirectX 9.0c was installed, seems to have issues, but I am not sure currently if I must use a lower version on Windows 98 FE. BTW on all three boards resetting hda.sys with Device Manager was not possible: Yellow Exclamation Mark. I logged those trials too (except on N68). Wdmhda.021_WIN98FE_N68&VT1705_SB600&ALC662_C200&ALC662.zip

Interesting, noted. I looked into the thread of @Dave-H but two times no issue in case of ALC272 ( @Danielx and @isolar ) . At least not in case of HDA2.DLL. Not fully sure if Verbinterface=$1 in both cases.

A new version of Watler's Win3x HDA-driver already: HDADRV9Q Download from: https://watlersfiles.netlify.app/ New: software volume; possible to set volumewidgetmax in HDACFG.INI, section Volume (default is $007F007F); four HDA-controllers added with auto-setting of pcipatchB; pcipatchB should be supported in HDAICOUT.HDA too; Export of functions sglinf, setbvalue and strlog (API).

Something strange with your link: gives on Firefox 'https://github.com/andrew-hoffman/WDM' - so a (nice) 404. I copied the link with context-menu and pasted here to show. Not a big deal, because the shown 'text' is correct.

Thanks, now I understand on how you are using the phrase "polling". BTW my boards Front Panel is not connected, I always use the green connection at the back.

Congratulations, your WDMHDA v21.a is working now on my N68-board with codec VT1705. Also Master Volume is working. I made two set's of log's, one without Jack inserted (Fallback Playback-path is okay) and one with Jack inserted. I can not find a meaningfull difference in the log's in this respect. Is this logged somewhere? WDMHDA.21a.N68_VT1705.WIN982.zip BTW I added a log from a tool Isolar is working on currently, so you can see the Jack is really inserted in PIN-widget 1Ch.

Tested on Windows 98 SE (DirectX 9.0c), no difference in performance, everything as reported earlier. To me the two logs produced seems to be almost equal as with version WDMHDA.020. WDMHDA.20a.N68_VT1705.zip

As said, I am not a programmer - sorry my AI-agent has been wasting your time. He also said he could rewrite your code, I had 'only' to do the compilation myself. With my earlier experiences with AI modifying existing bootcode fresh in mind, I thought I would make you no competition But my N68/VT1705 is always ready for testing.

Was just adding search machine-info while you posted, see above. Same phrase: site:msfn.org 2026

Maybe I was too not looking good enough (my eyes are already aging), but I checked again. It's in the title only. Same on Edge (on my Smartphone too - Edge only there): BTW I used Brave (brave.com) with Private Search and inside Firefox/ Edge, so not their browser.

I do understand THAT already. To be sure I made myself clear: on Brave only the two mentioned gave Thai results (without filtering on dates). This I do NOT understand (lack of skills ).