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

[Drew Hoffman]

Fixed the page fault crash and the hang on Atom systems.

https://github.com/andrew-hoffman/WDMHDA/releases/tag/Alpha-014-1

The problem I'm having installing Win98se without QuickInstall on newer hardware is not the resources crash that SweetLow mentioned and running JHRobotics' Patcher9x does not fix it. I think it is an ACPI related issue with Configmg as installing with setup /p I will allow me to at least boot in to the OS after setup, but it seems to do so in a fallback mode where no PCI devices are detected or enumerated and that is not very useful for testing a PCI device driver. 

I get somewhat better results copying an image of an existing install, after including the new ICH8+ machine.inf files and NUSB. As long as the machine has PS/2 ports anyway. If it's a laptop I end up with the Catch-22 of needing to install the USB drivers and being unable to click Next on the dialog box. 

Edited Tuesday at 06:12 AM by Drew Hoffman

[LoneCrusader]

8 hours ago, Drew Hoffman said:

...installing with setup /p I will allow me to at least boot in to the OS after setup, but it seems to do so in a fallback mode where no PCI devices are detected or enumerated and that is not very useful for testing a PCI device driver.

Modern hardware, expecting ACPI compatible operating systems, lacks whatever older "trigger" that is required to trigger the detection of the PCI bus device and subsequent enumeration. After installation and booting to the desktop, simply manually install a "PCI bus" device in the Device Manager and it will trigger the detection of the other connected devices.

8 hours ago, Drew Hoffman said:

...As long as the machine has PS/2 ports anyway. If it's a laptop I end up with the Catch-22 of needing to install the USB drivers and being unable to click Next on the dialog box. 

Sometimes it's possible to overload the keystroke buffer with ENTER presses before PS2 keyboard emulation is lost when the OS USB drivers take over during boot. This may or may not get you through all the dialogs, depending on whether the default options will be successful. May have to do this more than once to clear all of them.

[SweetLow]

13 hours ago, Drew Hoffman said:

Fixed the page fault crash and the hang on Atom systems.

The same short loops.

13 hours ago, Drew Hoffman said:

If it's a laptop I end up with the Catch-22 of needing to install the USB drivers and being unable to click Next on the dialog box. 

Two possible solutions for 98SE:

1. Generic - using the same registry key that Setup uses for unattended hardware installation.

2. USB specific - SilentInstall feature of USBHUB.SYS from 98SE and right version of USBHUB20.SYS

P.S. Laptops usually have PS/2 keyboard. Such problem more typical for legacy free PCs.

Edited Tuesday at 08:27 AM by SweetLow

[Drew Hoffman]

The Dell Mini 9 seems to have a USB keyboard and track pad, the Acer Aspire N450 netbook has a PS/2 Keyboard but USB Track pad, the Latitude E6400 has both ps/2 keyboard and track pad which is good since I can't get the USB controller drivers to install on that. Also my driver is still not producing any sound from IDT codecs it seems. That's all the old laptops with HDA I had immediately available.

On another topic, does anyone have tips on getting a driver to build without the official Microsoft DDK? I probably shouldn't be redistributing the full sample code and headers, even if Microsoft themselves have uploaded newer DDKs to Github under more permissive licenses. 

[jumper]

If it's a full driver, identify the subset of headers and link libraries needed. Include them directly into your source package. Once working, replace them with open-source versions from Wine or ReactOS. (Check for availability first!)

If it's a mini-driver, the framework might not be available as open-source.

 

[Drew Hoffman]

My driver is is a mini-driver using the WaveCyclic miniport.

ReactOS already includes Dogbert1's CMI8738 driver which works on the same miniport, though they have modified how it builds (compared to the version in the Google Code Archive) to remove the dependency on the Microsoft DDK. I would bet that CMI driver was also based heavily on DDK sample code just because the file and function layout is very similar to the two examples but I can't prove that and wouldn't want to accuse anyone of anything.