Drivers and tools to run Windows XP on newer hardware

/PAE is never required as long as DEP is enabled in any form, since DEP requires it. I usually set this to OPTOUT, or OPTIN if I'm finding myself constantly tripping DEP.

I don't know if PAE works with /NOEXECUTE=ALWAYSOFF (completely disable DEP) after patching with WinXPPAE. The problem is that since Windows XP SP2, when DEP is set to ALWAYSOFF, PAE also gets disabled, so you won't have access to all the RAM.

EDIT: This change is exclusive to Windows XP SP2, which M$ artificially limited the maximum RAM that made PAE pretty much redundant without DEP. This does not apply to Server 2003 SP1, as Windows Server's max RAM is mainly SKU-specific.

 

@daniel_k

I send this driver collection for testing our friend Mr dUSHA on OSZone forum. He discovered a bug in storahci.inf

Here should be REG_DWORD instead of REG_TYPE_DWORD
[storahci_general_values]

Code:

; Tell Storport in Win7/Srv08R2(KB982018) that driver can report 4K sector size (not needed in Win8)
HKR, "Parameters\Device", "EnableQueryAccessAlignment", %REG_TYPE_DWORD%, 0x00000001

[strings]

Code:

;Localizable
MS                      = "Microsoft"
storahci_ServiceDescription = "Microsoft Standard SATA AHCI Driver"
MS-AHCI="Standard SATA AHCI Controller"
PCI\CC_010601.DeviceDesc  = "Standard SATA AHCI Controller"
;*******************************************
;Non-localizable, Handy macro substitutions
SPSVCINST_ASSOCSERVICE = 0x00000002
SERVICE_KERNEL_DRIVER  = 1
SERVICE_BOOT_START     = 0
SERVICE_ERROR_NORMAL   = 1
SERVICE_ERROR_CRITICAL = 3
REG_EXPAND_SZ          = 0x00020000
REG_DWORD              = 0x00010001
REG_MULTI_SZ           = 0x00010000
REG_MULTI_SZ_APPEND    = 0x00010008

 

Hello George King thanks again for your contribution

 

I finally managed to include WinXPPAE patch in XP2ESD modern installer and patch files with detected RAM amount in GBs on the fly before first boot and HAL selection process.

@daniel_k
On VirtualBox with 8GB I see in system properties 8GB RAM, but on real HW with 8GB I can see 7,91GB any idea why? Patcher is executed with 8GB switch.

 

Probably your system is reserving some resources to the hardware. For example 64mb for the internal graphics?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Add them in Addons/Hotfixes section, integrate ported drivers in Drivers section. Everything should work as new needed files are added into setup to correct places.

 

Thanks. That is, in the Addons/Hotfixes section, specify the path to this addon? To the archive or to the unpacked folder?
The lines are registered, and .sys files where should they be copied?

 

del

 

don't mass storage drivers require a txtsetup.oem to get loaded in the text-mode setup or can we integrate the drivers without it?

 

По русски можно спросить?

 

I don't know if anyone tested these drivers on Windows Server 2003. I once tried integrating them by hand when testing Windows Server 2003 R2 Datacenter but it failed to work as I got a 0xDEADBEEF BSOD.

Actually Windows Server 2003 R2 Datacenter is the only place that can work with 128GB of RAM, minus nVidia drivers which only works with up to 64GB, and some sound cards which simply BSOD with more than 4GB of RAM enabled. Windows XP with the PAE patch can only work with up to 64GB and the same driver issues apply to both XP and 2003.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I am using what windows installer decided for me.
I have Core 2 Duo CPU.

 

Try this

.....

It's working for me on a turion X2 machine, so possibly even older than yours

The files IIRC are set for a 64GB maximum, and are coming from a fully upated XP PosReady 2009

 

You need to login to view this posts content.