Native (WDM) HD Audio driver for Windows 98se/Me

[Drew Hoffman]

Thank you for testing. That is certainly strange behavior, the only way I think that would be able to work is if my driver is loading first, sets up communication to the codecs, configures the codec at address 0 to start receiving from stream 1, then is unloaded. Then the Watler's driver loads later, sets up the controller a second time, doesn't send any messages to codec 0 and just starts streaming audio to stream 1 which happens to go to the right place. 

Can you tell me what chipset / PCH that netbook is using as well as the PID and VID of the HDA controller ? It's becoming clear that I'm missing a lot of newer Intel chipsets that should have the nosnoop flag set and I should probably send a pull request to Sbemul and VSBHDA once I know everything that's missing. I haven't been able to do much coding lately as I have been ill and screens are still giving me headaches.   

[isolar]

Thanks Drew, more than happy to provide any info that can help.

What you suggest is happening seems logical here, i'm not 100% sure how the HDA.SYS driver functions and what verbs it sends on enumeration (could you please advise?), but definitely when I rename HDA.SYS to HDA.BAK then sound stops. Renaming back to HDA.SYS - sound returns again. Deomsh has advised possibly your driver enumerates GPIO pins which I am not touching in the HDAICOUT file.. yet.. but currently investigating. And/Or nosnoop bit set on audio controller.. also under investigation but this is brand new info for me . The main mystery is how HDACfg.ini maps codec $2 instead of $0 (Codec $2 is HDMI audio out.. so Watler's should be doing nothing to get sound possible here).

Chipset I am struggling to identify due to the nature of this motherboard (without installing Win8+ that has drivers to identify).. it is a Lenovo S20-30 with Lenovo Edonis 2A1 motherboard, Baytrail-M CPU Intel Celeron N2840 and Valleyview integrated graphics. The audio controller is Intel 8086 0F04. Codec is Realtek HD Audio 10EC 0280.

For chipset if you know any hardware identifier progs that work on win98SE and can identify newer chipsets then I will be happy to try. Currently HWInfo32 shows 'unknown' chipset.

Wishing you a speedy recovery and hope to hear from you soon!