Dietmar

@K4sum1 You can use this hacked acpi.sys for DDB on any compi for XP SP2 bit64. The hack just makes sure, that if a device in DDB is not correct recogniced, the compi still boots XP SP2 to desktop, ignoring this device. When there is no problem with DDB on you compi, this acpi.sys works to 100% as an normal acpi.sys without this hack Dietmar

@George King Yepp, this intelppm.sys for XP SP3 from you is exact what I miss. This your file you have to modd via this, which gives the intelppm.sys which I offer in post above Dietmar 1. F:\intelppmModModXPSP3ENUUSA\intelppmModModXPSP3\intelppm.sys: 36.352 Bytes 2. F:\INTELPPMenglOri\intelppmKing.sys: 36.352 Bytes Offsets: hexadez. 128: C8 94 129: A6 C8 3F76: 50 28 3F77: 21 20 3FCA: 50 74 3FCB: 21 1F 5091: 50 74 5132: 50 20 5133: 21 22

@George King Yepp, this is not the complete hack for intelppm.sys. Can you send me your file intelppm.sys, I think it is USA language version XP SP3 Dietmar

@George King I think, that this is the correct modded intelppm.sys for XP SP3, for to bring power consumption down as much as possible, thanks to @pappyN4 Dietmar intelppm.sys for XP SP3 https://ufile.io/sjr0z6sw

@George King What is the latest intelppm.sys ENU, USA version for XP SP3 that you have? I think, we make a small mistake in power consumption hack for this. @pappyN4 brings me to this idea Dietmar

Hi, 3DMark2001 is not running on Windows Server 2003 bit 32. On both versions, Standard and Datacenter. As far as I can check, everything else runs. Crazy, for sound I have to install Microsoft UAA device driver for 2003 and enable sound in Directx and in Services. Directx 9c is installed, graphikcard GT 730 works , dxdiag.exe tells, that all is ok. error.log from 3DMar2001 tells, that only Directx 6 is installed, but it needs Directx 8.1. Already I fake OS version in registry to XP SP3, does not help, this only helps for to install Nvidia graphik driver 344.11-desktop-winxp-32bit-international.exe Any ideas Dietmar EDIT: 3DMark 2003 runs all correct. Via Legacy Update I have all updates until 2015(!). error.log https://ufile.io/vfrxi8r1

Next try for intelppm.sys to overcome the crazy power consumption. Intelppm.sys 5.2.3790.4143 (srv03_sp2_qfe.070831-1432) USA. Yesssaa, this works. Power consumption now 25 Watt, before 75 Watt. May be, that some powerstates want to go to win2000 powerstates, crazy, Dietmar https://ufile.io/75a3ypqp 1. F:\WindowsServer2003-KB941838-x86-ENU\SP2QFE\intelppm.sys: 36.864 Bytes 2. F:\WindowsServer2003-KB941838-x86-ENU\SP2QFE\intelppmhackkkkkk.sys: 36.864 Bytes Offsets: hexadez. 128: EF 23 129: D8 B3 3CF0: 68 90 3CF1: 2B 2C 3D44: B4 90 4E0D: B4 90 4EAE: 60 90 4EAF: 2D 2A

Hi, does anybody know, how to start Legacy Update for win2003 r2 SP2 DataCenter x86 ? It shows me wrong win2003 r2 SP2 DataCenter 64 Bit and the green running bar stops running at the beginning Dietmar PS: Is there an Service Pack for this win2003 r2 SP2 DataCenter x86 version? EDIT: I just have to wait 30min..

1. F:\WindowsServer2003-KB2281309-x86-ENU\SP2QFE\halmacpi.dll: 119.808 Bytes 2. F:\WindowsServer2003-KB2281309-x86-ENU\SP2QFE\halmacpiTimerhackkk.dll: 119.808 Bytes Offsets: hexadez. 139: F5 67 13A: 01 02 14B83: 79 EB

@XPRTM Thanks a lot, I get both *.exe Updates for wk2 bit32. Do you know a way, how I can extract those files alone to a folder, so that I can fetch only the wished drivers Dietmar

@casdanic I just boot this w2k3 bit32 from Samsung nvme 970 Pro, with the nice nvme driver from @daniel_k Dietmar

@casdanic When "smart" tells you, that something is not ok with your harddisk, this means, that your harddisk is dead already. I just check the Microsoft nvme from @daniel_k. It works with w2k3 bit32, when you use only the storport.sys (modded from win7) which is in the package for stornvme, also for Kai Sata Dietmar

@casdanic This Microsoft nvme driver from @daniel_k works without additional driver. But I never tested it for w2k3 bit32. So maybe, there can be a conflict with the used storport.sys Dietmar https://ufile.io/dusx00yq

@casdanic Yes, it boots from nvme but it is less stable compared with boot from HD. I dont know, why this happen, because we have already a lot of nvme drivers. Only the Microsoft nvme driver is stable. But for me, after few days of correct working, suddently Bsod appears. So, for any industrial production, to boot from nvme is not a good idea. But instead of this I noticed, that boot from Ram is very stable, no crash at all. I use for this the modified grub4dos from Kai Schtrom for to load XP to ram and this is ultrafast and rockstable Dietmar

@casdanic My experience with Gigabyte motherboards is: When they introduce a new board, its Bios is faulty as much as possible. But with time, when some newer Bios versions are out for the same board, it becomes really nice. So, when you are not afraid of flashing Bios, you can make a try also, if there is a newer Bios for your board. But in past I kill a board from Asus, just with updating its original Bios to a newer version. For me, this story with much better Bios now is true for the Gigabyte z690 UD DDR4, which at the beginning even dont recognice any CD-Rom, no working Serial Port etc. Now it is really good and I make all Debug via its Serial Port of XP SP2 bit64 Dietmar

@casdanic I would not buy another motherboard. I am quite sure, that your problem can be solved, may be just when you set up a brandnew w2k3 bit32 install Dietmar

@casdanic Now I get everything to work for w2k3 bit32 on the Asrock z690 Extreme with 12900k cpu. No conflict in Device Manager. USB3 via @daniel_k mod for w2k3 of its *.inf Dietmar https://ufile.io/isho2boc

@casdanic Yepp, hal.dll works, I test with timer, but intelppm.sys not. I install W2k3 bit32 R2, USA version. acpi.sys works. It shows more than 75 Watt doing nothing on the Asrock Extreme z690 board. With the intelppm.sys modded from XP SP3 , this goes down to 25 Watt, but it is still much bigger than it should be. This means, that to change the 2 offsets to C1 states in intelppm.sys is not enough. And also, that the powermanagment in W2k3 bit32 is other than in XP SP3. I get everything to work, I have GT 730 graphikcard, no conflict with any device. USB3 I do not get to work, only xhci, HUB3 not. I tried @daniel_k USB3 AMD 145 driver, the first USB3 driver from @Mov AX, 0xDEAD and the very last USB3 driver from Ramsey, which gives DEADBEEF Bsod, I think because incompatible ntoskrnl.exe from w2k3 bit32 Dietmar

I just notice, that the variant of hal.dll 5.2.3790.3959 (srv03_sp2_rtm.070216-1710) and its ntoskrnl.exe is very much different from XP SP3 version, because it has dependencies on ExiReleaseFastMutex ExiAcquireFastMutex ExiTryToAcquireFastMutex KiCheckForSListAddress which the XP SP3 version does not have Dietmar

@un user Please write here the exact Bsod with XP SP3 acpi.sys version with OS fakes from 21 December Dietmar PS: You have post. Please write everything here, what happens.

@casdanic I succeed to patch intelppm.sys for Win2k3 bit32 for to overcome the big power consumption, by hand only using Winhex Dietmar https://ufile.io/zl1fu6c2 1. F:\win2003filesbit32\files\intelppmOriginal.sys: 40.960 Bytes 2. F:\win2003filesbit32\files\intelppmModd.sys: 40.960 Bytes Offsets: hexadez. 128: CE FE 129: 71 4C 4DBB: B4 90 4E5C: 60 90 4E5D: 2D 2C

@casdanic Please give me the exact(!) name of your motherboard, may be even versions number. The Bios then I fetch from Webside and I modd DSDT. At once we see, if it is the same conflict VGa<=> IOTR or other Dietmar PS: At the weekend I can set up the same W2K3 bit32 on an z690 board. And I make one try more to edit the intelppm.sys by hand. I am quite sure, that on one of this boards will also show the error with missing videocard. And this I can debug Dietmar

@casdanic To edit Bios DSDT in this case is easy for me. But always is a big risk, when you flash Bios. But may be, that @Mov AX, 0xDEAD has another idea, how to overcome this problem with conflict between IOTR and graphic card. For the acpi.sys for XP SP3 it is solved and also for XP SP2 bit 64 I think. For me it is a little bit strange, that this error can be seen now in W2k3 bit32 , it can be overcome with mod in this acpi.sys also Dietmar

@casdanic Does your motherboard have Bios Flashback? In this case you can use the patch for DSDT from @Mov AX, 0xDEAD Dietmar --- DSDT.dsl +++ DSDT.dsl @@ -1,36 +1,13 @@ AMI1 = ITA1 /* \ITA1 */ AMA1 = ITA1 /* \ITA1 */ AMI2 = ITA2 /* \ITA2 */ AMA2 = ITA2 /* \ITA2 */ AMI3 = ITA3 /* \ITA3 */ AMA3 = ITA3 /* \ITA3 */ - If ((ITS0 == One)) - { - ConcatenateResTemplate (Local0, BUF0, Local1) - Local0 = Local1 - } - - If ((ITS1 == One)) - { - ConcatenateResTemplate (Local0, BUF1, Local1) - Local0 = Local1 - } - - If ((ITS2 == One)) - { - ConcatenateResTemplate (Local0, BUF2, Local1) - Local0 = Local1 - } - - If ((ITS3 == One)) - { - ConcatenateResTemplate (Local0, BUF3, Local1) - Local0 = Local1 - } Return (Local0) } } } Scope (_SB.PCI0.LPCB)

@casdanic I remember, that also with XP SP3 we have the problem with missing video card (long time ago). After a patch from @Mov AX, 0xDEAD suddently the graphic card can be seen in Device Manager. But I dont know, how he did this Dietmar