Jump to content

Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)


 Share

Recommended Posts

  • Mov AX, 0xDEAD changed the title to Compiling ACPI v2.0 driver for Windows XP SP3 (x32 only)

@Mov AX, 0xDEAD  @George King

 

I just test the new acpi.sys on the Asrock z370 Fatalty k6 board with 32 Gbyte ram.

It works, nicccceeeeeeee!!!!!!!!!

Interesting, that the Acpi error about mistake in DDB

0x000000A5 (0x00000011, 0x00000008, xxx, yyy)

is not longer shown without any mod

Dietmar

 

 

Edited by Dietmar
Link to comment
Share on other sites

14 hours ago, Dietmar said:

@Mov AX, 0xDEAD  @George King

 

I just test the new acpi.sys on the Asrock z370 Fatalty k6 board with 32 Gbyte ram.

It works, nicccceeeeeeee!!!!!!!!!

Interesting, that the Acpi error about mistake in DDB

0x000000A5 (0x00000011, 0x00000008, xxx, yyy)

is not longer shown without any mod

Dietmar

 

 

Great! I have added it as default one into   XP2ESD. Now we need x64 too :)

 

Compiled file can be found here

https://www.wincert.net/forum/topic/17688-xpw2k3-x86-on-modern-hardware/?do=findComment&comment=138493
Edited by George King
Link to comment
Share on other sites

Unfortunately, Windows 2000 is unfortunate, did not find anyone to support it from these problems :no:

If you knew its value and the value of its logo and the feelings of its users towards it, it would not be left like this :unsure:.

WinWord2000 triste ma grazie a tutti !

  • Like 2
  • Upvote 1
Link to comment
Share on other sites

On the new z690 Asrock extreme board,

the new Vers 2.0 acpi.sys gives BSOD

0x000000A5 (0x00000003, 0x98E1DBA4, 0xC0140008, 0x494E495F)

so until now manual hack in acpi.sys with IDAPro is needed also

Dietmar

 

PS:  _ValidateArgTypes was called with 2nd arg = pointer to string with "H" char inside

at winxp_5512 exist  C, I, O, A, B, D, .. but not "H"

 

 

Edited by Dietmar
Link to comment
Share on other sites

@George King

Can you please compile a "free" version of acpi.sys ver2.0 ?

Because with dirty hack, the acpi.sys "Debug" version shows always

BSOD 0x7E (0x80000003,..)

meaning that a Breakpoint is reached

Dietmar

Link to comment
Share on other sites

19 hours ago, WinWord2000 said:

Unfortunately, Windows 2000 is unfortunate, did not find anyone to support it from these problems :no:

If you knew its value and the value of its logo and the feelings of its users towards it, it would not be left like this :unsure:.

WinWord2000 triste ma grazie a tutti !

Yes, Windows 2000 is the best classic system and really needs this support

  • Like 1
  • Upvote 1
Link to comment
Share on other sites

@Mov AX, 0xDEAD

Concerning the CreateQwordfield implementation, would doing something like this work better?

	pbf->FieldDesc.dwNumBits = 8*sizeof(ULONGLONG);
	pbf->FieldDesc.dwFieldFlags = ACCTYPE_QWORD;
	

Edited by Damnation
  • Like 1
Link to comment
Share on other sites

@Mov AX, 0xDEAD

Thanks for this project. Really great job. I have successfully compiled Debug + Free acpi.sys v5.1.2600.1106

 

What about x64 support?

I have used Win2K3 tools folder inside XPSP1 tree and I tried to build this awesome acpi.sys with razzle option win64 amd64

But seems like compile problems are connected with converting data types and ASM in devpower.c , internal.c , type2op.c , osnotify.c. According to log it seems like it doesn't know "__asm" - keyword not supported it this product. But this is caused by missing ASM code for x64?

Is there any chance to make it x64 compatible? 

 

EDIT: I grabbed tool folder from Win2K3 tree and placed them into XPSP1 tree. I must copy build.exe and mofcomp.exe from x86 to amd64 to be able compile x64 files on Windows 10 x64. So now I can build x64 1106 files.

Now I can launch razzle with win64 amd64 on untouched XPSP1 source tree. I was able to build untouched ACPI for x64 without errors. I think leaked enviroment is capable to build 1106 ACPI for x64 5.2 systems too?

x86 ACPI 2.0 1106 works with 5.1 and 5.2

Windows-XP-5-2-ACPI-2-0.png

More info is  here

https://www.wincert.net/forum/topic/17688-xpw2k3-x86-on-modern-hardware/?do=findComment&comment=138493

Edited by George King
Link to comment
Share on other sites

15 hours ago, Dietmar said:

On the new z690 Asrock extreme board,

the new Vers 2.0 acpi.sys gives BSOD

0x000000A5 (0x00000003, 0x98E1DBA4, 0xC0140008, 0x494E495F)

so until now manual hack in acpi.sys with IDAPro is needed also

Dietmar

 

PS:  _ValidateArgTypes was called with 2nd arg = pointer to string with "H" char inside

at winxp_5512 exist  C, I, O, A, B, D, .. but not "H"

 

 

I think we can add it into misc.c and alipriv.h 

 

Can you try this one? I have added "blank case" result for H argument. But it could be same result as default case so maybe nothing changed.

https://anonfiles.com/1fffa8T7x8/ACPI_2.0_H_test_7z
Edited by George King
Link to comment
Share on other sites

  • Mov AX, 0xDEAD changed the title to Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...