deomsh

The Win3x HDA-driver is working nice in my WIN98se system, even better than under Windows 3.1 (playback only). You can find the driver here: http://turkeys4me.byethost4.com/programs/ You can install the driver manually, or you can use following INF-file I wrote for easy testing. The INF-file has following functions (quasi Plug&Play): 1. Recognizing a PCI-Card with yellow exclamation-mark in Device Manager as a HDA-controller and name it as such. 2. Copy four files from the folder "HDAFILES" to their respective directories. 3. Write strings for HDA2.DLL and HDATSR.EXE in SYSTEM.INI/AUTOEXEC.BAT. I added an uninstall-string to remove everything related tot this driver. The System Device "High Definition Audio Controller" is not affected by uninstall, it has to be deleted manually in Device Manager (if one prefer the PCI-card with yellow exclamation-mark, but can be left to give information about this specific device). ----------------------------------------------------- GENHDA16.INF ---------------------------------------------------- ;; GENHDA16.INF ;; 2018/03/26 ;; "Watlers World" 16-bit High Definition Audio Driver ;; INF-file Win9x only ;; (c) Copyright 2018 [Version] Signature=$CHICAGO$ Class=System ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318} Provider=%W_W% DriverVer=12/23/2017,9j [Manufacturer] %GEN%=GEN.Mfg [GEN.Mfg] %GEN_HDA.DeviceDesc%=HDA2,PCI\CC_0403 [HDA2] DelFiles=HDA2.DelFiles CopyFiles=HDA2DLL.CopyFiles,HDAHLP.CopyFiles,HDA2Inf.CopyFiles UpdateInis=HDA2.UpdateInis UpdateAutoBat=HDA.UpdateAutoBat AddReg=HDA2.AddReg Reboot [SourceDisksNames] 1="HDAFILES",,0 [SourceDisksFiles] hda2.dll=1 hdarun.exe=1 hdatsr.exe=1 genhda16.inf=1 [DestinationDirs] HDA2DLL.CopyFiles=11 HDAHLP.CopyFiles=25 HDA2Inf.CopyFiles=17 HDA2DLL.DelFiles=11 HDAHLP.DelFiles=25 HDA2Inf.DelFiles=17 WATLERInf.DelFiles=17,Other [HDA2.DelFiles] drvidx.bin,,,1 drvdata.bin,,,1 [HDA2DLL.CopyFiles] hda2.dll,,,1 ;;hda2.dll,hda2.dll,hda2.000,1 [HDAHLP.CopyFiles] hdarun.exe,,,1 hdatsr.exe,,,1 [HDA2Inf.CopyFiles] genhda16.inf,,,1 [HDA2.UpdateInis] system.ini,drivers,"wavehda=*",,0 ; deletes existing system.ini,drivers,,"wavehda=hda2.dll",1 ; adds new [HDA.UpdateAutoBat] CmdDelete=HDATSR ; deletes existing CmdAdd=HDATSR.EXE ; adds new [HDA2.AddReg] HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\High Definition Audio 16-bit" HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\High Definition Audio 16-bit",DisplayName,,"High Definition Audio 16-bit" HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\High Definition Audio 16-bit",UninstallString,,"rundll.exe %11%\setupx.dll,InstallHinfSection HDA2.Remove 132 %17%\genhda16.inf" [HDA2.Remove] DelFiles=HDA2DLL.DelFiles,HDAHLP.DelFiles,HDA2Inf.DelFiles,WATLERInf.DelFiles UpdateInis=HDA2.DelInis UpdateAutoBat=HDA.DelAutoBat DelReg=HDA2.DelReg [HDA2DLL.DelFiles] hda2.dll,,,1 ; deleted after reboot [HDAHLP.DelFiles] hdarun.exe hdatsr.exe hdacfg.ini,,,1 ; deleted after reboot hdalog.txt [HDA2Inf.DelFiles] genhda16.inf,,,1 ; deleted after reboot genhda16.pnf [WATLERInf.DelFiles] WATLER~1.INF [HDA2.DelInis] system.ini,drivers,"wavehda=*",,0 ; delete [HDA.DelAutoBat] CmdDelete=HDATSR ; delete [HDA2.DelReg] HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\High Definition Audio 16-bit" [Strings] ;Localized strings W_W = "Watlers_World" GEN = "GENERIC" GEN_HDA.DeviceDesc = "High Definition Audio Controller" SystemClassName = "System Devices" ; ENG ;;SystemClassName = "Systeemapparaten" ; DUT ----------------------------------------------------- By trial and error I found a new 'class' of wave devices accepted by the Drivers-section of SYSTEM.INI, the so called "wavehda"-devices, so other wave-devices remain untouched. Installation: 1) Place the four Sourcedisk files in a directory named "HDAFILES". 2) Go to Device Manager and try reinstalling yellow exclamation marks, mostly named "PCI-Card", by pointing to GENHDA.INF, or delete PCI-Cards and do the installation after reboot while Windows is detecting new hardware. If you hear a plopping noise during startup, the driver is connecting to your codec. If you don't hear the Window s Startup Sound, you have to place HDAICOUT.HDA in your Windows directory. The problem is that the "Widgets" (programmable function blocks) in the codec have default values. HDA2.DLL does not change these values (except a few). This can be done with the textfile HDAICOUT.HDA. If the file exist, HDA2.DLL sent the so called "Verbs" in this file to the addressed Widgets and change values at start-up. Try the one below. Worked for me in case of three different codecs (digital playback only). Copy the file to your Windows-directory and reboot. BTW in case of stability problems set MinFileCache=8192 & MaxFileCache=8192 (or both lower). Latest versions of HDAICOUT.HDA: https://msfn.org/board/topic/178295-audio-driver-for-realtek-hd-audio-hardware/?page=10&tab=comments#comment-1163305

@bz07 I do not understand why you want to disable IRQ-steering. As far I as I know, your BIOS will take over and you will loose all control, according what I have red in your laptop's manual about your BIOS Setup. If you want to continue with Audio, better forget all other devices for the time being. You can disable Communication and set the IDE-controller with exclamation mark to "None". Further I suggest temporarily disable following PCI-devices: Video, all USB and Ethernet. Maybe this gives you a free IRQ you can feed to your Audio (but tot be honest I am afraid this will not be the case). If you'r lucky, do not use IRQ9 if you have a choice.

Thanks, but Uxteme version you mentioned doesn't export Ordinal 61, so no need tot try.

Thanks for your info. In my opinion you must get rid of all Acpi-devices, and have to wait with installing USB/Ethernet/Audio devices until IRQ-problems are solved. As a starter I would suggest following steps. 1) Reboot in Safe mode. 2) rename ALL inf-files newer then the one's of your OS. Latest Viamach.inf to Viamach.inf.new, others to xxxx.inf.old. 3) Rename ALL xxxxx.pnf files to xxxx.pnf.old. 4) In Device Manager delete following devices: all IRQ-holders, both types alike; all USB/Ethernet/Audio devices; and - if still there - ACPI-Bios. 5) Reboot and reinstall your OS with SETUP /p i (watch the space between p and i). 6) During install, say always OK when asked, NEVER point to a driver-directory in this stage. As a result I expect you should have a few yellow exclamation marks in your Device Manager. After this I think it's better to report first, same type of pictures please.

Did you copy the DriverVer of Viamach.inf like I said?

No problem. Your chipset-driver is old, my idea is first to try the last 9x one: DriverVer=6.0.00.0300. It's inside Via_HyperionPro_524A.zip. You find it on http://download.viatech.com/en/support/driversSelect.jsp > Windows > ME > chipset. Rename your existing Viamach.inf to Viamach.inf.old. Open the zip, go to VIAMACH\DRIVER\WinMe\ and extract the new Viamach.inf. Copy the file to the folder where you found the old Viamach.inf and reboot. If there is still no IRQ for Audio, then go to DeviceManager > Computer > Properties and upload pictures from ALL used IRQ's (three pictures will be needed!). Also one picture for PCI-Bus, tab IRQ-steering please (to see if it's the same as your earlier one).

I tested all 31 ROS versions, also an Uxtheme version I downloaded long ago, found on my hard drive. Now I know that's your version. There are no real differences in drawing added toolbars (Toolbar.BMP) in MPC-HC 1.7.5, resizing buttons, or draw buttons that are currently not active. All NOT possible. Just for fun I took Uxtheme (6.00.2900.5512 (xpsp.080413-2105) from my XPSP3 installation, can be used, same results (asks for three other stubs). I can confirm that with your Uxtheme version MPC-HC 1.7.5 is starting without problems (and MPC-BE 1.4.3.5854 too).

The IRQ should be there first in my opinion. What's the DriverVer of your Viamach.inf?

@jumper My post of Februari 17 was'nt fully accurate. The API's I reported were in fact called by the Uxtheme.dll-version (ReactOS 0.4.3) I started to use after the app I mentioned called Ordinal 61 in Uxtheme. In the meantime I tested all ReactOS versions I could find; from 0.3.8 (first one) up to latest 0.4.11. Here is a list I made with ImportPatcher and Kexports, higher versions needed more stubs to load. Only one stub needed a return-value. IMPORTPATCHER (KernelEx mode VISTA) [Patches needed] Uxtheme.dll=Functions [GDI32.dll] ;SetDCPenColor= ; ROS 0.3.14 - covered since KernelEx 4.5.2 [Ntdll.dll] RtlAllocateHandle= ; ROS 0.4.6 - RtlFreeHandle= ; ROS 0.4.6 - RtlInitializeHandleTable=z1 ; ROS 0.4.6 - "set last error -1" z1 seems to work RtlIsValidHandle= ; ROS 0.4.6 - RtlRaiseException= ; ROS 0.4.11 - ;_vsnprintf=> ; ROS 0.3.3 - covered since KernelEx 4.5.2015.6 ;bsearch=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;DbgPrintExWithPrefix=t5 ; ROS 0.3.7 - covered since KernelEx 4.5.2015.4 ;memcmp=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;memcpy=> ; ROS 0.2.8 - covered since KernelEx 4.5.2015.6 ;memmove=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;memset=> ; ROS 0.2.8 - covered since KernelEx 4.5.2015.6 ;sprintf=> ; ROS 0.2.8 - covered since KernelEx 4.5.2015.6 ;sscanf=> ; ROS 0.2.8 - covered since KernelEx 4.5.2015.6 ;strchr=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;strcmp=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;strcpy=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;strcspn=> ; ROS 0.3.4 - covered since KernelEx 4.5.2015.6 ;wcschr=> ; ROS 0.2.8 - covered since KernelEx 4.5.2015.6 [user32.dll] KillSystemTimer= ; ROS 0.3.14 - PaintMenuBar= ; ROS 0.4.5 - SetSystemTimer= ; ROS 0.3.14 - UnregisterUserApiHook= ; ROS 0.3.14 - BTW: I didn't test the one's already covered by KernelEx.

@bz07 In the past I used a P4M800 board, Asus P5vd2-nvm. To find drivers for Windows 9x was a big problem, but finally I succeeded with AC'97 driver (ver:A4.00) from Biostar 8267R: alc850_6240.exe Your VEN/DEV is inside the WDM-inf's as far as I can see in my driver archive (major version only, no SUBSYS/REVisions). It's still available for download (you have to search the link with Google...). You can try if you like BTW: better do not use the setup, but unpack the exe with 7-zip and point during Windows's driver install directly to the WDM folder .

Somehow I succeeded with roytam1's manifest as a text-file, renamed to GetVersion.exe.manifest My earlier reported Windows 10 (x86) gives now: gv=0x42EE000A gvex=A,0,42EE,2,,0,0,100,1,0 And Windows 8.1 (64 bit): gv=0x25800306 gvex=6,3,2580,2,,0,0,300,1,0

Windows 7 Ultimate (x86) gv=0x1DB10106 gvex=6,1,1DB1,2,Service Pack 1,1,0,100,1,1E So last character of gvex is different. Regarding testing Windows 8.1: I'd like to help, but my programming skills are rather low. Maybe you can update Getversion or give some instructions? I don't know what to do with information here: https://docs.microsoft.com/en-us/windows/desktop/sysinfo/targeting-your-application-at-windows-8-1

My Windows 10 Pro was a (free) upgrade to Windows 7 Ultimate, years ago. Thats all I know. Today I tested a computer with Microsoft Windows 8.1 Pro (64 bit, sorry no x86 available): gv=0x23F00206 gvex=6,2,23F0,2,,0,0,100,1,0 BTW: my XPSP3 (x86) gave exactly the same values as IntMD's According to this document the return values for Windows 10/8.1 can be (should be?) the same as 8.0's: https://docs.microsoft.com/en-us/windows/desktop/sysinfo/operating-system-version

Here the GetVersion results for Windows 10 Pro version 10.0.17143 Build 17143 (or: Version1803 OS build 171430.590). gv=0x23F00206 gvex=6,2,23F0,2,,0,0,100,1,0</tt>

There are no definitions being used in kexstubs.log, except one Shlwapi-forward I need on my (almost) vanilla Win98SE installation: StrCmpLogicalW=>C:\Windows\Kernelex\W98\Shlwapi.IE6: ; MPC-HC 1.7.5 & MPC-BE 1.3.03; -> Shlwapi 6.0.2800.2006

Off Topic

Maybe here? https://web.archive.org/web/20170826223448/http://www.msfn.org/board/topic/175486-wpa2-for-windows-9x/

MPC-HC 1.7.5 is running with Kernelex 4.5.2016.18 and following stub: [User32.dll] KillSystemTimer= SetSystemTimer= UnregisterUserApiHook=

Last version of FFDShow (v1.3.4533.0 / ffdshow_rev4533_20140929_clsid.exe, ) is working fine, I am using Kernelex 4.5.2016.18 (Kernelex.dll v17; without Kstubs). Installer needs a NT compatibility mode, I used XPSP2. All four (!) configure-shortcuts are not working. By trial and error I found following workaround by editing "Target" in the shortcuts. Later I found that this workaround was reported already in June 2006 on MSFN, so the problem is much older than KernelEx. See also Drugwash (2013) and Loblo (2011). Schwups (2013) tried updating Rundll32.exe. C:\WINDOWS\RUNDLL32.EXE ffdshow.ax,configureAudio C:\WINDOWS\RUNDLL32.EXE ffdshow.ax,configure C:\WINDOWS\RUNDLL32.EXE C:\WINDOWS\SYSTEM\ff_vfw.dll,configureVFW C:\WINDOWS\RUNDLL32.EXE ffdshow.ax,configureDXVA All configure panels seems to be fine, but I didn't test VFW and DXVA. About Rundll32.exe: I used the original 4.10.1998 version.

@Goodmaneuver: I ment Jumpers KEX versions, 4.5.2015.3 and 6. I took a closer look at my LFN and it appears that the culprit was the use of the character " ï " (in Dutch normal). After changing to " i ", installation of LAV Filters 0.70.2 started as usual (but NOT in XP2 mode, only Windows 2003 SP1 or higher on my system). So the problem is different. Maybe we should discuss your problems with LAV Filters elsewhere.

@Goodmaneuver: About LAV Filters 0.70.2 there are two path-related problems. I hope this is still on-topic. First is that the installer (compat. mode minimum Windows 2003 SP1!) seems to work only from a folder without certain characters. Second: configuring LAV Filters without running a media file is possible after rewriting the shortcuts. Strip the path to the wanted LAV Filter in "Target". The full path is already in "Start in", In case of "LAV Audio Configuration" "Target" must become "C:\WINDOWS\rundll32.exe LAVAudio.ax,OpenConfiguration" and so on for the others (without qoutes!). This trick works for (latest) FFDShow configuration shortcuts too. On my system changes are correctly stored in the registry, no problems at all. "Enable system tray icon" is not working. I tried all KEX-versions i have, only 03 and 06 are missing - am not sure if they were ever published. All my versions are working on my new Almost-Vanilla installation, except 11 and 11a. Without KStubs LAV Filters are supported in 4.5.2016 and higher.

@jumper: about REGSVR32.EXE, I am not sure if relevant anymore, but here some details. Registering LAV Filters 0.70.2 (last XP version) with MSVCRT=MSVCR70.DLL in KnownDlls (linking three needed API's with Kstubs822 is not working: "_aligned_free", "_aligned_alloc" and "_aligned_malloc"). Other compatibility mode on REGSVR32 was only needed in case of using Total Commander's command-line. With "Run" or in Dosbox "Default" was good enough, I found out later. A bit strange was that "BASE" did the trick already in case of Total Commander's command-line (didn't try earlier). Is there a difference in KernelEx 4.5.2018 between "Use default compatibility options (KernelEx is enabled)" and "Use specific compatibility mode: Base enhancements (Api fixes + extentsions)", other than enabling "Advanced options" choices? After a full Windows 98SE reinstall, as Vanilla as possible (some DLL's only updated by DirectX9.0c, NUSB3.3, and Windows Installer 2.0 - NO Unofficial Servicepacks, NO new IE-version), "Default Compatibility Mode" was ALWAYS enough. Using the official LAV Filters 0.70.2 Installer ("Windows 2003 SP1 Compatibility Mode" minimum needed!) registering during installation already succeeded. Only remaining "thing" is that registering LAV Filters AX-files was NEVER possible with KernelEx "Disabled" for REGSVR32 (GetLastError 0x0000001F), different from all other media-files I tried.

I meant reinstalling the driver(s).

No. Files are not moved from Windows to System, as far as I know. Better try to reinstall again and again. Check your installation first with Run > SFC.