Hi,
has anyone tested the asl.exe Version 5 tool,
if it works under XP?
And if not, can this be changed?
This would be nice for to load DSDT tables to registry.
By the way I noticed, that for to upload a DSDT with asl.exe,
you have to change the revisionsnumber of the DSDT to a higher value, than DSDT in your Bios has.
This can be done with a simple hack in the dsdt.aml it is one Byte at place 08 , there 02 -> 03 (version 2 to version 3 of the DSDT table).
And you have to update your checksum of this dsdt.aml (-1).
This asl.exe version 5 does not crash with newer ACPI
Dietmar

PS: I cant install the WDK 8.1. Can somebody sent me the asl.exe Vers. 5 from there?
It should be in path of the WDK Tools\x86\ACPIVerify
also in WDK 10.

EDIT: Jessa, I got it:))!

I integrate its own DSDT (with versionsnumber of DSDT 2->3) with asl.exe Version 5 on the Q1900m board.
Works.

C:\>asl /loadtable dsdt.aml
Microsoft ACPI Source Language Assembler Version 4.0.0NT [Aug 1 2014, 18:35:18]

Copyright (c) 1996,2009 Microsoft Corporation
Compliant with the ACPI 5.0 Specification


Table overloading succeeded. This will only be active when testsigning is enable
d.

C:\>

I there any testsigning on XP? Or does it work in any case?

EDIT2: The asl.exe version 5 works on XP SP3 for to upload DSDT table.

del

I tried again to install Windows 2003 Server R2 SP2 Enterprise and finally I see for the first time in my B250M-Pro4 board both the total amount of ram correctly recognized and the USB3 working fine even after a shutdown. I would like to get the same on XP using the ram that exceeds 4GB as a ramdrive but before buying the memory I need, what can I try?

@Andalu: the Gavotte Ramdisk is the way to go. the correct version to use (the latest) is attached to my post at reboot.pro which link is below.
http://reboot.pro/topic/4064-gavottes-rramdisk/?p=52696
https://msfn.org/board/topic/176356-simp...comment=1147522
However for maximum stability, you should also set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\DisablePagingExecutive = 1, see:
https://msfn.org/board/topic/177110-wind...comment=1145279

@dencorso
Thanks for the links ;) I used Gavotte until two years ago. I need to use more ramdisks than one only. Currently, on my haswell system with 32GB of ram, I'm using 4 or more ramdisks of which three load at boot. My intention is to use 64GB on XP. Moreover, the software license is for two systems, at the moment I'm using only half of it :)

P.S.: the value in the registry is already set to 1 ;)

Zitat von Mov AX, 0xDEAD im Beitrag #3062

---

Found today bug in PatchPAE3, when it patch hal.dll, it allocate dma-buffers with limit of memory = MAX
in worst case it got memory above 4GB and then try to use it to dma transfers with 32b-only devices.
WinXP's HAL with last SPx doesnt support dma-64, so patch to hal.dll is unnecessary and may crash windows

patch to ntoskrml.exe seem OK, just remove two limitations of phys memory

---

@daniel_k Any chance you’re gonna share some of your FakePAE magic for other’s to test, or is it too experimental for now? It would be interesting to see if it could make a difference my system, at least in my opinion, haha.

Cheers
schreiberstein :)

Let me explain what I've found.

Windows 2003 has many licensing presets (which affects PAE and limits RAM available).

One of them does something interesting: enables PAE, but limits RAM to 4Gb.

The result? RAM is mapped in a more effective way so that more RAM is available.

At the same time, as it is limited to 4Gb, there are absolutely no issues with drivers or specific hardware, which is great for most of us.

New version here:
Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (243)

@daniel_k

thanks!

do we load winxppae in autoexec.bat? or how do we use it?

edit: nevermind, figured it out

edit2: testing in VMWare VM with 8GB RAM assigned to it - applying the /4GB option changes available RAM from 3GB to 8GB - is this expected behavior?

can you add in an option to remove the patch?

@Andalu

are you still having USB trouble with XP?

Zitat von daniel_k im Beitrag #3066

---

Yeah, I noticed that.
Patching hal.dll does result in random crashes.

---

 if ScatterGather=1 {
      no_need()
 }
 

win2003 sp2 logic:

 if ScatterGather=1 {
   if (PhysicalMemoryMayAppearAbove4GB=1 & Dma64BitAddresses=0)
      we_need_mapregisters()
   else
      no_need()
 }
 

winxp sp2 + "patch" logic:

 we_need_mapregisters() in any case
 

as I understand forcing mapregisters means dma double-buffering.
MS told this is not problem, just slowdown because additional memory tranfers.

Zitat von infuscomus im Beitrag #3069

---

edit2: testing in VMWare VM with 8GB RAM assigned to it - applying the /4GB option changes available RAM from 3GB to 8GB - is this expected behavior?

can you add in an option to remove the patch?

---

@daniel_k

awesome! works correctly now

I think it would be a good idea to have the program automatically make backups of the files it modifies, you can't always assume the user has made a backup.

Didn't try it before on VirtualBox.

Glad it works!

From 3.32Gb to 3.83Gb!

Let's hope it helps @schreiberstein too!

@daniel_k

Zitat von daniel_k im Beitrag #3054

---

Now I have 3.7Gb available, before there was only 2.97 Gb.
The best part of it: no compatibility issues!

---