deomsh

@SweetLow I cited Microsoft. Do you think their '2GB' is a mistake?

@jumper You are right, it's even lower than I remembered. On the other hand the article is stating too: 'Although the user interface is limited to 24 MB, the theoretical maximum size of the cache is actually 2GB.' However Q253912 stated: 'Vcache is limited internally to a maximum cache size of 800 MB.'

Now I think I understand you better. About the comment semi-colon: both ways should work. About 512 MB: I never said that for SYSTEM.INI, the MaxPhysPage=20000 was ment for SYSTEM.CB, so for Safe mode (setting MaxPhysPage in SYSTEM.CB is known as Usher's method - please correct me if I am wrong). About MaxFileCache=56320: this is the officially highest value tested by Micosoft and described in Q108079. MDGX mentions this value it too. My entries in MSBATCH.INF were not ment for running Windows 98 SE in general, but for during Setup. Which is the purpose of MSBATCH.INF

I do not understand, can you give an example? BTW there is some information about the ini-directive here: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/inf-updateinifields-directive Otherwise read 'Windows 98 Resource Kit', Appendix C.

I checked differences as far relevant for playback with HDA2.DLL: only differences concerning default mute/ unmute of Nodes. Unmute outputs is currently taken care of by my quasi-universal HDAICOUT.HDA up to node 1F. However: highest node number in AD1984 is 0x26. Unmute inputs is currently NOT taken care of by my quasi-universal HDAICOUT.HDA because of maximum number of verbs.

Nice. Thanks for reuploading the Linux codec info of AD1984. Now only needed for my 'administration': I want to make a quick comparison with the codec dump (found somewere on the internet) I used for the Thinkpad X61 of @sweaterfish . Good luck with your Thinkpad R61.

Help, your so fast So is everything good now?

Now the same surpassing of your codec at index $0. But no modem anymore, this time nothing: CODEC_VID=$0000 CODEC_DID=$0000 CODEC_REV=$000000 You can try with pcipatchB=$7900 in HDACFG.INI (you have an Intel ICH8 Family HDA-Controller Pci Id 8086:284B). Writing to PCI-registers is as always at your own risk, if any. You also can try changing wait-states in HDACFG.INI, set: wait1=$250 wait2=$250 or even higher. Watch HDALOG.TXT for changes and HDACFG.INI for populating CODEC_VID/DID. For now better wait with testing HDAICOUT.HDA, maybe rename extensions to .000 and 001 (in your Windows directory).

Nice to hear Watler's win3x HDA-driver is working with your Thinkpad Z60m. However for now I can not help you with your Thinkpad R61 (Type 7735). In HDACFG.INI your audio device is identified as 14F1:2BFA, this is a modem. HDALOG.TXT first found the HDA-device 11D4:1984 (should be AD1984), but switches (too fast?) to the second device. This is a known issue! You must *somehow* get rid of your modem. Search in this thread for modem, maybe helpful (maybe not).

Check this page: http://www.win3x.org/win3board/viewtopic.php?t=17965&start=7 for HDADRV9J. BTW archive-link provided by Watler is working, but downloading NOT (for me). Here you can download HDADRV9K: http://www.win3x.org/win3board/viewtopic.php?t=27321

On localized version of Windows, the Setup of Windows 98 will add lines for DISPLAY.SYS and COUNTRY to CONFIG.SYS, and lines for MODE and KEYB to AUTOEXEC.BAT (I have Dutch Windows 98FE and Windows 98SE CD-ROMS).

I never used batch.exe, I write my own msbatch.inf (with much help of all sources I can get). The updateinis-lines should be placed under the install-section (before [STRINGS] I guess). See https://leeos.epizy.com/infdoc.html?i=1#UpdateInisSections You can find it on the net, for instance mdgx.com is a reliable source. Simply start your search with site:www.mdgx.com and then what you want to know. EMMExclude will block Windows to use UMB's in the specified region. For instance the NVIDIA Geforce-drivers will block a (smaller) area. Most of the time I do not use UMB's. Usher's method is needed for Safe mode on computers with more than 1.xx GB of memory, just like in 'Normal mode'. However must be written to SYSTEM.CB. My section [Edit.Syscb] is FULLY undocumented, I wrote it by trial and error. You can't say this, unless you prove you can start Windows' Setup WITHOUT first loading HIMEM.SYS. However you can use MSBATCH.INF to write your own CONFIG.SYS and AUTOEXEC.BAT. About /NUMHANDLES=64: RLOEW mentioned them in his PATCHMEM-manual (above 2.75 GB memory).

Good However: your Setup-description not sound like a FULLY unattended setup. Better add following lines to your MSBATCH.INF: [Install] UpdateInis=Edit.Sysini,Edit.Syscb [Edit.Sysini] %10%\system.ini,386Enh,,"MaxPhysPage=40000" %10%\system.ini,386Enh,,"DMABufferSize=64" ; optional %10%\system.ini,vcache,,"MinFileCache=51200" ; Q108079 %10%\system.ini,vcache,,"MaxFileCache=56320" ; Q108079 %10%\system.ini,386Enh,,"MinSPs=8" ; optional %10%\system.ini,386Enh,,"MinTimeSlice=40" ; optional, multitasking slower but more stability ;;%10%\system.ini,386Enh,,"SystemROMBreakPoint=0" ;;%10%\system.ini,386Enh,,"EMMExclude=A000-FFFF" ;;%10%\system.ini,386Enh,,"MaxDMAPGAddress=1000" [Edit.Syscb] %10%\system.cb,Boot,,"*DisplayFallback=0" %10%\system.cb,386Enh,,"MaxPhysPage=20000" ; Usher's-method ;;Inf,Reg and BAT files need always a carriage Return on the end! BTW some WIN.COM-switches included for troubleshooting ('activate' one or more sysini-lines with semi-colons). With these lines in your MSBATCH.INF you should be able to use HIMEM.SYS during Setup (with switch /NUMHANDLES=64 OR /NUMHANDLES=128). If you want to use HIMEMX.EXE, change after Setup.

I have no idea, try Setup without the switch /nr - Setup should ask if you want to process existing Registry (if I remember well). Better backup first, if possible.

Search for MSBATCH.INF + use https://learn.microsoft.com/en-us/previous-versions//cc768165(v=technet.10)