sifonium

@deomsh Thank you for this final version of HDAICOUT, works perfectly! And for all the effort you put in making this driver work. I think now I have enough commodities to keep this laptop alive, almost as a full fledged Win98 machine. Hopefully our conversation helps someone else as well! Some notes: - doubling VolumeWidget doesn't work - KB138857 you suggested seems to be for playing SB sounds on speaker, not the other way around. I was hoping HDAICOUT might make it work, since there is DIGITAL BEEP widget and all, I did some more tries, but nothing. So I'm leaving the pc speaker thing alone for now - and somebody might find this useful - Device Manager / System Properties / Performance / File System / Troubleshooting - checking "Disable synchronous buffer commits" solves stuttering of the audio in DOS mode using the VDMsound. Seems to help the stability overall as well, but it's hard to tell for now. I will come by! :) Cheers!

@deomsh Apologies for these gdrive issues, the service gives me trouble sometimes loading a disk imaging tool, so I turn it off, until something or someone reminds me! It's online now.

@deomsh You're the HD Audio whisperer! The sound is coming out of my speaker, and nicely, thanks to your latest HDAICOUT! At glance! And thanks to all your input, and again your HDAICOUT, I think I connected all the links I was missing. HDAICIN is on gdrive - tests v12. I enhanced the volume to 3F's, I initially tried the higher values, but when I got no sound, I remembered the post which suggested the max is somewhere around 4x, beyond that, sound breaks (at least in this codec). I figured out how to change the volume on the fly with INTELHDA - that was straightforward. I then tried to include the system beeper in the mix, by trying some of the verbs with the beeper related NIDs, using the manual, however, that didn't work. I haven't tried more because I'm not sure if that's possible at all - maybe the system disables the beep when the audio driver is loaded? I think the system beep didn't work with USB audio as well. If you happen to know about these possibilities, let me know, and I'll do some more testing. It would be nice to have it for DOS purposes (an euphemism :)) Also, any ideas would it be complex to develop a simple program to manage the volume and some other things these verbs might handle? In other words, something that sends verbs. Just wondering, not that I have an idea on how to make one anyway.. This stuff here is pretty much my gaming - troubleshooting stuff. And games are just for testing purposes, in most cases ;)! Regardless - it's a fun, but time-guzzling hobby!

@deomsh Hi, I'm back, sorry for the delay.. I did a trial test, and I'd like to check with you if I know what I'm doing. I'm pretty sure I'd know better if I had a chance to read more on this, as you suggested, but currently my time is very limited, so I tried some quick things that seemed logical for start. I think I've got some results, let me know if they mean anything (test v11 on gdrive). I did this, let me know was that a correct procedure: 1. to make a SET verb out of a GET verb, I used the instructions/notes from the codec manual - the same page where you showed me the GET commands. 2. I used some of the first get verbs from the HDAICOUT, for each one first the GET verb, then the SET verb, then GET again, and some of them manage to get set, if I see things right Some of the questions I have: 1. As far as I learned and can see from the HDAICIN results, the last two digits in the SET verb, is the value to assign to the addressed node(or register .., I'm missing some terminology). Is that correct? 2. What should the values of those two last digits be for testing? Should they all be the same? Basically, I don't know anything about them, except they set the volume in some cases. I used 1F, randomly. 3. What is the goal of these first tests, is it to see which nodes can be set (accept the set command), and which not? 4. If these first tests are done well, by chance, what should be my next move - try the SET verb on each of the GET verbs I had in the HDAICOUT, or? 5. Should I be checking the sound at this phase? Or are these just preliminary tests? 6. I didn't quite get what you said about trying the different output widgets. Do you mean in HDACFG? Is that the output widget or did you mean the volume widget, if so? 7. Can INTELHDA help me with any of these tests maybe? To save on restarting.. As you can see, I'm quite not sure about many things, so feel free to send me back to school if you think I went too far ahead! Thank you!

tests v10 uploaded! HDA regularly gets unrecognized, but that's ok for now. Tests seem the same, except that the empty lines repeated the previous verb,

@deomsh I glanced over some of your posts in this thread, and now I hope I understand all the notes you wrote to me, also the table from the manual. I'm still far from understanding it all. So I made my first HDAICOUT test, and there are some kind of results in the HDAICIN, which mean nothing to me yet, though. I uploaded the tests v9 to gdrive. Let me know if this was done good, and why not

Nice, there are various conclusions coming out of this experiment! De aanhouder wint to you as well! I understood "ustrajati", and as far as I can see from this thread you are holding the throne! I'm unfortunate to say, my Dutch hasn't yet evolved even to "dobar dan" level, but I hope it will. HDACFG - I tried other Volume widget numbers - 05, 07, 14... also tried 14 for Sleeping widget. No settings produce any sound, but the current settings (03,06,03). Many thanks for your notes, I see you dug deep in this. So where are you heading with it, to making a new, more versatile driver? Or? I'm interested, and sorry if I missed this info in the thread, I had a tunnel vision looking for the correct configuration.. I have some questions on how to proceed with my experiments: 1. Am I done with HDACFG.INI or is there any more room to add or edit stuff? By adding, I mean more nodes, instructions, if there is capability.. 2. HDAICOUT.HDA - should I use it again, start from an empty one? Is this the place to try to get the sound out of the speakers since the widget changes didn't bring results? 3. Are any other files involved? I'm aware that any route will certainly need some time invested in studying (your notes, codec manual, this thread), I'm pretty sure I can't count on another BIOS scenario.. But, it's interesting stuff. So.. do you do this audio driver thing often, or is it just this one? Funny how this driver managed to crash even your main system. Watch out for the fuse box!

An unexpected break through!!! I updated the BIOS - twice, first to f.10 (using file from here - https://www.badcaps.net/forum/showthread.php?t=92864), then to f.20. (hp has it on the web). F.10 needs to be installed first. Funny thing is, I did that in hope that the modem would show up in bios, to turn it off. It didn't show up! BUT - when I booted Win98, although I didn't really expect to see any change in HDACFG and the log, when I checked - the 11D41981's and codec index=$0's all over the place! Check it out: $000F0000=$11D41981 $000F0004=$00000000 $000F0005=$00000000 $000F0000=$11D41981 $000F0002=$00100200 ... HDAICOUT is out of the picture! Waveout volume control works at glance! HDACFG looks perfect to me! I added the winner test files v8 to gdrive. I'm going to experiment now with the widgetry, and try out how things work from now on. Maybe the bios update made the driver use more stable.. I'll report! Cheers and a big thank you!

I played around with this new [HDA] section and the L driver: 1 - I created [HDA] section with the entries according to your instructions, first without, then with HDAICOUT, nothing new happened - test files v4 on gdrive 2 - I experimented with placing the [HDA] section's entries within the existing [HDA] section on the top of the file, nothing happened except some new moments in the log - test files v5 3 - I tried to add some other entries from the [HDA_284B8086,30C8103C] to the new [HDA] section, nothing 4 - renamed [HDA_284B8086,30C8103C] to [HDA] and edited the entries i knew - nothing again, the system just added the old [HDA_284B8086,30C8103C] section 5 - then tried your addendum - nothing, my new entries get overwritten every time by my "default", old entries, SEARCH=FALSE remains there though. - test files v6 I tried making the HDACFG read-only, just in case, but the error about it showed on the start-up - ofc. The driver seems stubborn in doing things its own way, and overwriting these entries. I will certainly do more studies of this thread, and search for ways to configure HDAICOUT, but that will take some time. Do you think I could find any inspiration for that within the system / driver files on a newer version of Windows (XP,..) which has the regular driver installed? Some similar files to HDAICOUT? (more shooting in the dark, I guess not) If any other idea comes to your mind, please let me know! I will keep you posted on potential progress (and probably will have some new questions).. Thank you one more time for making the sound work on my laptop!! Cheers!

Thank you for all this effort deomsh! Regarding stability - I'm ok with the current situation, I'd say it is better than expected considering so far experience with this driver. Now I'm back to the J version of the driver, WinQuake didn't work with the L one. So as I understand, most of these steps you wrote consider stability, except for the HDACFG ones, right? Some of them I already put in place, some of them I will try out yet. Verbinterface=$0 - it makes no difference, but makes a break in HDALOG with 3 lines begining with "First IRS change $...". Timing changing and pcipatch make no difference. I'd like to see what is possible for me to potentially get the sound on the speaker, also to have volume control - I read Vigami's and your posts, and I'd like to check some facts and ask some more questions, if that's ok. 1. Changing the HDACFG.INI basically does nothing in my case, since it's aimed at the wrong device (the modem). Only the HDAICOUT.HDA file communicates between the HDA driver and the HDA codec to configure the hda device - simply put. Is that correct? 2. HDAICOUT.HDA - it sends all the configuration messages / verbs to the HDA codec/device - power up, inputs, outputs, volume control,.. Right? As far as I managed to reach, these verbs consist of $ABCDEFGH, where A is codec index (in my case 0), BC is the Widget (or the Node?) to address, and GH is the value to assign to that address. Is that correct? And excuse my poor terminology. I wasn't able to reach what would would DEF numbers represent. And I didn't quite get how the file functions. I tried to put some extra entries inside of it to try to configure volume, inspired by Vigami's post, but that was just shooting in the dark, it did nothing, and I probably didn't do it well. Do you have any tips on how to start experimenting with the HDAICOUT, anything I could enter inside, that would give me some kind of result, so I could build on it? Does it need to have all those entries (as in your file I'm using), or those are just to cover as many posibilities / codecs? Are the comments after the semicolons just comments, or they do something? Also, do you have an idea how much effort could it be, what are the chances for a result? Maybe it's easier route to try to disconnect the modem phisically, and play with HDACFG? Appologies for this collection of questions, this is fun to do, but also really far above my expertise level!

Great news - the sound works now with the Index=0 HDAICOUT! Bravo!! I tried it first with the L driver version, and it worked, so I haven't tried the others. I uploaded the K one to gdrive. Then I experimented with the widget configs to try to get the sound out of the speaker instead of the headphones, and after a couple of variants, I realized that it made no difference what I write, whatsoever. I could even change the Output widget to whatever number, and the sound was still here - but only through the headphones. WAVEOUT volume control also has no effect, volume is always the same. I guess the reason could be that HDACFG.INI still has the CODEC Index=1, and the modem's VID and DID written in it. I tried to change those to the actual values, but Windows keeps reverting it to the modem ones. I uploaded the latest test files to gdrive, folder "tests v3". Do you have any suggestions on how to solve this? It would be great to have volume control, also sound on the speaker. Notes: - Whenever changing some hdacfg.ini config, or deleting the log files, the first, or couple of first boots end up in runtime errors. Then it gets normal. - system.ini - when i have "wave=hda2.dll" instead of "wavehda=hda2.dll", Windows stopped adding the "wave=mmsystem.dll". Also having two of "wave=" seems to disable one of them. - regarding the PCI memory thing from my last post - IntelHDA is showing a different memory address of the HDA card now (after I disabled all built in devices i could in bios). But I guess that's irrelevant. MIDI: I managed to install Yamaha S-YXG100plus soft synth, to work alongside as a Windows 98 MIDI driver - the Yamaha midi synth shows up in MM settings and can be used. That place was empty before, as the Windows MIDI driver didn't work with this HDA driver. SYSTEM.INI settings for it: ;;wave=mmsystem.dll ;;midi=mmsystem.dll ;;midi8=sxgma.drv ;;wave8=sxgma.drv ;;mixer8=sxgma.drv midi=sxgma.drv wavemapper=*.drv MSACM.imaadpcm=*.acm MSACM.msadpcm=*.acm WAVE=HDA2.DLL First few boots I got blue screens, but then it stabilized. So, my conclusions about the SYSTEM.INI config and the HDA driver (at least in my case) are: - there should be just one "WAVE=" entry, and just one "MIDI=" entry - no "WAVEHDA=", "WAVExxx=", "MIDIxxx=".. - if there is "WAVEHDA=" or "WAVExxx=" and no "WAVE=" entry, the system keeps adding it's own "WAVE=mmsystem.dll" which in my case can't coexist with the HDA driver. For information - both audio and Yamaha midi work with VDMSOUND in DOS mode, as well. There is some stuttering though, which is not present in Windows. But, I only tested Prince of Persia in DOS mode, and Doom95 in Windows, for now. One more question - are there any settings I could play with to tackle the latency, or potential stuttering? I'm really happy about the progress, cheers!

I get what you are saying about the modem, and this sounds like it could be the main problem. Maybe that is the reason why the HDA doesn't get recognized in Device Manager? Unfortunately, there is no option in the bios to remove it, should I try to disconnect it physically? I'd rather not dismantle the laptop, but hopefully I can. Also, let me know if I should look for the solution in the previous posts. So, just in case something could change, I disabled all other built-in devices I could. It didn't change anything. Then I let Windows create another HDACFG.INI, edited the widgets, erased the .txt logs, and let Windows create them freshly. I uploaded them to a new folder called "Tests v2" on the same google drive link. SYSTEM.INI is there too, but this mmsystem driver doesn't seem to crash my system any more, maybe it was something else. Should I try another version of the driver again (K or L), is there some important difference? I also added a more thorough manual of my laptop to the PDF Manuals folder. There is some more info on the built-in devices and how they are mapped, maybe that might help. Note: - after disabling all the built-in devices i could, the Pci mem of the card (IntelHDA) jumped from from E4644 to E4544, I don't know if that is relevant

Hi deomsh, thanks for your quick response! I did the following: - edited the volume down to 1F001F00 (HDACFG.INI) - placed the HDAICOUT.HDA from your "CODEC Index=$1" folder, to my "c:\Windows\" folder - tried all the combinations below (HDACFG.INI): SleepingWidget=$03, 14 (I don't know if 14 makes sense here, but I tried it) OutputWiget=$03 VolumeWidget=$03, 05, 06, 07, 14 No changes, sound is not there, except for the two clicks when Windows show up. I guess you would have warned me, but let me check anyway - can this work at all if there is no HDA device present in any of the known categories in the Device Manager? Looking forward to the next step - if there's any Cheers!

Hi guys, if anyone is interested to help me out, below is my testing info, and attached is the zip with the hdacfg.ini and hdaicout files, as well as HDA Utility exports. On link are the laptop and the codec manuals, HDA Utility and IntelHDA screenshots, as well as the files from the attached zip - https://drive.google.com/drive/folders/19xcjnslL5ibH1E1PeedwKmc55QjnFPz-?usp=sharing Laptop is HP/Compaq 2710p, audio codec AD1981HD. Here is my testing info of the HDA driver: - when starting Windows 98, I hear two clicks on my headphones, nothing else - wav files seem to be playing on the player, but no sound is heard - situation is the same with or without the HDAICOUT file - Judas player in DOS plays the xm file at glance, sound is heard nicely via the headphones - IntelHDA gives the same results before and after Judas - screenshots on link above - Multimedia Settings - HDA Sound is there, and I can select it - Device Manager - no new device shows as the driver is installed. There is an unknown PCI card with a same PCI address which is shown by IntelHDA, so I guess that might be the HDA card, but it stays unrecognized - HDA Utility - I tried it with Windows 10 that has the HDA driver installed, I exported what I was able (on link). Unfortunately, there is no graphic present, probably because of win 10. I don't know if that is crucial. - HDACFG.INI - I tried various combinations of widget numberings, all that made sense to me according to the AD1981HD manual and the HDA Utility info. Foremost changing the Sleeping and Output widgets to $03. Nothing made a difference, maybe sometimes I lost the start-up clicks or got error messages, I'm not sure if that was connected. Attached is the original, system generated HDACFG.ini Some other info: - Windows 98 keep adding "wave=mmsystem.dll" to system.ini. Should it be present? If it's present, system crashes when using the driver version K or L, but J works. I don't know if that is relevant though, when system didn't crash, it made no difference to the above. Let me know your thoughts, cheers! Hda.zip