deomsh

@Dave-H: Sorry for misunderstanding. I suggest: stay using HDATSR, HDAICOUT.HDA, HDACFG INI: Verbinterface=$1, Mytimer=0 and VolumeWidget=$0C as I suggested earlier. While experimenting stay with latest "best" configuration! For faster testing make shortcuts in your Startup folder to HDARUN.EXE and SNDREC32.EXE and place a long WAV-file in MyDocuments. I found two MS-DOS MPlayer versions during traffic, just tested with a WAV-file on my System. http://rayer.g6.cz/download/download.htm https://web.archive.org/web/20170501000000*/http://falcosoft.hu/mplayer_dos.zip You can download mplayer_dos.zip from the link september, 24th. So no direct linking (just in case Moderators think so and ZIP is included in the rules). Rayer's file is newest. If his version is not working with MPLAYER YOUR.WAV add to command-line: ao=wss:dev=-1:vol=21:latency=0.025 Other version should work with MPLAYER YOUR.WAV

@Dave-H: That erratic behaviour/ 'Device in use problem's' of the "HDA Sound"-option should be tackled somehow. Since I am not a programmer I cannot rewrite HDA2.DLL (source code is included in the Zip!). If I did understand your question well: you want a hint regarding "wait settings". Start with 120 (both) reboot, test, set to 140, etcetera. Go up to 200. If no changes try 80 and go down to 20. In the meantime I will try to re-read Intel's High Definition Audio Specification, although the part about the HDA Link is not my favorite. BTW: did you find a MS-DOS version of MPlayer?

@rloew: ALC885/ALC887 have no VolumeKnobWidget, as far I can see in the data sheet. The four DAC's connects to Mixers 0C/OD/OE/OF. If using HDAICOUT.HDA all PinWidgets should be connected to OC (I am not sure if SPDIF-OUT is acually functional, never tested it). ALC885 has more streams, with extra Mixer 26. HDA2.DLL has some stability issues: Sporadic 202 Error's at Startup or during operations involving bigger files. On my system extreme low Vcache settings gave more stability, MinFileCache=1024, MaxFileCache=1024, especially with other 16-bits drivers used). Also higher MinTimeSlice values May help. I have no video/ audio-problems. HDATSR's buffer can be forced being set to high by other program's (already with SMARTDRV 4096!). Alternative is shown in one of my Post's for Dave-H in this thread. Clipboard operations, depends somehow on the video card/ drivers too, didn't really test this, so maybe hypothetical. Issues with DosBoxes, absolutely video card/ driver related. Since I had to reverted back to my PCIe GF 6700XL I had less issues with the 7772 driver (IF all Nvidia's utilities had been disabled in MSCONFIG. BTW: according to the Readme EMM386 shouldn't be used (no testing possible on my System).

@rloew: Oops, I found that there are different species of M5A97, with different codec's. Please post content of HDACFG.INI. HDARUN is only needed with Mytimer=0, copied for testing purposes (but absolutely needed in Windows 3.x Standard mode). Maybe I should delete it in my INF-file in favour of WAVEOUT.EXE, and add some Volume Control Icon. There are some delays, on my system the Desktop is ready a few seconds later, opening a sound-file less than a second delay. Should be related to the timing settings in HDACFG.INI. They are related to sending/ receiving Verb's to the codec througt the Azalia controller. "Verbinterface=$1" is the CORB/RIRB-Interface (Default in version 9 of HDA2.DLL), "Verbinterface=$0" is the Immediate Command-Interface (only interface in earlier verisons of HDA2.DLL). The settings wait1=$100 and wait2=$100 can be changed, only a reboot is needed. I tested GOM Player, no problems. Best Audio renderer is Direct Sound, further setting the Wave Buffer in Multimedia Properties at 5 seconds. That sounds bad. Never heared of such "overheating", is damaging electronic circuits a possibility? There are various species of Z87. Your board seemes to have the same problem as Dave-H's. Most Linux-sources I have been reading mention in case of controller related HDA-problems setting/ disabling the NoSnoop bit, or setting MSI to a legacy mode. @Dave-H: In the mean time I compared the PCI-Registers of your picture with your HDA Controller's data sheet (page 495-507). Except one hardwired value, all values are the Defaults. So nothing special. Interesting test with Judas 2.1c. Maybe Judas is to old, but at least it's good to know that it doesn't work too. The operation of a MS-DOS HDA-player is of cause independent of HDA2.DLL, but I hoped to see a difference in your Controller's PCI-Registers afterwards. With a certain version of HDA2.DLL, Judas 2.1c changed one tiny bit on my SB600 system and I got sound in Windows. For a while I had to start Windows 3.1 with BUG.BAT, until Watler produced a new version of HDA2.DLL. Yesterday I tested MS-DOS version of MPlayer, plays WAV files and is much more recent. At the moment I have no time to seek for a link, but maybe you can find it. I'd like you to do the same test with a rewritten BUG.BAT, and posting a picture of AHDA17O -> PCI, IF you observe differences. I am hesitating a "bit" with theoretical possibilities, because of writing to PCI-registers on a system that is not mine. In HDACFG.INI one 8-bit Register can be changed with the setting "pcipatchB=$xxxx". About "HDA Sound", is the option stable with Mytimer=$1 too? If yes, return to this setting. Further it would be nice if you start experimenting with the "wait=" settings, I suggest higher settings first, with "20"-steps. Maybe you can observe a difference regarding the "your sound card may be in use" problem. Will cost you many reboot's, I don't feel responsible for the bearings of your Hard Disk. @UCyborg: Thanks for testing, does your IRQ-changing imply that the Controller had an exlusive IRQ? I am sorry but I can't understand your logic of facts related to a (even virtual) AC'97 controller. About your Choppy sound: maybe a silly question. Did you rule out Guest/Host problems? How's HDA-sound with W2K or XP? I saw some interesting HDA-correspondence on the VirtualBox-Forum about W2k/XP and even WIN10 as a Guest (mainly on older versions of VirtualBox). Your (Virtual) HDA Codec should be STAC9221. According to the data sheet: "VolumeKnob Node (NID = 0x16)". So try VolumeWidget=$16 if you like.

@Dave-H: Thanks a lot for the PCI-picture. I will compare it with your chipset's data sheet. Next (we are still in Step 3) I want you to run a small test: check with the batchfile if JUDAS 2.1c is delivering sound on your system in pure MS-DOS (after loading CONFIG.SYS/ AUTOEXEC.BAT). Both your chipset and your codec are listed inside the source code of JUDAS 2.1c. If there is some sound, enjoy Afterwards the batch-file will boot DIRECTLY (no reboot) into Windows. Once in Windows please do the same as you did earlier to deliver a picture with AHDA17O. Steps: 1) Get Judas 2.10c (ZIP-file) from https://web.archive.org/web/20121109163845/http://www.piotrkn22.republika.pl/judas/index.html 2) Make following directory in your root: JUDAS21C 3) Copy JP.EXE, JUDAS.CMD, ANAL.CFG, ANAL.EXE, CWSDPMI.EXE and TUNE1.XM to this directory. 4) Make following batch-file and save it in C:\ as BUG.BAT. ======================= BUG.BAT ======================= cd JUDAS21C JP.EXE TUNE1.XM -d C: cd \ WIN ======================= 5) Shutdown and Restart after a while (please!) 6) Boot into MS-DOS 7) Run BUG.BAT BTW: if CWSDPMI.EXE gives problems, try DOS4GW.EXE instead (never worked for me). It resides in the ZIP-file too.

@Dave-H Allright: Go to http://turkeys4me.byethost4.com/files and get AHDA17M (in fact it's version O) and unzip the AHDA17O-directory somewhere. Run INTELHDA.EXE, you will see two windows, both with tabs. Click ONLY Tab "PCI", resize the windows just like my picture below, and upload a picture. All W1/W2 values must be included. BTW: you can disable MaxPhysPage as long as you reenable HDATSR in AUTOEXEC.BAT. HDACFG.INI [Busmaster] values will be overwritten by the TSR after reboot.

@Dave-H: About the changing behaviour of the "HDA Sound"-option: is there any difference in behaviour after a cold boot (including power switch off for 120 seconds), a hard reset (Reset switch) and a soft reset (a reboot)? Regarding "SETUP /p i", I understand and respect your position, although unfavourable from a testing point of view. At the moment I am preparing the next step, so we (hopefully) get information about the actual values of the PCI-register of your Azalia controller.

@UCyborg: Thank you. I never used QEMU, but if you like to try.... More results are always of interest. Can you tell what version of VirtualBox you are using? I'd like to see your HDACFG.INI too. I always can take a look in the data sheets. Regarding IRQ's: maybe it was'nt clear what I ment. I am not a native speaker, sorry for my poor English. I did not ment an IRQ-conflict, but IRQ-sharing. Because of disturbances of the audio stream in Windows 3.1, I had to abandon my Legacy USB-mouse in favorite of PS/2. This could be IRQ-related. In Windows 98se IRQ-sharing is not bad, but in this respect I am not sure about Windows 95 osr2. If in VirtualBox exists a (virtual) BIOS, maybe there are options to change IRQ's.

@rloew: So a "successtory"? Good to hear that your RAM Limitation Patch is not conflicting, as I expected (if using HDATSR). Did you need HDAICOUT.HDA, or was the driver running out-of-the-box? Your motherboard has codec ALC887, according to the datasheet you will have to set VolumeWidget=$0C in HDACFG.INI. The Volume Control program has to be started manually, it's not included in my INF-file. Personally I do not use it, in Win9x I use the volume slider from the (multimedia) application. Regarding uninstall: HDA2.DLL can be disabled with a semicolon in SYSTEM.INI and manually deleted AFTER reboot. HDATSR can be removed from AUTOEXEC.BAT and deleted in %Windir%. My INF-file comes with an uninstall procedure ( Control Panel -> Software). After reboot the entrances in SYSTEM.INI and AUTOEXEC.BAT and all files directly related to HDA2.DLL should be removed (HDAICOUT.HDA has to be added if needed, so this file and the corresponding logfile HDAICIN.TXT will remain, but will do no harm). Only the entrance "High Definition Audio Controller" has to be deleted manually, but can be left too. I searched and experimented a lot, but I could not find a way to delete it by means of an entrance in an INF-file. I added the entrance in Device Manager -> System Devices only as information that the generic VEN/ DEV is accepted. The entrance is not needed since the driver is loaded by SYSTEM.INI (loading HDA2.DLL is not even logged by BOOTLOG.TXT).

@MrMateczko: For Ethernet there are many factory-made NDIS2-drivers. In case of HDA it would be nice if there exists a universal 16-bits driver, with non-ISA motherboards in case of Win3.x audio is much more difficult to get. Such an universal driver could be tried on Win9x too, without the "not really convenient" issues you described. Maybe take a look at the Linux ALSA project, how convenient programming their universal driver is. Watler adjusted his Win3.x driver for all chipsets/ motherboards he could obtain, but there was virtually no interest in his driver. The first version I tested (in Windows 3.1 on my motherboard) had no configuration options. When I asked him for help, I had to test more than twenty versions before I became sound. But he too made configuration options in HDACFG.INI and made startup codec-programming possible with HDAICOUT.HDA, both (almost) on a user level. I had the simple-minded idea to use this driver as 16-bits driver in Windows 98 SE about a year ago, and all in all it satisfies my needs. Still there are some stability and other issues, but I can live with them. "HDA Sound" should be usable with every program compatible with Wave Out or Direct Sound. In case of Direct Sound: with Software Emulation only. Hardware related Audio Accelaration is out of the question. As far I know in that case (minimal?) a WDM-driver is needed. I have used "HDA Sound", apart from System Sounds, with various Windows 3.1 VfW/ WAV/ Audio-CD/ MP3 and MIDI-to-wave players. In Windows 98se: Sound Recorder, various Microsoft Multimedia players, Foobar, WinAmp (16-bit output only, max 48khz; I assume two-channel - I am using headphones), MPC, MPC-HC, MPC-BE, KMplayer and POTplayer. BTW: did you read UCyborg's report about VirtualBox in this tread? As long no one is trying, there will be no new "success"-stories.

@Dave-H: That's the real spirit. I noticed your NDIS2-driver in your MEM output. Nice project too, I've did one for RTL8189. I am "confident" in so far, IF it's possible to get "HDA Sound" as stable Playback option it's worth to move on. In this respect you didn't answered my question yet if you tried in the past a Windows install with SETUP /p i Regarding the sound of silence it can be worth trying to plug-in your speakers (better use headphones!) one by one in all other available jacks, and listening during boot-time if you hear the slightest "plop" or "click".

@Dave-H: I am sorry to hear that your Sound System is not stable in combination with HDA2.DLL. This problem must be resolved first before we can move on. If you're afraid wasting your time, better go for another option. In the meantime I have found your motherboard manual; if I'm right you have two normal PCI-slots, so maybe there is a PCI-soundcard that suits your needs. I think I found the datasheet of your chipset too (needed for step Three) and I am reading it already. So plenty of time to waste If you'd like to continue, I'd suggest first retesting after commenting out following devices in your SYSTEM.INI: [386Enh] ;; device=convmem.vxd ;; device=c:\programf\afterdar\adw30.386 ;; device=dva.386 (unless you really need DVA.386 ??) [Drivers] ;; Adwrap=c:\programf\afterdar\adwrap.drv

@Dave-H: If the slider of Sound Recorder is moving, there is a stream of sound, I think we can try the next step. Maybe the memory addresses provided by HDATSR are somehow overwritten because of your Windows configuration. My idea is to disable HDATSR and give the driver a memory address just above 1 GB (is working on my System). So temporarily you will have less memory. Can be later fine-tuned if things work. I am not sure if this will conflict with your special memory driver, but don't think so. Configuration: following must be set (some values will be allready there). AUTOEXEC.BAT (.......) REM C:\%WINDIR%\HDATSR SYSTEM.INI (.......) [386Enh] (.......) MaxPhysPage=40000 (.......) HDACFG.INI (.......) [BUSMASTER] myPCIHI=$4012 myPCILO=$0000 myPCI=$40120000 aPCIHI=$4011 aPCILO=$0000 aPCI=$40110000 [HDA_269A8086,948015D9] (.......) Mytimer=0 Verbinterface=$1 wait1=$100 wait2=$100 pcipatchB=$0000 (.......) SleepingWidget=$02 VolumeWidget=$0C OutputWidget=$02 [Volume] PCM=$FFFFFFFF Back in Windows start HDARUN, click "Loop" (no other buttons!) and try to play a WAV file in Sound Recorder (the slider must be moving). Check behaviour of the "HDA Sound" option, and the DMA address of "Audio for HDA Sound 2017" (as you did in your post of 1 April). BTW: before closing HDARUN, first close Sound Recorder, then click "Loop" once again and close HDARUN.

@Dave-H: Did you mean: with the HDACFG.INI-setting Mytimer=0 "the Control Panel "Sounds" applet actually coming to life, in that the test facilities weren't all greyed out, and I could push the test play button on all the system sounds" while with Mytimer=1 everything was grayed out? What about the option "HDA Sound" as Audio Device in Multimedia properties, is that option stable with Mytimer=0, even after a reboot? If this is true, this is a big step forward. In my opinion Windows "Wave device" is in that case delivering sound to the driver. If you open Sound Recorder and start playing a WAV-file, with HDARUN enabled, is the slider moving? If yes, we maybe can ignore your configuration issues in Device Manager for the time being and try next logical step (out of three): to check if the memory address (-range, for a buffer) that the driver needs to send data to the Azalia Controller, is actually "outside the reach of Windows" (this address is different from the one of the cardmemregisters and now shown as the one delivered by HDATSR, somewhere in the 1MB-4MB region). BTW: I think the writing under the HDARUN windows is "This program runs wx3ac97.dll", bad placement, maybe a glitch of the programmer, its not important.

@Dave-H: Thanks for all your information! At least your High Definition Audio Controller's memory address is the same as noted in HDACFG.INI. Things are getting more complicated, but more challenging too. You said you "have never been able to resolve these conflicts". Maybe a silly question, but have you already tried a Windows install with SETUP /p i ? I took a look on my own system, but for me its impossible to change settings in Direct memory access controller or System timer, disabling not possible. I am not sure about the first, but as far as I remember Watler told me during our lengthy conversations that some Timer is needed. This (maybe) can be tested with HDARUN.EXE. It must reside in your Windows directory. Included in my INF-File for testing purposes (HDARUN.EXE is ment for Win3.x in Standard Mode, in Enhanced Mode it's not needed). So enable Windows Startup Sound, set "Mytimer=0" in HDACFG.INI and reboot.. Next: try to enable "HDA Sound" as Audio Device in the way you described earlier, but stay in Windows, NO reboot. Then open HDARUN.EXE and click "Event On". If your System timer is the (only) culprit you will be surprised.

@Dave-H : The driver is definitely talking to your hardware since CODEC information is received from your hardware. But there is a difference between sending/ receiving Verbs through one of the two possible Verb-interfaces and starting/ sending a continues (PCM-) audio stream. In my opinion (but I may be mistaken) it can be related to the handling of the PCI-memory address on your system in relation to how your chipsets HD Audio Controller is programmed. The reset after reboot of the option in the dropdown menu to select playback devices you described earlier is what bothers me in this respect. Are you sure there is no conflict in the properties of your High Definition Audio Controller in Device Manager? Please deliver the memory address.

@Dave-H: MEM looks good, nothing special and Conventional memory only. Your HDACFG.INI gives codec information, so the driver can send/ receive some Verbs (through the HD Audio controller) to/ from your codec. For now I have following ideas: 1) to be sure, check in your bios if everything regarding HD Audio is enabled (not auto, if there is a choice). Your chipset should be somehow capable of ac'97 too. If you find something like that, please disable. 2) Set your VolumeWidget=$0C (according to alc883-datasheet). Don't think that will make any difference now, but try with a reboot. 3) Verbinterface=$0 is the easiest option, if not succesfull reset to $1 please.

@UCyborg: I virtually do not know anything about VirtualBox, but I am deeply impressed that the Win3.x-16 bit driver connects to your somehow virtual HD Audio. Thanks for testing, I am happy too that my INF-file and my version of Watler's HDAICOUT.HDA are working as intended! Choppy audio with this driver can be an IRQ-issue (is told me). So try to change the IRQ from the "High Definition Audio Controller" to a free one, if that's a simple configuration issue. About your question regarding the volume setting: WAVEOUT.EXE needs the right VolumeWidget in HDACFG.INI. Mine is $02. You can found yours in the datasheet of your (virtual) codec. Volume can be written manually in HDACFG.INI, is set after reboot ( needs the right VolumeWidget too). Use an application with volume control (not there in Win3.x as far is I know, works in Win9x only). HDA Sound (WaveOut) needs the right VolumeWidget too, DirectSound: HDA Sound (emulation) strange enough not. The picture will answer your last question.

Thanks. The memory address looks normal if using HDATSR. The ICH10 will be not your controller, but that does'nt matter. I will search for your HD Audio Controller and I will take a look in the source code. Will take some time. In the meantime you can search in your Windows directory for HDACFG.INI. If the file exists, please make a full copy in your reply. Further I will need a full MEM-report. Please open a Command-prompt and enter MEM /A /D > HDADAVEH.TXT Ad this - much bigger - file as an attachment.

@Dave-H Sorry, I didn't ment the section "Sound, video and game controllers" in Device Manager. I ment "Sounds and Audio Devices" / "Multimedia" as part of Control Panel (I googled for the right terms for English Win98). My original term "Multimedia properties" was good, it seems to me now So: Control Panel -> Sounds and Audio Devices OR Multimedia -> (gives) Multimedia properties -> Devices -> (gives) Multimedia Drivers -> Audio Devices.

@UCyborg Nice that the driver is working in VirtualBox, I have only tested on real hardware. I do not think you have to use HDA. Please can you upload a picture of your "Multimedia properties"? About using this driver in Windows 95: did you install a PCI-bus? Volume control can be done in a number of ways. Do you need some advice? I can try to help if you like

Yes, there MUST be an entrance in that section. Maybe the HD Audio Controller of your chipset is not supported by HDA2.DLL. Please give me the VEN/DEV-ID, search in Registry -> HKLM -> ENUM (or use Device Manager of WIN10/XP). BTW this has nothing to do with the ID of your codec.

Fine, no problems with my INF-file or virtual memory (not the size of the swapfile matters, but Paging must be enabled as far as I know). But maybe wavehda=hda2.dll is not good on your system, rename to wave1=hda2.dll and reboot. Another option, give (your) full path: wave1=C:\WIN-98\SYSTEM\HDA2.DLL (I have never tried this driver with other WinDir).

Yes, its "Sound, video and game controllers" It's "Sounds and Audio Devices" / "Multimedia" as part of Control Panel" (I am using a Dutch version). "TSR loaded" is a good sign for HDATSR, but it seems that HDA2.DLL is not loaded. Please check if its in your System directory, maybe it was not correctly renamed by Windows Setup. Further: what is in the [Drivers] section of your SYSTEM.INI? Last: is Virtual Memory enabled (Swapfile)?

The driver is inside SYSTEM.INI and will not be shown in Device Manager. If HDA2.DLL is loaded, there will be a HDA-entry in "Sounds and Audio Devices" / "Multimedia" (as part of Control Panel). 1) Can you see that HDA-entry? Please write down the memory address in Properties. Do NOT change it. 2) Did you hear a soft plopping sound during startup? Best use earphones. This is crucial information! 3) Did you reboot after copying HDAICOUT.HDA to your Windows directory? 4) Is HDATSR loaded? Check with MEM /A /C /P after booting into MS-DOS only (command-prompt with processing of MS-DOS configuration files, mostly number 5. of startup options). The HDAICOUT.HDA I posted is a sort of experimental 'general one', but can be modified for individual codec's, which will take some time seeking and reading documentation.