deomsh

About HDA2.DLL in Windows ME: the TSR needed will not load from AUTOEXEC.BAT. Native Windows ME can't load real mode drivers that way. You will have to edit HDACFG.INI manually.

@~♥Aiko♥Chan♥~: You have to download "High Definition Audio Sound Driver 9". Late EDIT (on behalve of Copilot GPT-4 too): 1) HDARSR.EXE does not exist for HDA2.DLL, should be HDATSR.EXE 2) only HDA2.DLL should be placed in the SYSTEM-directory, other files should be placed in the WINDOWS-directory (HDATSR.EXE, WAVEOUT.EXE and if needed HDAICOUT.HDA)!

You need to download HDADRV9J.ZIP. The driver, HDA2.DLL must be placed in %windir%\system. HDATSR.EXE and WAVEOUT.EXE can be placed anywhere, but %windir% is convenient. In case of HDAICOUT.HDA, %windir% is mandatory. In latest VBox 6 the driver gives good sound with Windows 3.1, crackles only if moving the mouse, but that's normal behaviour for this OS. In Windows 98se the behaviour of the driver is normally BETTER than in Windows 3.1, but in VBox much WORSE! I am still testing in VBox 6. Sound ist *somehow* better with DirectX 9.0c and extreme low MinFileCache/MaxFileCache settings, but still crackling. So far I found following workaround in VBox: set MinTimeSlice=100 (100 !!) in SYSTEM.INI [386Enh]. Playing a MP3 in Media Player is not bad with this setting. BTW: In VBox all Widget´s in HDACFG.INI must be set to $03, as @UCyborg found out (SleepingWidget, PowerWidget and OutputWidget). HDAICOUT.HDA is not necessary, but I found out that an empty file speeds up the first playback considerably. ------------------- HDAICOUT.HDA ------------------- Begin End ------------------- BTW2: In VBox Windows 3.1 must be installed WITHOUT any System Acceleration. Windows 98se needs ALL System Acceleration enabled.

@tyukok: the error indicates a typo. Are you sure you didn't type $OC instead of $0C ? If you found a decent soundcard, there is no reason to continue, unless you like further experiments. But that's up to you. Using HDA2.DLL is not always easy and there is no garanteed succes.

@tyukok: I analyzed your latest files, all values are at least possible. Apart from setting VolumeWidget=$0C in HDACFG.INI and trying ALL jacks with Headphones I can´t suggest anything more at the moment (ALL jacks are set as Output Pin´s in playback mode by the "universal" version of HDAICOUT.HDA). There must be written a HDAICOUT.HDA for codec ALC1220, now its maybe worthwhile to spend time needed. Problem is your codec is a Realtek High-End codec WITHOUT data sheet available. So I have to try to reconstruct the codec from Linux and AppleHDA sources. Although I took already a first look, it doesn´t look as an easy task and will take some time.

@Dave-H: I am not aware of drawbacks for the 16-bit HDA driver. But HDATSR will cost you: about 9Kb Conventional memory, and a part of your memory area above 1Mb. If there is no room left in the first Mb's because of certain MS-DOS programs using that memory too, the Busmaster addresses used hy HDATSR will shift to higher addresses, risking being overwritten by Windows. That's all I think I can say about this subject. The experiments I described in my thread "Smartdrive Revisited" suggests this can already be a problem in case of SMARTDRV with a cache of 4096 (=4Mb), in combination with HDATSR. But there are centainly members that can give a more conclusive explanation than I am capable of.

@Dave-H: without HDATSR should be possible by means of limiting Windows' memory to a few Megabyte's less, and set the [BUSMASTER] addresses there in HDACFG.INI

@tyukok: About HDATSR and available memory, it's true you can do without HDATSR, but in that case you must set manually [BUSMASTER] memory addresses in HDACFG.INI that are "out of the reach of Windows". Since this is not the problem here, I'd like to see your latest HDACFG.INI, HDALOG.TXT, and since you're using HDAICOUT.HDA too HDAICIN.TXT.

@tyukok: Big progress. HDALOG.TXT looks much better. Also movenent of the slider when playing sound is good, means the driver is pumping digital sound to the HD-audio link. But this time there is a basic problem. "TSR=TSR not found" in your new versions of HDACFG.INI wasn't there in your first upload, so no DMA buffer anymore. The digital sound can not get to the buffer. Please check your AUTOEXEC.BAT for a HDATSR line.

@tyukok: Interesting, but the communication with and "setting" of the codec is still not good. But the driver got at least the right codec id: $000F0000=$10EC1220 means the codec answers the GET Verb $000F0000 with ($)10EC1220, which means Realtek 1220! In HDACFG.INI you should find CODEC_VID=$10EC and CODEC_DID=$1220. What actual value has CODEC Index= there?

@tyukok: No problem, there is no hurry. The OS is already retired. Sad the other Verb interface did nothing. There are not many options left to try. You can play a bit with the wait-timings in HDACFG.INI, although I am afraid the driver is not compatible with your HDA-controller. Reset to Verbinterface=$1 Normal values are: wait1=$100 wait2=$100 Try higher values, like wait1=$200 and wait2=$200 or even wait1=$500 and wait2=$500 BTW: I could'nt find anything useful about the controller, nor in linux sources, nor in the data sheet of your chipset (only power saving issues).

@tyukok: Disabled is the default, I asked just to be sure. If you like to continue: next step I suggest would be a different Verb interface. Set Verbinterface=$0 in HDACFG.INI and reboot. Please check if there is any difference in HDALOG.TXT, if there is any difference attach the file.

@tyukok: Nice board. Are all Power Management options disabled? See Page 2-7 of the User manual.

@tyukok: Thanks for the file. Look no good, the codec readout is'nt as it should be. All I can do is take a look at your system. I need full specs (motherboard, including Revision; in case of a laptop full model name). Further: are you using WIN98se?

@tyukok: The id is the HDA controller. But nevermind, I will search for the ALC1220 data sheet. Did you hear absolutely nothing during boot? Please attach latest HDALOG.TXT

@Dave-H: Yes, but situation is different now. At the time I was an active member of Watler's Win3x forum, I asked him if he could gave me room for Win9x experiments. Although he was a bit sceptic, he gave me room and even tried and criticized my INF-file. I made a statement about on MSFN only. But since a year ago the forum ended, so new opportunities for MSFN.

@tyukok: My INF-file doesn't make an entrance in Device Manager -> Multimedia, only in System Devices, (according to Windows conventions for HDA controllers). Your CODEC_VID=$14F1 CODEC_DID=$2BFA in HDACFG.INI doesn't look to me as ALC1220. Since you have CODEC Index=$1 in HDACFG.INI, I would suggest trying HDAICOUT.HDA.100 first (file in previous post). Rename to HDAICOUT.HDA, copy to your Windows directory and reboot.

@Dave-H: Good to here your system is stable with the 16-bits HDA driver. I still have no definitive opinion regarding stability issues, but I will do thourough testing with Virtualbox, no real risks involved (thanks to UCyborg)... Working with an unknown system was stimulating, especially with such a careful tester. Gave me some new insights and idea's too. As a sort of spinoff from this project I made three quasi-universal versions of HDAICOUT.HDA. Instructions which one to choose inside. Especially useful if there is the Sound of Silence after installation of the driver. Hdaicout.hda.000 Hdaicout.hda.100 Hdaicout.hda.200

@hfuria: Please search with Google the full filename "DP_w98_1.01.exe" (including quotationmarks), etc.

@UCyborg: I managed to install Win98se in VirtualBox 5.2.6 r120293 (I have 32 bits Windows 10 as a Host). OutputWidget=$03 is working for me too. Volume slider in Media Player functions. Sound is really bad with HDA, but almost acceptible with HDARUN. If you like to try, set Mytimer=0 in HDACFG.INI. After reboot: Run -> HDARUN. Don't forget to click the LOOP button before playing sound. Afterwards first stop the sound, then click LOOP again before shutting down HDARUN. Extreme low Vcache settings are helpfull against clicking noise in the background, but multitasking is not an option.

@Dave-H: If you can live with your erratic Sound Mapper we're done. Enyoy the Sound! BTW: be aware of possible stability issues I mentioned in one of my post's of April, 11

@UCyborg: Great! But if Volume Widget=$03, than your sound is coming from DAC1, connected to Pin Widget 0C. If sound is still bad, you can try with OutputWidget=$03 in your HDACFG.INI, although HDAICOUT.HDA should have configured this Widget already.

@Dave-H: Nice that Line1 is working. According to your Motherboard manual Line2 is for the HDA front panel (page 2-23). Can probably made working too. @farfigs11: Thanks for the files! The STAC9200 data sheet mentioned node 0B as Master Volume. Verbs are Standard. Try VolumeWidget=$0B in HDACFG.INI. But are you sure about your codec? HDACFG.INI indicates a different one. BTW According your HDACFG.INI I don't think your system will accept my version of the "universal" HDAICOUT.HDA. But since you have sound you should try without.

@UCyborg: The XML-file won't open, there is some error dialog in my program (Windows 10). But I compared your codec graph with the Widget Diagrams in the data sheet, All Widgets seem to match. I can't see how VirtualBox will connect output's from Pin Widgets to your Host's (physical) Audio, but there are four possibilities according to the data sheet. In the mean time I found out that the Volume Knob needs Verbs different of VolumeWidget one's, so a Volume Knob will probably not work with VolumeWidget setting in HDACFG.INI. All I can suggest is trying one of the four Output-connected DAC's, they all have a Volume/Mute function. You can try VolumeWidget=$02 / VolumeWidget=$03 / VolumeWidget=$04 or VolumeWidget=$05. Always reboot inbetween.

@Dave-H: Hereby version 202. If you want an Analog Audio input: enabling last line is mandatory. Further: you can choose out of five channels. I guess you have to enable Line2. Instructions are included in the file. Dave-H_ALC883_Hdaicout.hda.202 @farfigs11: Thanks for testing, nice that minfilecache=8192 and maxfilecache=8192 worked for you. If you attach HDACFG.INI and HDALOG.TXT I can take a look at your basic settings.