deomsh

@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