deomsh

I have only experience on Windows 3.1 (so NOT WFW 3.11). Browsers: best is Netscape 4.03 or 4.04, using a proxy server or a webproxy. Without: Netscape 3.04. Watch a-synchronous DNS. More details here (go to page 2): https://web.archive.org/web/20180329130629/http://win3x.conforums.com/index.cgi?board=net&action=display&num=1517876379

Can't help you as such, but just for the record: did you install DirectX 9.0c (win9x version)?

All right, if you are fine with your speakers, than stay with HDAICOUT.HDA.000 Apparently your laptop uses other Pin(output)Widgets than I selected: 0B, 0E (with HP-amp) and 10 (mono-out). To find the right ones will need quite lengthy experimentation using Get-commands...

All right, lets try this version of a tailor-made HDAICOUT.HDA first. Following steps: 1) Rename current working HDAICOUT.HDA to HDAICOUT.OK1 2) Rename new version and reboot, check if everything is working as before (VolumeWidget=$13 !). 3) Set VolumeWidget=$1C in HDACFG.INI and test if WAVEOUT.EXE is ruling speaker-volume only. Hdaicout.hda.Dell_Latitude_6430u

Good, so you can use this instead of WAVEOUT.EXE. Are you interested in my idea to redirect the speaker signal line to the Mixer_1C, so you can use WAVEOUT.EXE to rule the speaker-volume independent from your headphone?

Fine. There is no hurry, take all the time you need. Next: if you play an audio-file in MediaPlayer, is the volume slider of the player working?

That's good to know, if I am right this means Mixer_1C is not in the playback signal path. Sad, but is reported earlier. No driver is needed! Direct Sound is part of DirectX. Check with Start > Run > Dxdiag which version is installed. Best is DirectX 9.0c (Win98SE compatible version). If I am right MPlayer uses DirectSound by default. In some players you can choose output device, in case of HDA2.DLL you should choose DirectSound: HDA Sound (title is set by the driver!). Maybe possible in MultiMediaDevices too (option for Playback).

Great. If you read carefully the link I provided, you will see WAVEOUT.EXE is not always needed, except for System Sounds (but these can be disabled) and Soundplayer (don't remember the exact name). The trick is to use the volume slider of your player, if the player can be set to DirectSound: HDA Sound (or if the player uses this setting already by default). Is VolumeWidget=$1C working too? I ask because I have an idea to let WAVEOUT.EXE rule your speaker volume, while your headphones will get maximal volume, modified by the volume slider of a player/ and or the physical volume slider on the headphone (if your headphone has any). BTW how behaves the sound switches on your keyboard?

Thanks. Let's first try to fix WAVEOUT.EXE. According to the data-sheet, WDGET-diagram on page 50, there are three volume-widgets in the playback path. For DAC0 widget 13, for DAC1 widget 14 and the mixer has widget 1C. WAVEOUT.EXE is dependent on the VolumeWidget setting in HDACFG.INI. Default is $14, so try first VolumeWidget=$13 and later VolumeWidget=$1C too. More information about volume & HDA2.DLL: https://msfn.org/board/topic/178295-audio-driver-for-realtek-hd-audio-hardware-testing-thread/?do=findComment&comment=1161770

Be aware copying can be slow with the vcache-solution. SMARTDRV.EXE can help, best is (in AUTOEXEC.BAT): SMARTDRV.EXE /X /L /V /B:57344 Did you try WAVEOUT.EXE already? Start > Run > WAVEOUT.EXE With help of your HDACFG.INI I found out your codec is IDT 92HD93, revision 100203. Can you search for the data-sheet so I can take a look... BTW Do not upload because of copyright, just the web-address (mostly '.pdf'}

Thanks a lot! About the jittery/halt: did you already try higher values of MinTimeSlice? Default is '20', (my experimental) max is '100'. So try 'max' first in SYSTEM.INI, [386Enh] MinTimeSlice=100

So, that's quick, congratulations Will you do me a favor and upload HDACFG.INI and HDAICIN.TXT, so I can see which HDA-Controler and which HDA-codec is used on your system and which responces the HDA-codec gives to my version of HDAICOUT.HDA (000)? BTW: are you still using version 'J' of HDA2.DLL? I just found out latest version is 'L'. I will test soon...

Which version of HDAICOUT.HDA did you use?

The instructions on Operating System Revival are correct for WinME only. In case of Win98SE use for manual installation (taken from Operating System Revival + corrections): Instructions (Windows 95/98): 1. Download Watlers' driver HDADRV9J.zip 2. Place HDA2.DLL in C:\WINDOWS\System 3. Make sure HDARSR.EXE HDATSR.EXE and WAVEOUT.EXE are accessible (place in "C:\WINDOWS\SYSTEM" for convenience) 5. Add line "HDATSR.EXE" to AUTOEXEC.BAT (without quotes) 6. Add to SYSTEM.INI,[Drivers] "WAVEHDA=HDA2.DLL" (without quotes) 7. Reboot If there is no sound, try my quasi-universal version of HDAICOUT.HDA (found in DaveH's tread) and place in C:\WINDOWS\SYSTEM and reboot. If there is sound but system is unstable try in SYSTEM.INI, [Vcache] MinFileCache=1024 MaxFileCache=1024 + you can speed-up your system by adding line "SMARTDRV.EXE" to AUTOEXEC.BAT (without quotes). Always reboot in between. If there is still no sound, ask @deomsh for further help (only if you are fully dedicated to a long project, and willing to follow instructions you probably will not understand).

Your source says: 'To warn Windows that you have more than 512MB of memory installed, add the following line to the [VCache] section of your win.ini file: MaxFileCache = 524288."' It should be system.ini. Also: did you try a static Vcache, setting MinFileCache and MaxFileCache to the same value? Best start with 1024 both, most stable setting available, but slowest. And with WinME you can't use SMARTDRIVE.EXE -limited to 128G(i)B partitions- to speed-up things (unless you make WinME real-mode aware).