At some point, I'll try dumping all the w10 infs and look at it properly.

Why? Because all the guids and ven/dev ids and the device/subsection reg quirks will be in there since 10 supported the entire era and it is certain that the guids won't overlap anything.

Your driver won't support the quirks, but at least knowing that x behaves differently might help when someone inevitably tries it.

For various reasons I am using PCI_CC\0403 as the only device ID in the inf, and then reading the PCI vendor and device ID from config space to apply controller specific quirks. This is because most of the controller quirks require reading & writing to config space anyway, so there's no point in storing it in the registry keys, and also there's no way for the PnP Manager to read a codec VID/PID at driver install time because the driver is monolithic and not split into controller & codec(s) on the HDA bus like the Universal Audio Architecture.

Maybe it's possible on 9x to create a bus from the controller driver and make codec drivers attach to that but R. Loew couldn't get that to work and I'm not as smart or experienced. In the future I should still move all of the codec state into its own class to allow for multiple codecs on 1 controller like with a laptop in a docking station. This would also allow using a config script like the Watler's driver instead of depending on the very basic node parser.

2k used the same drivers, so I assume there's a way.
Then again, the 9x nvidia drivers are one giant sys vs several dlls on the nt branch.

2k also uses WDM drivers, true, but the HD Audio Bus architecture was backported from XP in KB888111 requiring a new sysaudio.sys and portcls.sys which R Loew could never get to work on 98se even with his WDMEX patching up the missing imports. The Toaster driver sample from the Windows 2000 DDK (the example for creating a bus) does not work in 98 either and I don't know why. Believe me if I could have backported the existing driver that would have been a Lot simpler.

Video driver architecture is completely different between 9x and 2k, and 9x drivers still need to have a 16 bit portion that handles GDI. But now anyone who wants to try to implement that can use all the code from JHRobotics' SoftGPU project.

I'm pretty ignorant, but as I understand from what you said, it's not possible to separate the hda bus from the codec for some reason.

Bus as in the literal bus like pci and isa are a bus? Or some logical bus?

HDAUDBUS.inf
Class = System
ClassGuid = {4D36E97D-E325-11CE-BFC1-08002BE10318}
%HDAudio.DeviceDesc% = HDAudio_Device, PCI\CC_0403
%HDAudio.DeviceDesc% = HDAudio_Device, ACPI\CLS_0004&SUBCLS_0003

HDAUDIO.INF
Class=MEDIA
ClassGuid={4d36e96c-e325-11ce-bfc1-08002be10318}

No actual devices in here. Seems like the inf equivalent of a header file.

HDAUDSS.INF
Class=MEDIA
ClassGuid={4d36e96c-e325-11ce-bfc1-08002be10318} Same as above.
Bunch of dev/ven, but not as many as I'd expect

I don't think the few GUIDs in your inf matter - they're all repeated in multiple infs in win11 so I think they're for a group thing.

One interesting thing - which seems to line up with the Watler's driver is the override verbs.

eg:
[HdAudModel_DellPrecision380.HdAudInit]
HKR,PinConfigOverrideVerbs,NumVerbs, 0x1,20,00,00,00
HKR,PinConfigOverrideVerbs,0000, 0x1,f0,1c,87,00
HKR,PinConfigOverrideVerbs,0001, 0x1,00,1d,87,00
HKR,PinConfigOverrideVerbs,0002, 0x1,00,1e,87,00
HKR,PinConfigOverrideVerbs,0003, 0x1,40,1f,87,00

Presumably that correlates to his - and therefore might be reversable for people to configure his better.

Maybe this new driver deserves its own topic?
WDM drivers have nothing to do with Windows 3.1x which this topic is about...

Read the last line.

Possibly discovered something useful for this driver.

That said, I agree

I made a new topic here for my windows 98 driver.

To answer the other question, yes HD Audio is a bus, the controller drives a low speed serial bus which connects to either audio ADC/DAC or modem codec chips. AC97 was also a bus like this which could have multiple devices (often software modems installed in the AMR or CNR slot) and this could be problematic because the controller and codec both had vendor specific Quirks and extensions and this all had to be covered by one driver for all combinations. It's not even possible for Plug & Play to see the ID of the codec(s) with no driver loaded. This meant that Realtek and Analog Devices and Sigmatel and others made their own driver packages with special features and you often had to try several to get one working. Since everything was closed source there was no easy way to tell without trying to use it either.

For HD Audio and the Windows Universal Audio Architecture, the functionality was split so separate drivers could handle the controller and bus, and each codec. Windows could then support the controller and let vendor specific drivers handle only the codec and Plug&Play would be able to find the right ones. But this architecture was never backported to 9x since it was already 2004. For Winmodems this was also pretty pointless since again it was already 2004 and there was never a separate slot for HD Audio modems like for AMR/CNR. They were occasionally used on laptops I think.

I had no luck trying to use the driver in my hardware.

I followed the steps from here: Re: HDA Audio driver for Windows 3.1x. And download INI files from here: Re: HDA Audio driver for Windows 3.1x. But I get no sound using speakers or headphones. I'm using Windows 3.11 (not Workgroups) in Standard Mode. Using MS-DOS 6.22 without EMM386 or any other EMS manager.

ntalaec wrote on Yesterday, 11:09:

I had no luck trying to use the driver in my hardware.

I followed the steps from here: Re: HDA Audio driver for Windows 3.1x. And download INI files from here: Re: HDA Audio driver for Windows 3.1x. But I get no sound using speakers or headphones. I'm using Windows 3.11 (not Workgroups) in Standard Mode. Using MS-DOS 6.22 without EMM386 or any other EMS manager.

And do you have either Realtek ALC1150 or Realtek ALC3202? Otherwise you should not expect those config files to work. The most important thing to understand is that this driver is not 'universal' in the sense that it can figure out the details of your HD audio system alone. You have to make the proper config files for yourself. The first step is to identify the exact model of your HD audio device/codec. If your HD audio is a Realtek one then there is a good chance that you can finally succeed. You should follow the steps from here:
Re: HDA Audio driver for Windows 3.1x

There was a newer version of the Watlers driver posted on MSFN in June, which includes at least a basic codec parser if you don't provide an INI file. MSFN is down at the moment so I might as well post it here. If Watler has a problem with that he's welcome to contact me.

AFIK Watler hasn't been heard from in many years.

The down side to the internet is you rarely find out what happened to people.

Falcosoft wrote on Yesterday, 11:38:

And do you have either Realtek ALC1150 or Realtek ALC3202? Otherwise you should not expect those config files to work. The most important thing to understand is that this driver is not 'universal' in the sense that it can figure out the details of your HD audio system alone. You have to make the proper config files for yourself. The first step is to identify the exact model of your HD audio device/codec. If your HD audio is a Realtek one then there is a good chance that you can finally succeed. You should follow the steps from here:
Re: HDA Audio driver for Windows 3.1x

According ASTRA is a Realtek ALC262.

1Realtek ALC262
2  Device (27D8h):                    82801G (ICH7 Family) High Definition Audio
3    Subsys Vendor (104Dh):             Sony Corp
4    Subsystem ID (9064h):              Unknown
5    Class (04h):                       Multimedia
6    SubClass (03h):                    High Definition Audio
7    Hardware ID:                       VEN_8086&DEV_27D8
8    Revision:                          02h
9    Interface:                         00h
10  Device Properties
11    Device Timing:                     Fast
12    Memory Access:                     [X]
13    I/O Access:                        [ ]
14    Bus Master:                        [X]
15    66 MHz Speed Support:              [ ]
16  Device Resources
17    Memory Address:                    F0440000h - F0443FFFh
18    System IRQ:                        7
19    Interrupt Pin:                     INTA#
20  Sound
21    Audio Codec Name:                  Realtek ALC262
22    Controller Type:                   High Definition Audio

onethirdxcubed wrote on Yesterday, 17:49:

There was a newer version of the Watlers driver posted on MSFN in June, which includes at least a basic codec parser if you don't provide an INI file. MSFN is down at the moment so I might as well post it here. If Watler has a problem with that he's welcome to contact me.

This version worked for me without editing any .INI files. But I have two issues: the volume is close to zero (I can barely hear anything) and takes about a minute to load.

These are my auto-generated files:

HDACFG.INI

1[ALLHDA]
2$00D8=$27D88086
3
4[HDA]
5Mytimer=1
6winmode=Enhanced;(HDATSR required!)
7TSR=HDATSR Found
8PCI_VID=$8086
9PCI_DID=$27D8
10
11[BUSMASTER]
12myPCIHI=$0012
13myPCILO=$0000
14myPCI=$00120000
15aPCIHI=$0011
16aPCILO=$0000
17aPCI=$00110000
18
19[HDA_27D88086,9064104D]
20cardmemregistersLO=$0000
21cardmemregistersHI=$F044
22CODEC_Index=$0
23Verbinterface=$1
24wait1=$100
25wait2=$60
26pcipatchB=$0000
27PCI_BUS=$00
28PCI_DEVICE=$1B
29PCI_FUNCTION=$0
30GCAP=$4401
31VMIN=$00
32VMAJ=$01
33GCTL=$0001
34CODEC BITMAP=00000001
35CODEC_VID=$10EC
36CODEC_DID=$0262
37CODEC_REV=$100302
38CODEC_NODEINFO=$010001
39CODEC_AFG_GPIO_CAP=$40000004
40CODEC_AFG_SUBSYSTEM_ID=$104D4000
41CODEC_AFG_PM_SUPPORT=$4000000F
42CODEC_AFG_PCM_DEFINITION=$E0560
43CODEC_AFG_F000B=$01
44SleepingWidget=$02
45OutputWidget=$02
46VolumeWidget=$02

HDALOG.TXT

1$000F0000=$10EC0262
2$000F0004=$00000000
3$000F0005=$00000000
4$000F0000=$10EC0262
5$000F0002=$00100302
6$000F0004=$00010001
7$001F0011=$40000004
8$001F2000=$104D4000
9$001F000F=$4000000F
10$001F000A=$000E0560
11$001F000B=$00000001
12$00170500=$00000000
13$00C707C0=$00000000
14$00C3B000=$00000000
15$00C3B000=$00000000
16$00D707C0=$00000000
17$00D3B000=$00000000
18$00D3B000=$00000000
19$00E707C0=$00000000
20$00E3B000=$00000000
21$00E3B000=$00000000
22$00F707C0=$00000000
23$00F3B000=$00000000
24$00F3B000=$00000000
25$010707C0=$00000000
26$0103B000=$00000000
27$0103B000=$00000000
28$011707C0=$00000000
29$0113B000=$00000000
30$0113B000=$00000000
31$012707C0=$00000000
32$0123B000=$00000000
33$0123B000=$00000000
34$013707C0=$00000000
35$0133B000=$00000000
36$0133B000=$00000000
37$014707C0=$00000000
38$0143B000=$00000000
39$0143B000=$00000000
40$015707C0=$00000000
41$0153B000=$00000000
42$0153B000=$00000000
43$016707C0=$00000000
44$0163B000=$00000000
45$0163B000=$00000000
46$017707C0=$00000000
47$0173B000=$00000000
48$0173B000=$00000000
49$018707C0=$00000000
50$0183B000=$00000000
51$0183B000=$00000000
52$019707C0=$00000000
53$0193B000=$00000000
54$0193B000=$00000000
55$01A707C0=$00000000
56$01A3B000=$00000000
57$01A3B000=$00000000
58$01B707C0=$00000000
59$01B3B000=$00000000
60$01B3B000=$00000000

61$00224011=$00000000
62$00270610=$00000000
63$00224011=$00000000
64$00270610=$00000000
65$00270500=$00000000
66$0023A07F=$00000000
67$0023907F=$00000000

If I run WAVEOUT.EXE and press the button waveOutGetDevCaps I get this log:

1szPName: HDA Sound   
2Driver Version: 0.145
3Stereo
4Independent L/R volume
511 kHz (1 channel) 8bits
611 kHz (2 channel) 8bits
711 kHz (1 channel) 16bits
811 kHz (2 channel) 16bits
922 kHz (1 channel) 8bits
1022 kHz (2 channel) 8bits
1122 kHz (1 channel) 16bits
1222 kHz (2 channel) 16bits
1344 kHz (1 channel) 8bits
1444 kHz (2 channel) 8bits
1544 kHz (1 channel) 16bits
1644 kHz (2 channel) 16bits
1748 kHz, mono, 8-bit  
1848 kHz, stereo, 8-bit  
1948 kHz, mono, 16-bit  
2048 kHz, stereo, 16-bit  
21Left : 65280, Right : 65280

If I change the sliders (volume control?) in the left, these lines are added to HDACFG.INI:

1[Volume]
2waveout=$FF00FF00
3floatvolL=1
4floatvolR=1

This don't have any change in output volume. According README.TXT in WAVEOUT's folder, VolumeWidget in HDACFG.ini can be changed to $7F, but there's no difference in volume and after exit Windows $02 value is restored. The TXT also says that "Volume may not work on some computers. Not all devices support volume control." maybe it's my case.

I also can't reduce the one minute delay when loading Windows. Does not matter the value in wait1 or wait2 in HDACFG.ini.