deomsh

Hi @Drew Hoffman , didn't expect you in this thread.... I am aware of your project (I am reading MSFN daily). So far I had no time to test your driver, but your project looks promising, in case of Windows 98/ME. About your question: difficult to say. If you search in this thread for IDT, it seems there is one report, working with some quasi-universal version of HDAICOUT.HDA. But that's a while ago... I also 'did' one VIA codec (VT1708B) in this thread, additional verbs where needed in that case. But at home I did VT1705 on Asrock N68C-S UCC without. Somehow Realtek codecs have the 'easiest' architecture, I 'did' a few. ALC66x-ALC88x and ALC1220 have roughly the same nodes and same output pin's Apart from extra's in ALC88x. ALC231/ALC260 are already different. This is in my notes (ment for personal use): The lines in my quasi-universal version of HDAICOUT.HDA focus on a few nodes/ widgets for power up, open the playback path and to set the DAC and volume to default values. Because there are about max 200 verbs free for sending at once, and because in my approach HDAICOUT.HDA is used to sent same verb to 'all' nodes/ widgets, so type of verbs is limited. As such this quasi-universal approach is fully 'blind', no intelligence at all (hopefully some in the maker). All based on Intel's High Definition Audio Specification, NOT on specific Realtek codecs. In most of my versions of HDAICOUT.HDA I have concentrated on output's, but I had plans to make a new version to 'open' input-ampifiers too (mixers). But furthermore ignoring Connection Select will be the price to pay. So maybe you can play with '35xxx', '36xxx' or L+R combined: '37xxx', just an idea. From my notes: Set Amplifier Gain 3 Payload(s) Set Amplifier Gain 3 5 0 8 0 Mute Input Channel 0 R Set Amplifier Gain 3 5 0 0 0 UnMute Input Channel 0 R Set Amplifier Gain 3 5 0 7 F Max Input Volume Channel 0 R Set Amplifier Gain 3 6 0 8 0 Mute Input Channel 0 L Set Amplifier Gain 3 6 0 0 0 UnMute Input Channel 0 L Set Amplifier Gain 3 6 0 7 F Max Input Volume Channel 0 L Set Amplifier Gain 3 7 0 8 0 Mute Input Channel 0 R+L Set Amplifier Gain 3 7 0 0 0 UnMute Input Channel 0 R+L Set Amplifier Gain 3 7 0 7 F Max Input Volume Channel 0 R+L Set Amplifier Gain 3 7 1 7 F Max Input Volume Channel 1 R+L But in case of EAPD, Unsollicited Response and GPIO, things are different and often model-specific (laptops). In that case more information is needed. I only did a few codecs/ chipsets, always on a n=1 basis, with help of study of Linux (ALSA)-sources to find appropiate verbs. However you have a parser, should make things more easy (Watler delivers a seperate parser too in version L, but his driver does not use a parser as such). I am willing to help, but I am not a programmer, just an ordinary Joe with more spare time because I am not interested in sports (no offence to readers of this thread ment of course).

Hello @space223 , can't say, there are no records of this codec with HDA2.DLL. Did you try already?

Please give more exact and accurate information! I use Office 2003 with Windows 10 x64, no problems with Compatibility pack. But this Compatibility pack can not open all docx-files (more specs are *somewhere* on the Internet). For now I made you a test file in Word, saved as docx with Compatibility pack. Feel free to try. Test file for Compatibility pack.docx

You are right, I checked again - this time on Windows 98SE. Only http is working with Google on Retrozilla, but Advanced Search and Cookie-dialogs not. Kameleon 9x same results. Both without KernelEx.

Are you sure it is not something else? Retrozilla (default settings) is still working for me with Google on Windows 95 OSR2. BTW tab with Google: only title is showed.

Sounds difficult. But I can take a look if you are doing something 'wrong'. Please upload followowing files (if available): HDALOG.TXT, HDACFG.INI and SYSTEM.INI (from your Windows directory), CONFIG.SYS and AUTOEXEC.BAT (from your C-drive).

@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).