deomsh

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 ).

Personally I am happy with msfn. AND: it's still Sunday, maybe don't expect too much from the people who keep msfn running. I did some new tests with following string (NO quotes): site:msfn.org 2026 BOTH Google and Bing give the full Thai-connection. Images seems to be max 2 days old according to Bing (Google gives no images ??). Today this one is my favourite: It may be useful if members from other zones than North-West Europe check for themselves and report too (unsure if they should ask for a refund - isn't this a gift to help msfn staying alive? ). I checked Mojeek and Brave too. Only on Brave I could filter on specific date (very nice, better than the Big Two). After 23 march there are no results anymore on Brave. Both seem to give normal results, EXCEPT on Brave the following TWO (checked all six pages with search results): 1) msfn.org/board 2) msfn.org/board/index.php

I continued my conversation with Copilote, with following question: "In an earlier conversation today (on another browser) Copilot said Bing was still indexing msfn.org. Was this an error, or is it possible the AI-engine was so called 'hallucinating'?" The answer was interesting (at least to me, probably not to AstroSkipper ). Cited small part of Copilot's answer only: "The earlier answer you saw was not you imagining things — it was almost certainly a case of the AI giving an overconfident but incorrect statement. In other words: yes, that was a hallucination, and I can explain exactly why it happens in this specific situation. 🎯 Short, direct answer Bing used to index MSFN normally, but it no longer indexes new MSFN content reliably. If another Copilot instance told you “Bing is still indexing MSFN,” that was incorrect — a classic AI hallucination caused by outdated assumptions about how search engines behave. (......) Bing is still returning MSFN pages, but it is not indexing new pages beyond ~2025. (....)."

Because bing.com seems to behave differently from Google, I couldn't resist to have a small a conversation with Copilot on bing.com. See the attachment. Copilot on Google-indexing changes.md