Jump to content

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


Mov AX, 0xDEAD

Recommended Posts

1 hour ago, Damnation said:

@Dave-H

That's outdated.

here - https://ufile.io/yuxh9ziz

first try the one in 5.1.2600.7777.4\i386_free

do an "ACPI Multiprocessor PC" install with this one. report any problems.

OK, thanks very much.
Do I have to do a complete new install, or can I just change the file on the existing installation and then try changing the machine type?
:dubbio:

Link to comment
Share on other sites


@Dave-H

To change the machine typ to any other on a running XP can be done but it is crazy hard work with registry.

Much more easy to make a new XP install.

May be, that the hack with faking the OS version via @daniel_k in the very last acpi.sys v4 7777 from @George King helps to overcome the crazy OSEL sleep order in DSDT

Dietmar

 

Edited by Dietmar
Link to comment
Share on other sites

11 minutes ago, Dietmar said:

@Dave-H

Read your DSDT out from your Bios. You can also try to find the original 64bit Bios for you Flex10, but may be you dont find.

Then compare it with my for XP modded DSDT for the Flex10.

And then, make by hand step by step a new DSDT for you, via Beyond Compare 2.

For example the OSEL sleep in DSDT entry makes any Sata driver to stop in XP.

 

            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                If ((OSEL == 0x02))
                {
                    Sleep (0xC8)
                }

                Return (0x0F)
            }

 

Now comes the really hard work:

Without changing anything(!) in Bios you can make use of the tool from @Mov AX, 0xDEAD

for to load a DSDT on boot time for XP SP3.

Then you will get a Flex10, that boots XP, win7, win8, win8.1, win10 etc.

Dietmar

https://ufile.io/72xyvlzd

I think we discussed this before @Dietmar.
You had a modified BIOS for a Flex 10, but it wasn't compatible with my processor.
:no:
I must say this does look very complicated!
:dubbio:

Link to comment
Share on other sites

3 minutes ago, Dietmar said:

@Dave-H

To change the machine typ to any other on a running XP can be done but it is crazy hard work with registry.

Much more easy to make a new XP install.

May be, that the hack with faking the OS version via @daniel_k in the very last acpi.sys v4 7777 from @George King helps to overcome the crazy OSEL sleep order in DSDT

Dietmar

 

At the moment the machine is an 'Advanced Configuration and Power Interface (ACPI) PC' in Device Manager.
The only other option offered is 'Standard PC', but I do remember doing a registry hack before to return the other options.
I'll give that a try first and if that doesn't work I will do another install from scratch with George's latest package.
:yes:

Link to comment
Share on other sites

OK, I tried a straight substitution, and to nobody's surprise I'm sure, I just got an A5 BSOD!
:D
I then tried a new install, putting the new acpi.sys file into \sources\$OEM$\$$\system32\drivers.
Still an A5 BSOD on every option except 'Standard PC'.
One strange thing though is that after the install, the \sources\$OEM$\$$\system32\drivers folder is empty.
Shouldn't the file still be in there @George King?
:dubbio:

Link to comment
Share on other sites

35 minutes ago, Dave-H said:

OK, I tried a straight substitution, and to nobody's surprise I'm sure, I just got an A5 BSOD!
:D
I then tried a new install, putting the new acpi.sys file into \sources\$OEM$\$$\system32\drivers.
Still an A5 BSOD on every option except 'Standard PC'.
One strange thing though is that after the install, the \sources\$OEM$\$$\system32\drivers folder is empty.
Shouldn't the file still be in there @George King?
:dubbio:

True, it should be still in USB\sources\$OEM$\$$\system32\drivers files from $OEM$ are only copied to HDD

Link to comment
Share on other sites

@Dave-H

Check the version of your used acpi.sys in Windows\system32\drivers

on the Flex10 board.

I think, it is not copied, so it is the normal 5512 version

Dietmar

EDIT: Is your Flex10 59433432 ?

Link to comment
Share on other sites

37 minutes ago, Dietmar said:

@Dave-H

Check the version of your used acpi.sys in Windows\system32\drivers

on the Flex10 board.

I think, it is not copied, so it is the normal 5512 version

Dietmar

EDIT: Is your Flex10 59433432 ?

Preview5 ISO contains latest v4 (without DDB hack) already inside ESD.

Link to comment
Share on other sites

1 hour ago, Dietmar said:

@Dave-H

Check the version of your used acpi.sys in Windows\system32\drivers

on the Flex10 board.

I think, it is not copied, so it is the normal 5512 version

Dietmar

EDIT: Is your Flex10 59433432 ?

Checking with Windows 10, the acpi.sys file now on the Windows XP installation is version 5.1.2600.7777 with modified date 28th April 2022, which I think is correct.
The created date is 14th April 2008. The properties' sizes match exactly with the correct file so I've no reason to think that it isn't the correct file.
:dubbio:

Link to comment
Share on other sites

@Dave-H Can you try these patched files? I have patched it in ACPIEnableEnterACPIMode() to disable A5x11 BSOD. There are two different patches. Let me know if any of them will work.

https://anonfiles.com/9cXeoadcy8/acpi_7777_experimental_patch_7z

And here is another one with previous patches and patched all BSOD A5x11 in ACPIInitialize()

 

https://anonfiles.com/Ddgdpad0y9/acpi_7777_experimental_patch2_7z

P.S.

Even if it works will be best to catch log from windbg, as this is only temporary fix when we have source code

Edited by George King
Link to comment
Share on other sites

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...