Win-Raid forum: Windows XP, 2003 x32 on modern hardware

Part 1 ◄ Part 2 ◄ Part 3 ► Part 4 ► Part 5

## Page 221

#3301

daniel_k

⇗ @Mov AX, 0xDEAD
Had an idea about IoConnectInterruptEx and IoDisconnectInterruptEx.
From Microsoft: Drivers that must also work on Windows 2000, Windows XP, or Windows Server 2003 can instead link to Iointex.lib to use the routine.
These functions are used on most storage drivers.
On Vista, msahci.sys only calls functions inside pciidex.sys, which is only missing IoConnectInterruptEx and IoDisconnectInterruptEx functions.
Porting the code from Vista+ is complicated as it is quite long and use many Vista+ only APIs.
What if we compile a code linking to Iointex.lib (calling IoConnectInterruptEx and IoDisconnectInterruptEx) and "isolate" the code so we can port the functions?
Thoughts?

#3302 | Tima177 | hello. can you make me usb 3.0-3.1 for windows xp sp3 pro? ASMedia® USB 3.1 Gen 2 controller : PCI\VEN_1B21&DEV_1242&SUBSYS_86751043
#3303 | diderius6 | ⇗ @Tima177 You can use the driver from Asmedia. Copy also usbd.sys to windows\system32\drivers thats all Dietmar
#3304 | Tima177 | The driver is not suitable, the minimum version of windows 7
#3305 | daniel_k | ⇗ @Tima177 That's what they say officially, don't worry. It works with XP.
#3306 | Tima177 | ⇗ @diderius6 (replying to post #3159): can you give a driver or an iso image? Also trying to install windows xp but on ryzen EDIT by Fernando: Fully quoted post replaced by directly addressing (to save space)

#3307

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3300

> About the AMDXHC USB3 driver, before I waste my time and effort...
> I understand that DMA memory allocation is done by IoGetDmaAdapter, right?
> Will try to implement the same allocation procedure in ASMedia and TI drivers.

No, IoGetDmaAdapter need to build abstract "adapter" and return struct with many pointers to functions:

    typedef struct _DMA_OPERATIONS {
      ULONG  Size;
      PPUT_DMA_ADAPTER  PutDmaAdapter;
      PALLOCATE_COMMON_BUFFER  AllocateCommonBuffer;
      PFREE_COMMON_BUFFER  FreeCommonBuffer;
      PALLOCATE_ADAPTER_CHANNEL  AllocateAdapterChannel;
      PFLUSH_ADAPTER_BUFFERS  FlushAdapterBuffers;
      PFREE_ADAPTER_CHANNEL  FreeAdapterChannel;
      PFREE_MAP_REGISTERS  FreeMapRegisters;
      PMAP_TRANSFER  MapTransfer;
      PGET_DMA_ALIGNMENT  GetDmaAlignment;
      PREAD_DMA_COUNTER  ReadDmaCounter;
      PGET_SCATTER_GATHER_LIST  GetScatterGatherList;
      PPUT_SCATTER_GATHER_LIST  PutScatterGatherList;

     // version 2 operations
      PCALCULATE_SCATTER_GATHER_LIST_SIZE  CalculateScatterGatherList;
      PBUILD_SCATTER_GATHER_LIST  BuildScatterGatherList;
      PBUILD_MDL_FROM_SCATTER_GATHER_LIST  BuildMdlFromScatterGatherList;
    }
     DMA_OPERATIONS, *PDMA_OPERATIONS ;

also IoGetDmaAdapter allocate some amount of MapRegisters in some cases (GatterScatter=1 & dma64=0 is our case)
real allocation is done in AllocateCommonBuffer, driver then get phys adress of this buffer and write to pci device registers
for example in intel usb3 controller one of this adresses stored at offset BAR+0xB0-0xB4 (Device Context Base Address Array Pointer)
Under Win7 x64 this adress is 1:3CA58000
in win32 this high adress will be maped to some LOW ring-0 adress
EDIT by Fernando: Quoting corrected and Code content put into a "spoiler" (to save space)

#3308 | Tima177 | I tried loading windows xp through sata ahci asm1061 pcie 1.0, although the drivers for usb through the pcie 1.0 usb controller do not work, it freezes when I boot without usb 3.0 and get the desktop without a single usb driver.

#3309

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3301

> @Mov AX, 0xDEAD
> From Microsoft: Drivers that must also work on Windows 2000, Windows XP, or Windows Server 2003 can instead link to Iointex.lib to use the routine.
> What if we compile a code linking to Iointex.lib (calling IoConnectInterruptEx and IoDisconnectInterruptEx) and "isolate" the code so we can port the functions?

Iointex.lib has simple emulation of *Ex over IoConnectInterrupt/IoDisconnectInterrupt, just copy&paste to your existing code and call it without modification of original code. Intel usb3.0 driver for win7 also has simple emulation *Ex over IoConnectInterrupt/IoDisconnectInterrupt, about 80 bytes

#3310 | daniel_k | ⇗ @Mov AX, 0xDEAD Thanks for the thorough explanation! To be honest, didn't see what's inside Iointex.lib. I did know it was emulating Ex using non-Ex functions, but never thought of using it without compiling some code. Hopefully this is easier and more prone to success than storport!

#3311

Tima177

I downloaded one assembly, deployed the acronis trueImage image to hdd, added OSDTOOL from another assembly, integrated the driver for sata ASM1061 and loaded windows xp into amd ryzen x370 in standard PC mode without ACPI via the pci-e sata controller, the keyboard and mouse do not work without USB drivers, if I integrate drivers for via usb pcie controller then it hangs at boot, without driver on usb windows xp controller it starts
can you help with the drivers?

#3312

Mov AX, 0xDEAD

> Zitat von ⇗ Tima177 im Beitrag ¶ #3311

> the keyboard and mouse do not work without USB drivers, if I integrate drivers for via usb pcie controller then it hangs at boot, without driver on usb windows xp controller it starts

Хай, Тима
- via usb3 drivers hard to integrate because they require coinstaller (WDF)
- if it possible enable port 64 emulation in bios, your mouse&keyboard will work as PS/2 Devices and you can install normal usb3 drivers after windows is loaded to desktop, then disable emulation

#3313 | Tima177 | No ps/2, can you give adapted amd usb 3.0 drivers for windows xp?

#3314

diderius6

⇗ @Tima177
It is also possible to do a silent installation of XP.
Then you do not type anything during XP install
Dietmar
PS: Or use a cheap USB card, where are drivers for XP without coinstaller,
for example nec (Renesas).

#3315 | Tima177 | With drivers on usb Windows does not start, hangs at the beginning of loading of a strip

## Page 222

#3316 | infuscomus | ⇗ @daniel_k i have an old program that can write extra functions onto the end of PE files did you want to try it out? maybe you can achieve something with it? here is an example of a file the program spits out ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (165)

#3317

diderius6

Hi, I just wrote my very first program
for a Quantum Computer and it works :)) !!
The program does the following:
First the start state is fixed, here a 0. (The coin shows head.)
Then the Hadamard operator is applied to it, here called H.
H creates a true overlay of the head (0) and coin of the number(1) (just like Schrödinger's cat).
Then comes the measurement, here the symbol with the arrow.
The Quantum Computer ran my program 1024 times.
And as you can see, almost 50% head and 50% number.
The huge difference to ALL other computer programs is,
here actually the computer throws really "dices" and shows me the result
Dietmar
⇗

#3318 | cedar | I always knew Schrödinger's cat can run XP32 and XP64 simultaneously. :-)

#3319

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3317

> H creates a true overlay of the head (0) and coin of the number(1) (just like Schrödinger's cat).

@diderius6...actually, Schrodinger's Cat was about Schrodinger poking fun at the more far out quantum theory claims started by Bohr et al. Schroddy decided to retire rather than get involved with what he saw as stupidity in quantum theory.
When Schroddy claimed the cat could be both dead and alive, he was poking fun at the notion of entanglement theory where a particle like an electron is inferred to be in two places at once.
I agree with Schroddy, it is nonsense.

#3320 | infuscomus | ⇗ @diderius6 do you have any solutions for XP ACPI on threadripper?
#3321 | Tima177 | Can you give a modified driver AMD USB 3.0-3.1 or for ASMedia® USB 3.1 Gen 2 controller? My chipset AMD x370
#3322 | Fernando | @recent posters: Did you all refer to the specific topic "PAE Bugs" or has the thread title been changed?
#3323 | infuscomus | ⇗ @Fernando for some reason replies are titled PAE bugs I have had to change it manually for this post
#3324 | infuscomus | ⇗ @Tima177 for ASMedia USB 3 try looking in the USB driver thread.
#3325 | Fernando | ⇗ @infuscomus: Thanks for your quick reaction. Each reply gets automaticly the title of the post, where the user had clicked onto the "Reply" button. To avoid a wrong/not matching title, just click onto the "Reply" button under a post with the correct thread title (e.g. the start post).

#3326

Tima177

> Zitat von ⇗ infuscomus im Beitrag ¶ #3324

> @Tima177
> for ASMedia USB 3 try looking in the USB driver thread.

What do you mean by driver stream?

#3327 | infuscomus | ⇗ @Tima177 ⇗ USB 3.0/3.1 Drivers (original and modded)

#3328

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3287

> your modded USB 3.0 drivers from earlier, were any of them generic?

Sorry, I overlooked your message.
Yes, when canonkong was asking me to mod some drivers for AMD controllers.
Don't have any files here, just kept the ones that work on Intel.

#3329 | infuscomus | ⇗ @daniel_k I was testing your modded amdxhci driver that works for intel, annoyingly it doesn't work for every AMD USB 3.0 controller (the controllers with 43 in the deviceID give a D0 BSOD)

#3330

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3299

>     my_memset:
>         jmp ds:__imp__memset ;  need 1 reloc !
>     endp
>     .....
>     call my_memset ; E8 xx xx xx xx 5 Bytes
>     nop

Can I use this for indirect calls?
Such as:

    8B35BC700700                   mov          esi,[0000770BC]
    FFD6                           call         esi

Just by replacing with this?

    FFE6                           jmp          esi

## Page 223

#3331

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3330

> @daniel_k
> I was testing your modded amdxhci driver that works for intel, annoyingly it doesn't work for every AMD USB 3.0 controller (the controllers with 43 in the deviceID give a D0 BSOD)

This is a known issue.
Try Etron or VIA drivers, if I'm not mistaken.

#3332

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3309

> Iointex.lib has simple emulation of *Ex over IoConnectInterrupt/IoDisconnectInterrupt, just copy&paste to your existing code and call it without modification of original code. Intel usb3.0 driver for win7 also has simple emulation *Ex over IoConnectInterrupt/IoDisconnectInterrupt, about 80 bytes

Managed to patch pciidex.sys, but msahci.sys still doesnt work as it needs Vista's ataport.sys and atapi.sys. Too much hassle.
Those in-box drivers are a headache, Microsof does some funky things.
Here is my x64 wrapper for memcpy_s to memcpy:

    mov          [rsp][020],r9
    mov          [rsp][018],r8
    mov          [rsp][010],rdx
    mov          [rsp][8],rcx
    sub          rsp,028
    mov          r8,[rsp][048]
    mov          rdx,[rsp][040]
    mov          rcx,[rsp][030]
    call         memcpy
    xor          eax,eax
    add          rsp,028
    retn

As I still don't know everything about assembly, managed to compile the code above with the DDK and took the code from the compiled driver.
It works!
Any comments? The only catch is that I had to disable optimizations, otherwise "my function" is compiled inline. Is there a way to force the compile to not do this?

#3333

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3331

> Can I use this for indirect calls?
> Such as:

>     FFD6                           call         esi

> Just by replacing with this?

>     FFE6                           jmp          esi

Hi Daniel,
- call -> jmp is not possible, you'l lost return adress
- i dont understand what is point ? avoid relocs?

#3334

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3333

> Here is my x64 wrapper for memcpy_s to memcpy:

>     mov          [rsp][020],r9
>     mov          [rsp][018],r8
>     ...
>     sub          rsp,028

esp+xx mean "shadow space", be carefull with this code, callee must reserve at least 4*8 (or 5*8 ?) bytes at stack before calling this. Unusual vs x32 calling conventions.

> Zitat von ⇗ daniel_k im Beitrag ¶ #3333

> The only catch is that I had to disable optimizations, otherwise "my function" is compiled inline. Is there a way to force the compile to not do this?

⇗ https://stackoverflow.com/questions/3366...er-optimization

#3335

daniel_k

⇗ @Mov AX, 0xDEAD
Thanks for info and link.
I'm patching iaStorA.sys (RSTe).
For x86, there 2 types of CALLs:

    FF15xxxxxxxx      CALL memcpy_s

This uses your previous suggestion.

    BE00580600                     mov          esi,000065800
    FFD6                           call         esi

For this one, can I just change the address to point to my new function?
My memcpy_s to memcpy:

    mov     edi, edi
    push    ebp
    mov     ebp, esp
    push    [ebp+arg_C]
    push    [ebp+arg_8]
    push    [ebp+arg_0]
    call    memcpy
    add     esp, 0Ch
    xor     eax, eax
    pop     ebp
    retn    10h

----------------
For x64, now with optimized compiler, forced non-inline:

    4883EC28                       sub          rsp,028
    498BD0                         mov          rdx,r8
    4D89C8                         mov          r8,r9
    E810500000                     call         memcpy
    33C0                           xor          eax,eax
    4883C428                       add          rsp,028
    C3                             retn

Now this seems correct, right? RCX is the first argument on both functions, so don't touch it.
Does it matter for the parameters if I change the call type from E8 to FF15?

#3336 | skullteria | What the problema now? I can't understand..well, if problem reside on storahci, i can update fode, because i used a beta versioj, maybe It ia unstable

#3337

diderius6

⇗ @coldwove
Please try this acpi.sys
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#3338

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3336

>     BE00580600                     mov          esi,000065800
>     FFD6                           call         esi

> For this one, can I just change the address to point to my new function?

yes, you can change to what you prefer, mov esi, offset new_func or relative call (e8 xx xx), but not to "FF 15"

> Zitat von ⇗ daniel_k im Beitrag ¶ #3336

> Now this seems correct, right? RCX is the first argument on both functions, so don't touch it.
> Does it matter for the parameters if I change the call type from E8 to FF15?

- i dont remember what is args of memcpy_s need to drop, 2nd i guess, so seems ok x32 and x64
- no matter what of "call" was used, they do with stack same things
- sub rsp, 28 - i dont know how compiler choose size of shadow space, so can't confirm

#3339

daniel_k

> Zitat von ⇗ skullteria im Beitrag ¶ #3337

> What the problema now? I can't understand..well, if problem reside on storahci, i can update fode, because i used a beta versioj, maybe It ia unstable

I didn't experience any issues, on VirtualBox and real PC.
⇗ @diderius6, please explain your issue with storahci. BSOD 7B on last stage of Setup?

#3340 | daniel_k | ⇗ @Mov AX, 0xDEAD Thanks, much appreciated!

#3341

diderius6

⇗ @skullteria
"⇗ @diderius6, please explain your issue with storahci. BSOD 7B on last stage of Setup?"
Yes, not all values from the *.reg file are stored in registry during Setup of XP.
The path to windows\system32\drivers\storahci.sys is gone and the same is true for the modded AMD USB driver for Intel boards.

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\storahci]
    "Type"=dword:00000001
    "Start"=dword:00000000
    "Group"="SCSI miniport"
    "ErrorControl"=dword:00000001

This is a strange error, because everything in txtsetup.oem or txtsetup.sif for STORAHCI together with storport.sys is correct.
When you add the entries by hand to registry or install STORAHCI on a running XP via storahci.inf
all is ok. The nice thing in STORAHCI for XP SP3 is, that it runs on really every motherboard
Dietmar

#3342 | coldwove | ⇗ @diderius6 putting that acpi.sys into driver.cab yielded the same A5 bsod as before sadly.
#3343 | diderius6 | ⇗ @coldwove Did you put this acpi.sys also in i386 folder from your Installationsmedium Dietmar
#3344 | coldwove | ⇗ @diderius6 i386 folder only holds an acpi.sy_ file, how would i convert the .sys file to .sy_?
#3345 | diderius6 | ⇗ @coldwove You can just delete the file acpi.sy_ there in i386 folder and put new acpi.sys at its place Dietmar

## Page 224

#3346

coldwove

⇗ @diderius6 nope still doing the same thing sadly :c
0x000000A5
0x00000002
0x8D1BF828
0x00000001
0x8D1C4778

#3347 | infuscomus | ⇗ @diderius6 have you tried this to fix storahci not working? ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (219)

#3348

dencorso

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3334

> > Zitat von ⇗ daniel_k im Beitrag ¶ #3331

> > Can I use this for indirect calls?
> > Such as:

> >     FFD6                           call         esi

> > Just by replacing with this?

> >     FFE6                           jmp          esi

> Hi Daniel,
> - call -> jmp is not possible, you'l lost return adress
> - i dont understand what is point ? avoid relocs?

⇗ @Mov AX, 0xDEAD:
Then again he could do as in the old times and...
push eip
jmp esi
... for the RET to work right, cannot he?

#3349

Mov AX, 0xDEAD

> Zitat von ⇗ dencorso im Beitrag ¶ #3348

> push eip

this opcode just not exist

#3350

infuscomus

⇗ @daniel_k
do you think it would be possible to fix or remove missing imports for acpi.sys vista beta 5365 to work for XP?
ntoskrnl
EmClientRuleEvaluate
_strtoui64
PoSetSystemWake
EmProviderRegister
IoSetDevicePropertyData
KeStartDynamicProcessor
RtlIoEncodeMemIoResource
EtwRegister
EtwWrite
EtwEventEnabled
RtlCmDecodeMemIoResource
RtlIoDecodeMemIoResource
EmClientQueryRuleState
RtlInvertRangeListEx
IoConnectInterruptEx
hal
HalGetInterruptTargetInformation
HalConvertDeviceIdtToIrql
HalGetMessageRoutingInfo
infuscomus has attached files to this post

- ⇗ acpi 5365.zip

#3351

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3316

> @daniel_k
> i have an old program that can write extra functions onto the end of PE files
> did you want to try it out? maybe you can achieve something with it?
> here is an example of a file the program spits out
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (165)

Thanks, will try later if need it.

> Zitat von ⇗ infuscomus im Beitrag ¶ #3350

> do you think it would be possible to fix or remove missing imports for acpi.sys vista beta 5365 to work for XP?

Maybe... but there are many missing imports.
Before trying to fix those imports, to know if that build does work on current systems.

#3352

daniel_k

⇗ @Mov AX, 0xDEAD
Patched and tested x64 iaStorA.sys, work just fine.
Working on x86.
Asked the wrong question, really sorry.
I have 93 calls with relocation like this:
FF15BC700700 call memcpy
Is there a way to keep the relocs and avoid to remove all of them?
I know that FF15 = CALL DWORD PTR, so I tried the following:
FF15B9100100 call d,[0000110B9]
...
110B9: B0640700 - pointer to actual memcpy_s to memcpy function, with relocation
...
764B0: 8BFF mov edi,edi - memcpy_s to memcpy function
764B2: 55 push ebp
764B3: 8BEC mov ebp,esp
764B5: FF7514 push d,[ebp][014]
764B8: FF7510 push d,[ebp][010]
764BB: FF7508 push d,[ebp][8]
764BE: FF15BC700700 call memcpy
764C4: 83C40C add esp,00C
764C7: 33C0 xor eax,eax
764C9: 5D pop ebp
764CA: C21000 retn 00010
Didn't work, need to read more about it.
PS: CODE tag is broken?! Will edit later...

#3353 | daniel_k | ⇗ @diderius6 Please pack and send me the following files of your ISO with storahci.sys that you've tried and didn't work. DOSNET.INF, HIVESFT.INF, HIVESYS.INF, SETUPREG.HIV and TXTSETUP.SIF.

#3354

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3353

> I have 93 calls with relocation like this:
> FF15BC700700 call memcpy
> Is there a way to keep the relocs and avoid to remove all of them?
> I know that FF15 = CALL DWORD PTR, so I tried the following:
> FF15B9100100 call d,[0000110B9]
> ...
> 110B9: B0640700 - pointer to actual memcpy_s to memcpy function, with relocation
> ...
> 764B0: 8BFF mov edi,edi - memcpy_s to memcpy function

All seems OK, to keep orig relocs need things you are already did

#3355

diderius6

⇗ @daniel_k
Here are the wished files from my XP SP3 setup CD,
which give BSOD via STORAHCI on last reboot
Dietmar
diderius6 has attached files to this post

- ⇗ STORAHCIFILES.rar

#3356

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3355

> All seems OK, to keep orig relocs need things you are already did

Thanks.
That'so odd, it crashes.
Will double check, maybe I missed something.

#3357 | daniel_k | ⇗ @diderius6 Files are 100% identical. Did you get the AHCI driver signature warning during Setup?
#3358 | diderius6 | ⇗ @daniel_k No error message at all about signature during Setup Dietmar

#3359

infuscomus

⇗ @daniel_k ⇗ @diderius6
try my solution in txtsetup.sif
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (219)
does it work for you?
⇗ @diderius6
you have several [SourceDisksFiles] in your txtsetup.sif - mine does not
maybe yours is malformed? start from scratch?

#3360

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #3359

> @daniel_k
> No error message at all about signature during Setup
> Dietmar

Hmm
You must get 2 driver signature warnings during Setup (AHCI and XHCI), otherwise the drivers are NOT installed and you'll get 0x7B when finished.
Did you use an untouched ISO and replaced the files with the ones of my package?

## Page 225

#3361 | diderius6 | ⇗ @daniel_k I integrated Servicepack SP3 into it. All other is original XP SP1 CD Dietmar

#3362

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3360

> @diderius6
> you have several [SourceDisksFiles] in your txtsetup.sif - mine does not
> maybe yours is malformed? start from scratch?

The original TXTSETUP.SIF is just like that.
If you use nLite, it consolidates all sections into a single one.

#3363

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #3362

> @daniel_k
> I integrated Servicepack SP3 into it.
> All other is original XP SP1 CD
> Dietmar

Don't do this.
That is why you are having issues.
Get the original ISOs with SP3 already integrated.
Need help to find ENU or DEU?

#3364 | diderius6 | ⇗ @infuscomus I just burn a new CD with all your changes and in this moment I do Setup of XP SP3 with it, with the identical installation of the EVGA dark board Dietmar
#3365 | infuscomus | ⇗ @diderius6 i also agree with daniel_k, use an ISO with SP3 already integrated, it would save a lot of hassle like what you have already been experiencing.
#3366 | diderius6 | ⇗ @infuscomus After I choose the harddisk for install, XP Setup tells me: Error 1984 in SIF file, setup has been canceled, hit F3 Dietmar
#3367 | infuscomus | ⇗ @diderius6 strange, these entries worked for me. i suggest starting over with a clean SP3 ISO.

#3368

diderius6

⇗ @infuscomus ⇗ @daniel_k
I look through my hundreds of XP install CDs.
And I notice, that I have really all
but no CD with original XP SP3 in it.
Always I used XP CD and install Servicepack SP3 with nlite
Dietmar
EDIT: I just found a original XP SP3 Setup CD from HP. But even on this, it is a CD with new integrated SP3 package.

#3369

infuscomus

⇗ @diderius6
the file you should look for is de_windows_xp_professional_with_service_pack_3_x86_cd_x14-80444.iso
I'll let you know if i find it
edit:
here
⇗ https://keybase.pub/gottz/var/iso/de_win...d_x14-80444.iso

#3370 | diderius6 | ⇗ @infuscomus Thanks a lot Dietmar

#3371

daniel_k

⇗ @Mov AX, 0xDEAD
Was having issues, but finally succeeded.

    BE00580600                     mov          esi,000065800
    FFD6                           call         esi

This actually also acts like a call dword ptr.
My memcpy_s to memcpy:

    ...
    retn    10h

Should be just retn, as the caller is responsible for stack cleanup.
Interestingly, retn 10h works with call <register>, but doesn't work for call <dword ptr>.
Will post the updated drivers later.
Now will see what can I do with the AMDXHC driver.

#3372

diderius6

Yesssaa:)) ,
this time I can install XP SP3 on the EVGA dark board at once via STORAHCI driver.
I also see, where the difference between the original XP SP3 CD and the one updated with Servicepack SP3 is:
The CD with servicepack SP3 use as standard settings the "NO" option, when a driver without valid signatur is choosen.
Here now I see for the very first time the question during device install "Do you want xhci.sys" with option settings to "NO"
but I can change this to yes, and few seconds later the same question for STORAHCI.sys , 2 times.
I think, this question never appears on XP SP1 and so crazy SP3 package just ignore this driver via its path in registry.
The same is true for the xhc driver, now it has path in registry also
Dietmar
PS: This means, we have with this STORAHCI a generic driver for XP SP3 for all boards with AHCI.

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\storahci]
    "Type"=dword:00000001
    "Start"=dword:00000000
    "Group"="SCSI miniport"
    "ErrorControl"=dword:00000003
    "DisplayName"="AHCI SATA Driver"
    "ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
       52,00,49,00,56,00,45,00,52,00,53,00,5c,00,73,00,74,00,6f,00,72,00,61,00,68,\
       00,63,00,69,00,2e,00,73,00,79,00,73,00,00,00
    "Tag"=dword:00000021

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\storahci\Parameters]
    "BusType"=dword:0000000b

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\storahci\Parameters\PnpInterface]
    "5"=dword:00000001

#3373

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3350

> > Zitat von ⇗ dencorso im Beitrag ¶ #3349

> > push eip

> this opcode just not exist

⇗ @Mov AX, 0xDEAD
Just curious.
When you write push eax, you are pushing the value in eax. There are opcodes for that.
What if you wrote push [eip]? Would the assembler accept that as an immediate push as in push 15000 and push the current address stored at eip?
The push immediate operands are 6A for a single byte, and 68 for a word and double word. Does the push instruction know how to read an immediate value via a pointer?

#3374

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3373

> I also see, where the difference between the original XP SP3 CD and the one updated with Servicepack SP3 is:

@diderius6...good work on your storage driver.
Don't know if you are aware of this or whether it has been covered elsewhere on win-raid.
There are apparently other issues between the original XP SP1 CD, the XP SP2 setup file, and XP SP3 setup file. Apparently Microsoft has admitted their service packs can sometimes produce a conflict with the setupapi file on the service pack installer and that can lead to errors in the slipstreamed version.
For example, when upgrading SP1 to SP2 on an x86 machine, Microsoft suggested decompressing the SP2 file to a directory, renaming the setupapi file on the SP2 service pack installation, then applying the extract command from the SP2 installation:
On the extracted service pack file directory in a cmd window:
cd i386\update
ren setupapi.dll setupapi.old
update.exe /integrate:c:\bin
Where c:\bin is the directory of the existing OS to be updated.
I don't know if they have fixed this in SP3 but I am having a serious problem in which I am stuck in the middle of a repair install where the installer won't accept a valid product ID from the label on the case of the original XP installer.
Microsoft has admitted in the past that such a problem is related to installing a service pack on a different OS than the target OS. I am referring to slipstreaming a target disk for XP using win 7 or higher.
I did use nlite but even they insist that slipstreams should be done on an OS that is the same as the target OS.

#3375

infuscomus

> Zitat von ⇗ daniel_k im Beitrag ¶ #3351

> aybe... but there are many missing imports.
> Before trying to fix those imports, to know if that build does work on current systems.

⇗ @daniel_k
vista beta 5365 works on my AB350 gaming K4 Ryzen motherboard - no A5 BSOD
do you think you can remove those missing imports without breaking it?

## Page 226

#3376

Mov AX, 0xDEAD

> Zitat von ⇗ gordo999 im Beitrag ¶ #3373

> What if you wrote push [eip]

you'l get compiler error, ip is hidden register on x32 asm language, only x64 allow use it as base offset

#3377

icinemagr

I give up i try anything and everything i could read in forum.
Can someone tell me if is possible to install XP on the follow Specs.
motherboard
Gigabyte Z270 k3 gaming
Northbridge Intel Kaby Lake rev. 05
Southbridge Intel Z270 rev. 00
memory
Memory Type DDR4
Memory Size 16 GBytes
Channels Single
Memory Frequency 1199.8 MHz (1:18)
Graphics
Name NVIDIA GeForce GTX 1060 6GB
Board Manufacturer ASUSTeK Computer Inc.
hard disk
Name Samsung SSD 960 EVO 500GB
cpu
Intel Core i7 7700k

#3378 | Fernando | ⇗ @icinemagr: Since you need support from an expert about how to get Windows XP installed onto an Intel 200-Series Chipset system, I have moved your request into this already existing 100% matching thread. Good luck!

#3379

diderius6

⇗ @icinemagr
All will work under XP SP3.
When you want 3D graphik,
you need to change your videocard against
for examle GTX 980
Dietmar

#3380 | diderius6 | Hihi, I succeed to crash the Quanten Compi:)) Dietmar ⇗

#3381

gordo999

@ diderius6
Dietmar...wondering how I could apply your latest version of acpi.sys for XP.
Up till now, I have been trying to get an existing XP SP3 OS on a drive running so I could apply things you guys are doing in this thread. It's a steep learning curve but I am making headway.
Today, I got a stable version of XP SP4 (yes..SP4...by harkaz) running but without any of my existing apps, which I need running. The SP4 update by harkaz offered an install from the slipstreamed SP3/SP4 disk and I mistook it for a repair install. What it did was install a separate copy of XP along with my current install in parallel directories, one marked winxp and the other winxp.0.
But, hey...what the heck, I have the one in winxp.0 running. If possible I'd now like to get my original install running.
Tried tonight and it got to the XP screen with the running horizontal dots and it crashed with an 0xA5 error...good old ACPI.
Can I install your ACPI driver using the F6 method or via a direct registry edit?
I would work this out for myself but I am a bit eager to get my version running, no matter how badly it might behave. That's part of the challenge, eh?
While getting the working version going I figured out how to get around the invalid product key issue. It involves pidgen.dll, licdll.dll, and a couple of other files version changes.

#3382

gordo999

@ infuscomus...remember the problem I had with an old w98 on a FAT32 partition 1 and XP on partition 2? I removed the w98 partition (deleted it) and moved the xp partition to the front of the disk. I think it was Easeus partition manager I used.
That took care of my boot.ini problem.
Anyway, I completely forgot that the registry has everything for XP under partition 2, the D:\ drive. So, I had to change them all manually to C:\ drive. Partition Magic used to have a utility that would do that for you.
I got into it by hand and thought it was a bit much. Some companies like Comodo have over 250 entries in one hklm/system sub-hive alone. Why doesn't the registry have a search and replace function? And why do companies dump their garbage in there? Like someone said, the registry is like garbage truck that never reaches the dump.
Solved it by taking each hive from the windows\sys32\config directory and loading each one in a text editor that had a search/replace utility. I got it to find all references to my win dir, d:\winxp and replace it with c:\winxp.
Learned along the way that it's not necessary to edit each currentcontrol set. There is an entry in the registry that tells which CCS is in use (default) and which one is the last known good one. My hklm\system hive had 4 currentcontrol sets and I only had to edit ccs003. I did ccs004 as well, which saved a lot of work.
There was one other monster sub-hive, shareddlls, in the software hive, but the text editor took care of them all.

#3383 | infuscomus | ⇗ @gordo999 you have alot of patience, I would've just done a fresh install of XP.

#3384

genieautravail

⇗ @daniel_k
The latest build of your modded acpi.sys file ins't compatible with AMD Carrizo APU.
Here the link to the motherboard :
⇗ https://www.biostar.com.tw/app/en/mb/int...on.php?S_ID=935
At boot, I get the famous BSOD (STOP : 0x000000A5)
Can you do something about this ?
Best regards

#3385

diderius6

⇗ @gordo999
When you have a working XP version with acpi support,
it is enough to copy the modded acpi.sys into folder
windows\system32\drivers
Dietmar
PS: Here is the entry for registry for acpi.sys

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ACPI]
    "ErrorControl"=dword:00000001
    "Group"="Boot Bus Extender"
    "Start"=dword:00000000
    "Tag"=dword:00000001
    "Type"=dword:00000001
    "DisplayName"="Microsoft ACPI-Treiber"
    "ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
       52,00,49,00,56,00,45,00,52,00,53,00,5c,00,41,00,43,00,50,00,49,00,2e,00,73,\
       00,79,00,73,00,00,00

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ACPI\Enum]
    "0"="ACPI_HAL\\PNP0C08\\0"
    "Count"=dword:00000001
    "NextInstance"=dword:00000001

#3386 | infuscomus | ⇗ @genieautravail more info is needed - can you take a screenshot of the BSOD? it will show more about the exact error

#3387

genieautravail

> Zitat von ⇗ infuscomus im Beitrag ¶ #3386

> @genieautravail
> more info is needed - can you take a screenshot of the BSOD? it will show more about the exact error

Here a screenshot.
The text is in french because it's a french edition of Windows XP SP3.
To quickly resume :
The BIOS isn't fully compliant with ACPI specifications and you can silently disable ACPI by pressing F7 key during installation.
⇗

#3388 | diderius6 | Hi, does anybody know, what this error means: STOP: c0000139 {Entry Point Not Found} The procedure entry point GdiGetBitmapBitssize could not be located in the dynamic link library GDI32.dll. Dietmar
#3389 | infuscomus | ⇗ @diderius6 I'm guessing the function GdiGetBitmapBitssize isn't in GDI32.dll ? check it with dependency walker.
#3390 | diderius6 | ⇗ @infuscomus Yepp, this is just true, "GdiGetBitmapBitssize isn't in GDI32.dll" thanks a lot Dietmar

## Page 227

#3391

IntiMD

> Zitat von ⇗ diderius6 im Beitrag ¶ #3388

> Hi, does anybody know, what this error means:
> STOP: c0000139 {Entry Point Not Found}
> The procedure entry point GdiGetBitmapBitssize could not be located in the
> dynamic link library GDI32.dll.

It actually should be there, maybe the service pack installation was unfinished or something like that? Here's a blogpost related to the problem and a possible solution: ⇗ https://vit-experts.blogspot.com/2008/06...-not-found.html

#3392

diderius6

⇗ @genieautravail
Here is fresh modded acpi.sys
against BSOD A5, 0x0000000D
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#3393 | genieautravail | ⇗ @diderius6: Thank you, I will try it in the next days EDIT by Fernando: Fully quoted post replaced by directly addressing (to save space and for better readability)

#3394

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3385

> When you have a working XP version with acpi support,
> it is enough to copy the modded acpi.sys into folder
> windows\system32\drivers
> Dietmar

@diderius6....Not sure what you mean, Dietmar. By acpi support, do you mean in the BIOS? I have an Asus B360M mobo and it has acpi 6.1 However, when I get the 0xA5 bsod it claims the BIOS is not acpi compliant.
Oddly enough, the same installation of XP SP3 slipstreamed with the unofficial SP4 upgrade does not get the 0xA5 error and it has no acpi.sys in %windir%\system32. Neither does my original XP SP3 install, even though it has an entry in the registry. The only acpi.sys on my original system is in a directory called %windir%\i386. Have no idea where it came from.

> Zitat von ⇗ diderius6 im Beitrag ¶ #3385

> PS: Here is the entry for registry for acpi.sys

My registry for the XP SP3 install is much simpler. It has everything you list in the first part except the image path is in ASCII, not hex.
There is no ENUM sub-tree. In fact, the registry values you describe are the same as in my Win 7 registry under HKLM\System\ACPI which also has a reference to ACPI_HAL.
Maybe I need to go further back in the thread and read about HAL, etc.

#3395 | infuscomus | ⇗ @gordo999 it sounds like you don't have ACPI enabled on your system.

#3396

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3388

> Hi, does anybody know, what this error means:
> STOP: c0000139 {Entry Point Not Found}
> The procedure entry point GdiGetBitmapBitssize could not be located in the
> dynamic link library GDI32.dll.
> Dietmar

@diderius6...In my experience it has meant the dll has been updated so that the address is no longer valid. The function is likely still in the dll, it's no longer at the address called. You might need to find the version to which the calling address applies. Or edit the calling file to point it to the new address.
BTW...I inserted your acpi.sys into the %windir%\System32\drivers and amended my registry to reflect your example and I no longer get the 0xA5 bsod. Instead, I get an 0X7B and I think I know the solution.
When I updated my XP SP3 disk to the unofficial XP SP4 upgrade from harkaz, there was a SATA driver in the package signed by Fernando. It works well for XP on a newer mobo. Unfortunately I don't think it has a txtsetup.oem file for an F6 install so I may have to compare registry values for iaStor in the version that works with my version that gets the bsod.
Progress!!! :-)

#3397

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3395

> it sounds like you don't have ACPI enabled on your system.

@infuscomus....It is enabled. Solved the problem for now using Dietmar's driver and advice.
I am now getting an 0X7B which is likely the driver required by Windows to interface with the SATA drive. The bsod only occurs when Windows is trying to start, either through a normal boot or via an install disk. The install disk routine happily goes along till the point where it says windows is starting.
re patience...with the amount of patience I have, I should have been a doctor.
BTW...I would gladly do a fresh install but I want many of the old apps I have on the current drive. Replacing them would be a real pain.

#3398 | jinzouningen | Hello guys! I'm new in this forum and I want to ask you a question. I have a baytrail tablet which comes with windows 8 and now I want to install windows xp on it. Is it possible? Can someone provide me a x86 windows xp vhd ready to test? Thanks and sorry for my english D:
#3399 | diderius6 | ⇗ @jinzouningen I put XP SP3 on a Lenovo Flex 10 (with Bay Trail cpu). But no Acpi, no 3D graphik, so it is not a good base for XP Dietmar
#3400 | jinzouningen | Thanks, I will try to do some tests BTW, we can find a way to get the graphic card to work ;D

#3401

gordo999

In a very recent post I described a problem where I am getting an 0x7B stop bsod just as windows starts, or is starting.
Discovered likely problem, I have no AHCI driver on my XP original install.
Well....duh!!!
I apparently have no means of running the SATA ports in IDE mode either since that option does not seem available in my BIOS. My options are AHCI or Intel's system. With the latter selected it keeps asking me to connect a bootable drive. Under CSM I can select oprom but that doesn't seem to help.
The other version of xp, upgraded with unofficial SP4, does have an AHCI iastor driver from Fernando and it boots all the way. I took the same setup files used in the SP4 slipstream disk that installed that version and put them on a floppy. I started the install disk, pressed F6 and the install stopped a bit later and asked me to select the AHCI driver, which I did. It claims to have installed them but there is nothing in the registry and no iaStor.sys file in the XP\sys32\drivers directory, or anywhere else.
Is the F6 install not supposed to install the drivers permanently, or am I misunderstanding something? I am asking, because as the install proceeded, the installer claimed to be loading an iaStor driver, after the F6 install. I could hear the floppy drive reading as it did. However, I hit an 0x7B soon after when it was indicated that windows was starting.
Looks like I'll have to manually load the drivers via the registry.

#3402

diderius6

⇗ @gordo999
I make strange experiance with F6 on newer motherboards and XP SP3.
Yes, always after F6 the driver is loaded but this does not mean, that this driver works.
The STORAHCI driver can be integrated to registry very easy, just look in forum here for
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (211)
Dietmar

#3403

Gelip

To avoid displaying messages about unsigned drivers during WinXP installation, you need to add the following entry to the winnt.sif file on F6 floppy:

    [Unattended]
    DriverSigningPolicy=Ignore

#3404 | diderius6 | ⇗ @Gelip Does this method also works on the installation of XP SP3 via CD Dietmar
#3405 | Gelip | ⇗ @diderius6 It should not matter if the winnt.sif file is on an F6 floppy disk or on a CD in I386 or AMD64

## Page 228

#3406 | infuscomus | ⇗ @diderius6 works for me

#3407

genieautravail

> Zitat von ⇗ diderius6 im Beitrag ¶ #3392

> @genieautravail
> Here is fresh modded acpi.sys
> against BSOD A5, 0x0000000D
> Dietmar

YES, IT WORKS!
Here some screenshots just after the first start of XP (after sysprep of course) :
⇗
⇗
⇗
The missing drivers :
SM bus controller:
PCI\VEN_1022&DEV_790B&SUBSYS_790B1022&REV_4A\3&11583659&0&A0
USB bus controller:
PCI\VEN_1022&DEV_7914&SUBSYS_79141022&REV_20\3&11583659&0&80
PCI coding/decoding controller:
PCI\VEN_1022&DEV_1578&SUBSYS_15781022&REV_00\3&11583659&0&40
Video controller:
PCI\VEN_1002&DEV_9874&SUBSYS_1C401002&REV_C4\3&11583659&0&08
For the USB controller, I have found (but no tried yet) a driver on the driverpacks solutions website :
⇗ https://drp.su/en/hwids/PCI%5CVEN_1022%26DEV_7914
For the PCI coding/decoding controller, I have found (but no tried yet) a forced driver (for Windows 10 ?) on the driverpacks solutions website :
⇗ https://drp.su/en/hwids/PCI%5CVEN_1022%26DEV_1578
For the video controller , I have found (but no tried yet) a forced driver (for Windows 10 ?) on the driverpacks solutions website :
⇗ https://drp.su/en/hwids/PCI%5CVEN_1002%2...61103C%26REV_E6
For the SM bus controller, I have found (but no tried yet) a forced driver (for Windows 10 ?) on the driverpacks solutions website :
⇗ https://drp.su/en/hwids/PCI%5CVEN_1022%26DEV_790B
Others ideas for the drivers ?

#3408 | infuscomus | ⇗ @genieautravail for VGA you could try the R9 270 XP drivers and add the HWID to the inf? ⇗ https://www2.ati.com/drivers/13-12_xp32_dd_ccc.exe
#3409 | genieautravail | Thank you for the link! But your link doesn't works (for the moment ?)...
#3410 | diderius6 | ⇗ @skullteria ⇗ Dietmar ⇗ https://docs.microsoft.com/en-us/windows...rectedfrom=MSDN

#3411

IntiMD

> Zitat von ⇗ infuscomus im Beitrag ¶ #3408

> @genieautravail
> for VGA you could try the R9 270 XP drivers and add the HWID to the inf?
> ⇗ https://www2.ati.com/drivers/13-12_xp32_dd_ccc.exe

> Zitat von ⇗ genieautravail im Beitrag ¶ #3409

> Thank you for the link!
> But your link doesn't works (for the moment ?)...

It should work when downloading the file through wget: 'wget "https://www2.ati.com/drivers/13-12_xp32_dd_ccc.exe" --referer=drivers.amd.com --content-disposition'

#3412 | infuscomus | ⇗ @genieautravail scroll down to XP section ⇗ https://www.amd.com/en/support/previous-...d-radeon-r9-270

#3413

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3375

> vista beta 5365 works on my AB350 gaming K4 Ryzen motherboard - no A5 BSOD
> do you think you can remove those missing imports without breaking it?

Sorry, too many missing imports with endless calls.
That could take months and may not even work as there are too many code changes, not just ACPI interpreter ones.
I think is easier to implement most used opcodes in original ACPI.SYS than patch beta versions.

#3414

daniel_k

> Zitat von ⇗ genieautravail im Beitrag ¶ #3407

> > Zitat von ⇗ diderius6 im Beitrag ¶ #3392

> > @genieautravail
> > Here is fresh modded acpi.sys
> > against BSOD A5, 0x0000000D
> > Dietmar

> YES, IT WORKS!

I'll apply those changes to my last ACPI.SYS x86 and x64.
Great work, guys!

#3415 | daniel_k | ⇗ @diderius6, what were you doing when the system BSOD'ed? That's an unusual error. AMD or Intel system?
#3416 | genieautravail | ⇗ @IntiMD Done (97 MB)!
#3417 | daniel_k | ⇗ @genieautravail AMD USB 3.0 driver 1.1.0.145 ⇗ http://ftp.hp.com/pub/softpaq/sp64501-65000/sp64533.exe That is the last supporting XP. Link is from HP, but the driver is generic, just unpack and install.

#3418

daniel_k

⇗ @canonkong, ⇗ @diderius6, ⇗ @infuscomus
Hey guys.
Just learned something interesting about the XHCI drivers.
Some settings may crash the drivers. You may think they are incompatible, but that is now always the case.
For example, the TI driver.
It is a nice driver, supporting PAE properly and is not a WDF crappy driver, which means it can be used to install XP from USB.
Works just fine with VIA VL805/VL806 controllers, as long as the DataPumpXhcdWiringValue registry setting is not present.
This is a really nice find, as cards with those controllers are the cheapest ones and can be found anywhere.
So, please delete all registry settings and try the drivers again, may be this helps with crashing.

#3419

genieautravail

> Zitat von ⇗ daniel_k im Beitrag ¶ #3417

> @genieautravail
> AMD USB 3.0 driver 1.1.0.145
> ⇗ http://ftp.hp.com/pub/softpaq/sp64501-65000/sp64533.exe
> That is the last supporting XP.
> Link is from HP, but the driver is generic, just unpack and install.

Thank you very much!

#3420

daniel_k

⇗ @Mov AX, 0xDEAD
Just confirmed that the either:
- AMD drivers are poorly coded
- MCCI's drivers are properly coded and/or include workarounds to support PAE.
Tried AMD drivers on VIA VL805 card, same issues with NTVDM crashing.
Tried TI drivers written by MCCI, absolutely no issues on Server 2003 Enterprise/Datacenter and XP with "ours" patched NTOSKRNL/HAL unlocked PAE.

## Page 229

#3421 | infuscomus | ⇗ @daniel_k I've already seen some crashes, got a D0 BSOD on AMD Ryzen using AMD USB 3.0 driver 1.1.0.145 - this was from an attempt at loading it in XP setup textmode, no registry keys applied to the driver though.
#3422 | diderius6 | ⇗ @daniel_k I will tell you later about new project:)). Do you have Symbols for XP 64 SP1 (1830) Dietmar
#3423 | daniel_k | ⇗ @diderius6 UEFI, maybe? No, maybe I have symbols for SP2, not sure.

#3424

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3420

> @Mov AX, 0xDEAD
> - AMD drivers are poorly coded
> - MCCI's drivers are properly coded and/or include workarounds to support PAE.

Thank for info
Myself experince:
- Intel usb3 for windows7 has missing imports but can be modded to run on windows xp. Driver itself has problems, it can init hub after installing
- VIA drivers has deferred initialization of devices and have issue with USB BULK mode (ofter drop link to usb devices), only ISO mode works, but this mode is very CPU expensive

#3425

IntiMD

> Zitat von ⇗ diderius6 im Beitrag ¶ #3422

> @daniel_k
> I will tell you later about new project:)).
> Do you have Symbols for XP 64 SP1 (1830)
> Dietmar

A nitpick, but an important one. the RTM build of XP Professional x64 Edition is based on Server 2003 SP1 - ⇗ https://www.thecollectionbook.info/builds/windows/build/225
Something that might be interest, MSDN includes the debug/checked build of XP Pro x64 Edition RTM by the filename "en_windows_xp_professional_x64_chk.iso" and the SHA-1 hash of "45f2a3ec578c4f7095e60439d9af5bcaebe57fd9" of size 628MB. Consult 'the eye' for more info.

#3426

Mattiwatti

> Zitat von ⇗ IntiMD im Beitrag ¶ #3425

> Something that might be interest, MSDN includes the debug/checked build of XP Pro x64 Edition RTM by the filename "en_windows_xp_professional_x64_chk.iso" and the SHA-1 hash of "45f2a3ec578c4f7095e60439d9af5bcaebe57fd9" of size 628MB. Consult 'the eye' for more info.

Beware that this ISO is only bootable without modifications if a kernel debugger is attached from the very first boot (meaning to text mode setup) so that you can catch and ignore debug asserts. The reason for this is acpi.sys triggering several asserts at boot time, on every boot. If you replace acpi.sys there is no issue since the other drivers do not (normally) trigger kernel asserts. It is also possible to integrate the checked build of SP2, the file for this is "WindowsServer2003.WindowsXP-KB914961-SP2-x64-DEBUG-ENU.exe". I can't remember off hand whether this version also has a poorly behaved acpi.sys, but I think so because I eventually just patched out the entire assert in ntkrnlmp.exe that acpi.sys was triggering since it was getting tiresome.

#3427

Gelip

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3423

> UEFI, maybe?

I'm interested in WinXP x64 under UEFI. Do you follow the topic on ⇗ https://www.betaarchive.com/forum/viewto...20327&start=100 ?
I do various tests. WinXP x64 SP2 can be run under UEFI from MBR or GPT partition. There is only a problem with the video driver. All other drivers work - ethernet, wifi, audio, usb, sata

#3428

diderius6

⇗ @Gelip
Thanks a lot,
installing "Symbols" and at once I found the problem with Windbg
OVERLAPPED_MODULE: Address regions for 'dump_iaStor' and 'imapi.sys' overlap
Dietmar

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MmLoadSystemImage+10d6
    fffff800`01528976 488b4e30 mov rcx,qword ptr [rsi+30h]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MmLoadSystemImage+10d6

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 42435bd5

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0x0_nt!MmLoadSystemImage+10d6

    BUCKET_ID: X64_0x0_nt!MmLoadSystemImage+10d6

    Followup: MachineOwner

#3429 | diderius6 | ⇗ @skullteria ⇗ https://j00ru.vexillium.org/2010/06/insi...re-enforcement/ Dietmar PS: On x64-based versions of the operating system, kernel-mode drivers must be digitally signed. I think, it can be hacked in ntoskrnl.exe.

#3430

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3429

> @skullteria
> ⇗ https://j00ru.vexillium.org/2010/06/insi...re-enforcement/
> Dietmar
> PS: On x64-based versions of the operating system, kernel-mode drivers must be digitally signed.
> I think, it can be hacked in ntoskrnl.exe.

Or if you use modded winload.exe or winload.efi from beta Server Longhorn 16497: ⇗ winload.efi ⇗ winload.exe

#3431

canonkong

⇗ @daniel_k
I had tested the TI driver for DEV_ID: 149C , but it can not work for the USB DISK on win7.
For AMD X570 and ryzen 3000 CPUs' XHCI, only Etron MOD driver can work well.
VIA also can work well, but it will 0X0000001E BSOD sometime.
ASMedia, AMD 1.0.5.3 and TI drivers can not work for USB DISK.
INTEL 5.0.5.43 and AMD 2.0.0.48 drivers will 0X0000002C BSOD sometime. (This two drivers can work well for most all USB devices but AMD 149C.).
Fresco Logic USB Driver can not install the hub driver.
Renesas USB driver will BSOD when you install xhci driver.
I tried again and again, but can not found a way to solve the BSOD problems or made the USB DISK work.

#3432

XPLives

⇗ @genieautravail

> Zitat von ⇗ genieautravail im Beitrag ¶ #3409

> Thank you for the link!
> But your link doesn't works (for the moment ?)...

Use this link instead.
⇗ https://www.amd.com/en/support/graphics/...-radeon-hd-6570
Then select "Windows XP - Professional/Home"
Revision Number
14.4
File Size
179 MB
Release Date
4/25/2014
Then click the DOWNLOAD button link which goes to:
⇗ https://www2.ati.com/drivers/14-4-xp32-64-dd-ccc-pack2.exe
For whatever reason you can't hotlink download so you must use the first link to get to the page.
To Whom It May Concern:
Dual Brand Graphics Card Users
I also found a nasty bug. When using both nVidia and AMD XP drivers it cause the nVidia card to BSOD when accessing 3D graphics. After going back to a cleaner image before any graphics drivers it was fine. So if you want to use the AMD graphics driver only and no nVidia. Both cards work fine on a clean install using just their own driver. So don't attempt installing both cards. If you do install both cards' drivers only the AMD will always work properly.
As far as performance nVidia will probably be the strongest in XP.

#3433

XPLives

⇗ @canonkong

> Zitat von ⇗ canonkong im Beitrag ¶ #3431

> @daniel_k
> I had tested the TI driver for DEV_ID: 149C , but it can not work for the USB DISK on win7.
> For AMD X570 and ryzen 3000 CPUs' XHCI, only Etron MOD driver can work well.
> VIA also can work well, but it will 0X0000001E BSOD sometime.
> ASMedia, AMD 1.0.5.3 and TI drivers can not work for USB DISK.
> INTEL 5.0.5.43 and AMD 2.0.0.48 drivers will 0X0000002C BSOD sometime. (This two drivers can work well for most all USB devices but AMD 149C.).
> Fresco Logic USB Driver can not install the hub driver.
> Renesas USB driver will BSOD when you install xhci driver.
> I tried again and again, but can not found a way to solve the BSOD problems or made the USB DISK work.

CanonKong, which of these do you think are the top 3 best for Intel USB 3.0 use? Or can you list the weaknesses/issues of these for Intel USB 3.0 on XP 32-Bit use?
Using real USB 3.0 PCIe cards the TI USB 3.0 xHCI driver is the best performing overall as I mentioned to Daniel_K. If you need to mod one successfully that is the best choice in performance. At least on the USB 3.0 PCIe cards comparison random seek times was the lowest latency. You can compare this to a fast car that also brakes the quickest. So if you enjoy skipping around large HD videos you find this most pleasurable. Delays were as low as 0.5 seconds. Other brands could be as high as 2.0 seconds in delay.
If you're just copying large data only NEC performed the best times but overall all USB 3.0 xHCI cards are very close within a few percentage of each other.
How modding the TI USB 3.0 driver to work on the Intel or AMD USB 3.0 ports will affect the driver performance is unknown compared to the real USB 3.0 PCIe cards. But if anyone successfully modifies the TI USB 3.0 for XP 32-Bit and can access the USB hard drive, USB webcam, USB audio, USB mouse, USB keyboard, USB floppy, USB printer, and USB optical disc drive successfully without any connection issues is the winner. Then I can conduct a true USB 3.0 modded Intel, AMD, vs. PCIe card benchmark comparison.

#3434

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3401

> In a very recent post I described a problem where I am getting an 0x7B stop bsod just as windows starts, or is starting.
> Discovered likely problem, I have no AHCI driver on my XP original install.
> Well....duh!!!
> I apparently have no means of running the SATA ports in IDE mode either since that option does not seem available in my BIOS. My options are AHCI or Intel's system. With the latter selected it keeps asking me to connect a bootable drive. Under CSM I can select oprom but that doesn't seem to help.
> The other version of xp, upgraded with unofficial SP4, does have an AHCI iastor driver from Fernando and it boots all the way. I took the same setup files used in the SP4 slipstream disk that installed that version and put them on a floppy. I started the install disk, pressed F6 and the install stopped a bit later and asked me to select the AHCI driver, which I did. It claims to have installed them but there is nothing in the registry and no iaStor.sys file in the XP\sys32\drivers directory, or anywhere else.
> Is the F6 install not supposed to install the drivers permanently, or am I misunderstanding something? I am asking, because as the install proceeded, the installer claimed to be loading an iaStor driver, after the F6 install. I could hear the floppy drive reading as it did. However, I hit an 0x7B soon after when it was indicated that windows was starting.
> Looks like I'll have to manually load the drivers via the registry.

SATA IDE Compatibility Mode has been gone since SkyLake so say good bye to that. You want that mode you'll need to go back to Z97.
Too many messages to sort through but I believe you are on an Intel Coffee Lake 300 Series motherboard.
The F6 method was meant for real internal floppy disk drives although it is possible to use USB floppy drives on real eHCI USB 2.0 ports which no longer exist on SkyLake 100 Series+.
First you cannot use the floppy drive method which I can only assume you are using a USB floppy drive since no onboard FDD controller anymore since Ivy Bridge. It might read the driver but because eHCI no longer exists since SkyLake the driver will not successfully load even though it appears to have loaded something on the floppy disk before BSOD 7B later.
The easiest way at least for you would be nlite the SATA AHCI driver from Intel. Don't mix with the ReactOS STORAHCI driver. You don't need that driver if you are using Intel motherboards. That should only be used for AMD if you aren't using Asmedia SATA ports or unless you are using a NVME then you will need STORAHCI. Personally you should use the K.I.S.S. method and I also suggest you don't need the SP4. I don't know if you're adding that due to paranoia of getting hacked or what then just don't install the driver to your ethernet or WIFI. I'd use SP2 or SP3 integrated on a clean ISO such as XPP SP0 with just the Intel SATA driver only integrated with nLite and install XP to a completely new partition unless you wish to override your old one then you should copy the contents and back it up first before formatting that partition before using it. XP allows you to install it to as many new partitions if you need if you wish to preserve your older XP installation. You'll have to modify the BOOT.INI to give the description to distinguish between the partitions when choosing which one to boot.
Later after you successfully installed XP you can run the unofficial SP4 update inside Windows XP desktop. That is the best way. Don't forget to include the modded ACPI.sys during the setup phase which may need to be copied a couple times if you plan on using ACPI. It's much easier to install XP to a FAT32 partition and have a bootable DOS floppy to do this or have a bootable 98SE DOS partition on the drive itself - Best Method. The other way is to disconnect your drive and hook it up to another machine if you're using NTFS.

#3435

LoneCrusader

⇗ @daniel_k, ⇗ @Mov AX, 0xDEAD
RE: modifying TI USB3 drivers
I assume you guys are already aware of this, but at least one set of .PDB files for the TI drivers were leaked at some point. These were the only .PDB files I've ever been able to turn up for any of the manufacturer's XP USB3 drivers. I don't know how much the code may have changed since the version with .PDB files, but maybe they will be helpful in deciphering some of the code. Here's the link:
⇗ https://www.helpjet.net/Fs-14515117-2670...16-extract.html

## Page 230

#3436

XPLives

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3077

> On the Q1900m board, the Celeron CPU J1900 (soldered on socket all in one chip SoC),
> I can install MPS Multiprocessor which shows also (as on acpi) 4 cpu cores, because this chip has 4 cores
> and no Hyperthreading. On this Bios is an extra MPS table, on the Lenovo Flex 10 is no MPS table as RW-everything tells.
> In MPS the sound works. Interesting, from where the devices get their information on MPS,
> because no acpi.sys there, which looks at DSDT table. But the DSDT table is still needed,
> compi does not start, when you delete DSDT or give fake empty DSDT.
> I will make a speed comparisation ACPI against MPS (all Multiprocessor).
> With full ACPI, strange things happen on this board:
> Windbg via COM1 runs only correct in Safe Mode (F8) and no sound.
> A yellow questionmark is at partmgr in Device Manager. This I do not understand at all,
> because without loaded partmgr.sys the compi does not start but it starts
> Dietmar
> PS: In MPS there are 2 yellow marks at pci-to-Pci bridge, reclaiming not enough free resources
> even the IRQs from MPS go up to 128 and noone is double.
> This may be a hint, what is really going on in the SoC, may be something is shared there.
> All boards with such a SoC cpu have absolut identic devices, because they are all integrated in this SoC chip.
> This is very nice, when you compare compis with the same SoC cpu.
> I do not like, that I can not change the cpu. But I think, that there is no cheaper and better board today on the market.
> It is to 100% silent, passiv cooling and SSD, power consumption around 10 Watt.
> Now I just get 155 updates from Posready^^.
> EDIT: Now I have also sound on full ACPI Multiprocessor XP SP3 on the Q1900m board. For this I have to disable "Microsoft UAA-Bustreiber für High Definition Audio"
> in Device Manager and after this to enable "Microsoft UAA-Bustreiber für High Definition Audio" again, crazy. It has to do with not enough resources. USB2, 3, Lan, sound works now there. The only device is the integrated GPU, which does not work
> under XP SP3 even I make hack. Windbg works now also normal, after I deactivated the 2 pci-to-Pci bridges, reclaiming not enough free resources. Now I benchmark full ACPI Multiprocessor against MPS Multiprocessor.
> I use for this Nvidia GT 730. The bottleneck is here the CPU J1900.
> 3DMark2001 Acpi: 17347 Cinebench 11.529: 1.37
> 3DMark2001 MPS: 15739 Cinebench 11.529: 1.33
> So, Acpi is faster than MPS, even I do not know why. 1440 HD Video runs normal.
> Commander Keen 4 runs in full screen modus^^. Prime95 and other Benchmarks all together show: XP SP3 runs absolut stable on the Q1900m board in full ACPI Multiprocessor mode.
> Hihi:
> "Intel ® Bay Trail platform does not support:
> Win XP Pro 32bit
> Windows Embedded Standard 2009 (XPe SP3) 32bit "
> And just for fun: I do pur USB boot on the Q1900m board via USB3 port and the nice driver from @daniel_k , so
> no more problems with iastor or storahci^^
> ⇗

> Zitat von ⇗ diderius6 im Beitrag ¶ #3077

> On the Q1900m board, the Celeron CPU J1900 (soldered on socket all in one chip SoC),
> I can install MPS Multiprocessor which shows also (as on acpi) 4 cpu cores, because this chip has 4 cores
> and no Hyperthreading. On this Bios is an extra MPS table
> I will make a speed comparisation ACPI against MPS (all Multiprocessor).
> I do not like, that I can not change the cpu. But I think, that there is no cheaper and better board today on the market.
> It is to 100% silent, passiv cooling and SSD, power consumption around 10 Watt.
> Now I benchmark full ACPI Multiprocessor against MPS Multiprocessor.
> I use for this Nvidia GT 730. The bottleneck is here the CPU J1900.
> 3DMark2001 Acpi: 17347 Cinebench 11.529: 1.37
> 3DMark2001 MPS: 15739 Cinebench 11.529: 1.33
> So, Acpi is faster than MPS, even I do not know why. 1440 HD Video runs normal.

Dietmar provided nice idea to benchmark ACPI vs NO ACPI MPS Multiprocessor.
This I used i5-8400 downclock to 792 MHz. Reduced CPU cores from 6 to 2.
I used Server 2003 32-Bit OS instead.
Now is it fair? :) We shall see...
Most of these tests and more were done about 2 weeks ago over a 1 week period. Then the wild fires and PGE safety black out caused havoc here so I did not post sooner.
To be quick and clear. The conclusion is incorrect that Dietmar discovered. I found at first the MPS Multiprocessor results were slightly better. But after a few tests I find that both MPS Multiprocessor Mode and APCI Modded ACPI.SYS from Daniel_K showed nearly identical results.
Note: I did not test on Hyperthreaded CPU. All 2 Cores are 2 Cores / 2 Threads on i5-8400. Later it would be interesting to see CPU with 2 Cores 4 Threads test vs 2 Cores 2 Threads if any difference in benchmarking if ACPI with hyperthreading has any advantage.
However as a follow up I would be interested if Dietmar has a Kill-A-Watt to measure total wattage of PSU connected to Motherboard how much it draws from outlet minus Monitor.
I think it will be much higher than 10 Watts for combined Motherboard and PSU connected total watts usage.
Okay now down to the actual results.
I used an nVidia GT 710 PCIe 2GB model for the test which is much worse than Dietmar's GT 730 which is better. :(
But still the results I found interesting even with dual cores for both ACPI and MPS Mode.
i5-8400 (Dual Cores) Enabled of 6.
792 MHz
[3DMark03 Score] DK_ACPI / MPS
20306
[CineBench Benchmark v11.529]
OpenGL
19.62 FPS
vs Dietmar Q1900 Benchmark
Quad-Core Processor J1900
⇗ https://ark.intel.com/content/www/us/en/...o-2-42-ghz.html
2000 MHz / 2420 MHz Boost
3DMark2001 ACPI: 17347
3DMark2001 MPS: 15739
[CineBench Benchmark v11.529]
ACPI: 1.37 FPS
MPS: 1.33 FPS
I just noticed Dietmar used 3dMark2001 which uses DX 8.1. I used 3DMark03 which uses DX 9.0c. But I would also think scores should be higher on 3DMark2001 than 3DMark2003?
I have also tested multiple cores from 2-6 on MPS Mode but will need time to do comparison of all results before reporting those benchmarks and power consumption.
So in conclusion my tests on modern hardware Z370 showed even on an inferior GT 710 the Benchmark scores were much higher even on a downclocked 792MHz and 6 Cores reduced to 2 Cores setup and showed that ACPI vs NO ACPI MPS Multiprocessor Mode to be a tie or very close within margin of error.
Maybe Dietmar can redo the same tests on Q1900 and also on modern motherboard and will find similar results using 3DMark01 and 3DMark03.
Although the Q1900 results seems fishy why the results are so different since the CPU has no hyperthreading capability to be a possible reason for the performance difference.
If Dietmar has older GT 710 model to test that would be interesting on Q1900.

> Zitat von ⇗ diderius6 im Beitrag ¶ #3077

> Hihi:
> "Intel ® Bay Trail platform does not support:
> Win XP Pro 32bit
> Windows Embedded Standard 2009 (XPe SP3) 32bit "

This was before modded ACPI.sys but MPS would have worked and proven XP could work on Baytrail at least on a desktop motherboard model. MPS Mode should also work on Baytrail laptop model but you state no MPS table? What happens when you install with F7 method on Baytrail laptop? Does it go to Standard PC?
But hihi - yes Intel is wrong again.

#3437

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3434

> SATA IDE Compatibility Mode has been gone since SkyLake so say good bye to that. You want that mode you'll need to go back to Z97.
> Too many messages to sort through but I believe you are on an Intel Coffee Lake 300 Series motherboard.

@XPLives...thanks for the valuable info re my problem. I am running an Asus B360M which is Coffee Lake. Don't want the mode, I am on a learning curve and thought XP might need it to boot.

> Zitat von ⇗ XPLives im Beitrag ¶ #3434

> First you cannot use the floppy drive method ...the driver will not successfully load even though it appears to have loaded something on the floppy disk before BSOD 7B later.

Wondered about that, I have just been exhaustively through the registry and there is no sign of iaStor. The SP4 update did add it and reg entries to a working version of xp and I am cloning everything re registry and drivers from the good copy to my copy with the apps I need.
The reason I tried SP4 had nothing to do with paranoia about being hacked, I thought it might provide drivers for the modern mobo which it does. There is a signed version by Fernando for ahci drivers which I am hoping to transfer.

> Zitat von ⇗ XPLives im Beitrag ¶ #3434

> Later after you successfully installed XP you can run the unofficial SP4 update inside Windows XP desktop. That is the best way. Don't forget to include the modded ACPI.sys during the setup phase ...

I used Dietmar's modded acpi.sys and it seems to have gotten me past the 0xA5 error. I used the Driver Packs site on a version of Win 7 on the same mobo. It supplied a few drivers I needed and made W7 solid on this mobo. Don't know if they have anything for XP.
Just looking in the SP4 working version for an ACPI reference under HKLM\system\ccs\enum but I see no signs of an acpi section. Just looking up Dietmar's post where he included some registry stuff.
I really just want to get it going. I really enjoyed seeing the old Windows XP boot screen but I got the 0x7b error about that point. Then, I'd like to check out some of the mods you guys are doing.

#3438 | Andalu | ⇗ @genieautravail you can also try this: ⇗ https://archive.org/details/icafe-winxp-...-br294594-sep24 It should be the latest ATI display driver for WinXP 32-bit.

#3439

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3159

> this morning I make the ultimative ACPI test for the EVGA dark z390 board.

⇗ @diderius6
Dietmar...your drivers (storahci) got me further along the boot sequence. I have now reached a screen informing me that my hardware has changed and they are nagging me to reactivate within 3 days. However, the system seems unstable at this point. If I hit yes to activate or no to bypass activation, the nag screen disappears for 20 seconds then re-appears, having done nothing.
I was reading an article on how ro reset some of the licensing files, like licdll.dll, but I can't get into safe mode. I reach the safe mode screen with the safe mode boxes in each corner but the screen flashes regularly and does nothing.
I would like to slipstream your drivers into my XP SP3 install disk but I'll need to research that.
BTW...found a neat way to enter a reg file into an offline system. You probably know about it. In the W7 registry, you can highlight the HKLM key then use Load Hive from the File menu to load a hive from windir\sys32\config in the offline OS registry.
I selected the 'system' hive, for example, and a box appeared asking me to name it. I called it winxp sys and it loaded the hive under HKLM with that name. That hive can now be edited freely. Must remember to unload the hive when finished.
With your reg file, I edited it to replace references to 'system' in HKLM\system with 'winxp sys'. Therefore, the reg entry would be HKLM\winxp sys instead of HKLM\system.
Then I changed your control set number to my default ccs which is ccs003. Then I went back to the W7 reg, highlighted the winxp sys hive, and activated Import from the File menu. I pointed it to your edited file and it imported your reg data into my win xp hive.
This was all done in a text editor with a search/replace tool.
Saves a lot of grief.

#3440

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3437

> > Zitat von ⇗ XPLives im Beitrag ¶ #3434

> > SATA IDE Compatibility Mode has been gone since SkyLake so say good bye to that. You want that mode you'll need to go back to Z97.
> > Too many messages to sort through but I believe you are on an Intel Coffee Lake 300 Series motherboard.

> @XPLives...thanks for the valuable info re my problem. I am running an Asus B360M which is Coffee Lake. Don't want the mode, I am on a learning curve and thought XP might need it to boot.

> > Zitat von ⇗ XPLives im Beitrag ¶ #3434

> > First you cannot use the floppy drive method ...the driver will not successfully load even though it appears to have loaded something on the floppy disk before BSOD 7B later.

> Wondered about that, I have just been exhaustively through the registry and there is no sign of iaStor. The SP4 update did add it and reg entries to a working version of xp and I am cloning everything re registry and drivers from the good copy to my copy with the apps I need.
> The reason I tried SP4 had nothing to do with paranoia about being hacked, I thought it might provide drivers for the modern mobo which it does. There is a signed version by Fernando for ahci drivers which I am hoping to transfer.

> > Zitat von ⇗ XPLives im Beitrag ¶ #3434

> > Later after you successfully installed XP you can run the unofficial SP4 update inside Windows XP desktop. That is the best way. Don't forget to include the modded ACPI.sys during the setup phase ...

> I used Dietmar's modded acpi.sys and it seems to have gotten me past the 0xA5 error. I used the Driver Packs site on a version of Win 7 on the same mobo. It supplied a few drivers I needed and made W7 solid on this mobo. Don't know if they have anything for XP.
> Just looking in the SP4 working version for an ACPI reference under HKLM\system\ccs\enum but I see no signs of an acpi section. Just looking up Dietmar's post where he included some registry stuff.
> I really just want to get it going. I really enjoyed seeing the old Windows XP boot screen but I got the 0x7b error about that point. Then, I'd like to check out some of the mods you guys are doing.

> > Zitat von ⇗ gordo999 im Beitrag ¶ #3437

> > [quote=XPLives|p3434]
> > SATA IDE Compatibility Mode has been gone since SkyLake so say good bye to that. You want that mode you'll need to go back to Z97.
> > @XPLives...thanks for the valuable info re my problem. I am running an Asus B360M which is Coffee Lake. Don't want the mode, I am on a learning curve and thought XP might need it to boot.
> > [quote=XPLives|p3434]
> > Wondered about that, I have just been exhaustively through the registry and there is no sign of iaStor. The SP4 update did add it and reg entries to a working version of xp and I am cloning everything re registry and drivers from the good copy to my copy with the apps I need.
> > The reason I tried SP4 had nothing to do with paranoia about being hacked, I thought it might provide drivers for the modern mobo which it does. There is a signed version by Fernando for ahci drivers which I am hoping to transfer.

Again totally unnecessary to need SP4. It might only have some additional security updates but nothing that would increase compatibility with games. It's also possible any new updates are not tested for any possible compatibility conflicts. There are no new drivers that you can't download yourself off say nVidia or whatever vendor. Again it's better to NOT integrate a massive driver pack into your install disc. I know it may seem like a good idea but later you will find it isn't when constructing your first installation disc.
I went ahead and renamed my older XP 32-Bit support thread that already was renamed before but I decided to modify the SATA AHCI package that Fernando had uploaded but I found there's too much going on in there and simplified the nLite package for integration to an optical disc.
Forget the SP4, just use a clean XP SP0, 1, 2, or 3 or get XP SP0 and integrate the SP into it using nLite before integrating the SATA AHCI driver. If you need to add more drivers later I recommend you just don't install or integrate them but just manually install them "AFTER" XP is fully booted to the desktop and installed. You are also better off imaging the clean installation before adding any drivers. The only driver that should be integrated is just the SATA AHCI from Intel and that's it. Once you add all that other crap into the registry it's a pain to remove it which is why a clean image after you've installed it without the bloat you can restore again later if you corrupt it.
Then you can start adding the graphics drivers, sound, network, et cetera. Image your OS partition again.
Finally install all your software applications. Image your OS partition again.
That's the best way in case you want to avoid reinstalling everything from scratch or go to an even cleaner OS before drivers / applications installed.
I put the modified SATA AHCI driver here in my old renamed thread.
⇗ Windows 32-Bit OS iNTEL SATA & Gaming Discussions 2000 XP 2003 2009
Just download the file there called:
XP 32-Bit and Server 2003 32-Bit SATA AHCI Driver - Fernando MOD.ZIP
Make sure you pick the correct Hardware ID to integrated that matches your Intel SATA AHCI Hardware Device ID.
If you don't know it then boot into Windows Vista or later.
Copy and paste all the Hardware ID fields for:
Device Instance ID:
Hardware IDs:
Compatible IDs:
Matching Device ID:
I could then construct one specific to your motherboard.
And make sure you at least got a PS/2 keyboard hooked up to your PS/2 keyboard - NO USB ones.
Later if you require a USB mouse you can try using your PS/2 keyboard and install one of the USB 3.0 modded drivers or get a real USB 3.0 PCIe card and install their XP driver. If it's too difficult then get a USB 2.0 PCIe card which usually has built in drivers to work with XP.
The speed difference between USB 2.0 and USB 3.0 I found is around 5 times roughly in XP and Server 2003.
If you don't want to deal with the modded ACPI. - Again in my own tests the best one so far is Daniel_K's. Although Dietmar might have a better one now I just have not had time to test every one of them.
I can tell you the NO ACPI MPS Multiprocessor method works with everything I have tested despite the loss of ACPI related functions. This method works best on Intel CPUs and NOT AMD which may lack a MPS Table so may install as a Standard PC with just 1 core.

#3441

XPLives

> Zitat von ⇗ Andalu im Beitrag ¶ #3438

> @genieautravail
> you can also try this:
> ⇗ https://archive.org/details/icafe-winxp-...-br294594-sep24
> It should be the latest ATI display driver for WinXP 32-bit.

Never tested this but saw this iCafe driver a while back. It might work better on the newer AMD R9 series than the v14.4. So far no one willing to test their R9 to see if it works.

#3442

Mov AX, 0xDEAD

> Zitat von ⇗ LoneCrusader im Beitrag ¶ #3435

> I assume you guys are already aware of this, but at least one set of .PDB files for the TI drivers were leaked at some point.

Wow, rare find !
this version 1.16.3 is not last, but PDB make it very valuable

#3443

daniel_k

⇗ @Mov AX, 0xDEAD
The TI driver gives the following error on Intel controllers:
This device is disabled because the firmware of the device did not give it the required resources. (Code 29)
As this driver works with VIA, which in turn works with the same AMD driver which works with Intel, is most probably compatible.
There should be some "sanity" check somewhere.
If we could patch it, would make it the best driver ever.
Any ideas as to how the driver reports error 29? I believe the issue lies in tixhci.sys, which doesn't provide device resources to tihub3.sys.

#3444 | daniel_k | ⇗ @canonkong Sorry that it didn't help you. When you say "USB disk not work", what you mean exactly? The device is detected but doesn't work? Or device IDs are all 0 (zeros)?
#3445 | daniel_k | ⇗ @LoneCrusader Thanks you very much! Nice to see you here! I've seen a couple of driver with "leaked" PDBs sometimes, but never really pay attention to them.
#3446 | canonkong | ⇗ @daniel_k You can find the letter of the U disk in the computer, but it can't load the capacity and other information, or open the U disk to read the contents.
#3447 | daniel_k | ⇗ @canonkong All other devices, such as input devices (mouse/keyboard) work?

#3448

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #3443

> @Mov AX, 0xDEAD
> Any ideas as to how the driver reports error 29? I believe the issue lies in tixhci.sys, which doesn't provide device resources to tihub3.sys.

- error usualy generated by one of IRP request to driver
- i will check soon this driver on intel controller and give you more info
p.s. year ago i played with intel usb3 win7 driver to run it on winxp, this is log of irq request (DispatchPnp is irp handler):

    DriverAddDevice
    {
      ->BaseDeviceCreate
      ->XhcdCreateController
          ->XhcdInitializeParams
                     +DeferredRoutine_0
                     +DeferredRoutine_1
                     +DeferredRoutine_4
      ->MakeHostName
    }

    DispatchPnp (18 notsupport) IRP_MN_QUERY_LEGACY_BUS_INFORMATION

    DispatchPnp (0D {off[178]=0 result=0}) IRP_MN_FILTER_RESOURCE_REQUIREMENTS

    DispatchPnp (08 notsupport) IRP_MN_QUERY_INTERFACE

    DispatchPnp (08 notsupport) IRP_MN_QUERY_INTERFACE

    DispatchPnp (00 ->WorkerCreate{} IoCallDriver result=STATUS_PENDING) IRP_MN_START_DEVICE
       ->WorkerCreate
             +WorkerEvtRelease
             +IoQueueWorkItem(WorkerRoutine)

    WorkerRoutine
     ->FdoStartDeviceWorker
       ->FdoStartDevice
         ->FdoSendIrpSynchronously
         ->XhcdStartController
    {
          ->ManyCalls0

          ->XhcdInitResources(03 memory 81 private 02 irq)
            ->XhcdRegisterInterrupt
            ->XhcdInitMmIoSpace

          ->XhcdDmaCreate
            ->DispatchPnp (08 notsupport)

          ->XhcdCbmCreate
                     +XhcdCbmResizeEvtProc
            ->BaseThreadCreate
            ->BaseThreadStart
                       +BaseThreadStartRoutine
              ->PsCreateSystemThread

            ->KeSetBasePriorityThread
              ->BaseThreadStartRoutine
                ->XhcdCbmResizeEvtProc(suspend->WaitForSingleObject)

          ->XhcdCbmCreateAny
            ->XhcdCbmInflate (HalAllocateCommonBuffer align error)
               7x { push 7 pop esi mov 0x200, mov 0x1000 }

          ->XhcWaitHCReady
          ->XhcCheckExtendCap
          ->XhcReset
          ->XhcdCreateComBufManagement
          ->XhcdCreateDeviceManagement
            ->XhcdAllocPhyMemorySizeBoundary(HalAllocateCommonBuffer)
              ->XhcdAllocPhyMemoryPageBoundary(HalAllocateCommonBuffer)
          ->XhcdCreateTransferManagement
          ->XhcdCreatePortManagement
          ->XhcdCreateCmdProcess
            ->XhcdInitializeTrbRingParam
          ->XhcdCreateEventProcess
          ->XhcdCreateXferCapProcess
            ->XhcdXferCapThreadStart

          ->XhcdWatchThreadStart
            ->BaseThreadCreate
            ->BaseThreadStart
                         +BaseThreadStartRoutine
              ->PsCreateSystemThread

          ->XhcdTransferThreadStart
            ->BaseThreadCreate
            ->BaseThreadStart
                         +BaseThreadStartRoutine
              ->PsCreateSystemThread

          ->XhcStart

          ->XhcdInitializeController
            4x {
            ->BaseThreadStartRoutine
              ->ISRWorker2
              ->DeferredRoutine_1
                     }

    } ;XhcdStartController

         ->FdoReadPciConfig
         ->CreateRootHubDevice

           ->HubCreateUsbDevice
             ->XhcdSubmitUrb

           ->HubInitializeUsbDevice
             ->BaseThreadStartRoutine
             ->BaseThreadStartRoutine
             ->BaseThreadStartRoutine
             ->XhcdSubmitUrb
             ->XhcdSubmitUrb

         ->GetDeviceCapabilities
           ->DispatchPnp
         ->SomeProc3
         ->pXhcdUpdateCounter
         ->WatchThreadStart
         ->BaseDeviceProcessQueuedRequests
         ->FdoGetTopologyAddress
           ->DispatchPnp
    } ;FdoStartDevice
    ->WorkerEvtRelease

    DispatchPnp (09 res=103)
    DispatchPnp (14 res=103)
    DispatchPnp (07 res=103)
     ->FdoQueryDeviceRelations
       ->FdoPassDownLevels
         ->PdoPnp (09)
           ->PdoQueryCapabilities
             ->GetDeviceCapabilities
               ->DispatchPnp (09 res=103)
         ->PdoPnp (08 PdoQueryInterface notsupport)
         ->PdoPnp (08 PdoQueryInterface support)

#3449 | canonkong | ⇗ @daniel_k Yes, mouse and keyboard both can work.
#3450 | daniel_k | ⇗ @Mov AX, 0xDEAD Thanks for the info. In the mean time, I've managed to "re-add" XP support for last Intel compatible AMD driver 1.1.0.276 from Dec 2018. Too bad the fixes are just related to hub or sleep mode issues (expected, as you've proven that the driver has no issues with PAE on Win7).

## Page 231

#3451 | daniel_k | ⇗ @canonkong Interesting, will do some research later.

#3452

daniel_k

⇗ @Mov AX, 0xDEAD
By the way, the device check is simple.
Just change (unicode):

    PCI\VEN_104C&DEV_8241&*REV_02*

to

    PCI\*

#3453 | daniel_k | ⇗ @Andalu Hi, let's fix the USB3 working as USB2 issue? Got some nice ideas. Did you ever try to install the HCSwitch driver by hacking the INF file? Rename [HCSwitch_PCIF.NTx86.6.1] to [HCSwitch_PCIF.NTx86.5.1] and install the driver.
#3454 | Andalu | ⇗ @daniel_k sorry for the late of my reply. Do you mean HCSwitch from intel usb3 1.0.6.245 driver? If so, I got the error "the specified location does not contain information about your hardware"
#3455 | daniel_k | ⇗ @Andalu HCSwitch must be installed for the PCI Bus device under System Devices.
#3456 | Andalu | ⇗ @daniel_k I get the same message for PCI bus (hardware ID: *PNP0A08)

#3457

daniel_k

⇗ @Andalu
Huh, missed the following:
Replace the line
%STDDEV%=HCSwitch_PCIF,NTx86.6.1,NTx86.6.2
with
%STDDEV%=HCSwitch_PCIF,NTx86.5.1

#3458 | genieautravail | ⇗ @XPLives ⇗ @Andalu Thank you to everyone. I will try to install the drivers this week and I will let you know the results.
#3459 | Andalu | ⇗ @daniel_k the driver update works correctly but on the needed restart I got the bsod 7B (0xBACC3524, 0xC0000034, 0x00000000, 0x00000000) Edit: I just saw your updated post.. I'll try soon ;)

#3460

Andalu

⇗ @daniel_k
the driver update works only if also the line
[HCSwitch_PCIF.NTx86.6.1]
%XHCI.DeviceDesc%=HCSwitch, *PNP0A08
is modified to
[HCSwitch_PCIF.NTx86.5.1]
%XHCI.DeviceDesc%=HCSwitch, *PNP0A08
but on the restart I got the bsod 7B as before

#3461

daniel_k

⇗ @Andalu
Thought it would work right away, sorry.
Can you recover from this?
If not, do the following:
- Boot from another Windows, open Regedit.
- Select HKEY_LOCAL_MACHINE
- File menu -> Load Hive.
- Browse your XP drive and open \WINDOWS\system32\config\System
- Key name may be whatever, such as XP
- Open HKEY_LOCAL_MACHINE\XP\ControlSet001\Enum tree and search for iusb3hcs
- Delete the LowerFilters
- Select the XP tree, open File menu -> Unload Hive
- Boot XP as usual

#3462 | daniel_k | ⇗ @Mov AX, 0xDEAD Trying really hard to find, on VM where it triggers error code 29. On VM the driver loads fine, the "best" I could do was to get error 24 on hub.
#3463 | Andalu | ⇗ @daniel_k No problem, I have to thank you for your time ;) recovering an xp image is faster with a bootable media

#3464

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3440

> Forget the SP4, just use a clean XP SP0, 1, 2, or 3 or get XP SP0 and integrate the SP into it using nLite before integrating the SATA AHCI driver. If you need to add more drivers later I recommend you just don't install or integrate them but just manually install them "AFTER" XP is fully booted to the desktop and installed. You are also better off imaging the clean installation before adding any drivers. The only driver that should be integrated is just the SATA AHCI from Intel and that's it.

@XPLives....thanks again for detailed explanation. I am currently working on my old XP installation without SP4. I have made progress meantime using Dietmar's storahci driver setup. I am now able to boot to the XP boot screen and beyond. However, I am stuck at a nag screen for activation which appears before the logon screen.
If I press 'no' to not activate, the nag disappears for 20 seconds then re-appears. If I hit 'yes' same thing. So it's stuck in a loop of some kind.
If I boot into safe mode, everything is cool till the graphics appear. That is, I get a blank screen with the 'safe mode' boxes in each corner and it is stable but when the graphics appear for the desktop the screen starts blinking and stays that way. That suggests to me a graphics driver problem.
It's the same in the cmd prompt version of safe mode. It tries to load graphics.
With regard to the activation screen I have encountered a similar problem related to the Internet Explorer version. Windows needs IE for the activation process and if the IE version is wrong it stalls. As I recall the solution, you had to update the version from 6 to 8 but now I am reading you have to move it back to 6.
Any ideas on how to replace IE on an offline system?

> Zitat von ⇗ XPLives im Beitrag ¶ #3440

> Once you add all that other crap into the registry it's a pain to remove it which is why a clean image after you've installed it without the bloat you can restore again later if you corrupt it.
> Then you can start adding the graphics drivers, sound, network, et cetera.

I agree totally. However, my registry is loaded with crap I need to remove. I should likely have done it while XP was running on an older system but now I have changed partitions and removed some with apps that XP needs to remove them.
Not to worry, I like this sort of challenge.

> Zitat von ⇗ XPLives im Beitrag ¶ #3440

> Finally install all your software applications. Image your OS partition again.

Well...that's the problem. My layout is so complex that re-installing all the apps would be a major headache. That's why I'm trying to revive the current installation.

> Zitat von ⇗ XPLives im Beitrag ¶ #3440

> I could then construct one specific to your motherboard.......And make sure you at least got a PS/2 keyboard hooked up to your PS/2 keyboard - NO USB ones.

I'll keep that in mind, thanks, I do have a P/S2 keyboard and mouse hooked up.

#3465

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3464

> > Zitat von ⇗ XPLives im Beitrag ¶ #3440

> > Forget the SP4, just use a clean XP SP0, 1, 2, or 3 or get XP SP0 and integrate the SP into it using nLite before integrating the SATA AHCI driver. If you need to add more drivers later I recommend you just don't install or integrate them but just manually install them "AFTER" XP is fully booted to the desktop and installed. You are also better off imaging the clean installation before adding any drivers. The only driver that should be integrated is just the SATA AHCI from Intel and that's it.

> @XPLives....thanks again for detailed explanation. I am currently working on my old XP installation without SP4. I have made progress meantime using Dietmar's storahci driver setup. I am now able to boot to the XP boot screen and beyond. However, I am stuck at a nag screen for activation which appears before the logon screen.
> If I press 'no' to not activate, the nag disappears for 20 seconds then re-appears. If I hit 'yes' same thing. So it's stuck in a loop of some kind.
> If I boot into safe mode, everything is cool till the graphics appear. That is, I get a blank screen with the 'safe mode' boxes in each corner and it is stable but when the graphics appear for the desktop the screen starts blinking and stays that way. That suggests to me a graphics driver problem.
> It's the same in the cmd prompt version of safe mode. It tries to load graphics.
> With regard to the activation screen I have encountered a similar problem related to the Internet Explorer version. Windows needs IE for the activation process and if the IE version is wrong it stalls. As I recall the solution, you had to update the version from 6 to 8 but now I am reading you have to move it back to 6.
> Any ideas on how to replace IE on an offline system?

> > Zitat von ⇗ XPLives im Beitrag ¶ #3440

> > Once you add all that other crap into the registry it's a pain to remove it which is why a clean image after you've installed it without the bloat you can restore again later if you corrupt it.
> > Then you can start adding the graphics drivers, sound, network, et cetera.

> I agree totally. However, my registry is loaded with crap I need to remove. I should likely have done it while XP was running on an older system but now I have changed partitions and removed some with apps that XP needs to remove them.
> Not to worry, I like this sort of challenge.

> > Zitat von ⇗ XPLives im Beitrag ¶ #3440

> > Finally install all your software applications. Image your OS partition again.

> Well...that's the problem. My layout is so complex that re-installing all the apps would be a major headache. That's why I'm trying to revive the current installation.

> > Zitat von ⇗ XPLives im Beitrag ¶ #3440

> > I could then construct one specific to your motherboard.......And make sure you at least got a PS/2 keyboard hooked up to your PS/2 keyboard - NO USB ones.

> I'll keep that in mind, thanks, I do have a P/S2 keyboard and mouse hooked up.

Okay first you got to do some simple things on your Coffee Lake system and get this info for me.
Take another existing Windows Vista, 7, 8.X, or 10 OS install on another drive and hook it to your Coffee Lake system and boot up. Go to Device Manager.
Find your Intel(R) SATA Controller device.
Copy and paste all the Hardware ID fields for:
Device Instance ID:
Hardware IDs:
Compatible IDs:
Matching Device ID:
Get this info and I'll simplify that installer.
I recommend you drop using that SP4 and STORAHCI method for now and you are trying to mix it with an old installation which is worse. If you want to just install XP you can later spend the rest of your time experimenting with other methods later and add it to a new partition on your drive.
I don't know what computer system your XP (old) installation was you are migrating came from. But there are some activation checks that detect any hardware changes and if you are moving from say a Pentium 4 to Coffee Lake it will trigger it and notice your hardware is completely different. You're going to have to do a fresh installation (no choice). The other issue is if you are using a genuine copy or not. If you are and only activated it once you might be able to activate it again after a fresh installation on your Coffee Lake using the telephone number method. But if you do this you'll probably want to clone the old XP copy first and your old copy you might have to keep offline from then on if XP has some sort of deactivation feature to nullify it when caught online?
There might be a way to transfer the activation over to the new system but I never researched heavy into it and it was easier to use a Windows version that didn't require it.
I don't know the exact details of your current drive size and how you partitioned it. What's the partition layout on the drive and how much space is the old XP partition using of the space? You might have to use a second drive and repartition it properly to have multiple XP installations on it and transfer your old partition over to it.
But if your old XP installation is on D:
make a new partition E: - for this clean XP installation method that I'm trying to help you with.
Make another partition F: - when you are ready to mess around with the STORAHCI install method with SP4 once you've completed my version which should work.
Partition Sizes - 32GB would be enough for a few years. If you don't have that much room 8GB would be enough for the install and get some programs on.
I do recommend a larger partition 64GB or larger NTFS for redirecting your Programs Files location which will be the last partition on the drive. You don't want to install all your Programs to your OS partition and make it extremely huge and run out of space.
I still use FAT32 for my OS partitions since I can modify it without booting into another Windows.
So if you want to make it harder for yourself you can keep on the path till you tire out. Also if you want to just test installing XP the easy way then you could still test it out before needing to activate it. I can't remember how long maybe 3 months before the nag screen pops up on a new installation. But in the end you'll probably want to get XP installed on your Coffee Lake and play around before messing with other methods which just complicates things.
Internet Explorer 6-8? I say don't do it for now and not worth your time. It's vulnerable to being hijacked on the internet very easily as soon as you go to some unknown shady site. Then you'll have to go back to a clean image again. Lots of headaches once infected. You could boot into another Windows and then manually delete the files you isolated as trojans/malware but still a complete headache when you can just restore an earlier image in minutes so no point. If you're just viewing web pages offline FireFox can be put in offline mode.
Use FireFox v52.X - Best thing to still get on the Internet today and Youtube videos still work from 1080P to 4K. Though they are removing Flash videos as a priority if you wait long enough and the Video you want to watch is getting lots of views, eventually Youtube converts it to flash so you can watch it. By default Youtube seems to only release videos in HTML5 now first. I haven't spent the time to adapt Firefox to view HTML5. I saw some sites that show you how to do this. Guess I'm lazy on that until they completely kill of Flash. Hopefully this won't happen as we all want to watch "Me At The Zoo" every now and then.
⇗ https://www.youtube.com/watch?v=jNQXAC9IVRw

## Page 232

#3466

LoneCrusader

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3442

> Wow, rare find !
> this version 1.16.3 is not last, but PDB make it very valuable

> Zitat von ⇗ daniel_k im Beitrag ¶ #3445

> @LoneCrusader
> Thanks you very much! Nice to see you here!
> I've seen a couple of driver with "leaked" PDBs sometimes, but never really pay attention to them.

Glad I could be of some help. Hopefully having the PDB files will aid in disassembly...
I went digging for USB3 driver PDB files a year or so ago, rloew and I were attempting to find one that could be loaded under 98SE. He satisfied the missing WDM functions with his WDMEX.VXD driver, but in the end we hit a weird roadblock where the driver appeared to be exiting before crashing. There were a couple of WDM kernel calls that were used in a manner incompatible with 98SE, but he said the driver was exiting before this code was reached (rloew thought he could write a workaround for that, but we never got there, and now that he's gone it's probably lost.) All this is over my head though, lol, I could barely manage to operate the debugger and report what I found to him.
At any rate, I hope to find the time soon to do some experimenting with XP and what you guys are doing. I have an Intel X299 system that I've not even tried to boot the first OS on yet.

#3467

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3465

> Okay first you got to do some simple things on your Coffee Lake system and get this info for me.

@XPLives...thanks again for the reply and the detailed info. I will get the info for you off my SATA controller but there is something I need you to understand.
I am no longer having 0xA5 (related to ACPI) and 0x7b (related to AHCI). I am getting no errors whatsoever, my old XP disk boots to almost the logon screen but it is intercepted by a Windows Activation nag screen.
The title of the nag screen is Windows Product Activation. It read in part "A problem is preventing Windows from accurately checking the license for this computer..."
Everything seems to be working fine with regard to ACPI and the SATA controller, otherwise Windows would not get past the boot screen.
I mentioned Internet Explorer, not because I use it, I don't. I use Firefox. I mentioned it because in the past, when I was trying to load an OS onto a newer mobo, the installation stalled in the same place, at the activation process. It turned out to be Internet Explorer causing the problem.
The existing OS only had IE version 6 and it would not work with the repair install and the new mobo. So, I had to get in there and update it to IE 8. Then the activation part of the install completed and gave me an activation screen.
Right now, the activation screen won't appear because something is stopping the nag screen from completing its routine. It's likely related to Internet Explorer not working for the activation process but it could be any kind of license issue.
I can't get into safe mode. The activation process can cause that. If it has disqualified you Windows won't boot into safe mode.
My license is valid. I own the disk and I bought it years ago.

#3468

XPLives

> Zitat von ⇗ LoneCrusader im Beitrag ¶ #3466

> > Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #3442

> > Wow, rare find !
> > this version 1.16.3 is not last, but PDB make it very valuable

> > Zitat von ⇗ daniel_k im Beitrag ¶ #3445

> > @LoneCrusader
> > Thanks you very much! Nice to see you here!
> > I've seen a couple of driver with "leaked" PDBs sometimes, but never really pay attention to them.

> Glad I could be of some help. Hopefully having the PDB files will aid in disassembly...
> I went digging for USB3 driver PDB files a year or so ago, rloew and I were attempting to find one that could be loaded under 98SE. He satisfied the missing WDM functions with his WDMEX.VXD driver, but in the end we hit a weird roadblock where the driver appeared to be exiting before crashing. There were a couple of WDM kernel calls that were used in a manner incompatible with 98SE, but he said the driver was exiting before this code was reached (rloew thought he could write a workaround for that, but we never got there, and now that he's gone it's probably lost.) All this is over my head though, lol, I could barely manage to operate the debugger and report what I found to him.
> At any rate, I hope to find the time soon to do some experimenting with XP and what you guys are doing. I have an Intel X299 system that I've not even tried to boot the first OS on yet.

Got it.

#3469

Andalu

> Zitat von ⇗ XPLives im Beitrag ¶ #3441

> Never tested this but saw this iCafe driver a while back. It might work better on the newer AMD R9 series than the v14.4. So far no one willing to test their R9 to see if it works.

I'm late for the reply to your post but still in time to thank you for your detailed guides about installing XP on modern systems.
I currently do not have the possibility to try the i-cafe drivers on a R9 270 card. I'm using them on the older R7 250 with no issue but I am not a gamer :)

#3470

Andalu

⇗ @diderius6
I'm sorry to bothering you, but I need your help :) I've read that you're probably the first one who has successfully booted XP from a nvme disk. I would like to do the same on my asrock B250M-Pro4 board which natively supports the NVMe SSD as boot disk. The disk was extracted from a Samsung X5 Portable SSD, PN: MZBLB500HAJQ - controller S4LR020.
I used Windows 10 to initialise the disk using the MBR partition style. Following your advice, I tried to install XP from a boot cd with integrated OFA nvme 1.3 and storport.sys 5.2.3790.4173 via nlite and after txt setup completed without problems, I copied by hand storport.sys to windows\system32\drivers but on restart I got the message: "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk".
In the bios the NVMe SSD disk is not listed as boot device, it appears only in the 'storage configuration' section.
Also all the software I tried to cloning from another XP disk or to recovering an XP image don't allow these operations, the NVMe SSD is greyed out or does not listed. Only when booting from another XP disk I can successfully install the nvme drivers and the disk is correctly recognized in device manager and explorer.
Is there any possibility to solve?

#3471

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3467

> > Zitat von ⇗ XPLives im Beitrag ¶ #3465

> > Okay first you got to do some simple things on your Coffee Lake system and get this info for me.

> @XPLives...thanks again for the reply and the detailed info. I will get the info for you off my SATA controller but there is something I need you to understand.
> I am no longer having 0xA5 (related to ACPI) and 0x7b (related to AHCI). I am getting no errors whatsoever, my old XP disk boots to almost the logon screen but it is intercepted by a Windows Activation nag screen.
> The title of the nag screen is Windows Product Activation. It read in part "A problem is preventing Windows from accurately checking the license for this computer..."
> Everything seems to be working fine with regard to ACPI and the SATA controller, otherwise Windows would not get past the boot screen.
> I mentioned Internet Explorer, not because I use it, I don't. I use Firefox. I mentioned it because in the past, when I was trying to load an OS onto a newer mobo, the installation stalled in the same place, at the activation process. It turned out to be Internet Explorer causing the problem.
> The existing OS only had IE version 6 and it would not work with the repair install and the new mobo. So, I had to get in there and update it to IE 8. Then the activation part of the install completed and gave me an activation screen.
> Right now, the activation screen won't appear because something is stopping the nag screen from completing its routine. It's likely related to Internet Explorer not working for the activation process but it could be any kind of license issue.
> I can't get into safe mode. The activation process can cause that. If it has disqualified you Windows won't boot into safe mode.
> My license is valid. I own the disk and I bought it years ago.

I understood your problem and you're still not willing to give up on your old installation hoping to save yourself some time reinstalling everything. Depending on what your goals are when using XP on the Coffee Lake. If it's meant for gaming then I'd go with a fresh install using my K.I.S.S. method and see if this activation snafu is still happening and if it is then you might want to consider Server 2003 if you're just using it for browsing, word processing, and other non gaming applications. Games probably will work for the most part with most of the titles I've tested but I haven't gone and tested every single title to claim 100% compatibility. With Server 2003 you bypass the entire activation BS you're encountering and can use more of the RAM, add GPT support, and eliminate most of your headaches trying to use IE to activate it. I do remember you could bypass online activation and use a phone number to call method instead as one of the options. You have to decide how valuable your time is and whether or not you want to continue grunting along weeks from now out of stubbornness. It's a shame they implanted that activation BS into XP which is why Windows 2000 was such a beauty to install and why many stuck to it until XP got too popular to ignore upgrading due to dependencies. It's possible Microsoft officially abandoned IE6.0-8.0 support entirely on their site so you probably can't activate it if you could get those browsers online if its dependent on IE.
If you use your old XP copy back on the original system does it no longer have the activation nag or does it still appear?
If you reinstall XP onto the Coffee Lake. I believe there's a token file that's saved once your copy is activated. If you copy this file over to the newly installed Coffee Lake system it might appear activated. I only read about this awhile back somewhere but I have no idea if this actually worked and couldn't explain the actual procedure. But that's just another possibility I could come up with you "could" try to prolong the suffering some more or it could work?

#3472

diderius6

⇗ @Andalu
When the nvme disk is recogniced in XP on your motherboard,
you have good chances for nvme boot of XP.
Let your XP recognice the nvme disk.
This XP you copy with AOMEI Partition Assistant Standard Edition 7.0
to your nvme disk.
If you cant copy this XP via AOMEI it means, that your Bios has no legacy nvme support
and until now I do not find a solution for this
Dietmar
EDIT: I just look in Bios B25MP2.50 for your board.
Your Bios has legacy nvme support, so nvme boot of XP should work.

#3473 | Andalu | ⇗ @diderius6 You are correct, I forgot to mention that my board boots with another SSD NVME M.2 drive (sandisk SD8SN8U-256G-1012). I already used Aomei Partition Assistant Pro 8.2 with no success, the samsung NVMe SSD is greyed out. I don't understant why the firts step of XP installation (text mode) ends normally with the classic reboot but the next step with GUI is not allowed.

#3474

diderius6

⇗ @Andalu
May be, that storport.sys isnt any longer in
windows\system32\drivers
Just copy it there again.
Dietmar
PS: You need to clearify situation: Best is to let recognice XP the nvme disk first, where you want to copy your working XP from harddisk. After Aomei copied this XP from harddisk to your nvme device, disconnect all, only the nvme drive stays connected.

#3475

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3470

> @diderius6
> I'm sorry to bothering you, but I need your help :) I've read that you're probably the first one who has successfully booted XP from a nvme disk. I would like to do the same on my asrock B250M-Pro4 board which natively supports the NVMe SSD as boot disk. The disk was extracted from a Samsung X5 Portable SSD, PN: MZBLB500HAJQ - controller S4LR020.
> I used Windows 10 to initialise the disk using the MBR partition style. Following your advice, I tried to install XP from a boot cd with integrated OFA nvme 1.3 and storport.sys 5.2.3790.4173 via nlite and after txt setup completed without problems, I copied by hand storport.sys to windows\system32\drivers but on restart I got the message: "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk".
> In the bios the NVMe SSD disk is not listed as boot device, it appears only in the 'storage configuration' section.
> Also all the software I tried to cloning from another XP disk or to recovering an XP image don't allow these operations, the NVMe SSD is greyed out or does not listed. Only when booting from another XP disk I can successfully install the nvme drivers and the disk is correctly recognized in device manager and explorer.
> Is there any possibility to solve?

There might be an easier way to get this to work. Maybe I can test this on Coffee Lake which should mean it works on your system.
First which link to driver for OFA nvme 1.3?
And which link to driver storport.sys 5.2.3790.4173?
Aside from trying diderius6 suggestion maybe you can try this also.
Use 98SE DOS boot and FDISK.
Partition C: for FAT16 for 98SE DOS boot
Partition D: for FAT32 for XP
Install XP to D: with Intel SATA AHCI driver only not mixing with STORAHCI or any other drivers to SSD Drive.
Inside XP OS install the NVME driver manually using Device Manager.
Do a clone of your SSD Drive to NVME to get the C: and D: partitions identical.
Remove your original XP SSD and any other USB storage devices connected just so no other Boot Device will be detected accidentally to boot from in BIOS.
In the BIOS select NVME as the Primary Boot Device if not set.
Reboot and it should attempt to boot into XP OS on your NVME.

#3476

Andalu

⇗ @diderius6
In all attempts I copied by hand storport.sys into c:\windows\system32\drivers folder after the 'txt setup' and before the reboot for the 'gui' step. I always verified that all the OFA files were present, but on the restart I got the usual message: "Windows could not start because of a computer disk hardware configuration problem.... etc").
I followed your advice on Aomei but in all cases (disk copy, partition copy and migrate OS to SSD) I got the message:
"the bytes per sector on the source and the destination disk are not equal, so the program is unable to copy".
⇗ @XPLives
the link is from diderius6:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (14)
I also know the links on sourceforge.net and reboot.pro
I'll try your method soon ;)

#3477

daniel_k

⇗ @Andalu
Make your life easier by properly integrating storport.sys:
Just add this to TXTSETUP.SIF, under storprop.dll

    storport.sys = 1,,,,,,3_,4,0,0,,1,4

This must also be present in DOSNET.INF, in section [FloppyFiles.x] (where x can be 1, 2 or 3) and in section [Files].

    d1,storport.sys

No more files need to be edited.

#3478

FireKillerGR

Hello guys,
with all the posts and files flying around I got a bit confused.
Can I make an older XP image I got to be compatible with Z390?
At the moment I get that bios isnt ACPI compliant.
Will this be fixed if I replace the ACPI.sys in the system32/drivers/ folder?
Or do I have to make a clean installation of the OS?
If thats the case what should the procedure be to get it to work?
a) install ahci drivers -> b) install without acpi (mps?) and then replace the acpi.sys to make it work?
Thanks in advance

#3479 | skullteria | Well, i can edit Hal from Windows XP x64 with my own Reset display, maybe based on Reactos Code. Reactos use a Fast486 lib to emulate BIOS. It can solve the problem with winload.

#3480

diderius6

⇗ @Andalu
"the bytes per sector on the source and the destination disk are not equal, so the program is unable to copy"
means, that the disk structure on your original XP harddisk and on your nvme disk are different.
This you can solve with Gparted on CD
Dietmar

## Page 233

#3481 | diderius6 | ⇗ @FireKillerGR Yes, this works, if have done hundreds of times. Most easy is to use STORAHCI and modded acpi.sys Dietmar

#3482

cedar

⇗ @skullteria
Big thanks for the Storahci driver which made XP 32 work on my AMD Prime B350.
At the moment,
anything with audio (Winamp, Kmplayer, Potplayer will reboot my XP64 or 2003
64 bit within a minute or two, probably ACPI 64 or HdAudiobus.sys related.
But I can run older ffmpeg64 version 3.1.2 to backup files in x265 formats.
But newer ffmpeg 64 versions need Numanode function to run x265.
I like to test some of the One Core API capabilities.
Can your One Core API files solves this dependency? If so,
Which files are needed to be replaced in XP64?.

#3483 | antome | guys I'm trying to install xp32 on asus xi gene z390 and 9900k. I took the original cd of xp sp3 copied the content on the pc, opened acpi5048_intel_amd_final.rar (acpi.sys) and created with cabmaker 1.4 the acpi.sy_ file and replaced in the 386 folder. Created the iso with nlite integrating the drivers sata of fernando . The installation crashes returning an error iostore.sys is corrupt. Where am I wrong?
#3484 | diderius6 | ⇗ @antome Take the STORAHCI driver Dietmar
#3485 | daniel_k | ⇗ @Mov AX, 0xDEAD Did some tests here, maybe tihub3.sys has some issues when used with Intel XHCI? Hacked the tixhci.sys driver to use ASMedia-like hub IDs. Then let Windows install the ASMedia hub driver, it is loaded but crashes...
#3486 | antome | ⇗ @diderius6 where do i find it, is a modified version to work with this modified acpi.sys? thanks
#3487 | diderius6 | ⇗ @antome ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (211) Dietmar

#3488

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3471

> I understood your problem and you're still not willing to give up on your old installation hoping to save yourself some time reinstalling everything. Depending on what your goals are when using XP on the Coffee Lake. If it's meant for gaming

⇗ @XPLives
⇗ @diderius6
....it's far more complicated than that. If it was just gaming, I already have a working copy of XP with the SP4 unofficial update just waiting to be activated. It is a fresh install.
If you know anything about debuggers that will only run on an x86 XP machine you'll understand what I'm dealing with. That, and the associated apps used in x86 debugging. It was a nightmare setting them up in the first place on a running XP system on a mobo that would run XP natively.
I am getting closer all the time. Last night I was able to use the working version of XP to create a Recovery Console choice in my boot menu that actually starts, It stops with an A5 error, however, and I need to somehow include the acpi.sys of Dietmar. The acpi.sys in the c:\cmdcons directory is compressed and I am going to test today to see if I can replace it with Dietmar's ACPI.sys version.
The fact that the unofficial SP4 upgrade can create an XP install disk that will create a working copy of XP on an 8th gen mobo means there is something in the drivers inserted during the slipstream that allow XP to boot to the desktop.
Obviously, the acpi.sys they use does not work in the Repair Console files in C:\comdcons but it allows me to boot without an 0xA5 bsod.
Go figure.

#3489

cedar

⇗ @diderius6
I tried the outer space acpi.sys yesterday on Ivy system. It worked!
both in Ivy and Ryzen system. By the same logic, 64 bit outer space
acpi version perhaps can solved some stability issues in XP64 too.
I still have to boot on average 3 times to get into XP64 SP2, SP1 or 2003.
If Realtek driver is disabled, Kmplayer can run for hours without crashing.
When enabled, computer will reboot with any applications which use sounds,
sometimes with irq not less than error message.
I can also encode x264 or x265 for hours without problems. But loading
Coretemp while encoding seem to crash XP64 too.

#3490

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3487

> #3159Dietmar

⇗ @diderius6
Dietmar...I wonder if I could apply that fix, or just your straight modded acpi.sys to the C:\cmdcons directory to get a Repair Console selection in the boot menu?
I created a new cmdcons directory using a version of XP SP3 with the unofficial XP upgrade and it booted to the desktop. I inserted the slipstreamed XP SP3/SP4 disk into the CD drive and in a command console in the i386 directory performed the command winnt32.exe /cmdcons. It created a new cmdcons directory in C:\ that actually works. However, I get the old 0xA5 ACPI error as the Windows screen starts.
I am going to replace the existing compressed acpi.sy_ with your version to see if it helps. There is also a small registry hive in cmdcons under an extension .HIV. It can be loaded in a W7 registry using the Load Hive function under another name.
Please note that the c:\cmdcons is a hidden directory unless you have turned off the 'hide system files' feature within XP. All the files are read only but the Attrib -r makes them writable.

#3491

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3485

> Hacked the tixhci.sys driver to use ASMedia-like hub IDs. the driver is loaded, but crashes...

⇗ @daniel_k
Just curious, are you using windbg or just a straight code read in IDA? I started tracing the full USB system a couple of month ago using windbg remotely in kernel mode but my skills on windbg are seriously noobie. I got dragged off on another project and I'm only getting back to it now.
Part of the reason I want to get my working XP (existing on disk) install going is so I can debug live using a far better (IMHO) debugger than windbg. I am kidding in part because windbg allows me remotely to stop an OS while it's booting and follow the boot process.
I have the far better debugger going in a VM but that does not help when tracing at the hardware level. Too much interference from the VM software. Since my version of XP is 32-bit, I should be able to use my x86 debugger in that XP environment to trace USB driver action.

#3492

Andalu

⇗ @XPLives
I followed your advice and I tried to clone the NVME disk with Aomei but I got again the message: "the bytes per sector on the source and the destination disk are not equal, so the program is unable to copy". And I don't know how to solve this issue.
⇗ @daniel_k
I changed the two files and this time the storport.sys is correctly copied in the system32\drivers and it is never missed at end of the txt installation setup. But at reboot the message "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk" appears again.
Only a bit note: in DOSNET.INF, in the section [FloppyFiles.x] I have the 'x' and no number.
⇗ @diderius6
I don't know how to modify the disk structure with Gparted. I will try to find some guide.

#3493

cedar

⇗ @gordo999
Can you build a new fresh working XP , then merge "only" the new system hive to
your old working XP?. Afterward, use the old "Documents and Settings" too.
I cannot guarantee it will work every time. I did that sometime, if XP conditions are very similar,
,and same disk drive,it may work.
Meanwhile use Ycopy to clone the old XP folders just for safe keeping.

#3494

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3492

> ... got again the message: "the bytes per sector on the source and the destination disk are not equal

@Andalu....this could provide a headache for you depending on the situation. Does your NVRAM module state the number of bytes per sector or whether it uses a 512 bytes per sector emulation?
The problem is likely that your current system uses a standard 512 bytes/sector and the target drive uses a newer technology wherein the formatting is written in 4096 bytes/sector chunks.
There are two types of formatting: real physical formatting and logical formatting. If a disk is written from the factory with 512 bytes/sector, a file system like NTFS can create a logical format on top of that which resides in the OS and not on the disk. That's why when you convert from a FAT32 system to NTFS it gives you the option to write the logical partition at 512, 4096, etc. bytes per sector.
Easeus claims they have an ability to clone disks between different formatted surfaces but the feature is in their paid version only. Even at that I'd be wary. If a disk is written with the new Advanced format, it seems the sectors are hard-written at 4096 bytes per sector, in which case a disk written at 512 bytes/sector may not be clonable.
Don't quote me on this, it just FYI.

#3495

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3493

> Can you build a new fresh working XP , then merge "only" the new system hive to your old working XP?. Afterward, use the old "Documents and Settings" too.

@cedar...thanks for suggestion. I have already merged pertinent parts of the new system hive related to acpi and sata controllers. I don't know of any utility that will automate the process.
My old system hive is a veritable junk yard of old drivers, etc. I have hardware listed in there, like a Plextor CD/DVD drive that gave up the ghost at least 10 years ago.
So, yes, I will try your suggestion if push comes to shove. Since the working copy was used to make the Recovery Console and it boots cleanly to the desktop, I was hoping it would include an acpi system that worked in the Recovery Console.
We would not expect thing to work out that easily, would we?

## Page 234

#3496 | cedar | ⇗ @gordo999 There are 2 lines of XP acpi.sys now. Also try the one from outer space version,thanks to diderius6. This one can run on older system too. It saves time if you need to move the disk between older and newer computer to trouble shootings.

#3497

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3496

> There are 2 lines of XP acpi.sys now. Also try the one from outer space
> version,thanks to diderius6.

⇗ @cedar
OK..thanks. The outer space version from Dietmar (diderius6) got me going past the 0xA5 bsod on my older XP OS.
I'll look for the other one as well. I began reading through this thread from the beginning but I have only reached page 10. Still have a lot of stuff to read about.

#3498

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3483

> guys I'm trying to install xp32 on asus xi gene z390 and 9900k. I took the original cd of xp sp3 copied the content on the pc, opened acpi5048_intel_amd_final.rar (acpi.sys) and created with cabmaker 1.4 the acpi.sy_ file and replaced in the 386 folder. Created the iso with nlite integrating the drivers sata of fernando . The installation crashes returning an error iostore.sys is corrupt. Where am I wrong?

IaStor.sys is corrupt error is due to incorrect Hardware ID selected for the Intel SATA AHCI device.
Do this for me and I will try to combine this with gordo999's, and lonecrusader's X299, and yours for nlite SATA driver integration.
Take another existing Windows Vista, 7, 8.X, or 10 OS install on another drive and hook it to your X299 system and boot up. Go to Device Manager.
Find your Intel(R) SATA Controller device.
Copy and paste all the Hardware ID fields for:
Device Instance ID:
Hardware IDs:
Compatible IDs:
Matching Device ID:

#3499

XPLives

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3485

> @Mov AX, 0xDEAD
> Did some tests here, maybe tihub3.sys has some issues when used with Intel XHCI?
> Hacked the tixhci.sys driver to use ASMedia-like hub IDs. the driver is loaded, but crashes...

Don't give up. Keep plowing that driver till it works.
Both the Asmedia and Intel xHCI probably will have problems due to ACPI even with your modded ACPI.SYS.
Have you tried using NO ACPI MPS Multiprocessor install method on unmodded BIOS? I believe it will work properly if you try this.

#3500

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3488

> > Zitat von ⇗ XPLives im Beitrag ¶ #3471

> > I understood your problem and you're still not willing to give up on your old installation hoping to save yourself some time reinstalling everything. Depending on what your goals are when using XP on the Coffee Lake. If it's meant for gaming

> @XPLives
> @diderius6
> ....it's far more complicated than that. If it was just gaming, I already have a working copy of XP with the SP4 unofficial update just waiting to be activated. It is a fresh install.
> If you know anything about debuggers that will only run on an x86 XP machine you'll understand what I'm dealing with. That, and the associated apps used in x86 debugging. It was a nightmare setting them up in the first place on a running XP system on a mobo that would run XP natively.
> I am getting closer all the time. Last night I was able to use the working version of XP to create a Recovery Console choice in my boot menu that actually starts, It stops with an A5 error, however, and I need to somehow include the acpi.sys of Dietmar. The acpi.sys in the c:\cmdcons directory is compressed and I am going to test today to see if I can replace it with Dietmar's ACPI.sys version.
> The fact that the unofficial SP4 upgrade can create an XP install disk that will create a working copy of XP on an 8th gen mobo means there is something in the drivers inserted during the slipstream that allow XP to boot to the desktop.
> Obviously, the acpi.sys they use does not work in the Repair Console files in C:\comdcons but it allows me to boot without an 0xA5 bsod.
> Go figure.

Try the other ACPI mod that I tested working from Daniel_K.
I placed it at the link below so it is easier to find on the first page.
⇗ Modded ACPI Drivers Depot 2000 XP 2003 2009
DK_ACPI XP 2003 32-Bit and 64-Bit Z370 Z390 Coffee Lake MOD 10-10-2019.ZIP
If that still doesn't work... Here's the only method that will probably guarantee success.
Get those Hardware IDs info I asked for so I can create the driver for nlite.
We will use a clean XP SP3 ISO or at least XP SP0 or SP1 if using large capacity drives > 128GB.
You will have to "NOT" use any modded ACPI.sys nor STORAHCI driver for this test.
You will not use any modded USB drivers for this test.
You will have to use the F7 "NO ACPI" MPS Multiprocessor method to install XP OS fresh.
Have a USB 2.0 PCIe card installed.
Final suggestion when even this does not work.
If your programs are having issues and it still doesn't work in this NO ACPI MPS mode then I think you will have to go back to Ivy Bridge Z77 or Broadwell Z97 if you want full compatibility and less headaches. X99 might also work but haven't had the opportunity yet to test compatibility.

#3501

XPLives

⇗ @cedar

> Zitat von ⇗ cedar im Beitrag ¶ #3489

> @diderius6
> I tried the outer space acpi.sys yesterday on Ivy system. It worked!
> both in Ivy and Ryzen system. By the same logic, 64 bit outer space
> acpi version perhaps can solved some stability issues in XP64 too.
> I still have to boot on average 3 times to get into XP64 SP2, SP1 or 2003.
> If Realtek driver is disabled, Kmplayer can run for hours without crashing.
> When enabled, computer will reboot with any applications which use sounds,
> sometimes with irq not less than error message.
> I can also encode x264 or x265 for hours without problems. But loading
> Coretemp while encoding seem to crash XP64 too.

Ivy Bridge system should work without outerspace acpi.sys. Better to use built in one from Microsoft on Ivy Bridge since BIOS is ACPI compliant.
For Ryzen modded acpi.sys is needed because missing MPS Table will result in single core only installation as NO ACPI Standard PC.
Also funny things can happen on modded ACPI.sys I tested on "innerspace" diderius6 acpi.sys. System seemed very sluggish even when increasing Clock Speed and Cores made not much difference. Later I will have to retest as this could have been due to faulty equipment as I believe part of the issue was possibly my SATA data cables were defective after later troubleshooting using the same cables on Intel motherboard I noticed a few weeks ago taken from the AMD AM4 MB test system the same sluggish defective behavior or drive not detected during boot process. So it's possible the older "innerspace" driver could be good when using "good" SATA cables.
But the graphics card still showed up in Device Manager for AMD AM4 which was good during that old experiment. But the same Did6 ACPI on Intel systems Z370 the graphics card and onboard graphics was missing in Device Manager until Daniel_K's acpi.sys for 300 series it showed for the first time on ACPI but still issues with games not working properly.
Also what programs are you "requiring" the XP/2003 64-Bit version? I found that XP and 2003 32-Bit version seems more stable and easier to use even with NO ACPI.

#3502

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3469

> > Zitat von ⇗ XPLives im Beitrag ¶ #3441

> > Never tested this but saw this iCafe driver a while back. It might work better on the newer AMD R9 series than the v14.4. So far no one willing to test their R9 to see if it works.

> I'm late for the reply to your post but still in time to thank you for your detailed guides about installing XP on modern systems.
> I currently do not have the possibility to try the i-cafe drivers on a R9 270 card. I'm using them on the older R7 250 with no issue but I am not a gamer :)

For AMD R5 230 fanless model probably be good enough for your system if not gaming. Will last forever since no fan to die. I didn't have the chance to test yet but bought a used one. It has official XP driver support for non gaming but good for HTPC DVD/Blu-ray playing. But I find nVidia models GT 710 to be much better although GT 930 would have been the best if released.
Also R9 testing was not directed to you, but anyone who might own it. :)

#3503

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3492

> @XPLives
> I followed your advice and I tried to clone the NVME disk with Aomei but I got again the message: "the bytes per sector on the source and the destination disk are not equal, so the program is unable to copy". And I don't know how to solve this issue.
> @daniel_k
> I changed the two files and this time the storport.sys is correctly copied in the system32\drivers and it is never missed at end of the txt installation setup. But at reboot the message "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk" appears again.
> Only a bit note: in DOSNET.INF, in the section [FloppyFiles.x] I have the 'x' and no number.
> @diderius6
> I don't know how to modify the disk structure with Gparted. I will try to find some guide.

Yes you cannot clone the entire drive due to "different" actual total capacity. Only works with identical drives.
Only way is to image C: and D: partitions to their own files.
Then do the same FDISK to create the same C: and D: partitions on NVME drive in 98SE DOS.
Then restore the C: and D: file images to each respective partition.
Then disconnect all other SATA and USB drives and only NVME drive installed. Make sure BIOS set for Primary Drive as NVME only.
I found I can make NVME 98SE DOS bootable. I remember there was some strange issue I can't remember. Perhaps I couldn't format the C: partition in 98SE DOS so I used my cloned C: image that was 98SE DOS bootable and transferred it to that partition and it was bootable as well on NVME. First! :) Funny to see 98SE DOS boot on NVME and 98SE Splash Logo on Coffee Lake.

#3504

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3495

> > Zitat von ⇗ cedar im Beitrag ¶ #3493

> > Can you build a new fresh working XP , then merge "only" the new system hive to your old working XP?. Afterward, use the old "Documents and Settings" too.

> @cedar...thanks for suggestion. I have already merged pertinent parts of the new system hive related to acpi and sata controllers. I don't know of any utility that will automate the process.
> My old system hive is a veritable junk yard of old drivers, etc. I have hardware listed in there, like a Plextor CD/DVD drive that gave up the ghost at least 10 years ago.
> So, yes, I will try your suggestion if push comes to shove. Since the working copy was used to make the Recovery Console and it boots cleanly to the desktop, I was hoping it would include an acpi system that worked in the Recovery Console.
> We would not expect thing to work out that easily, would we?

One time I had a corrupted XP install that I wanted to keep. Actually it's this one I am still using. Similar to you I didn't want to reinstall from scratch but could use an earlier image from before to restore .
However maybe you could transplant your old XP into a fresh Coffee Lake install but it may be tricky and may or may not work.
What was the older system Motherboard Make and Model the XP was installed on? And were you connected on SATA controller or IDE?
Inside
X:\WINDOWS\system32\config
You can copy the entire contents of the old XP drive from this directory and transplant into the Coffee Lake new install and see what happens. Make a backup of your X:\WINDOWS\system32\config on your Coffee Lake before doing this so you can restore back and try other tests.
Sometimes this might fail so you might have to only copy specific one branch only and see how it reacts as copying all branches it might crash.
Probably try copying SOFTWARE first to Coffee Lake and boot and see if it looks like your entire Software branch is showing up.
Next you can try copying SYSTEM but no idea if strange behavior can occur or better to not integrate this if Software branch is enough.
If XP reintegrates itself properly then you might have a possible working transfer of the older XP system registries. Some programs may still need to be "reinstalled" to work properly but some may work just fine.
Again this isn't recommended but if you have time to kill this might be worth investigating. But regarding your activation issue you probably can't get around this so better to use a new install or Server 2003 so you can transplant your OS in the future to any system without that BS.

#3505

daniel_k

> Zitat von ⇗ gordo999 im Beitrag ¶ #3491

> @daniel_k
> Just curious, are you using windbg or just a straight code read in IDA?

For now, straight code read in IDA.
Still need to (learn to) setup kernel debugger.
Last time I used a KD, was SoftICE for Windows 9x.
Usually I use OllyDbg, but that's for user mode.

#3506

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3492

> @daniel_k
> I changed the two files and this time the storport.sys is correctly copied in the system32\drivers and it is never missed at end of the txt installation setup. But at reboot the message "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk" appears again.
> Only a bit note: in DOSNET.INF, in the section [FloppyFiles.x] I have the 'x' and no number.

Are you using a disc modified with nLite? If so, that's expected as it merges all sections into one.
About the boot error... Are you trying to boot from NVME? If so, Dietmar has experience with this, didn't try it myself yet.

#3507

cedar

⇗ @XPLives, ⇗ @Daniel_K
It is very likely the SATA cable caused sluggishness. When moving
hard disk between computers, causing the cable not perfectly fit,
I got the same sluggishness when copy files, like 2MB/s.
Once readjusted the cable, may take several tries.
Speed went back to 50+ MB/s.
I use 64 bit ffmpeg.exe, or x265.exe to encode TS files to x265 format.
64 bit is about 35% faster than 32 bit versions. For x264 format,
it is about 10% faster only. So I prefer encoding inside XP64 than XP32.
When done, the batch file notify me with any 1 of the below
start /min mplay32 /play /close %WINDIR%\media\tada.wav
start /min "F:\Program Files\Winamp\winamp.exe" b:\sound\song.mp3
start /min mplay32 /play /close b:\sound\song.mp3
tada.wav is only 1 second long. will less likely to crash XP64, 2003.
But a 2 min long song.mp3 will always reboot XP or 2003 in less than a minute.
Media player classic, Potplayer, Kmplayer, winamp all reboot XP64
or 2003 x64 in less than a minute unless Realtek audio device driver is disabled.
It is strange because sounds or musics played fine, no stuttering before
sudden reboot. I tried at least 3 versions of Realtek Audio drivers which
can installed and play sounds fine until sudden reboot within minutes
of any applications which play sounds.
Memory spaces are progressively being corrupted once sounds are played!
Daniel_K may have some good insight into this. I suspect irq issues
as sometime it BSOD with irq not less than equal... message
after sounds are played.
I will ask Daniel_K if he can help fixing the Realtek audio issue.

#3508 | cedar | ⇗ @daniel_k Could you please read #3507? Thanks for the great driver. My IVY system can run USB 3.0 for months with no issue.
#3509 | antome | I have made some small steps forward, now I get to formatting the disk with acpi active, without having a5 errors, but at the end of copying the files(99%) I get a problem on the row 0 hivesys.inf is damaged

#3510

Andalu

⇗ @gordo999
thank you for the clarification. Indeed my nvme ssd disk has 4096 bytes per sector instead the disk with XP installed has 512 bytes per sector. So this is a way not achievable... my headache goes on :)
⇗ @XPLives
Windows98SE dos version and so FDisk don't detect my NVME SSD disk. I had to create the two partitions C: (fat16) and D: (fat32) with aomei partition assistant bootable media. But I was unable to perform the copy disk operation.
The nvme disk never appears in the bios as bootable device.
⇗ @daniel_k
I tried both cd and pendrive modified with nLite and thanks to your suggestion there is no longer the need to copy by hand storport.sys to system32\drivers folder all the times.
Dietmar has already suggested me to modify the disk structure with GParted but at moment i have not found the way to do or, more likely, I don't know how to proceed.

## Page 235

#3511 | cedar | ⇗ @antome Never got any corrupt hivesys.inf problem in my XP installs. Perhaps hard disk problem or very fragmented hive.

#3512

genieautravail

Following my message on the BIOSTAR A10N-8800E motherboard:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (228)
Here some notes about the missing drivers:
SM bus controller:
PCI\VEN_1022&DEV_790B&SUBSYS_790B1022&REV_4A\3&11583659&0&A0
USB bus controller:
PCI\VEN_1022&DEV_7914&SUBSYS_79141022&REV_20\3&11583659&0&80
PCI coding/decoding controller:
PCI\VEN_1022&DEV_1578&SUBSYS_15781022&REV_00\3&11583659&0&40
Video controller:
PCI\VEN_1002&DEV_9874&SUBSYS_1C401002&REV_C4\3&11583659&0&08
About the SM bus controller:
I have two drivers, one come from the driverpacks solutions website and the other one from driverpacks.net was already in my disk image (C:\D\C\A\SMBUSamd.inf)
Only the one from driverpacks.net can be installed.
⇗
About the USB bus controller:
Again, I have two drivers, one come from the driverpacks solutions website and the other one from driverpacks.net was already in my disk image (C:\D\M\U3\amdxhc.inf)
The two can be installed.
⇗
About the PCI coding/decoding controller:
No driver exist for XP.
The situation will stay like this.
About the video controller:
The most problematic.
I have four packages of drivers and I have tried every Radeon Rx video controller.
XP has accepted to install some of them but none of them can be activated.
The only one solution for the video controller is to mount a graphic card on the PCI-Express 3.0 x16 slot.
I have a lot (eight) of graphic cards Radeon HD 4550, 5450 and 6450 in my stock of hardware.
So, for me it will be easy to resolve the issue but I can't mount the motherboard in a tiny case
What I wanted to do when I have purchased it.
A much larger case is needed.
Fortunately, I have an empty case LC-POWER LC-1400mi available!

#3513

infuscomus

⇗ @daniel_k ⇗ @diderius6
I've made a patched ntoskrnl.exe and hal.dll (multiprocessor versions) that satisfy dependencies of ACPI 5365 for XP.
if you have the time, can you test it?
infuscomus has attached files to this post

- ⇗ acpi_5365_test.zip

#3514

diderius6

⇗ @infuscomus
I just test your files.
I get message, that dlls are missed for hal.dll.
This message I have seen before. It appears,
when other dlls from Vista are missed for bootprocess,
there are some of them more than in XP SP3
Dietmar

#3515 | infuscomus | ⇗ @diderius6 did it say which dlls were missed for hal.dll?

#3516

infuscomus

⇗ @diderius6
i just noticed in import table - ntoskrnl.dll - i will fix
fixed
infuscomus has attached files to this post

- ⇗ halmacpi.zip

#3517

diderius6

⇗ @infuscomus
Same message as before.
Hal needs more dlls in "Vista"
Dietmar
PS: As far as I remember there where about 6 extra dlls in Vista for hal,
compared to XP SP3

#3518 | infuscomus | ⇗ @diderius6 I'm hoping this is the problem here - ⇗ I'll fix it tomorrow, for now i'm off to bed.

#3519

FireKillerGR

ok so what I did was:
a) get acpi.sys and syssetup.sys to .sy_ (via cmd) and replace the installation files under i386 (Windows XP Sp3)
b) install Fernando ahci drivers via nlite
c) install windows normally
issue is that after the restart I got the known A5 bios isnt acpi compliant error.
Any thoughts? What am I missing?
Edit: woks fine now :)

#3520

gordo999

@XPLives....got it going. My old system is now right to the desktop awaiting a 30 day activation period. It's amazingly solid. I had to tweak a few addresses that were still pointing to the old D: partition but most of my main apps are running on the new mobo.
My priority now is to get LAN drivers going so I can reach the Net via a network connection through my laptop's wifi. I am currently networked with the laptop via W10 and W7 on an Intel(R) Ethernet Connection (7) 1219-V. It's using an e1d62x64.sys driver. Of course, my XP is x86.
I'd also like to get USB working if possible...for my keyboard and mouse. PS/2 works OK but so far I am stealing the mouse from my laptop. Have to get out an buy another corded mouse.
I'd also like to slipstream ACPI and AHCI drivers into my XP SP3 install disk so I can run a proper repair install.
Here's the data you asked for:

    Device Description

    Intel(R) C600+/C220+ series chipset SATA AHCI Controller

    ***
    Hardware IDs

    PCI\VEN_8086&DEV_A352&SUBSYS_86941043&REV_10
    PCI\VEN_8086&DEV_A352&SUBSYS_86941043
    PCI\VEN_8086&DEV_A352&CC_010601
    PCI\VEN_8086&DEV_A352&CC_0106

    ****

    Compatible IDs

    PCI\VEN_8086&DEV_A352&REV_10
    PCI\VEN_8086&DEV_A352
    PCI\VEN_8086&CC_010601
    PCI\VEN_8086&CC_0106
    PCI\VEN_8086
    PCI\CC_010601
    PCI\CC_0106

    ***

    Matching Device ID

    pci\ven_8086&dev_a352&cc_0106

#3521

gordo999

> Zitat von ⇗ FireKillerGR im Beitrag ¶ #3519

> issue is that after the restart I got the known A5 bios isnt acpi compliant error.
> Any thoughts? What am I missing?

@FireKillerGR...Dietmar's (diderius6) acpi.sys from outer-space solved the 0xA5 issue for me. You can find a link a few pages back. I understand there is another ACPI version from daniel_k, I think, but I have not checked that out.
I used it recently on my XP recovery console. Their acpi.sys was in compressed format as acpi.sy_ but I simply substituted Dietmar's acpi.sys with no compression and the 0xA5 error disappeared.
BTW...how did you compress that file using CMD window? I know of the expand.exe function but I searched recently for a compression function and could not find one.

#3522 | FireKillerGR | if I recall correctly I used the makecab command

#3523

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3500

> Have a USB 2.0 PCIe card installed.

@XPLives...thanks again for all your help. As I told you in another reply my old XP system is now at the desktop and stable.
I have an external USB card which offers both USB 2 and 3 but it's aimed at W7 and above. I'm pretty sure it has no XP drivers, although I will check.
The Device decription is VIA USB eXtensible Host Controller
Main hardware ID is PCI\VEN_1106&DEV_3483&SUBSYS_34831106&REV_01
It also takes a DEV_3483&CC_0C03
I am not asking you to do work on this for me, just letting you know the basics about the card. It obviously has it's own onboard controller.
I would really like to get the USB ports on the mobo going. I recently used canon kong's USB driver to do that with W7. Of course, W10 drives the mobo ports naturally.
Not sure on the story, I think canon kong was working with daniel_k. I know daniel_k has a USB driver out but I have not read far enough through this thread to know what is what.

#3524

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3505

> Still need to (learn to) setup kernel debugger. Last time I used a KD, was SoftICE for Windows 9x.

⇗ @daniel_k
You have done amazingly well if all you are using is IDA for cold code reading. It's a real art in itself which I have used on many an occasion at a basic level but usually in conjunction with a debugger and a hex editor.
I have even used softice in W98 and to work with DOS mode apps. It wasn't all that stable in those days.
As you know, you can set up a kernel mode session in windbg using a VM. I have used softice on a VM in XP but I needed to get at real hardware, which is a problem with a VM. For one, much of the hardware the VM uses is built in and virtual. For another, it's code is always interfering during kmode traces.
So, I built myself a serial debugger arrangement using a laptop as host and a desktop as the target. The laptop has no serial port so I bought a USB to serial adapter from StarTech. It plugs into a USB port on the laptop (running W7) and the other end of the module has a serial cable which plugs into a serial port on my desktop (has W7, W10, and now XP). The adapter presents itself to Windows as a serial port, even though it's plugged into a USB port.
It was seriously frustrating to set it up even though I have a strong background with hardware. I got it going eventually by using W10 as the target. The W10 OS seemed to have a better ability to deal with a serial protocol than W7 but once I got a connection, W7 worked just as well.
If you want to get such a system going I'd be happy to offer whatever assistance I can. The advantage over a VM system is significant. When the target is first reached it is during an early stage of the target boot sequence, so you can trace through almost the entire boot sequence with windbg in kmode.
Although I'd still prefer to work in the softice environment, Wdbg in kmode has it's own advantages. You can call up the entire USB driver hierarchy and it will give you data on each driver. For example, it's parent and it's dependants.

#3525

cedar

⇗ @gordo999
I put modded acpi to "old" folder
CABARC -m LZX:21 N ACPI.SY_ ACPI.SYS
cabarc -r -m LZX:21 n driver.cab b:\old\*.*
cabarc -r -m LZX:21 n sp3.cab b:\old\*.*
cedar has attached files to this post

- ⇗ CABARC.zip

## Page 236

#3526

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3510

> @gordo999
> thank you for the clarification. Indeed my nvme ssd disk has 4096 bytes per sector instead the disk with XP installed has 512 bytes per sector. So this is a way not achievable... my headache goes on :)

⇗ @Andalu
Never say die. Find out if your nvme drive has a 512 byte compatibility mode. If so, it should be able to run in that mode to communicate with another drive written with 512 bytes/sector.
Or, check out taking an image of one drive rather than a clone then write the image back to a 4k drive. I don't think images care about sectoring. I created an image of my XP system and used it to create the XP OS on a VM.
Alternately, check out the Easeus claim that they have software (paid) to do the conversion. What the drive on the read/write head sees is 4096 bytes/sector. Maybe someone has devised a method to let it write to sectors of that size while actually writing data based on 512 bytes/sector.
Something from Seagate on the 4K issue:
⇗ https://www.seagate.com/ca/en/tech-insights/advanced-format-4k-sector-hard-drives-master-ti/
Something from minitool partition manager on emulation:
⇗ https://www.partitionwizard.com/partitionmagic/what-is-4k-hard-drive.html
a discussion on the subject with a link to Easeus:
⇗ https://forums.tomshardware.com/threads/cloning-windows-10-from-hdd-to-ssd-512-bytes-to-4096-bytes.3425477/

#3527

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3525

> I put modded acpi to "old" folder

⇗ @cedar
Thanks...is that for compressing a file? Or is it an alternate acpi.sys?

#3528

cedar

⇗ @gordo999
The new single acpi.sy_ is for making a new CD via Nlite.
SP3.cab and Driver.cab also has old acpi.sys needed replaced.
I use winrar or 7zip to expand the original cab files to
the "old" folder. Copy the new modded acpi.sys to it,
even storahci.sys to it as it does no harm.
Then run 1 of the line in the batch file to create a new cab
before running Nlite to make a new ISO.

#3529

Mattiwatti

> Zitat von ⇗ gordo999 im Beitrag ¶ #3526

> ⇗ @Andalu
> Never say die. Find out if your nvme drive has a 512 byte compatibility mode. If so, it should be able to run in that mode to communicate with another drive written with 512 bytes/sector.
> Or, check out taking an image of one drive rather than a clone then write the image back to a 4k drive. I don't think images care about sectoring. I created an image of my XP system and used it to create the XP OS on a VM.
> Alternately, check out the Easeus claim that they have software (paid) to do the conversion. What the drive on the read/write head sees is 4096 bytes/sector. Maybe someone has devised a method to let it write to sectors of that size while actually writing data based on 512 bytes/sector.
> Something from Seagate on the 4K issue:
> ⇗ https://www.seagate.com/ca/en/tech-insights/advanced-format-4k-sector-hard-drives-master-ti/
> Something from minitool partition manager on emulation:
> ⇗ https://www.partitionwizard.com/partitionmagic/what-is-4k-hard-drive.html
> a discussion on the subject with a link to Easeus:
> ⇗ https://forums.tomshardware.com/threads/cloning-windows-10-from-hdd-to-ssd-512-bytes-to-4096-bytes.3425477/

To add to this, (since I don't know what NVMe drive ⇗ @Andalu is using, and this may be helpful for others regardless): if you have an enterprise Intel SSD you can use the ⇗ Intel SSD Data Center Tool to change the LBA format on some drives (not all drives support this, even the Data Center ones). I have successfully done this in the past to change a 512 KB sector SSD to a 4KB one and the other way around with an Intel 750 400GB PCIe SSD, and later with an Optane P4800X 750GB.
Example: query the number of supported LBA formats and their features:
> isdct show -intelssd 0 -identify
Output:

    - Identify Namespace PHKS746500<rest of my serial here> -

    - Byte 0-7 -

    Namespace Size : 1465149168

    - Byte 8-15 -

    Namespace Capacity : 1465149168

    - Byte 16-23 -

    Namespace Utilization : 1465149168

    - Byte 24 -

    Namespace Features : 0
    Bit 0 - Thin Provisioning Support : 0

    - Byte 25 -

    Number of LBA Formats : 6

    - Byte 26 -

    Formatted LBA Size : 0
    Bit 7:5 - Reserved : 0
    Bit 4 - Metadata transfer bit : 0
    Bit 0:3 - LBA Format Support : 0

    - Byte 27 -

    Metadata Capabilities : 1
    Bit 7:2 - Reserved : 0
    Bit 1 - Metadata transfered as part of a separate buffer support : 0
    Bit 0 - Metadata transfered part of extended data LBA Support : 1

    - Byte 28 -

    End-to-end Data Protection Capabilities : 11
    Bit 7:5 - Reserved : 0
    Bit 4 - Protection Info transfered as last 8 bytes of metadata Support : 1
    Bit 3 - Protection Info transfered as first 8 bytes of metadata Support : 0
    Bit 2 - Protection Type 3 Support : 0
    Bit 1 - Protection Type 2 Support : 0
    Bit 0 - Protection Type 1 Support : 1

    - Byte 29 -

    End-to-end Data Protection Type Settings : 0
    Bit 7:4 - Reserved : 0
    Bit 3 - Protection Information Transfer : 0 (Transferred as the last eight bytes of metadata.)
    Bit 2:0 - Protection Type Information : 0 (Protection Information is not enabled)

    - Byte 131 -

    LBA Format 0 Support : 2090000
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x2 (Good performance)
    Bit 23:16 - LBA Data Size : 09
    Bit 15:0 - Metadata Size : 0000

    - Byte 135 -

    LBA Format 1 Support : 2090008
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x2 (Good performance)
    Bit 23:16 - LBA Data Size : 09
    Bit 15:0 - Metadata Size : 0008

    - Byte 139 -

    LBA Format 2 Support : 2090010
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x2 (Good performance)
    Bit 23:16 - LBA Data Size : 09
    Bit 15:0 - Metadata Size : 0010

    - Byte 143 -

    LBA Format 3 Support : C0000
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x0 (Best performance)
    Bit 23:16 - LBA Data Size : 0C
    Bit 15:0 - Metadata Size : 0000

    - Byte 147 -

    LBA Format 4 Support : C0008
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x0 (Best performance)
    Bit 23:16 - LBA Data Size : 0C
    Bit 15:0 - Metadata Size : 0008

    - Byte 151 -

    LBA Format 5 Support : C0040
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x0 (Best performance)
    Bit 23:16 - LBA Data Size : 0C
    Bit 15:0 - Metadata Size : 0040

    - Byte 155 -

    LBA Format 6 Support : C0080
    Bit 31:26 - Reserved :
    Bit 25:24 - Relative Performance : 0x0 (Best performance)
    Bit 23:16 - LBA Data Size : 0C
    Bit 15:0 - Metadata Size : 0080

    <...snip...>

Byte 25 tells us the number of supported formats is 6, though this is misleading as the value actually means the number of the highest LBA format supported. Since LBA format indices start at 0, this means 7 supported formats of which LBAFormat=6 is the highest.
Not very helpfully, the rest of the LBA formats then do not give their actual sector size. However 512 bytes and 4KB formats can still be told apart by "relative performance": 512 bytes on my Optane is "good" and 4KB is "best" (which is true - using a sector size of 4KB I saw about a 10% performance improvement across all benchmarks). You can use 'isdct show -intelssd X -all' to show the current metadata size, which will normally be 0 unless you modified this manually. In this case that gives LBA format 0 and LBA format 3 for 512 bytes and 4KB respectively assuming you wish to keep the remainder of the LBA format settings unchanged. So if the index of your target SSD is 0 and you wish to convert its LBA format 0 to change the sector size to 512 bytes, you can issue
> isdct start -intelssd 0 -nvmeformat LBAFormat=0 SecureEraseSetting=0
WHICH WILL WIPE ALL DATA ON THE SSD and convert it to the specified LBA format including the sector size.
I have to strongly recommend against using the EaseUS software. It may have improved since the last time I used it, but when I did attempt to use it to clone my 512 byte sector OS partition to the "4KB" Optane P4800X, it managed to brick the Optane (not a joke!). Of course one can argue that there is an underlying Intel firmware issue here since it should not be so trivial to kill such an expensive SSD using only software (and Intel did indeed replace the drive free of charge), but I would still steer clear of EaseUS. Another reason for simply not bothering in this case is that XP does not support booting off 4KB sector size drives: the official MS policy is that ⇗ this is only supported on Windows 8 and later. While I am normally skeptical of such claims by MS, I have never managed to get my Optane to boot Windows 7 in 4KB sector mode (either through a fresh install or from a cloned disk), so by extension I sincerely doubt that booting XP/2003 would ever work.
EDIT by Fernando: Unneeded parts and blank lines from the fully quoted post removed (to save space)

#3530

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3528

> The new single acpi.sy_ is for making a new CD via Nlite.
> SP3.cab and Driver.cab also has old acpi.sys needed replaced.

⇗ @cedar
Thanks for clarification and files.

#3531

gordo999

> Zitat von ⇗ Mattiwatti im Beitrag ¶ #3529

> I have to strongly recommend against using the EaseUS software.

⇗ @Mattiwatti
Thanks for info and advice. I don't use Easeus and I was not promoting it. I was referring to their claim that a 512 byte/sector drive could be cloned to a 4k drive. Just the messenger.
I did find it interesting that a disk image at 512 bytes/sector might be transferable to a disk with 4k sectors. I have done it 512 to 512 but I don't see why it would not work since images are not based on the bytes/sector, as far as I know.

#3532

infuscomus

⇗ @diderius6 ⇗ @daniel_k
OK,
can you test if this versions works? or same error?
infuscomus has attached files to this post

- ⇗ acpi_5365_test_2.zip

#3533

gordo999

Getting brain-lock trying to figure out a basic driver for an Intel LAN for XP. The mobo is 8th generation, an Asus B360M.
According to my W7 Device Manager the hardware ID is:
PCI\VEN_8086_DEV_15BC&SUBSYS_86721043_REV_10
Have not been able to track down a suitable Intel XP driver to try it.
I can't believe Asus. They supply a disk for the mobo but they don't list this DEV number. Anyway, they are all 64-bit drivers.

#3534 | FireKillerGR | Finally got XP to work on ASUS Z390! :D So far had success with fresh installation - now need to get older images/installation (on z270) to work.
#3535 | cedar | ⇗ @gordo999 I think daniel_k and diderius6 had XP patched Lan drivers maybe 2 months ago. I have not tried them. But they worked for daniel_k and diderius6.

#3536

Andalu

⇗ @gordo999
Some news from here. Thanks to easeus todo backup home 10.0 I was able to clone the XP disk (512 bytes) to the nvme ssd (4096 bytes) with the 'normal mode' because the 'sector by sector' method was unable to use due to different sector sizes. But the XP boot from this disk doesn't work and the disk does not appear in the boot screen menu of bios. After this, I tried also to install windows 10 (in Legacy mode) on the nvme disk (in MBR style) and again I got an error "Windows cannot be installed to this disk. The computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS".
I'm still looking for a workaround.
⇗ @Mattiwatti
Thanks for your reply and the useful information. My nvme disk was extracted from a Samsung X5 Portable SSD - PN: MZBLB500HAJQ, so I can't apply the intel method.
Here the aida report about my nvme ssd disk:

      [ Samsung Portable SSD X5 (S420NK0KB00056L) ]

        NVMe Device Properties:
          Model ID.......................................................... Samsung Portable SSD X5
          Serial Number.................................................. S420NK0KB00056L
          Revision.......................................................... 1P3QEXE7
          Device Type..................................................... NVMe v1.3.0
          Unformatted Capacity....................................... 476940 MB
          PCI Vendor ID.................................................. 144Dh  (Samsung)
          PCI Subsystem Vendor ID................................. 144Dh  (Samsung)
          IEEE OUI Identifier............................................ 38-25-00  (Samsung)
          Controller ID.................................................... 4
          Version........................................................... 66304
          Recommended Arbitration Burst Size................. 2
          Max Data Transfer Size.................................... 9
          Runtime D3 Resume Latency............................. 200000 us
          Runtime D3 Entry Latency................................. 8000000 us
          Abort Command Limit...................................... 8
          Asynchronous Event Request Limit.................... 4
          Firmware Slots............................................... 3
          Max Error Log Page Entries.............................. 64
          Power States.................................................. 5
          Warning Composite Temperature Threshold...... 329
          Critical Composite Temperature Threshold........ 330
          Total NVM Capacity......................................... 476940 MB
          Min / Max Submission Queue Entry Size............ 64 / 64 bytes
          Min / Max Completion Queue Entry Size............ 16 / 16 bytes
          Namespaces................................................... 1
          Atomic Write Unit Normal................................. 128 blocks
          Atomic Write Unit Power Fail............................. 1 blocks

        NVMe Device Features:
          128-bit Host Identifier...................................... Not Supported
          Autonomous Power State Transitions................ Supported
          Command Effects Log Page.............................. Supported
          Compare & Write Fused Operation................... Not Supported
          Cryptographic Erase....................................... Supported
          Directives...................................................... Not Supported
          Firmware Activation Notices............................ Not Supported
          Firmware Activation Without Reset.................. Supported
          First Firmware Slot Read Only........................ No
          Format All Namespaces................................. Supported
          Multiple Controllers....................................... No
          Multiple PCIe Ports........................................ No
          Namespace Attribute Changed Event............... Not Supported
          Non-Operational Power State Permissive Mode.. Not Supported
          Reservations................................................ Not Supported
          Save / Select Fields...................................... Supported
          Secure Erase All Namespaces........................ Not Supported
          SGLs........................................................... Not Supported
          SGL Bit Bucket Descriptor............................... Not Supported
          SGL Byte Aligned Contiguous Physical Buffer of Metadata..... Not Supported
          SGL Commands Larger Than Data................. Not Supported
          SMART Information Per Namespace.............. Supported
          SR-IOV Virtual Function................................ No
          Volatile Write Cache..................................... Present

        NVMe Commands:
          Compare......................................... Supported
          Dataset Management........................ Supported
          Device Self-test................................ Not Supported
          Doorbell Buffer Config....................... Not Supported
          Format NVM.................................... Supported
          Firmware Commit............................ Supported
          Firmware Image Download............... Supported
          Namespace Attachment.................... Not Supported
          Namespace Management.................. Not Supported
          NVMe-MI Receive............................. Not Supported
          NVMe-MI Send................................. Not Supported
          Security Receive.............................. Supported
          Security Send.................................. Supported
          Virtualization Management............... Not Supported
          Write Uncorrectable......................... Supported
          Write Zeroes................................... Supported

        SSD Physical Info:
          Manufacturer................................... Samsung
          SSD Family...................................... Portable SSD X5
          Form Factor..................................... Proprietary
          Controller Type................................ Samsung Phoenix S4LR020
          Flash Memory Type.......................... Samsung 64-layer 3D TLC V-NAND
          Physical Dimensions......................... 119 x 62 x 19.7 mm
          Max. Weight.................................... 150 g
          Max. Sequential Read Speed............. 2800 MB/s
          Interface......................................... Thunderbolt 3
          Interface Data Rate.......................... 5000 MB/s

#3537

diderius6

⇗ @infuscomus
This time I do not get an error about missed Dlls.
This means, you found all.
But I get BSOD about writing in wrong memory
in normal boot and also in Safe Mode (via F8)
Dietmar

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Opened \\.\com1
    Waiting to reconnect...
    Connected to Windows XP 2600 x86 compatible target at (Wed Nov  6 21:01:20.178 2019 (UTC + 1:00)), ptr64 FALSE
    Kernel Debugger connection established.
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
    *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
    Executable search path is: C:\localsymbols
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntoskrnl.exe -
    Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
    Built by: 2600.xpsp_sp3_qfe.170427-1622
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
    System Uptime: not available
    WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
    Wed Nov  6 21:01:33.006 2019 (UTC + 1:00):
    *** Fatal System Error: 0x0000007e
                                                 (0xC0000005,0x00000000,0xF789E168,0xF789DE64)

    Wed Nov  6 21:01:33.053 2019 (UTC + 1:00): Break instruction exception - code 80000003 (first chance)

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    Connected to Windows XP 2600 x86 compatible target at (Wed Nov  6 21:01:33.209 2019 (UTC + 1:00)), ptr64 FALSE
    Loading Kernel Symbols
    ..............................
    Loading User Symbols

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {c0000005, 0, f789e168, f789de64}

    *** WARNING: nt!MmPoisonedTb is non-zero:
    ***    The machine has been manipulated using the kernel debugger.
    ***    MachineOwner should be contacted first

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner
    ---------

    nt!PoRegisterSystemState+0xd5:
    804e29c2 cc              int     3
    11: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 00000000, The address that the exception occurred at
    Arg3: f789e168, Exception Record Address
    Arg4: f789de64, Context Record Address

    Debugging Details:
    ------------------

    POISONED_TB: nt!MmPoisonedTb is non-zero:

    EXCEPTION_CODE:
     (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher
    bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x"
    nicht in den Arbeitsspeicher  bertragen.

    FAULTING_IP:
    +16a2faf00c0dfc0
    00000002 ??              ???

    EXCEPTION_RECORD:  f789e168 -- (.exr 0xfffffffff789e168)
    ExceptionAddress: 00000000
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 00000000
       Parameter[1]: 00000000
    Attempt to read from address 00000000

    CONTEXT:  f789de64 -- (.cxr 0xfffffffff789de64)
    eax=00000000 ebx=80703900 ecx=54445358 edx=00000001 esi=f758db00 edi=80703830
    eip=00000000 esp=f789e230 ebp=f789e250 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    00000000 ??              ???
    Resetting default scope

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    PROCESS_NAME:  P›

    ERROR_CODE:
     (NTSTATUS) 0xc0000005 - Die Anweisung "0x%08lx" verweist auf Speicher
    bei "0x%08lx". Die Daten wurden wegen eines E/A-Fehlers in "0x%081x"
    nicht in den Arbeitsspeicher  bertragen.

    WRITE_ADDRESS:  00000000

    FOLLOWUP_IP:
    +16a2faf00c0dfc0
    00000002 ??              ???

    FAILED_INSTRUCTION_ADDRESS:
    +16a2faf00c0dfc0
    00000002 ??              ???

    BUGCHECK_STR:  0x7E

    LAST_CONTROL_TRANSFER:  from 00000000 to 00000000

    STACK_TEXT:
    f789e22c 00000000 00000000 00000000 f75924ae 0x0

    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  0x7E_VFL_BAD_IP_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  0x7E_VFL_BAD_IP_ANALYSIS_INCONCLUSIVE
    *** WARNING: nt!MmPoisonedTb is non-zero:
    ***    The machine has been manipulated using the kernel debugger.
    ***    MachineOwner should be contacted first

    Followup: MachineOwner
    ---------

    11: kd> lm
    start    end        module name
    804d7000 80701000   nt       M (pdb symbols)          c:\localsymbols\exe\ntoskrnl.pdb
    80701000 80724600   HAL2       (deferred)
    b83c3000 b83dce80   Mup        (deferred)
    b83dd000 b8409980   NDIS       (deferred)
    b840a000 b8496d00   Ntfs       (deferred)
    b8497000 b84a9f00   WudfPf     (deferred)
    b84aa000 b84c0b80   KSecDD     (deferred)
    b84c1000 b84d2f00   sr         (deferred)
    b84d3000 b84f2b00   fltMgr     (deferred)
    b84f3000 b8533000   storport   (deferred)
    b8533000 b854a880   SCSIPORT   (deferred)
    b854b000 b8800000   iaStor     (deferred)
    f746f000 f7494a00   dmio       (deferred)
    f7495000 f74b3d80   ftdisk     (deferred)
    f7554000 f7564a80   pci        (deferred)
    f7565000 f75a8000   ACPI       (deferred)
    f75a8000 f75d6000   amdxhc     (deferred)
    f75f7000 f7600300   isapnp     (deferred)
    f7607000 f7611580   MountMgr   (deferred)
    f7617000 f7624200   VolSnap    (deferred)
    f7627000 f7637000   asahci32   (deferred)
    f7637000 f7644000   storahci   (deferred)
    f7647000 f764fe00   disk       (deferred)
    f7657000 f7663180   CLASSPNP   (deferred)
    f7707000 f770d780   USBSTOR    (deferred)
    f770f000 f7713d00   PartMgr    (deferred)
    f7897000 f789a000   BOOTVID    (deferred)
    f7987000 f7988b80   kdcom      (deferred)
    f7989000 f798a500   USBD       (deferred)
    f798b000 f798c100   WMILIB     (deferred)
    f798d000 f798e700   dmload     (deferred)

#3538

daniel_k

> Zitat von ⇗ cedar im Beitrag ¶ #3507

> But a 2 min long song.mp3 will always reboot XP or 2003 in less than a minute.

Are you dual booting the system? Windows 7 or later? Any issues?
If there are no issues, probably is something driver related.
Are you using a modified ACPI.SYS?
Which AHCI driver and version is installed?

#3539

daniel_k

> Zitat von ⇗ gordo999 im Beitrag ¶ #3524

> You have done amazingly well if all you are using is IDA for cold code reading. It's a real art in itself which I have used on many an occasion at a basic level but usually in conjunction with a debugger and a hex editor.

Not a big deal. Many times is simply hit or miss.
Seriously, some patches I did some years ago, specially to fix Audigy's Equalizer app, was really tiresome.
Step-by-step execution on OllyDbg on XP, then run on Vista and see where it didn't behave the same. Spent several days.

> Zitat

> If you want to get such a system going I'd be happy to offer whatever assistance I can. The advantage over a VM system is significant. When the target is first reached it is during an early stage of the target boot sequence, so you can trace through almost the entire boot sequence with windbg in kmode.

Thanks, will surely ask for help if needed.

#3540 | daniel_k | ⇗ @infuscomus, unless you actually add the code for an exported function, it won't work at all.

## Page 237

#3541

daniel_k

> Zitat von ⇗ gordo999 im Beitrag ¶ #3533

> PCI\VEN_8086_DEV_15BC&SUBSYS_86721043_REV_10

Strange, no drivers on WindowsUpdate Catalog.
What is the exact motherboard model?

#3542

daniel_k

⇗ @Andalu
Had a new idea about your USB3 issue.
Download WPCREDIT:
⇗ http://ftp.vector.co.jp/32/55/2012/wpcre14.exe
Official website: ⇗ http://hp.vector.co.jp/authors/VA002374/
Old, but gold. It's from 2004 and 32-bit only utility.
- Write down the Device ID of your Intel USB3 controller.
- Run, WPCREDIT and select the device with matching IDs.
- To save a register "snapshot": File menu -> Register Save.
I need 2 saves, one save with working USB3, another one with no working USB3.

#3543 | daniel_k | ⇗ @Mov AX, 0xDEAD It seems the driver gets stuck into device initialization, cannot disable controller, need to reboot. The TI driver works with VirtualBox's XHCI controllers in both Intel and Renesas mode.

#3544

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3537

> ... the XP boot from this disk doesn't work and the disk does not appear in the boot screen menu of bios.

That's usually a problem with the MBR (master boot record) not being written properly, the boot.ini file being wrong, or missing files like ntldr or ntdetect. It could also be an issue wherein the disk you cloned had a hidden system partition that got cloned with the XP install. The XP partition should begin at sector 0x63 (decimal 64) on a standard 512 byte/sector format. I have no idea where it should begin on a 4k setup. Get a free disk editor like the Active@ Disk Editor, load your disk and see where the XP partition begins. If it's not at sector 0X63 that's your problem.
Of course, I have no idea what Easeus has done to accomplish the clone. They also offer a free partition manager. Boot it up and see what it has to say about the partitions on your NV disk. If none of this works, try doing a disk image of just your XP installation and try transferring it to a clean NV disk freshly partitioned with the MBR in place. I had to do all sorts of funny things to move my XP partition from 2 to 1 and fix the MBR.

#3545

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3536

> I think daniel_k and diderius6 had XP patched Lan drivers maybe 2 months ago.

@cedar...thanks...will look into that.

#3546 | daniel_k | ⇗ @Mov AX, 0xDEAD, had a chance to play with the TI drivers? Patched about a hundred suspecting conditional jumps, the "best" I've got was to change the Hub device error code from 29 to 10. All those patches were in MCCIHCD_DriverExtension_PdoClass_Initialize function, which initializes the Hub (child device).

#3547

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3542

> What is the exact motherboard model?

⇗ @daniel_k ...Asus Prime B360M-C/CSM

#3548 | gordo999 | ⇗ @Andalu ...that should be the Active@ Disk Editor. Sorry for typo. It's a very good editor, I have used it to trace right into the NTFS MFT table structure.
#3549 | infuscomus | ⇗ @daniel_k I originally thought of adding them in properly, but the code seems like an unending rabbit hole now I'm thinking it might be easier to patch ntoskrnl 5365 beta to add back in functions that were removed from it since XP.

#3550

Andalu

⇗ @gordo999
I did the cloning operation from the easeus winpe emergency disk and after cloning the first thingh I verified was the boot.ini, ntldr and ntdetect.com, all were in the root C:. The source and the destination disks had the same size (500GB) and no hidden partition.
The properties of the cloned disk (taken from two different sw) (sorry for bad quality):
⇗ ⇗ ⇗
About Active@ Disk Editor I'll try it in the afternoon, thanks for the info ;)

#3551

Andalu

⇗ @daniel_k
Here the snapshots of the usb controller (ID: PCI\VEN_8086&DEV_1E31&SUBSYS_1E311849&REV_04) of my crazy B75 Pro3-M board
;)
Andalu has attached files to this post

- ⇗ Snaps.zip

#3552

Andalu

> Zitat von ⇗ gordo999 im Beitrag ¶ #3550

> @daniel_k ...Asus Prime B360M-C/CSM

Good news :) I have the previous asus Prime B250M-C/CSM and my next step is to boot XP from it with a m.2 or nvme ssd. Nothing is reported in the user's manual about the boot from those disks. I haven't tried yet. Do you have any news about it?

#3553

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3553

> I did the cloning operation from the easeus winpe emergency disk...

⇗ @Fernando ...is the following suitable?
⇗ @Andalu ...there are several things you can try from the recovery console. The console has the utilities bootcfg, fixboot, and fixmbr. You'll need to research them to get the right order in which to apply them since I forget. bootcfg will build a boot.ini file for you after you delete your present one. I would back it up first. It is hidden in the C:\ directory and you need to use attrib *.* to see all the hidden files then attrib boot.ini -r -h -s to rename it.
However, bootcfg won't do you much good till you can see and access your C:\drive. It will tell you if it can see the C:\ drive, however. If it can't see the drive, you have other problems. fixmbr does what it says, it fixes the mbr. fixboot writes the entire partition boot sector. The mbr takes up the first sector on the disk but the partition boot sector takes up 0x63 sectors. It has code in it to help start the computer and activate the hard drive. Alternately, Active@ Disk Editor will show you the mbr, partition boot sector, and everything on the disk. You just have to learn to interpret what you see and it's not all that hard since Active@ has tables explaining each colour-coded section.
According to this whitepaper from Western Digital you need to use a special tool to setup a 4k disk if it is a native 4k, meaning it has no emulation. Emulated disks can read 8 x 512 Sectors at a time from a 512 byte/sector drive and load them into one 4096 byte sector. 8 x 512 bytes = 4096 bytes. I don't know if that might be related to your problem although I doubt it.
⇗ http://products.wdc.com/library/whitepapers/eng/2579-771430.pdf

#3554

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3555

> Nothing is reported in the user's manual about the boot from those disks. I haven't tried yet. Do you have any news about it?

⇗ @Andalu ...not sure what you mean about booting from the disks. All I got with mine was a disk with drivers for x64 and I have not read a manual. Did not know they had one. I would like better instructions for the BIOS. I am not impressed with the job Asus has done supporting this board. The only reason I got it is because Intel stopped manufacturing motherboards and this Asus board had an Intel architecture.
ps. you might have more luck with your board since it uses a 200-series Intel chipset. I think Intel was still releasing USB drivers for that series on Windows 7 so maybe it would be easier adapting them to XP.

#3555 | infuscomus | ⇗ @Gelip do you know if there is any kind of signature check in ntoskrnl or hal? as an experiment I want to swap XP ntoskrnl and hal with server 2003 versions and have it boot, but it doesn't want to work, so I was wondering if there was a signature check in it or something?

## Page 238

#3556

daniel_k

⇗ @Andalu
I've read the datasheet and, with your .RG files, confirmed the registers that the Intel switch driver changes to enable USB3 speeds.
With broken USB3, run WPCREDIT, select the XHCI controller and change registers D0 and D8 to 0F.
Benchmark your USB drive.
Now we need to find a definitive solution.

#3557

Mattiwatti

> Zitat von ⇗ infuscomus im Beitrag ¶ #3559

> @Gelip
> do you know if there is any kind of signature check in ntoskrnl or hal?
> as an experiment I want to swap XP ntoskrnl and hal with server 2003 versions and have it boot, but it doesn't want to work, so I was wondering if there was a signature check in it or something?

No, this is due to inherent kernel (and to a lesser extent, HAL) differences between NT 5.1 and 5.2. For this version specifically I can think of a few things off hand that would cause issues, for example user mode exception dispatching was changed subtly in 5.2. In general though you can assume that replacing one kernel version (of Windows; on Linux the following is not true) will not work simply due to changed syscall numbers alone. Syscall numbers are what ntdll.dll and a select few other DLLs use to request services from the kernel. These are (again, in Microsoft land) arbitrary and change with every release. This means that a program that calls OpenFile() by its syscall number on NT 5.1 may be calling CrashTheSystem() on NT 5.2, even if the program itself was not changed. This also holds true for many service packs and certainly beta releases which is where new syscalls are introduced.

#3558

cedar

⇗ @daniel_k
Thanks for the helps.
On the current AMD Asus Prime B350-Plus with Ryzen 2600, Windows 8 x64,
XP 32 bit can run for days with no issues. Both Windows use Realtek onboard
chip for sounds work flawlessly. I am planning to get a PCI or
USB sound card to test on XP64. But since Realtek sound on XP64 is
very unstable here, I somewhat doubt sound cards can solve this issue.
But never know until tested.
All chipset drivers, network driver installed. USB 3.0 and 3.1 work.
The current hard disk has XP64 SP2, SP1 and 2003 Std for testings.
All experience this audio reboot XP64 symptoms as well as
hard to boot into XP64 symptom.
The hard to boot into XP64 symptom, may or may not relate to audio
issue is like this:
If booting fail the first or/and 2nd times
,I can see the Windows Logo linger on normally as if it can
almost boot into XP64, then instantly reboot, no BSOD A5 or 7B.
The 3rd or 4th time choosing "Last Good Configuration" will very
likely boot into XP64.At most the 5th or 6th time,I can boot into
XP64 by choosing various hardware profiles.
But the hardware profiles are unreliable. Booting ok this time
does not guarantee booting work next time.
I tried 2003, XP64 SP2 before, now I run
XP64 SP1 with your modded acpi from post #2202 and Storahci.sys.
acpi,sys SHA1- 789E6923019D9BB22333393A9C51241F4554359F

cedar has attached files to this post

- ⇗ acpiXP64Ryzen#2202.rar

#3559

schreiberstein

Hey everyone!
I sadly have been inactive for a week or two due to a lack of time (college).
I will test daniel_ks patch on Windows 2003 and see if it makes any difference.
And I will also record the amount of memory with several VRAM settings for the integrated Intel HD.
Yesterday, I abandoned the SoundBlaster Audigy 2 ZS PCI-E to PCI bridge mini-project.
It worked for a couple of days, but then it started to freeze the system (any OS) randomly.
There must be a faulty connection / lack of proper shielding.
I felt like, ... you know what... I am 100% sure there wont be drivers for my onboard Realtek ALC1220-VB, but lets try it anyway...
So, I downloaded the latest Realtek HD Audio driver package (2.74, I think) for Windows XP from May 2014.
To my surprise, the driver installed without any modifications and worked immediately with my onboard audio.
This is amazing. 100% compatibility. Thats all I need.
TL;DR : Onboard Realtek ALC-1220VB soundcard of Gigabyte Z390 Designare works on XP x86 using latest official driver.
Chrome still crashes regularly (out of mem) with the memory patch on XP x86.
I wish there were a way to just swap in the Server 2003 kernel / hal files, as everything works correctly on 2003.
(Running Server 2003 is a pain when every application needs XP for installation or needs to be patched to think it is running on NT 5.1)
I also wish there would be a replacement for that unreliable AMD USB XHCI driver, since it kills NTVDM completely and has issues with USB soundcards / DACs. Maybe this TI based driver can make a difference?
By the way, would it be possible for some ISO patcher on here to share the SP3.cab index file for the makecab utility?
The one that is needed to create a new sp3.cab from a folder? (Win XP x86 EN_US) I would be very thankful.
Its great to see how active this thread is!
Thank you all!
Cheers,
schreiberstein

#3560 | cedar | ⇗ @schreiberstein Please see message #3525. This one can make new SP3.cab. Also #3528.

#3561

Gelip

⇗ @infuscomus

> Zitat von ⇗ infuscomus im Beitrag ¶ #3559

> @Gelip
> do you know if there is any kind of signature check in ntoskrnl or hal?
> as an experiment I want to swap XP ntoskrnl and hal with server 2003 versions and have it boot, but it doesn't want to work, so I was wondering if there was a signature check in it or something?

There is no signature checking on WinXP x64, and there probably isn't on Win 2003 x64

#3562

daniel_k

⇗ @Mov AX, 0xDEAD
I think the issue lies in the DataPumpXhcdWiringValue config value.
In the TI driver, even if removed, the driver seems to have some hardcoded value or detect and uses a value incompatible with Intel XHCI controller.
In the ASMedia driver, which I have managed to properly patch the ID check, with DataPumpXhcdWiringValue value in Registry, the Hub reports the same error code 29 as with the TI driver.
As soon as you remove that value, Hub start just fine, devices are properly detected. Responsiveness when a device is plugged in or removed is great.
Unfortunately, there is still an issue with storage devices, which hang immediately if you run AIDA64 Disk Benchmark.
For some reason, it seems DMA is not (properly) initialized, same behavior as AMDXHC with forced 32-bit DMA. Any ideas?
When used with VIA controller, it works just fine.
Can you please track down if there is a hardcoded value for DataPumpXhcdWiringValue or how differently it detects that value against the ASMedia driver?
I've also patched the child Hub ID, so it is a static ASMedia 2142, allowing the WHQL Hub driver to be automatically installed.

daniel_k has attached files to this post

- ⇗ ASMedia_Intel_Test.rar

#3563 | daniel_k | ⇗ @cedar Thought the issue was with your Intel system. For Ryzen, you'd better ask Dietmar.

#3564

Mattiwatti

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3563

> I wish there were a way to just swap in the Server 2003 kernel / hal files, as everything works correctly on 2003.
> (Running Server 2003 is a pain when every application needs XP for installation or needs to be patched to think it is running on NT 5.1)

You are thinking about this the wrong way ;)
Instead of transplanting the kernel and/or HAL of a different OS, which is in general an impossible task as I mentioned in my previous post, I would advise doing a clean installation of Server 2003 SP2 instead. It is far easier to modify the kernel to pretend that the system is NT 5.1 (or whichever version you like) than it is to modify an NT 5.1 system to "work correctly" the way a 5.2 system does (as you put it). For example: which OS is this?
Opinions seem to differ among the judges ;) AIDA64 is the winner for at least detecting that this is a server OS, which can be a problem on its own with some programs because they will smell money and demand that you purchase the Enterprise (TM) version of their product. Of course the "server-ness" of the OS can be changed just as simply as the version.
If applications demanding XP instead of 2003 truly is a problem for you and you don't mind trading in your XP installation for a Server 2003 one, just do the swap (and apply the necessary updates first...), send me your up-to-date ntkrnlpa.exe image, and I'll patch it to a faux NT 5.1 for you.

#3565 | cedar | ⇗ @daniel_k My Ivy is solid in XP32 and 64. Ryzen is solid in XP32 too. Have not try XP64 debug version. But I doubt the outcome as other XP64 variants all fail at audio instability.

#3566

Andalu

⇗ @gordo999
I had already tried the commands you suggested (bootcfg /rebuild and fixboot /mbr) but the boot from the nvme disk had never worked as a boot disk.
I installed Active@ Disk Editor and I'm taking some time to understand if I need to change some settings and how to do.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3557

> ...not sure what you mean about booting from the disks....

I was talking about the boot from nvme/M.2 disks for our asus prime boards. I bought the B250M-C/CSM a week ago and haven't had time to try it yet. I just looked at the user manual but nothing is reported about the boot from those disks, so I don't know if it supported. Asus doesn't seem to give remark to it, at least for those models of motherboards.

#3567

Andalu

⇗ @daniel_k
I made the changes for the XHCI controller with WPCredit. After reboot I connected to a USB3 port an external toshiba disk that uses the blue led when connected to a USB3 port and the white led when connected to a usb2 port. The disk connected to the USB3 port has correctly used the blue led but the performances don't seem to be like usb3. I got similar results with a Maxtor M3 portable. The USB3 driver installed is the amd 1.1.0.0145.
⇗

#3568

cedar

⇗ @Andalu
Teracopy can show real speed MB/s during copying files.
I use an older version 2.3. Copy files to My Book 3TB is max
at 26ish MB/s using USB2.0 port. 50 to 80 MB/s under USB 3.0
from my Asmedia Hardware USB3.0 PCIe card, or from Daniel_K's
driver.
⇗ https://www.codesector.com/teracopy

#3569

daniel_k

⇗ @Andalu
Actually, I'd make the changes and benchmark without rebooting as we don't know if the BIOS resets the register changes.
Try again, after rebooting, open WPCREDIT and check if the registers are still set to 0F.
Whatever is the case, I believe USB3 is active. as USB2 can't reach more than 26 ~ 30Mb/s.
Please benchmark with AIDA64.

#3570

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3569

> I was talking about the boot from nvme/M.2 disks for our asus prime boards.

⇗ @Andalu ....don't know anything about that since all of my drives are disk drives. I find the Asus manual to be very poor in an overall sense. The manual indicates there are 2 x M.2 Socket 3 with key type 2242/2260/2280 storage devices with IRST support (1@SATA* & PCIe mode x 4 optane memory). Whatever that means. It says nothing about booting other than the M.2 sockets on the mobo allows you to install an M.2 (NGFF) SSD module and that SATA mode shares with the SATA6G_2 port.

## Page 239

#3571 | gordo999 | ⇗ @daniel_k ...I have been reading through this thread from the beginning and came across one of your posts where you are modifying code related to memcpy. I have not, as yet, figured out what you guys were doing but memcpy is a very simply function and I have traced through it many times. All it does is point to the data to be moved in the esi register and an address where it is to be moved in the edi register, along with a count of the number of bytes to be moved. I noticed a 'push 4' statement and I took that to be the number of bytes to be moved, which is usually in the ecx register within the function code. You can watch ecx being decremented as each chunk of data is moved. Can you briefly tell me what you guys were doing?

#3572

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3566

> ... the boot from the nvme disk had never worked as a boot disk.

⇗ @Andalu ...sorry I missed this point. I would hope the Easeus app would take care of that during the clone. I cloned an OS from a laptop hard disk to a newer, larger disk with no issues. I don't recall having to prep the target disk. One problem I can visualize is the partitioning of the native 4k SSD. I have noted that it also has its first partition at the 0x63 sector (decimal 64). That would mean it is located at physical address 4096 bytes/sector x 64 sectors = 262,144 byes from beginning of disk whereas the 512 bytes/sector drive would be at 512 bytes/sector x 64 sectors = 32,768 bytes.
The disk manufacturers claim the move to 4k helps with density issues but it also represents a colossal waste of disk space if a lot of small files are being written. If a file of length 240 bytes is written to a sector of 4096 bytes, it takes up the entire sector. The rest of the sector is wasted. It's obvious that larger sector sizes also helps them sell disks. I would still consider make a disk image of your present C: drive using a free backup program like Macrium Reflect and restoring it directly to the SSD after the SSD has been properly formatted with a primary partition marked active. That's another thing to check, is your partition marked primary and active?

#3573 | daniel_k | ⇗ @gordo999, I was patching a driver, converting calls from memcpy_s to memcpy. It's already done.

#3574

schreiberstein

⇗ @Mattiwatti
Hello!
Yes, I would strongly consider using Server 2003 instead. I really don't mind, except that I cannot even install nVidia drivers since it requires XP SP3.
I would be happy if you could patch my attached kernel files to report Windows XP SP3.
Theoretically, I could just retain the old files and make them an additional boot option in boot.ini, so I could "switch" between versions, right?
Btw. the same Chrome issues occur on Windows 2003, but the system seems to be much more stable / compatible overall.
(I will try to debug Chrome and find the reason why it says it is "out of memory".)
EDIT: It would be very interesting to know which tool I can use to patch such files. (So I can eventually do it myself)
Thank you for the advice!
Cheers,
schreiberstein
schreiberstein has attached files to this post

- ⇗ 2003sp2_ntkernel.zip

#3575

Andalu

⇗ @daniel_k
I had also done the benchmark just after the changes with WPCredit and before the first restart and the results were the same. However, the modified values are lost after an extended shutdown over a minute :) It will seem strange but it is so, one minute of power off is enough to lost the modified values.
⇗ @daniel_k ⇗ @cedar
I tried the same toshiba external disk connected to a usb3 port on the B250M-Pro4 board and the difference is really too much between the two benchs.
⇗

#3576

Andalu

⇗ @gordo999
I'll give a try to macrium reflect. I also found another link where this software is recommended to solve some problems related to a nvme disk but I have not read it yet. I'll let you know as soon as I have done the test.
The partition of my nvme ssd disk has always set a primary partition and marked as active.
Thanks for your help ;)

#3577

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3510

> @gordo999
> thank you for the clarification. Indeed my nvme ssd disk has 4096 bytes per sector instead the disk with XP installed has 512 bytes per sector. So this is a way not achievable... my headache goes on :)
> @XPLives
> Windows98SE dos version and so FDisk don't detect my NVME SSD disk. I had to create the two partitions C: (fat16) and D: (fat32) with aomei partition assistant bootable media. But I was unable to perform the copy disk operation.
> The nvme disk never appears in the bios as bootable device.
> @daniel_k
> I tried both cd and pendrive modified with nLite and thanks to your suggestion there is no longer the need to copy by hand storport.sys to system32\drivers folder all the times.
> Dietmar has already suggested me to modify the disk structure with GParted but at moment i have not found the way to do or, more likely, I don't know how to proceed.

How large is the SSD? If it's 128GB and smaller you should be able to create the partitions. If FDISK isn't allowing you to enter then maybe using a hex editor and wiping Sector 0 of the NVME to 0s. Then trying to boot up on USB floppy drive and 98SE DOS and try FDISK again. If not then you might try to use a FAT32 partitioner to make it visible to 98SE DOS.
Use this link
⇗ Data Backup and Recovery for MBR Drives
Look for the FAT32 formatting program downloaded from here:
And use that link to download that program I used.
If you still can't see the NVME in 98SE DOS you can try
FDISK /MBR and see what happens if this fixes it.
Once you get into FDISK you then will have to set the first partition as Active assuming you could then delete any partitions existing and create a new FAT16 2GB partition. The if this works reboot and then FDISK again to create the larger extended partition of the remaining space with FAT32. Then you can make the logical drive partitions for D: E:.

#3578

XPLives

⇗ @cedar

> Zitat von ⇗ cedar im Beitrag ¶ #3507

> @XPLives, @Daniel_K
> It is very likely the SATA cable caused sluggishness. When moving
> hard disk between computers, causing the cable not perfectly fit,
> I got the same sluggishness when copy files, like 2MB/s.
> Once readjusted the cable, may take several tries.
> Speed went back to 50+ MB/s.
> I use 64 bit ffmpeg.exe, or x265.exe to encode TS files to x265 format.
> 64 bit is about 35% faster than 32 bit versions. For x264 format,
> it is about 10% faster only. So I prefer encoding inside XP64 than XP32.
> When done, the batch file notify me with any 1 of the below
> start /min mplay32 /play /close %WINDIR%\media\tada.wav
> start /min "F:\Program Files\Winamp\winamp.exe" b:\sound\song.mp3
> start /min mplay32 /play /close b:\sound\song.mp3
> tada.wav is only 1 second long. will less likely to crash XP64, 2003.
> But a 2 min long song.mp3 will always reboot XP or 2003 in less than a minute.
> Media player classic, Potplayer, Kmplayer, winamp all reboot XP64
> or 2003 x64 in less than a minute unless Realtek audio device driver is disabled.
> It is strange because sounds or musics played fine, no stuttering before
> sudden reboot. I tried at least 3 versions of Realtek Audio drivers which
> can installed and play sounds fine until sudden reboot within minutes
> of any applications which play sounds.
> Memory spaces are progressively being corrupted once sounds are played!
> Daniel_K may have some good insight into this. I suspect irq issues
> as sometime it BSOD with irq not less than equal... message
> after sounds are played.
> I will ask Daniel_K if he can help fixing the Realtek audio issue.

There's only one way to know if this is ACPI related. If you do a separate installation with NO ACPI MPS Multiprocessor Mode or clone your current drive and change the Computer to MPS Multiprocessor Mode and repeat the test and see if the stability is the same.
My current tests probably put this MPS Multiprocessor mode at 95% Compatibility on Intel systems.

#3579 | Andalu | ⇗ @XPLives The nvme disk size is 500GB. I had already tried to boot with an usb floppy drive with 98SE DOS but fdisk still did not see the disk. Thanks for the link and advice. I will also try osfclone as soon as I have some time.

#3580

XPLives

⇗ @genieautravail

> Zitat von ⇗ genieautravail im Beitrag ¶ #3512

> Following my message on the BIOSTAR A10N-8800E motherboard:
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (228)
> Here some notes about the missing drivers:
> SM bus controller:
> PCI\VEN_1022&DEV_790B&SUBSYS_790B1022&REV_4A\3&11583659&0&A0
> USB bus controller:
> PCI\VEN_1022&DEV_7914&SUBSYS_79141022&REV_20\3&11583659&0&80
> PCI coding/decoding controller:
> PCI\VEN_1022&DEV_1578&SUBSYS_15781022&REV_00\3&11583659&0&40
> Video controller:
> PCI\VEN_1002&DEV_9874&SUBSYS_1C401002&REV_C4\3&11583659&0&08
> About the SM bus controller:
> I have two drivers, one come from the driverpacks solutions website and the other one from driverpacks.net was already in my disk image (C:\D\C\A\SMBUSamd.inf)
> Only the one from driverpacks.net can be installed.
> ⇗
> About the USB bus controller:
> Again, I have two drivers, one come from the driverpacks solutions website and the other one from driverpacks.net was already in my disk image (C:\D\M\U3\amdxhc.inf)
> The two can be installed.
> ⇗
> About the PCI coding/decoding controller:
> No driver exist for XP.
> The situation will stay like this.
> About the video controller:
> The most problematic.
> I have four packages of drivers and I have tried every Radeon Rx video controller.
> XP has accepted to install some of them but none of them can be activated.
> The only one solution for the video controller is to mount a graphic card on the PCI-Express 3.0 x16 slot.
> I have a lot (eight) of graphic cards Radeon HD 4550, 5450 and 6450 in my stock of hardware.
> So, for me it will be easy to resolve the issue but I can't mount the motherboard in a tiny case
> What I wanted to do when I have purchased it.
> A much larger case is needed.
> Fortunately, I have an empty case LC-POWER LC-1400mi available!

> Zitat von ⇗ genieautravail im Beitrag ¶ #3512

> About the PCI coding/decoding controller:
> No driver exist for XP.
> So, for me it will be easy to resolve the issue but I can't mount the motherboard in a tiny case
> What I wanted to do when I have purchased it.
> A much larger case is needed.
> Fortunately, I have an empty case LC-POWER LC-1400mi available!

What is the smallest case you were going to use this in?
The only modern integrated iGPU for XP you could use for graphics card slot free is Ivy Bridge. For AMD they stopped XP driver support much earlier for APU. I think around AM2?
PCI coding/decoding controller
This I saw on AMD AM4. I don't know if this also existed on earlier AM3, AM2 chipsets or had XP drivers?

#3581

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3579

> @XPLives
> The nvme disk size is 500GB. I had already tried to boot with an usb floppy drive with 98SE DOS but fdisk still did not see the disk.
> Thanks for the link and advice. I will also try osfclone as soon as I have some time.

Try the FAT32 GUI formatter I mentioned in the link. I don't know if you are using Windows 7 or 10 but I think this program can work in it. Is there a NVME to USB adapter you can use? If NVME to USB adapter exists then maybe you can do it as a USB device. I usually use SATA to USB adapter. Also 500GB will be a bit too large for my method. You probably could still do the FAT16 2GB, but for the Extended Partition Size you will have to self cap it to 9999 MB. Then you can create a 8GB -> 32GB D: for XP, E: just the rest of it. Anything above the 102GB you can then use XP Disk Management and create it as NTFS partitions to utilize the 300+GB left over. Don't use Windows Vista->10 to create or delete any of the partitions as you could corrupt it. It's okay to install Windows Vista->10 onto the XP created NTFS partitions with no problems.

#3582

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3520

> @XPLives....got it going. My old system is now right to the desktop awaiting a 30 day activation period. It's amazingly solid. I had to tweak a few addresses that were still pointing to the old D: partition but most of my main apps are running on the new mobo.
> My priority now is to get LAN drivers going so I can reach the Net via a network connection through my laptop's wifi. I am currently networked with the laptop via W10 and W7 on an Intel(R) Ethernet Connection (7) 1219-V. It's using an e1d62x64.sys driver. Of course, my XP is x86.
> I'd also like to get USB working if possible...for my keyboard and mouse. PS/2 works OK but so far I am stealing the mouse from my laptop. Have to get out an buy another corded mouse.
> I'd also like to slipstream ACPI and AHCI drivers into my XP SP3 install disk so I can run a proper repair install.
> Here's the data you asked for:

>     Device Description

>     Intel(R) C600+/C220+ series chipset SATA AHCI Controller

>     ***
>     Hardware IDs

>     PCI\VEN_8086&DEV_A352&SUBSYS_86941043&REV_10
>     PCI\VEN_8086&DEV_A352&SUBSYS_86941043
>     PCI\VEN_8086&DEV_A352&CC_010601
>     PCI\VEN_8086&DEV_A352&CC_0106

>     ****

>     Compatible IDs

>     PCI\VEN_8086&DEV_A352&REV_10
>     PCI\VEN_8086&DEV_A352
>     PCI\VEN_8086&CC_010601
>     PCI\VEN_8086&CC_0106
>     PCI\VEN_8086
>     PCI\CC_010601
>     PCI\CC_0106

>     ***

>     Matching Device ID

>     pci\ven_8086&dev_a352&cc_0106

Looks like you missed the
Device Instance ID:
The Device Name ID isn't necessary. It can be renamed anything you want. :)
What was the old XP system specs? Motherboard Make / Model?
Can you get the same Hardware IDs info off that system and paste?
To me you are better off repairing it on your older motherboard first before transplanting. I am not sure the repair disc will be of any use. It will most likely end up overwriting your SP4 files or corrupting the OS even further. Best to install from scratch or transplanted successfully state. Then go back to that image rather than trying to repair which I'm not sure if repair supports integrated storage drivers when booted off the CD. Usually the self repair if you swapped the X:\Windows\system32\config files that I had mentioned one at a time and rebooted will self integrate and repair itself. If this worked for you already let me know as I don't know exactly what you did to fix the problem you were having or if you tried my windows system32 config file swap technique.

#3583

XPLives

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3559

> Hey everyone!
> I sadly have been inactive for a week or two due to a lack of time (college).
> I will test daniel_ks patch on Windows 2003 and see if it makes any difference.
> And I will also record the amount of memory with several VRAM settings for the integrated Intel HD.
> Yesterday, I abandoned the SoundBlaster Audigy 2 ZS PCI-E to PCI bridge mini-project.
> It worked for a couple of days, but then it started to freeze the system (any OS) randomly.
> There must be a faulty connection / lack of proper shielding.
> I felt like, ... you know what... I am 100% sure there wont be drivers for my onboard Realtek ALC1220-VB, but lets try it anyway...
> So, I downloaded the latest Realtek HD Audio driver package (2.74, I think) for Windows XP from May 2014.
> To my surprise, the driver installed without any modifications and worked immediately with my onboard audio.
> This is amazing. 100% compatibility. Thats all I need.
> TL;DR : Onboard Realtek ALC-1220VB soundcard of Gigabyte Z390 Designare works on XP x86 using latest official driver.
> Chrome still crashes regularly (out of mem) with the memory patch on XP x86.
> I wish there were a way to just swap in the Server 2003 kernel / hal files, as everything works correctly on 2003.
> (Running Server 2003 is a pain when every application needs XP for installation or needs to be patched to think it is running on NT 5.1)
> I also wish there would be a replacement for that unreliable AMD USB XHCI driver, since it kills NTVDM completely and has issues with USB soundcards / DACs. Maybe this TI based driver can make a difference?
> By the way, would it be possible for some ISO patcher on here to share the SP3.cab index file for the makecab utility?
> The one that is needed to create a new sp3.cab from a folder? (Win XP x86 EN_US) I would be very thankful.
> Its great to see how active this thread is!
> Thank you all!
> Cheers,
> schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3559

> Hey everyone!
> And I will also record the amount of memory with several VRAM settings for the integrated Intel HD.

I'm pretty sure it's related to that.
I did some more testing of my Ivy Bridge which supported XP integrated graphics.
It has 32MB to 1024MB MAX.
I tried all the tests using XPP SP0 with PAE.
Without PAE a huge chunk of OS base memory was missing as expected.
With PAE enabled I got the absolute full 4.00 GB of RAM showing. This to me with a 1GB shared memory setting means it is possible to boost the Shared Video Memory to 4.00 GB possibly with a BIOS MOD. However sadly I don't know of a way to make the Intel HD Graphics 630+ work with the XP driver. I can only theorize transplanting the BIOS modules for the IGPU from the Ivy Bridge to Coffee Lake and hope some form of it works even in 2D if 3D fails it's better than nothing.
I also agree you should switch to Server 2003 32-Bit and have it patched to fake ID it's XP Pro so all XP programs will install properly if it doesn't like Server 2003 ID.

#3584

Mattiwatti

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3574

> @Mattiwatti
> Hello!
> Yes, I would strongly consider using Server 2003 instead. I really don't mind, except that I cannot even install nVidia drivers since it requires XP SP3.
> I would be happy if you could patch my attached kernel files to report Windows XP SP3.
> Theoretically, I could just retain the old files and make them an additional boot option in boot.ini, so I could "switch" between versions, right?
> Btw. the same Chrome issues occur on Windows 2003, but the system seems to be much more stable / compatible overall.
> (I will try to debug Chrome and find the reason why it says it is "out of memory".)
> EDIT: It would be very interesting to know which tool I can use to patch such files. (So I can eventually do it myself)
> Thank you for the advice!
> Cheers,
> schreiberstein

Here you go, see attached ZIP for the patch.

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3574

> Theoretically, I could just retain the old files and make them an additional boot option in boot.ini, so I could "switch" between versions, right?

Yes, and that is exactly what I would recommend. I would say it is best to stick with the normal "Server 2003 mode" until some program requires you to be running XP, in which case you can reboot and reintroduce the system as NT 5.1. Example basic boot.ini:

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    redirect=COM1
    redirectbaudrate=115200
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003" /noexecute=optin /fastdetect
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Faux XP" /noexecute=optin /fastdetect /kernel=ntkrnlpa.xp

Your addendum that the nVidia drivers specifically require SP3 to install actually made this a bit more work than I anticipated, because there is of course no SP3 for Server 2003. That's not really a problem in itself, since you can change the service pack version to whatever you want by changing a single value in the registry. But this does present a problem when you reboot into "2003 mode" and the service pack number is now obviously invalid for the OS. This may lead to issues with some programs (unlikely but possible), but a more pressing issue is that it will almost certainly break your Windows installation after a while since Windows will think you are trying to tamper with the serial and/or circumvent licensing restrictions. Thus you should install the patch as follows:
1. Install the .reg file included in the ZIP, which will add a "CXPVersion" value to HKLM\SYSTEM\CurrentControlSet\Control\Windows indicating "Service Pack 3", next to the original "CSDVersion" which you should not touch.
2. Copy ntkrnlpa.xp to system32, and modify boot.ini to suit your preferences and make it possible to choose either kernel.
3. After rebooting, the patched kernel will use the bogus "CXPVersion" to report the service pack, while the 2003 kernel will keep using the old unmodified value which will cause it to report SP2 as before.
Additionally attached is "notserver.sys", which is an extremely simple driver I made some years ago after I got sick of programs (that I paid for!) refusing to work after finding that they were running on a "server" OS. (For some reason, partitioning tools seem to be particularly prone to this obnoxious behaviour.) The driver will change your OS to a "workstation" one while it is running, and revert it back to a "server" when it is stopped. While it is possible and fairly easy to patch a kernel image to make a server a workstation or the other way around, this is very dangerous since it will be immediately detected as an attempt at circumventing client-server SKU licensing restrictions and the associated costs. (even if you are doing this to your own detriment by changing a more expensive server OS to a cheaper workstation). Of course, if you work on any patch long enough you can eventually bypass this sort of thing, at which point you've essentially just made a crack. Notserver.sys on the other hand is an extremely simple and dumb driver that you should only use as long as it is necessary, since Windows does not joke around when it thinks you are messing with SKU restrictions and will simply throw you a bugcheck 0x9A (SYSTEM_LICENSE_VIOLATION) until you reformat. OK, now that the warnings are out of the way...
1. Install by copying notserver.sys to system32\drivers and running 'sc create notserver type= kernel binPath= system32\drivers\notserver.sys' (mind the weird spacing).
2. Start the driver with 'sc start notserver'.
3. After you are done installing or running obnoxious program X, stop the driver with 'sc stop notserver'.
The full source code for the driver is provided below:

    #include <ntddk.h>

    // Ntoskrnl internal variables
    static const ULONG ExpMultiUserTS = 0;
    static const ULONG ExpHydraEnabled = 1;

    // Default backup values
    static NT_PRODUCT_TYPE RealProductType = NtProductServer;
    static BOOLEAN RealProductTypeIsValid = TRUE;
    static ULONG RealSuiteMask = 0x110;

    _Use_decl_annotations_
    NTSTATUS
    DriverEntry(
    	_In_ PDRIVER_OBJECT DriverObject,
    	_In_ PUNICODE_STRING RegistryPath
    	)
    {
    	PAGED_CODE();

    	UNREFERENCED_PARAMETER(RegistryPath);

    	// Backup data
    	RealProductType = SharedUserData->NtProductType;
    	RealProductTypeIsValid = SharedUserData->ProductTypeIsValid;
    	RealSuiteMask = SharedUserData->SuiteMask;

    	// Do the thing
    	SharedUserData->NtProductType = NtProductWinNt;
    	SharedUserData->ProductTypeIsValid = TRUE;
    	SharedUserData->SuiteMask = (1 << TerminalServer) | (ExpMultiUserTS ? 0 : 0x100) | (ExpHydraEnabled ? 0x10 : 0);

    	DriverObject->DriverUnload = DriverUnload;

    	return STATUS_SUCCESS;
    }

    _Use_decl_annotations_
    VOID
    DriverUnload(
    	_In_ PDRIVER_OBJECT DriverObject
    	)
    {
    	PAGED_CODE();

    	UNREFERENCED_PARAMETER(DriverObject);

    	// Restore original values
    	SharedUserData->NtProductType = RealProductType;
    	SharedUserData->ProductTypeIsValid = RealProductTypeIsValid;
    	SharedUserData->SuiteMask = RealSuiteMask;
    }

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3574

> EDIT: It would be very interesting to know which tool I can use to patch such files. (So I can eventually do it myself)

For this patch in particular I only used one program (plus ⇗ CFF Explorer afterwards to fix PE checksums), and that is IDA Pro. I would highly recommend not looking up the price of an IDA licence at this point, by the way... just a suggestion. In general I would say you need to have at least a basic grasp of x86 assembly and a good understanding of the PE executable format. Experience with programming in C/C++ is not necessary, but will help a lot. You don't need IDA to learn either programming or assembly: you can get started with Visual Studio Community and x64dbg, which are both free. Furthermore IDA does have a trial version of 7.0 which is free to use but limited to disassembling x86 (32 bit) files only.
Mattiwatti has attached files to this post

- ⇗ NT52-x86-masquerade-as-NT51.zip
- ⇗ notserver.sys-x86.zip

#3585 | daniel_k | ⇗ @Andalu Are you dual booting that system? If so, please run the benchmark on an OS with official USB3 driver support (Win7 or later).

## Page 240

#3586 | daniel_k | ⇗ @Mattiwatti, really interesting your approach, thanks for sharing it with us!
#3587 | daniel_k | ⇗ @schreiberstein With Mov AX, 0xDEAD's help, I've managed to patch hal from XP SP3 to behave exactly the same as Server 2003. Will update my patcher soon. Unfortunately, issues with AMDXHCI driver remain, so I'm trying to fix a driver developed by MCCI (ASMedia, AMD and TI).

#3588

cedar

⇗ @XPLives
It is XP64 on 'Ryzen" that has unstable audio issue. 64 bit has no MPS. :-(
XP32 has no ACPI or audio issue, except 1 XP SP3 installed can't use USB3.0 on Ryzen.
It will always BSOD whether install or uninstall any USB3.0 drivers, but USB3.1 is
rock stable. XP32 on Ryzen works fine in ACPI, MPS or Standard Mode.
It would be very fun if someone can "create" MPS mode for XP64 or
patch Win2000 for Intel or Ryzen on modern hardwares.

#3589 | cedar | Thread moved to XP64 forum.

#3590

genieautravail

⇗ @XPLives
What is the smallest case you were going to use this in?
I wanted to mount the motherboard into this case :
⇗ https://www.lc-power.com/en/product/pc-c...ases/lc-1340mi/
The only modern integrated iGPU for XP you could use for graphics card slot free is Ivy Bridge. For AMD they stopped XP driver support much earlier for APU. I think around AM2?
No, the last AMD APU with support for XP is Kabini (release in 2014).
PCI coding/decoding controller
This I saw on AMD AM4. I don't know if this also existed on earlier AM3, AM2 chipsets or had XP drivers?
No, no driver for XP exist.

#3591

schreiberstein

⇗ @Mattiwatti
Thanks a lot!
This sounds very interesting / promising! Have you shared this knowledge before? It's amazing and I am sure it will help a lot (whatever the numbers are in 2019) of folks who want to use "personal" applications on Server 2003.
I will give that a try very soon!
We just started learning ARM Cortex M3 assembly at college and I have looked into several resources of Intel x86 assembly.
It would be very interesting to me to learn more about it, since I could use it for so many different things.
Brilliant idea to write your own driver to override the version strings.
I sure have seen some Russian versions of IDA Pro on the internet, haha.
⇗ @daniel_k
Hey! Interesting news! I think you are onto something great with that new XHCI driver and the HAL patcher.
Things seem to be getting better and better for us folks with newer machines.
I have been using XP with the 4GB patch several times now and it seems to be working fine! (Like Server 2003 with native 32GB PAE)
Perhaps it is just a problem of the Advanced Chrome version I am using. Palemoon seems stable, so is every other application.
It is very satisfying. No audio artifacts with integrated Realtek HD either.
Thanks to everyone involved!
Cheers,
schreiberstein

#3592 | IntiMD | ⇗ @genieautravail FYI this device is related to the AMD Platform Security Processor (AMD Secure Technology). To put this simply it's AMD equivalent to Intel's Management Engine BTW if you feel lucky, you can give Snappy Driver Installer Origin a try, so as to try finding the missing drivers for the devices. Assuming that you have working internet connection in the XP machine, go to ⇗ https://www.snappy-driver-installer.org/download/ and download the "Application only" package. Unpack the zipped archive and open the main exe. Choose to download only indexes. After it finishes downloading the indexes it should show you the list of devices that need a driver or need to be updated (depending on the filters set ofc, assuming the filters are default ones). Don't do anything in it (especially DO NOT install the drivers from the app level, even though SDIO is much legit compared to other driver boosters, you need to be cautious. If you're interested, you can hover over a device for info related to the device and drivers offered by the app, including the location of them in the driverpacks that the app offers to download), just close the app. Find the latest snapshot file ending with the .SNP file extension, and upload it to a hosting of your choice (preferably zippyshare or uploadfiles). I'll then check and research the snapshot, hoping the app will find drivers for those unknown devices.

#3593

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3579

> ...fdisk still did not see the disk.

⇗ @Andalu ....I am beginning to suspect a driver problem, or a setup issue for your NV drive. An SSD has to emulate a real hard drive and that requires a driver that can interpret data intended for a real, physical drive to the SST format. When you first attached the SSD was it ever visible in disk manager?
If Easeus was able to clone to the SSD then Active@ Disk Editor should be able to see the partition with XP on it. Bootcfg should at least be able to detect an OS on the disk.
When I had this issue, with XP on partition 2 and an old non-working W98 OS on partition 1, nothing could see the XP install except for an XP SP3 disk slipstreamed with the unofficial SP4 update. My stock XP SP3 disk encountered both 0xA5 and 0x7B bsods and could not reach the repair console. However, the slipstreamed SP4 disk had neither and recognized the existing XP installation. That's why I am thinking there are driver issues, either with your SSD drivers or with the SATA/ACPI drivers. Try running an XP SP3, or earlier, installation disk and see if it can see the XP install on your SSD.
You'll have to let it run from boot as it goes past the F6 install window. If you are getting an 0XA5 bsod, hit F7 immediately when you see the screen for the F6 driver install. That gets you past the 0xA5 ACPI error. Unfortunately, you will likely get an 0xF7 error when Windows starts to boot.

#3594

gordo999

⇗ @XPLives ...update...I now have the old system running with good stability on the 8th gen mobo. I even have a USB connection for keyboard and mouse through an onboard VIA USB2/3 controller. Found the drivers online. The missing drivers are (yellow question marks):
-the NVidia GT 730 graphics driver
-the Creative Xfi drivers
-Intel SPI (flash) controller - A324
-PCI Simple Communications Controller - PCH HECI Controller - A360
-SM Bus controller - A323
-HDAUDIO - NVidia ven_10de_&dev_0051 - CK804 ISA Bridge
-HDAUDI0 - realteck related from the old mobo. I have uninstalled them.
I am currently trying to get the LAN going because my Internet connection is via the Network to another computer. I have a lot of experience with such installations but it becomes a bit mind bending trying to keep all the requirements in place. Like an 8th gen mobo and x86 drivers.

> Zitat von ⇗ XPLives im Beitrag ¶ #3582

> What was the old XP system specs? Motherboard Make / Model?

Intel DQ35JOE from Intel. It would be a lot of trouble at present to set it up since I am using the case for the new mobo. I have set it up on a table top in the past to run a floppy drive.
I can't swap the registry hives one for one since the originals contain a vast amount of data about apps I had installed. I might try it for a laugh to see what happens but right now I am trying to get online so I can activate. Don't want to go through the tedious process required by phone.
BTW...the matching ID for my SATA controller is pci\ven_8086&dev_a352&cc_0106.

#3595

XPLives

⇗ @genieautravail

> Zitat von ⇗ genieautravail im Beitrag ¶ #3590

> @XPLives
> What is the smallest case you were going to use this in?
> I wanted to mount the motherboard into this case :
> ⇗ https://www.lc-power.com/en/product/pc-c...ases/lc-1340mi/
> The only modern integrated iGPU for XP you could use for graphics card slot free is Ivy Bridge. For AMD they stopped XP driver support much earlier for APU. I think around AM2?
> No, the last AMD APU with support for XP is Kabini (release in 2014).
> PCI coding/decoding controller
> This I saw on AMD AM4. I don't know if this also existed on earlier AM3, AM2 chipsets or had XP drivers?
> No, no driver for XP exist.

> Zitat von ⇗ genieautravail im Beitrag ¶ #3590

> @XPLives
> No, the last AMD APU with support for XP is Kabini (release in 2014).

Since you are working on building a desktop in the smallest case then the last claimed supported AMD Desktop APU looks like "Kaveri" (2014) which is socket FM2+ which I should not have called AM2 but because they shifted the name to AM4 it makes it easier to follow.
I also found a strange "Kabini" (2013, SoC) that came right before Kaveri. So if Kaveri works then this Kabini could also.
This one uses Socket AM1 aka Socket FS1b.
Sempron 2650
Sempron 3850
Sempron 3850
Athlon 5350
Athlon 5370
One user here has posted about their Kaveri build here:
⇗ How To - Create a Windows XP 32bit Digital Audio Workstation (and installing on AMD Socket FM2+ hardware).
I did some more searching and found other possible AMD Desktop APUs that might also work and placed on this page link below.
⇗ Windows 32-Bit OS AMD Discussions 2000 XP 2003 2009
But in the interest of easiest to install since Sandy Bridge beat AMD to the theirs and Ivy Bridge improved upon it I think the best will be based on the Ivy Bridge iGPU for that small case. Power consumption and efficiency were very good. Also I noticed easier to find quad core versions compared to the AMD counterpart.
As for how the AMD Kaveri APU compared to the Intel Ivy Bridge iGPU in XP would be interesting to test.
Since I did not invest in AMD CPUs since the K6 series and only recently the AM3 series which I haven't had time to test but doesn't look like any will work on it and I do not know much about the AMD Desktop APU XP performance. I only have AMD graphics cards but once nVidia released Maxwell it was game over and I switched for lower wattage and higher performance. XP driver support also went dead first with AMD on their graphics cards so nVidia had an extra year of support. Only sad thing is they did not release a beta Pascal 1000 series XP driver.

#3596

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3594

> @XPLives ...update...I now have the old system running with good stability on the 8th gen mobo. I even have a USB connection for keyboard and mouse through an onboard VIA USB2/3 controller. Found the drivers online. The missing drivers are (yellow question marks):
> -the NVidia GT 730 graphics driver
> -the Creative Xfi drivers
> -Intel SPI (flash) controller - A324
> -PCI Simple Communications Controller - PCH HECI Controller - A360
> -SM Bus controller - A323
> -HDAUDIO - NVidia ven_10de_&dev_0051 - CK804 ISA Bridge
> -HDAUDI0 - realteck related from the old mobo. I have uninstalled them.
> I am currently trying to get the LAN going because my Internet connection is via the Network to another computer. I have a lot of experience with such installations but it becomes a bit mind bending trying to keep all the requirements in place. Like an 8th gen mobo and x86 drivers.

> > Zitat von ⇗ XPLives im Beitrag ¶ #3582

> > What was the old XP system specs? Motherboard Make / Model?

> Intel DQ35JOE from Intel. It would be a lot of trouble at present to set it up since I am using the case for the new mobo. I have set it up on a table top in the past to run a floppy drive.
> I can't swap the registry hives one for one since the originals contain a vast amount of data about apps I had installed. I might try it for a laugh to see what happens but right now I am trying to get online so I can activate. Don't want to go through the tedious process required by phone.
> BTW...the matching ID for my SATA controller is pci\ven_8086&dev_a352&cc_0106.

Are you saying all these devices you don't have the driver working?
-the NVidia GT 730 graphics driver
-the Creative Xfi drivers
-Intel SPI (flash) controller - A324
-PCI Simple Communications Controller - PCH HECI Controller - A360
-SM Bus controller - A323
-HDAUDIO - NVidia ven_10de_&dev_0051 - CK804 ISA Bridge
-HDAUDI0 - realteck related from the old mobo. I have uninstalled them.
The only one that should work that you really need is the GT 730.
Use HDMI Video/Audio output solution and you're done.
All other devices are not required.
The Intel DQ35JOE is ancient. Was that the last motherboard you've used since going to Coffee Lake? You really dragged on that thing forever.
No PS/2 ports luckily USB 2.0 working on that.
Easiest to setup again without installing in the new case. Just unhook the PSU from the case and place motherboard onto a motherboard box top. Hook up the PSU. Then add the old memory back if you've removed it. Then hook up the SATA drive and boot into XP. Add USB keyboard/mouse to get info. And hook up old VGA monitor to integrated VGA port.

#3597

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3596

> The only one that should work that you really need is the GT 730.
> Use HDMI Video/Audio output solution and you're done.

⇗ @XPLives ...not following you. What is HDMI Video/Audio solution? I got the Creative Xfi sound card going and I have been working on the Nvidia card but an INF file I have lists it and the installer claims the hardware is not right. Go figure.
Spoke too soon. I tried one last time to load Nvidia drivers with a popup Add New Hardware windows and this time it worked. After a reboot, I was in high definition mode as opposed to a super VGA mode. In Control Panel\Display they list the driver as Nvidia GT 730, but nowhere else. Normally Nvidia has a presence under Start\Programs but there's nary a sign of them. No monitor, no setup facility...nada. There's hardly a mention under Program Files either. Weird.

#3598

XPLives

@quote=gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3597

> > Zitat von ⇗ XPLives im Beitrag ¶ #3596

> > The only one that should work that you really need is the GT 730.
> > Use HDMI Video/Audio output solution and you're done.

> @XPLives ...not following you. What is HDMI Video/Audio solution? I got the Creative Xfi sound card going and I have been working on the Nvidia card but an INF file I have lists it and the installer claims the hardware is not right. Go figure.
> Spoke too soon. I tried one last time to load Nvidia drivers with a popup Add New Hardware windows and this time it worked. After a reboot, I was in high definition mode as opposed to a super VGA mode. In Control Panel\Display they list the driver as Nvidia GT 730, but nowhere else. Normally Nvidia has a presence under Start\Programs but there's nary a sign of them. No monitor, no setup facility...nada. There's hardly a mention under Program Files either. Weird.

Use Device Manager and point to the driver INF folder directly. Don't use the Installer. If the graphics card doesn't show up as the default selected on the list then pick GT 710.
Just use settings, control panel, display and there will be a tab there.

#3599

genieautravail

> Zitat von ⇗ IntiMD im Beitrag ¶ #3592

> @genieautravail FYI this device is related to the AMD Platform Security Processor (AMD Secure Technology). To put this simply it's AMD equivalent to Intel's Management Engine
> BTW if you feel lucky, you can give Snappy Driver Installer Origin a try, so as to try finding the missing drivers for the devices. Assuming that you have working internet connection in the XP machine, go to ⇗ https://www.snappy-driver-installer.org/download/ and download the "Application only" package. Unpack the zipped archive and open the main exe. Choose to download only indexes. After it finishes downloading the indexes it should show you the list of devices that need a driver or need to be updated (depending on the filters set ofc, assuming the filters are default ones). Don't do anything in it (especially DO NOT install the drivers from the app level, even though SDIO is much legit compared to other driver boosters, you need to be cautious. If you're interested, you can hover over a device for info related to the device and drivers offered by the app, including the location of them in the driverpacks that the app offers to download), just close the app. Find the latest snapshot file ending with the .SNP file extension, and upload it to a hosting of your choice (preferably zippyshare or uploadfiles). I'll then check and research the snapshot, hoping the app will find drivers for those unknown devices.

thank you!
I will try Snappy in the next weeks.
Not before, because I have ordered some new DDR4 memory modules for the motherboard and I will do everything in the same time.

#3600 | genieautravail | ⇗ @XPLives Yes, Socket AM1 is for kabini APU. I have one Athlon 5350 APU and one Sempron 3850 APU with this motherboard: ⇗ https://www.asrock.com/mb/AMD/AM1H-ITX/

## Page 241

#3601

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3598

> Use Device Manager and point to the driver INF folder directly. Don't use the Installer. If the graphics card doesn't show up as the default selected on the list then pick GT 710. Just use settings, control panel, display and there will be a tab there.

⇗ @XPLives ...maybe you could clarify something. There was no listing for the NVidia card in Device Manager. The Display entry had a generic VGA driver. Are you saying I should have used the generic driver entry to load the NVidia drivers? Furthermore, there is an entry under the USB controller section for the VIA USB drivers for their USB card I have plugged into the PCIe sockets. Is there a way for me to install drivers for the B360M's mobo onboard chipset from DM without disturbing the VIA drivers?

#3602

gordo999

> Zitat von ⇗ genieautravail im Beitrag ¶ #3590

> I wanted to mount the motherboard into this case :

⇗ @genieautravail ...as someone with scads of experience with hardware I suggest with a case that the rule of thumb is "the bigger the better". Those smaller, sleek cases look good, but in the heat of summer you can almost bet your processor temperature will skyrocket. Heat dissipation from the processor is based on conduction of heat to the heat sink (physical contact via thermal paste), convection of heat from the heat sink to the surrounding air, and the further conduction of heat away from the heat sink by external fans. Since the heat dissipation by conduction is limited by the thermal gradient between the processor and the heat sink, the major dissipation factor is how fast you can get the heat away from the heat sink and how cool you can keep the heat sink. Heat will flow faster when the temperature between source and sink is higher.
I run a much larger case open because I am always in there tinkering. During summer, I noticed the CPU temperature reaching 80C, an alarming observation for anyone associated with hardware. I immediately pointed a fan with a 12" blade at the motherboard and the temperature dropped in a few minutes to a more acceptable 50C range. I got it even lower by positioning the external and larger fan. The smaller fans in those slim-line boxes is not enough to carry off the heat of a multi-core processor under load in higher ambient room temperatures unless you have a water-cooled heat sink on the processor . If you look in the computer room of a major commercial or industrial environment, the rooms are air conditioned to the point it can be uncomfortably cool in there. That's not for the benefit of the employees in the room.

#3603

schreiberstein

I just attempted to install Visual Studio 6.0 on my XP machine and it failed without any error messages. I assume this is all due to NTVDM, since I did not encounter such issues on my XP VM. Did not find a way to temporarily disable the AMD USB driver, so I guess I will just wait for another driver until I deploy a final system for myself.
(I am using PS/2 keyboard and mouse)
I also attempted disabling NTVDM via group policy, but it did not change anything for the better.
VMware Workstation 10 installed fine on Server 2003, but starting a VM took about two minutes, mouse went unresponsive (like on Windows 98 with interrupt issues) and the Linux kernel (Ubuntu 64) crashed while booting (Kernel Panic - Something about interrupts)
This might be due to an incompatibility with the new CPU and this old version of VMware though. I will look into that.
⇗ @Mattiwatti
Thank you again for your patched kernel. I was able to install the nVidia drivers (it seems, but some sub installers failed, but that might have been due to the previously failed i stallation.) I am now able to use the nVidia control panel to configure my dual monitor setup. Very cool!
Id personally prefer XP for compatibility though if daniel_k and 0x pull off the 4GB+ hal.dll patching. Aside from NTVDM, there is no real showstopper for me on XP, I think.
I am really happy about it. Thanks to all.
Cheers,
schreiberstein

#3604

gordo999

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3603

> I just attempted to install Visual Studio 6.0 on my XP machine and it failed without any error messages.

⇗ @schreiberstein ...there is usually an installation log. There is usually a setupapi.log somewhere and Visual Studio may have their own.

#3605 | cedar | ⇗ @gordo999 Once awhile I place foods that need defrosted from the fridge between the fan and the open case computer.

#3606

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3605

> Once awhile I place foods that need defrosted from the fridge
> between the fan and the open case computer.

⇗ @cedar ...I know this discussion is getting off topic but I thought it might be valuable information related to the topic since the issue was raised within the thread in relation to the topic.
Never thought of your idea re thawing food but a long time ago when I worked repairing computers I encountered a situation where a power transistor had been mounted on a cabinet cover (back door) as a heat sink. You could not hold your finger on the transistor's metal case because it would burn you severely. The metal around the transistor was so hot, I swear you could have fried an egg on it. That transistor was capable of carrying 8 amps unsinked and that's a lot of current to run through a tiny transistor junction. It also produces a lot of heat.
My processor is an Intel i5-8400 and it is rated at 65 watts. It only uses 70% of rated capacity at full load "at room temperature". That 30% hedge can soon be used up if the heat in the case gets too hot. Even at 50 watts, and a presumed processor voltage of 1.2 volts, that's a current draw of 41 amps, 5 times what my power transistor drew. Mind you, a processor draws the current through 50 million+ transistors. All the same, it amounts to 5 times the heat on my single power transistor and that heat needs to be well dissipated as well as being supplied from an adequate power rated supply. As you claimed, you can use the heat to thaw out frozen food. The processor can draw that much current due to DC-DC buck converters used on modern mobos that step down the 3.3 volt PS line to 1.2 volts while increasing the current, just like a step down transformer.

#3607

cedar

⇗ @gordo999
Heating problem is very real in the summer.
My old Pentium DualCore used to be overclocked 3+Ghz via Setfsb
utility for several years. Bought an Arctic Freezer Pro which was several mm
oversize and didn't fit the Asrock VSTA board. So it needs open case and
real mid size fan blow to it. Now I underclock it to run it, due to its
old age. I also underclock the video card using an older version Afterburn.
Otherwise it won't run stable in the hot summer. I was not joking about
the defrosting. The cooling affect is quite small, but it is there and harmless.

#3608

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3573

> @gordo999, I was patching a driver....

⇗ @daniel_k ...speaking of patching drivers someone mentioned that you had worked on LAN drivers recently. Not asking you to patch anything for me but would you read over this issue and let me know what you think?
I found a possible XP LAN driver for my Asus B360M which uses an Intel I219-V, according to the W7 Network section in Device Manager. The driver is in the package ProWin32Legacy.exe from Intel. My DEV_15BC is listed in the INF file but all the references are to W7, 6.1.1. I changed all the 6.1.1 settings to 5.1.1 and XP happily loaded everything to my registry and the driver e1d6232.sys to %windir%\System32\drivers. However, the driver won't start and in XP Device Manager it is marked as error (Code: 39) meaning the driver MIGHT be corrupted or missing.
I am wondering if in your experience drivers get marked internally as being for one OS only. I can, and will find out for myself, but I thought you might be able to help me not re-invent the wheel, so to speak. BTW...I got the Creative XFi card going with all the bells and whistles (sounds really good) and the Nvidia graphics card GT 730.

#3609

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3601

> > Zitat von ⇗ XPLives im Beitrag ¶ #3598

> > Use Device Manager and point to the driver INF folder directly. Don't use the Installer. If the graphics card doesn't show up as the default selected on the list then pick GT 710. Just use settings, control panel, display and there will be a tab there.

> @XPLives ...maybe you could clarify something. There was no listing for the NVidia card in Device Manager. The Display entry had a generic VGA driver. Are you saying I should have used the generic driver entry to load the NVidia drivers? Furthermore, there is an entry under the USB controller section for the VIA USB drivers for their USB card I have plugged into the PCIe sockets. Is there a way for me to install drivers for the B360M's mobo onboard chipset from DM without disturbing the VIA drivers?

On your regular fresh XP installation it will show up as "Video Controller (VGA Compatible)", but on my automated installation that I'm working on using my modified driver it installs directly so I only see the graphics card name.
Once the drivers are installed for a device installing another driver for another device does not affect the devices already installed. However if the drivers are using the same shared names and your modified driver overwrites the original driver it may cause it to fail. You will usually get an overwrite prompt popup to confirm. So in that case of two nVidia graphics cards of different generations it is necessary to modify the driver filenames as well since the drivers are different but use the same filenames. The other method is using two different graphics card brands AMD and nVidia and not modify the drivers. But recently I found AMD driver causes the nVidia driver or card to somehow BSOD. Once the registries are modified you will have to find a way to purge it or go back to an earlier image before any graphics drivers were installed. So that's why it is better to choose one brand and in my experience nVidia has the best performance for XP. Once the two drivers are mixed in the same system only the AMD continues to work without BSOD. The other option is if you are using both AMD for 98SE and nVidia for XP never install the AMD drivers and you'll be fine.
So if you plan on using a VIA USB 3.0 PCIe card and using a modified VIA USB 3.0 driver for your onboard Intel USB 3.0 ports it might work, might not work, or behave erratically. Also if the drivers are written by the same manufacturer it's also possible they could conflict even though different card brands. Only way to know for sure is to test it.

#3610

XPLives

⇗ @genieautravail

> Zitat von ⇗ genieautravail im Beitrag ¶ #3600

> @XPLives
> Yes,
> Socket AM1 is for kabini APU.
> I have one Athlon 5350 APU and one Sempron 3850 APU with this motherboard:
> ⇗ https://www.asrock.com/mb/AMD/AM1H-ITX/

Yeah it's strange AMD use FM1 and AM1. Kaveri is probably the last generation for you. If you go desktop and discrete GPU then AM3+ is the best XP compatible.
Interesting motherboard AM1H-ITX. Has an option to use an external power brick. At first I thought it was missing the ATX connector or why put that on the rear then it states includes both so if you use power brick you could use a smaller case. I don't think any Intel one has this feature that I've seen but I do not buy Mini ITX size motherboards just ATX. But you gave me nice idea to hunt for a Sandy/Ivy Bridge Mini ITX for a small case system build maybe one day for experiment. Have you tried Pico PSU or fanless SFF PSU?
Do you have any Kabini laptop with XP some were < 10W.
If you want to go super small I remember some USB computer sticks from Intel. I actually wanted to test if they could use XP.

#3611

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3606

> > Zitat von ⇗ cedar im Beitrag ¶ #3605

> > Once awhile I place foods that need defrosted from the fridge
> > between the fan and the open case computer.

> @cedar ...I know this discussion is getting off topic but I thought it might be valuable information related to the topic since the issue was raised within the thread in relation to the topic.
> Never thought of your idea re thawing food but a long time ago when I worked repairing computers I encountered a situation where a power transistor had been mounted on a cabinet cover (back door) as a heat sink. You could not hold your finger on the transistor's metal case because it would burn you severely. The metal around the transistor was so hot, I swear you could have fried an egg on it. That transistor was capable of carrying 8 amps unsinked and that's a lot of current to run through a tiny transistor junction. It also produces a lot of heat.
> My processor is an Intel i5-8400 and it is rated at 65 watts. It only uses 70% of rated capacity at full load "at room temperature". That 30% hedge can soon be used up if the heat in the case gets too hot. Even at 50 watts, and a presumed processor voltage of 1.2 volts, that's a current draw of 41 amps, 5 times what my power transistor drew. Mind you, a processor draws the current through 50 million+ transistors. All the same, it amounts to 5 times the heat on my single power transistor and that heat needs to be well dissipated as well as being supplied from an adequate power rated supply. As you claimed, you can use the heat to thaw out frozen food. The processor can draw that much current due to DC-DC buck converters used on modern mobos that step down the 3.3 volt PS line to 1.2 volts while increasing the current, just like a step down transformer.

I don't think i5-8400 can get that hot but gets pretty warm if 4.0 GHz. Check your temps for 800 MHz mine runs at 27.0-29.0C. Very nice for fanless XP setup. Closed system no ventilation maybe will increase temps 10.0C? Once Ice Lake / Tiger Lake 10nm we can see if they will drop to 400 MHz and no heatsink needed.

#3612

Mattiwatti

> Zitat von ⇗ gordo999 im Beitrag ¶ #3608

> > Zitat von ⇗ daniel_k im Beitrag ¶ #3573

> > @gordo999, I was patching a driver....

> ⇗ @daniel_k ...speaking of patching drivers someone mentioned that you had worked on LAN drivers recently. Not asking you to patch anything for me but would you read over this issue and let me know what you think?
> I found a possible XP LAN driver for my Asus B360M which uses an Intel I219-V, according to the W7 Network section in Device Manager. The driver is in the package ProWin32Legacy.exe from Intel. My DEV_15BC is listed in the INF file but all the references are to W7, 6.1.1. I changed all the 6.1.1 settings to 5.1.1 and XP happily loaded everything to my registry and the driver e1d6232.sys to %windir%\System32\drivers. However, the driver won't start and in XP Device Manager it is marked as error (Code: 39) meaning the driver MIGHT be corrupted or missing.

I can't speak for ⇗ @daniel_k, and perhaps he has some driver (modified or not) hidden up his sleeve that will work for the I-219V. But as far as I know this range of onboard ethernet adapters (I-217V, I-218V, I-219V) has never seen XP-compatible drivers released by Intel. I will explain why the driver you took can't work on NT 5.1 or 5.2 regardless of .inf file modification, since it may help in the future (exact results may differ, since I'm probably using a different version of the driver and also on x64):
1. Make a new folder on your desktop named 'drivers' (any name works) and drop the .sys file(s) that the .inf will install for you in there. In this case that would just be e1d6232.sys.
2. Copy any dependencies living in system32\drivers to the same folder. Since we don't yet know which these are, and I don't want to spoil the surprise, simply copy all .sys files from system32\drivers to the folder on your desktop. Why not drop e1d6232.sys into system32\drivers? Because this way you are free to work with a hypothetical modified drivers folder (e.g. using some Vista or Windows 7 drivers) without messing up your real installation.
3. Run ⇗ Dependency Walker, making sure to use the version with the right bitness for your OS (x86 vs x64).
4. Open e1d6232.sys in the 'drivers' folder that lives on your desktop.
5. At this point you will get an error about missing dependencies, which is the guarantee that the .sys driver will not work on an unmodified system.
6. Fortunately Dependency Walker does a lot more than saying something is wrong (like Windows does, and even then you have to be aware which cryptic error codes map to which dependency problem). It also shows which functions are missing and in which files the driver expects these to be. (Note that this works the same way for user mode binaries with .exe/.dll extensions.)
7. Upon closer inspection you will see that the driver is missing several functions in ndis.sys, which is the general purpose network driver almost all network-related drivers will depend on. One hypothetical (and not entirely stupid, given that it works for some other drivers) fix that one could come up with is to simply take ndis.sys from Windows 7. Do so now by replacing ndis.sys (in the folder on your desktop!) with one from Windows 7 of the same bitness. Close the file in Dependency Walker and reopen it.
8. You will once again receive an error, this time related to a missing msrpc.sys. On your system you may also have missing ntoskrnl.exe dependencies (I use a highly modified kernel with about ~400 extra exports so I can't really check this). The 'only msrpc.sys' case is the optimistic one. Let's also assume we don't already know what this driver is and what it depends on... Repeat the procedure from above by naively dropping msrpc.sys from Windows 7 into the drivers folder. Close and reopen the Intel .sys file.
9. This is the part where you will hit a brick wall due to missing dependencies in ntoskrnl.exe. Whether or not such a missing dependency is truly fatal requires some knowledge of NT internals, and even then the definition of 'fatal' can be argued since anything can in principle be done given enough time... but I will call this a fatal scenario. What's the problem? Msrpc.sys requires the ALPC (Advanced or Asynchronous, depending on whom you ask, Local Procedure Call) subsystem to be present. You can tell this is the case from the various ZwAlpcXxx functions the driver requires.
Several (more simple) drivers can be made to work this way by using the above procedure (taking one or two simple export drivers from a newer Windows version if needed), which is why I outlined it in detail even though in this case it still ended up not fixing anything. At the very least you will be able to see why a driver's dependencies cannot be satisifed instead of the useless error codes that Windows returns.
Back to reality... what should you do? Well, first of all, await ⇗ @daniel_k's response in case he's aware of a fix or workaround for this particular adapter. Personally, what I have done is buy a simple ⇗ Intel Gigabit CT Desktop Adapter (from ~2009), which is still a perfectly acceptable 1Gbps card today and fits in a PCIe x1 slot. This name is a bit generic: the precise adapter you are looking for has ID PCI\VEN_8086&DEV_10DE which translates to (in the INF) "Intel(R) 82567LM-3 Gigabit Network Connection" or (PCI ID repository/Linux kernel) "Intel Corporation 82574L Gigabit Network Connection". Beware that Intel has memory holed all XP/2003-compatible drivers 1984 style and you will not find them on intel.com. The latest compatible version of the network drivers I was able to find using Google was v18.3 (for NT 5.2 x64).

#3613

Mattiwatti

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3591

> @Mattiwatti
> Thanks a lot!
> This sounds very interesting / promising! Have you shared this knowledge before? It's amazing and I am sure it will help a lot (whatever the numbers are in 2019) of folks who want to use "personal" applications on Server 2003.

You can hereby consider it shared ;)
If you feel like the "faux XP" kernel is worthy of its own thread or should be shared somewhere else, feel free to do so. I don't own the copyright to the file, and in so far as I own the copyright to any modifications I release them to the public domain. I just don't want to become the "maintainer" of the patch with all the boring duties that come with such a job. Although if you have any problems with it you can always try to @ping me by name (or PM me) and see if I show up and am able to fix the problem.

#3614

genieautravail

> Zitat von ⇗ XPLives im Beitrag ¶ #3610

> Interesting motherboard AM1H-ITX. Has an option to use an external power brick. At first I thought it was missing the ATX connector or why put that on the rear then it states includes both so if you use power brick you could use a smaller case. I don't think any Intel one has this feature that I've seen but I do not buy Mini ITX size motherboards just ATX. But you gave me nice idea to hunt for a Sandy/Ivy Bridge Mini ITX for a small case system build maybe one day for experiment. Have you tried Pico PSU or fanless SFF PSU?

Not for the moment, the motherboard is mounted in the same case that I wanted to use for the BIOSTAR motherboard:
⇗ https://www.lc-power.com/en/product/pc-c...ases/lc-1340mi/
I have 4 of these cases.

> Zitat von ⇗ XPLives im Beitrag ¶ #3610

> Do you have any Kabini laptop with XP some were < 10W.

Not a laptop, but in one of my LC-POWER cases In have mounted this motherboard:
⇗ https://www.biostar.com.tw/app/en/mb/int...on.php?S_ID=711
The AMD E1-2100 APU has a TDP of 9W. More informations here:
⇗ http://www.cpu-world.com/CPUs/Jaguar/AMD...%20E1-2100.html

> Zitat von ⇗ XPLives im Beitrag ¶ #3610

> If you want to go super small I remember some USB computer sticks from Intel. I actually wanted to test if they could use XP.

Not truly an USB computer stick, but I have just installed XP on a mini PC equiped with an AMD A6-1450 APU with a TDP of 8W.
See here:
⇗ XP and mSATA
More informations on the APU:
⇗ http://www.cpu-world.com/CPUs/Jaguar/AMD...%20A6-1450.html

#3615

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3585

> @Andalu
> Are you dual booting that system? If so, please run the benchmark on an OS with official USB3 driver support (Win7 or later).

Your predictions were correct. Even in Windows 7 the performance of the toshiba external disk connected to the USB3 port are not as expected. A tiny better with the samsung M3 portable, but the main problem is that there is no way to make the usb3 function available on my crazy board also after a shutdown.
At this point, I'm thinking it's time to put this board aside, also because I have another board where usb3 doesn't work at all and I still have not found a way to solve.

## Page 242

#3616

Andalu

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3593

> > Zitat von ⇗ Andalu im Beitrag ¶ #3579

> > ...fdisk still did not see the disk.

> @Andalu ....I am beginning to suspect a driver problem, or a setup issue for your NV drive. An SSD has to emulate a real hard drive and that requires a driver that can interpret data intended for a real, physical drive to the SST format. When you first attached the SSD was it ever visible in disk manager?
> If Easeus was able to clone to the SSD then Active@ Disk Editor should be able to see the partition with XP on it. Bootcfg should at least be able to detect an OS on the disk.
> When I had this issue, with XP on partition 2 and an old non-working W98 OS on partition 1, nothing could see the XP install except for an XP SP3 disk slipstreamed with the unofficial SP4 update. My stock XP SP3 disk encountered both 0xA5 and 0x7B bsods and could not reach the repair console. However, the slipstreamed SP4 disk had neither and recognized the existing XP installation. That's why I am thinking there are driver issues, either with your SSD drivers or with the SATA/ACPI drivers. Try running an XP SP3, or earlier, installation disk and see if it can see the XP install on your SSD.
> You'll have to let it run from boot as it goes past the F6 install window. If you are getting an 0XA5 bsod, hit F7 immediately when you see the screen for the F6 driver install. That gets you past the 0xA5 ACPI error. Unfortunately, you will likely get an 0xF7 error when Windows starts to boot.

About the XP installation on the nvme disk please see my post ¶ here
I don't understand why the XP txt installation setup has completed with no problems and the GUI setup does not start anyway.
The nvme disk is immediately seen in the XP mechanical disk as a generic PCI device and after installing the ofa driver 1.3 and storport.sys 5.2.3790.4173 it is correctly recognized as disk drive.
Active@ Disk Editor was able to see the partition with XP on it, but i don't know what to modify. With Macrium Reflect, when I tried to restore an image created previously from the XP disk (with 512 bytes per sector), I got the error: "the target disk has an incompatible sector size for this operation".
The bootcfg /scan command from the recovery console also does not detect the XP installation on the nvme disk (drive D:).

#3617

Andalu

⇗ @XPLives

> Zitat von ⇗ XPLives im Beitrag ¶ #3577

> How large is the SSD? If it's 128GB and smaller you should be able to create the partitions. If FDISK isn't allowing you to enter then maybe using a hex editor and wiping Sector 0 of the NVME to 0s. Then trying to boot up on USB floppy drive and 98SE DOS and try FDISK again. If not then you might try to use a FAT32 partitioner to make it visible to 98SE DOS.
> Use this link
> ⇗ Data Backup and Recovery for MBR Drives
> Look for the FAT32 formatting program downloaded from here:
> And use that link to download that program I used.
> If you still can't see the NVME in 98SE DOS you can try
> FDISK /MBR and see what happens if this fixes it.
> Once you get into FDISK you then will have to set the first partition as Active assuming you could then delete any partitions existing and create a new FAT16 2GB partition. The if this works reboot and then FDISK again to create the larger extended partition of the remaining space with FAT32. Then you can make the logical drive partitions for D: E:.

> Zitat von ⇗ XPLives im Beitrag ¶ #3581

> Try the FAT32 GUI formatter I mentioned in the link. I don't know if you are using Windows 7 or 10 but I think this program can work in it. Is there a NVME to USB adapter you can use? If NVME to USB adapter exists then maybe you can do it as a USB device. I usually use SATA to USB adapter. Also 500GB will be a bit too large for my method. You probably could still do the FAT16 2GB, but for the Extended Partition Size you will have to self cap it to 9999 MB. Then you can create a 8GB -> 32GB D: for XP, E: just the rest of it. Anything above the 102GB you can then use XP Disk Management and create it as NTFS partitions to utilize the 300+GB left over. Don't use Windows Vista->10 to create or delete any of the partitions as you could corrupt it. It's okay to install Windows Vista->10 onto the XP created NTFS partitions with no problems.

At moment I have no NVME to USB adapter and I don't know if my nvme disk can effectively work on it. I tried again with win98SE bootable pendrive but fdisk still does not recognize the nvme disk.

#3618 | cedar | ⇗ @Andalu Have you tried XXclone or Paragon rescue kit 9 free edition? They make unbootable hard disk partition bootable for cloning W2k, XP. It worked for my SSD 120GB on Ivy system test some months ago. Maybe they have newer versions that can work for you.
#3619 | diderius6 | ⇗ @Andalu Please tell me the exact name of the nvme disk, which makes problems to boot XP SP3 from it. I will buy and check ) Dietmar

#3620

cedar

Partial install(with errors) of 64bit_Win7_Win8_Win81_R272 Realtek
audio driver overwrite some files on another version of installed Realtek
audio driver stabilize my XP64 SP2 Ryzen. I tested Kmplayer can play
several hours of video with "sounds" without rebooting XP64.
However, test playing 10 epsodes of tv shows overnight still reboot
XP64 at some point last night. Nevertheless, It is a big improvement.
Lot more tests still needed. Like whether it can encode while watching
videos. or using ffmpeg ,Virtualdub64 or 32 bit...
edIt: This won't install(partially) under XP64. unless extract the file
to a folder and add new section AND your hardware ID from:
eg. HDX.inf
[Manufacturer]
%MfgName% = AzaliaManufacturerID, NTamd64.6.0
[AzaliaManufacturerID.NTamd64.6.0]
"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC
"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_0861
"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_0880
to:
[Manufacturer]
%MfgName% = AzaliaManufacturerID, NTamd64.6.0, NTamd64
[AzaliaManufacturerID.NTamd64]
;Your audio hardware ID here
[AzaliaManufacturerID.NTamd64.6.0]
"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC
"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_0861
"Realtek High Definition Audio" = IntcAzAudModel, HDAUDIO\FUNC_01&VEN_10EC&DEV_0880

#3621 | Andalu | ⇗ @cedar Thank your for the info. I'll give a try.

#3622

Andalu

⇗ @diderius6
I am sorry and I thank you very much for your kind availability but I cannot allow it. My board already boots from a M.2 SSD disk, so I am in no hurry to solve. I asked for help in this great forum to have the opportunity to learn something new about my passion (and also to write better in english which is the most difficult thing for me ....it's still so poor). I ask you the courtesy of not making any purchase to solve the problem I have. Thank you again so much ;)
P.S.: I take this opportunity to apologize if I have caused any disturbance for my requests.

#3623

diderius6

⇗ @Andalu
Is this M.2 SSD disk, from where you can boot XP SP3, a real nvme device
Dietmar
PS: Is there a name on the NVME disk written by Samsung,
that you have extracted from samsung x5 portable ssd?
EDIT: The nvme in the X5 case seems to be very near to this one.
I have done nvme boot of XP SP3 with this device.
Samsung SSD 970 EVO 500GB, M.2 (MZ-V7E500BW)
(351)
Info beim Hersteller
Bauform Solid State Module (SSM)
Formfaktor M.2 2280
Schnittstelle M.2/M-Key (PCIe 3.0 x4)
Lesen 3400MB/s
Schreiben 2300MB/s SLC-Cached (600MB/s TLC)
IOPS 4K lesen/schreiben 370k/450k
Speichermodule 3D-NAND TLC, Samsung, 64 Layer (V-NAND v4)
TBW 300TB
Zuverlässigkeitsprognose 1.5 Mio. Stunden (MTBF)
Controller Samsung Phoenix (S4LR020), 8 Kanäle
Cache 512MB (LPDDR4), SLC-Cache (4-22GB)
Protokoll NVMe 1.3
Datenschutzfunktionen 256bit AES, TCG Opal 2.0
Leistungsaufnahme 10W (maximal), 5.7W (Betrieb), 0.03W (Leerlauf), 0.005W (Schlafmodus)
Abmessungen 80x22x2.38mm
Besonderheiten L1.2 Low-Power-Standby
Herstellergarantie fünf Jahre oder bis Erreichen der TBW
Gelistet seit 24.04.2018, 18:03

#3624 | Andalu | ⇗ @diderius6 your Samsung SSD 970 EVO 500GB, M.2 (MZ-V7E500BW) is similar to the model I have. The controller is the same. How did you boot XP from it? edit: my board boots correctly from the Sandisk SD8SN8U-256G-1012

#3625

diderius6

⇗ @Andalu
May be the reason is, that the Samsung 970 EVO has 512-e mode.
This means, internal it uses 4096 Byte/sector but to the environment it acts
like 512 Byte/sector. Only from 512 Byte/sector XP SP3 can boot.
When the internal controller of the Samsung nvme in the X5 case ONLY works
with real 4096 Byte/sector you can use it under XP only as USB device in an USB case
Dietmar

#3626 | Andalu | ⇗ @diderius6 Thanks for the explanation. You confirmed what ⇗ @gordo999 reported in a previous post, the trouble is there, XP can't boot from a nvme disk with 4096 byte per sector and no 512 byte emulation mode. But how can I figure if my nvme disk has or not the 512e? I understand, if I had it I wouldn't have found so many difficulties for cloning the disk or restoring an XP image and also the partitioning software would have listed the nvme disk.
#3627 | diderius6 | ⇗ @Andalu For nvme disks I also do not know, how to decide between real and only 4096 bytes per sector or 512 emulated. On the WD harddisks in their description is written, that they have 512e mode Dietmar

#3628

gordo999

⇗ @Mattiwatti ....thank you kindly for the detailed and in-depth explanation. I have enough experience with reversing and the NT Kernel to follow you and I would dearly love getting into ntoskrnl to the level you mention. However, the only debugger of which I am aware that will trace through ring 0 code is softice. I have asked experienced people if windbg will trace through it but the answers I receive are vague as to what constitutes ring 0. Anytime I have tried to enter ring 0 with wdbg at a sysenter point, it turfs me out the other end without tracing through the code. Having said that, since I am working in x86 code, I would love to get SI going on this converted XP machine and I know it won't be easy. Tried the other night for a laugh and got a bsod with stop: 0x24, apparently related to ntfs.sys. Does that mean SI only runs on a FAT32 system? Don't think so since I recall using it to trace into the MFT via ntfs.sys. Don't want to get off-topic talking about debuggers but if you have anything to add on that topic perhaps you would be kind enough to PM me.
Your explanation re dependency walker is interesting. It had occurred to me to try it at some point but it had not occurred to me to load the entire drivers directory into the same test folder. Why not the entire sys32 directory as well? Having said that, if we are creating a directory with all those files, should it not work by running DW on a W7 machine?

> Zitat von ⇗ Mattiwatti im Beitrag ¶ #3612

> ...what I have done is buy a simple ...Intel Gigabit CT Desktop Adapter

From what I gather I'd need to find an older version. I looked the adapter up on the Intel site and they claim the 32-bit version won't run on anything below W7. Of course, that's Intel. They have unfortunately abandoned ship. I came across an adapter last night that is a USB - Network adapter....don't know if that would work.
BTW...I managed to get online last night using a Cisco AM10 wifi adapter. It plugs into a USB port and for some reason sets itself up as a drive. Bit of a nuisance. The good news is that I am now activated.

#3629

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3624

> your Samsung SSD 970 EVO 500GB, M.2 (MZ-V7E500BW) is similar to the model I have.

⇗ @Andalu ...check out this troubleshooting FAQ from Samsung. They talk about a Magician utility for checking the drive.
⇗ https://www.samsung.com/semiconductor/minisite/ssd/support/faqs-02/
Also, does the drive show up correctly in BIOS and in Device Manager? Based on the information in the Samsung FAQ, your driver may need a mod to run under XP.

#3630

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3609

> So if you plan on using a VIA USB 3.0 PCIe card and using a modified VIA USB 3.0 driver for your onboard Intel USB 3.0 ports it might work, might not work, or behave erratically. Also if the drivers are written by the same manufacturer it's also possible they could conflict even though different card brands. Only way to know for sure is to test it.

⇗ @XPLives ...thanks for the info. Not sure if VIA drivers will work with the B360 USB hardware since VIA uses its own onboard USB controller. I did try the drivers for XP by ⇗ @diderius6 but they crashed. I have not had time to look into this since Dietmer specified the acpi.sys driver by daniel_k and I am using a later acpi version by him. See post #2072 on page 139.

## Page 243

#3631

daniel_k

WinXPPAE 2.0, a small utility to patch all kernel and hal files, supporting all languages and versions 5512 (SP3) and later:
What's new:
- thanks to ⇗ @Mov AX, 0xDEAD, now includes HAL patches for ACPI Timer fix and proper memory management from Server 2003.
- creates backups files (.bak) automatically
To use it, copy the following hal and kernel files (found in SP3.CAB) and the utility to the same folder.
ntkrnlmp.exe - Multiprocessor Kernel
ntoskrnl.exe - Uniprocessor Kernel
ntkrpamp.exe - Multiprocessor PAE Kernel
ntkrnlpa.exe - Uniprocessor PAE Kernel
hal.dll - Standard PC HAL
halaacpi.dll - ACPI Uniprocessor HAL
halacpi.dll - ACPI HAL
halapic.dll - MPS Uniprocessor HAL
halmacpi.dll - ACPI Multiprocessor HAL
halmps.dll - MPS Multiprocessor PC HAL
Run WinXPPAE with the appropriate command line.
Usage: winxppae [/4GB | /ALL | /NB or /NOBACKUP]
/4GB Enables PAE limiting RAM to 4Gb to avoid stability issues.
/ALL Enables PAE with unlimited RAM, may have stability issues.
/NB Does not create backup copies of original files.
/NOBACKUP Same as /NB
You may test the files on a running system by replacing the files from another OS (otherwise File Protection will restore the files).
In this case, pay attention to the filenames, on multiprocessor systems, rename ntkrnlmp.exe to ntoskrnl.exe and ntkrpamp.exe to ntkrnlpa.exe. Hal filename is always hal.dll.
Or integrate them on the CD (rebuilding SP3.CAB and repacking ntkrnlmp.ex_, ntoskrnl.ex_, hal.dl_, halaacpi.dl_, halacpi.dl_, halapic.dl_, halmacpi.dl_ and halmps.dl_).
No need to include a /PAE switch in boot.ini, as this works just like on Server 2003.
As I've patched the files properly, ntoskrnl.exe automatically chainloads the PAE kernel, ntkrnlpa.exe.
PS: Only supports Windows XP SP3. Another version supporting Server 2003 will be released later.

#3632 | daniel_k | ⇗ @gordo999 and ⇗ @Mattiwatti Me and ⇗ @diderius6 have tried to mod the last Intel LAN XP driver to support the Intel I219-V, but gave up. Try to get a XP compatible PCIe (Intel, Realtek, Atheros) or USB (ASIX, Realtek?!) LAN adapter.

#3633

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3615

> Your predictions were correct. Even in Windows 7 the performance of the toshiba external disk connected to the USB3 port are not as expected. A tiny better with the samsung M3 portable, but the main problem is that there is no way to make the usb3 function available on my crazy board also after a shutdown.
> At this point, I'm thinking it's time to put this board aside, also because I have another board where usb3 doesn't work at all and I still have not found a way to solve.

Try this (not sure if really XP compatible):
⇗ http://ftp.vector.co.jp/10/14/2012/wpcrs120.exe
⇗ http://www.a7vtroubleshooting.com/articles/wpcrset/index.htm
⇗ @Mattiwatti
You seem to have many experience with driver development, can you help us, please?
Have you ever seem a driver sample which we can modify to suit our needs?
Basically we need to set two PCI configuration registers in the Intel XHCI controller in order to properly enable USB3 speeds.

#3634

daniel_k

> Zitat von ⇗ schreiberstein im Beitrag ¶ #3591

> @daniel_k
> Hey! Interesting news! I think you are onto something great with that new XHCI driver and the HAL patcher.
> Things seem to be getting better and better for us folks with newer machines.
> I have been using XP with the 4GB patch several times now and it seems to be working fine! (Like Server 2003 with native 32GB PAE)
> Perhaps it is just a problem of the Advanced Chrome version I am using. Palemoon seems stable, so is every other application.
> It is very satisfying. No audio artifacts with integrated Realtek HD either.

Just released new WinXPPAE. This one was tough, too many files, several versions... but it's done.
The TI/ASMedia XHCI drivers are promising, but can't do it myself, really need help.

#3635

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3632

> Me and @diderius6 have tried to mod the last Intel LAN XP driver to support the Intel I219-V, but gave up.

⇗ @daniel_k ...thanks. That's what the memcpy/memcyp_s mod was about. I see memcpy_s, sprintf_s, strcpy_s, etc., are all listed as missing in dependency walker. I am sure those functions are not missing but relocated. Just reading that memcpy_s is a member of the memcpy group. The former copies between buffers whereas memcpy copies between memory addresses. They would not remove those functions from ntoskrnl, I am betting. In fact, there are only 10 functions missing in ntoskrnl and 4 of them are related to copy and string functions.
As Mattiwatti pointed out, the main problem is with ndis.sys. I am going to try what he said and get a copy from an x86 version of W7 to compare them. The function listed as missing in ntoskrnl are: EtwWrite, IoGetAffinityInterrupt, KeGetProcessorIndexFromNumber, KeGetProcessNumberFromIndex, KeQueryHighestNodeNumber, PoRegisterPowerSettingCallback, PoUnregisterPowerSettingCallback, memcpy_s, sprintf_s, strcpy_s, vprintf_s.
ndis.sys is another matter with 29 reported missing functions. Keep in mind that I am a noob with dependency walker and I may be misinterpreting the results. I am going on the functions marked red, although there may be other reasons why they are marked red.

#3636

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3626

> @diderius6
> Thanks for the explanation. You confirmed what @gordo999 reported in a previous post, the trouble is there, XP can't boot from a nvme disk with 4096 byte per sector and no 512 byte emulation mode. But how can I figure if my nvme disk has or not the 512e? I understand, if I had it I wouldn't have found so many difficulties for cloning the disk or restoring an XP image and also the partitioning software would have listed the nvme disk.

Offhand I can't remember what brand your NVME is... Looks like you are using a Samsung. But there were some Intel SSDs that using a utility you could change the sector size by flashing it. I don't know if Samsung has a similar way to flash it to do the same. Also maybe one exists for NVME or contact Samsung to see if they have one or will make one.
But the other question is when your NVME is installed into the motherboard, can you boot into both Windows 7 and 10 using a normal SSD or hard drive and then see if your NVME drive shows up in Disk Management at all in either OS? And if so do you see any partitions shown?

#3637 | gordo999 | ⇗ @Mattiwatti ...exactly like you called it. Got an ndis.sys and an msrpc.sys from a w7 x86 disk and dropped them in with the other files and it asked for a netio.sys. Ndis is now happy but it's relationship with ntoskrnl has soured. Msrpc and netio.sys are happy but their relationship with ntoskrnl is off. The Zwxxxxx files are mainly related to msrpc.sys and marked in red. Some are as you said, alpc related. Good call. :-)
#3638 | cedar | ⇗ @gordo999 Sorry about misinforming you about the LAN driver, the working version was an earlier one. Flaking memory...

#3639

Andalu

⇗ @gordo999
I'll try also samsung magician, but the newest version doesn't work in XP and the latest for XP I don't think it can detect the nvme disk. I don't know if I can solve by updating my nvme with the 970 EVO firmware. To recognize the nmve disk from another XP hard disk I installed the ofa 1.3 driver, the only that works in XP. I don't find any samsung driver for XP.
Here the NVMe disk detected in bios (it is never listed in the boot menu section):
⇗ ⇗
EDIT: I tried to update the firmware with the 970 EVO version but the samsung dos utility give me the message: "No supported SSD detected for firmware update!!!"

#3640 | Andalu | ⇗ @XPLives here the shots, the nvme is correctly detected in all SO: ⇗ ⇗ ⇗

#3641

daniel_k

⇗ @gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3632

> Me and @diderius6 have tried to mod the last Intel LAN XP driver to support the Intel I219-V, but gave up.

It's the last XP driver ever released with no missing dependencies
We've tried to patch the device ID with no success.
I217, I218 and I219 are from the same family.
Just attached all drivers I have collected, including the XP one.
Earliest drivers when a new device ID was added.
- I217_I218: XP only
- I219_1_2: Win7 only, variants 1 and 2 (IDs 156F/1570/15B7/15B8)
- I219_3_4_5: Win7 only, variants 3, 4 and 5 (IDs 15B9/15D7/15D8/15E3/15D6)
- I219_6_7: Win7 only, variants 3, 4 and 5 (IDs 15BD/15BE/15BB/15BC)
Official means ID is in INF file.
Unofficial means ID is NOT in INF file, but support is present in driver .SYS file.

#3642

Andalu

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3631

> WinXPPAE 2.0, a small utility to patch all kernel and hal files, supporting all languages and versions 5512 (SP3) and later:
> What's new:
> - thanks to @Mov AX, 0xDEAD, now includes HAL patches for ACPI Timer fix and proper memory management from Server 2003.
> - creates backups files (.bak) automatically
> To use it, copy the following hal and kernel files (found in SP3.CAB) and the utility to the same folder.
> ntkrnlmp.exe - Multiprocessor Kernel
> ntoskrnl.exe - Uniprocessor Kernel
> ntkrpamp.exe - Multiprocessor PAE Kernel
> ntkrnlpa.exe - Uniprocessor PAE Kernel
> hal.dll - Standard PC HAL
> halaacpi.dll - ACPI Uniprocessor HAL
> halacpi.dll - ACPI HAL
> halapic.dll - MPS Uniprocessor HAL
> halmacpi.dll - ACPI Multiprocessor HAL
> halmps.dll - MPS Multiprocessor PC HAL
> Run WinXPPAE with the appropriate command line.
> Usage: winxppae [/4GB | /ALL | /NB or /NOBACKUP]
> /4GB Enables PAE limiting RAM to 4Gb to avoid stability issues.
> /ALL Enables PAE with unlimited RAM, may have stability issues.
> /NB Does not create backup copies of original files.
> /NOBACKUP Same as /NB
> You may test the files on a running system by replacing the files from another OS (otherwise File Protection will restore the files).
> In this case, pay attention to the filenames, on multiprocessor systems, rename ntkrnlmp.exe to ntoskrnl.exe and ntkrpamp.exe to ntkrnlpa.exe. Hal filename is always hal.dll.
> Or integrate them on the CD (rebuilding SP3.CAB and repacking ntkrnlmp.ex_, ntoskrnl.ex_, hal.dl_, halaacpi.dl_, halacpi.dl_, halapic.dl_, halmacpi.dl_ and halmps.dl_).
> No need to include a /PAE switch in boot.ini, as this works just like on Server 2003.
> As I've patched the files properly, ntoskrnl.exe automatically chainloads the PAE kernel, ntkrnlpa.exe.
> PS: Only supports Windows XP SP3. Another version supporting Server 2003 will be released later.

I tried both /4Gb and /ALL options of the new WinXpPAE patch and I copied by hand from another hard disk all the files in windows\system32 (included the renamed ntoskrnl.exe and ntkrnlpa.exe) but on restart I got a blank screen immediately after the XP logo screen. It starts correctly when I used the hal.dll 5.1.2600.5687 extracted from ¶ 'hal_pae_fix' and also the ram is correctly visualized.

#3643

gordo999

> Zitat von ⇗ cedar im Beitrag ¶ #3638

> Sorry about misinforming you about the LAN driver, the working
> version was an earlier one. Flaking memory...

⇗ @cedar ...no apology necessary. These days, I can't go from the kitchen to the bedroom without forgetting why I went there. It's not till I go back to the kitchen that I remember,

#3644

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3641

> Just attached all drivers I have collected, including the XP one.

⇗ @daniel_k ....thanks dk, I'll have a look.

#3645

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3639

> I'll try also samsung magician, but the newest version doesn't work in XP

⇗ @Andalu ...do you have a dual boot with W7 or W10? You could run it in W7 to see if it detects the SSD. If not, what error do you get if you try to install/run Magician in XP? XP and W7 are both fairly compatible systems with the exception that XP runs 16-bit apps. I can't see why Magician would not run in XP unless it was written to detect the OS and not install simply because the writer did not want it to run on XP. I don't know if DOS can detect an ntfs file system but I seem to recall a DOS version that can read ntfs, Maybe I'm wrong.

## Page 244

#3646

Mattiwatti

> Zitat von ⇗ gordo999 im Beitrag ¶ #3628

> @Mattiwatti ....thank you kindly for the detailed and in-depth explanation. I have enough experience with reversing and the NT Kernel to follow you and I would dearly love getting into ntoskrnl to the level you mention. However, the only debugger of which I am aware that will trace through ring 0 code is softice. I have asked experienced people if windbg will trace through it but the answers I receive are vague as to what constitutes ring 0. Anytime I have tried to enter ring 0 with wdbg at a sysenter point, it turfs me out the other end without tracing through the code. Having said that, since I am working in x86 code, I would love to get SI going on this converted XP machine and I know it won't be easy. Tried the other night for a laugh and got a bsod with stop: 0x24, apparently related to ntfs.sys. Does that mean SI only runs on a FAT32 system? Don't think so since I recall using it to trace into the MFT via ntfs.sys. Don't want to get off-topic talking about debuggers but if you have anything to add on that topic perhaps you would be kind enough to PM me.

I'll reply to the rest of your questions via PM, but I'll answer the question of what constitutes 'ring 0' here. For the longer and more accurate version, read ⇗ Protection ring on Wikipedia, although that article is not specific to x86. In x86 (and x64), as the article also mentions, there is the notion of the CPL (Current Privilege Level), and the generally agreed upon definition is that CPL = 0 constitutes ring 0, aka 'kernel mode'. Neither Windows NT (or 9x for that matter) nor Linux use any CPLs other than 0 and 3, so 'ring 0', 'kernel mode', 'supervisor mode' (NB: not hypervisor!), 'CPL 0' are all interchangeable terms for the same thing and can be contrasted with 'ring 3', 'CPL 3' and 'user mode' which is the normal operating environment for a program you would write to execute some specific task. Very few operating systems use more than 2 privilege levels, even though many processor architectures offer more than this in theory. It is also sometimes useful to define a 'ring -1' when describing a virtualized OS running within a hypervisor using e.g. Intel VT-x or AMD's SVM. Finally there are the notions of 'ring -2' for SMM (System Management Mode) and 'ring -3' (Intel ME; as far as I know the AMD PSP does not run in ring -3 due to being on-CPU, unlike the Intel ME which runs even when the main CPU is off). These are generally only used in security research, where a vulnerability in a 'lower' (more privileged) ring is worse since it is theoretically more powerful and/or harder to detect. Since we are interested in debugging ring 0 code, and the question is whether WinDbg is able to do this, the answer is: yes it can! Not only can WinDbg debug kernel mode code, I'd say it's the only debugger worth considering when the target system is Windows NT. SoftICE is certainly an impressive creation, but I'd sooner call it a curiosity than a real debugger. You should view a debuggee as a sick patient. Correctly diagnosing a patient is only possible when done completely externally, i.e. without making use of one or two of the patient's organs and hoping they continue to work throughout the diagnosis, which is how I see SoftICE. As a simple example: suppose you are developing a filesystem driver, or a disk controller driver such as an NVMe one. Or more likely, suppose you're not doing either of these, but that the system somehow fails to boot with BSOD 0x7B (INACCESSIBLE_BOOT_DEVICE). What's SoftICE going to do? The answer is nothing, since if the boot disk cannot be accessed, SoftICE cannot be loaded. There are other more insidious scenarios where SoftICE will give a wrong or skewed perspective of the system due to the fact that by nature it lives on the 'patient' system, and even affects its state simply by being loaded.
It's true that there are certain instructions WinDbg cannot step through, at least in my experience (mostly with VirtualBox - it's possible that some of these will work correctly when using a serial port since VirtualBox itself uses some creative protection ring magic to do its work). These are all related to ring transitions or instructions closely related to those. I don't generally use 32 bit operating systems, but the sysenter you mentioned would be an example of this. The equivalent x64 instruction is 'syscall': you cannot step into this instruction and expect to land cleanly on the other (kernel mode) side. Another instruction you should avoid stepping into is 'swapgs', which is used on the return from ring 0 to ring 3 on x64 (unsure about x86). Stepping into a swapgs will crash WinDbg and as a result hang the debuggee. Why is this? I don't know, but I generally assume that this is something that is actually impossible (or close to) to fix, since WinDbg supports basically anything else the NT kernel might ever do. It is after all the debugger used by the NT team to develop NT itself. Fortunately the solution to this problem is fairly simple: don't step into these instructions. If that sounds unhelpful, consider the following: what are you trying to achieve when stepping into a 'sysenter'? Generally this is an indicator that you are debugging the wrong piece of code. In the case of sysenter, this is an instruction that is executed in user mode to transition to kernel mode. Instead, set a breakpoint on the syscall you wish to debug (e.g. `'bp nt!NtCreateFile'` to set a breakpoint on the NtCreateFile syscall in ntoskrnl.exe in ring 0; 'nt' is short for 'ntoskrnl' in WinDbg). Similarly, stepping through a 'swapgs' means you are debugging the generic code that is executed upon return from every syscall. In general there is little reason to be here since the code is of little interest to anyone except perhaps the NT team. If you wish to continue debugging the user mode program that executed some syscall, my first advice would be: don't. You can use a user mode debugger such as x64dbg or a second instance of WinDbg running on the debuggee instead, which will be much easier and give better results. But if you must do this from WinDbg debugging ring 0 code, find the next instruction that will be executed in the program in user mode and set a breakpoint on that. Here is an example of an x64 program executing 'NtWriteFile':

    fffffadf`7dec61d0 fffff800`008517ea nt!KiSwapContext+0x7b [C:\<snip>\base\ntos\ke\amd64\ctxswap.asm @ 74]
    fffffadf`7dec6350 fffff800`00849949 nt!KiSwapThread+0x3ea [C:\<snip>\base\ntos\ke\thredsup.c @ 2012]
    fffffadf`7dec63c0 fffffadf`8fc51109 nt!KeWaitForSingleObject+0x589 [C:\<snip>\base\ntos\ke\wait.c @ 1242]
    fffffadf`7dec6450 fffffadf`8fc50f07 Ntfs!NtfsWaitSync+0x28
    fffffadf`7dec6490 fffffadf`8fc51e43 Ntfs!NtfsNonCachedIo+0x3c9
    fffffadf`7dec6700 fffffadf`8fc5131a Ntfs!NtfsCommonWrite+0x24da
    fffffadf`7dec69e0 fffff800`00999e22 Ntfs!NtfsFsdWrite+0x2e4
    (Inline Function) --------`-------- nt!IoCallDriver+0x35 (Inline Function @
    fffff800`00999e22) [C:\<snip>\base\ntos\inc\io.h @ 3281]
    fffffadf`7dec6ab0 fffff800`00994bab nt!IopSynchronousServiceTail+0x132 [C:\<snip>\base\ntos\io\iomgr\internal.c @ 7510]
    fffffadf`7dec6b10 fffff800`008b1b63 nt!NtWriteFile+0x7eb [C:\<snip>\base\ntos\io\iomgr\write.c @ 785]
    fffffadf`7dec6c00 00000000`77ef02aa nt!KiSystemServiceCopyEnd+0x3 (TrapFrame @
    fffffadf`7dec6c70) [C:\<snip>\base\ntos\ke\amd64\trap.asm @ 1917]
    00000000`0012f3d8 00000000`77d7030b ntdll!ZwWriteFile+0xa
    00000000`0012f3e0 0000005c`003a0043 0x77d7030b
    00000000`0012f3e8 00000000`00000000 0x0000005c`003a0043

Note that I do not have debug symbols loaded for the program, which is why you only see addresses for the user mode part of the stack vs symbol names for the ntdll and kernel mode portions. In this case, you would set the breakpoint upon return from the kernel, i.e. 'bp ntdll!ZwWriteFile+0xa'. Realistically you will probably also want to skip the ntdll frame since it only contains generic syscall wrapper code, so you'd set a breakpoint at 0x77d7030b.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3628

> Your explanation re dependency walker is interesting. It had occurred to me to try it at some point but it had not occurred to me to load the entire drivers directory into the same test folder. Why not the entire sys32 directory as well? Having said that, if we are creating a directory with all those files, should it not work by running DW on a W7 machine?

There is no need to copy over system32 since it is already part of the search path. An exception would be if you want to test some modified file that normally lives in system32: you can just throw this in with the rest of the files in 'drivers' since the current directory is searched first. To elaborate: let's take our Intel network driver, which depends on both ndis.sys and ntoskrnl.exe, and (pretending for a moment that it actually works) suppose we wish to place it in a hypothetical 'drivers2' directory in system32. There would be a need to copy ndis.sys and all of its transient dependencies to this new 'drivers2' folder', but there would not be a need to copy ntoskrnl.exe, hal.dll or any other file living in system32. Kernel mode drivers follow the same rules as user mode programs when it comes to this. System32 is 'special' and always part of the search path; any other dependencies must be placed in the search path explicitly, usually by placing them in the same folder as the file being loaded.
Regarding your second question: yes, it is in fact perfectly possible to do the entire 'what-if' thing on a different system such as on Windows 7. In this case you do want to copy over system32, mostly for the sake of simply having easy access to all of the files. The easiest way to go about this would be to then copy the few kernel mode pieces living in system32 to system32\drivers. Off the top of my head you want at least ntoskrnl.exe, hal.dll, bootvid.dll, kdcom.dll, (if it exists) ATMFD.dll, and win32k.sys. Check Process Hacker or Process Explorer to see which modules are loaded if unsure.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3628

> > Zitat von ⇗ Mattiwatti im Beitrag ¶ #3612

> > ...what I have done is buy a simple ...Intel Gigabit CT Desktop Adapter

> From what I gather I'd need to find an older version. I looked the adapter up on the Intel site and they claim the 32-bit version won't run on anything below W7. Of course, that's Intel. They have unfortunately abandoned ship. I came across an adapter last night that is a USB - Network adapter....don't know if that would work.
> BTW...I managed to get online last night using a Cisco AM10 wifi adapter. It plugs into a USB port and for some reason sets itself up as a drive. Bit of a nuisance. The good news is that I am now activated.

Don't believe anything Intel says when it comes to OS compatibility. They have started pretending Windows XP and 2003 never existed (rather than simply pointing to the latest available drivers to support those OSes), and many of their newer drivers already don't support Windows 7 either, although you can at least still find Windows 7 drivers listed for now. The network card I linked works perfectly fine on Server 2003 x64, and I strongly suspect XP x86 as well since they have the same major NDIS version. Of course, if the USB adapter with wifi works, there is no need to get the PCIe card. Personally I prefer wired over wireless, and PCIe over USB. Reason: wifi runs on top of ethernet, and USB runs on top of PCIe... and simpler stuff breaks less often.

#3647

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3633

> Try this (not sure if really XP compatible):
> ⇗ http://ftp.vector.co.jp/10/14/2012/wpcrs120.exe
> ⇗ http://www.a7vtroubleshooting.com/articles/wpcrset/index.htm

It workssss!!
Your are great! Thank you very much again

#3648

Andalu

> Zitat von ⇗ gordo999 im Beitrag ¶ #3645

> @Andalu ...do you have a dual boot with W7 or W10? You could run it in W7 to see if it detects the SSD. If not, what error do you get if you try to install/run Magician in XP? XP and W7 are both fairly compatible systems with the exception that XP runs 16-bit apps. I can't see why Magician would not run in XP unless it was written to detect the OS and not install simply because the writer did not want it to run on XP. I don't know if DOS can detect an ntfs file system but I seem to recall a DOS version that can read ntfs, Maybe I'm wrong.

Firstly, in windows7, I uninstalled the ofa 1.3 driver and installed the Samsung NVMe Driver 3.2. After this, I installed samsung magician but the program does not seem to do much for my problem. It simply lists some information about the disk and does not allow to do any other operation than the benchmark.
The program you talking about may be ntfs4dos? If so, how could it help me?

#3649

gordo999

⇗ @Mattiwatti ....I know this is getting off topic but there are posters in this thread who may find it of interest in relation to the content of the thread. Besides, I want to contribute to this thread by tracing into the LAN driver, for example, to see what, if anything, can be done to get it going. As you have claimed, it's likely impossible, if not really hard, due to the number of functions absent in ntoskrnl and ndis.sys. That's what I am trying to find out in this discussion. Is there anything that can be done via modding to make it work?

> Zitat von ⇗ Mattiwatti im Beitrag ¶ #3646

> ...I'll answer the question of what constitutes 'ring 0' here.

I probably failed to present myself clearly. I did not mean to convey that I did not understand ring 0, I meant that people I have spoken to about it re windbg don't seem to be talking about the same code.

> Zitat von ⇗ Mattiwatti im Beitrag ¶ #3646

> It's true that there are certain instructions WinDbg cannot step through...it's possible that some of these will work correctly when using a serial port

I have not investigated that entirely but with my serial remote debugging sessions the target has to be rebooted for the source to find it. When the target reboots, it is stopped early in the boot process, before the logon screen, and as far as I can see it's possible to trace all the way to the desktop, if desired. In that case, Microsoft may have built in code to prevent wdbg getting past a sysenter or syscall into kernel code.

> Zitat von ⇗ Mattiwatti im Beitrag ¶ #3646

> ...what are you trying to achieve when stepping into a 'sysenter'?

There are times when the system is called from a user mode app and the system calls back into user mode, sometimes multiple times, before returning after the sysenter. If you don't enter system code at sysenter you miss the call back and there could be code in the call back in u-mode you need to see. I have encountered that many times with SI, tracing into system code then suddenly being back in user code in the app I am debugging, yet well before the system code returns you to the original call for the u-mode app at sysenter.
This action would also make it very difficult to follow a cold code read in IDA. In IDA, a function often begins with no reference to where it was called from. It's likely being called from system code via a call to system code elsewhere. You'd need a debugger to confirm that.

> Zitat von ⇗ Mattiwatti im Beitrag ¶ #3646

> Instead, set a breakpoint on the syscall you wish to debug (e.g. `'bp nt!NtCreateFile'`

That's fine if you know the call you want to trap with a bp. It's kind of shotgun approach at times since you are guessing that the app might call via that function. What if it doesn't, and there is code during a system call that is called by the system before exiting the syscall? I agree that setting a BP is more elegant but sometimes you just have to trace to see where the code goes. I also agree with what you say below, that the system code itself is not of much interest. However, it's what the system code does with the calling parameters that can be of interest. Besides, if you want to learn how the system processes calls from U-mode, or just how a driver works, it's helpful to see the system in action. It's one thing to read about a PDO in theory, or see a it in table form in Windbg, and quite another to see the actually code and data related to a PDO. Some people are happy to set BPs and ignore the intervening code but I find the implementation of assembly language to be fascinating, especially as related to functions in a higher level language like C++.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3628

> There is no need to copy over system32 since it is already part of the search path.

As I said, if I need to run DW from W7 for a driver in XP, I need the XP sys32 contents. I ensured that the pertinent equivalent files were in the folder you described. For example, if I was testing a driver from XP I made sure ntoskrnl, ndid.sys, hal, etc., from XP, were in the same folder.

#3650

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3648

> ... I installed samsung magician but the program does not seem to do much for my problem. It simply lists some information about the disk......The program you talking about may be ntfs4dos? If so, how could it help me?

⇗ @Andalu ...Yes, but Magician does see the disk. The disk is not being seen from XP. So, if Magician sees the disk in W7 the disk is OK and there is something going on in W7 that is not going on in XP. You have to find out what it is.
Re ntfs4dos: DOS cannot read an NTFS partition so you would not expect to see your SSD if it is formatted in ntfs from DOS. With something like ntfs4dos you should be able to detect the drive if it's there, should you not? If it uses a standard MBR, DOS should see it. Then again, can DOS read a 4kbytes/sector format?
Have you tried transferring the XP OS using an image? Use the free Macrium Reflect, or similar, to create an image of the XP partition running on a good system. You don't need to do the entire XP disk if you have related logical partition, they can be transferred later.You'll need an external disk drive or another drive with enough space to store the image, obviously not on the XP disk. Run your SSD as a logical partition connected to the good drive. Now use Macrium to restore the XP image to the SSD drive. The image does not care about the logical partitioning or formatting of the drive. After restoring the image to your SSD, add a boot.ini file, ntldr, and ntdetect to the root directory (C:\) of the SSD. During boot, ntldr should find the XP OS on the disk since you have pointed to it in boot.ini.

#3651

infuscomus

⇗ @diderius6 ⇗ @daniel_k
using my patcher program I tried patching ntoskrnl and hal from vista beta 5365 re-adding functions that were taken out from XP.
in hal I re-added

    HalDisableSystemInterrupt
    HalEnableSystemInterrupt

in ntoskrnl i re-added

    CcFastReadNotPossible
    CcFastReadWait
    IoInitializeCrashDump
    KeConnectInterrupt
    KeDcacheFlushCount
    KeDisconnectInterrupt
    KeIcacheFlushCount
    KiEnableTimerWatchdog
    PsCreateSystemProcess
    PsDereferenceKernelStack
    PsReferenceKernelStack
    WmiFlushTrace
    WmiQueryTrace
    WmiStartTrace
    WmiStopTrace
    WmiUpdateTrace

put ci.dll clfs.sys pshed.dll along with halmacpi.dll and ntoskrnl.exe in system32
can you test to see if this works?
infuscomus has attached files to this post

- ⇗ XP_5365_TEST.zip

#3652 | Naoto | I want to buy a laptop which uses intel 10th cpu,Is there a way tolet xp support 10th chips?

#3653

Fernando

⇗ @Naoto
Welcome to the Win-RAID Forum!
Since I am not an expert regarding your request, I have moved it into this already existing thread, where you can find a lot of information and hopefully get an answer from anyone among our XP Gurus.
Regards
Dieter (alias Fernando)

#3654 | PPeti66x | ⇗ @daniel_k The file halsp.dll really does not need to be patched by WinXPPAE 2.0?

#3655

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3640

> @XPLives
> here the shots, the nvme is correctly detected in all SO:
> ⇗ ⇗ ⇗

Could you identify your picture filenames with the Operating System in the name as well? From the three photos I am guessing you only tested in Windows 10 judging from the last picture with the icon with 4 blue windows logo or is that Windows 8.X?
I need you to go to "Disk Management" not "My Computer" to look at the drive.
Go to "Administrative Tools", "Computer Management", Under the Storage, there is "Disk Management".
It will show all the drives connected with their Partitions, File Systems, et cetera.
Try "Disk Management", NOT "My Computer" for XP/2003, Windows 7, and Windows 10 again and make sure you label the photos with OS. I will compare. Also another shortcut to "Disk Management" you can try RUN and type in "diskmgmt.msc".

#3656

XPLives

⇗ @gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3632

> ⇗ @gordo999 and @Mattiwatti
> Me and @diderius6 have tried to mod the last Intel LAN XP driver to support the Intel I219-V, but gave up.
> Try to get a XP compatible PCIe (Intel, Realtek, Atheros) or USB (ASIX, Realtek?!) LAN adapter.

Not to deflate your interest in getting newer Intel I21X on board to work in XP. It's quite possible if you commit enough time it could be a few months or could be years which could end in success or just reassuring the same failure. The question is is it worth the time to commit? The reason I ask is because it's easier to spend $5-$6 on eBay and get a PCIe x1 Realtek 8111E and pop it into your motherboard and get XP going fast. If that dead Ethernet port on the rear of your motherboard annoys you that's it's not working in XP you could at least use in in Windows Vista/7 perhaps?. Just hook up a network switch to connect two independent ethernet cables one from the onboard Intel, and the other from the Realtek NIC and depending on which OS is booted the network switch doesn't care and you'll get internet on both. I usually pick the PCIe x1 slot closest to the CPU which usually gets obstructed by my CPU cooler so it would have been a wasted slot anyhow so I actually gain the use of an empty slot for a purpose. Also Realtek NIC supports MAC OSX as well in case you wanted to do a Hackintosh experiment on Intel CPU system.
The other easiest option if you don't want to waste a slot. If you can get a USB PCIe card to fit into the 1st slot then you could have at least 4 USB slots and use one of them for a USB ethernet or USB Wifi adapter. It's not as pretty but you get to add at least 3 more USB devices while only sacrificing 1 slot.
But again you have to evaluate how much time you are going to put into getting that one rear motherboard ethernet to work. I'm pretty sure when Ice Lake or newer chipsets are released it is less likely you can get it to work as they may use a completely different chipset.
If there is one thing going forward that is lacking it's a universal modified VGA driver for 2D/3D that works with Intel HD Graphics past 4000, the AMD AM4 APU/GPU, or the nVidia graphics card Pascal+. Without such a driver a lot of useful programs just won't work.
The other is modifying the HDMI Audio out driver to work even though the nVidia or AMD graphics official drivers is not installed due to no proper driver. For whatever reason the HDMI Audio out is linked to the graphics driver and only works once the HDMI Video driver is installed. Perhaps someone can look into bypassing this requirement so the HDMI Audio out driver will work independently. Would save people from needing a USB or PCIe sound card/device.

#3657

XPLives

⇗ @Naoto

> Zitat von ⇗ Naoto im Beitrag ¶ #3652

> I want to buy a laptop which uses intel 10th cpu,Is there a way tolet xp support 10th chips?

Don't know as it would depend on which laptop brand / model, and is it UEFI only?
First why do you want to use XP on it?. No supported graphics driver for XP would exist except the built in MS one.

#3658

Andalu

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3650

> @Andalu ...Yes, but Magician does see the disk. The disk is not being seen from XP. So, if Magician sees the disk in W7 the disk is OK and there is something going on in W7 that is not going on in XP. You have to find out what it is.
> Re ntfs4dos: DOS cannot read an NTFS partition so you would not expect to see your SSD if it is formatted in ntfs from DOS. With something like ntfs4dos you should be able to detect the drive if it's there, should you not? If it uses a standard MBR, DOS should see it. Then again, can DOS read a 4kbytes/sector format?
> Have you tried transferring the XP OS using an image? Use the free Macrium Reflect, or similar, to create an image of the XP partition running on a good system. You don't need to do the entire XP disk if you have related logical partition, they can be transferred later.You'll need an external disk drive or another drive with enough space to store the image, obviously not on the XP disk. Run your SSD as a logical partition connected to the good drive. Now use Macrium to restore the XP image to the SSD drive. The image does not care about the logical partitioning or formatting of the drive. After restoring the image to your SSD, add a boot.ini file, ntldr, and ntdetect to the root directory (C:\) of the SSD. During boot, ntldr should find the XP OS on the disk since you have pointed to it in boot.ini.

When I tried to install magician 5.0 and 6.0 on XP I got the message: "This program requires Windows NT version 6.1.7600 or later". Below the info from magician 4.9.7 (the latest version XP compatible):
⇗ ⇗
I had already tried to restore an image created with macrium (and acronis also) but I had the same message "Incompatible Disk Selected". The macrium knowledgebase about that message:
⇗ https://knowledgebase.macrium.com/displa...e+Disk+Selected
Also the acronis site reports: "you can clone a 512 bytes/sector disk to 512 bytes/sector disk; you can clone a 4096 bytes/sector disk to 4096 bytes/sector disk; but you cannot clone a disk with logical sector size 512 bytes to disk with logical sector size 4096 bytes".
I found out the information which seem to exclude any further possibility:
⇗ ⇗
When the field 'byte/sector' reports 4096 means that the disk has no 512 emulation, so XP will never boots from it. Even as storage device there would be some problems because the trim function for this ssd doesn't seem supported in XP (trimcheck and corsair toolbox report trim 'not supported' or 'not working'. Adata toolbox doesn't detect the ssd).

#3659

Andalu

⇗ @XPLives

> Zitat von ⇗ XPLives im Beitrag ¶ #3655

> Could you identify your picture filenames with the Operating System in the name as well? From the three photos I am guessing you only tested in Windows 10 judging from the last picture with the icon with 4 blue windows logo or is that Windows 8.X?
> I need you to go to "Disk Management" not "My Computer" to look at the drive.
> Go to "Administrative Tools", "Computer Management", Under the Storage, there is "Disk Management".
> It will show all the drives connected with their Partitions, File Systems, et cetera.
> Try "Disk Management", NOT "My Computer" for XP/2003, Windows 7, and Windows 10 again and make sure you label the photos with OS. I will compare. Also another shortcut to "Disk Management" you can try RUN and type in "diskmgmt.msc".

sorry for the misunderstanding, here the screenshots from three different hard disk drives (I reported the OS type in the images because I can't get the picture naming work here in the forum):
⇗ ⇗ ⇗
Please also see my post above, thanks.

#3660

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3642

> I tried both /4Gb and /ALL options of the new WinXpPAE patch and I copied by hand from another hard disk all the files in windows\system32 (included the renamed ntoskrnl.exe and ntkrnlpa.exe) but on restart I got a blank screen immediately after the XP logo screen. It starts correctly when I used the hal.dll 5.1.2600.5687 extracted from ¶ 'hal_pae_fix' and also the ram is correctly visualized.

Must be a driver issue, possibly with AMDXHC.SYS.
Double checked all files and everything is fine.
Just did a clean install of XP SP3 fully updated with PAE enabled, but with no AMDXHC, just ASMedia and VIA.
100% stable and fast.
Don't have much time now, if you have PS/2 ports, connect some PS/2 keyboard and/or mouse, disable the USB driver and try again with WinXpPAE patched files to see if the issue is related to the hacked Intel driver.

## Page 245

#3661

daniel_k

> Zitat von ⇗ PPeti66x im Beitrag ¶ #3654

> @daniel_k
> The file halsp.dll really does not need to be patched by WinXPPAE 2.0?

While I could patch it, it isn't worth the effort and is not supported by Server 2003, on which the patch is based.
halsp.dll was designed for Compaq SystemPro Multiprocessor or 100% Compatible, from Nov 1989, see the wiki:
⇗ https://en.wikipedia.org/wiki/Compaq_SystemPro

#3662

stf

Hello,
I have no experience in editing BIOS or parts of SYS-OP,so excuse me for the stupidity of some questions.
My current PC is running XP home 32 bit on Quad core Q6700 with 5GB of RAM
that the system sees thanks to the bios and to a modification that I found on the net.
multi (0) disk (0) rdisk (0) partition (1) WINDOWS = "Microsoft Windows XP Professional" /kernel=ntkl64g.exe /hal=hal64g.dll / fastdetect / PAE / NoExecute = optin
currently the system is slow (latency and disk speed 198 Mb / s), having a 2T HDD disk, but everything I read (security) and see(cortana etc...)
on other PCs in windows 7 8 and 10 convince me to stay on windows XP despite the slowness.
I was thinking to solve the problem by switching to a sata SSD SAMSUNG AHCI to arrive, having sata 2
at 300 MB / s and much lower latencies.
but then I found this forum, I read part of "Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware"
I have difficulty / perplexity in understanding how to proceed.
My question is:
wanting to buy a new PC based on one of the 2 processors below
intel I9 9900k 16 threads PCIe 3.0 SAMSUNG EVO plus o
AMD Ryzen 3900 12 cores 24 threads PCIe 4.0> AORUS SSD
it is possible to clone my current main partition of win 32, by first uninstalling the current drivers, on a temporary HDD,
boot the new PC, install your work, the patches and new drivers and also the NVME M.2 or pcie 3.0 or 4.0 drivers
, to then clone the system obtained , on a NVME ssd (SAMSUNG or aorus SSD NVME) bootable M.2 at 3500 Mb / s or if AMD M.2 5000Mb / s
I mean, with XP 32 bit home operating system, currently, it is possible on Intel 9900k or AMD ryzen 3900 with the most appropriate motherboard,
make work:
4K or 4096x 2160 monitor,
multithreading
NVME on M.2 (or M.2 NVME via PCIe adapter) the OPTANE intel on pcie costs a lot,
64 gb ddr4
sata 3
USB 3.0 / 3.1 functional
LAN working
working audio
or, to understand, which motherboard it would be advisable to use or which platform, at present, should be used
to get the maximum benefit from the current hardware with XP 32 bit home.
Thanks !

#3663

Andalu

⇗ @daniel_k
tried with a clean XP (5.1.2600) install; only acpi.sys 5048 and AHCI+RAID driver v11.2.0.1006 mod by Fernando slipstreamed by nlite; no amd usb3 modded driver (¶ amdxhci_XP_final); only the ps/2 keyboard connected and no usb mouse, it still hangs at same point with a blank screen, immediately after the XP logo. Same behavior on a different board (haswell Q87).
Below the SHA-1 of the patched files (copied by hand from another system into the windows\system32 folder; only hal.dll, ntoskrnl.exe and ntkrnlpa.exe files need to be replaced there):

    hal.dll		020f03ed6b133765c879adf248ed3d2d99109bd3
    halaacpi.dll	c7fbaf343c827e8a2f0bc9e30148f06697a3c86b
    halacpi.dll	aa6fc0c1ab163bcc55cc3cbad368d3d6d3d9dc51
    halapic.dll	ba833399b2bbb51163ae702e7ec9d44f07f90589
    halmacpi.dll	be202c78dbf4d59880aa6a9430be05d4156d6764
    halmps.dll	30b791b03fbb67e0ac73e5b741df950aedf5cdf4
    ntoskrnl.exe	742fcf126111532187d4a2861c8b45f882757850

    ntkrnlpa.exe (/4GB)	39ca749c1988e469ea2b6c46eafd6537734fdcce
    ntkrnlpa.exe (/ALL)	2a67c6024530159b1f47565ca8ace3a46e39ad8a

#3664

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #3656

> It's quite possible if you commit enough time it could be a few months or could be years which could end in success or just reassuring the same failure. The question is is it worth the time to commit?

⇗ @XPLives ...I don't plan to make a career of it but this sort of thing interests me. I have had an interest in reversing for many years now but I have steered clear of modding windows components. Since msoft has essentially abandoned XP, and W7, we users are left with little option than to get XP working as best we can. In an overall sense there is not much of a benefit to me to get XP going on this new mobo, it's more for the principle. It's still a good and useful OS and it's a shame to abandon it. Except for a few hiccups XP is running really well on the new mobo. I have to thank the posters in this thread and Fernando for hosting it.

#3665 | cedar | ⇗ @gordo999 Agree, going back to the original room does connect back what was lost in the earlier process.

#3666

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3658

> When the field 'byte/sector' reports 4096 means that the disk has no 512 emulation, so XP will never boots from it. Even as storage device there would be some problems because the trim function for this ssd doesn't seem supported in XP (trimcheck and corsair toolbox report trim 'not supported' or 'not working'. Adata toolbox doesn't detect the ssd).

⇗ @Andalu ...that's not exactly true from what I understand about 512e emulation. If you have 512e emulation, the emulator treats each 4096 byte sector as 8 x 512 bytes/sectors per 4096 byte sector. I would think that means any app looking at the SSD would see 512 bytes/sector if it is in emulation mode.
Have you found out yet if your SSD has 512e emulation? It it doesn't, I can see the point being made above re XP. On a 512 byte/sector medium, the MBR is written right at the front of logical sector 0. Right behind it is some boot code then a logical partition table which ends at sector 0x63. In other words, that section is 64 sectors long. 64 sectors is 64 x 512 bytes/sector = 32,768 bytes. Divide that by 4096 and you get 8 sectors of the 4k sectors.
What would happen if you found a way to write the data covering 64 sectors on a 512 byte/sector format into the first 8 bytes of the 4k format? You claim above, that the disk is rejected when the app sees a 4k format. Is that true with the Windows boot code in BIOS? I hardly think they'd have enough space in BIOS to check that out. Maybe they do, but there is a section on this site dealing with BIOS mods.
When a system boots, and BIOS reads cylinder 0, head 0, sector 0, it should not care how long the sector is. All it reads is the jump statement in the MBR that sends it to an address in BIOS which contains the boot code. If you boot your system from the SSD, what errors do you get, if any? Does it give an error or just a blank screen?

#3667

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3651

> using my patcher program I tried patching ntoskrnl

⇗ @infuscomus ...is your patcher a private patcher or one available on the Net?

#3668 | infuscomus | ⇗ @gordo999 it's a copy of the old kernelex 3.6 that I've been modifying - from what I can see it isn't available on the internet anymore.

#3669

gordo999

> Zitat von ⇗ stf im Beitrag ¶ #3662

> ...it is possible to clone my current main partition of win 32, by first uninstalling the current drivers, on a temporary HDD, boot the new PC, install your work, the patches and new drivers and also the NVME M.2 or pcie 3.0 or 4.0 drivers

⇗ @stf ...not quite as simple as that. I just started into this thread recently but I have a lot of experience with these systems. Even at that, I had to spend days trying to get the system going. I am not trying to discourage you, or to be unkind, I had to start somewhere. However, if you are new to this, and you're looking for a quick fix re getting XP going on a newer motherboard, you have a pretty steep learning curve ahead. No one really has the time to explain it on a step by step basis, although, if you begin reading at the first post in this thread, you can absorb a lot of what it's about. There are recent posts about problems with nvme.
What do you know about XP and why it won't boot on a newer motherboard? Do you understand acpi or ahci, even at a simple level? The first boot errors you will get are likely acpi and ahci related. What do you know about windows boot processes? What do you know about windows drivers? Explain stuff like that and what specific problems you are encountering. Like I said, go to the beginning of the thread and start reading. If something confuses you, research it on google, then ask for help with a specific question. But don't expect at this depth in the thread to ask a very general, vague question and receive a reply. Most of the posters are busy communicating with each other about specific issues and yours is very general, if not somewhat vague.
For example, you ask if it's possible to clone your main partition. That usually means the C: partition...partition 1. But you said a win32 partition. Does that mean XP, Win 7, 8, or Win 10...they all have 32 bit partitions available. Why would you uninstall the current drivers to an HDD then try to boot? The system won't boot without the drivers and with the original XP drivers it won't boot at all. Your question is extremely vague.

#3670 | infuscomus | this tool looks interesting ⇗ https://github.com/AxtMueller/Windows-Kernel-Explorer

#3671

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3670

> this tool looks interesting

⇗ @infuscomus ...thanks...they mentioned PCHunter in the description. I noticed it in my collection but I don't recall using it yet.
⇗ https://www.majorgeeks.com/mg/getmirror/pc_hunter,1.html

#3672

daniel_k

⇗ @stf
Personally, I'd go for the Intel.
Easier to get it working.
For graphics, you'll need a XP compatible card, such as NVIDIA GTX980Ti.
NVME is not fully stable, specially with Samsung NVME drives.
USB3 is working.
LAN works if Intel i211 or i217, Killer E2500 (depends on revision) or Realtek (depends on model), you might try an USB3 to LAN adapter.
Audio works probably, as 99% of current HDAudio codecs are from Realtek, which has XP drivers.

#3673

daniel_k

⇗ @Andalu
Don't know what the issue is.
I did many tests here before releasing the patcher.
- VirtualBox 8GB RAM
- Core i3-2310M "Sandy Bridge" Lenovo G470 8GB w/ Insyde BIOS
- i7-8700K / Z370 Gaming 3 / 16GB
Tested all patched HALs, with no issues on any of the systems.
Even tried on an old T6600 eMachines D525 with 4GB just to test patch stability.
Are you really sure you're not missing something?
What about trying storahci.sys or iastora.sys?
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (218)
iaStor is old and has issues on newer systems, maybe things get worse with PAE enabled.

#3674

infuscomus

⇗ @daniel_k
do you want to see the source code for my kernel patcher program?
you seem more knowledgeable than me so you might have better luck producing something useful with it
see this post for an example of what it outputs (patched hal ntoskrnl)
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (244)

#3675

gordo999

> Zitat von ⇗ stf im Beitrag ¶ #3662

> My current PC is running XP home 32 bit on Quad core Q6700 with 5GB of RAM that the system sees thanks to the bios and to a modification that I found on the net.
> multi (0) disk (0) rdisk (0) partition (1) WINDOWS = "Microsoft Windows XP Professional" /kernel=ntkl64g.exe /hal=hal64g.dll / fastdetect / PAE / NoExecute = optin

⇗ @stf ...OK...try again. You have a 32-bit XP on an older Q6700 but your boot.ini says XP Professional and the kernel and hal drivers have been modded to give you more RAM. You claim the system sees 5Gb, which is useless because a 32 bit system is limited to 4 Gb...2^32 = 4 Gb. It only has 32 bit address registers and unless you get inside the processor and increase it's register sizes, it cannot possibly address more than 4 Gb of RAM.
You only get a bit over 3 Gb because the system needs RAM to operate. If you start messing with the free space the system requires you stand a good chance of interfering with system processes that may need to expand in memory, ergo, your system may run really slowly. My suggestion is that you forget about squeezing more RAM from a 32-bit system. We used to do that with DOS, with the 640Kb of RAM because we were desperate. We'd squeeze RAM from the 640K - 1 meg RAM area where the display drivers resided and often memory would spill over and crash the system.
Get rid of the modded drivers, get XP running properly on its original drivers. Get your new mobo running with system like W10, or even an easier mod with W7. I was able to plug a disk created on an older system with W7 right into an ASUS B360M, a 300-series chipset with an 8th gen Intel i5-8400, and it ran straight to the logon screen on it's stock drivers. Of course, I had no USB drivers so I could not have a mouse or keyboard but luckily I had PS/2. I would strongly recommend that you find a mobo that has PS/2 ports, if available, since they will save your butt if USB is not there. You can buy two USB to PS/2 adapters.
Once the mobo is running with a newer OS, take your disk drive from the old system, with XP, and plug it straight into the new mobo SATA port. I did this will all other drives unplugged and I had my SATA drives set in BIOS to be hot-plugged. The XP disk can interfere with other OS installations and once it is running, if hot-plugged, it will show up in the other OS file manager. Boot it. The first thing you will likely see is an acpi related 0xA5 error. Get one of the modded acpi.sys drivers from this thread, I used the acpi.sys from Diderius6, and replace the acpi.sys in your XP directory. Apparently, daniel_k has one as well. If you have a running W7 system, or even W10, you can see and replace files on the XP drive from Windows Explorer in the other system. You can even mod it's registry from W7 using the Load Hive function in W7 registry.
Boot again. The next error will likely be an 0x7B related to ahci, namely the SATA controller. The disk will likely boot fine up till the boot screen but when Windows tries to start, it will crash with an 0x7B bsod. Fernando has a driver which is used in the SP4 unofficial update that worked on my Asus mobo. I don't recall how I loaded it but there are several ways and you might find one here in this thread. Maybe someone could help me out with a link.
That will get you to the logon screen where hopefully you have a PS/2 keyboard/mouse to get you to the desktop. From there, you can start messing with the other modded drivers from this thread. I would not mess with your SSD till you get XP running from an HDD. Alternately, you can learn how to add the SATA drivers, etc., by replacing the drivers in the Windows directory/S32/drivers with the required iaStor driver and changing registry entries to suit.

## Page 246

#3676

stf

Hi, Thanks !
if i remember the patch was files of professional XP patched (must find the linc).
maybe is like you say, first of that patch i used
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro with /3GB" /fastdetect /3GB /Userva=2900
now i have this patch i don't know how work, i don't use virtual memory and the memory of the video board is near zero because disabled
(i use a PCI video card)
The PC is slow for what i use the software , but i have optimized at best(game), and for a XP PC is FAST a lot.
this board support max 8gb (ASUS P5B-VM DO)
stf has attached images to this post ⇗ XP conf.PNG

#3677

gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3675

> ... a 32 bit system is limited to 4 Gb...2^32 = 4 Gb. It only has 32 bit address registers and unless you get inside the processor and increase it's register sizes, it cannot possibly address more than 4 Gb of RAM.

Here I am answering my own posts...pathetic. ..I forgot about pae. Some 32-bit versions of Windows with the right processor will allow 32-bit systems to go beyond 4 Gb. However, it's only the server types. Here's a wiki blurb on PAE. Even Win 7, 8, and 10 are limited to 4 Gb. I stand to be corrected, maybe someone has a hack for extending beyond 4 Gb with these systems.
⇗ https://en.wikipedia.org/wiki/Physical_Address_Extension

#3678

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3659

> @XPLives

> > Zitat von ⇗ XPLives im Beitrag ¶ #3655

> > Could you identify your picture filenames with the Operating System in the name as well? From the three photos I am guessing you only tested in Windows 10 judging from the last picture with the icon with 4 blue windows logo or is that Windows 8.X?
> > I need you to go to "Disk Management" not "My Computer" to look at the drive.
> > Go to "Administrative Tools", "Computer Management", Under the Storage, there is "Disk Management".
> > It will show all the drives connected with their Partitions, File Systems, et cetera.
> > Try "Disk Management", NOT "My Computer" for XP/2003, Windows 7, and Windows 10 again and make sure you label the photos with OS. I will compare. Also another shortcut to "Disk Management" you can try RUN and type in "diskmgmt.msc".

> sorry for the misunderstanding, here the screenshots from three different hard disk drives (I reported the OS type in the images because I can't get the picture naming work here in the forum):
> ⇗ ⇗ ⇗
> Please also see my post above, thanks.

Okay now we're onto something. So for both Windows 7 and Windows 10 you did not install any drivers for the NVME? Is your NVME using the built in built in driver that came with Windows 7 and 10?
Now in "Disk Management"
Go to your "Disco 1" - your NVME drive letter, Use your mouse Right Click and choose "Properties"
There will be 4 tabs to pick from, "General", "Policies", "Volumes", "Drivers".
Click the "Volumes" Tab and make a screenshot.
Then on the same Window it says "Volumes:"
Select the Volume D: and then click the Properties button.
Now take a screenshot of this Window that pops up that should say "Local Disk (D:) Properties" but in your language.
Do this steps for both Windows 7 and Windows 10. So we should have 4 pictures total (2 for each OS).
Also you can do some information gathering of your NVME. Go to "Command Prompt", type this:
FSUTIL FSINFO NTFSINFO D:
Right Click on the Command Prompt Window and Choose "Select All", then hit the "ENTER" KEY. This will copy the data. Now go to Notepad and Ctrl+V to Paste and then save the file as NVMEW7.TXT
for Windows 10 do the same but change the output filename.
FSUTIL FSINFO NTFSINFO D:
Right Click on the Command Prompt Window and Choose "Select All", then hit the "ENTER" KEY. This will copy the data. Now go to Notepad and and Ctrl+V to Paste and then save the file as NVMEW10.TXT
Then locate these two files and upload them.

#3679

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3677

> > Zitat von ⇗ gordo999 im Beitrag ¶ #3675

> > ... a 32 bit system is limited to 4 Gb...2^32 = 4 Gb. It only has 32 bit address registers and unless you get inside the processor and increase it's register sizes, it cannot possibly address more than 4 Gb of RAM.

> Here I am answering my own posts...pathetic. ..I forgot about pae. Some 32-bit versions of Windows with the right processor will allow 32-bit systems to go beyond 4 Gb. However, it's only the server types. Here's a wiki blurb on PAE. Even Win 7, 8, and 10 are limited to 4 Gb. I stand to be corrected, maybe someone has a hack for extending beyond 4 Gb with these systems.
> ⇗ https://en.wikipedia.org/wiki/Physical_Address_Extension

The CPU must be > 32-Bit I think at least 36-Bit since PAE uses 36-Bit. Also the chipset limits it. I have one laptop that has issues breaking 3GB but one chipset newer it broke it so something else to do with the BIOS possibly since using the same CPU it was able to break it on one generation newer chipset. Don't know where the cut off is for desktops or the same. I have not tested Server 2003 on my old P4. Would be interesting to find which desktop chipset broke it.
For Windows 7 32-Bit -> Windows 10 32-Bit there is a patch made that allowed to see over 4GB limit with PAE. I assume this is very similar to Server 2003 PAE technique. But most people would probably use Vista 64-Bit or newer anyhow.
This gives an interesting idea if PAE was 36-Bit how to modify so PAE is closest to 64-Bit memory addressing for NT5.X 32-Bit OS. The other issue is expanding the amount of memory each process can use beyond 4GB.

#3680

Andalu

⇗ @XPLives

> Zitat von ⇗ XPLives im Beitrag ¶ #3655

> Okay now we're onto something. So for both Windows 7 and Windows 10 you did not install any drivers for the NVME? Is your NVME using the built in built in driver that came with Windows 7 and 10?
> Now in "Disk Management"
> Go to your "Disco 1" - your NVME drive letter, Use your mouse Right Click and choose "Properties"
> There will be 4 tabs to pick from, "General", "Policies", "Volumes", "Drivers".
> Click the "Volumes" Tab and make a screenshot.
> Then on the same Window it says "Volumes:"
> Select the Volume D: and then click the Properties button.
> Now take a screenshot of this Window that pops up that should say "Local Disk (D:) Properties" but in your language.
> Do this steps for both Windows 7 and Windows 10. So we should have 4 pictures total (2 for each OS).
> Also you can do some information gathering of your NVME. Go to "Command Prompt", type this:
> FSUTIL FSINFO NTFSINFO D:
> Right Click on the Command Prompt Window and Choose "Select All", then hit the "ENTER" KEY. This will copy the data. Now go to Notepad and Ctrl+V to Paste and then save the file as NVMEW7.TXT
> for Windows 10 do the same but change the output filename.
> FSUTIL FSINFO NTFSINFO D:
> Right Click on the Command Prompt Window and Choose "Select All", then hit the "ENTER" KEY. This will copy the data. Now go to Notepad and and Ctrl+V to Paste and then save the file as NVMEW10.TXT
> Then locate these two files and upload them.

The disk is recognized as a nvme in Win10 only. On both XP and Win7 it is seen as a generic 'pci device'. In XP the only driver that works is the ofa driver 1.3.
In Win7 I can install both the ofa driver 1.3 and the Samsung NVM Express Driver 3.2. The built in driver works for Win10 only and also there I can install the Samsung NVM Express Driver 3.2 too.
This time I think there all information you need about my disk, if not ask me again :)
⇗ ⇗
Andalu has attached files to this post

- ⇗ NVME.zip

#3681 | Andalu | ⇗ @gordo999 Thanks for all the info. But the problem remains unsolvable for me. First strange behavior: my asrock B250M-Pro4 board doesn't boot when the nvme is the only disk connected, it enters directly into the bios. It needs cd-rom device or another hard disk (even with no operating system) connected at a sata port and even in this case the boot blocks on the message: "Reboot and select proper boot device or insert boot media in selected boot device and press a key".

#3682

antome

boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
⇗

#3683

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3681

> "Reboot and select proper boot device or insert boot media in selected boot device and press a key".

⇗ @Andalu ...I have seen that error before and it happened when the SATA boot was pointing at the Intel RST driver with acceleration in BIOS rather than the AHCI driver. In my B360M BIOS, under Advanced/PCH Storage Configuration, there is a listing near the top for SATA Mode Selection. If you open it with the 'Enter' key it gives you two choices: AHCI or Intel RST With Intel Optane System Acceleration. When I selected the Intel setting to see what it did, I got the same message about 'reboot and select proper boot device'.
OK, I know you device is an SSD but on my mobo the SSD shares one of the SATA slots. If the SATA slot is set in BIOS on the Intel RST option, maybe it is interfering with your SSD. If you have the same BIOS, check that out and make sure the SATA mode is set to AHCI. Or, find out what the Intel RST setting does. It may be related to your SSD.

#3684

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3680

> @XPLives

> > Zitat von ⇗ XPLives im Beitrag ¶ #3655

> > Okay now we're onto something. So for both Windows 7 and Windows 10 you did not install any drivers for the NVME? Is your NVME using the built in built in driver that came with Windows 7 and 10?
> > Now in "Disk Management"
> > Go to your "Disco 1" - your NVME drive letter, Use your mouse Right Click and choose "Properties"
> > There will be 4 tabs to pick from, "General", "Policies", "Volumes", "Drivers".
> > Click the "Volumes" Tab and make a screenshot.
> > Then on the same Window it says "Volumes:"
> > Select the Volume D: and then click the Properties button.
> > Now take a screenshot of this Window that pops up that should say "Local Disk (D:) Properties" but in your language.
> > Do this steps for both Windows 7 and Windows 10. So we should have 4 pictures total (2 for each OS).
> > Also you can do some information gathering of your NVME. Go to "Command Prompt", type this:
> > FSUTIL FSINFO NTFSINFO D:
> > Right Click on the Command Prompt Window and Choose "Select All", then hit the "ENTER" KEY. This will copy the data. Now go to Notepad and Ctrl+V to Paste and then save the file as NVMEW7.TXT
> > for Windows 10 do the same but change the output filename.
> > FSUTIL FSINFO NTFSINFO D:
> > Right Click on the Command Prompt Window and Choose "Select All", then hit the "ENTER" KEY. This will copy the data. Now go to Notepad and and Ctrl+V to Paste and then save the file as NVMEW10.TXT
> > Then locate these two files and upload them.

The disk is recognized as a nvme in Win10 only. On both XP and Win7 it is seen as a generic 'pci device'. In XP the only driver that works is the ofa driver 1.3.
In Win7 I can install both the ofa driver 1.3 and the Samsung NVM Express Driver 3.2. The built in driver works for Win10 only and also there I can install the Samsung NVM Express Driver 3.2 too.
This time I think there all information you need about my disk, if not ask me again :)
⇗ ⇗

Thanks for going deeper.
Andula in the Windows 7 Photo, what happens when you click on the Volume Tab, then select the D: drive in the list before clicking Properties? I didn't see you highlight the D: before hitting Properties so it didn't focus on that drive.
However both Win7 and Win10 confirms the drive is MBR which at first I thought maybe you were using GPT so that wasn't the case.
I looked at the sectors information and it definitely is recognized as a 4K drive. This is why Windows 7 won't recognize it. Only Windows 8.X-> Windows 10 supported 4K native sector drives.
But since only Windows 10 can see the drive. Go to Disk Management and select that Drive and right Click and Delete that Partition so it should be Unallocated and Blank.
Next select that drive again and right click on the Disco 1 area to the left of the partition chart to see if the options convert to MBR or GPT show up?
If it's saying it's on MBR then convert to GPT and see if it shows GPT, then again convert GPT back to MBR and confirm it's back to MBR.
Now see if they will now allow you to create a FAT32 Partition. Should be limited to 32GB as that's the forced partition size limit on Windows but we will use FAT32 in this case to test, you can format the 32GB partition with allocation unit size 16,384 Bytes or 16KB. Do not create any more partitions.
Repeat the same photo and Command Prompt steps again we did for Windows 7 and 10 in the last message instructions. I want to see if anything changed and if Windows 7 can see that drive and allow you to open the drive letter at all or even in XP.

#3685

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3682

> boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> ⇗

This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
Reboot on Z270 and make sure it works and boot correctly back into XP.
If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

#3686

Andalu

⇗ @XPLives

> Zitat von ⇗ XPLives im Beitrag ¶ #3684

> Thanks for going deeper.
> Andula in the Windows 7 Photo, what happens when you click on the Volume Tab, then select the D: drive in the list before clicking Properties? I didn't see you highlight the D: before hitting Properties so it didn't focus on that drive.
> However both Win7 and Win10 confirms the drive is MBR which at first I thought maybe you were using GPT so that wasn't the case.
> I looked at the sectors information and it definitely is recognized as a 4K drive. This is why Windows 7 won't recognize it. Only Windows 8.X-> Windows 10 supported 4K native sector drives.
> But since only Windows 10 can see the drive. Go to Disk Management and select that Drive and right Click and Delete that Partition so it should be Unallocated and Blank.
> Next select that drive again and right click on the Disco 1 area to the left of the partition chart to see if the options convert to MBR or GPT show up?
> If it's saying it's on MBR then convert to GPT and see if it shows GPT, then again convert GPT back to MBR and confirm it's back to MBR.
> Now see if they will now allow you to create a FAT32 Partition. Should be limited to 32GB as that's the forced partition size limit on Windows but we will use FAT32 in this case to test, you can format the 32GB partition with allocation unit size 16,384 Bytes or 16KB. Do not create any more partitions.
> Repeat the same photo and Command Prompt steps again we did for Windows 7 and 10 in the last message instructions. I want to see if anything changed and if Windows 7 can see that drive and allow you to open the drive letter at all or even in XP.

Thank you for the help ;) As you can see below the changeover from MBR to GPT is not allowed, at least in windows:
⇗

> Zitat von ⇗ XPLives im Beitrag ¶ #3684

> Andula in the Windows 7 Photo, what happens when you click on the Volume Tab, then select the D: drive in the list before clicking Properties? I didn't see you highlight the D: before hitting Properties so it didn't focus on that drive.

The D: drive properties in Win7 are those shown in the image on the right, even if the volume does not seem to be highlighted.

#3687

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3686

> @XPLives

> > Zitat von ⇗ XPLives im Beitrag ¶ #3684

> > Thanks for going deeper.
> > Andula in the Windows 7 Photo, what happens when you click on the Volume Tab, then select the D: drive in the list before clicking Properties? I didn't see you highlight the D: before hitting Properties so it didn't focus on that drive.
> > However both Win7 and Win10 confirms the drive is MBR which at first I thought maybe you were using GPT so that wasn't the case.
> > I looked at the sectors information and it definitely is recognized as a 4K drive. This is why Windows 7 won't recognize it. Only Windows 8.X-> Windows 10 supported 4K native sector drives.
> > But since only Windows 10 can see the drive. Go to Disk Management and select that Drive and right Click and Delete that Partition so it should be Unallocated and Blank.
> > Next select that drive again and right click on the Disco 1 area to the left of the partition chart to see if the options convert to MBR or GPT show up?
> > If it's saying it's on MBR then convert to GPT and see if it shows GPT, then again convert GPT back to MBR and confirm it's back to MBR.
> > Now see if they will now allow you to create a FAT32 Partition. Should be limited to 32GB as that's the forced partition size limit on Windows but we will use FAT32 in this case to test, you can format the 32GB partition with allocation unit size 16,384 Bytes or 16KB. Do not create any more partitions.
> > Repeat the same photo and Command Prompt steps again we did for Windows 7 and 10 in the last message instructions. I want to see if anything changed and if Windows 7 can see that drive and allow you to open the drive letter at all or even in XP.

Thank you for the help ;) As you can see below the changeover from MBR to GPT is not allowed, at least in windows:
⇗

> Zitat von ⇗ XPLives im Beitrag ¶ #3684

> Andula in the Windows 7 Photo, what happens when you click on the Volume Tab, then select the D: drive in the list before clicking Properties? I didn't see you highlight the D: before hitting Properties so it didn't focus on that drive.

The D: drive properties in Win7 are those shown in the image on the right, even if the volume does not seem to be highlighted.

You didn't delete the partition first. You must delete the partition before you can change to MBR and GPT.
I had to translate "spazio disponibile" which means space available. When you delete the partition it should say "Unallocated space".
Or if I translated incorrectly is that a deleted partition? If so then it is strange you cannot change between MBR and GPT.
Ahh I noticed it is green highlighted. Usually this means extended partition. You need to remove all partitions.
If it really has no partitions Primary and Extended are gone then something is strange.
We can try to use Hex Editor and zero out Sectors 0-8.
Here's a free one.
⇗ https://mh-nexus.de/en/hxd/
Make sure you point to the correct disk and not your OS drive.

#3688

Andalu

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3683

> @Andalu ...I have seen that error before and it happened when the SATA boot was pointing at the Intel RST driver with acceleration in BIOS rather than the AHCI driver. In my B360M BIOS, under Advanced/PCH Storage Configuration, there is a listing near the top for SATA Mode Selection. If you open it with the 'Enter' key it gives you two choices: AHCI or Intel RST With Intel Optane System Acceleration. When I selected the Intel setting to see what it did, I got the same message about 'reboot and select proper boot device'.
> OK, I know you device is an SSD but on my mobo the SSD shares one of the SATA slots. If the SATA slot is set in BIOS on the Intel RST option, maybe it is interfering with your SSD. If you have the same BIOS, check that out and make sure the SATA mode is set to AHCI. Or, find out what the Intel RST setting does. It may be related to your SSD.

In my B250M bios, under Advanced/Storage Configuration, I have no SATA Mode Selection as you can see in the first image of a previous post ¶ here.
Can you upload the yours please?

#3689 | Andalu | ⇗ @XPLives You are right and I'm real groggy I'm trying now....

#3690

XPLives

> Zitat von ⇗ Andalu im Beitrag ¶ #3689

> @XPLives
> You are right and I'm real groggy
> I'm trying now....

Ahh... get some sleep no rush to get the data. I just noticed it was strange the "green border" and compared to mine. :)
Read my post again I updated slightly but since it looks like you didn't delete the partition then maybe not necessary to hexedit.

## Page 247

#3691 | Andalu | ⇗ @XPLives I did everything in Win10 as you explained ¶ here until the 'fsutil fsinfo ntfsinfo D:' command which give me the message: "the fsutil utility needs a local NTFS volume" (translated by me... so inaccurate :)). The partition (in MBR mode) has now a size of 31,2GB and has been formatted with the fat32 file system. No other partition created. No hex editing applied.

#3692

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3691

> @XPLives
> I did everything in Win10 as you explained ¶ here until the 'fsutil fsinfo ntfsinfo D:' command which give me the message: "the fsutil utility needs a local NTFS volume" (translated by me... so inaccurate :)).
> The partition (in MBR mode) has now a size of 31,2GB and has been formatted with the fat32 file system. No other partition created. No hex editing applied.

Yes that's correct because now it is a true FAT32 and not NTFS. Can you check under Disk Management for XP, W7, and W10 show the drive with snapshots?
Also can you access the NVME drive letter in XP, W7, and W10? Can you explore D: or copy a folder or file to it?
If you use Hex Editor go to Absolute Sector 0 on NVME drive and snapshot or copy it. And do the same for Sector 1-8 and upload it.

#3693

Andalu

⇗ @XPLives
I can access to the nvme partition in all SO and operate with it as a normal disk drive. Here the snaps.
Andalu has attached files to this post

- ⇗ NVME Fat32.zip

#3694

XPLives

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #3693

> @XPLives
> I can access to the nvme partition in all SO and operate with it as a normal disk drive. Here the snaps.

This is good. You can now see the NVME in XP.
I checked the Sectors. Now that you can access the partition in XP but you must change it back to XP Partition style not Windows 7 or 10.
In XP Disk Management you must now delete the partition. So now completely Unallocated Space "Non allocata" again.
Then go to HxD and enable "write" mode for NVME Drive F:.
Go to Sector 0-8, and 63, 64 and zero out the entire sector to 00s.
Then reboot the XP system.
Once in XP again go to Disk Management.
On NVME Drive,
Create the 2GB FAT16 Partition #1 and use allocation unit size 32,768 Bytes or 32KB and format.
Create the 32GB FAT32 Partition #2 and use allocation unit size 16,384 Bytes or 16KB and format.
Go to HxD and select NVME disk and copy absolute Sector 0-8, 63, 64 and upload it.
Next if you have time. If you got 98SE DOS boot disk using USB floppy you can try and format the first partition of NVME. Make sure all other drives are disconnected to prevent accidents. Only NVME attached and USB floppy as primary boot device to boot 98SE DOS.
Then type
Format C:/s
If it sees the drive it should format this partition #1.
Reboot and check the BIOS to see if NVME is set to Primary Boot Drive. Eject floppy disk so it won't access it. After it is done you can reboot.
If it works then it should boot to 98SE DOS on NVME and should then be possible to install XP to it on D:. Also test does FDISK work to see NVME.

#3695

Andalu

⇗ @XPLives
I deleted the partition in XP disk management to have unallocated space only. But now, about HxD, please keep in mind that I have never used a disk hex editor before :)
I already enabled the 'write mode' for the physical disk 2 (nvme) and to be sure: for '0-8' do you mean by selecting all the sectors from 0 to 8 at one step at time (1,2,3,4 etc. and after the sectors 63 and 64)? And mostly important: how to edit the 'entire sector' to 00s? :)
EDIT: I did it all in HxD, I just hope I didn't make a crap :)
Two partitions created in the nvme disk and formatted in fat16 and fat32.
Below the sectors exported from HxD in .txt format.
Andalu has attached files to this post

- ⇗ Fat16_Fat32.zip

#3696

antome

> Zitat von ⇗ XPLives im Beitrag ¶ #3685

> @antome

> > Zitat von ⇗ antome im Beitrag ¶ #3682

> > boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> > edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> > ⇗

> This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
> ⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
> XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
> Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
> Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
> Reboot on Z270 and make sure it works and boot correctly back into XP.
> If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

Thanks for the driver now something has changed, xp x64 in normal mode I get error 0x000000CA while in safe mode it starts correctly on the z390, how do I solve this problem? the same disk starts correctly on the z270
⇗ ⇗ ⇗

#3697

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3696

> > Zitat von ⇗ XPLives im Beitrag ¶ #3685

> > ⇗ @antome

> > > Zitat von ⇗ antome im Beitrag ¶ #3682

> > > boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> > > edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> > > ⇗

This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
Reboot on Z270 and make sure it works and boot correctly back into XP.
If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

Thanks for the driver now something has changed, xp x64 in normal mode I get error 0x000000CA while in safe mode it starts correctly on the z390, how do I solve this problem? the same disk starts correctly on the z270
⇗ ⇗ ⇗

Your error explained here.
⇗ https://docs.microsoft.com/en-us/windows...code-reference2
⇗ https://docs.microsoft.com/en-us/windows...ted-fatal-error
0x000000CA PNP_DETECTED_FATAL_ERROR
I would try and install Z390 from scratch using my driver instead of moving to this machine from Z270.
But disable onboard ethernet, sound, et cetera in BIOS.
If still getting that error could be the modded ACPI.SYS causing it and needs further patching from creator.

#3698

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3680

> The disk is recognized as a nvme in Win10 only.

⇗ @Andalu ...that's not what I am seeing. In the photos you attached, in disk management, both are showing as NVME (D:) with 465.69 GB NTFS. The Fsutil readouts from W7 and W10 differ in MFT positions. That's strange since the MFT readings should be in the same spot for both. There is a backup MFT in an ntfs system and fsutil is reporting it in different locations for W7 and W10.
Here are the BIOS photos you requested:
⇗ ⇗
⇗
.

#3699

Mattiwatti

> Zitat von ⇗ daniel_k im Beitrag ¶ #3633

> @Mattiwatti
> You seem to have many experience with driver development, can you help us, please?
> Have you ever seem a driver sample which we can modify to suit our needs?
> Basically we need to set two PCI configuration registers in the Intel XHCI controller in order to properly enable USB3 speeds.

Sorry, I missed most of this discussion and it is a bit hard to find all of the details scattered throughout such a big thread...
I'm going to go ahead and say that I probably won't be able to help here, since I'm missing the source code to the drivers (obviously) and USB in general isn't really my area of expertise. It may still be possible to mod an existing driver if the problem is more what you would call a (small, dumb) driver bug than a hardware issue or a major bug in the drivers. Sorry, for the repetition here, but just to clarify...
- The XHCI controller is an onboard one on an Intel PCH? (and if so, which chipset?)
- Which drivers (exact versions) are being used on XP, and which on 7 (presumably these are different ones since Intel has released XHCI drivers for Windows 7, but not XP)?
- Can you give details on which PCI config registers need to be set to which values? (and also, what they are being set to right now?) Are these values being (re)set at every boot (I'm guessing yes, otherwise this would not be such a big problem)? Also not unimportantly, do you have any idea about the meaning of these PCI config registers and their values?
In my experience USB performance problems are almost always purely down to hardware (especially cheap adapters such as USB3 <-> SATA ones for external hard disks) and drivers are only rarely the issue, especially the USB controller drivers themselves. I have never seen actual XHCI controller drivers be the cause of any performance issue (but very occasionally the driver of a device itself, e.g. poorly written USB disk drivers). Though that doesn't mean it is impossible of course, maybe I've just been lucky with the motherboards I've used in the past.

#3700

Mattiwatti

> Zitat von ⇗ gordo999 im Beitrag ¶ #3649

> @Mattiwatti ....I know this is getting off topic but there are posters in this thread who may find it of interest in relation to the content of the thread. Besides, I want to contribute to this thread by tracing into the LAN driver, for example, to see what, if anything, can be done to get it going. As you have claimed, it's likely impossible, if not really hard, due to the number of functions absent in ntoskrnl and ndis.sys. That's what I am trying to find out in this discussion. Is there anything that can be done via modding to make it work?

I'm always hesitant to use words like 'impossible', since this being the internet, saying something is impossible guarantees that some smartarse will spend months of his/her life just to prove you wrong. But... getting an NDIS 6.x driver to work on XP is about as close to impossible as it gets, from what I can see. It's possible that the msrpc.sys dependency can be patched out by NOP-ing all of the function calls going to this driver, which would clear the biggest hurdle that I can see here (namely the absence of ALPC before Vista). The difficulty would then depend on the remaining missing kernel APIs - as you can probably guess, some functions are harder to implement than others. For this driver in particular I'd say you probably have a better chance of success trying to find an older (NDIS 5.x based) driver that works with an ethernet card that is reasonably similar in terms of hardware to the I2XX-V onboard controllers that were introduced later.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3649

> I have not investigated that entirely but with my serial remote debugging sessions the target has to be rebooted for the source to find it. When the target reboots, it is stopped early in the boot process, before the logon screen, and as far as I can see it's possible to trace all the way to the desktop, if desired.

Correct, the target must be booted in debug mode with the debugger ready to 'receive' the serial connection at boot time. (This is no longer true in newer versions of Windows with ethernet debugging where you can attach a debugger after the target has booted, provided that the target booted into debug mode.) You can toggle the 'initial break' with CTRL+ALT+K if you don't want to break into the target immediately on every boot.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3649

> In that case, Microsoft may have built in code to prevent wdbg getting past a sysenter or syscall into kernel code.

This is out of the question. Firstly MS would be shooting themselves in the foot by doing this, since the kernel developers are after all the primary consumers of WinDbg themselves (and no, they do not have a secret version of WinDbg with extra superpowers.) A more boring reason is that sysenter/sycall really do not do anything magical or 'hidden' (though it certainly is true that a debugger might have trouble stepping into them):

    1: kd> rdmsr 0xc0000082 ; 0xc0000082 == MSR_LSTAR, the 64 bit 'syscall' target
    msr[c0000082] = fffff800`008b1980
    1: kd> u fffff800`008b1980
    nt!KiSystemCall64 [C:\<snip>\ntos\ke\amd64\trap.asm @ 1720]:
    fffff800`008b1980 0f01f8          swapgs
    fffff800`008b1983 6548892425a0010000 mov   qword ptr gs:[1A0h],rsp
    fffff800`008b198c 65488b2425a8010000 mov   rsp,qword ptr gs:[1A8h]
    fffff800`008b1995 6a2b            push    2Bh
    fffff800`008b1997 65ff3425a0010000 push    qword ptr gs:[1A0h]
    fffff800`008b199f 4153            push    r11
    fffff800`008b19a1 6a33            push    33h
    fffff800`008b19a3 51              push    rcx

Thus we can see that on this Server 2003 x64 machine, the destination of a 'syscall' instruction will be KiSystemCall64 in ntoskrnl. Admittedly this is not very interesting because it is true for every syscall instruction, and KiSystemCall64 is only a relatively short preamble to transfer execution to the 'real' syscall that was requested, which is dependent on the syscall number (this is true for both x86 and x64, with some minor differences in how these numbers are handled). The information on how these functions can be found by their syscall number is encoded in nt!KeServiceDescriptorTable (there is also nt!KeServiceDescriptorTableShadow for win32k.sys syscalls, which works similarly but is not relevant here.)
I don't want to make this post too long, but the ⇗ second half of this article gives some good info on how to view the SSDT (System Service Descriptor Table) in WinDbg. Note that syscall targets are encoded differently on x86 and x64 - I couldn't immediately find a good source for x86 but it is very similar, just without the bit shifting. This knowledge is fairly useful if you want to, for example, know which kernel mode function the following bit of user mode code (taken from my Windows 7's ntdll.dll) is going to end up calling:

    mov r10, rcx
    mov eax, 16h ; syscall number
    syscall
    retn

All 400+ syscalls (a bit less than that in XP) follow this pattern, with only the syscall number varying. Of course, since MS makes debug symbols publicly available which you should be using, I already saw that this is ntdll!NtQueryInformationProcess, which (to no one's surprise) goes to nt!NtQueryInformationProcess. But this can sometimes still be useful to know, e.g. if debug symbols are missing for some file version or if you are dealing with an obfuscated program that performs its own syscalls.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3649

> > Zitat von ⇗ Mattiwatti im Beitrag ¶ #3646

> > ...what are you trying to achieve when stepping into a 'sysenter'?

> There are times when the system is called from a user mode app and the system calls back into user mode, sometimes multiple times, before returning after the sysenter. If you don't enter system code at sysenter you miss the call back and there could be code in the call back in u-mode you need to see. I have encountered that many times with SI, tracing into system code then suddenly being back in user code in the app I am debugging, yet well before the system code returns you to the original call for the u-mode app at sysenter.

There are only a handful of user mode functions that are called in this way, most of which are related to exception dispatching and not usually interesting on the user mode side. The one black sheep in the NT family is win32k.sys, which makes extensive use of user mode callbacks. For both cases it is perfectly possible (and easier) to attach a user mode debugger to the target to debug user mode portions of a call stack. In practice it is in my experience seldom useful to step through user mode callbacks however.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3649

> This action would also make it very difficult to follow a cold code read in IDA. In IDA, a function often begins with no reference to where it was called from. It's likely being called from system code via a call to system code elsewhere. You'd need a debugger to confirm that.

Sure. It's always best to use a combination of static and dynamic analysis and use whichever one best suits the problem.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3649

> > Zitat von ⇗ Mattiwatti im Beitrag ¶ #3646

> > Instead, set a breakpoint on the syscall you wish to debug (e.g. `'bp nt!NtCreateFile'`

> That's fine if you know the call you want to trap with a bp. It's kind of shotgun approach at times since you are guessing that the app might call via that function. What if it doesn't, and there is code during a system call that is called by the system before exiting the syscall? I agree that setting a BP is more elegant but sometimes you just have to trace to see where the code goes. I also agree with what you say below, that the system code itself is not of much interest. However, it's what the system code does with the calling parameters that can be of interest. Besides, if you want to learn how the system processes calls from U-mode, or just how a driver works, it's helpful to see the system in action. It's one thing to read about a PDO in theory, or see a it in table form in Windbg, and quite another to see the actually code and data related to a PDO. Some people are happy to set BPs and ignore the intervening code but I find the implementation of assembly language to be fascinating, especially as related to functions in a higher level language like C++.

See above re: analyzing syscalls. What you will end up doing by 'stepping into a syscall' is stepping through KiSystemCall[32|64]. This is hyper-generic and utterly boring (not really if you are into OS internals - but for most practical purposes) boilerplate code that has barely changed since Windows NT 4, and has no relation to the user mode function you were stepping through a moment before. If you are stepping through a user mode program that is calling NtCreateFile in ntdll, trust me that you really want to step through NtCreateFile in the kernel (if you do want to step through it), not any function(s) leading to it.

#3701

Andalu

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #3698

> ...that's not what I am seeing. In the photos you attached, in disk management, both are showing as NVME (D:) with 465.69 GB NTFS.

I meant that the nvme is recognized immediately as a disk in win10 with the built in driver while in XP and Win7 it is recognized as a "PCI Device" until the drivers (ofa or samsung) are installed.
Thanks for the screenshots ;)

#3702

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #3701

> I meant that the nvme is recognized immediately as a disk in win10 with the built in driver while in XP and Win7 it is recognized as a "PCI Device"...

⇗ @Andalu ...I gather from your device being described as a portable SSD that it is a plugin device for the PCIe bus. When a device like your is connected hot, if that is the case, the driver which is first in line interrogates the device and gets pertinent information from the device. If the device is plugged into the PCIe bus it will identify itself as a PCI device.
If a SATA drive, on the other hand, is plugged into a SATA port, it would identify itself as a SATA device. It's all written in the device fixed memory. If an NV device is connected to the motherboard permanently, it would likely describe itself as a an NVMI device. Because NVMI was not introduced to Windows till W8, W7 in a raw state would know nothing about it, nor would XP. Apparently, Microsoft released a driver for W7 in an update. You'd have to track down which update. There's a hotfix from Microsoft about that: KB2990941.

#3703

antome

> Zitat von ⇗ XPLives im Beitrag ¶ #3697

> @antome

> > Zitat von ⇗ antome im Beitrag ¶ #3696

> > > Zitat von ⇗ XPLives im Beitrag ¶ #3685

> > > @antome

> > > > Zitat von ⇗ antome im Beitrag ¶ #3682

> > > > boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> > > > edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> > > > ⇗

> This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
> ⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
> XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
> Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
> Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
> Reboot on Z270 and make sure it works and boot correctly back into XP.
> If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

Thanks for the driver now something has changed, xp x64 in normal mode I get error 0x000000CA while in safe mode it starts correctly on the z390, how do I solve this problem? the same disk starts correctly on the z270
⇗ ⇗ ⇗

Your error explained here.
⇗ https://docs.microsoft.com/en-us/windows...code-reference2
⇗ https://docs.microsoft.com/en-us/windows...ted-fatal-error
0x000000CA PNP_DETECTED_FATAL_ERROR
I would try and install Z390 from scratch using my driver instead of moving to this machine from Z270.
But disable onboard ethernet, sound, et cetera in BIOS.
If still getting that error could be the modded ACPI.SYS causing it and needs further patching from creator.

Thanks for your patience :), I tried with a DVD installation of xp x64, first of all I replaced acpi.sy_ in the Amd64 folder and recreated the driver.cab file with acpi.sys always modified in the amd64 folder, then I created iso with nlite with the ahci drivers for the z390 have I done something wrong? because I get the same error 0x000000CA during the initialization of the hardware. I disabled everything possible from bios, audio lan, all usb port.
⇗ ⇗

#3704

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3703

> > Zitat von ⇗ XPLives im Beitrag ¶ #3697

> > ⇗ @antome

> > > Zitat von ⇗ antome im Beitrag ¶ #3696

> > > > Zitat von ⇗ XPLives im Beitrag ¶ #3685

> > > > ⇗ @antome

> > > > > Zitat von ⇗ antome im Beitrag ¶ #3682

> > > > > boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> > > > > edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> > > > > ⇗

This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
Reboot on Z270 and make sure it works and boot correctly back into XP.
If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

Thanks for the driver now something has changed, xp x64 in normal mode I get error 0x000000CA while in safe mode it starts correctly on the z390, how do I solve this problem? the same disk starts correctly on the z270
⇗ ⇗ ⇗

Your error explained here.
⇗ https://docs.microsoft.com/en-us/windows...code-reference2
⇗ https://docs.microsoft.com/en-us/windows...ted-fatal-error
0x000000CA PNP_DETECTED_FATAL_ERROR
I would try and install Z390 from scratch using my driver instead of moving to this machine from Z270.
But disable onboard ethernet, sound, et cetera in BIOS.
If still getting that error could be the modded ACPI.SYS causing it and needs further patching from creator.

Thanks for your patience :), I tried with a DVD installation of xp x64, first of all I replaced acpi.sy_ in the Amd64 folder and recreated the driver.cab file with acpi.sys always modified in the amd64 folder, then I created iso with nlite with the ahci drivers for the z390 have I done something wrong? because I get the same error 0x000000CA during the initialization of the hardware. I disabled everything possible from bios, audio lan, all usb port.
⇗ ⇗

Have you tried XP 32-Bit install with modded ACPI.SYS and Fernando SATA driver? Does it get the same error on Z390?
Hard to isolate if this is ACPI related since there is no MPS Mode for X64. But PNP is Plug and Play so that is why we need similar test on XP 32-Bit to compare.
Also make sure the XP 32-Bit you do a clean ISO before integrating the Fernando SATA driver. If you already mixed it with STORAHCI then we cannot use that image. It's possible what Gordo999 said could be installing two different storage drivers using the same hardware ID as the cause. I don't know if that is what happened so that's why you will have to use a clean XP 32-Bit for this test and just integrated Fernando SATA driver only. Copy the modded ACPI.SYS manually when you get BSOD A5 error for testing rather than integrating into driver.cab.

#3705

gordo999

> Zitat von ⇗ antome im Beitrag ¶ #3703

> ... I get the same error 0x000000CA during the initialization of the hardware

⇗ @antome ...the 0xCA error seems to be related to duplicate device IDs. In other words, during hardware enumeration, the plug and play manager is seeing the same Device ID used twice. Not sure how to deal with that right now since I am a bit under the weather and not thinking clearly. Maybe ⇗ @XPLives can figure something out.
If your system was booting I'd try to fix it by loading the HKLM\System hive in regedit in another system and checking for identical device IDs in HKLM\Susyem\ControlSetxxx\Enum. It sounds like your system is not booting at all so there is something wrong in your installation disk. In that case, I'd remove recent additions one by one to see which one is causing two drivers to be loaded with the same Device ID. Might be easier to remove all recent additions and add them one by one. If you remove them all, see if you can get back to the 0XA5 (acpi) error or the 0x7B (ahci) error.

## Page 248

#3706

antome

> Zitat von ⇗ XPLives im Beitrag ¶ #3704

> @antome

> > Zitat von ⇗ antome im Beitrag ¶ #3703

> > > Zitat von ⇗ XPLives im Beitrag ¶ #3697

> > > @antome

> > > > Zitat von ⇗ antome im Beitrag ¶ #3696

> > > > > Zitat von ⇗ XPLives im Beitrag ¶ #3685

> > > > > @antome

> > > > > > Zitat von ⇗ antome im Beitrag ¶ #3682

> > > > > > boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> > > > > > edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> > > > > > ⇗

> This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
> ⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
> XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
> Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
> Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
> Reboot on Z270 and make sure it works and boot correctly back into XP.
> If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

Thanks for the driver now something has changed, xp x64 in normal mode I get error 0x000000CA while in safe mode it starts correctly on the z390, how do I solve this problem? the same disk starts correctly on the z270
⇗ ⇗ ⇗

Your error explained here.
⇗ https://docs.microsoft.com/en-us/windows...code-reference2
⇗ https://docs.microsoft.com/en-us/windows...ted-fatal-error
0x000000CA PNP_DETECTED_FATAL_ERROR
I would try and install Z390 from scratch using my driver instead of moving to this machine from Z270.
But disable onboard ethernet, sound, et cetera in BIOS.
If still getting that error could be the modded ACPI.SYS causing it and needs further patching from creator.

Thanks for your patience :), I tried with a DVD installation of xp x64, first of all I replaced acpi.sy_ in the Amd64 folder and recreated the driver.cab file with acpi.sys always modified in the amd64 folder, then I created iso with nlite with the ahci drivers for the z390 have I done something wrong? because I get the same error 0x000000CA during the initialization of the hardware. I disabled everything possible from bios, audio lan, all usb port.
⇗ ⇗

Have you tried XP 32-Bit install with modded ACPI.SYS and Fernando SATA driver? Does it get the same error on Z390?
Hard to isolate if this is ACPI related since there is no MPS Mode for X64. But PNP is Plug and Play so that is why we need similar test on XP 32-Bit to compare.
Also make sure the XP 32-Bit you do a clean ISO before integrating the Fernando SATA driver. If you already mixed it with STORAHCI then we cannot use that image. It's possible what Gordo999 said could be installing two different storage drivers using the same hardware ID as the cause. I don't know if that is what happened so that's why you will have to use a clean XP 32-Bit for this test and just integrated Fernando SATA driver only. Copy the modded ACPI.SYS manually when you get BSOD A5 error for testing rather than integrating into driver.cab.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3705

> > Zitat von ⇗ antome im Beitrag ¶ #3703

> > ... I get the same error 0x000000CA during the initialization of the hardware

> @antome ...the 0xCA error seems to be related to duplicate device IDs. In other words, during hardware enumeration, the plug and play manager is seeing the same Device ID used twice. Not sure how to deal with that right now since I am a bit under the weather and not thinking clearly. Maybe @XPLives can figure something out.
> If your system was booting I'd try to fix it by loading the HKLM\System hive in regedit in another system and checking for identical device IDs in HKLM\Susyem\ControlSetxxx\Enum. It sounds like your system is not booting at all so there is something wrong in your installation disk. In that case, I'd remove recent additions one by one to see which one is causing two drivers to be loaded with the same Device ID. Might be easier to remove all recent additions and add them one by one. If you remove them all, see if you can get back to the 0XA5 (acpi) error or the 0x7B (ahci) error.

I only integrated the ahci a352 by fernando single driver. I remember that to get the installation to xp x32 as well as replacing acpi.sy_ (acpi.sys) I had also replaced the syssetup.sy_ file in the i386 folder of the installation disk, these 2 files were also necessary to update a working image on z270 and make it compatible for z390 without any errors. You probably need a syssetup.dll file x64 modified for the z390.
This was the procedure performed on xp x32
So to get windows to work we care about the following files:
acpi.sys (exists in SP3.CAB and Driver.cab both under I386 folder of installation)
acpi.sy_ (exists under I386 folder of installation) - acpi_sy is the result of makecab.exe command of the acpi.sys
syssetup.sy_ (exists under I386 folder of installation) - again result of the syssetup.sys
ahci drivers which we import by nLite
How I did it is -> get .iso file, decompress -> replace the above files -> nlite to import ahci driver -> make bootable .iso.
Attached you can find all the files that are needed and work with Z390 without modding the bios
antome has attached files to this post

- ⇗ Z390 Files.zip
- ⇗ AHCI Update _1_.zip

#3707

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3706

> > Zitat von ⇗ XPLives im Beitrag ¶ #3704

> > ⇗ @antome

> > > Zitat von ⇗ antome im Beitrag ¶ #3703

> > > > Zitat von ⇗ XPLives im Beitrag ¶ #3697

> > > > ⇗ @antome

> > > > > Zitat von ⇗ antome im Beitrag ¶ #3696

> > > > > > Zitat von ⇗ XPLives im Beitrag ¶ #3685

> > > > > > ⇗ @antome

> > > > > > > Zitat von ⇗ antome im Beitrag ¶ #3682

> > > > > > > boys xp x32 works properly on gene xi z390. Now I'm trying with xp x64 but the structure of the installation disk is completely different. Which is the correct procedure to integrate the files on the xp x64 installation disk? Where to put acpi.sys? Thanks
> > > > > > > edit: I tried windows xp x64 running on apex ix z270, I started xp on z270 replaced acpi.sys x64 in the windows / system32 folder, copied the 2 sys files of the ahci driver into the driver folder and executed the reg file to integrate the drivers in the registry, mounted disk on the z390 crashes due to a sata driver problem
> > > > > > > ⇗

This is expected. Reattach the SATA drive back to your Z270 system. Go download my driver here.
⇗ Windows XP Pro 64-Bit and Server 2003 64-Bit on Modern Hardware
XP Pro 64-Bit and Server 2003 64-Bit - Universal Intel SATA Controller Driver - XPLIVES64.ZIP
Then go to Device Manager while in XP on Z270. Update driver of the Intel SATA controller using mine.
Then in Device Manager take a snapshot and upload it to confirm it installed correctly.
Reboot on Z270 and make sure it works and boot correctly back into XP.
If this works then you can shutdown and reconnect the SATA drive to the Z390 and it should boot up properly without the BSOD 7B error.

Thanks for the driver now something has changed, xp x64 in normal mode I get error 0x000000CA while in safe mode it starts correctly on the z390, how do I solve this problem? the same disk starts correctly on the z270
⇗ ⇗ ⇗

Your error explained here.
⇗ https://docs.microsoft.com/en-us/windows...code-reference2
⇗ https://docs.microsoft.com/en-us/windows...ted-fatal-error
0x000000CA PNP_DETECTED_FATAL_ERROR
I would try and install Z390 from scratch using my driver instead of moving to this machine from Z270.
But disable onboard ethernet, sound, et cetera in BIOS.
If still getting that error could be the modded ACPI.SYS causing it and needs further patching from creator.

Thanks for your patience :), I tried with a DVD installation of xp x64, first of all I replaced acpi.sy_ in the Amd64 folder and recreated the driver.cab file with acpi.sys always modified in the amd64 folder, then I created iso with nlite with the ahci drivers for the z390 have I done something wrong? because I get the same error 0x000000CA during the initialization of the hardware. I disabled everything possible from bios, audio lan, all usb port.
⇗ ⇗

Have you tried XP 32-Bit install with modded ACPI.SYS and Fernando SATA driver? Does it get the same error on Z390?
Hard to isolate if this is ACPI related since there is no MPS Mode for X64. But PNP is Plug and Play so that is why we need similar test on XP 32-Bit to compare.
Also make sure the XP 32-Bit you do a clean ISO before integrating the Fernando SATA driver. If you already mixed it with STORAHCI then we cannot use that image. It's possible what Gordo999 said could be installing two different storage drivers using the same hardware ID as the cause. I don't know if that is what happened so that's why you will have to use a clean XP 32-Bit for this test and just integrated Fernando SATA driver only. Copy the modded ACPI.SYS manually when you get BSOD A5 error for testing rather than integrating into driver.cab.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3705

> > Zitat von ⇗ antome im Beitrag ¶ #3703

> > ... I get the same error 0x000000CA during the initialization of the hardware

> ⇗ @antome ...the 0xCA error seems to be related to duplicate device IDs. In other words, during hardware enumeration, the plug and play manager is seeing the same Device ID used twice. Not sure how to deal with that right now since I am a bit under the weather and not thinking clearly. Maybe @XPLives can figure something out.
> If your system was booting I'd try to fix it by loading the HKLM\System hive in regedit in another system and checking for identical device IDs in HKLM\Susyem\ControlSetxxx\Enum. It sounds like your system is not booting at all so there is something wrong in your installation disk. In that case, I'd remove recent additions one by one to see which one is causing two drivers to be loaded with the same Device ID. Might be easier to remove all recent additions and add them one by one. If you remove them all, see if you can get back to the 0XA5 (acpi) error or the 0x7B (ahci) error.

I only integrated the ahci a352 by fernando single driver. I remember that to get the installation to xp x32 as well as replacing acpi.sy_ (acpi.sys) I had also replaced the syssetup.sy_ file in the i386 folder of the installation disk, these 2 files were also necessary to update a working image on z270 and make it compatible for z390 without any errors. You probably need a syssetup.dll file x64 modified for the z390.
This was the procedure performed on xp x32
So to get windows to work we care about the following files:
acpi.sys (exists in SP3.CAB and Driver.cab both under I386 folder of installation)
acpi.sy_ (exists under I386 folder of installation) - acpi_sy is the result of makecab.exe command of the acpi.sys
syssetup.sy_ (exists under I386 folder of installation) - again result of the syssetup.sys
ahci drivers which we import by nLite
How I did it is -> get .iso file, decompress -> replace the above files -> nlite to import ahci driver -> make bootable .iso.
Attached you can find all the files that are needed and work with Z390 without modding the bios
⇗ z390 files xp x32
⇗ Ahci update

Those attachments will not work due to needing a hwbot account. You should refer to the actual page it was attached and not the download link.
But first did your clean XP-32 Bit with just Fernando SATA driver and modded ACPI.SYS work on your Z390 clean install without any BSOD issue 0x000000CA?
If no 0x000000CA Error then do a clean install of XP Pro 64-Bit with 64 Bit versions of (Fernando SATA driver and modded ACPI.SYS) on your Z390 again. Don't add any other drivers or storage drivers. You don't need the SYSSETUP.

#3708

antome

> Zitat von ⇗ XPLives im Beitrag ¶ #3707

> @antome
> Those attachments will not work due to needing a hwbot account. You should refer to the actual page it was attached and not the download link.
> But first did your clean XP-32 Bit with just Fernando SATA driver and modded ACPI.SYS work on your Z390 clean install without any BSOD issue 0x000000CA?
> If no 0x000000CA Error then do a clean install of XP Pro 64-Bit with 64 Bit versions of (Fernando SATA driver and modded ACPI.SYS) on your Z390 again. Don't add any other drivers or storage drivers. You don't need the SYSSETUP.

⇗ @XPLives I apologize I have corrected the links of the files used for xp x32 on the z390. Regarding the x64 disk I only integrated the driver sata a352 by Fernando, no other driver

#3709

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3708

> > Zitat von ⇗ XPLives im Beitrag ¶ #3707

> > ⇗ @antome
> > Those attachments will not work due to needing a hwbot account. You should refer to the actual page it was attached and not the download link.
> > But first did your clean XP-32 Bit with just Fernando SATA driver and modded ACPI.SYS work on your Z390 clean install without any BSOD issue 0x000000CA?
> > If no 0x000000CA Error then do a clean install of XP Pro 64-Bit with 64 Bit versions of (Fernando SATA driver and modded ACPI.SYS) on your Z390 again. Don't add any other drivers or storage drivers. You don't need the SYSSETUP.

> @XPLives I apologize I have corrected the links of the files used for xp x32 on the z390. Regarding the x64 disk I only integrated the driver sata a352 by Fernando, no other driver

So clean XP Pro 64-Bit ISO and 64-Bit (Fernando SATA driver and Modded ACPI.sys) resulted in BSOD issue 0x000000CA?
Can you retest Z390 with clean XP Pro 32-Bit ISO and 32-Bit (Fernando SATA driver and Modded ACPI.sys) to see if any BSOD issue and report back?

#3710

antome

> Zitat von ⇗ XPLives im Beitrag ¶ #3709

> @antome

> > Zitat von ⇗ antome im Beitrag ¶ #3708

> > > Zitat von ⇗ XPLives im Beitrag ¶ #3707

> > > @antome
> > > Those attachments will not work due to needing a hwbot account. You should refer to the actual page it was attached and not the download link.
> > > But first did your clean XP-32 Bit with just Fernando SATA driver and modded ACPI.SYS work on your Z390 clean install without any BSOD issue 0x000000CA?
> > > If no 0x000000CA Error then do a clean install of XP Pro 64-Bit with 64 Bit versions of (Fernando SATA driver and modded ACPI.SYS) on your Z390 again. Don't add any other drivers or storage drivers. You don't need the SYSSETUP.

> > @XPLives I apologize I have corrected the links of the files used for xp x32 on the z390. Regarding the x64 disk I only integrated the driver sata a352 by Fernando, no other driver

> So clean XP Pro 64-Bit ISO and 64-Bit (Fernando SATA driver and Modded ACPI.sys) resulted in BSOD issue 0x000000CA?
> Can you retest Z390 with clean XP Pro 32-Bit ISO and 32-Bit (Fernando SATA driver and Modded ACPI.sys) to see if any BSOD issue and report back?

yes, clean xp x64+ acpi.sys x64+ ahci a352 by Fernando= 0x000000CA.
i will try xp x32 installation with only acpi.sys and driver sata to understand returns the same error without using sysetup.dll modified

#3711 | XPWELL64 | Windows XP Intel HD Gpu Test drivers coming soon.

#3712

XPLives

⇗ @antome

> Zitat von ⇗ antome im Beitrag ¶ #3710

> > Zitat von ⇗ XPLives im Beitrag ¶ #3709

> > ⇗ @antome

> > > Zitat von ⇗ antome im Beitrag ¶ #3708

> > > > Zitat von ⇗ XPLives im Beitrag ¶ #3707

> > > > ⇗ @antome
> > > > Those attachments will not work due to needing a hwbot account. You should refer to the actual page it was attached and not the download link.
> > > > But first did your clean XP-32 Bit with just Fernando SATA driver and modded ACPI.SYS work on your Z390 clean install without any BSOD issue 0x000000CA?
> > > > If no 0x000000CA Error then do a clean install of XP Pro 64-Bit with 64 Bit versions of (Fernando SATA driver and modded ACPI.SYS) on your Z390 again. Don't add any other drivers or storage drivers. You don't need the SYSSETUP.

> > > @XPLives I apologize I have corrected the links of the files used for xp x32 on the z390. Regarding the x64 disk I only integrated the driver sata a352 by Fernando, no other driver

So clean XP Pro 64-Bit ISO and 64-Bit (Fernando SATA driver and Modded ACPI.sys) resulted in BSOD issue 0x000000CA?
Can you retest Z390 with clean XP Pro 32-Bit ISO and 32-Bit (Fernando SATA driver and Modded ACPI.sys) to see if any BSOD issue and report back?

yes, clean xp x64+ acpi.sys x64+ ahci a352 by Fernando= 0x000000CA.
i will try xp x32 installation with only acpi.sys and driver sata to understand returns the same error without using sysetup.dll modified

I examined the two files you uploaded
For Z390 Files, I would suggest use the newer version 11.2 for classic SATA AHCI driver from Fernando instead of v8.9.8.1005.
Do not use the file AHCI Update_1_.zip. That contains StorAHCI and if you are combining both possibly causing drivers fighting to install to the same storage device and maybe BSOD CA.

#3713

antome

> Zitat von ⇗ XPLives im Beitrag ¶ #3712

> @antome

> > Zitat von ⇗ antome im Beitrag ¶ #3710

> > > Zitat von ⇗ XPLives im Beitrag ¶ #3709

> > > @antome

> > > > Zitat von ⇗ antome im Beitrag ¶ #3708

> > > > > Zitat von ⇗ XPLives im Beitrag ¶ #3707

> > > > > @antome
> > > > > Those attachments will not work due to needing a hwbot account. You should refer to the actual page it was attached and not the download link.
> > > > > But first did your clean XP-32 Bit with just Fernando SATA driver and modded ACPI.SYS work on your Z390 clean install without any BSOD issue 0x000000CA?
> > > > > If no 0x000000CA Error then do a clean install of XP Pro 64-Bit with 64 Bit versions of (Fernando SATA driver and modded ACPI.SYS) on your Z390 again. Don't add any other drivers or storage drivers. You don't need the SYSSETUP.

> > > > @XPLives I apologize I have corrected the links of the files used for xp x32 on the z390. Regarding the x64 disk I only integrated the driver sata a352 by Fernando, no other driver

> So clean XP Pro 64-Bit ISO and 64-Bit (Fernando SATA driver and Modded ACPI.sys) resulted in BSOD issue 0x000000CA?
> Can you retest Z390 with clean XP Pro 32-Bit ISO and 32-Bit (Fernando SATA driver and Modded ACPI.sys) to see if any BSOD issue and report back?

yes, clean xp x64+ acpi.sys x64+ ahci a352 by Fernando= 0x000000CA.
i will try xp x32 installation with only acpi.sys and driver sata to understand returns the same error without using sysetup.dll modified

I examined the two files you uploaded
For Z390 Files, I would suggest use the newer version 11.2 for classic SATA AHCI driver from Fernando instead of v8.9.8.1005.
Do not use the file AHCI Update_1_.zip. That contains StorAHCI and if you are combining both possibly causing drivers fighting to install to the same storage device and maybe BSOD CA.

I did the test with xp x32 and actually to have an xp x32 running on xi gene z390 just replace acpi.sy_ and recreate driver.cab and sp3.cab with acpi.sys modified and insert with nlite driver a352 by Fernando.
Now I try on x64 with the driver you recommended
Edit: unfortunately it continues to give error 0x000000CA always in the same point of the installation, I have used the same bios settings both for xp x32 and x64 one works the other not

#3714

gordo999

> Zitat von ⇗ antome im Beitrag ¶ #3710

> ...i will try xp x32 installation with only acpi.sys and driver sata to understand returns the same error without using sysetup.dll modified

@atome ...I am speaking from ignorance, I have never applied drivers to an existing install disk. Don't you have to remove the existing drivers, or reference to them, before adding new drivers? If there's a reference in the installation manifest to both drivers, the installer may try to install both sets, hence an 0xCA error if the drivers have the same Device IDs.
You added an edit claiming the same 0xCA error with 32 bit. The installer is reading INF files to guide it and it seems there is a duplicate entry in an INF file. Either that, or your XP installation already has a reference to the same Device ID the installer is trying to install.

#3715

genieautravail

⇗ @IntiMD

> Zitat von ⇗ IntiMD im Beitrag ¶ #3592

> BTW if you feel lucky, you can give Snappy Driver Installer Origin a try, so as to try finding the missing drivers for the devices. Assuming that you have working internet connection in the XP machine, go to ⇗ https://www.snappy-driver-installer.org/download/ and download the "Application only" package. Unpack the zipped archive and open the main exe. Choose to download only indexes. After it finishes downloading the indexes it should show you the list of devices that need a driver or need to be updated (depending on the filters set ofc, assuming the filters are default ones). Don't do anything in it (especially DO NOT install the drivers from the app level, even though SDIO is much legit compared to other driver boosters, you need to be cautious. If you're interested, you can hover over a device for info related to the device and drivers offered by the app, including the location of them in the driverpacks that the app offers to download), just close the app. Find the latest snapshot file ending with the .SNP file extension, and upload it to a hosting of your choice (preferably zippyshare or uploadfiles). I'll then check and research the snapshot, hoping the app will find drivers for those unknown devices.

Hello,
I have just uploaded the file you have asked:
⇗ https://www18.zippyshare.com/v/CYpZxmVj/file.html
For convenience, I have posted the same message on the MSFN forum.
EDIT by Fernando: Unneeded blank lines removed (to save space)

#3716

IntiMD

⇗ @genieautravail First of all, there was no need to install the 'High Precision Event Timer' and 'AMD Processor' drivers, which are old and not destined for your hardware. It would be much better to revert their states to before installation.
I couldn't find the appropriate XP-compatible drivers for the AMD PSP device. The drivers that SDIO offers is 4.9.0.0 destined for Win10 x86, which is offered only because in the inf file (exactly in the manufacturer models section), they used 'NTx86' instead of, say 'NTx86.10.0', and i strongly doubt the key driver files are compatible with XP. IMO, would be best to leave it be in its state (which is: no drivers installed)
Neither couldn't find the appropriate driver for the AMD GPU.
Anyway, what SDIO offers according to the snapshot is updated drivers for:
* Realtek High Definition Audio (in my opinion no need to update if audio works perfectly fine)
* Logitech Unifying USB receiver (i assume it's something related to the wireless logitech mouses depending on the receiver. I absolutely don't see any reason to install these drivers.)
* Realtek PCIe GBE Family Controller (wouldn't actually hurt to get this updated if you want, since the drivers that SDIO offers are miles newer than the ones you currently uses (5.836.125.2018 2018-01-25 vs. 5.824.107.2014 2014-01-07) if you want then i can share you these drivers to install. best to do is to uninstall the realtek ethernet drivers first through devmgmt (assuming you installed them manually) and updating the device drivers by directing to the folder containing those newer driver files))

#3717 | genieautravail | ⇗ @IntiMD Thank you for your efforts. I already have the lastest version of the Realtek driver. I don't need to update this driver because Realtek only added support for new OS like Windows 10.
#3718 | gordo999 | Hello....anybody there? Awfully quiet out there. :-)

#3719

schreiberstein

⇗ @gordo999
Yes, it is sad...
I will continue some of my experiments in a few days. I am preparing an XP x64 install media for my system to check stability there to confirm whether some of side effects I experience are due to XP x86 memory management or the software itself. I think I will also E-Mail Gigabyte about the memory mapping issues on x86 (e.g. low available ram < 4GB), since I think this issue will affect Windows 10 x86 as well (have not confirmed this yet) and I can just pull the "muh mission critical legacy industrial applications" card.
And I really hope we will be blessed with a new USB3 XHCI driver. It would be amazing.
I recently got an "Exsys EX-1010" external PCI-Express to PCI 32 enclosure (~150) (4 slots! - connected via a DVI-cable) which allowed me to permanently integrate the Creative Audigy 2 ZS soundcard into my system, albeit externally. Sound is broken on XP x86 for some reason (sound is nothing but noise), but I can play back via ASIO in XMPlay with no issues for some reason... Works flawlessly in Windows 10 and Mac OS X. I think it is because of the 4GB PAE memory patch - not the latest version from daniel_k though since I accidentally lost my old unmodified files and need to retrieve them from another machine first (no big deal) before I can test his latest patch.
I think it will be somehow necessary to "burn" the first few GBs of RAM since there appears to be something else there. I even have application stability issues on Server 2003, sadly.
But I don't know much of the details of this platform.
Cheers,
schreiberstein

#3720

gordo999

⇗ @schreiberstein ...I can't talk, I have been forced to check out a registry key that is mainly hidden in case it's a rootkit. Part of the reason it's hidden is that it's full of Chinese characters which regedit cannot read. I got a bit suspicious, however, when gmer, the rootkit finder, crashed while I was trying to export the hidden registry key. It was not hidden to gmer and in fact the key was marked in red, indicating suspicious activity.
Not trying to lay a guilt trip on anyone, the thread went from rather hectic daily activity to nothing. Hope everyone is OK. Getting near Christmas in the western world so I imagine posters are getting into the Christmas spirit and doing other things.

## Page 249

#3721

diderius6

Hi,
I rebuild a Lenovo Thinkpad x220 with i7 2640M, 8 GB ram and the good IPS screen from scratch. It has USB3 from Nec.
⇗ @Gelip told, that XP64 runs there in UEFI mode.
It lasts nearly whole day with setup, new thermal paste and crazy screws. Now I use a Samsung 860 EVO 500 GB SSD, which shows 500 MByte/s for read and write under XP. The problem with TRIM under XP I do not solve. May be someone here in the forum succeeds with this. At the moment I use Win10 for this. I do not found an Intel Optane in SSD size. Optane does not need TRIM.
The Bios chip is Winbond 25Q64CVSIG, where I put Bios 1.39 from summer 2013 with Revelprog IS on it. I also think about to put a new Bios chip on socket there.
Nice, benchmark for 3DMark 2001 with integrated grafik HD3000 is 22400 under XP SP3
and 14000 under Win 10
Dietmar
⇗

#3722

Fernando

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3721

> The problem with TRIM under XP I do not solve. May be someone here in the forum succeeds with this.

Have you already tried the tool named "Anvil's Storage Utilities" (look ⇗ >here<)? It is able to trigger TRIM to all SSDs.

#3723

diderius6

⇗ @Fernando
Thanks, I just test the tool.
Now I get message,
that all drives do not respond to the "TRIM" command
Dietmar
⇗

#3724 | Fernando | ⇗ @diderius6: The error message is misleading, because the SSD supports TRIM and the onboard Intel SATA AHCI Controller lets the TRIM command pass through. Thanks for the nice picture, but I cannot read the error text. Please do the following while getting such popup message: Press ALT+PRINT, run Windows Paint, click onto "Insert" + "Crop" and save the image as *.png file.

#3725

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #3721

> @Gelip told, that XP64 runs there in UEFI mode.

I have already written about it but I will sum up again.
Yes, WinXP SP2 x64 boot in UEFI but with CSM with AnaPa VGA driver on X220. There are all WinXP drivers for this laptop. In the bios there is only legacy VGA option ROM, no VGA GOP firmware, no option to disable CSM.
Now I'm testing other hardware with WinXP SP2 x64 and UEFI: ASUS P8H61-M LE R2. This motherboard allows you to boot the OS:

- pure Legacy (CSM)
- UEFI with CSM e.g. with legacy VGA ROM
- pure UEFI with GOP VGA ROM

The latest bios has GOP firmware for iGPU:
⇗
The board also has PCIe and even old PCI slot so you can test various graphics cards. WinXP SP2 x64 with AnaPa driver and PCIe GeForce 6200 card also works on this ASUS hardware in UEFI + CSM
There are all WinXP drivers for this mobo. ASUS also has a COM port for debugging with WinDbg.

#3726

Gelip

⇗ @diderius6
Try other software for SSD - maybe Samsung_Magician_Setup_v497.exe or ADATA_SSDToolBoxSetup.exe
Also try this registry settings for SSD: Windows-XP-SSD.zip
⇗ ADATA_SSDToolBoxSetup.exe
⇗ Samsung_Magician_Setup_v497.zip
Gelip has attached files to this post

- ⇗ Windows-XP-SSD.zip

#3727 | diderius6 | ⇗ @Gelip Can you run 3Dmark2001 on the ASUS P8H61-M LE R2 board under UEFI Dietmar

#3728

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3727

> Can you run 3Dmark2001 on the ASUS P8H61-M LE R2 board under UEFI

I would have to reinstall WinXP with the AnaPa driver because I have something else on the disk right now.

#3729

diderius6

⇗ @Gelip
Only the ADATA_SSDToolBoxSetup.exe
works for TRIM under XP SP3 for the Samsung 860 EVO 500 Gbyte.
Crazy, the Samsung tool tells, only for Samsung devices^^
Dietmar
PS: The health of my SSD went from 10% to 100% after about 90 seconds of TRIM via ADATA SSD ToolBox,
so thanks a lot! The speed of the SSD raises to 565 MByte/s.

#3730 | Gelip | ⇗ @diderius6 3DMark2001 cannot be installed when the system is running on the AnaPa driver because it doesn't support 3D: ⇗

#3731

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #3721

> The Bios chip is Winbond 25Q64CVSIG, where I put Bios 1.39 from summer 2013...

The latest bios for the X220 is: ⇗ 1.46 released 27 Jun 2018

#3732 | diderius6 | ⇗ @Gelip, yes I know this. But from the Bios 1.39 you can change to any other Bios version. Also you can take any akkumulator, that you wish. Those possibilities are gone from Bios >= 1.42 for the Thinkpad x220 Dietmar

#3733

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #3732

> yes I know this. But from the Bios 1.39 you can change to any other Bios version.
> Also you can take any akkumulator, that you wish.
> Those possibilities are gone from Bios >= 1.40 for the Thinkpad x220
> Dietmar

Akkumulator - I don't understand? Do you mean battery?

#3734 | Gelip | Today I tested ASUS P8H61-M LE R2 with WinXP SP2 x64 under UEFI + CSM + iGPU SandyBridge + AnaPa and it works. So, on this motherboard WinXP 64-bit works in UEFI with both iGPU and PCIe graphics card.

#3735

Andalu

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #3673

> @Andalu
> Don't know what the issue is.
> I did many tests here before releasing the patcher.
> - VirtualBox 8GB RAM
> - Core i3-2310M "Sandy Bridge" Lenovo G470 8GB w/ Insyde BIOS
> - i7-8700K / Z370 Gaming 3 / 16GB
> Tested all patched HALs, with no issues on any of the systems.
> Even tried on an old T6600 eMachines D525 with 4GB just to test patch stability.
> Are you really sure you're not missing something?
> What about trying storahci.sys or iastora.sys?
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (218)
> iaStor is old and has issues on newer systems, maybe things get worse with PAE enabled.

I installed XP v5.1.2600 on my former crazy asrock B75-Pro3M as 'acpi multiprocessor pc' with the only Intel RST AHCI+RAID driver v11.2.0.1006 by Fernando slipstreamed by nLite. No other driver installed, no usb3 driver and no acpi.sys mod. The XP installation ends normally. I launched the WinXpPAE.exe 2.0 with /ALL /NB command line on another computer and from there I copied by hand the patched files in the windows\system32 folder of the destination XP disk, replacing the existing files with the patched versions of hal.dll, ntkrnlpa.exe and ntoskrnl.exe files (the last two renamed for multiprocessor pc).
After connecting the patched disk to the B75-Pro3M board, on restart, I got the blank screen always at same point: the pc hangs as soon as the XP logo and the horizontal scroll bar below appear.
The same on each restart. Same behavior on three other boards (one LGA 1150 and two 1151). XP boots in safe mode only.
By copying all the patched files (included ntkrnlmp.ex_ and ntkrpamp.ex_ not renamed) in the \i386 folder of the XP setup cd, then repacking the SP3 and DRIVER cab files and slipstreaming them together with the sata_ahci driver v11.2.0.1006 and acpi.sys 5048 in the .iso image, the setup ends normally and on restart, XP has finally booted and the total amount of ram has correctly recognized. But in the windows\system32 folder of the WinXPPae patched disk, the hal.dll is different from the one integrated into the iso image (hal.dll was slipstreamed into sp3.cab, driver.cab and copied to the i386 folder as hal.dl_ by makecab) while other libraries (halaacpi.dll, halacpi.dll, halapic.dll, halmacpi.dll, halmps.dll) are not present.
I copied this hal.dll (sha1: BE202C78DBF4D59880AA6A9430BE05D4156D6764) to another disk connected to another board where XP always froze (asus prime B250M) and this time the boot works fine and the total ram is correctly visualized. In this case, for the USB3 function, it is need to replace original amdxhc.sys with the one from 'amdxhc_pae_fix'.
I also tried a clean XP installation on the asus prime B250 with sliptreamed patched files but the results are the same as for the asrock B75 Ivy board.
Already tried with iaStor, iaStorA and storahci from your "XPSP3_CDDRIVERS_ENU" with no success.
For the above, how can I be sure that the patch applied in my system is the WinXpPae 2.0 and not the old 1.1 version?

## Page 250

#3736

dencorso

In my opinion, sufficient time has elapsed, so I'd like to ask ⇗ @Mov AX, 0xDEAD to kindly update his assessment of the currently still unresolved problems for running Windows XP x32 on sky/kaby/coffee lake hardware, and of the progress done till now.

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #172

> There many unresolved problems running Windows XP x32 on sky/kaby/coffee lake hardware
> my own list:
> - ACPI BSOD:
> .......... 0xA5 (0x03, X, 0xС0140001, Z) ACPI 2.0 syntax, 99% solved (custom acpi.sys), 1% - "QWordAcc" still 32bit only
> .......... 0xA5 (0x02, X ,Y ,Z) error in ACPIRangeValidatePciResources, PCI vs E820 list conflict, solved (custom acpi.sys)
> .......... 0xA5 (0x11, 0x08 ,Y ,Z) error in ACPIInitializeDDB, solved (custom acpi.sys)
> .......... other possible BSODs, unresolved
> - all integers in original ACPI 1.0 XP are 32 bits, ACPI 2.0 requires all ints to be 64 bits, unresolved. Acpi.sys from Longhorn v.5048 has 64 bit integers and compatible win Winxp
> - Broken acpi pm_timer, solved (custom hal.dll, forced to use TSC counter) or enable hidden bios option "TCO Timer"
> - Acpi tables patcher at boot time like Chameleon/Clover, solved,( ⇗ http://reboot.pro/topic/22051-acpi-patcher-at-boot-time)
> - CPU in C0 power state 50-60% of time even without cpu load, solved (custom intelppm.sys, 1) only C1 c-state or 2) C1/С7s/C10 c-states)
> - USB 3.x drivers for integrated intel chipsets, solved (patched AMD USB3 driver)
> - Resource manager show conflict VGA card with ACPI IOTR/IOTraps device, solved 1) manual patching dsdt or 2) custom acpi.sys
> - UEFI x64 Boot, partial solved for WinXP x64 only (bootmgr from vista beta+vesa vga driver)
> - NVMExpress drivers, partial solved (modified OFA 1.3/1.5 driver+storport.sys from windows 2003)
> - Access to additional 3TB+ Disks/GPT partitions, solved (Paragon GPT Loader)
> - Boot from GPT partitions, unresolved (require uefi boot support first)
> - TRIM support in NTFS/Storport/??? driver unresolved
> - Kernel debug with WinDBG/KD over LAN/USB3.0 connection solved, (⇗ https://github.com/MovAX0xDEAD/KDNET)
> - fixing PAE support in HAL (in progress)

#3737

genieautravail

> Zitat von ⇗ diderius6 im Beitrag ¶ #3729

> Only the ADATA_SSDToolBoxSetup.exe works for TRIM under XP SP3 for the Samsung 860 EVO 500 Gbyte.
> Crazy, the Samsung tool tells, only for Samsung devices^^.

⇗ @diderius6
Can you try Naraeon SSD Tools and tell us if TRIM is working too ?
⇗ https://sourceforge.net/projects/naraeon-ssd/
EDIT by Fernando: Unneeded parts of the fully quoted post and unneeded blank lines removed (to save space)

#3738

diderius6

⇗ @genieautravail
Naraeon SSD Tools work for XP SP3 for TRIM of Samsung SSD EVO 860 EVO. Time for manual TRIM is about 2 min.
Thanks a lot, this is a nice tool for SSD, because it also shows, how much Gbyte are written to this SSD at all.
Problem is with downloading NST(5.4.0).exe . I have to chose manual a server from Germany,
Dietmar

#3739 | XPWELL64 | Which Motherboard is best for Windows XP? I want a Desktop and it must contain IDE/AHCI/RAID setting to Install retro OS.
#3740 | Andalu | ⇗ @genieautravail thanks for the info ;) I tried a dozen of ssd utility and this is the only that permits the trim function in XP for my samsung nvme ssd. Even if Trimcheck 0.7 reports that 'trim appears to be not working' I did the manual trim anyway :)

#3741

gordo999

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #3739

> Which Motherboard is best for Windows XP?

⇗ @XPWELL64 ...can't advise you overall but make sure the mobo has PS/2 ports so you can use a keyboard and mouse while USB is being setup. You'll need two USB to PS/2 adaptors if you use a USB keyboard/mouse. Don't know if a unifying adapter will work via USB to PS/2 adapters if you use cordless keyboard/mouse.
Personally, I favour Intel chipsets and processors. I use an Asus B360M with an Intel chipset/processor and it is a lower end version of the Z370/390 chipsets.
⇗ https://www.pcworld.com/article/3268063/intel-motherboard-z370-vs-h370-vs-b360-vs-h310-8th-gen-cpu.html
Sorry...missed your requirement for IDE/AHCI/RAID compatibility. Did you mean SATA/AHCI/RAID compatibility? Although SATA controller can run in IDE mode I don't think modern motherboards use the old PATA IDE connectors if you intend to connect a hardrive via a parallel cable.

#3742 | XPWELL64 | ⇗ @diderius6 I want you to mod igxpmp32.sys file to work with DEV_1616
#3743 | diderius6 | ⇗ @XPWELL64 I tried to mod igxpmp32.sys, but without success Dietmar
#3744 | sqpp | Just a quick note, is there any 64 bit Windows XP ACPI patch already? T480 - Coffee Lake owner i5-8350u ⇗ @diderius6 ⇗ @daniel_k Just an update, so, I was able to bypass the earlier issue, with the A5 BSOD, now I am using 32 bit WinXP and getting 0x0000007B BSOD.

#3745

gordo999

> Zitat von ⇗ sqpp im Beitrag ¶ #3744

> now I am using 32 bit WinXP and getting 0x0000007B BSOD.

⇗ @sqpp ...the 7B bsod is related to SATA drivers. You will likely notice it occurs after it says, "Starting Windows". The Windows OS uses a miniport driver to communicate with the drive even though boot phase drivers have already done so. It's related to the ioStor driver or the lack thereof. There is a set of drivers listed in this thread and a set signed by Fernando that fixed the problem for me on XP 32-bit.

#3746

infuscomus

⇗ @diderius6 ⇗ @daniel_k
I have made a new patched hal.dll for XP
It contains these new functions from windows 7

    HalAllocateHardwareCounters
    HalBugCheckSystem
    HalConvertDeviceIdtToIrql
    HalDisableInterrupt
    HalEnableInterrupt
    HalEnumerateEnvironmentVariablesEx
    HalFreeHardwareCounters
    HalGetEnvironmentVariableEx
    HalGetInterruptTargetInformation
    HalGetMemoryCachingRequirements
    HalGetMessageRoutingInfo
    HalGetProcessorIdByNtNumber
    HalGetVectorInput
    HalInitializeBios
    HalInitializeOnResume
    HalMcUpdateReadPCIConfig
    HalQueryEnvironmentVariableInfoEx
    HalQueryMaximumProcessorCount
    HalRegisterDynamicProcessor
    HalRegisterErrataCallbacks
    HalRequestClockInterrupt
    HalSetEnvironmentVariableEx
    HalStartDynamicProcessor
    x86BiosAllocateBuffer
    x86BiosCall
    x86BiosFreeBuffer
    x86BiosReadMemory
    x86BiosWriteMemory

ntoskrnl is being more difficult to patch - the compiler complains about the heap stack size and I've already given it the maximum
I'm actually an amateur at programming, is anyone here skilled with Visual C++ 6.0?
infuscomus has attached files to this post

- ⇗ HAL2.zip

#3747 | sqpp | Yeah, I figured out yesterday, although none of the fernando drivers worked for me, can you guys help me to identify which one should I use? I5-8350u and 6th generation AHCI I think.

#3748

diderius6

⇗ @infuscomus
This is nice work, and everything begins with the first step.
Today I succeed to enable USB3 on the Lenovo x230.
I use the nice driver from ⇗ @daniel_k .
And in Bios I force to use USB3 (set to enabled).
From the Lenovo Webpage
"USB 3.0 is not supported on Windows XP - ThinkPad
USB 3.0 port doesn't work on Windows XP for ThinkPad. Affected Systems: Helix (Type 3xxx)L330, L430, L530 T430, T430i, T430s, T430si, T430u, T431sT530, T530i Twist S230uW530 X1 CarbonX230, X230s, X230 Tablet, X230i, X230i Table"
Oh, this is soso much fun:)),
I just also succeed to boot XP SP3 via USB3 on the x230 Thinkpad and this is faaast )
Dietmar
⇗

#3749

diderius6

⇗ @sqpp
Nice STORAHCI.sys driver from ⇗ @skullteria together with storport.sys will work. I just use this method for the Lenovo x230 Thinkpad.
Copy this 2 driver files on a working XP to windows\system32\drivers and add entry to registry

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci]
    "Type"=dword:00000001
    "Start"=dword:00000000
    "ErrorControl"=dword:00000003
    "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
       72,00,69,00,76,00,65,00,72,00,73,00,5c,00,73,00,74,00,6f,00,72,00,61,00,68,\
       00,63,00,69,00,2e,00,73,00,79,00,73,00,00,00
    "Group"="SCSI Miniport"
    "DisplayName"="@mshdc.inf,%storahci_ServiceDescription%;Microsoft Standard SATA AHCI Driver"
    "DriverName"="mshdc.inf"

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters]
    "BusType"=dword:0000000b
    "IoTimeoutValue"=dword:0000000a

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters\Device]
    "ResetInInit"=hex(7):56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,\
       00,45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,\
       2a,00,00,00,00,00
    "SingleIO"=hex(7):56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,30,\
       00,30,00,00,00,56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,31,\
       00,30,00,00,00,56,00,45,00,4e,00,5f,00,31,00,31,00,30,00,36,00,26,00,44,00,\
       45,00,56,00,5f,00,36,00,32,00,38,00,37,00,26,00,52,00,45,00,56,00,5f,00,32,\
       00,30,00,00,00,00,00
    "IgnoreHotPlug"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,32,00,26,00,\
       44,00,45,00,56,00,5f,00,34,00,33,00,38,00,30,00,26,00,52,00,45,00,56,00,5f,\
       00,2a,00,00,00,00,00
    "NeverNonQueuedErrorRecovery"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,\
       32,00,26,00,44,00,45,00,56,00,5f,00,34,00,33,00,38,00,30,00,26,00,52,00,45,\
       00,56,00,5f,00,2a,00,00,00,00,00
    "EnableCLOReset"=hex(7):56,00,45,00,4e,00,5f,00,31,00,30,00,30,00,32,00,26,00,\
       44,00,45,00,56,00,5f,00,34,00,33,00,39,00,31,00,26,00,52,00,45,00,56,00,5f,\
       00,2a,00,00,00,00,00
    "NoFUACommand"=hex(7):48,00,54,00,45,00,2a,00,00,00,48,00,69,00,74,00,61,00,63,\
       00,68,00,69,00,2a,00,00,00,48,00,54,00,53,00,2a,00,00,00,48,00,44,00,53,00,\
       2a,00,00,00,48,00,44,00,54,00,2a,00,00,00,00,00
    "NeedSetTransferModeCommand"=hex(7):4d,00,43,00,42,00,51,00,45,00,36,00,34,00,\
       47,00,42,00,4d,00,50,00,50,00,2a,00,00,00,00,00
    "NoLPM"=hex(7):57,00,44,00,37,00,34,00,30,00,41,00,44,00,46,00,44,00,3f,00,30,\
       00,30,00,4e,00,4c,00,52,00,31,00,2a,00,00,00,57,00,44,00,43,00,20,00,57,00,\
       44,00,37,00,34,00,30,00,41,00,44,00,46,00,44,00,3f,00,30,00,30,00,4e,00,4c,\
       00,52,00,31,00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,00,72,00,20,00,36,00,\
       56,00,3f,00,3f,00,3f,00,45,00,30,00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,\
       00,72,00,20,00,36,00,56,00,3f,00,3f,00,3f,00,46,00,30,00,2a,00,00,00,4d,00,\
       61,00,78,00,74,00,6f,00,72,00,20,00,37,00,56,00,3f,00,3f,00,3f,00,45,00,30,\
       00,2a,00,00,00,4d,00,61,00,78,00,74,00,6f,00,72,00,20,00,37,00,56,00,3f,00,\
       3f,00,3f,00,46,00,30,00,2a,00,00,00,00,00

    [HKEY_LOCAL_MACHINE\System\ControlSet001\Services\storahci\Parameters\PnpInterface]
    "5"=dword:00000001

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\PCI#CC_010601]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="storahci"

Dietmar

#3750 | sqpp | Could you please link to these specific posts? I can't find it. Also, you mentioned that copy these 2 driver files on a working XP. But I am getting this on the installation. So how I am supposed to do that? shouldn't I use nLite and include these drivers then build the iso?

## Page 251

#3751 | diderius6 | ⇗ @sqpp ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (59) you can use this with nlite Dietmar
#3752 | sqpp | ⇗ @diderius6 just a quick last question, do I also need to convert these to .SY_ right?
#3753 | diderius6 | ⇗ @sqpp I think, you can let them be, as they are Dietmar
#3754 | sqpp | Afaik, I can't import DLLs into Nlite, just inf files. So I guess, I must do, because DRIVER.CAB should contain these.
#3755 | sqpp | ⇗ @diderius6 same error actually, I might did something wrong? edit: I have used the i386 folder to import the inf file, so that should be 32 bit, not sure what else to do.
#3756 | diderius6 | ⇗ @sqpp Please describe step by step what you have done and results Dietmar
#3757 | sqpp | In the nLite driver section, I have included the i386 folder's file storahci.inf, then the rest of the files added to the DRIVER.CAB file via CABPCK14. Nothing else done on my end, this resulted in a B7 BSOD again.
#3758 | infuscomus | ⇗ @sqpp add your AHCI HWIDs to the section in txtsetup.sif ⇗ @diderius6 do you have any experience with Visual C++ 6.0?

#3759

diderius6

⇗ @sqpp
"In the nLite driver section, I have included the i386 folder's file storahci.inf"
I think, this is not correct.
You only have to go via nlite to folder storahcitxtsetup and from there to i386 folder
and integrate the driver
Dietmar

#3760 | diderius6 | ⇗ @infuscomus Years ago I played a little bit with Visual C++ but nothing more Dietmar
#3761 | sqpp | I don't really have other choices other than the .inf Look at my screenshots. ⇗ https://photos.app.goo.gl/B5EaZRnS5w5Hv5oJ9
#3762 | diderius6 | ⇗ @sqpp I think it is the fault of win10. Make a try with nlite 1.4.9.3 under XP SP3 Dietmar ⇗
#3763 | sqpp | ⇗ @infuscomus do I have to give the HWID for the controller or for the disk itself? I guess it's a silly question, so the controller?

#3764

sqpp

Same error by the way, I have used the HWID for the SATA controller by checking with HWinfo64 within Win10 and added this ID to the txtsetup.sif file within i386 folder.

    [HardwareIdsDatabase]
    PCI\VEN_8086&DEV_9D03&SUBSYS_225D17AA&REV_21 = "STORAHCI"

Does it look good?

#3765

sqpp

Just attached my sif file, so you might validate, but it should be good, I think
sqpp has attached files to this post

- ⇗ TXTSETUP.zip

## Page 252

#3766

diderius6

⇗ @sqpp
I just edit your TXTSETUP.SIF for storport and storahci
Dietmar
diderius6 has attached files to this post

- ⇗ TXTSETUP.rar

#3767 | sqpp | ⇗ @diderius6 same error actually. should I also replace the HWID in your TXTSETUP?

#3768

diderius6

⇗ @sqpp
I tested, that my settings work, no modification needed.
Have you copied storport.sys storahci.sys storahci.inf
into installationsfolder i386
Dietmar
PS: Have you edit dosnet.inf as described in
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (232)
and may be this is also needed
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (224)

#3769 | sqpp | Yes, I did. They are there, the problem might could be that I am using Easy2Boot to make this all happen, as I don't really have DVD reader neither a rewritable CD/DVD
#3770 | sqpp | I haven't edited dosnet.inf. In that post, you mentioned that it gave BSOD.
#3771 | Andalu | Is there someone who applied the WinXPPAE patch v2.0 with no issues?

#3772

diderius6

⇗ @sqpp
Here is my german dosnet.inf with storport and storahci
Dietmar
diderius6 has attached files to this post

- ⇗ DOSNET.rar

#3773

infuscomus

> Zitat von ⇗ sqpp im Beitrag ¶ #3769

> Yes, I did.
> They are there, the problem might could be that I am using Easy2Boot to make this all happen, as I don't really have DVD reader neither a rewritable CD/DVD

If you're using Easy2boot on your motherboards USB 3.0 ports it will always fail with a 7B BSOD
you need native USB 2.0 EHCI ports to use Easy2boot
USB 2.0 PCIE card
⇗ https://www.ebay.com/itm/USB-2-0-to-PCI-...lEAAOSwaBZZmNXa
or otherwise use a SATA DVD drive. The following contents have been linked to this post:

#3774 | infuscomus | ⇗ @diderius6 can I send you the source code for my kernel patcher program? if yes, maybe you can fix the heap size problem with ntoskrnlxp.cpp?
#3775 | diderius6 | ⇗ @infuscomus Yes, please send to me. I take a look at it from 20 December, because then I have holidays Dietmar
#3776 | infuscomus | ⇗ @diderius6 I sent you a PM with the source code
#3777 | diderius6 | ⇗ @infuscomus Thanks for the files )! "you use genpatch to convert ASM files into cpp files for the patcher program to apply" Please, describe this a little Dietmar
#3778 | infuscomus | ⇗ @diderius6 you can write a new function that you want to have patched into a program in assembler, then genpatch can convert that ASM into C++ code that the patcher program then uses to know what to write into the file you wish to patch.
#3779 | sqpp | ⇗ @infuscomus It's a laptop, so can't use, how about using my dock which has a 2.0 port? Although it uses Thunderbolt 3, but I think it may work in pre-environment (BIOS)
#3780 | infuscomus | ⇗ @sqpp you need a native USB 2.0 controller chip for XP setup to see your easy2boot drive, which your system doesn't have - hence the 7B BSOD because setup cannot see your easy2boot USB drive so you'll need to use a SATA DVD drive if you want to install XP

## Page 253

#3781

sqpp

⇗ @infuscomus, yeah, but it's actually loaded, I mean the files are actually loaded from the PenDrive, because the BSOD 7B only comes, when the drivers are loaded, including ACPI, then when it says windows setup starts or something like that, that's when the error appears. So it's half loaded? Because in this case, the files are actually loaded just fine from the USB, otherwise it would whine about the missing inf files.
Also, neither I can't properly use any SATA DVD drive, as my laptop has only one SATA connectors, which is used by the SATA SSD itself. I do have an USB DVD Reader, but that's not an option, I guess?

#3782

infuscomus

⇗ @sqpp
I'm just reporting what I found from attempting to install XP on my AMD Ryzen system
I only ever managed to get easy2boot to work without a 7B BSOD on the PCI-E USB 2.0 card - I've never got it working properly on the USB 3.0 ports on the motherboard.
SATA DVD drive worked for me.

#3783 | infuscomus | ⇗ @diderius6 I think I found a solution to the compiler heap stack issue - I managed to migrate it to Visual Studio 2005.
#3784 | sqpp | How about using this? ⇗ https://msfn.org/board/topic/149612-winntsetup-v394-40-rc2/

#3785

diderius6

⇗ @sqpp
I just test this and it installs XP from any USB port because it uses firadisk.
01. Insert blank USB Flash Drive and Start RMPrepUSB.
02. You may use any Volume Label but Select NTFS > make no other changes, do NOT Choose Source, just [lower left] 6 Prepare Drive > OK > OK
03. Wait for it to finish then click on Install grub4dos [center right button]
04. YES > OK > [Enter] > **STOP!!** Press on Cancel [do NOT copy grldr file when asked]
05. Exit [lower right]
06. Extract ASUS Tools and files for W7/XP USB file Install OS from USB.rar
Copy contents of folder Install OS from USB\XP\USB root to USB Flash Drive's root directory.
07. Extract ASUS AHCI driver for XP file iaStor_skl.rar
Copy contents of folder iaStor_skl to USB Flash Drive's root directory.
08. Copy the actual .iso file, Windows XP iso file to USB Flash Drive's root directory and make sure file name is XP.iso and not something else.
09. Disconnect E-V-E-R-Y-T-H-I-N-G from the motherboard so that only one hard drive is connected to it and make sure it is connected to one of the main Intel SATA ports, not additional ones you may have on the side.
10. F8 at startup should let you boot from the newly created USB Flash Drive.
You may see two versions of the USB Flash Drive.
DO NOT SELECT the UEFI version. If the non-UEFI version is not there, you need to go to BIOS and set the non-UEFI as a boot priority device.
BOTH non-UEFI and UEFI must be selected in the BIOS list, but boot from the non-UEFI version.
All non SATA/IDE drives should be disconnected, they should not show up in the boot device list at all, or the Windows XP installation may try to write to them and fail, which will crash the installation process, so only have a single IDE/SATA Windows XP drive connected
You may see the cursor flash in the upper left corner.
*WAIT*WAIT*WAIT*
11. SELECT: Widows XP Setup Step 1 (TXT-mode)
12. Wait for ISO to load and after you see Remember to press F6... message, *GET READY* to press Enter after which you will see a blue screen and at the bottom: Press F6 if you need to install a third party SCSI or RAID driver...
START PRESSING F6 then F7 then F6 then F7 (one after the other)...
13. Blue Windows Setup screen appears > Press S >
Select: FiraDisk Driver (32-Bit) and press Enter
Press S
Select: Intel (R) SKL SATA AHCI Controller (X99+Skylake) and press Enter
Press S
Select: ASMEDIA USB3 Controller Driver and press Enter
14. Press Enter to Continue
15. Setup is Starting Windows > Enter > F8 (to agree) > Select partition where Windows XP should be installed. No partition should ever be formatted under Windows XP, only under Windows Vista/7/8/10 so > Leave the current file system intact (no changes)
PAY ATTENTION TO DRIVE LETTER OF PARTITION YOU ARE INSTALLING TO, that will be the Windows XP system drive letter after installation completes.
16. Wait for the process to finish and ALLOW the timer to run out telling you the computer will be restarted, do not press Enter to Restart immediately. Start pressing F8 to be able to select to boot from the USB Flash Drive again. If the computer freezes, restart it manually and boot from USB Flash Drive again.
17. This time SELECT: Widows XP Setup Step 2 (GUI-mode)
18. Windows XP may hang on first boot, just like in the "good old days".
If (when) that happens, Reboot!
On the XPinstallfromUSBviaFiradisk.pdf instruction from hwbot it is on page 19-26
Dietmar
⇗ https://community.hwbot.org/topic/141067...-of-mainboards/
look for file Install OS from USB.rar there, it contains also working RMPrepUSB.
diderius6 has attached files to this post

- ⇗ USB root.rar
- ⇗ XPinstallfromUSBviaFiradisk.pdf

#3786 | sqpp | I actually do have Coffee Lake and not Sky Lake it's a 8th generation i5
#3787 | diderius6 | ⇗ @sqpp It works on any motherboard for install of XP, as long as it has an USB connector Dietmar
#3788 | sqpp | I will check it, hopefully the last time!
#3789 | sqpp | NVM!
#3790 | diderius6 | ⇗ @sqpp You have to set mark at XP/BartPE bootable [NTLDR] in RMPrepUSB install of XP Dietmar
#3791 | sqpp | ⇗ @diderius6 it was actually the grub, I forgot to install that, but now it is okay!
#3792 | sqpp | There is a problem though, I really didn't partitioned the current Windows 10 and couldn't install beside of that, so I think, I will need to Install win10 now and seperate a partition just for XP using NTFS.

#3793

diderius6

⇗ @sqpp
Can you see your harddisk?
Best is, to use another disk for the XP install.
If you chose the same harddisk as for Win10,
use program AOMEI. But this will only work, if the harddisk has a MSDOS partions table.
If the harddisk is formatted with GPT,
only Gparted can help to change the harddisk to MSDOS partions table
Dietmar
PS: Only the Professional version of AOMEI can change GPT <=> MSDOS partions table on harddisk
without loosing data.

#3794 | sqpp | Well, that's what I wanted, although the laptop HDD I have in extra won't fit into my Thinkpad, it's a bit thicker than the SSD which is currently used.
#3795 | sqpp | There is a tool called Partition Tool Mini, I just got it today, as there was a free giveaway, using it long ago, it can covert drives and partitions to MBR

## Page 254

#3796 | diderius6 | ⇗ @sqpp I use a mSata from Samsung EVO 860 500 GB in my Lenovo x230 laptop as second harddisk Dietmar ⇗
#3797 | sqpp | Thats a good idea, btw, I have found a problem, installing the USB 3.0 driver, it freezes the setup

#3798

diderius6

⇗ @sqpp
No need to install any USB driver.
Do not press F6, if you make and use a XP.iso with needed drivers for AHCI.
The firadisk driver is already installed,
it is an error in the description
Dietmar
EDIT: For XP SP3 the bootable USB stick only needs to contain
firahelper.ima.gz
grldr
menu.lst
XP.iso (your XP install medium)

#3799 | sqpp | I think, my ISO might be a bit messed up because of yesterday, it's whining about some INF files now that are missing. I have tried to make a new one just with ACPI patch, but then it didn't recognize the disk (even I have selected the SATA drivers with F6)
#3800 | diderius6 | ⇗ @sqpp If your XP.iso contains STORAHCI driver and storport, no need to hit F6 Dietmar
#3801 | sqpp | All right, the problem I actually got is The following value in the .SIF file used by Setup is corrupted or missing: Value on on the line in section [WinntDirectories] with key "201." Setup cannot continue.
#3802 | sqpp | I think I found the issue, trying to solve it now. Just a quick question, by any chance I might able to get at least DirectX9 on my WinXP for the MX150 or no chance?
#3803 | diderius6 | @ sqpp Drivers for nVidia GeForce MX150 for Windows XP x86 do not exist. But because it is from Nvidia, there is a small chance, that another Nvidia driver for XP can be hacked Dietmar
#3804 | sqpp | Okay, other thing, I was able to install the Windows XP, but when I am about the GUI install and the XP logo about to boots, it's goes BSOD A5 again. The ACPI should work, already, I do believe, as otherwise it would have failed before. PS:. I am really sorry for talking this much.
#3805 | diderius6 | ⇗ @sqpp I think, the XP Setup has changed the modded acpi.sys against the original one. If this is true, you only need to copy the modded acpi.sys again into windows\system32\drivers on your harddisk Dietmar
#3806 | sqpp | How could I do that without booting into the OS? Using Windows 10?
#3807 | diderius6 | ⇗ @sqpp I use for this a harddisk to USB dock, but from other OS it is also possible Dietmar
#3808 | sqpp | Jesus Christ, now it's telling me when about to boot that hal.dll is missing or corrupt.
#3809 | diderius6 | Mühsam nährt sich das Eichhörnchen:)) Dietmar

#3810

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3746

> the compiler complains about the heap stack size and I've already given it the maximum

⇗ @infuscomus ....I am no expert with C or C++ but one thing I have noticed about compiler errors is that you cannot take them literally all of the time. A heap error could be generated by an error elsewhere. It could be in the way you have written a C++ statement and how the compiler has interpreted it. It could come down to a simple syntax error where you have omitted a required bracket, like a ) on the end of a statement.
Here's an example of reasons for an out of heap space compiler error: ⇗ https://docs.microsoft.com/en-us/cpp/error-messages/compiler-errors-1/fatal-error-c1060?view=vs-2019

## Page 255

#3811 | infuscomus | ⇗ @gordo999 I managed to migrate the project over to Visual Studio 2005 the 2005 compiler seems to work better, no heap error now.

#3812

infuscomus

⇗ @sqpp ⇗ @diderius6
just an idea to get around all of these problems installing XP
using paragon rescue kit (diderius6 I sent you a copy of this earlier) we could make an image of a working XP install (with ACPI and AHCI patches - and USB3?)
then send the image and paragon rescue kit media to sqpp
have sqpp use rescue kit to restore the image to a HDD and see if it works?

#3813

diderius6

⇗ @infuscomus
I use the Paragon rescue kit for a laptop with secured Bios,
put whole XP SP3 like a big file via USB bootable stick and start after from this,
really nice
Dietmar
PS: We can make a generic XP.iso with the STORAHCI driver and stortport and all the new USB drivers,
very similar as ⇗ @daniel_k did.

#3814 | sqpp | That would be really amazing, actually probably in the next year not now, but I am building an XP machine, it's an EVGA 780 SLI board and I still need many hardware, but at least now I will know how to include the SATA drivers, as I have tried to do that already with Easy2Boot, which didn't really work, so I guess, I will need to do something else (most likely the way diderius6 said yesterday, where I was finally able to at least get into the boot logo)

#3815

gordo999

> Zitat von ⇗ infuscomus im Beitrag ¶ #3811

> I managed to migrate the project over to Visual Studio 2005
> the 2005 compiler seems to work better, no heap error now.

⇗ @infuscomus ...that another solution I forgot about.

#3816

kithylin

I hope no one is mad for me asking but I found this thread last night via google searching and I ended up on page 55 of this thread, back when folks were still hacking the acpi.sys for XP for B350 boards. Well I recently just went AMD and bought an X470 motherboard. Specifically the MSI Gaming Plus X470. Is there anyone that could PM me a download link to a working version of XP-32 ISO file that would install and run stable on this motherboard perhaps?
Do we still need to self-modify the files via n-lite? Because I could do that.. if there is a post with instructions and a link to the modified files.

#3817 | diderius6 | ⇗ @kithylin Copy a for Ryzen modded acpi.sys into your installationsfolder i386 of XP SP3 and use as AHCI driver for the MSI Gaming Plus X470 board the STORAHCI driver together with storport and it is done via nlite Dietmar
#3818 | kithylin | Okay.. where would I get / download these modified files then? Is it buried somewhere back in this thread?

#3819

diderius6

⇗ @kithylin
For the STORAHCI driver file storahcitxtsetup.rar
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (64)
For acpi.sys 5048 line for Ryzen
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (149)
The last best acpi.sys from outer space ) version, works also for Ryzen
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (215)
And for storport settings
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (190)
Dietmar

#3820

genieautravail

> Zitat von ⇗ Andalu im Beitrag ¶ #3771

> Is there someone who applied the WinXPPAE patch v2.0 with no issues?

What issues do you have ?

#3821 | Andalu | ⇗ @genieautravail please see my post ¶ here. Does it work for you?

#3822

genieautravail

> Zitat von ⇗ Andalu im Beitrag ¶ #3821

> @genieautravail
> please see my post ¶ here. Does it work for you?

I don't slipstream the patch into a CD and I think that isn't a good idea to do like this.
I apply the patch only after install of XP.
I'm testing the patch 2.0 /4GB on a Dell laptop (Latitude E6230) with no issues.
With the patch 1.1, I had lost all the USB ports of the laptop.
Each time I plugged an usb device, XP displayed a message sayng that the USB hub doesn't have enough power for running the device...
No more issues like this with the patch 2.0.

#3823 | genieautravail | ⇗ @Andalu For playing with files protected by the Windows File Protection (WFP), see here: ⇗ Windows File Protection (WFP)
#3824 | genieautravail | ⇗ @Andalu And don't forget to backup the original files before applying the patch...
#3825 | Andalu | ⇗ @genieautravail As already reported, I also tried to replace the files from another hard drive to the destination XP drive bypassing the WFP protection but XP always hangs at same point for every tried board. In my case, I installed the WinXPPae 1.1 patch with no issues but some programs, like macrium reflect, freeze sometimes and most probably, the WinXPPae 2.0 patch would solve those problems.

## Page 256

#3826

daniel_k

⇗ @Mattiwatti, sorry for the late reply.
I was talking about a simple driver, which is loaded as a PCI bus filter driver (*PNP0A08), like the one from Intel (sadly it crashes XP).
It should scan for a device with ID like PCI\VEN_8086&DEV_1E31 and change its configuration registers D0 and D8 to a value of 0F.
Have you ever seem something like that?
Additionally, we have an AMD driver which works just fine with Intel XHCI controllers.
But when PAE is enabled, it breaks NTVDM and by consequence VGA?! or the other way around.
In certain cases, only affects full screen mode of a DOS app (running EDIT.COM and trying to switch to full screen with ALT+Enter) results in the following error:

    ---------------------------
    16 bit MS-DOS Subsystem
    ---------------------------
    The NTVDM CPU has encountered an illegal instruction.
    CS:0000 IP:9872 OP:ff ff 00 00 00

In other cases, no DOS apps can be run and error message is the same.
Any tips to track down this conflict or memory corruption? Personally, I believe the driver somehow corrupts memory used by NTVDM or VGA.

#3827

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3735

> @daniel_k
> I installed XP v5.1.2600 on my former crazy asrock B75-Pro3M as 'acpi multiprocessor pc' with the only Intel RST AHCI+RAID driver v11.2.0.1006 by Fernando slipstreamed by nLite. No other driver installed, no usb3 driver and no acpi.sys mod. The XP installation ends normally. I launched the WinXpPAE.exe 2.0 with /ALL /NB command line on another computer and from there I copied by hand the patched files in the windows\system32 folder of the destination XP disk, replacing the existing files with the patched versions of hal.dll, ntkrnlpa.exe and ntoskrnl.exe files (the last two renamed for multiprocessor pc).
> After connecting the patched disk to the B75-Pro3M board, on restart, I got the blank screen always at same point: the pc hangs as soon as the XP logo and the horizontal scroll bar below appear.
> The same on each restart. Same behavior on three other boards (one LGA 1150 and two 1151). XP boots in safe mode only.

Please post complete system specs.

#3828

daniel_k

> Zitat von ⇗ dencorso im Beitrag ¶ #3736

> In my opinion, sufficient time has elapsed, so I'd like to ask @Mov AX, 0xDEAD to kindly update his assessment of the currently still unresolved problems for running Windows XP x32 on sky/kaby/coffee lake hardware, and of the progress done till now.

Hi Den!
It's a shame that he went into "Ignore" mode.

#3829 | daniel_k | ⇗ @genieautravail, when you have some time, please test with /ALL option.

#3830

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3674

> @daniel_k
> do you want to see the source code for my kernel patcher program?
> you seem more knowledgeable than me so you might have better luck producing something useful with it

Thanks, but I'm not into kernel patching and don't have that much time.

#3831

daniel_k

⇗ @diderius6 and everyone
Please try this new AMDXHC driver, based on latest driver v1.1.0.0276 from Dec 2018.
This was a really tough job, please don't modify and redistribute publicly. Thanks.
Managed to restore XP support, INF files merged into a single one for easier installation.
Sadly, 32-bit PAE is still an issue. Otherwise, this driver is perfect.
The AMDXHC driver is the only driver which works with devices connected to hubs during XP/Server 2003 setup.
Previous version had a bug that could deadlock your system under certain circumstances.
Please use this beta, which fixes the issue (but code still not perfect).
Final version to be released really soon.
PS: This makes no sense: "Removed USBD.SYS dependency (it's integrated into driver)"
As the file is needed for other purposes, otherwise USB devices won't work.

#3832

Andalu

⇗ @daniel_k
Systems setup:
- i5-3470 Ivy Bridge (LGA 1155)
- Asrock B75 Pro3-M
- 32GB ram (4x8) Kingston HyperX Fury DDR3 1600MHz
- HD WD5000
- i7-4770k Haswell (LGA 1150)
- Msi CSM-Q87M-E43
- 32GB ram (4x8) GSkill RipjawsX DDR3 2133MHz
- SSD 250GB Samsung 850 evo
- i5-6600 SkyLake (LGA 1151)
- Asrock B250M Pro4
- 64GB ram (4x16) GSkill Aegis DDR4 2400MHz
- HD HGST 7k1000
- Pentium G4440 SkyLake (LGA 1151)
- Asus Prime B250M-C/CSM
- 8GB ram (2x4) Corsair Vengeance 2400Mhz
- HD Seagate ST1000LM035
Common for all systems:
- Windows XP SP3 original ISO v5.1.2600 ITA, no updates
- Intel RST AHCI+RAID driver v11.2.0.1006 by Fernando slipstreamed by nLite
- 16GB USB2.0 Flash Drive with XP ISO installed by yumi
- Acpi.sys 5048 (SHA1: 8EF48518B17DAAC4A90632A811FBFDC8183C325B) from acpi5048_intel_amd_final.rar added for LGA1151 boards only.
No other driver or file slipstreamed.

#3833 | daniel_k | ⇗ @Andalu All systems running with onboard graphics? It's so strange that the system boots in Safe mode.
#3834 | infuscomus | ⇗ @daniel_k can you show me how you properly remove a dependency from a driver? I'd like to know how you removed USBD.SYS dependency from it
#3835 | Andalu | ⇗ @daniel_k All with onboard graphics except for the msi Q87 equipped with a Radeon R7 250 Your new AMDXHC driver seems to work fine on my asus prime B250. Not tested yet on other boards.

#3836

antome

Hi guys I still have problems starting windows xp x64 on Z390 XI Gene. The same os start regularly on the z270 IX Apex without the need for modified bios. On the z390 it only starts in safe mode, can you help me? Has anyone managed to start it correctly on the z390? To exclude problems with the sata deactivated by bios and I used a pcie / sata jmicron card
⇗ ⇗
in normal mode i get this error
⇗

#3837 | diderius6 | ⇗ @antome I managed to install a full XP64 on z390 board. Make use of STORAHCI driver together with Storport Dietmar

#3838

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3834

> @daniel_k
> can you show me how you properly remove a dependency from a driver? I'd like to know how you removed USBD.SYS dependency from it

Can't give you a step by step explanation, but I think you can figure it out by yourself with some guidance:
- I've attached the original driver and delcert utility to delete signature (just run delcert driver.sys).
- Get CFF Explorer from ⇗ https://ntcore.com/?page_id=388
- Compare both files (use amdxhc.sys), my patched file is larger. Open both original and patched in CFF Explorer, I've created a new section named .text with same flags as the original where the new code was written.
- Disassembly original and patched. In the disassembly of original, search for every function from USBD.SYS that I've integrated in patched file (USBD_CreateConfigurationRequestEx, USBD_ParseConfigurationDescriptorEx and USBD_GetUSBDIVersion). For every API call found, search for the corresponding offset in the disassembly of the patched file and "follow" the call through the added code. You'll see I've replaced the call import with a call to "local" code (disassembly usbd.sys and see for yourself).
For x86 only, it was needed to delete the corresponding address in the relocation table.
- After all API calls were replaced with local calls with their corresponding code, deleted the whole USBD.SYS imports with CFF Explorer. Optionally, you can "delete" the strings by "zeroing" all function name / usbd.sys texts.
I still didn't take the time to understand how to delete a single import function, but what I do is simply to rename the name to another known existing function.

daniel_k has attached files to this post

- ⇗ delcert.rar
- ⇗ 1.1.0.0276.rar

#3839

antome

> Zitat von ⇗ diderius6 im Beitrag ¶ #3837

> @antome
> I managed to install a full XP64 on z390 board.
> Make use of STORAHCI driver together with Storport
> Dietmar

the problem cannot be the a352 driver because I have disabled the integrated ports on the motherboard and I used a pcie sata jmicron card with native driver for xp.
what acpi.sys file did you use? Have you also re-created sp2.cab with modified acpi.sys?
did you use the z390 dark or something else? the datk has almost complete acpi support for xp via bios which could fill gaps in the modified acpi.sys file

#3840

diderius6

⇗ @antome
It is a driver, because XP64 starts in Safe Mode.
Try STORAHCI together with Storport.
I noticed, that XP64 SP2 is unstable on nearly every motherboard.
Sound, Lan, brrr..
So, another driver can make this BSOD also
Dietmar

## Page 257

#3841

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3826

> It should scan for a device with ID like PCI\VEN_8086&DEV_1E31 and change its configuration registers D0 and D8 to a value of 0F.

⇗ @daniel_k ....how do you figure out what the configuration registers should be? Are you getting the info from an Intel spec sheet or by trial and error? Just curious.

#3842 | daniel_k | ⇗ @Andalu It's so odd your issue, makes no sense. What about disabling any non-essential onboard devices such as LAN, Audio, COM/LPT ports etc? If it boots in Safe Mode, there is something causing that blank screen issue. Thanks for trying the new driver, by the way.
#3843 | daniel_k | ⇗ @diderius6 Don't have any issues with XP x64 here, maybe using the original ACPI.SYS with a modded DSDT is better. Remember that ⇗ @Mov AX, 0xDEAD said that the beta 5048 ACPI.SYS has issues with 64-bit variables.

#3844

daniel_k

> Zitat von ⇗ gordo999 im Beitrag ¶ #3841

> @daniel_k ....how do you figure out what the configuration registers should be? Are you getting the info from an Intel spec sheet or by trial and error? Just curious.

By reading the datasheet:
⇗ https://www.intel.com/content/dam/www/pu...h-datasheet.pdf
Page 698:
D0hD3h - USB 2.0 Port Routing
D8hDBh - USB 3.0 Port SuperSpeed Enable
Page 713 - 17.1.33 XUSB2PR xHC USB 2.0 Port Routing Register (USB xHCID20:F0)
Page 714 - 17.1.35 USB3_PSSENUSB 3.0 Port SuperSpeed Enable Register(USB xHCID20:F0)
Just needed confirmation from ⇗ @Andalu by booting Windows 7 with USB properly operating in XHCI mode.
Intel did some really silly things just to break XHCI in XP, first the 64-bit DSDT thing to prevent any driver from loading, then the need of a PCI bus filter driver to fully enable XHCI mode/speed on "selected" OSes.
The "switch" driver uses KMDF 1.9 (supported by XP), but was written in a way to support only Windows 7, although it does work in Vista, but crashes XP.

#3845

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #3844

> Intel did some really silly things just to break XHCI in XP, first the 64-bit DSDT thing to prevent any driver from loading, then the need of a PCI bus filter driver to fully enable XHCI mode/speed on "selected" OSes.

daniel_k ....once again, congrats for figuring all this out. Intel have indeed abandoned faithful users like myself to side with Micro$oft. Even their setup files for USB drivers have built-in code to prevent the loading of the software for anything beyond Skylake.
There's no good technical reason for this behavior other than to enable Micro$oft in forcing users to use Windows 10, which is no better than W7, and has spyware built in. M$oft abandoned desktop users with W8 by designing the OS for touch screen users until the users revolted and forced them back to a mouse/keyboard option. If Linux designers were not so lame they could have taken over by now. But they insist on keeping that archaic Unix system under the hood, with brilliant features [/sarc off] like no extensions on files and text editors that have not changed since the 1970s.

#3846 | infuscomus | ⇗ @daniel_k Thanks very much

#3847

dencorso

> Zitat von ⇗ daniel_k im Beitrag ¶ #3828

> > Zitat von ⇗ dencorso im Beitrag ¶ #3736

> > In my opinion, sufficient time has elapsed, so I'd like to ask @Mov AX, 0xDEAD to kindly update his assessment of the currently still unresolved problems for running Windows XP x32 on sky/kaby/coffee lake hardware, and of the progress done till now.

> Hi Den!
> It's a shame that he went into "Ignore" mode.

So it is! But I'm confident he'll be back sometime soon (one can hope, right?).
BTW, WildBill 's PETool can remove individual relocations and fix the relocation table for you... maybe you'll find it useful: ⇗ http://www.mediafire.com/file/elfceaj4ny..._0.0.5.zip/file

#3848

Andalu

⇗ @daniel_k
Thanks so much for your new USB3 modded driver and for sharing it
Win7 32bit boots correctly with it (forced driver installation needed).
XP 32bit with new amd driver also works on:
Asus prime B250
Asrock B250
Asrock B75 Pro3
It fails on Msi Q87 (but here any usb3 driver has never worked).

#3849

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3842

> @Andalu
> It's so odd your issue, makes no sense.
> What about disabling any non-essential onboard devices such as LAN, Audio, COM/LPT ports etc?
> If it boots in Safe Mode, there is something causing that blank screen issue.

All onboard devices are always set on disable, except for the audio controller. Same issue even disabling it.
I restored an old asus P5QSE lga775 (XP boots on sata mode with 32bit Intel RST AHCI & RAID driver v11.2.0.1006 by Fernando installed) to try the WinXPPae 2.0 patch (files copied by hand from another XP hard drive) and here I got for the first and only time the following bsod:
BAD_POOL_HEADER
0x00000019 (0x00000020, 0xE1563530, 0xE1563820, 0x0C5E0408)
on next reboots/shutdown never seen again the bsod. XP hangs when the logo appears as for the other boards.
The identical bsod occurs only when the WinXPPae patch 2.0 procedure is re-started from stratch.
Here too XP can boot in safe mode only.

#3850 | daniel_k | ⇗ @Andalu Please compress your XP ISO with 7-zip or WinRAR, upload it to MediaFire, Google Drive or Mega and send me a PM with the link.

#3851

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3848

> @daniel_k
> Thanks so much for your new USB3 modded driver and for sharing it
> Win7 32bit boots correctly with it (forced driver installation needed).
> XP 32bit with new amd driver also works on:
> Asus prime B250
> Asrock B250
> Asrock B75 Pro3
> It fails on Msi Q87 (but here any usb3 driver has never worked).

Glad to know it works!
For Win7, you better use Intel official drivers.
What is the error with the MSI Q87?

#3852

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3851

> What is the error with the MSI Q87?

The new amd xhci driver installs properly on msi Q87 but all usb3 ports act as usb2. In bios the USB options are configured like the other boards where the usb3 feature works fine. I tried all the usb3 drivers found in this forum but each of them gave me error or the usb3 feature doesn't work anyway.
P.S.: you have pm ;)

#3853 | infuscomus | Has anyone here successfully installed XP on Threadripper?

#3854

genieautravail

> Zitat von ⇗ daniel_k im Beitrag ¶ #3829

> @genieautravail, when you have some time, please test with /ALL option.

I have only 4 GB of memory on this computer. The /ALL option has no sense.

#3855

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3852

> The new amd xhci driver installs properly on msi Q87 but all usb3 ports act as usb2. In bios the USB options are configured like the other boards where the usb3 feature works fine.

You need to change those same registers with WPCRSET.

## Page 258

#3856

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3855

> > Zitat von ⇗ Andalu im Beitrag ¶ #3852

> > The new amd xhci driver installs properly on msi Q87 but all usb3 ports act as usb2. In bios the USB options are configured like the other boards where the usb3 feature works fine.

> You need to change those same registers with WPCRSET.

It works here too
Thankssssss!!!!

#3857

dencorso

> Zitat von ⇗ Andalu im Beitrag ¶ #3856

> > Zitat von ⇗ daniel_k im Beitrag ¶ #3855

> > > Zitat von ⇗ Andalu im Beitrag ¶ #3852

> > > The new amd xhci driver installs properly on msi Q87 but all usb3 ports act as usb2. In bios the USB options are configured like the other boards where the usb3 feature works fine.

> > You need to change those same registers with WPCRSET.

> It works here too
> Thankssssss!!!!

OK. Great!
Well, I know how to use WPCRSET... yet, I'm lost somewhat... would you please kindly detail: which registers, from which value to which new value, exactly?

#3858

daniel_k

> Zitat von ⇗ dencorso im Beitrag ¶ #3857

> OK. Great!
> Well, I know how to use WPCRSET... yet, I'm lost somewhat... would you please kindly detail: which registers, from which value to which new value, exactly?

It's here:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (238)
By the way, I've uploaded a beta version of the latest USB driver (276), please read info at:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (256)

#3859

XPWELL64

⇗ @diderius6
There is no PDBM &= 0xFFFFFFFFFFFFFFF9 PDBM &= 0xFFFFFFFFFFFFFFFD in my HP cs1011nt in my dsdt of my bios but there are lots of ToIntegers. You said that two of the long integers are PDBM &= 0xFFFFFFFFFFFFFFF9 and PDBM &= 0xFFFFFFFFFFFFFFFD. Download the file and look at two dsdt.dsl. 07.dsl is without PDBM &= 0xFFFFFFFFFFFFFFF9 and PDBM &= 0xFFFFFFFFFFFFFFFD (cs1011nt) and 11.dsl is from another hp laptop with PDBM &= 0xFFFFFFFFFFFFFFF9 and PDBM &= 0xFFFFFFFFFFFFFFFD.
XPWELL64 has attached files to this post

- ⇗ 2hpdsdt.zip

#3860 | XPWELL64 | I decompiled 4 AMD ASUS MOBO DSDTs and 1 Intel DSDT and all of the AMD MOBOs doesn't have PDBM.

#3861

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3858

> By the way, I've uploaded a beta version of the latest USB driver (276), please read info at:
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (256)

It works fine, thanks again

#3862

Andalu

> Zitat von ⇗ dencorso im Beitrag ¶ #3857

> OK. Great!
> Well, I know how to use WPCRSET... yet, I'm lost somewhat... would you please kindly detail: which registers, from which value to which new value, exactly?

> Zitat von ⇗ daniel_k im Beitrag ¶ #3858

> It's here:
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (238)

I can only add that the same method worked on two different boards (B75 Ivy and Q87 Haswell) with two slightly different usb3 issues.

#3863 | XPWELL64 | Please look at the eighth page of the PDF: ⇗ http://download.microsoft.com/download/5...cpa002_wh06.ppt
#3864 | XPWELL64 | The X79 has TOINTEGERS too.
#3865 | XPWELL64 | ⇗ @diderius6 With MMTool I got Invalid FFS file while I was integrating a dsdt table into a bios. How do I integrate your DSDT.AML into BIOS with MMTool 5.02? My laptop's series is ASUS K555LB/X555LB. Is there any IASL step before integrating it?
#3866 | diderius6 | ⇗ @XPWELL64 DSDT.AML has to be exchanged against old DSDT body, at the same place in Bios as before, via Uefi tool Dietmar
#3867 | infuscomus | ⇗ @XPWELL64 I think ⇗ @Mov AX, 0xDEAD wrote a program so that you can test your DSDT works before you flash it to BIOS
#3868 | XPWELL64 | First, I'll test the DSDT.aml with ⇗ @Mov AX, 0xDEAD's DSDT patcher at boot time program. If it works, I'll integrate it into the bios with UEFITool. Next, I'll mod the igxpmp32.sys + all DLL files (if it works with only modded igxpmp32.sys no need for this) with IDA 32 bit and Dependency Walker.

#3869

greybeard

Hi, I'm new here and have been following this thread closely since I plan to finally assemble my new Asus Prime X-370 box over the holidays. I'm not fond of Windows 10, so I'm trying to maintain my current environment which is a mix of Windows 7 and XP64 apps. With your help (Thank you!) I've got Windows 7 installed and working well and am making some progress in getting XP64 installed. It's still crashing during the "loading drivers" phase of the install, but I think I can muscle my way through that.
However, I have a question that may be off-topic. One of my options is to use Windows Server 2008, and I'm wondering if any of your mods will help me get USB support working there. So far, I've been unable to get any mouse support. If not, can you point me to the right forum?
Thanks!

#3870

gordo999

> Zitat von ⇗ greybeard im Beitrag ¶ #3869

> I've been unable to get any mouse support. If not, can you point me to the right forum?Thanks!

⇗ @greybeard ...the x370 has a single PS/2 port which is a combo mouse/keyboard port. You'll need an adapter cable that adapts the mouse and kbd to a single input plus 2 USB to PS/2 connectors. That will get you going with a USB mouse/kbd till you solve the USB problem.
On my Asus B360M, I had to get a USB 3 adapter card to get USB running initially on W7. I plugged a 7 port USB extender into that and ran my wireless mouse off one of those doohickeys that plug into a USB port. That left me with 3 extra USB 3 ports and 6 USB 2 ports. I even got that running on XP using drivers I found on a Czech site.
I have USB running on W7 now through all mobo USB ports using a driver from this site. Still working on getting the mobo USB ports running on XP. I have been kind of distracted but I think daniel_k has a recent offering.

## Page 259

#3871 | greybeard | ⇗ @gordo999 Thanks for the quick reply. Yeah, I was thinking about getting one of those combo cables. Rummaging through my parts bin, I found one that doesn't have the right connectors. If necessary, I'll buy the right one and see if it will help with my Windows Server 2008 issue.
#3872 | YuriyCN | I need USB3 driver for Windows XP (32-bit). Chipset = Intel H110M (100-series) HardwareID= VEN_8086&DEV_A12F Is there a working driver?

#3873

gordo999

> Zitat von ⇗ greybeard im Beitrag ¶ #3871

> If necessary, I'll buy the right one and see if it will help with my Windows Server 2008 issue.

⇗ @greybeard ...Don't forget the 2 x USB to PS/2 adapters while you're at it...unless you have a PS/2 mouse/kbd. I have never seen a combo port for PS/2 since my board has two PS/2 ports for mouse and kbd.
I wouldn't mess around with cables unless you confirm the pin-out. Asus is pretty good with supplying pin-outs although sometimes you have to decode the supplied datagram (in the manual) to reveal them. That's especially true on the mobo. There are two serial ports on mine and it was lucky that I confirmed the pin layout first, it's not done to any convention I knew off. May not be an issue with low power devices like mouse/kbd but having already blown a mobo through a dumb mistake, like getting a fan connector mixed up with the BIOS battery shorting clip, right beside it, I no longer take chances.

#3874 | YuriyCN | I know about AMDXHC driver, but I did not understand, whether this driver supports a motherboard ⇗ https://www.gigabyte.com/Motherboard/GA-H110M-DS2-rev-10#ov with an Intel H110M chipset??
#3875 | diderius6 | ⇗ @YuriyCN I tested Intel H110M and all drivers are there for XP SP3 Dietmar

#3876

YuriyCN

> Zitat

> I tested Intel H110M and all drivers are there for XP SP3
> Dietmar

Please give a link where to download this driver.

#3877

greybeard

Ok, I'm stuck and need some help. Trying to install Windows XP32 SP3 on an ASUS Prime X-370A and here's what has happened over the last 2 days
The installation begins,
Allows me to select a partition,
Begins copying files
Says it cannot copy storahci.reg,
Reboots to the installation GUI and starts the actual install,
Gets to installing devices,
Crashes with a Stop 0xc5.
I think I'm using the latest drivers, and have made the suggested edits to txtsetup.sif and dosnet.inf, but I'm clearly missing something.
Can anyone help?

#3878 | infuscomus | ⇗ @greybeard put storahci.reg in your i386 folder of your XP install media
#3879 | greybeard | ⇗ @infuscomus Thanx for the quick reply. I had done that earlier and it didn't seem to help. Will verify, try again, and get back to you.
#3880 | diderius6 | ⇗ @greybeard BSOD 0xc5 is a driver fault. Disable nearly everything in Bios and try install again. Another way is to hit F8 for Safe Boot on last step of XP install Dietmar

#3881

greybeard

⇗ @diderius6
Not sure what to disable in the BIOS. Am using the most recent BIOS with pretty much default settings. Just making sure I can boot to MBR disks. But if you an give me some suggestions about problematic settings, I can try to disable them.
The one thought I had is a potential problem with my boot disk - Samsung EVO SSD. That shouldn't be a problem, right?
I wish I could get to the last boot

#3882 | diderius6 | ⇗ @greybeard The Samsung EVO SSD is no problem, as long as it has 512 Bytes/sector. Disable everything in Bios: Only SATA driver stay enabled Dietmar
#3883 | greybeard | ⇗ @diderius6 OK, will do, and let you know how it works out. Thx.

#3884

greybeard

⇗ @infuscomus
Ok, I placed storahci.reg in the installation folder and the installation script still refused to copy it during the "copying files" phase. I pressed the ESC key to continue.
The installation proceeded normally until it crashed during the "installing devices" phase - Stop 0xD1.
Have any ideas what its trying to tell me?

#3885 | greybeard | ⇗ @diderius6 I disabled everything in the BIOS except SATA, as you suggested - that's a lot of options. I booted into XP to continue the installation. It crashed again while "installing devices" with a Stop: 0xc5 (0xB80187, 0x2, 0x1, 0x8087A5A1). Any other ideas?

## Page 260

#3886 | infuscomus | ⇗ @greybeard try restarting the installation from textmode setup, reformat the drive, something might not have been copied over correctly.
#3887 | diderius6 | ⇗ @greybeard Hit F8 and chose "Safe Boot" before the last start from installing XP before BSOD Dietmar

#3888

gordo999

> Zitat von ⇗ greybeard im Beitrag ¶ #3885

> It crashed again while "installing devices" with a Stop: 0xc5 (0xB80187, 0x2, 0x1, 0x8087A5A1). Any other ideas?

⇗ @greybeard ...an 0xC5 bsod is related to a hard drive error, memory error, or driver error. In this case, it's likely a driver error...a bad driver or one that doesn't work with your system.
Nirsoft has a free blue screen interpreter that will examine the bsod minidump file and advise which driver faulted. I have not used it but you may need to get access to your minidump files from another computer to use it.
⇗ https://www.nirsoft.net/utils/blue_screen_view.html
Loading devices means the installer is loading device drivers. It it's trying to load a driver into a memory space that is already assigned, or isn't available, that could give you the 0xC5 error. You might try a memory test although Windows usually runs one first. Also, do a chkdsk /f from another OS with your disk attached. Do you have a pagefile installed or are you trying to run off straight RAM memory? I am wondering as well whether you are using a modded PAE kernel/HAL. If so, with memory intensive driver loading, maybe more memory is being allocated than what you have. Remember, the mods on this site are experimental in nature. I don't think anyone has claimed each mod will work for every machine.

#3889

greybeard

⇗ @gordo999
Yep, I understand - nothing's guaranteed. I'm just happy that I found this site. Hell, 20 years ago (hmmm, make that 30) I would have joined it the fun. My mind doesn't work that well anymore.
But no, I'm not using any hacked HAL's or anything like that. Just trying to get std WinXP SP3 installed on this Ryzen box. I"m amazed, actually, that you guys have been able to get me this far.
I will try check out that mini dump viewer and see what it tells me.
Thanx!

#3890 | YuriyCN | Please, help me. I need USB 3.0 driver for Intel H110M (100-series) chipset. HardwareID= VEN_8086&DEV_A12F Please give URL where to download working driver for Windows XP (32-bit)?
#3891 | diderius6 | ⇗ @YuriyCN ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128) Dietmar

#3892

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #3891

> Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128)

Thanks you!
I did not understand how to install this driver, since I have a other DEV_ID.
Next, should I edit the amdxhc.inf and replace the ID code
%INTELXHC.DeviceDesc% = AMDXHC, PCI\VEN_8086&CC_0C0330
on the ID codes my USB device
%INTELXHC.DeviceDesc% = AMDXHC, PCI\VEN_8086&DEV_A12F
It is right?

#3893 | dencorso | Yes, it is. CC_0C0330 is a class code, meaning any USB 3.0, whatever the DEV code.

#3894

gordo999

> Zitat von ⇗ greybeard im Beitrag ¶ #3889

> Just trying to get std WinXP SP3 installed on this Ryzen box. I"m amazed, actually, that you guys have been able to get me this far

⇗ @greybeard ...I got XP going initially on my Asus B360M 300-series mobo by using the unofficial SP4 upgrade. Be careful if you use it, however. If you don't have a running copy of XP, it requires you to create an integrated (slipstreamed) install disk using your XP install disk and the SP4 upgrade.
I had a disk with XP SP3 already installed and I tried to do a repair install by running the integrated disk till windows starts and you are presented with the choice to install a clean XP version or do an in-place (repair) install. At that point, with the SP4 upgrade integrated disk, you are presented with only two choices (no option to go to a prompt), one of them a clean install and the other an install leaving the files and system alone. I selected the latter, presuming that was a repair install but it wasn't, it actually installed another edition of XP. I did not think you could do that but with my windows directory called WinXP it created a new windows directory called Winxp.0.
Confused the heck out of me at first but once I clued in I realized I had two working versions of XP on the same partition that could be selected at the boot menu (by manipulating boot.ini) and booted independently. I could have had 3 or 4 if I'd wanted to. They all work perfectly fine, except the SP4 version is barebones and lacks the installed files you have on your main installation. It did not solve problems like the LAN and USB3 functionality and I am currently working on finding a way to get a LAN driver working. I could use a plugin card but, hey, that would be cheating. Already did that with my USB ports. :-)
The only reason I mention this upgrade, unofficial or not, is that it got me going. I was stuck trying to insert drivers like the ACPI and iaStor SATA drivers because I was not up to speed on what the guys were doing here. The slipstreamed SP4 upgrade disk managed to bypass all those errors and get XP running on my 300-series mobo. Since then, I have learned how to add the modded ACPI and iaStor drivers from this forum to my initial XP installation, got it running, and even got it activated.
It was helpful to flip back and forth between my original install and the new SP4 install, especially comparing registry entries. Here's a link to instructions for acquiring and integrating SP4 using ntlite. Be careful, if using ntlite, that it is an XP version and running on an xp compatible OS. You can use XP installed in a VM to do the integration but running ntlite on W7 or 10 won't create a slipstreamed disk that works..
⇗ https://ryanvm.net/forum/viewtopic.php?t=10609⇗ https://ryanvm.net/forum/viewtopic.php?t=10609

#3895 | YuriyCN | I installed the driver AMDXHCI_XP_FINAL.rar. Unfortunately, I got error code 10 for the "Intel USB3.1 extensible host controller". My motherboard - Gigabyte GA-H110M-DS2 ⇗ https://www.gigabyte.com/Motherboard/GA-H110M-DS2-rev-10#ov Why did I get an error?
#3896 | diderius6 | ⇗ @YuriyCN Have you set in Bios USB3 "enabled" Dietmar

#3897

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3895

> ...I got error code 10 for the "Intel USB3.1 extensible host controller"....Why did I get an error?

⇗ @YuriyCN ...Error code 10 is a general and normal error for an XHCI, or any other controller in Device Manager when the driver cannot be loaded. No one can tell you why it happened. The guys in the forum are working hard to find out why but there are not always answers for every motherboard chipsets. You may have an Intel chipset but Gigabyte may have implemented it differently. Read the recent post by daniel_k on modifying PCI settings. Also, look into buying a PCIe USB3 add-on card for Win 7 and try to find XP drivers for it. I did that with a VIA chipset on an add-on card. Now it works on both W7 and XP.

#3898 | XPWELL64 | Patching a dsdt.aml is better.

#3899

YuriyCN

diderius6

> Zitat

> Have you set in Bios USB3 "enabled"

When installing Windows 7 with Intel USB 3.0 driver v5.0.4.43 - USB ports work fine!
But, I need to work USB on Windows XP.
Photo BIOS-UEFI.

#3900 | Andalu | ⇗ @YuriyCN try to set "xhci hand-off" on disabled

## Page 261

#3901

Andalu

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #3898

> Patching a dsdt.aml is better.

It would be even better if you could explain "how to do"

#3902

greybeard

⇗ @gordo999
Thx for the detailed reply.
I'm actually making some progress. I thought I could do this while working on my "day job" but decided to give this my undivided attention. Started over with a clean SP3 installation disk and carefully walked through the installation of acpi, storport, and storachi drivers until I actually got to the XP desktop! Yay!!!
But I don't have any USB (mouse) support and have a bunch of yellow warnings in Device Manager complaining about uninstalled drivers. So far, very attempt to add USB drivers has crashed the system with various BSOD's, depending upon the specific driver. Since many have already solved this problem, I'm gonna assume it's a hardware problem on my end (BIOS, chipset, etc.)
I'll give this a serious effort this weekend and let you know how it goes. I'll figure it out - it's just a bleeping computer ...

#3903

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #3900

> try to set "xhci hand-off" on [I]disabled/I]

I set "xhci hand-off" to disabled - no result.

> Zitat

> Legacy USB Support --- > Enabled
> XHCI Hand-off --- > Disabled
> Port 60/64 Emulation --- > Enabled
> USB Mass Storage Driver Support --- > Enabled

Next ... I tried to set all the settings to disabled.

> Zitat

> Legacy USB Support --- > Disabled
> XHCI Hand-off --- > Disabled
> Port 60/64 Emulation --- > Disabled
> USB Mass Storage Driver Support --- > Disabled

Unfortunately,USB does not work, code 10.
Maybe for this driver needs a special USBD.SYS??

#3904 | diderius6 | ⇗ @YuriyCN Set Port 60/64 Emulation --- > Disabled all other USB to enabled Dietmar
#3905 | kukonosau | ⇗ @diderius6 Do you have ACPI for XP 64-bit in Ryzen 3 2200G? Do you have 1050 Ti drivers or Vega 8 drivers?
#3906 | diderius6 | ⇗ @kukonosau Only the acpi.sys here in the forum I have. Most newer compis are unstable under XP 64 SP2 but absolut stable for XP SP3. There are no graphics driver for XP for the 1050 and above card Dietmar
#3907 | kukonosau | Ok. But where is last version ACPI for XP 64-bit? Under Vega 8 graphics also absent drivers? This is integrated cards into processors Ryzen 3 2200G.
#3908 | infuscomus | ⇗ @YuriyCN check if USBD.SYS is in your C:\Windows\System32\driver folder if not copy it across.
#3909 | infuscomus | ⇗ @kukonosau no driver for 2200G Vega 8 graphics for XP are you able to install another separate graphics card?
#3910 | kukonosau | Only GT 710((( 1050 Ti and Vega 8 cannot.

#3911

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #3904

> @YuriyCN
> Set Port 60/64 Emulation --- > Disabled
> all other USB to enabled
> Dietmar

I tried your variant.
Moreover, I tried all 16 variants "Enabled / Disabled" for 4 settings.
AMDXHCI_XP_FINAL.rar driver does not work.
Anyway, error code 10.

#3912

greybeard

> Zitat von ⇗ diderius6 im Beitrag ¶ #3906

> @kukonosau
> Only the acpi.sys here in the forum I have.
> Most newer compis are unstable under XP 64 SP2 but absolut stable for XP SP3.
> There are no graphics driver for XP for the 1050 and above card
> Dietmar

⇗ @diderius6
Whoa! Does that mean that XP64 is unstable for Ryzen2? I'm running a Ryzen 5 2600 on an x370 box and really need XP64 SP2 to work. My plan was to get XP32 to work, just to make sure I understood the process, then switch over to XP64.
Is this a bad plan?

#3913

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #3908

> @YuriyCN
> check if USBD.SYS is in your C:\Windows\System32\driver folder
> if not copy it across.

\driver - no find this folder
\drivers - !!!
After installing the driver, usbd.sys appears in C:\Windows\System32\drivers folder.
See screenshot.
My usbd.sys uploaded here.
YuriyCN has attached files to this post

- ⇗ usbd.zip

#3914 | kukonosau | From post #958 files USBXPSP1.rar copy into system32, and after AMD USB 3.1 drivers v1.0.5.3 WHQL.rar install drivers with device manager.

#3915

infuscomus

⇗ @YuriyCN
I noticed that some files like usbport.sys and usbstor.sys are missing from your C:\Windows\System32\Drivers folder
I have attached a zip of them for you - extract into C:\Windows\System32\Drivers
infuscomus has attached files to this post

- ⇗ usbfiles.zip

## Page 262

#3916 | infuscomus | ⇗ @greybeard XP64 is a real pain in the butt, if you absolutely need to use 64-bit software it's best to use windows 7, much more stable. XP32 is stable on Ryzen with generic AHCI driver patched ACPI driver - I've gotten it working on my ASRock AB350 Gaming K4 with a Ryzen 2700X.
#3917 | greybeard | ⇗ @infuscomus Ok, thanx for that. I was afraid that was what he meant. Damn! Well, I'm gonna give it my undivided attention this weekend and determine a path forward. Sometimes I just hate computers ... On another note, do you have any idea how I can get USB drivers to work in Windows Server 2008? I can get that to install cleanly, right out of the box, but without USB (mouse) support.

#3918

infuscomus

⇗ @greybeard
for AMD Ryzen you can try fernandos driver
32/64bit AMD USB 3.1 Controller and Hub Drivers v1.0.5.3 WHQL
thread:
⇗ USB 3.0/3.1 Drivers (original and modded)
direct link:
⇗ https://www.win-unattended.de/Benutzer/F....5.3%20WHQL.rar

#3919 | greybeard | ⇗ @infuscomus Ok, will do! Thx.

#3920

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #3915

> @YuriyCN
> I noticed that some files like usbport.sys and usbstor.sys are missing from your C:\Windows\System32\Drivers folder
> I have attached a zip of them for you - extract into C:\Windows\System32\Drivers

I unpacked these files into C:\Windows\System32\Drivers folder.
But still, the driver does not work. Error code 10.
What else do I need to do?
kukonosau

> Zitat

> From post #958 files USBXPSP1.rar copy into system32, and after AMD USB 3.1 drivers v1.0.5.3 WHQL.rar install drivers with device manager.

AMD USB 3.1 drivers v1.0.5.3 - This driver not installed through the device manager.
The driver does not contain my hardware ID. It contains AMD codes only.
Are you sure that AMD driver can work on Intel chipset?
My motherboard - Gigabyte GA-H110M-DS2 with Intel H110M chipset
⇗ https://www.gigabyte.com/Motherboard/GA-H110M-DS2-rev-10#ov
My hardware ID = VEN_8086&DEV_A12F

#3921 | infuscomus | ⇗ @YuriyCN now that you have those files placed in the drivers folder try reinstalling the USB 3.0 driver in device manager

#3922

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #3921

> @YuriyCN
> now that you have those files placed in the drivers folder try reinstalling the USB 3.0 driver in device manager

I did so. Does not work.
Are you sure that AMD driver can work on Intel chipset?
These are different manufacturers.

#3923 | infuscomus | ⇗ @YuriyCN you should use the modded AMD driver made by daniel_k, this has been confirmed to work for intel USB 3.0 if your using ACPI you should use the modded ACPI driver too.

#3924

IntiMD

> Zitat von ⇗ greybeard im Beitrag ¶ #3917

> On another note, do you have any idea how I can get USB drivers to work in Windows Server 2008? I can get that to install cleanly, right out of the box, but without USB (mouse) support.

Give these a try, also from daniel_k: ⇗ https://msfn.org/board/topic/180769-inte...s-vista-x86x64/

#3925

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #3923

> @YuriyCN
> you should use the modded AMD driver made by daniel_k, this has been confirmed to work for intel USB 3.0
> if your using ACPI you should use the modded ACPI driver too.

For intel USB 3.0 to work, I additionally have to install modded ACPI driver?
Without modification of ACPI the USB 3.0 driver will not work?
Tell me, what else should I do?

#3926

gordo999

> Zitat von ⇗ greybeard im Beitrag ¶ #3902

> But I don't have any USB (mouse) support and have a bunch of yellow warnings in Device Manager

⇗ @greybeard ...that was anticipated, it's why I suggested having a PS/2 mouse/kbd standing by. If you're desperate for USB functionality, buy a peripheral USB card that has XP drivers available. I bought one with a VIA chipset and found XP drivers on a Czech site. Or try the USB driver from this site. It has not worked on my Asus B360M but I have not tested the most recent version of the driver.
The unofficial SP4 upgrade took care of a lot of the yellow question marks in DM but some of them are not important unless you really need XP running in pristine condition. I only want to use XP for specific applications. I think W7 is the best all-round Windows OS available.
XP is still a good OS but it was a hybrid between 16 bit and 32 bit apps and I found it could freeze or BSOD often with apps not written correctly. It was meant to be backward compatible with W98 and W95. When I first got my 300-series mobo I was told to forget running W7 on it. Much to my surprise, once I got the PS/2 mouse/kbd running, W7 went straight to the desktop on stock drivers on an existing installation on a SATA drive. I was even able to get stable 1920 x 1080 resolution on a super VGA driver from the stock installation. Since then, I have loaded the free W10 OS but I prefer the W7 installation. I had it in mind that XP would be a lot of trouble to get going on the 300-series but it has surprised me how stable it is once the correct drivers are loaded. In that respect, it's a good OS, so why abandon it?
I'll use XP, depending on what I am doing. Some games run only on XP and I have my full Creative XFi card functional on the current install on the 300-series board as well as my NVidia GT 370 video card.

#3927

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3925

> For intel USB 3.0 to work, I additionally have to install modded ACPI driver?
> Without modification of ACPI the USB 3.0 driver will not work?

⇗ @YuriyCN ...without ACPI you cannot get XP to run never mind the USB drivers. Read through the entire thread from the beginning to see what is involved. You don't have to read every post but pick out the parts you need. In fact, research ACPI to see what it is and why it is required.

#3928

YuriyCN

> Zitat von ⇗ gordo999 im Beitrag ¶ #3927

> without ACPI you cannot get XP to run never mind the USB drivers.

I had BSOD through ACPI, when I had a fall loading Windows XP on the new F20, F21, F22 version UEFI (BIOS). After I downgraded UEFI (BIOS) to version F3, I have no ACPI problems. My Windows XP is loaded without ACPI patches.
Tell me which file you need to modify for ACPI on Windows XP SP3. I do not read English well, I use Google translator.

#3929

greybeard

⇗ @gordo999
Thanx for the help. But I really want to use XP64 for what I'm trying to do.
So with that in mind, I went back to my Windows Server 2008 alternative. It took me all day, but I finally got all the drivers sorted out, and was able to install my backup application. So with the platform issue resolved, it's just about installing applications, validating stability & performance, and configuring things to my liking. It's gonna be a fun 2 weeks.
You guys have been a tremendous help, and I really appreciate it. Nice to find a board with real talent that's willing to help newbies like me. Kinds reminds me of the good old days (80's and 90's) when the industry was young and we were all trying to figure it out. Since I'm back in "technology mode" through the end of the year, I'm willing to help out if I can. My days as a programmer and bit twiddler are over but I'm more than willing to test things for you. Just let me know.
Again, thanx a bunch.

#3930

diderius6

⇗ @YuriyCN
May be, that during downgrade Bios something went wrong.
It is not easy to do this, as they told on the side from Gigabyte.
So, flash newest Bios for your board, add modified acpi.sys
and USB3 will work
Dietmar

## Page 263

#3931

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #3930

> @YuriyCN
> May be, that during downgrade Bios something went wrong.
> It is not easy to do this, as they told on the side from Gigabyte.
> So, flash newest Bios for your board, add modified acpi.sys
> and USB3 will work
> Dietmar

The BIOS (UEFI) version is downgraded via FPT (Flash Programming Tool).
With FPT you can replace any version BIOS with any version BIOS.
Please, give a URL to download modified acpi.sys for Windows XP SP3
and my motherboard Gigabyte GA-H110M-DS2.

#3932

diderius6

⇗ @YuriyCN
This is best acpi.sys until now for XP SP3 based on 5048 vers.
Dietmar
diderius6 has attached files to this post

- ⇗ acpi.rar

#3933 | XPWELL64 | I hate acpi.sys. I'll use ⇗ @Mov AX, 0xDEAD's DSDT patcher at boot time.
#3934 | infuscomus | ⇗ @XPWELL64 why do you hate acpi.sys?

#3935

YuriyCN

For successful installation of AMD USB 3.0 driver on Intel motherboard it is necessary to replace the modified ACPI.SYS. With the original ACPI.SYS you will have an error code 10.
Windows XP SP3 (32-bit)
Motherboard Gigabyte GA-H110M-DS2 (USB 3.0, DDR4, Socket 1151)
Chipset = Intel H110M (100-series)
HardwareID= VEN_8086&DEV_A12F
Mod acpi.rar- ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (263)
Driver - AMDXHCI_XP_FINAL.rar ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128)
The USB 3.0 port is already working!!!
Thank you all!

#3936

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3935

> The USB 3.0 port is already working!!!@Thank you all!

YuriyCN ...did you bother to read the title of the thread...'Windows XP32-bit and Server 2003 32-bit on Modern Hardware'? Your chipset came out in early 2017 and it is Skylake compatible. That is NOT what is meant by modern hardware. We know USB works on the Skylake series (200-series...yours is 100-series) in W7 and Intel was likely supplying XP drivers in 2017.
When I first saw your post you were asking us to do everything for you. I was going to ignore you but since Diderius tried to help you I tried to help too. Next time someone shows up asking dumb question, having obviously done no research on their own, I am going to ignore them. In other forums in which I have participated, that has been a requirement, that posters do their own research to show they are trying to learn rather than just leeching the work of others, or asking to have their hand held. It's not my business how things are done at win-raid, so I have nothing to say about it other than I won't be trying to help anyone asking dumb questions, when it's obvious they have taken no time to understand what they are asking.
Besides, I got caught with that one. I should have seen that the chipset was a 100-series and guessed it was at least 3 years old.

#3937

bcwinit

Wow. This gordo999 post is an absolute gem. I felt obligated to register just to comment a bit.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3936

> YuriyCN ...did you bother to read the title of the thread...'Windows XP32-bit and Server 2003 32-bit on Modern Hardware'? Your chipset came out in early 2017 and it is Skylake compatible. That is NOT what is meant by modern hardware. We know USB works on the Skylake series (200-series...yours is 100-series) in W7 and Intel was likely supplying XP drivers in 2017.

USB 3.0 drivers were NEVER provided by Intel for XP. Intel's Sandy Bridge boards had a NEC/Renesas chip on the board, and that supported XP, but once USB 3.0 support was added to the chipset (starting with Ivy Bridge) there weren't any drivers that could be used for USB 3.0 in XP/2003 for Intel-chipset boards without also using a third-party controller.
Additionally, Intel's driver support in general for XP/2003 ceased after Ivy Bridge. There was an early Haswell graphics driver but that's about it as far as I know. Unofficially the AHCI driver can be used with a modified INF on later hardware. In general though anything after Ivy Bridge is most definitely "modern" (not officially supported) as far as XP and 2003 are concerned.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3936

> When I first saw your post you were asking us to do everything for you. I was going to ignore you but since Diderius tried to help you I tried to help too. Next time someone shows up asking dumb question, having obviously done no research on their own, I am going to ignore them. In other forums in which I have participated, that has been a requirement, that posters do their own research to show they are trying to learn rather than just leeching the work of others, or asking to have their hand held. It's not my business how things are done at win-raid, so I have nothing to say about it other than I won't be trying to help anyone asking dumb questions, when it's obvious they have taken no time to understand what they are asking.

Despicable, unforgivable behavior. The posts about USB 3.0 support for Intel hardware are scattered throughout this thread. That YuriyCN even found this thread at all shows that some research was done before posting. Some posts in this thread mention the additional need for a modified acpi.sys, but a lot of them don't mention it at all. Assuming that everyone can sift through thousands of posts, especially if their first language isn't English, to maybe piece together some useful info is not reasonable at all.
YuriyCN asked for help, misunderstood the requirements, came to understand the requirements with the help of responses in the thread, and then kindly and politely posted a thank you message with links to what worked for them. You responded to that by insulting YuriyCN for "asking dumb questions" and complaining while spewing completely false info about Intel driver support in XP/2003.
What YuriyCN wanted help with is very important for XP/2003 users with Intel USB 3.0 controllers on ANY generation of hardware. Since that information is buried in this thread it's very, very normal and helpful to have that information resurface closer to the most recent posts. This is especially true since older posts have solutions that may work but aren't the latest/best ones currently available.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3936

> Besides, I got caught with that one. I should have seen that the chipset was a 100-series and guessed it was at least 3 years old.

Oh, heaven forbid, a chipset from three years ago. Here was me thinking this was a forum friendly to users of both "old" software and "old" hardware and you seem like you'd be happy with a ban on discussions about anything that's what, more than two years old, one year old, three seconds old?
To YuriyCN: Please don't be afraid to ask questions. Please do feel free to try daniel_k's recently released, much newer (but still beta) modified AMD XHCI driver:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (256)

#3938

YuriyCN

> Zitat von ⇗ gordo999 im Beitrag ¶ #3936

> > Zitat von ⇗ YuriyCN im Beitrag ¶ #3935

> > The USB 3.0 port is already working!!!@Thank you all!

> YuriyCN ...did you bother to read the title of the thread...'Windows XP32-bit and Server 2003 32-bit on Modern Hardware'? Your chipset came out in early 2017 and it is Skylake compatible. That is NOT what is meant by modern hardware. We know USB works on the Skylake series (200-series...yours is 100-series) in W7 and Intel was likely supplying XP drivers in 2017.

You write nonsense. Officially, Intel released drivers for the 75th chipset and older.
For the 80-, 90-, 100-, 200- series, the Intel driver did not exist. I read the forum for a long time.
It was not written that in addition to USB 3.0 you need to install a modified file ACPI.SYS.

#3939

hardware-prefetcher

First: Install the old version of bios mbr win7 BSOD on the lenovo xiaoxin air14 laptop: . Here are the BIOS settings for installing WIN7: .
lenovoxiaoxin air14 laptop hardware:
I download the thread ¶ #3932 acpi attachment and extract it.The thread¶ #3932 acpi.sys overrides the acpi.sys that comes with WIN7,Can WIN7 0x000000A5 BSOD ERRORS be resolved? Notebook is not in my hand now.
Second: If the modified ACPI.sys cannot resolve the WIN7 0x000000A5 error, then what tool do you use to modify ACPI.sys, and where can you modify it to resolve the WIN7 0x000000A5 BSOD? Please give me directions and I will share the results with you if the problem is solved.
WIN7 is still a popular operating system. In the future, you may use WIN7 on hardware around 2019. You will also encounter WIN7 0x000000A5 BSOD. Forum members work together to solve this problem and resist Intel Microsoft. Good luck!

#3940

IntiMD

⇗ @hardware-prefetcher This ACPI.sys mod is destined only for XP/Server 2003 systems only, not for Windows 7, due to their architectural differences they can't be compatible + it might be a pain in the ass to modify it so as to not trip the driver signature enforcement, especially since it's a system file. I recommend creating a separate thread about your problem in the Windows 7 subsection on this forum for more visibility. I'm sure the experts here will be able to help you with that problem (especially canonkong, due to his hard work with the drivers for new AMD devices).
For that Win7 problem of yours with the Ryzen APUs, you have to keep in mind that not all mobos with the Ryzen APUS will work (hope for your sake that it's not the case, or if it is: it can be circumvented), there may be a BIOS update that might solve the BSOD problem amongst other general issues (doesn't need to be mentioned), though i'm not sure that Lenovo would offer that for your laptop, especially since the only drivers that it offers is for Windows 10. (have checked it in the support page of your laptop in lenovo's chinese website).
If you eventually get this to work, I recommend that you install canonkong's package with the APU video + chipset drivers found ⇗ here (use this link from "Driver package download link that can be integrated into the original WIN7 image")

#3941

gordo999

> Zitat von ⇗ bcwinit im Beitrag ¶ #3937

> Despicable, unforgivable behavior. The posts about USB 3.0 support for Intel hardware are scattered throughout this thread.

⇗ @bcwinit ...you seem rather naive as to how technical blogs operate. You have people on here doing cutting edge work to discover how to run XP on newer 300+ series mobos and other people interacting with them trying to understand what they are doing and how to do it themselves. To a man, or woman, since I joined this forum, people trying to learn are doing their own work and being graciously helped by the experts freely with very helpful information. Then someone shows up, almost demanding that the experts do the work for him.
It doesn't work that way. On many technical sites, you won't even get an answer if you show up asking for drivers and immediate solutions, yet one of the experts, diderius, took the time to try to help this guy. In the end, the person in question seemed to scoff that his system does not need USB drivers hence an acpi driver. That's when I clued in that he was not using a motherboard that had the requirements of this forum. I should have clued in immediately since it was a 100-series mobo but I missed it. Maybe he did not want to appear demanding but he should have known that one line requests, when translated into another language, can sound that way.
I belonged to a reversing forum where people would enrol simply to ask for cracks and serials, which is illegal. They were politely told to go do research to demonstrate their understanding of the issue. Others had better intentions but they essentially were asking more experienced reversers to do the work for them. Again, they were politely asked to do further research so they could pose a question that demonstrated they were in the process of learning. I answered YuriyCN twice trying to help him understand and I was very polite. However, the questions he was asking were naive and contradictory. He was complaining that the ACPI driver from this forum was crashing his system then complaining that the USB driver was failing with a code 10 error. Again, I tried to explain politely what a code10 error meant.
YuriyCN did not ask for help that would show he is doing his own work. His first post asked for a link to a driver. When I joined this forum, I started at the beginning of the thread to see what problems were involved and I began reading page by page to gain an understanding of the issue. By the time I started to ask questions, I had a good idea of the issues and I was also reading current posts. So, I had a good idea of when the drivers were being posted. It's easy for me here because I speak English but I have done the same on Russian sites where everything was in Russian. I not only had to translate from Russian I had to further translate the unique meanings Russians give to literal translations of English. In that vernacular, a disk drive becomes a 'screw' and a disk platter becomes a 'pancake'.
I know all about communicating on a site where my language is not the primary language and there are techniques you can use via translators like Google to reasonably ensure your interpretation will be received with some clarity. There are guys on this forum whose native language is German and the forum originates in Germany. There is at least one guy whose native language is Italian. They all manage to communicate effectively and not one of them has ever asked, in my experience, for a link to a driver. All of them are doing their own work to an in-depth level. BTW...my native language is Scottish, a language which translators find almost impossible to decipher. So, lighten up, will you?

> Zitat von ⇗ bcwinit im Beitrag ¶ #3937

> What YuriyCN wanted help with is very important for XP/2003 users with Intel USB 3.0 controllers on ANY generation of hardware.

Maybe so, but he failed to communicate that. Instead, he started by asking pointed questions as to whether people could help him with specific issues that did not apply to his particular chipset. The owner of the forum, Fernando, has come along several times and redirected posts that were not pertinent to the forum to other forums where there might be answers. Therefore, I presume there is a precedent for such an action.
The issues involved in getting XP working on a 300+ series chipset are much different than getting USB 3 drivers to run on any version of any chipset. I know for a fact that Intel recognized early chipsets such as Skylake because it says so right in their setup.exe file. I traced it and I saw the reference to Skylake. In other words, Intel offered x86 drivers for chipsets that were Skylake and before. I also know from reading their release notes that those drivers would run on XP x86 systems.

> Zitat von ⇗ bcwinit im Beitrag ¶ #3937

> Oh, heaven forbid, a chipset from three years ago. Here was me thinking this was a forum friendly to users of both "old" software and "old" hardware and you seem like you'd be happy with a ban on discussions about anything that's what, more than two years old, one year old, three seconds old?

The policies on this forum are none of my businiess and it's obvious that Fernando has offered valuable information that applies to old software and hardware. Furthermore, I have no interest in banning anything, nor could I. I have never been able to stand certain individuals who have tried to take over forums, especially in the newgroups.
You have obviously completely misunderstood my post. I got PO'd because I was politely trying to help the guy in question, thinking he had a legitimate problem adapting XP to a 300+ series chipset, when in fact, he was in the wrong forum. Even at that, I would not have gotten upset had he not so frivolously disappeared with the claim that his stock ACPI was working fine as was his USB. What????? His ACPI and USB suddenly began working on a 300+ series chipset? That's when I looked up his chipset and found it was a 100 series that would operate with drivers up to Skylake.
I wish it was that easy with 300+ series chipsets. I am currently looking at a LAN driver for XP on a 300-series chipset that has 30 exports missing in ndis.sys, the networking interface.

#3942

bcwinit

Another gem. Thanks for doubling down on what made your previous post so disappointing. I love reading this forum and your disdain for others is quite a shame. Also thank you for assuming you have any idea who I am or what my background is.
My favorite bit was probably this:

> Zitat von ⇗ gordo999 im Beitrag ¶ #3941

> I know for a fact that Intel recognized early [USB 3.0] chipsets such as Skylake because it says so right in their setup.exe file. I traced it and I saw the reference to Skylake. In other words, Intel offered x86 drivers for chipsets that were Skylake and before. I also know from reading their release notes that those drivers would run on XP x86 systems

You're still claiming that Intel released USB 3.0 drivers that worked on XP for many chipsets. XP users have been desperate for years for an XHCI driver for Intel chipsets starting with Ivy Bridge and you're acting as if they just weren't bothering to use the ones available. The (brilliantly) modified AMD drivers and ability to use a Vista 5048 ahci.sys are such a big deal because they've made the dream a reality.
I won't waste my life away dissecting your latest post point-by-point just to get yet another junk response, and another, and another. Just be sure to keep posting claims that this is the "wrong forum" for discussion of any issue that isn't your personal 300+ series issue. That will help a lot. Also continue to rudely ignore the first post in this thread in which the OP states acceptable platform options:

> Zitat von ⇗ deSSy2724 im Beitrag ¶ #1

> It would be the best to build a PC based on the Skylake, Kaby Lake, Coffe Lake etc.

#3943

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3938

> @YuriyCN ....You write nonsense. Officially, Intel released drivers for the 75th chipset and older.
> For the 80-, 90-, 100-, 200- series, the Intel driver did not exist. I read the forum for a long time.
> It was not written that in addition to USB 3.0 you need to install a modified file ACPI.SYS.

This is what I wrote: "We know USB works on the Skylake series (200-series...yours is 100-series) in W7 and Intel was likely supplying XP drivers in 2017". I said 'likely'. The point I was trying to make is that 200-series chipsets and earlier were supported by Intel on W7 but not the 300+ series chipsets. I have already modded W7 to run in a very stable manner on a 300-series chipset with USB 3 using modded drivers by Canonkong.
Then I turned my attention to XP on the same 300+ series chipset. It was an entirely different situation. W7 on a SATA hard drive ran to the desktop on stock drivers using a PS/2 mouse/keyboard. I had it running in 1920 x 1080 using stock W7 drivers. With XP, the OS would not even start. The integrated XP SP3 installation disk could not see the OS and before it could load its drivers, I encountered an 0XA5 error. I got past it using an F7 at the F6 prompt asking for storage drivers, only to get an 0x7B when windows started. The modded ACPI driver worked fine for me and another one of Fernandos SATA controller drivers got rid of the 0x7B error.
I thought you were having similar problems but the manner in which you posed your questions was very abrupt with no explanation as to the real problem. I have had no problem understanding posts from people who speak German and Italian and I had no problem understanding your most recent post. So, why were you asking so many short questions without offering more information to explain your problem? You asked for a link to a modded ACPI driver then came back and said it did not work. Then you came back later and said your stock ACPI driver was working fine. I know one thing, if you have a stock ACPI driver that works on XP, on a 300+ series chipset, you are way ahead of the rest of us.
Maybe I have presumed too much in thinking that modern hardware means a 300+ series chipset. It does with W7 on a 'modern' chipset. Sometimes it's easy to confuse the requirements of W7 versus XP. There are exports missing in the XP ntoskrnl that won't allow W7 drivers to be substituted without modification but I do know that Intel supported USB 3 in W7 right up till Skylake, which is a 200-series chipset. Based on that information, I still don't understand what question you were asking. Why were you asking for a link to an ACPI driver when your stock ACPI driver was working and how did your USB suddenly start working? You disappeared with no explanation.

#3944

gordo999

> Zitat von ⇗ bcwinit im Beitrag ¶ #3942

> You're still claiming that Intel released USB 3.0 drivers that worked on XP for many chipsets.

⇗ @bcwinit ...and you are still misquoting me. I did not say at any time that Intel released USB 3 drivers for XP, I said they released x86 drivers that would work on XP. You don't seem to understand what XHCI drivers do, or the relationship between ACPI, PCI, XHCI and the older USB drivers. The XHCI standard is incorporated into some drivers with the older USB 2 driver. If the driver detects a USB 2 device, it uses that chain in the USB stack. If it detects USB 3, it brings in the XHCI driver.
I also admitted in another post that it's easy to confuse the requirements of XP with W7 when working on both systems concurrently. If I thought USB 3 would run on XP I'd have done it long ago and I would not be here wasting my time replying to a lurker who reads the thread and joins to take shots at me. The mistake I made was confusing 'modern chipsets' with only the 300-series mobo and above which is true for W7 but not XP. The W7 OS has USB 3 drivers that will run on certain 200 series chipsets and they were put out by Intel. Furthermore, Asus issues W7 drivers for certain Asus mobos that have chipsets where the manufacturer has its own driver.
I have a USB 3 add-on with a VIA chipset and I am running it in XP using drivers written for XP. So, don't tell me there are no XP drivers for USB 3 devices. There are certainly no USB 3 Windows drivers since Microsoft abandoned USB 3 on XP and W7. There are likely no XP drivers from Intel for modern mobos but that does not mean Intel X86 drivers won't run on certain XP machines. I did not claim those drivers run in USB 3 mode but the XHCI controller was designed to work in conjunction with the USB 2 drivers in the same driver.
As I said, the mistake I made was claiming the 100-series chipset ' using XP' was not part of a modern system. If I had thought there were XP drivers for the 100-series, why was I trying to help the guy with suggestions on ACPI drivers and USB drivers? If I thought there were XP drivers why did I not tell him where to find them? That was not my beef with him, it was simply the way the guy was bugging people to find him a driver then complaining when it did not work, using one liners. At no time did he try to explain his problem or what he was doing to fix it. He simply kept asking people to solve it for him. And please don't bring in language issues. As I said, I have communicated on Russian sites, in Russian, in detail, via Google translator, which is much better today than then. Furthermore, I had to figure out the extensive technical slang Russians use to describe our Western terminology.
Why you are jumping all over the issue is another question. Why have you not joined before and tried to contribute? You have claimed the ACPI driver is the root of the USB problem yet the guy in question now claims to have USB working with his stock ACPI driver. Have you asked him if it is running in USB 3 mode, or have you merely presumed that?

#3945

bcwinit

You really are determined to drag this on. This is unfortunate.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> ...and you are still misquoting me. I did not say at any time that Intel released USB 3 drivers for XP, I said they released x86 drivers that would work on XP."

A matter of semantics at best then. You're claiming they released them but didn't say that they released them. The exact quotes just for context:

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> Intel was likely supplying XP drivers in 2017

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> ...also know from reading their release notes that those drivers would run on XP x86 systems.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> You don't seem to understand what XHCI drivers do, or the relationship between ACPI, PCI, XHCI and the older USB drivers. The XHCI standard is incorporated into some drivers with the older USB 2 driver. If the driver detects a USB 2 device, it uses that chain in the USB stack. If it detects USB 3, it brings in the XHCI driver.

There you go again, assuming what you think I don't know. There's a whole lot in the world that I don't know, including plenty of fine details on this subject, but I'm also not utterly clueless about this subject.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> I also admitted in another post that it's easy to confuse the requirements of XP with W7 when working on both systems concurrently. If I thought USB 3 would run on XP I'd have done it long ago and I would not be here wasting my time replying to a lurker who reads the thread and joins to take shots at me. The mistake I made was confusing 'modern chipsets' with only the 300-series mobo and above which is true for W7 but not XP. The W7 OS has USB 3 drivers that will run on certain 200 series chipsets and they were put out by Intel. Furthermore, Asus issues W7 drivers for certain Asus mobos that have chipsets where the manufacturer has its own driver.

This is an improvement aside from the use of "lurker" as a derogatory term and the irrelevant info about Asus drivers for non-Intel onboard USB 3.0 controllers on a version of Windows outside the scope of this thread. You acknowledging that you were thinking Windows 7 while talking about XP and that you were at least somewhat detached from the reality of USB 3.0 driver support for XP is very much appreciated.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> I have a USB 3 add-on with a VIA chipset and I am running it in XP using drivers written for XP. So, don't tell me there are no XP drivers for USB 3 devices.

I explicitly stated that supported third-party controllers aren't a problem:

> Zitat von ⇗ bcwinit im Beitrag ¶ #3937

> ..there weren't any drivers that could be used for USB 3.0 in XP/2003 for Intel-chipset boards without also using a third-party controller

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> As I said, the mistake I made was claiming the 100-series chipset ' using XP' was not part of a modern system. If I had thought there were XP drivers for the 100-series, why was I trying to help the guy with suggestions on ACPI drivers and USB drivers? If I thought there were XP drivers why did I not tell him where to find them? That was not my beef with him, it was simply the way the guy was bugging people to find him a driver then complaining when it did not work, using one liners. At no time did he try to explain his problem or what he was doing to fix it. He simply kept asking people to solve it for him.

YuriyCN was pretty clear to me. The need for a modified acpi.sys was originally not realized. People say the modified AMD driver should work, it didn't, so why didn't it? Because the modified acpi.sys is also needed. Not nearly enough posts mention that both are required. The modified AMD drivers are very frequently mentioned in complete isolation from ACPI. That's fine for anyone who has been following the thread for months. That's far from ideal for others.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> And please don't bring in language issues. As I said, I have communicated on Russian sites, in Russian, in detail, via Google translator, which is much better today than then. Furthermore, I had to figure out the extensive technical slang Russians use to describe our Western terminology.

Since you brought it up again I'll help with this. You're assuming that your ability to communicate across language barriers via various means must be the same as everyone else. This is unrealistic. Also, as boastful as you are about your abilities in this area, you're still at a loss about some of YuriyCN's messages. Some do require some interpretation to make sense of. For example...

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> You have claimed the ACPI driver is the root of the USB problem yet the guy in question now claims to have USB working with his stock ACPI driver. Have you asked him if it is running in USB 3 mode, or have you merely presumed that?

YuriyCN ("the guy in the question") clearly, after interpretation, stated that the modified acpi.sys had to be used. This is YuriyCN explaining that they weren't having any success before when just using the modified AMD driver:

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3935

> With the original ACPI.SYS you will have an error code 10

This is where you seem to be getting lost:

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3935

> For successful installation of AMD USB 3.0 driver on Intel motherboard it is necessary to replace the modified ACPI.SYS

Every bit of context makes it clear that YuriyCN is saying here that it was necessary to replace the original acpi.sys with the modified acpi.sys. Reading the message literally is a dead-end due to a communication mishap. Reading the message in context the meaning is clear. For confirmation, see YuriyCN's next message which includes this:

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3938

> in addition to USB 3.0 you need to install a modified file ACPI.SYS

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> Why you are jumping all over the issue is another question.

From my perspective it's monumentally good fortune that anyone is dedicating the skill and time necessary to do things like modify drivers for free and for the public. Discouraging the use and appreciation of that work for any reason is not constructive. I felt like this subject was too important to ignore when you insulted YuriyCN after that user succeeded in putting modified drivers to good use.

> Zitat von ⇗ gordo999 im Beitrag ¶ #3944

> Why have you not joined before and tried to contribute?

A combination of having very little time to spare for more than perusing discussions and abysmally poor health that prevents me from regularly doing my own dev work and supporting users of that work. Engaging in support-related activities that are in any way related to the work of others isn't something I have the luxury of doing aside from exceptional situations like this.

## Page 264

#3946 | Fernando | Is this a battle or just a discussion? Please calm down!

#3947

daniel_k

Have been really busy.
Just a quick update: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (128)

> Zitat

> Updated the so called "FINAL DRIVER" with V2 (Dec 19, 2019):
> - revised device check patch
> - applied small bug fix to 32-bit (x86), as seen on newer 153 and later releases. 64-bit is not affected.

Regarding the latest version (276), I've finally managed to fix it, was driving me nuts. It's under final testing and should be released before Christmas.
PS: Please don't send me PM's requesting help. If needed, I contact you. Thanks!

#3948 | infuscomus | ⇗ @daniel_k is the latest version (276) when you release it only for use with intel USB 3.0?

#3949

kukonosau

⇗ @diderius6
Where is USB 3.0 drivers for 15E0, 15E1 for Windows XP x86? I have Ryzen 3 2200G platform. Where is chipset drivers? What is motherboard resources in device manager in system devices? Where is AMD PSP drivers? Also I have unknown device ACPI. How to send screenshots?
kukonosau has attached images to this post ⇗ Photo.PNG

#3950

YuriyCN

I have a trouble with an modified driver.
1. I replaced the file c:\WINDOWS\system32\drivers\acpi.sys with the file that was modified by you.
2. Then I installed the modified USB 3.0 driver through the Device Manager.
At first, after the OS is booted up, USB ports work fine.
Read speeds on USB 2.0 ports up to 40 MB/s, on USB 3.0 ports up to 110 MB/s.
Everything works fine and suits me.
But not for long! After a time (from 3 to 15 minutes), the ports stop working. It is very likely that the voltage was decreased on the ports, because when user inserts a USB flash drive, its LED does not light up. If to restart the computer at the moment, then it hangs toughly when shutting down - even the Reset button on the PC case does not work! Only a complete disconnection from the power supply helps.
My system is Windows XP Pro SP3.
Motherboard - Gigabyte GA-H110M-DS2 (Socket 1151, DDR4)
⇗ https://www.gigabyte.com/Motherboard/GA-H110M-DS2-rev-10#ov
Mouse and Keyboard - PS/2
Is it a problem with modified ACPI or modified USB 3.0?
Please help me.

#3951 | diderius6 | ⇗ @YuriyCN May be, that your USB3 device needs to much power. In this situation, the motherboard stops this USB device after some time. This you can test with an USB3 device with ultra low power consumption Dietmar

#3952

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #3951

> @YuriyCN
> May be, that your USB3 device needs to much power. In this situation, the motherboard stops this USB device after some time.
> This you can test with an USB3 device with ultra low power consumption
> Dietmar

Not. This is a simple flash drive.
The voltage is removed from all USB ports at the same time.
After 3-15 minutes, the USB ports stop working, even if nothing was connected to them.
Can you upload for me all versions of your modifications ACPI and USB drivers in one archive?
I want to try working in different combinations.

#3953

YuriyCN

I have done several experiments and now sending an updated information. A trouble with the stops of USB ports occurs more often if to boot the PC with a USB flash drive already inserted into the port. When one inserts/removes the USB flash drive in an already loaded system - stops happens 10 times less often.
To assurely receive a stops, user must boot a PC with a USB flash drive already inserted into the port. After OS is fully booted up (untill the desktop), you need to remove the USB flash drive and insert it into the neighboring port. In this case, the USB flash drive will be now incorrectly defined in the Device Manager as "Unknown device" with the ID code USB\VID_0000&PID_0000. At the same time, in 100% of cases I get a complete hang of USB interface. Altogether all ports freeze, that is, none of the 6 available USB ports works. When the USB port hangs, the voltage on it does not disappear. But the LED on the flash drive does not light up, since the flash drive is not defined as a device, although the voltage between the "1" and "4" pins of the USB connector - 5 Volt is present (measured with a voltmeter).
Checks were made on two different USB flash drives, connecting them to any of the 6 connectors. The situation is reproducible. My equipment is 100% operational. The problem is either in the USB driver you modified or in the ACPI.SYS file you modified. I ask for help.

#3954 | diderius6 | ⇗ @YuriyCN This behavior "Unknown device" happens on Intel motherboards only with the very first tries of making an USB3 driver for XP. It does not happen with newer USB3 driver for XP SP3 Dietmar

#3955

YuriyCN

> Zitat

> This behavior "Unknown device" happens on Intel motherboards only with the very first tries of making an USB3 driver for XP.
> It does not happen with newer USB3 driver for XP SP3

An "Unknown device" is displayed not for the USB port (Controller and Hub), but for a Flash Drive (or other device) connected to the port. A trouble with the freeze of USB ports occurs more often if to boot the PC with a USB flash drive already inserted into the port.
1) Please, look again at my previous message - it describes how to get this trouble.
2) Can you upload for me all versions of your modifications ACPI and USB drivers in one archive? I want to try working in different combinations this drivers.

#3956

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3950

> ....But not for long! After a time (from 3 to 15 minutes), the ports stop working...

⇗ @YuriyCN ...just a thought. In Device Manager, under the USB section, find the USB 3 hub driver and see if it has a Power Management tab under 'Properties'. If it does, see if it is set to allow the OS to turn off the device for power management. You might also check to see if the individual hub to which the device is connected has a power management feature. You might also look in your BIOS settings to see if the USB ports have power management features that can be turned on or off.
While you are checking the hub driver in Device Manager, under Properties, look under the Details tab. Scroll down to 'Power data' and see what power state is indicated for the device right after you boot then after it loses power. My current power state is set to D0, which means full power. If it is set to any other Dx state, where x = 1,2,3...it means the device has been set to a low power state.

#3957

YuriyCN

> Zitat von ⇗ gordo999 im Beitrag ¶ #3956

> > Zitat von ⇗ YuriyCN im Beitrag ¶ #3950

> > ....But not for long! After a time (from 3 to 15 minutes), the ports stop working...

> @YuriyCN ...just a thought. In Device Manager, under the USB section, find the USB 3 hub driver and see if it has a Power Management tab under 'Properties'. If it does, see if it is set to allow the OS to turn off the device for power management. You might also check to see if the individual hub to which the device is connected has a power management feature. You might also look in your BIOS settings to see if the USB ports have power management features that can be turned on or off.

Unfortunately this is not possible! In the modified driver, the "Power Management" tab is missing in the properties of "USB 3.0 Hub". I wrote earlier that the voltage in the port is not absent - the voltmeter shows 5 Volts. The LED on the USB flash drive does not light up not because of the absence of 5 Volts, but because of the freezing of the USB port.
diderius6
As a result, the main problem of the modified driver is the freezing of USB ports when Windows XP boots with a device already connected to the USB. Perhaps this is not an issue of the modified USB driver, but a complex problem (for the ACPI + USB bundle). Let me remind you that without installing the upgraded ACPI.SYS, I could not install the USB driver (an error occurred - code 10).
Please send me in one archive all the versions of USB and ACPI drivers that you have available. I want to experiment with installing these drivers in different combinations of versions.

#3958 | diderius6 | ⇗ @YuriyCN Look through this forum Dietmar
#3959 | daniel_k | ⇗ @YuriyCN, try to disable XHCI Hand-off in BIOS. It's the only suggestion I can give you. You are the first person to report this strange behavior.

#3960

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3948

> @daniel_k
> is the latest version (276) when you release it only for use with intel USB 3.0?

Don't have any modern AMD systems system, so can't test.
Anyway, the drivers are "unlocked", so one can try them with any XHCI controller, by editing the device ID in the INF file.

## Page 265

#3961

daniel_k

⇗ @canonkong, can you please sign this simple INF file? Needs a valid certificate for it to be (hopefully) accepted during Windows installation.
All it does is to disable NVME devices by installing a NULL driver. I want this to prevent Windows 8+ from touching my NVME drive and installing its own boot manager etc.
Thanks!

#3962

daniel_k

AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018
- Fixed XP/Server 2003 compatibility by re-adding PoStartNextPowerIrp calls, luckily the code didn't really change after build 145, could find all proper locations for every call. Interesting info:
⇗ PoStartNextPowerIrp - ⇗ Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
- Removed IoSetDevicePropertyData dependency, only found in Vista and later, doesn't affect functionality.
- Removed BCrypt functions dependencies (Ksecdd.sys), only found in Vista and later and re-added code from build 145.
- Combined hub and controller INFs into a single amdxhc.inf for easier installation and integration.

#3963

canonkong

⇗ @daniel_k
Try it.
SHA1 sign need run the reg file first.
canonkong has attached files to this post

- ⇗ NoNVME.zip

#3964

bcwinit

> Zitat von ⇗ diderius6 im Beitrag ¶ #3958

> @YuriyCN
> Look through this forum
> Dietmar

It's worth mentioning that daniel_k removed the links to the beta/experimental builds of the modified USB 3.0 drivers once the final versions were released. Looking through the forum will not allow anyone to find those alternate versions. I don't know how many there were in total, but there were at least two (AMDXHC_276_NO_USBD.rar and 276BETA.rar) for 1.1.0.0276 which was just updated to final a short while ago as AMDXHCI_XP_276_FINAL.rar.
daniel_k: Please let us know if it's acceptable for others to upload those beta versions as attachments in this thread and if so how you would like them described to prevent confusion with the final builds.

#3965 | daniel_k | ⇗ @bcwinit, the beta versions are really buggy so, as you've already said, to prevent confusion, don't upload them, please.

#3966

bcwinit

> Zitat von ⇗ daniel_k im Beitrag ¶ #3965

> the beta versions are really buggy so, as you've already said, to prevent confusion, don't upload them, please.

Understood. Thank you very much for the quick response.

#3967

Andalu

⇗ @daniel_k ⇗ @YuriyCN
I can confirm that issue. Booting with an USB3 disk inserted, the USB device is not recognized and displayed as 'unknown' in the device manager. Sometimes XP also hangs during boot; shutdown and restart don't work. I tried both XHCI_XP_FINAL_V2 and AMDXHCI_XP_276_FINAL with same results.
The issue disappears replacing 'amdxhc.sys' with the version included in the "¶ amdxhc_pae_fix.rar".

#3968

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #3967

> @daniel_k @YuriyCN
> I can confirm that issue. Booting with an USB3 disk inserted, the USB device is not recognized and displayed as 'unknown' in the device manager. Sometimes XP also hangs during boot; shutdown and restart don't work. I tried both XHCI_XP_FINAL_V2 and AMDXHCI_XP_276_FINAL with same results.

I get the same problem. I wrote the same thing.
The new driver (AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018) does not resolve the problem.

#3969

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #3967

> Booting with an USB3 disk inserted, the USB device is not recognized and displayed as 'unknown' in the device manager. Sometimes XP also hangs during boot; shutdown and restart don't work. I tried both XHCI_XP_FINAL_V2 and AMDXHCI_XP_276_FINAL with same results.

Cold boot (power on) or warm boot (restart)?
Don't have the issue here, but PAE is not enabled.
If my system would be affected by that issue, I wouldn't be able to install XP from an USB drive.

#3970 | daniel_k | ⇗ @canonkong, thanks! Didn't see you edited your message. Will try it. Any chance of signing it with SHA256? Forgot to ask that. Windows 8 accepts the SHA1 sign, Windows 8.1 and Windows 10 don't accept and just ignores the driver. Fixed some mistakes in the INF, please sign both files.

#3971

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #3969

> If my system would be affected by that issue.

Check several times...
Most often freezes when a USB Wi-Fi adapter is connected, but with a USB flash drive - is not always.

#3972

daniel_k

⇗ @YuriyCN and ⇗ @Andalu
My BIOS is patched with a XP friendly ACPI table.
With original ACPI.SYS 5512 SP3, no issues.
With beta modified ACPI.SYS 5048, no issues with USB drives, wi-fi dongle, keyboard and mouse. Cold boot (power on) and restart, no disconnections after 15 idle.
However, WiFi doesn't automatically connect with this ACPI.SYS, which is strange.

#3973

YuriyCN

My BIOS is not patched (original version F3).
With original ACPI.SYS 5512 SP3 - driver is not installed (error code 10).
With any other (modified ACPI.SYS) - driver is installed, but there are problems with booting Windows with USB3 device inserted and also when rebooting and turning off the PC.
The best, most stable driver with file "amdxhc_pae_fix.rar". There are no problems with this file when booting Windows. There were problems when rebooting or turning off the PC - but this rarely happens, maybe 1 time out of 10.

#3974 | infuscomus | ⇗ @YuriyCN So the pae_fix version solves the issue? Do you have the PAE patch applied? try removing it if you do.

#3975

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #3974

> @YuriyCN
> So the pae_fix version solves the issue?

Using file amdxhc_pae_fix.rar partially solves the issue, but not completely. At the moment, this is the best driver option.
I do not understand, why with the original ACPI.SYS I can not install the driver. The driver is normally installed only with the modified ACPI.SYS. Even if, after installing the driver, I return the original ACPI.SYS file back - then after booting Windows again I get a non-working USB.
Replacing the original file with a modified one removes this error. In this forum I found 3 different versions of the modified ACPI.SYS. Which is better to use?

## Page 266

#3976

canonkong

⇗ @daniel_k
Try it.
SHA1 also can work on win8.1/10, but you need run the reg file first.
canonkong has attached files to this post

- ⇗ NoNVME_2.zip

#3977 | YuriyCN | I use PAE patch, because in Windows XP SP3 x86 installed 8GB RAM. The driver with file amdxhc_pae_fix.rar - is much more stable!!! But when the USB port freezes, then see the screenshot.

#3978

Andalu

⇗ @daniel_k
I did some test with different configurations and the behavior can change from one to another.
I installed the same XP iso image from the same pendrive with the following driver/patch/files slipstreamed by nLite:
- Acpi.sys 5048 (SHA-1: 8EF48518B17DAAC4A90632A811FBFDC8183C325B);
- Universal 32bit Intel RST AHCI+RAID driver v11.2.0.1006 mod+signed by Fernando;
- NVME OFA driver 1.3;
- WinXPPae2 patch.
No USB3 driver added. In bios the devices not needed are disabled. Mouse connected to the ps/2 port during the setup. I chose the 'ACPI multiprocessor PC' option. The installation ends without errors for all my configurations.
For all usb3 driver versions, the 'AMD USB 3.0 Root HUB' and the 'Intel Extensible USB3.1 Host Controller' are correctly installed.
All the usb3/usb2 devices connected are recognized before a shutdown/restart. At first warm boot (restart), most of the time, even with the only mouse connected to the USB2 (or usb3 port), my pc hangs with a blank screen when the XP logo appears. Same behavior on a cold boot (power on) and so for the following shutdown/restart.
Other times, at first warm boot (restart) after installing the driver, even with the only mouse connected to the USB2 port, XP hangs as before but on the next cold boot (power on) XP boots normally also with the usb2 mouse connected but it is not recognized and considered as 'unknow device' in the device manager. The same for an external drive connected to the usb3 port.
In one case, I got the strangest behavior:
- on the first warm boot (restart) after installing the driver, XP hangs with the usb2 mouse as above;
- on the next cold boot (shutdown) XP boots correctly but the usb2 mouse doesn't work even it is powered (the led is always on); in the device manager the usb2 mouse is not listed;
- on the next warm boot (restart) XP boots correctly but the usb2 mouse doesn't work. It is listed in the device manager as unknow device but not powered. This time XP hangs on shutdown.
At moment, to have XP with USB3 and PAE features fully functional, I need to use a ps/2 mouse only and remember to disconnect any usb device before restarting or 'shutting down and turning on' the pc. For the boards without a ps/2 port I can use the amdxhci.sys from the amdxhc_pae_fix.rar packet. No issues with it in all my configurations. The restart and shutdown also worked correctly (the restart never worked only for the asrock B250-Pro4 that seems 'insensitive' to each driver tried).

#3979 | infuscomus | try removing the PAE patch? maybe that is causing problems
#3980 | daniel_k | ⇗ @canonkong, thank you very much! Now it worked with Windows 8.1 and Windows 10 1909! When I load this "null" driver, NVME drive disappears! The issue was the driver date, Windows seems to ignore version number.

#3981

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #3979

> try removing the PAE patch? maybe that is causing problems

This!
⇗ @YuriyCN and ⇗ @Andalu
If you had followed my discussion with ⇗ @Mov AX, 0xDEAD, you would be aware of all issues the AMDXHC driver causes when PAE is enabled.
The PAE patch works perfectly, but you must have drivers properly written to work with it, which isn't the case of the AMDXHC driver (even with PAE fix, there are many issues).
The AMDXHC driver works fine on 64-bit (x64) and 32-bit (x86) with PAE disabled.
If you really need PAE enabled, get a card with VIA VL805 controller (really cheap) or ASMedia ASM1142, ASM2142 or ASM3142 (more expensive).
Cards with TI and Fresco Logics also should work fine with PAE, but are not that easy to find.

#3982

daniel_k

Did some tests with the available Intel storage drivers to check which ones properly support Standby Immediate command, to avoid drive wear and data corruption when shutting down the computer. See this datasheet from Intel:
⇗ https://www.intel.com/content/dam/www/pu...ology-brief.pdf
This info is from Samsung:

> Zitat

> A count of the number of sudden power off cases. If there is a sudden power off, the firmware must recover all of the mapping and user data during the next power on. This is a count of the number of times this has happened.

To check if the unsafe shutdown happens with a particular driver, see if the SMART attribute with of these names increase, based on the controller's manufacturer:
- Samsung: "POR Recovery Count"
- Phison: "Unsafe Shutdown Count"
- Sandforce: "Unexpected Power Loss Count"
Only RSTe drivers 3.8.1.1006 and later, including my modded 4.7.0.1098 support the Standby Immediate command.
Storahci (from Skullteria) and iaStor (last for XP) don't support it.

#3983

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #3981

> If you had followed my discussion with @Mov AX, 0xDEAD, you would be aware of all issues the AMDXHC driver causes when PAE is enabled.
> The PAE patch works perfectly, but you must have drivers properly written to work with it, which isn't the case of the AMDXHC driver (even with PAE fix, there are many issues).
> The AMDXHC driver works fine on 64-bit (x64) and 32-bit (x86) with PAE disabled.

I delete this post.

#3984

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #3981

> The PAE patch works perfectly, but you must have drivers properly written to work with it, which isn't the case of the AMDXHC driver (even with PAE fix, there are many issues).
> The AMDXHC driver works fine on 64-bit (x64) and 32-bit (x86) with PAE disabled.

Thanks for the clarification. This information will be also useful for users who want to try to have both USB3 and PAE enabled at the same time.

#3985

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #3979

> try removing the PAE patch? maybe that is causing problems

I already knew it was the patch, but my goal was to have both allowed without issues. Now I know this will not be possible and I will have to accept a compromise.

#3986 | daniel_k | Just released ⇗ Intel RSTe AHCI/RAID driver v4.7.0.1117 for Windows XP/Server 2003

#3987

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #3986

> Just released ⇗ Intel RSTe AHCI/RAID driver v4.7.0.1117 for Windows XP/Server 2003

Does this driver support commands for SSD drive on Windows XP, including the TRIM command?

#3988

daniel_k

> Zitat von ⇗ YuriyCN im Beitrag ¶ #3987

> Does this driver support commands for SSD drive on Windows XP, including the TRIM command?

The driver does support TRIM, but getting it to work on XP is another story.
To be honest, as XP doesn't send TRIM commands itself, which would be optimal, I personally wouldn't care about it.
I find that running an utility just to trigger TRIM an annoyance.

#3989

YuriyCN

> Zitat

> The driver does support TRIM, but getting it to work on XP is another story.
> To be honest, as XP doesn't send TRIM commands itself, which would be optimal, I personally wouldn't care about it.
> I find that running an utility just to trigger TRIM an annoyance.

Without the use of TRIM, the SSD disk will wear out more or performance will only decrease? I did not find on this forum a discussion on the use of SSD disks on Windows XP. I think this is important.

#3990 | veselcraft | What about ASRock B450 USB xHCI drivers? I tried to use ⇗ this trick, but it doesn't work, Windows XP Setup from USB shows BSOD with error code 0x0000007B. Hardware ID is 1022-43D5

## Page 267

#3991

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #3981

> The PAE patch works perfectly, but you must have drivers properly written to work with it, which isn't the case of the AMDXHC driver (even with PAE fix, there are many issues).
> The AMDXHC driver works fine on 64-bit (x64) and 32-bit (x86) with PAE disabled.

Dear daniel_k, I'm sorry, I misled you with the latest reviews about the USB driver. Over the past 2 days, I reinstalled Windows several times and did a lot of experimentation. It turned out that the driver "amdxhc_pae_fix" stably works only in the "Windows Server 2003" and "Windows XP + PAE patch" systems. But in Windows XP without the PAE patch, this driver causes the PC to freeze at boot. Hangup does not always happen, but about once per 5 times. Moreover, freezing can occur even when nothing is connected to the port.
Conclusion:
Unfortunately, the universal driver failed. In Windows XP with and without the PAE, we need to use 2 different drivers. I ask you to try to combine functionally two drivers into one. If the result wiil be obtained, I am ready to test.

#3992 | YuriyCN | The main developments of this topic should be placed in the 1st post. Periodically, the 1st post to update. Its hard for users to find information in over than 260 pages.
#3993 | XPWELL64 | Toshiba 1135 Amber Lights[/URL]⇗ @diderius6 ⇗ @Lost_N_BIOS ⇗ @infuscomus ⇗ @Mov AX, 0xDEAD ⇗ @IntiMD Hello Look at my broken Windows XP laptop. How do I fix it? ⇗ Toshiba Satellite 1135 Amber lights

#3994

diderius6

⇗ @XPWELL64
I think the easiest way is to desolder the Bios chip,
program it new with Epromer with Bios file from other notebook
of the same type
Dietmar
PS: I have done this 3 times and always with success.

#3995

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3994

> I think the easiest way is to desolder the Bios chip

⇗ @diderius6 ...just curious, are you using a hot air device for unsoldering/resoldering or a normal soldering iron? How many pins on the chip?

#3996

diderius6

⇗ @gordo999
Until now I soldered only Bios chips with 8 legs. Years ago I soldered other chips with much more pins.
One time I used hot air for desoldering Bios chip, be carefull with your fingers!
It depends, on how the Bios chip can be reached. When there are other components very near,
I use normal soldering iron.
For to put back the chip into the motherboard I always use only normal solder iron
Dietmar
PS: This is not an easy task for everybody. You need a calm hand, good eye and experience in soldering.
I also thought, how I can help ⇗ @XPWELL64 . He could send to me his whole Asus laptop, but I have no business in soldering^^,
so it would be without any garantie.

#3997

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #3996

> PS: This is not an easy task for everybody.

⇗ @diderius6 ...I know, I have been doing it for decades but not much experience with high density SMD devices. I have a mobo apart right now trying to replace mosfets but I need a LAN chip I cannot find anywhere. I am suspicious about all the sites in China claiming to have them.
I bought a stereoscope from Amscope so I could see what I am doing. Also, bought a hot air station and a power supply on which I can limit the current. Very important for checking short-circuit conditions. I asked how many pins you have because it's nearly impossible to use a soldering iron when the pin count gets really high, like 16 pins per side.

#3998 | XPWELL64 | ⇗ @diderius6 The error not comes from bricked bios. Can you find me a solution? Can you look at the photo to find the cable issue? I think it is from cable issue. If there aren't any cable issues, find the missing solder points.

#3999

diderius6

⇗ @XPWELL64
I do not understand your question.
What happened with those cables?
The only error I have had with notebook was with corrupt ram. May be give this a try.
Do you get a picture at boottime on screen?
Because I do not know this Toshiba 1135
try to get a service manual or picture of cables via Google
Dietmar

#4000

diderius6

⇗ @XPWELL64
I take a short look via Google for Toshiba 1135.
This LED changed from green => amber?
If yes, this can be a problem with power.
Disconnect the battery and after this connect only AC adapter,
press power on for 30 seconds
Dietmar

#4001 | XPWELL64 | ⇗ @diderius6 I'll try this method but don't forget to look at my pc. Here are the photos: XPWELL64 has attached images to this post ⇗ IMG_0158.JPG ⇗ IMG_0157.JPG
#4002 | diderius6 | ⇗ @XPWELL64 I think, those cables are the antenna for the pci-e WIFI chip Dietmar ⇗ https://www.youtube.com/watch?v=fo5easyIX0Y&t=19s ⇗
#4003 | XPWELL64 | ⇗ @diderius6 1- I have an external broadcom wireless adapter came from HP pavilion. 2- Can you look at the photo again? Is there any missing cable connection?

#4004

diderius6

⇗ @XPWELL64
I cant see any other disconnected cable.
I am quite sure, that it is a problem with power.
Take the battery out.
After this, press for one minute power on.
Then connect only AC adapter (battery is still out) and press power on
Dietmar

#4005

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4002

> I think, those cables are the antenna for the pci-e WIFI chip

⇗ @diderius6 ...that makes sense they leads are soldered to terminals in the case, where an antenna should be. I think you're right, it's likely a power supply issue.
⇗ @XPWELL64 ...you need to get a service manual (not a user manual) if possible, as Dietmar suggested. Some can be found on the Net if you look carefully. You'll need a Digital Volt Meter (DVM) to measure voltages, especially the output of the AC adapter 'when it is plugged in'. This is not an easy repair, it's not something you can solve over the Net.
A user manual might tell you what the amber light means. I would suspect a power supply issue, a bad hard drive, etc. Listen to the hard drive for sound when you power on. You should hear it 'seeking'...clicking sounds during boot. Some are noisier than others. If it is clicking, and/or, the hard drive LED is flickering, you should get an indication on the screen that it is trying to boot. You might even get beeps. If so, count them and look it up in a user manual as to what the beeps mean.

## Page 268

#4006 | XPWELL64 | ⇗ @gordo999 There isn't any hdd on my laptop.
#4007 | Dibya | Anyone can link me storahci driver of Skulltrail?
#4008 | Andalu | ⇗ @Dibya it's ¶ here ~~~~~~~~~~~~~~~~~~~~~~~~~ Happy New Year to all forum members
#4009 | Dibya | Anyone can link me to timer bug fix patch of hal?
#4010 | KeesoN | Hello. I had some problem after installing Windows Xp 32 bit to my computer. After restarting system i couldn't boot system because hal.dll was corrupted. Can somebody send me link with modified/normal hal.dll for Windows XP 32 bit(or better for 64 bit), i wanna install again windows XP and i hope with modified hal.dll system will boot without problems(I speak in English and Russian). Also i wanna know,everyone could install all needed drivers to their machines.

#4011

gordo999

> Zitat von ⇗ KeesoN im Beitrag ¶ #4010

> Also i wanna know,everyone could install all needed drivers to their machines.

⇗ @KeesoN ...I have XP running on an Asus B360M chipset (300-series), with an i5-8400 processor, with all the features I need. I am running USB through an add-on card (Vantec with VIA chipset and XP drivers) but I have not tried daniel_k's latest USB driver. My Nvidia GT-730 video card is running as well as my Creative XFi audio card. Video is stable at 1920 x 1080.

#4012

gordo999

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #4006

> There isn't any hdd on my laptop.

XPWELL64 ...not familiar with SSDs. Does an SSD not have an indicator light? On my mobo, the LED driver light comes from the mobo, not the disk drive. If your light is connected in your laptop, it should indicate with an SSD plugged in.
Did your laptop come with an SSD or did you add it? If so, check the manual for which light represents the HDD and see if it lights with your SSD connected.

#4013

KeesoN

> Zitat von ⇗ gordo999 im Beitrag ¶ #4011

> My Nvidia GT-730 video card is running as well as my Creative XFi audio card. Video is stable at 1920 x 1080.

So,how you play some games or use some modern programs? Because i use some needed program,that isn't starting on VM

#4014 | diderius6 | I just test on a Lenovo W530 with K2000m 2GB graphik card 3Dmark2001. Under Win 10 64 bit: 25001 Under XP SP3 32 bit: 51841 Waaoh, what a difference Dietmar

#4015

IntiMD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4014

> I just test on a Lenovo W530 with K2000m 2GB graphik card 3Dmark2001.
> Under Win 10 64 bit: 25001
> Under XP SP3 32 bit: 51841
> Waaoh, what a difference
> Dietmar

⇗ @diderius6
Doesn't surprise me considering how since Windows 8 the DirectDraw and DirectX pre-9 (iirc; either pre-9 or pre-8) APIs have been deprecated, thus old games depending on those APIS worked sluggish on Win8 and above compared to Win7.
I wonder what results would be in Win10, if you use the dgVoodoo graphic-layer translator:
⇗ http://www.dege.freeweb.hu/ (stable version)

#4016

gordo999

> Zitat von ⇗ KeesoN im Beitrag ¶ #4013

> So,how you play some games or use some modern programs? Because i use some needed program,that isn't starting on VM

⇗ @KeesoN ...don't understand your question. I use XP only for older games that won't run on W7. I don't run modern apps on XP, you'll have to ask someone who does. I have never tried newer games or apps on a VM because I like the video and sound better in real mode. I use a VM only to run another OS within W7.

#4017 | kukonosau | Do you have B350 chipset drivers on Windows XP x86? And what is motherboard resources in system devices in device manager?
#4018 | kukonosau | GeForce Experience is working in Windows XP GTX 960 and so on today? Doesn't work in GT cards, for example GT 710. But in GTX cards working ShadowPlay?

#4019

gordo999

> Zitat von ⇗ kukonosau im Beitrag ¶ #4017

> Do you have B350 chipset drivers on Windows XP x86? And what is motherboard resources in system devices in device manager?

⇗ @kukonosau ....My mobo is an Asus B360M-C\CSM. The motherboard resources are as follows:
ACPI\PNP0C02\0
ACPI\PNP0C02\1
ACPI\PNP0C02\2
ACPI\PNP0C02\5
ACPI\PNP0C02\IOTRAPS
ACPI\PNP0C02\PCHRE3V
ACPI\PNP0C02\SARESV
I have a full set of 6 processor cores indicated in Device Manager for the i5-8400.

#4020 | YuriyCN | Dear daniel_k, OS - Windows XP Pro SP3 MB - Gigabyte GA-H110M-DS2 I use of the modified USB 3.0 driver included in the "amdxhc_pae_fix.rar". I found a nuance in the work of this driver. If the computer is put into "Standby mode", then after exiting "Standby mode" all USB ports stop working, and any device connected to the port is defined as "Unknown device" with USB\VID_0000&PID_0000. Only reboot helps.

## Page 269

#4021 | daniel_k | ⇗ @YuriyCN You're the first one who was able to wake up a system from standby while running XP. We don't really support Standby as almost all Haswell+ systems have issues with it. Please disable PAE and try my new driver and see if it works properly.

#4022

YuriyCN

Please specify, I must check the "AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018" from your post - ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (265)
But specify with what AСPI I should check. I found 3 different versions of the ACPI.SYS. Which one do you recommend to use together with a your USB driver?
I will reinstall Windows XP and check on a clean system.

#4023 | kukonosau | ⇗ @gordo999 Can we install motherboard resources? How to fixing? This is normally? System with motherboard resources is stable working? Where is chipset drivers?

#4024

YuriyCN

OS - Windows XP Pro SP3 VL Professional
MB - Gigabyte GA-H110M-DS2 (Socket 1151, installed 8GB DDR4 RAM)
Keyboard and mouse - PS/2
Test 1: Windows XP SP3 + PAE
USB 3.0 Driver - "AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018" + "amdxhc_pae_fix.rar"
ACPI driver - acpi.sys (239616 bytes)
Result: If the computer is put into "Standby mode", then after exiting "Standby mode" all USB ports stop working, and any device connected to the port is defined as "Unknown device" with USB\VID_0000&PID_0000. In addition to USB, all other devices work flawlessly.
Test 2: Windows XP SP3 (without PAE)
USB 3.0 Driver - "AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018"
ACPI driver - acpi.sys (239616 bytes)
Result: The situation is much worse. After exiting "Standby mode" - nothing works. I get a black screen or BSOD.
Test 3: Windows XP SP3 (without PAE)
USB 3.0 Driver - "AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018" + "amdxhc_pae_fix.rar"
ACPI driver - acpi.sys (239616 bytes)
Result: The situation is like in Test 1. File "amdxhc_pae_fix.rar" does wonders.

#4025 | ap7cesar | Hello: I am new to this forum. How can obtain an iso of windows XP pro 32 bit with usb intel xhci drivers and acpi.sys integrated? I have a clevo laptop and a skylake CPU. Thanks.
#4026 | daniel_k | ⇗ @YuriyCN, thanks for the reports, but as I've said before, getting XP running properly is already a challenge, fixing Standby is completely out of question.

#4027

daniel_k

⇗ @schreiberstein
Hi mate, as your are german, please take a look at this forum:
⇗ https://www.waldbauer.com/vb/showthread.php?t=2149
They have some interesting fixes for issues with NTVDM. Really knowledgeable persons there.
Hope that they can give us some clues as to how to fix it.
When you have some time, please share with them our issues with PAE, tell them it also affects Server 2003.
As far as I remember, you can't even run any DOS app, even in a windowed DOS Prompt, right?
In my case, the issue happens when trying to switch a windowed DOS app to full screen.

#4028

gordo999

> Zitat von ⇗ kukonosau im Beitrag ¶ #4018

> GeForce Experience is working in Windows XP GTX 960 and so on today? Doesn't work in GT cards, for example GT 710. But in GTX cards working ShadowPlay?

⇗ @kukonosau ...I have the Nvidia control panel and Experience working with driver package 340.52. I already had newer drivers working but the setup.exe file in 340.52 reloaded everything without complaining. So now my GT-730 is running with following drivers on XP x86:
NvCplSetupEng.exe version 1.0.3
dbInstaller version 6.14.13,4052
nvdrsdb.bin version 'unknown'
OpenCL.dll version 1.0.0
nv4_mini.sys version 6.14.13.4052
nv4_disp.dll version 6.14.13.4052
nvapi.dll "
nvcompiler "
nvcuda.dll "
nvcuvid.dll "
etc.
re your other question...my Device Manager does not show chipset drivers for the B360 chipset. It only shows PCI drivers, all from Cannon Lake series and what I posted last time. Don't look for chipset drivers, just follow instructions in this thread about loading an acpi.sys driver and a storport driver. I had my XP installation already loaded on a disk from an older Intel mobo. If you are doing a fresh install, follow the instructions in this thread about adding the drivers above to your XP installation disk.
BTW...you will need a PS2 port to operate the mouse and keyboard unless you can get the USB drivers working with daniel_k's USB drivers.

#4029

gordo999

⇗ @daniel_k ...hate to bug you since you are busy. Tried your latest release of the AMD USB drivers on my Asus B360M mobo and it crashed with a BSOD 0x7B. It may be related to the SATA AHCI drivers I am using which came from drivers on the XP SP4 unofficial package. They were issued by Fernando and they work well otherwise. Maybe I need a SATA driver related to your USB issue, since that cured the 0x7B error at boot. I have a Vantec USB add-on card working with a VIA chipset and I can run my mouse and keyboard off that.
The only drivers i have added to get XP going is an acpi.sys version 6.0.5048.0 from this thread and an iaStor.sys version 11.2.0.1006 with a DEV_A352 added to the INF by Fernando. My BIOS has not been modded.You might be happy to hear that my Creative XFi with driver ctaud2k.sys, version 6.0.230.0004-2.3.0000 is working great with all the software goodies working. Just got my Nvidia GT-730 fully operational as well with driver package 340.52.

#4030

YuriyCN

Dear daniel_k,
I am a fan of the old operating systems and of the classic interface therein. After installing Windows 7, it turned out that Microsoft has committed despicable - in all basic (simplified) themes, including my favorite Classic one, composition (2D video acceleration) is disabled. For this reason, the program interface is drawn with large delays / blinking text / stickings. There are no such shortcomings in aero-themes, but its more convenient for me to work in the usual Classic.
To solve this problem, a specialist "EL_Sanchez" made a patch for the DWM.EXE file. After replacing the original file with a patched one, the work of the classic theme is significantly accelerated. Unfortunately, when using the patched DWM.EXE, the window titles become transparent and user must restart the Explorer for correct displaying ot the Taskbar. Can you make a more correct patch for DWM.EXE, which will not have such shortcomings?
More details and patch DWM here: ⇗ [Solution] Acceleration of GUI interface on the non-Aero themes of Windows 7
DWM is already patched:
But this patch is not enough, here are issues:
1. The patch does not enable compositing, but does not disable compositing when switching from Aero to classic. If one restarts the PC, then on the newly loaded classic theme, acceleration no longer works; in short, the fact of switching the theme (aero -> classic) is important.
2. After switching to the classics, the look of the taskbar deteriorates - it becomes pale and translucent. If to restart the explorer process, then the color will return to normal.
But it is difficult to make a correct patch, so that when loading on a classic theme, the acceleration was initially, without switching themes and without restarting the Explorer.exe.
The technical essence of the needed patch:
so that when switching to the classic theme, leave the value of the field of the CDwmAppHost::s_fCompositionEnabledByPolicy class = 1, regardless of the checks. This value is then used to check whether the composition should be enabled.
Can you help with it (CompositionEnabledByPolicy) ?

#4031

daniel_k

⇗ @YuriyCN, seeing the details of that BSOD in the amdxhc.sys 276, I've found a bug.
Can you please retest the drivers? I have also included a PAE fix based on 276 (check PAE_fix folder).
By the way, I've updated the amdxhc_pae_fix.rar, it is now based on the V2 release, found here:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (208)
Regarding the DWM patch, I'll take a look at it when I have more time.

#4032 | daniel_k | ⇗ @gordo999 You mean the BSOD 0x7B as soon as the USB driver was installed on a working XP install? If so, we haven't ever seen this behavior. Otherwise, if you were trying to install XP with the USB driver integrated, something wrong happened during driver integration.

#4033

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #4031

> Regarding the DWM patch, I'll take a look at it when I have more time.

1. Thanks you. I will now reinstall Windows XP SP3 and check for new drivers (USB3 + PAE) on a clean system.
2. Regarding the DWM.EXE patch, this is generally the most important patch; without it, the Сlassic theme Windows 7 works without 2D graphic acceleration. A complete set of solutions, consisting of a new version of theme "Classic AE mod 2019_8", a patch for the DWM.EXE file, and a set of programs to accelerate the user interface (including the source code) - ⇗ [Solution] Acceleration of GUI interface on the non-Aero themes of Windows 7

#4034

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #4032

> You mean the BSOD 0x7B as soon as the USB driver was installed on a working XP install?
> If so, we haven't ever seen this behavior..

⇗ @daniel_k ...thanks for reply. I tried the driver installation on a working installation of XP. I already had a yellow exclamation mark from the failed installation of a USB driver by Dietmar and I looked under properties for that failed install and hit 'Update Drivers'. Maybe I should have uninstalled the old drivers first.
What kind of information would help you? I'll send as much as you need. I should point out that I have a set of VIA USB drivers running successfully for a USB3 add-on card. I have not verified USB3 operation but I have a mouse/keyboard running off a unified USB module and I am able to insert thumb drives and read from them.

#4035

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4030

> ... including my favorite Classic one, [b]composition (2D video acceleration) is disabled. For this reason, the program interface is drawn with large delays / blinking text / stickings. There are no such shortcomings in aero-themes, but its more convenient for me to work in the usual Classic.

⇗ @YuriyCN ....maybe I am misunderstanding you. Are you referring to 2-D issues in one application, or in Windows 7 in general? I have W7 running in Classic mode, on the same Asus B360M mobo, with no issues like you describe. I even have W10 running in W7 Classic mode with no issues. I also have XP running in Classic mode with no video problems, everything is running very smoothly with the graphics. I don't use Aero mode because I don't like it.
I don't know what you mean by 2-D mode, could you give more detail and I will check on my system? Is 2-D mode not the normal mode for Windows? I thought 3-D mode applied only to graphics cards.

## Page 270

#4036

YuriyCN

> Zitat von ⇗ gordo999 im Beitrag ¶ #4035

> I am misunderstanding you. Are you referring to 2-D issues in one application, or in Windows 7 in general?

This is a general Win7 problem.
Please be silent, you write nonsense and confuse thoughts. Study the problem first, for example - ⇗ https://www.neowin.net/forum/topic/10363...-win7/#comments
The basic information, with examples, programs and a patch DWM look here - ⇗ [Solution] Acceleration of GUI interface on the non-Aero themes of Windows 7
Dear daniel_k,
I remember, my PC:
OS - Windows XP SP3 Pro with PAE patch
Chipset - Intel H110M
I tested the proposed 3 variants of drivers. I currently have 4 versions of the amdxhc.sys file.
Driver 0 - a7623c00e10530ad1479b7b29d845412 *amdxhc_0.sys - my old driver
Driver 1 - 377d326e670d69305d1e0636f58956f3 *amdxhc_1.sys - driver from amdxhc_test.rar\PAE_fix\amdxhc.sys
Driver 2 - 093b13195b2b9c9c7b871f6a0b8cb09c *amdxhc_2.sys - driver from amdxhc_test.rar\amdxhc.sys
Driver 3 - 70bf62de81351beadb23d2b01a65e18e *amdxhc_3.sys - driver from amdxhc_pae_fix.rar
All files in 1 archive - ⇗ https://www.upload.ee/files/10958105/Int...ersion.zip.html
Driver 0 - My old driver. It works fine on a loaded system, without complaints. But after exiting the Standby mode into working state - all devices connected to USB ports are defined as PID_0000&VID_0000 (Unknown Device). When user disconnects the device, it disappears from the Device Manager. It turns out that the USB port does not freeze, it senses the fact of connecting to it, but cannot correctly identify the device and defines it as an "Unknown Device". In general, the situation is the same as I described to you earlier.
Your NEW FILES:
Driver 1 - the operation in all cases is completely identical to Driver 0.
Driver 2 - does not work at all on a loaded system, USB devices are not visible. When putting the computer into Standby mode, the PC freezes. Even the Reset button does not work, it is needed to turn off the power.
Driver 3 - the operation in all cases is completely identical to Driver 0.
As a result, none of the proposed drivers works after exiting the Standby mode. We are going the right way. Maybe the problem is not in the USB driver, but in the ACPI.SYS file ??

#4037 | daniel_k | ⇗ @gordo999 Before trying to install the driver, search for amdxhc.sys and amdhub30.sys in the \Windows folder (including subfolders) and delete all found. Now install as usual, if something goes wrong, something else should be causing the issue.
#4038 | daniel_k | ⇗ @YuriyCN, one last try. Please try it if you can. If this doesn't fix it there is nothing else I can do.

#4039

gordo999

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4036

> Please be silent, you write nonsense and confuse thoughts.

⇗ @YuriyCN ...If you would learn to present the problem correctly in the first place there would be no misunderstanding. This is a forum for XP, not W7. If you are going to whine about non-issues then you can expect people to wonder what the heck you are talking about.
You are the one misunderstanding the problem. If you want true hardware video acceleration, buy a good video card with a fast processor and lots of memory. If the main processor has to do the video as well as the rest of its loads, you might get the undesirable effects you describe. Even with my old Intel processor/mobo I did not experience what you are experiencing and I tried to do you a favour by informing you of that. Neither my W7 or XP installations have the problems you describe. You have something else wrong in your system or you are using an application/game that is placing too much of a demand on your processor.
Besides, daniel_k has indicated he is very busy. Why are you being so rude and demanding as to use up his time asking irrelevant questions about W7? Take your own advice. Go somewhere else and ask questions bout W7.

#4040

YuriyCN

gordo999
It does not depend on the productivity of the PC, even on a modern computer, with a powerful CPU and GPU, you will get problems with 2D performance in any non-Aero themes. To check, do download a simple program, for example 2ip NetMonitor from the website ⇗ https://2ip.ru/download/NetMonitor.exe and become assured that without the DWM patch on the Classic theme - all lines will flicker. But with the DWM patch, the lags disappear.
Similar problems will occur on other programs that do not use double buffering of video output. Another example is the simplest Neutron 1.07 program, you can download it from ⇗ https://neutron.ru.uptodown.com/windows/download or take it from the "Solutions" archive from ⇗ [Solution] Acceleration of GUI interface on the non-Aero themes of Windows 7 Even in the "Task Manager" (built-in from Win 7), the column "CPU load" flashes. There are a lot of such examples...
All cases are united by a trait - programs that do not use double buffering of video output will work slowly in any non-Aero themes (including built-in Classic). Enabling composition through the DWM.EXE patch forces double buffering, and significantly increases 2D GDI performance - removing blinking text labels and speeding up drawing of a 2D interface up to 10 times.
daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #4038

> Please try it if you can. If this doesn't fix it there is nothing else I can do.

I tested new version of the USB driver (amdxhc_test2.rar). Unfortunately, the situation is the same. After using the "Standby" mode, all USB ports stop working normally. Any connected device is identified as an "Unknown device".

#4041

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #4037

> Before trying to install the driver, search for amdxhc.sys and amdhub30.sys in the \Windows folder

⇗ @daniel_k ...sent a reply but it seems to have disappeared. That worked, thank you. Don't know why but there was an amdxhc.sys in the sys32\drivers directory, dated 2016. I deleted it and re-installed and now all USB ports are working.
Thanks for your hard work and help.

#4042

XPWELL64

⇗ @diderius6
Here are two pseudocode examples (From WINDOWS 7 X64 AND WINDOWS XP X86 Intel HD Graphics drivers):
XPWELL64 has attached files to this post

- ⇗ pseudo.zip

#4043

YuriyCN

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #4042

> @diderius6
> Here are two pseudocode examples (From WINDOWS 7 X64 AND WINDOWS XP X86 Intel HD Graphics drivers):

Do you have a driver HD530 graphics (CPU Intel i5-6600) for Windows XP ??
Please share with me.
daniel_k
Dear daniel_k, testing your drivers many times, I found a peculiarity that I had not noticed before. I thought this peculiarity as important, so I decided to write to you. Perhaps the information in "paragraph 2" will help you check the error.
1. If to put the PC into Standby mode with the USB device turned off, then after exiting Standby mode, the USB ports do not work normally. The device connected to the port is defined as an "Unknown Device" and obviously it cannot work normally.
2. But, now attentively!! If the PC is put into Standby mode with a device already connected (for example, a USB flash drive), it turns out that after exiting the Standby mode the flash drive works !!! I tried to open the flash drive - the files are seen, copied, everything works correctly. If to remove it and reinsert it, then it will already be defined as an "Unknown Device" and will stop working. If at the moment when the flash drive is working, connect the second - then the second is already defined as an "Unknown Device" and will not work, but the first will continue normal operation.
Conclusion:
USB can work even after the PC wakes up from standby mode. An important peculiarity is that only a USB device that was already connected to the port at the time of switching to standby mode can continue to work.

#4044 | XPWELL64 | ⇗ @YuriyCN I will mod it for you but you have to wait for the weekend. I'm learning how to reverse engineer drivers as pseudocode
#4045 | YuriyCN | XPWELL64 I will be very glad. I need such a HD530 driver for XP. daniel_k I received additional information that you might be interested in. The ability to correctly return from standby mode is very dependent on the BIOS/UEFI version. I updated the BIOS/UEFI to the latest version of F24 - the PC goes into Standby mode, but when wakes up - I get a black screen and halt. If to roll back the BIOS/UEFI version to the older version F3 that I used before, then returning from Standby mode is normal. In general, for the correct operation of Windows XP, it is advisable to use the old BIOS/UEFI versions.
#4046 | XPWELL64 | ⇗ @YuriyCN What is your issue about Intel HD 530 Windows XP drivers? Can you find the source of error code with dependency walker? Can you give me the dependency name with issue? I can fix it and I will send you a new igxpmp32.sys + inf.
#4047 | daniel_k | ⇗ @gordo999 Glad to know it worked! ⇗ @YuriyCN Glad to know that my "last" driver, although it gives "Unknown Devices", at least it doesn't crashes or hangs (black screens) your PC. Will update the "final" driver. Thanks for testing it. Yes, I know that older BIOS have better XP compatibility, but as most of us dual boot or even multi boot our systems, I think we all agree that it's better to have a BIOS optimized for supported OSes and lose XP Standby.

#4048

daniel_k

⇗ @canonkong
Hi mate!
Can you please sign these INF files?
- Fine tuned NoNVME.inf to support Windows 7 with NVME hotfix in case someone needs it.
- Created a "null" MEI driver, to prevent Windows from installing Intel's crappy driver which is useless for us and prone to security issues.
- Both INFs are future-proof, with a 01/13/2030 date.
Thanks!

#4049

YuriyCN

> Zitat

> What is your issue about Intel HD 530 Windows XP drivers?

Where can I download the HD530 driver for WinXP?
On the official Intel website there is a version for Win7/8/10 only.

#4050

canonkong

⇗ @daniel_k
Signed, enjoy it.
canonkong has attached files to this post

- ⇗ No EMI NVME SIGN.zip

## Page 271

#4051 | XPWELL64 | ⇗ @YuriyCN Please download Dependency Walker and find the issue.

#4052

YuriyCN

> Zitat von ⇗ XPWELL64 im Beitrag ¶ #4051

> @YuriyCN
> Please download Dependency Walker and find the issue.

I need a HD530 video driver to install through the "Device manager".
But I do not have this driver for WinXP. I have nothing to install.
I dont understand how "Dependency Walker" can solve my problem and what exactly should I do?
daniel_k
Today all day I experimented about Windows XP with different versions of BIOS/UEFI. There is a clear dependence: the older the BIOS/UEFI version -- the less problems there are with the installation and operation of Windows XP.
For my motherboard GA-H110M-DS2 there are such BIOS/EFI versions:
F1, F2, F3, F20, F21, F22, F23, F24.
I have 3 CDs with Windows XP installation - a clean installation with integrated SP3 (MSDN image) and 2 disks of different WinXP SP3 builds + upto 2017 updates. On older versions of BIOS/UEFI (F2, F3) - all 3 CD-ROMs are installed and work well. On the latest version F24 - only 1 CD is installed without problems. Unfortunately, the remaining 2 CDs are installed with different issues. For example, on one of the disks, at the first stage of the installation, I had to disable ACPI, otherwise I received a BSOD with error code 0x000000A5.
It would seem that the best option is to leave the old BIOS / UEFI F3 version and not to bother myself. But in the old version there is a big issue - a too large range of addresses (1.8GB) is reserved for devices (reserved memory). As a result, with version F3, in a 32-bit OS, only 2.2GB RAM is seen. I think it is abnormal.
When installing the latest version of F24 - this is not a problem. In 32-bit OC, 3.2GB of RAM is seen (800MB reserved). This is pretty normal, but as I wrote above, WinXP with the new version of BIOS/UEFI works worse. Do you have experience of finding and fixing the size of the Reserved Memory Area for devices in the BIOS/UEFI of the GA-H110M-DS2 motherboard?

#4053

IntiMD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4048

> - Created a "null" MEI driver, to prevent Windows from installing Intel's crappy driver which is useless for us and prone to security issues.

Wouldn't it be reinventing the wheel with that? ;)
If i do recall correctly the intel chipset inf files (at least in fernando's AiO) had already a null MEI/HECI inf to just fix that yellow bang.

#4054

daniel_k

⇗ @canonkong
Thank you very much!
⇗ @YuriyCN
I'm used to patch the DSDT table of Gigabyte BIOS.
If you are comfortable with flashing a modified BIOS, I can patch the DSDT table of your GA-H110M-DS2 for improved XP compatibility. Just let me know.

> Zitat von ⇗ IntiMD im Beitrag ¶ #4053

> If i do recall correctly the intel chipset inf files (at least in fernando's AiO) had already a null MEI/HECI inf to just fix that yellow bang.

My INF file has 52 device IDs.
Comparing with Fernando's pack, there are only 11 matches.
Most devices needing an actual MEI driver are not included in the Chipset driver, so no, I'm not reinventing the wheel.

#4055

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #4054

> I'm used to patch the DSDT table of Gigabyte BIOS.
> If you are comfortable with flashing a modified BIOS, I can patch the DSDT table of your GA-H110M-DS2 for improved XP compatibility. Just let me know.

My MB: Gigabyte GA-H110M-DS2
⇗ https://www.gigabyte.com/Motherboard/GA-H110M-DS2-rev-10#ov
BIOS/UEFI version F3 works best for Windows XP. Please, patch this version.
⇗ https://download.gigabyte.com/FileList/B...110m-ds2_f3.zip

#4056 | XPWELL64 | ⇗ @YuriyCN There is red mark on the Dependency with issue.
#4057 | XPWELL64 | I''m currently working on Intel HDMI Audio for windows xp.
#4058 | XPWELL64 | ⇗ @canonkong ⇗ @diderius6 ⇗ @Mov AX, 0xDEAD ⇗ @YuriyCN I'm learning reverse engineering. After that, I can patch the intel gpu drivers for debug. ⇗ @infuscomus I found 6.8 version of ida pro w/hex rays decompiler. I got used to IDA so I deleted relyze. There isn't any guide for Relyze. I found an XP compatible IDA Pro (not freeware). Relyze is not popular disassembler. I also prefer ollydbg because It is more basic than IDA.

#4059

YuriyCN

XPWELL64
IDA Pro with crack:
v6.5 - ⇗ https://rutracker.org/forum/viewtopic.php?t=4802739
v6.8 - ⇗ https://rutracker.org/forum/viewtopic.php?t=5129253
v7.0 - ⇗ https://rutracker.org/forum/viewtopic.php?t=5459068
v7.2 - ⇗ https://rutracker.org/forum/viewtopic.php?t=5748289
Hello daniel_k
I sent you a link to the binary of my BIOS version F3, that WinXP works best with. I ask to patch this file, and to reduce the amount of memory reserved for devices. Or is it a difficult task, and here is a high probability of breaking down the PC due to incorrect BIOS patching?

#4060 | XPWELL64 | ⇗ @YuriyCN I will patch vista drivers. Do you want to install vista? It is easier to patch it.

#4061

XPWELL64

⇗ @diderius6 ⇗ @canonkong
Vista driver comparison between original 1st and 2nd gen and 2nd and 3rd gen cpus:
For 1st and 2nd gen cpus:

    loc_180037F83:
    mov     [rsp+28h+arg_0], rbx
    call    memset
    mov     rbx, rdi
    mov     dword ptr [rdi+350h], 8086h
    mov     dword ptr [rdi], 16B8h
    add     rdi, 16B8h
    mov     [rbx+2C0h], rdi
    add     rdi, 480h
    mov     rcx, rbx
    mov     [rbx+288h], rdi
    add     rdi, 68h ; 'h'
    mov     [rbx+2B8h], rdi
    add     rdi, 370h
    mov     [rbx+2A8h], rdi
    add     rdi, 140h
    mov     [rbx+298h], rdi
    add     rdi, 5E8h
    lea     rax, [rdi+2000h]
    mov     [rbx+16A8h], rdi
    mov     [rbx+708h], rax
    call    sub_180037E50
    test    eax, eax
    jz      short loc_180038031

For 2nd and 3rd gen cpus:

    loc_180048D93:
    mov     [rsp+28h+arg_0], rbx
    call    memset
    mov     rbx, rdi
    mov     dword ptr [rdi+7C8h], 8086h
    mov     dword ptr [rdi], 1E50h
    add     rdi, 1E50h
    mov     [rbx+740h], rdi
    add     rdi, 480h
    mov     rcx, rbx
    mov     [rbx+708h], rdi
    add     rdi, 68h ; 'h'
    mov     byte ptr [rbx+7C0h], 1
    mov     [rbx+738h], rdi
    add     rdi, 368h
    mov     [rbx+728h], rdi
    add     rdi, 140h
    mov     [rbx+718h], rdi
    add     rdi, 628h
    lea     rax, [rdi+2000h]
    mov     [rbx+1E40h], rdi
    mov     [rbx+0BD0h], rax
    call    sub_180048C60
    test    eax, eax
    jz      short loc_180048E48

`480h 68h 140h` are same. Are they from 2nd gen cpus?

#4062 | YuriyCN | Why daniel_k stopped visiting this forum. He has not been online since January 14. We worry, who has the information?

#4063

Duke Solo

Hi guys!
Is it possible to run up windows xp 32bit on gigabyte B450M motherboard?
I have tried acpi.sys from post 2225, and some other, but unsuccesfull - i've got BSOD A5 (0x3
also i've tried ISO (⇗ https://piratebay.surf/torrent/34952867/...ition_2019.11.1) with same result
BIOS is CSM Enabled, but version is F41, software downgrade seems impossible...

#4064 | infuscomus | ⇗ @daniel_k ⇗ @diderius6 BSOD A5 0x3 any ideas?

#4065

YuriyCN

> Zitat

> Is it possible to run up windows xp 32bit on gigabyte B450M motherboard?
> I have tried acpi.sys from post 2225, and some other, but unsuccesfull - i've got BSOD A5 (0x3
> also i've tried ISO (⇗ https://piratebay.surf/torrent/34952867/...ition_2019.11.1) with same result
> BIOS is CSM Enabled, but version is F41, software downgrade seems impossible...

Read carefully what I wrote earlier.
In a standard way, the BIOS downgrade is blocked.
Use Intel Flash Programming Tool (FPT) for downgrade to older versions.

> Zitat

> Today all day I experimented about Windows XP with different versions of BIOS/UEFI. There is a clear dependence: the older the BIOS/UEFI version -- the less problems there are with the installation and operation of Windows XP.
> For my motherboard GA-H110M-DS2 there are such BIOS/EFI versions:
> F1, F2, F3, F20, F21, F22, F23, F24.
> I have 3 CDs with Windows XP installation - a clean installation with integrated SP3 (MSDN image) and 2 disks of different WinXP SP3 builds + upto 2017 updates. On older versions of BIOS/UEFI (F2, F3) - all 3 CD-ROMs are installed and work well. On the latest version F24 - only 1 CD is installed without problems. Unfortunately, the remaining 2 CDs are installed with different issues. For example, on one of the disks, at the first stage of the installation, I had to disable ACPI, otherwise I received a BSOD with error code 0x000000A5.

## Page 272

#4066 | infuscomus | ⇗ @YuriyCN Duke Solo has an AMD B450 motherboard, so using Intel Flash Programming Tool (FPT) for downgrade wont work for him.

#4067

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #4066

> @YuriyCN
> Duke Solo has an AMD B450 motherboard, so using Intel Flash Programming Tool (FPT) for downgrade wont work for him.

Versions from the Intel website for my Intel H110M chipset also did not work.
I used this version - ⇗ http://www.mediafire.com/file/p66jhts7cf...pt_DOS-Z170.zip
Sorry, I didnt pay attention that this is AMD.

#4068 | diderius6 | ⇗ @infuscomus We need to know the whole BSOD A5 (0x00000003, xxx,yyy,zzz) for the AMD Gigabyte B450M motherboard. In the meantime, test acpi.sys from outer space ) in post 3219 Dietmar
#4069 | XPWELL64 | ⇗ @canonkong Can you mod the Windows XP 32 bit Intel HD graphics?

#4070

gordo999

> Zitat von ⇗ Duke Solo im Beitrag ¶ #4063

> I have tried acpi.sys from post 2225, and some other, but unsuccesfull - i've got BSOD A5

@DukeSolo ...how did you insert acpi.sys into XP? You can't do it directly otherwise the system file checker will replace it. You need to do it offline, from an external OS, like a system with XP and W7 dual-booted and W7 as the boot drive..
I ran SPF and it removed the modded acpi.sys. I had to find where it got it's files from and insert the modded acpi.sys offline so that when SPF tried to replace the file it used the modded acpi.sys

#4071 | XPWELL64 | ⇗ @diderius6 A user named ⇗ @canonkong on this forum doesn't listen us. I told him to mod the XP 32 bit and Vista 64 bit driver but he didn't reply. I think he should stop only working on Win7 and start working on XP and Vista 32 bit graphics drivers.
#4072 | canonkong | @ XPWELL64 I have no experience in modifying XP and Vista systems. One is that they have a long history, and the other is that they not have any effective drive source. I toke a lot of time to modify the drivers for win7 and win8.1 because they are more people use.
#4073 | XPWELL64 | ⇗ @canonkong But Vista drivers looks same as 7 drivers because of 64 bit architecture.

#4074

gordo999

> Zitat von ⇗ canonkong im Beitrag ¶ #4072

> I have no experience in modifying XP and Vista systems.

⇗ @canonkong ...You did a good job with the W7 USB driver for modern chipsets (eg. B360M). It worked on mine and I have all of my USB ports working on W7. Thank you. Thanks to ⇗ @daniel_k, I have all my USB ports working on XP as well on the same chipset.

#4075

daniel_k

⇗ @YuriyCN
I have been busy.
For safety reasons, I always check the BIOS before and after modification with UEFITool_NE, to see if there are any warnings, as this version does additional verification that the "regular" UEFITool doesn't do.
There are some messages or warnings we need to be careful with, I believe.
See these screens:
⇗ ⇗
⇗ @Lost_N_BIOS, are those messages critical when modifying the BIOS or they can be ignored?

#4076 | YuriyCN | ⇗ @daniel_k Maybe my motherboard GA-H110M-DS2 has a hidden menu in BIOS/UEFI with advanced options? If this menu is available, please unlock advanced menu for BIOS/UEFI version F3.
#4077 | infuscomus | ⇗ @diderius6 can we solve the ACPI BSOD when using XP in a KVM VM? I would like to be able to have the option to use XP inside KVM with hardware passthrough in the future once CSM is fully removed from UEFI in the near future.
#4078 | diderius6 | ⇗ @infuscomus What is the exact ACPI BSOD in the KVM VM? And is it always the same BSOD, not depending on which machine this VM is running Dietmar
#4079 | infuscomus | ⇗ @diderius6 the BSOD is A5 0x0000014 It's the same on BSOD on any physical machine running KVM, it does not matter which hardware your physical machine has, so I think the problem must be inside the ACPI code of KVM hypervisor itself
#4080 | diderius6 | ⇗ @infuscomus Please write the exact ACPI BSOD, something is missing Dietmar

## Page 273

#4081 | infuscomus | ⇗ @diderius6 i posted the BSOD earlier in post #3132 ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (209)

#4082

diderius6

0x14 : ACPI_PNP_RESOURCE_LIST_LENGTH_TOO_LARGE
The current buffer that ACPI was parsing
⇗ @infuscomus
This BSOD means:
1.Variable: The buffer's tag
2.Variable A pointer to a variable that contains the ULONGLONG length of the buffer
3.Variable ACPI could not parse the resource descriptor. The length exceeds MAXULONG.
Have you tried also the acpi.sys from outer space? This seems to be a strange error. When all are 64 bit, how can this happen
Dietmar

#4083 | Duke Solo | Guys, regarding AMD B450 chipset. I have tried acpi.sys from post 3129 with same result. SFC is completely disabled (zero file list method). Exact BSOD is 0xA5 (0x3,0x895741E4,0xC0000034,0x494E495F)

del-1

diderius6

Hi,
a little bit off topic,
but has anybody here in the forum has been able to install Win98SE with all drivers on a IBM ThinkPad T43 laptop with discrete graphic card x300?
If yes, I think this would be the only notebook,
where everything works from win98 to Win10^^
Dietmar

#4084 | infuscomus | ⇗ @diderius6 outer space same error If you not afraid of using linux, you can setup KVM yourself to confirm the result.

#4085

XPWELL64

⇗ @diderius6
Method (_INI, 0, Serialized) // _INI: Initialize
{
TBPE = One
OSYS = 0x07D1
If (CondRefOf (\_OSI, Local0))
}
What does it mean? I modified OSYS = 0x07D1 from 0x07D9

#4086

diderius6

⇗ @XPWELL64
This change the versionsnumber back to 8 numbers, I think from Win7 to NT4?
Which OS belongs to which OSYS number is described at the beginning in DSDT.
I think, the number has to be changed at other places also.
But do this only, if you are sure what this changes are doing
Dietmar

#4087 | XPWELL64 | ⇗ @diderius6 0x07D1 This is XP!!!!!!!!!!!!

#4088

XPWELL64

⇗ @diderius6
I found that why Vista can run on ACPI on newer PCs Please read this text has taken from Microsoft (maybe it is wrong).The website says Windows operating systems return 0xFFFFFFFF if the argument to the _OSI method specifies an earlier version of Windows. For example, Windows 7 returns 0xFFFFFFFF for both "Windows 2009" (Windows 7) and "Windows 2006" (Windows Vista). Windows 7 equals 0x07D9.
0x00000000 if the operating system does not support the version in the argument.
0xFFFFFFFF if the operating system does support the version in the argument.

#4089

Andalu

XP seems don't work on asrock H310M-HDV. I tried both a fresh installation and the image restoring from a working XP with no success. I got the A5 BSOD for all the acpi sysfiles found on this forum except for this ¶ acpi.sys for which I got the 7B error.
Any suggestion?

#4090 | XPWELL64 | ⇗ @Andalu Did you try DSDT.aml patching? I don't prefer ACPI.sys because of more bugs such as bsod at installation, ACPI specific issues. Use the ⇗ @Mov AX, 0xDEAD's dsdt patcher at boot time. Search this term to google and follow the steps. You have to try at least two times to finish installation with custom acpi.sys.
#4091 | Andalu | ⇗ @XPWELL64 It is the first time that I am unable to install XP due to an acpi error. Unfortunately, I have never been able to understand how to use the ⇗ @Mov AX, 0xDEAD's dsdt patcher or another dsdt patching method. In the past all my attempts have been unsuccessful
#4092 | XPWELL64 | ⇗ @Andalu ⇗ @Mov AX, 0xDEAD tells you all steps here: ⇗ https://msfn.org/board/topic/179059-acpi...r-at-boot-time/

#4093

Andalu

⇗ @XPWELL64
thank you for the link. I had read this similar thread of ⇗ @Mov AX, 0xDEAD:
⇗ http://reboot.pro/topic/22051-acpi-patcher-at-boot-time/ (at the moment not reachable)
I'm still stuck at step 4)
from the point 5) and following I have many difficulties to understand how to proceed
Please keep in mind that I am still unable to modify a dsdt table. I never found any guide on the net.

#4094

diderius6

Hi,
I just do USB boot to XP SP3 on a ThinkPad T43 via SSD.
This is much faster than the original IDE harddisk^^.
Now I try to install really every OS (NT4, win95, win98, Linux..) on this nice machine
Dietmar
⇗

#4095 | XPWELL64 | Where did you find it? I will buy an Intel g31 because there is a new motherboard. I don't like second hand unless I get it from the most trusted store.

## Page 274

#4096

gordo999

Just wondering which version of HAL I should be using on XP? I have an Asus B360M, with an Intel 300-series chipset. Just noticed that my HAL version in system32 is hal.dll ver. 5.1.2600.5687. I am using a modded acpi.sys from this blog and it works fine but should I be using a different HAL?
Everything is working much better than expected except I still have no LAN drivers. Have full USB, no BSODS. I am running an AM10 USB Cisco wireless adapter and I can get on the Net, but all of my browsers run very slow and are not usable. Internet Explorer ver 8 runs good enough to do some basic downloads but Firefox and Opera 36 wont run at all. Had older versions of Firefox and Opera before but same problem.
My NVidia GT - 730 works fine for games but the other day while using windbg the NVidia driver nv4_disp.dll crashed part way through a debug session. Error 0x50 which is related to a memory problem. My memory is good. There are so many NVidia driver packages I don't know which one to use. My current is 340.52. Read about a modded nv4_disp that is available, does anyone know anything about this?

del-2

diderius6

Hi,
hard job to install Win98SE with all needed drivers on the ThinkPad T43.
But now I have them all: Lan, sound, USB2, grafikdriver which works only after an *.inf modifikation for the Radeon mobility x300
Dietmar
PS: I miss only a good browser^^..
⇗

del-3

dencorso

> Zitat von ⇗ diderius6 im Beitrag ¶ #del-2

> PS: I miss only a good browser^^..

Not anymore. Get Retozilla: ⇗ https://msfn.org/board/topic/174987-retr...comment=1175917

del-4

IntiMD

> Zitat von ⇗ dencorso im Beitrag ¶ #del-3

> > Zitat von ⇗ diderius6 im Beitrag ¶ #del-2

> > PS: I miss only a good browser^^..

> Not anymore. Get Retozilla: ⇗ https://msfn.org/board/topic/174987-retr...comment=1175917

Either that or Opera 10.70 build 3488 for vanilla 98 (w/o KernelEx)
⇗ https://retrosystemsrevival.blogspot.com...windows-95.html
here's a nice compendium of browser and the old OS compatibility:
⇗ https://www.vogons.org/viewtopic.php?f=24&t=12102

del-5

gordo999

> Zitat von ⇗ IntiMD im Beitrag ¶ #del-4

> Either that or Opera 10.70 build 3488

⇗ @IntiMD ...I am running Opera 9 for certain functions on W7 but it does not work well on many sites. For some reason, none of my browsers will run well on XP with the 300-series chipset. Sadly, Internet Explorer 8 is the only one that function half decently. I'm wondering if it has something to do with the lack of a network driver. There is also the possibility that I messed something up in the registry. I had to convert all references to the D:\ drive, where I had XP installed, to C:\. I don't want to do a fresh install because I have so many old apps loaded on XP and reloading them would be a nightmare. Looking at a repair install but that leads to other issues, like getting all the updates re-loaded.

del-6

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #del-2

> hard job to install Win98SE with all needed drivers

@diderius6... Dietmar...are you aware of the work done by the late R. Loew with win98? Google 'r.loew windows 98' and see what comes up. If you can't find anything I can get a Wayback Machine link for you.
Just found it:
⇗ https://archive.org/search.php?query=creator%3A%22Rudolph+R.+Loew%22

#4097 | juk777 | I welcome you, dear! Prompt, please, the worker acpi.sys for Windows XP x64 on Ryzen... Thanks...
#4098 | MVoloshin | Hello, could you give me the links to most stable modded acpi.sys and storahci.sys versions, please?

del-7

diderius6

⇗ @dencorso
I tried a lot of browsers for Win98 SE.
The best one is the one you told about, Retozilla.
It is fast and shows every website.
But on youtube it cant show videos, I think because of HTML5.
But for daily use just just looking news,
Retozilla can be used in 2020:))
Dietmar

#4099 | diderius6 | ⇗ @MVoloshin Take a look at post ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (255) Dietmar

#4100

gordo999

> Zitat von ⇗ genieautravail im Beitrag ¶ #3822

> XP displayed a message sayng that the USB hub doesn't have enough power for running the device...

⇗ @genieautravail you could try an external USB hub that supplies its own power. The output current is independent of the input current from the USB port.

#4101

ruthan

Hello,
thanks all for this work, especially Diderius6+Daniel+ MovAX0xDEAD , i started with XP on Z370 (GB Aorus ultra gaming) (Z170 was easy) almost 2 years ago, later i tested Daniels moded bioses. I remember when i after zillion tried made Xp install on with with automated install because even PS/2 port where not working.. and later managed to integrate network drivers and connected through vnc or remote desktop and slowly made thinks working to make possible actually used machine..
Well as maybe some know my goal, is multiboot gaming machines, i made some fastest and as possible DOS with PCI Sound to Windows 7 x64 machine(max is X58/ X79), i have on every machine Linux (or more of them) too and on main ones have Mac OS too.
Gaming is important because otherwise you can just use virtualization(real one - Vmware Workstation/Fusion), which is working quite good for non gaming stuff. I spend also some time with Unraid, where you can passthrough videocard to guest. Its working, but has lots of disadvantages.. and only main advantage - you can run on one machine multiple - machines in parallel without rebooting. I dont follow last 2 years progress but there wasnt possible to simply switch USB devices, so i needed lots of cables and KVM switches.
Main difference which is generation my goal, is that you need much more PCI-E slots to have some special devices for target os. So you need multiple videocards (XP support ends with Geforce 9xx), sounds card, disk controllers and every saved slot big victory (good placement you components because videocards are often is 2 slots.. is quite puzzle game). So for example make integrated lan in XP matters.
From gaming perspective is XP 64 dead end, so im not interested.
I read whole thread, here are my notes, sorry for lenght, but it was lenghty reading too, so im giving you your own medicine:)
1) This thread is behemoth, can some make some Wiki or at least some Google shared docs with some main info and keep there links to all important and proven working patches? Its disable by Forum rules, we can make at least some mega summary post amd the start of some thread.
Maybe we can add some collection of lastest XP drivers or something like that.
2) What you thing about X299 platform, there is lots of Z370 / Z390 users, but there are even more power CPUs (yeah nosier too, you need water cooler) and much more PCI-E lines 16 vs 28/44 - what is great epecially for multiboot machine, when you need 2/3 parallel GPUs and M.2 disk are PCI-E eaters too.
3) Why PAE matters? If you have really adjusted system with lots of apps, from my experience PAE mode (old Dibya patch) with more than 3.X GB of RAM is much
smoother and there is less micro freezes, when is working.
And believe me that i have 2 quite loade and fully configured system images ~15 years old (Z97,X99,X58,it ran on AM3,FM2,Z170,X99 too), second 12 years old (Coffelaked now) XP installs, which survived lots of CPU and MB changes (P2P and P2V tools are you friend, low level guys will tell that its just sysprep for dummies, but i dont need to do everything on lowlevel.). Because i really hate that you must reinstall it because of problem.. bla, bla.. and proven that there is other way, when there is will.
If you think that for DOS PCI audio, you just need PCI slot (there are still Z370 MBS with PCI slot), you are wrong, there are details:
⇗ https://www.vogons.org/viewtopic.php?f=62&t=24769
⇗ https://www.vogons.org/viewtopic.php?f=46&t=63773
4) If im not wrong, there are still not intel 218,219? It means that - 217 is ok? On MSFN, BearnWindows tried simply mod *.inf - no luck too. Some MB have Killer 2500 lan adapters (i read that depends on revision, which ones are ok?), can at least their drivers could be fixed for WinXP?
5) Other thing which make XP line mode problematic, manage someone get 3 monitors working (Nvidia 9xx cards supports i thing up 4 monitors)? I can manage do get working only 2 in XP, regardless of card, i thing that is Nvidia driver limitation.
6) There is lot of USB talk, but anything about USB firmware (and we are on win-raid:), at least for addon USB3 cards there are newer firmware, maybe this sometime could make a difference? BTW i dont see here much talk about NEC and Reneses USB3 cards they are working too in WinXP.
7) Is in some Device manager screenshots are both ACPI multi procand MPS multi proc.. Its it ok?
8) There was some Win98 talk, there main problem are really videocards drivers,because only very old cards are supported - you need some PCI-E gen1 - Geforce 6xxx (Geforce 7 even with Rloew patch is lost cause for gaming,Geforce 5 PCI-E / PCI are rare) or Radeon X300-X850 and even them are too modern for some games. Other problem is that at least some newer MBs (Z370) simply throw away PCI-E gen1 cards support and cant boot with them, simply behave as these cards are not pluged in.
If someone can fix it, or find some new MB, which is still suporting them, it would be nice.
If dont want mess with forcing OS to disable some gpu make other primary, what is half working (infamous dual dual stunt). You need Gigabyte or HP O.E.M MBs which are only ones which has in bios primary GPU slot selection - so you can make bios profiles per OS and with multiple display cables and monitor inputs or hdmi switches you can make it working fine.
Only other solution and probably only possible future.. unless some direct GPU Passthroug of whole GPU to virtual machine is drive new open source GPU drivers from the scratch.
New video cards have enough horsepower that you can waste u dunno 95% of its performance and even that performance would be greater that Win98 fastest videocards. Im a bit dissapointed that there are lots open source Linux graphics drivers, graphical API translators etc..but nothing for Win98.. ve have only generic 2D drivers, without any Direct3D/OpenGL support, i thing that is possible to write them.
Otherwise there is lots of urban legends about that Win98 are not supporting PCI-E, its just lie - if you have drivers, its working at least - videocards, storage controllers and Nics can work.. Chipset drivers - for modern MBs, are not exists, but you dont need them, if want just have right names for devices are some null drivers (Lone Crusader made some package).
You really need only storage drivers - unless you get generic 2MB/s transfers.. btw lost of disk benchmarks for Win98 just reporting non senses, just copy files.
Rloews Sata and AHCI drivers (i tested them at least with Z170) are working fine, dont forget that in Win98 you have to enable DMA for every disk usually manually otherwise again - 2MB/s "fun".
9) Managed someone to boot modern Mac OS through Grub2, or only way is still Clover and other Mac specific bootloaders? rEFIfind alone is hell from my point of view.
10) There some MBs without PS/2 and its USB issue, there some some cheap PCI/ PCI-E cards, would be possible make them working with XP installer?
11) Regarding of 900 MB RAM in XP instead of 3 GB, i had this problem with some MSI X99 board (no moding or special ACPI needed).. Its just bad Bios design, there is some like memory map or areas and they are just made for much modern OS.. and make these problem with XP.
Details are here:
⇗ https://msfn.org/board/topic/176845-xp-p...-available-why/
In some supermicro manuals you can even find details, who these areas are designed on some MB, so it could be adjusted if you can mess with EFI code, unless is connected with bad HW design too.
There is lots of claims that is GPU related, but i thing that is miskate, i did lot of testing that and usable memory was always the same regardless of used videocard.
12) DOS full screen hang its on Nvidia present even in Win98 - its never fixed old bug, i thing that you can simulate it even with classic vanilla XP install on old supported HW.
13) If someone care about last just supported without moding XP MB its B75, where PCI DOS sound is still working and it already has EFI (XP im booting in legacy mode) and primary videocard slot selection in case of Gigabyte. For installation you just need switch in bios storage controller to IDE.
14) Dos with Win98 even with 3dfx can be now covered quite good with PCem emulator,
and there is even progress on Vmare Dos SB16 emulation:
⇗ https://www.vogons.org/viewtopic.php?f=62&t=69314
And you never know what QEMU will bring to table.. its probably most ambitious SW project with all its supported architectures.. but it strungle with missing Windows GUI and other things for years.
15) If searching some ultimate multiboot NIC, its Broadcom 5721 gigabit NIC, which is running from Win98-Win10, Linux too, unfortunately no MacOS afaik (i thing that it could be added to universal driver, but i wasnt able to reach author -
⇗ https://www.tonymacx86.com/threads/fakep...17#post-1887882 ), there are Mac OS Broadcom suppoted NIC, but this one is not added. On some MBs, is working even in pure Dos with native packet drivers (MS dos networking stack is crapp).
16) BTW Has someone working 10Gbit NIC with WinXP?
17) If want make install more smooth there nice cheap (<10$) ASM PCI-E 106x storage controllers, which IDE bios too, so you can bypass AHCI stuff install XP and care about storage controllers(Fernando drivers) later and have fallback possiblity.
18) I have bad memory, but for those who are still using CDs, im sure XP install worked fine with Rufus, Yumi or Sardu. ISO was loaded into ramdisk before installation. Im using same way for Win98 installs too.
19) Other not discussed problem here is non System GPT disk access from XP, its handy for share data. Im using paid Paragon GPT loader for it for years, its working fine, with most of disk controllers.

#4102 | genieautravail | ⇗ @genieautravail you could try an external USB hub that supplies its own power. The output current is independent of the input current from the USB port. No more issue with the latest release of WinXPPAE !

#4103

YuriyCN

Windows XP SP3 + Intel RSTe AHCI/RAID driver v4.7.0.111 ⇗ Intel RSTe AHCI/RAID driver v4.7.0.1117 for Windows XP/Server 2003
1TB HDD drive (SATA 2):
Read speed = 100-110 MB/s; Write Speed = 80-100 MB/s
250GB SSD drive (SATA 3):
Read Speed = 180-200 MB/s; Write Speed = 85-90 MB/s
Windows 7 SP1
1TB HDD drive (SATA 2):
Read speed = 110-120 MB/s; Write Speed = 90-100 MB/s
250GB SSD drive (SATA 3):
Read Speed = 490-500 MB/s; Write Speed = 420-430 MB/s
Why does the SSD drive slow down on Windows XP?
Is it possible to increase disk performance?

#4104

diderius6

Hi,
I just succeed to install Win7 with all drivers, USB, sound, lan, wlan, grafik
on the nice notebook IBM T43 thinkpad.
Now I am going to Win 8.1 where I notice a problem with drivers for the IDE harddisk,
until now no solution
Dietmar
PS: On the Pentium M 770 you can enable the NX memory protect bit, which I think is necessary from >=win8.

#4105

AbdullahTrees

Hello Guys!
I've installed Windows XP SP3 on a 2012 Laptop (HP Envy m6-1105dx) as I'm using it as a semi-portable retro-arcade machine. By using driverpacks and Easy2Boot, I've managed to make my system 90% usable. Everything works; from Graphics to Sound to Networking, and the speed is quite good too. There's just one problem: The laptop has 4 USB ports, 3 USB 3.0 ports and 1 USB 2.0 port. Only the USB 2.0 port works, and I'm trying very hard to install USB 3.0 drivers so I can at least use the USB ports like a USB 2.0 port for things like a keyboard and mouse, but to no avail.
According to Device Manager: Other Devices > USB Controller(Yellow Question Mark)
Hardware ID: PCI\VEN_1022&DEV_7812&SUBSYS_18A6103C&REV_03\3&2411E6FE&0&81
Hardware ID: PCI\VEN_1022&DEV_7812&SUBSYS_18A6103C&REV_03\3&2411E6FE&0&80
I've found drivers for my system from ⇗ here (USB 3.0/3.1 Drivers (original and modded)), pointed out to me by Fernando and IntiMD, but after following the instructions on the page (who knows, maybe I messed up somewhere?), I successfully installed the drivers for the Controllers, but I find no devices which accept the drivers in the folder 'for Hub'. The end result is that I have two unknown devices...
Other devices > [Yellow Question Mark] Unknown Device > Device Instance ID: AMDUSB30\ROOT_HUB30\4&8A736FC&0
Other devices > [Yellow Question Mark] Unknown Device > Device Instance ID: AMDUSB30\ROOT_HUB30\4&A1279A9&0
But I can't find drivers for these two. I tried searching DriverPacks with the Devices Instance ID, but it gives an error saying that the installation failed ⇗ cause the .inf file was made for Windows 95 or later (which doesn't make sense cause Windows XP IS after Windows 95). I'd appreciate any and all help on this issue: It's so frustrating to have a perfect Windows XP Setup with just one major flaw, unusable USB ports... Thanks in Advance :D

#4106

diderius6

Yesssa,
now I succeed to install win98SE, XP SP3, Win7, Win8, Win8.1, win10 32 bit from November 2019 on
the Thinkpad T43.
The problem was, that only Win7 likes to stay on the IDE harddisk together with XP.
When XP with ntldr is gone, you can install win10 on the IDE harddisk
Dietmar
EDIT: Seems, like I was happy to early: At the end of the Win10 installation the compi crashes with
Irql not less or equal, hm..

#4107 | Zix | Is there anywhere all latest required files in one bundle? Id like to try on Ryzen, thank you all

#4108

IntiMD

⇗ @AbdullahTrees
⇗ https://www3.zippyshare.com/v/Njphl3Sp/file.html
Replace the original inf file from the 'for Hub' folder with the one in the link. The reason why this strange error happens is that there were no entries for NT 5.1 in original inf.
Let me know if this works, and if it was enough to make it work and behaves stable, then it would be nice to let Fernando know so as to update the pack (or alternatively add a modified package alongside it)

> Zitat von ⇗ diderius6 im Beitrag ¶ #4106

> Yesssa,
> now I succeed to install win98SE, XP SP3, Win7, Win8, Win8.1, win10 32 bit from November 2019 on
> the Thinkpad T43.
> The problem was, that only Win7 likes to stay on the IDE harddisk together with XP.
> When XP with ntldr is gone, you can install win10 on the IDE harddisk
> Dietmar
> EDIT: Seems, like I was happy to early: At the end of the Win10 installation the compi crashes with
> Irql not less or equal, hm..

⇗ @diderius6 What exact Pentium M Dothan CPU model does this laptop have? In thinkwiki it is to be said that bunch of CPU models doesn't report the PAE and NX flags support, even though the core is said to support said flags.

> Zitat

> Physical Address Extension (PAE)
> Most modern Linux distributions use PAE kernels which will fail to boot if this feature is not present in the CPU. The Dothan core is said to support PAE even though it doesn't report the feature to the operating system. As a workaround, kernel parameter forcepae can be used to successfully use PAE-kernels on any Dothan core.
> All second generation Dothan models with a 533 MHz FSB and some newer model first generation Dothan cores with a 400 MHz FSB do report PAE and NX in their CPU flags. All others must use the workaround.
> Note: As a direct result, when the CPU flag PAE and NX (No eXecute, the XD-Bit) is not reported, 32-Bit-Windows starting with Windows 8 will also not run (Windows doesn't have a forcepae option), leaving 32-Bit Windows 7 the last supported Windows operating system on Pentium M CPUs before the second generation Dothan core.
> source:⇗ https://www.thinkwiki.org/wiki/Intel_Pentium_M_(Dothan)

You might also want to fool around with the other supported Windows 10 builds (especially the LTSC or LTSB ones: 2019 (1809), 2016 (1607) and 2015 (1507); Check these links for comparision of each editions: ⇗ https://old.reddit.com/r/Windows10LTSC/wiki/comparison + ⇗ https://forums.mydigitallife.net/threads...019-ltsc.79358/; Worth lurking the entire LTSC wiki on reddit. nice unofficial knowledge base)

#4109

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4106

> The problem was, that only Win7 likes to stay on the IDE harddisk together with XP.
> When XP with ntldr is gone, you can install win10 on the IDE harddisk

⇗ @diderius6 ....Dietmar, the problem seems to be with the EFI BIOS used by W10. It will allow W7 to be dual booted but not XP. My W10 installation initially used a BCD boot system but somehow, while playing with it, I converted it to an EFI bios. Now I am looking for a way to convert back to a BCD boot system. IF W10 is BCD-based it should allow a dual or triple boot with XP, would it not?
I use separate drives for each OS. I have not yet tried to triple boot them from the same boot menu and I don't care if I do. I am currently dual booting W7 and W10, and when I need XP, I unplug W7 and W10 while running XP by itself.
Here's an article that talks about this situation.
⇗ https://neosmart.net/wiki/easybcd/dual-boot/windows-xp/installing-second/

#4110

diderius6

⇗ @IntiMD ⇗ @gordo999
I have the Pentium M 770, 2.13 GHz with FSB533 (TDP: 27 W), with XD-Bit.
I put all UEFI away during install.
Now I think, the BSOD very late during install of Win10 vers. 1909
belongs to this special Win 10 32 bit version.
Win 8 pro 32 bit I can install without problems on the T43, see photo
Dietmar
⇗

## Page 275

#4111

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4110

> Now I think, the BSOD very late during install of Win10 vers. 1909
> belongs to this special Win 10 32 bit version.

⇗ @diderius6 ...I am trying to install ver 1909 right now as an update on an old laptop. Don't have BSOD but it complains about my system being on a USB device. Research tells me it's likely related to old updates being incomplete and one solution is to run the W10 troubleshooter for Windows Update. It did find issues.

#4112

XPLives

⇗ @Fernando, ⇗ @Lost_N_BIOS
--- Win-Raid moderator attention needed ---
This XP / 2003 32-Bit thread is already bloated enough to not include 98SE posting.
Off topic thread/posts must be moved to where it will be much easier to find and flourish.
Move the following posts to the proper designated thread:
OS related Topics » DOS/Windows 3.X/9X/ME - Retro Gaming
⇗ DOS/Windows 3.X/9X/ME - Retro Gaming
New thread title of start post #4084 to be #1:
Post #1 (original #4084)
Installing 98SE to Windows 10 - ThinkPad T43
Creator:
Diderius6
All Posts below to be relocated:
Post #1
#4084 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
#4095 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
#4098 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
#4099 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
Post #5
#4100 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
#4101 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
#4102 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
#4105 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
Post# 9
#4108 | RE: Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
My Dencorso 2 cents $0.02.
XPLives
EDIT by Fernando: I have partly done what you requested. The previous posts #4084, 4095, 4098-4102 and 4105 have been moved into a separate thread named "[How to] Install Win98 onto a ThinkPad T43" within the Sub-Forum "DOS/Windows 3.X/9X/ME - Retro Gaming". Regarding the other posts you have listed I am unsure, because they are about other Windows Operating Systems as well.

#4113

ruthan

Well i personally liked it more before only with space moderation.. sometimes wild is better. I though about why such thread is no elsewhere in positive way.. for example on MSFN.. and it was because of lack of moderation.
I dont mind few post about quantum computers here etc. I dont modere anything, unless some vulgar posts. That attitude to judge someones posts and telling him that some post is not good enough, it dont feel right to me.
Try to clean 4000 post thread, good luck.

#4114

Fernando

> Zitat von ⇗ ruthan im Beitrag ¶ #4113

> I dont modere anything, unless some vulgar posts. That attitude to judge someones posts and telling him that some post is not good enough, it dont feel right to me.

Nobody told anybody, that his/her post(s) are not good enough, but each Forum member should pay attention, that his/her contribution matches the title of the thread and the title of the related Sub-Forum.
A Forum visitor, who wants to know how to get Win98 installed onto a modern PC/notebook, will probably not search within this thread.

#4115

XPLives

⇗ @ruthan

> Zitat von ⇗ ruthan im Beitrag ¶ #4113

> Well i personally liked it more before only with space moderation.. sometimes wild is better. I though about why such thread is no elsewhere in positive way.. for example on MSFN.. and it was because of lack of moderation.
> I dont mind few post about quantum computers here etc. I dont modere anything, unless some vulgar posts. That attitude to judge someones posts and telling him that some post is not good enough, it dont feel right to me.
> Try to clean 4000 post thread, good luck.

In your original post, "1) This thread is behemoth, can some make some Wiki or at least some Google shared docs with some main info and keep there links to all important and proven working patches? Its disable by Forum rules, we can make at least some mega summary post amd the start of some thread.
Maybe we can add some collection of lastest XP drivers or something like that."
You were complaining about the thread being a behemoth which I do not disagree. The XP thread which was previously not titled "Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware" but later I suggested it to be renamed to the current thread title. But In addition, the thread posts was around 2500 then and I wanted to help separate the thread into searchable sub-topics at the time which it could be broken into such as ACPI, USB 3.0, and a few others I forget at the moment. However since the moving of such messages required moderator access it would not be possible as well as voiced opposition from Dencorso and Diderius6 said it would kill the thread so I was unable to do what you had hoped and why the thread is the way it is currently. So unfortunately this burden you are expressing cannot be resolved. I no longer have the time to carefully dissect it properly and it has since then bloated to 4000 messages. So if you had wanted the proper separation of the thread into a more readable and manageable form for users that time seems to have passed when you were away. :(
Had more users spoken up in support of me fixing the thread properly what you asked for would have happened. Sorry is all I can say.
The moving of those 98SE OS type messages is good as even other OS threads could use activity. It is already tough enough for a newcomer to read through 4000 messages to get the necessary information they wanted. As for the off topic post about quantum computers if it is a single post I'm sure it will slip by and probably not a huge issue. But since the series of 98SE related posts and followups began in rapid succession it was better to suggest moving it into the appropriate OS sub topic that was already created and available over a year ago to be used should more follow up posts related to the same 98SE topic be added to that topic would be surely welcomed there. There was a danger that more follow up 98SE type posts would continue to be added into the XP / 2003 thread. Why make it harder for newcomers to now have to sift through both 98SE and XP messages? Now it is properly relocated by Fernando people can find and post more on the same topic as much as they want. So only small preventative measures can be done if caught early than waiting weeks/months when hundreds of posts have happened. This time it was caught early enough.
Also your post should have been moved too but there was XP related comments so I assume Fernando decided it was in the middle and left it there. Since I had intended to respond to your post regarding the 98SE subject to prevent adding more bloated messages to the XP thread now I cannot. I might try and quote those parts of the message and post in the 98SE subtopic for you.
I do disagree that MSFN does not moderate their own threads. I've seen plenty of messages posted there in the wrong topic moved or deleted. In fact I think they are more stringent on this. It's also possible they have become more relaxed on this because most of the moderators are funding the donations to keep that site alive. But I've seen them ban people who don't follow the rules so I disagree again they don't pay attention.
2) X299 should work with XP 32-Bit. The XP Pro 64-Bit would require a modded ACPI.sys or BIOS MOD. Again this is speculation based on how Z370 works which is newer than X299.
3) PAE. Just use the standard XP 32-Bit and Ramdrive software or use Server 2003 32-Bit with proper PAE memory access. Don't mess with the hacks unless you don't intend it to be used on a stable 24/7 system or just used for non serious nature.
4) i-218 I believe driver exists. i-219 No luck.
5) Try using nVidia and AMD (1 card each). Should avoid driver conflict. Although I noticed last AMD driver causes problem with nVidia cards BSOD.
6) Just use USB 3.0 PCIe card if you can afford. You can try modded USB 3.0 driver from DK but ymmv on stability/functionality.
7) Not sure why both. Usually either MPS or ACPI is shown.
8) Will address in a 98SE post for you later.
9) Can't answer no hackintosh experience yet.
10) Not sure what you are asking here can you rephrase? All I can say is PS/2 Keyboard Port on Rear Motherboard you should be fine.
11) This is caused by the integrated Intel HD Graphics Shared Memory setting.
12) Will address in a 98SE post for you later.
13) B75 should be Ivy Bridge so Z77 should be similar - Which cards did you test? -- This may need to be expanded further and address in a 98SE post for you later.
14) Working on making V5 work on Coffee Lake not emulated.
15) Realtek NIC has MAC OS driver too.
16) No haven't looked. Try looking for earliest PCIe 10Gb NIC released.
17) Could not get it to recognize internal PCIe SATA card. You had success?
18) Just stick to SATA optical disc drive. USB will create possible issues and USB 4.0 will most likely.
19) Paragon no longer sells this product. Also if I remember correctly you cannot boot off the drive over 2TB in size correct?

#4116

diderius6

Hi,
I just install Win10 32 bit version 1507,
which is the very first one from summer 2015. It installs without any problem on the Thinkpad 43.
When you take a look at the differences in those Win10 versions,
oha, they changed a lot, see
⇗ https://en.wikipedia.org/wiki/Windows_10
Even needed ram size has changed from 1 GB => 2 GB
and free space on harddrive from 16 GB => to 32 GB
and support for older CPUs is gone
Dietmar
PS: 3Dmark2001 shows always maximal values only under XP SP3, no matter what other OS tell..
⇗
This 1507 version of win10 32 bit is not slow on this compi from feeling!
EDIT: On a T42 with Pentium M 735 processor 1.7 GHZ (Dothan) it is not possible to install any Win10 32 bit.
Very first in the setup process via DVD it claims, that you have to use a processor with RAM > 4GB PAE enabled.

#4117

ruthan

> Zitat von ⇗ Fernando im Beitrag ¶ #4114

> > Zitat von ⇗ ruthan im Beitrag ¶ #4113

> > I dont modere anything, unless some vulgar posts. That attitude to judge someones posts and telling him that some post is not good enough, it dont feel right to me.

> Nobody told anybody, that his/her post(s) are not good enough, but each Forum member should pay attention, that his/her contribution matches the title of the thread and the title of the related Sub-Forum.
> A Forum visitor, who wants to know how to get Win98 installed onto a modern PC/notebook, will probably not search within this thread.

Well, you are the boss, i undestand what are of saying.. but it has theory and praxis problems.. or at least clash of few good ideas and intentions.. Some small adjustment you my original sentence would be not good enough for this thread :) That is how i actually meant it.
For example there were some Diderius post about notebook bios downgrading.. and you can say that its not WinXP related, but in wider context i was important to know, its progress because it blocked some XP fixing progress.
Or now, i would like to post some lines about MacOS and Win98, because its part of my multiboot projects which are related to XP too, because all OSes has to work on machine and it has some consequences and synergii.. Boot how to multiboot problem divide to OS related threads? I never would be only about 1 OS, you can say that you can make whole other thread.. but most of the info this would be related to some OS, in this case to XP.
I simply trying to say pleas dont try to overmoderate it.. it was nice. I can speak for other, but there people as me which are quite sensitive to it and love much openness, freedom as is possible.
End of philosophy intermission.

#4118

ruthan

⇗ @XPLives
1) I wasn't complaining.. i thing that i described reality, that is why there are lots of new people, which are repeatly asking the same, because they dont want to spend at least day to read all messages.
I thing that some summary document with link to this discussion will not kill this thread i think it could help, i personally have problem to keep track all files and and i had to same them to my system with number of post, where it they were posted.. There were also some replacements to not use old files, which is not bad idea, but it made tracking even worse.
I thing that bigger question is who will create such document, its few hours of work for first version and some additional work later.. I was probing if there is not big opposition to it at first.
MSFN - i would say that is more professional.. with good and bad thing that comes with that.. i like it less professional, less strict at least in my inner feeling.. i often a bit under pressure even with its file uploads limit (i dunno if this the same), but i was 5/10 MB per user and all posts.. and there was some problem to include Dropbox pictures to post to bypass it.
2) That my idea too, but i would love to hear some success story, before i would again first lemming to try it, it could be quite expensive.
3) PAE as wrote old Dibya PAE patch, hack.. how you name it, made system smoother (maybe less swapping, maybe memory resource management worked differently - i dunno design details).. and less stable too, yeah im greedy so i would like to have bough, or lets say both alternatives to choose from Boot.ini. Ramdisks are nice, but for me smooth system is much better.
4) Some link would be nice (ideal material for that wiki:), otherwise its shame that manufacturers in specs are wring just Intel Gigabit, usually no details..
5) Ok thanks for info, i dont have enough slots and i bit afraid how games will reacts.. because there is probably nothing like OS level utility to make some videocard primary for games.. it has also some noise and power negatives.. if there is no way to make it running on 1 card or 2 nvidias, i will pass. I know some bios have some multi monitoring through iGPU, but it also seems as lots of hassle.. like optimus on Notebooks. I dunno if it ever worked in XP. If im not wrong Intel bough for it Lucid Virtu or something like that and it wasnt success story.
6) Too much shortcuts - what is "DK but ymmv on stability/functionality".. one card, integrated Intel would be nice, because almost anybody have it like Realtek HD and NIC. Otherwise i like ASM cards, they where working on XP with even MB, even before modding, but i found only hard with 2 USB ports (i dunno how much hassle is use USB3 hub?) Opposite are Nec/Renesas cards.. i saw one with 4 USB ports, 1 internal and even with USB3 header for frontpanel.. I never saw ASMedia card with lots of ports.
10) Newer MBs without any PS/2 ports.. its new trend. But there are some PCI-E PS/2 cards.. but i dunno if they are working within some happy scenarior or just some chinese ebay not working stuff, it they are legit.. it would nice to make them working with WinXP installation and OS.
11) I would like to see some proof.. for example i had it X99.. if my memory is working there is not even integrated iGPU within 5960X which i had. I tried lots of external videocards, even some few MBs PCI-E and i still had 900 MB and some Supermicro manual.. for which i dont have now link, really the end explained why, there are some memory areas / spaces.. and they are in 4GB zones, because nobody counted with 32 bit OS usage, i thing that this problem was present even with 32 bit Linux.
13) I already linked Vogons thread about it.. there is my compatibility sheet in addition and Kamerat chipset vs videocards matrix (quite few test results are from me) - there are in these threads. For such only need MB boards, are only 2 working lines of cards.. Yamaha 7x4 and Aureal Vortex 1/2 nothing else.
⇗ https://docs.google.com/spreadsheets/d/1...c2xhYKK4l0/edit
⇗ https://docs.zoho.com/sheet/published.do...04bf92a9209e034 // Multiple tabs - as in Excel.
⇗ https://www.vogons.org/viewtopic.php?f=61&t=61044 // My ultimate thread about that, lots of bla, bla..:)
14) V5 - do you need Vooodoo 5 - in some PCI variant?
15) Intel too, even USB- Realtek lans.. but i never tough that its good idea had two 2 nics in machine with connected cables.. which are not in some team etc.. because was afraid what they would be stealing of connection and switching.. but yeah its true, that you can disable them in Windows, in Linux you can blacklist one too.. Im not only sure about router mac address to force static ip address.. if you can 2 Mac address to 1 static ip - i thing that minimally some routers not allow it.
16) There are some old Intels 10Gbit for servers, but they are i a bit expensive on ebay 50-100$ to just try, but once there would be cheaper 10Gbit router, it would make sense.. were stuck with 1Gbit for how much 15 years or so?
17) I never had problem there, its like SCSI, just connected only disc on it and it booted like from on board IDE port.. At least some Z97 MBs, had some controller even integrated on board.. these were fancy times - where on MBs were multiple USB3 controllers from different vendors and 2 storage controllers. I still have Z97 Asrock Extreme 4 MB machine with such combo and Marwell controller.. which is even booting from M.2 in PCI-E slots and its able to make 2500 MB/s, on board M.2 slot is limited to 1GB/s. its storage controller lovers paradise.
18) I did lots of reinstall so multi booting USBs (Sardu was first i thing which massively did it) are great with CDs i always a bit afraid that problems is connected with some reading errors.
19) AFAIK i read somewhere that Paragon guys are some ex Russian military guys which back in time made some Russian Dos or something like that.. Try to mail them, they will probably bundle it to some other product. XP cant boot from GPT, it needs MBR. I had this issue always connected with EFI, because it came with same time, i thing that EFI is needed to boot form GPT, there are if im not wrong some work around.. same as for M.2 boot for MBs which are not working it. agent_x007 on Vogons.. i thing had something like boot clover from some flash to boot M.2.. I saw him in this thread too.
Im just using GPT loader for data disk and here 4 TB disc is working fine.

#4119 | ruthan | ⇗ @diderius6 Nice, if remember correctly somewhere around 16xx version, MS just ditched silently AGP support and maybe other stuff..
#4120 | diderius6 | ⇗ @ruthan The whole chipline Pentium M was canceled on newer win10 versions, see ⇗ https://msfn.org/board/topic/177957-unsu...comment-1156627 Dietmar

#4121

gordo999

> Zitat von ⇗ ruthan im Beitrag ¶ #4117

> I never would be only about 1 OS, you can say that you can make whole other thread.. but most of the info this would be related to some OS, in this case to XP.

⇗ @ruthan ...since I joined this thread, not very long ago, the focus has been on getting XP working on 'modern systems'. From my understanding it's not just about XP itself. I got into a disagreement with one poster over what 'modern' meant and I realized afterward that my focus had been too narrow. So, I understand your point.
On the other hand, ⇗ @diderius6 has spent 99.99% of his time focused on modding files for XP on modern systems, as have the other regulars in this thread, and he has done great work. He has also tried to make the modded files work on different XP systems then he branched out slightly to try it on W7 and W98 systems. In my opinion, he has earned the right to introduce off-topic discussion if he feels like it, and when he has done so, it has a been brief. In general, no one has gone off-topic most of the time.
I can understanding ⇗ @Fernando narrowing the focus. I mean, look at the length of the thread just focusing on the topic. It could get totally out of control if the focus was lost. I was attracted to the group because I understood the difficulty of getting XP to run on a modern system like my Intel B360 chipset. I had been told it could not be done and I am amazed how easily it could be done with a modded ACPI and Storport driver. The process of development of the modded drivers has come from certain guys focusing for lengthy periods at a time on the problems. Had this group been open to a general discussion on XP on any system, I don't think that would have happened nearly as quickly.

#4122

gordo999

> Zitat von ⇗ ruthan im Beitrag ¶ #4118

> I wasn't complaining.. i thing that i described reality, that is why there are lots of new people, which are repeatly asking the same, because they dont want to spend at least day to read all messages.

⇗ @ruthan ...that's pretty well what I did and I did it because I have belonged to a reversing group for 15 years who won't even talk to you unless you demonstrate that you have educated yourself on the subject.
I am not speaking through my hat. I am currently involved in trying to mod files from a reversing POV and it can get frustrating real fast. There is a steep learning curve and even though I have experience with import tables it's like learning a new language when you start dealing with export tables and two different OSs. I am spending hours and hours just researching and to hear you complain about having to read through this entire thread a bit amazing. Not knocking you, just wondering how you can learn anything about this topic without doing that. I can't count the number of times I have been forced back to the bottom of the hill to start climbing a steep learning curve. That's why I have little patience for those who show up asking for links without showing any other rinterest or ability in the field.
Over the years, I have noticed new people showing up at our reversing site asking for cracks, which we don't do. We do reversing for the joy of it but we are willing to help newbies who want to learn. The next step up from those asking for cracks is people who want a quick fix for a crack. They are willing to do a minimal amount of work but they want everything right now. We won't help them till they show they have done the work and are stuck on a certain point.
It bugs me personally when people suddenly show up asking for links. It's not like you need to read the entire thread, most of the links required are in the last third of the thread. You could skim through those pages and find not only the links, but why they work and what to watch for. I mean, why should the experts in here, and I am not one of them, feel obliged to stop what they are doing to produce links for those to lazy too dig for themselves. It amazes me that the experts do take the time to supply the links, showing they are dedicated people. I also find it rude to make such requests without otherwise participating in the group.
I learned by doing. The first time I fired XP up on my 300-series chipset, I got nothing. It's what I expected.Then I graduated to an 0XA5 error which I learned was related to an ACPI problem. One of the modded ACPI files from this group fixed that. Then I graduated to an 0x7C error which turned out to be a SATA driver issue. Another modded driver from here fixed that. Typically, what you get from people demanding links to modded files is them coming back complaining about other errors and how to fix them. In other words, they have no idea what they are doing and need someone to hold their hands and lead them through it.
I don't even mind doing that much of the time provided that person is capable of helping themselves. Many are not and it gets tedious going over and over the same subject when you know that person has little interest in learning, or helping themselves. In other words, you need to distinguish the leechers from those willing to learn by doing their own work. I would suggest that reading through this thread to get a grasp of what is going on is a good start. You can skim through it, no need to read each and every post.

#4123 | Illen | Regarding the whole UEFI booting topic, this looks like a very interesting project: ⇗ https://github.com/maharmstone/quibble A custom Windows UEFI bootloader (made by the developer of WinBtrfs project), it is compatibe with each Windows version from XP to latest 10 (both x86 and x64). The list of planned features looks interesting as well. It is in early state at this point, and might not work in some cases, but still I think it is definitely worth a mention.

#4124

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #4121

> > Zitat von ⇗ ruthan im Beitrag ¶ #4117

> > I never would be only about 1 OS, you can say that you can make whole other thread.. but most of the info this would be related to some OS, in this case to XP.

> @ruthan ...since I joined this thread, not very long ago, the focus has been on getting XP working on 'modern systems'. From my understanding it's not just about XP itself.

Gordo999, yes you are a newcomer in a sense so you "missed" a lot of history of how these XP threads began. I'll try to summarize it as best as I can.
Originally I was the only one who created the early XP threads relating to installing XP on SkyLake Z170 and later Modern Hardware on Win-RAID. This was way back in 2017. Other than the larger XP thread
"[Guide] Integration of Intels AHCI/RAID drivers into a Windows XP/W2k3/W2k CD"
by Fernando on how to install the SATA modified drivers there was no presence. In fact there was no specific OS Sub-Group then. I asked Fernando to create them and I gave him the names to use and he obliged:
This is how the "OS related Topics" Sub-forum was born. Part of the reasoning was MSFN did not have a DOS dedicated category and most topics there were not actually geared towards gaming. I focused more on the technical part of getting XP installed on Modern Hardware here and simplifying it. There was no real gaming discussion. Only recently I renamed my older topics because the large XP thread kind of took place of that and I've started to refocus back to gaming because all this technical stuff can get boring after 3 years.
[OS related Topics]
Windows 8-10/Server 2012-2019
Windows 7/Vista/Server 2008
Windows XP/2000/Server 2003
DOS/Windows 3.X/9X/ME - Retro Gaming
The thread you now know as "Windows XP/2000/Server 2003" was meant to be the new name of the thread I was going to reorganize properly that would have addressed an outline on the first post and links to specific important posts. The original name of the thread was actually a post created by: deSSy2724 called "Windows XP SP3 32bit and modern PC parts". It was a random user who came and posted for help.
What happened later was diderius6 and Mov AX, 0xDEAD began switching it into an ACPI discussion. Later diderius6 used it as a dumping ground on his ACPI research. I think around 1500 Messages time it shifted to USB 3.0.
This is the point where I had asked Fernando to separate the thread but it was not done so it continued and bloated to around 2500. At this point I asked again and unfortunately due to Dencorso's opposition and Diderius6 saying it will kill the thread it was not done.
So while a post or two off topic may be okay it would make better sense to post it into a whole new thread on the material that way it's not making the congestion worse for new users to read through assuming it began taking a life of its own into hundreds of posts on 98SE in a week within the XP thread.
There was a lot of Windows 98 discussion in a series of post and there is already a dedicated Sub-Forum for it called "DOS/Windows 3.X/9X/ME - Retro Gaming" which would a better fit for them and "NONE" of the original posts were deleted but moved.
So stop harshing "Fernando" about his decision. And please remember Fernando is retired. Had I waited for it to bloat to 100 message or more it would be too much work for him. If I was the moderator I would have done it transparently. I asked him or LNB to move it because the last two times I asked Fernando when they were not done early enough and allowed to continue to explode and often times we now find comments on "where is this driver" kind of post quite often. Had I had user support on fixing it this new Main thread would probably be around 1600 messages instead of 4000+ and the others topics USB 3.0 and others would have their own thread and the 1st post of the intended renamed "Windows XP/2000/Server 2003" thread would have had a 1st post that addressed all these issues you Gordo999 and Ruthan wanted oi find files easier. So quit complaining about a few posts being moved regarding 98SE. This is a preventative measure and they weren't deleted and no one is stopping you or anyone from posting more content relating to 98SE there. It's also much easier to follow and Diderius6 can post more updates as he is the "creator" of that moved thread so he could change the 1st post into a guide for the Thinkpad T42 if he chose to later.
The biggest problem with the current thread "Windows XP/2000/Server 2003" was I was not able to split it into different threads and use the 1st post to create an outline. I wanted both Diderius6 and Mov AX, 0xDEAD to write a guide on the modding BIOS process to fix the ACPI issues that other users could follow. And later Daniel_K could have created his own thread for modding USB 3.0 drivers and how to do it.
I know for some it's more interesting to just accept a modified driver and test it but to me this isn't good enough. But I'm more interested in how to do it myself and maybe improve upon it should one day these people are no longer here due to death or just not visiting any longer others can continue modifying it or this technique will be lost.

> Zitat von ⇗ gordo999 im Beitrag ¶ #4121

> On the other hand, @diderius6 has spent 99.99% of his time focused on modding files for XP on modern systems, as have the other regulars in this thread, and he has done great work. He has also tried to make the modded files work on different XP systems then he branched out slightly to try it on W7 and W98 systems. In my opinion, he has earned the right to introduce off-topic discussion if he feels like it, and when he has done so, it has a been brief. In general, no one has gone off-topic most of the time.
> I can understanding @Fernando narrowing the focus. I mean, look at the length of the thread just focusing on the topic. It could get totally out of control if the focus was lost. I was attracted to the group because I understood the difficulty of getting XP to run on a modern system like my Intel B360 chipset. I had been told it could not be done and I am amazed how easily it could be done with a modded ACPI and Storport driver. The process of development of the modded drivers has come from certain guys focusing for lengthy periods at a time on the problems. Had this group been open to a general discussion on XP on any system, I don't think that would have happened nearly as quickly.

So while Diderius6 and many others have earned to right to post off topic stuff you also have to know when it should be moved so it doesn't get into a situation where it is harder to separate the posts without disturbing other posts. For example a lot of the issues when people attach file to posts or links to other post numbers could be affected if these groups of 98SE related posts were moved much much later.
If this thread was only 30-50 messages in size maybe nothing would have been done. You have to recognize it is now over 4000 posts in size and how long it will take for a new user to sift through that and if they don't understand English as their first language how much longer it will take.

> Zitat von ⇗ gordo999 im Beitrag ¶ #4121

> I got into a disagreement with one poster over what 'modern' meant and I realized afterward that my focus had been too narrow. So, I understand your point.

You're probably referring to YuriyCN. He's a very stubborn and persistent user and was here in the beginning when my XP threads were born. He wanted the USB 3.0 ports working but even at the time the best recommendation was to use a USB 3.0 PCIe card to solve his problems. And I wondered why hasn't he simply bought one during the 2 years since then till now. Hopefully the DK driver he's using is working well for him but I really don't know how reliable it is for him.
The term "Modern" meant Z170+. That was the intent back then when I wrote "Modern" in the XP thread titles. So he is correct in posting to still finding help with his Z170. It doesn't mean it has to be a Z370/Z390. In fact I suppose if you really wanted to know what I considered modern it would be SkyLake, Kaby Lake, and Coffee Lake and whatever next gen Intel puts out in 2020. But today the meaning is anything that XP can't be installed to and work properly with ACPI. I originally had XP threads targeted for SkyLake, Kaby Lake, and then Coffee Lake.
So the thread you know as "Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware" is incomplete in the way I had intended. The new name was left on it instead of reverting it back to the original deSSy2724 thread called "Windows XP SP3 32bit and modern PC parts".
Now you have your answer as to what "Modern" meant and to stop blaming Fernando as if he did not listen to me in the beginning there would be NO XP THREADS to complain about! In the beginning I also did a lot of redirecting to this site to drive traffic as best as I could. It seems to have paid off and eventually diderius6 began posting frequently here and also advertising the threads. But it was a real slow start for a long time.
XPLives

#4125

ruthan

> Zitat von ⇗ Illen im Beitrag ¶ #4123

> Regarding the whole UEFI booting topic, this looks like a very interesting project: ⇗ https://github.com/maharmstone/quibble
> A custom Windows UEFI bootloader (made by the developer of WinBtrfs project), it is compatibe with each Windows version from XP to latest 10 (both x86 and x64). The list of planned features looks interesting as well.

State - proof of concept, no real list of features, but big todo list and donate link.. - Im skeptic.

## Page 276

#4126

XPLives

@Ruthan

> Zitat von ⇗ ruthan im Beitrag ¶ #4118

> @XPLives
> 1) I wasn't complaining.. i thing that i described reality, that is why there are lots of new people, which are repeatly asking the same, because they dont want to spend at least day to read all messages.
> I thing that some summary document with link to this discussion will not kill this thread i think it could help, i personally have problem to keep track all files and and i had to same them to my system with number of post, where it they were posted.. There were also some replacements to not use old files, which is not bad idea, but it made tracking even worse.
> I thing that bigger question is who will create such document, its few hours of work for first version and some additional work later.. I was probing if there is not big opposition to it at first.
> MSFN - i would say that is more professional.. with good and bad thing that comes with that.. i like it less professional, less strict at least in my inner feeling.. i often a bit under pressure even with its file uploads limit (i dunno if this the same), but i was 5/10 MB per user and all posts.. and there was some problem to include Dropbox pictures to post to bypass it.
> 2) That my idea too, but i would love to hear some success story, before i would again first lemming to try it, it could be quite expensive.
> 3) PAE as wrote old Dibya PAE patch, hack.. how you name it, made system smoother (maybe less swapping, maybe memory resource management worked differently - i dunno design details).. and less stable too, yeah im greedy so i would like to have bough, or lets say both alternatives to choose from Boot.ini. Ramdisks are nice, but for me smooth system is much better.
> 4) Some link would be nice (ideal material for that wiki:), otherwise its shame that manufacturers in specs are wring just Intel Gigabit, usually no details..
> 5) Ok thanks for info, i dont have enough slots and i bit afraid how games will reacts.. because there is probably nothing like OS level utility to make some videocard primary for games.. it has also some noise and power negatives.. if there is no way to make it running on 1 card or 2 nvidias, i will pass. I know some bios have some multi monitoring through iGPU, but it also seems as lots of hassle.. like optimus on Notebooks. I dunno if it ever worked in XP. If im not wrong Intel bough for it Lucid Virtu or something like that and it wasnt success story.
> 6) Too much shortcuts - what is "DK but ymmv on stability/functionality".. one card, integrated Intel would be nice, because almost anybody have it like Realtek HD and NIC. Otherwise i like ASM cards, they where working on XP with even MB, even before modding, but i found only hard with 2 USB ports (i dunno how much hassle is use USB3 hub?) Opposite are Nec/Renesas cards.. i saw one with 4 USB ports, 1 internal and even with USB3 header for frontpanel.. I never saw ASMedia card with lots of ports.
> 10) Newer MBs without any PS/2 ports.. its new trend. But there are some PCI-E PS/2 cards.. but i dunno if they are working within some happy scenarior or just some chinese ebay not working stuff, it they are legit.. it would nice to make them working with WinXP installation and OS.
> 11) I would like to see some proof.. for example i had it X99.. if my memory is working there is not even integrated iGPU within 5960X which i had. I tried lots of external videocards, even some few MBs PCI-E and i still had 900 MB and some Supermicro manual.. for which i dont have now link, really the end explained why, there are some memory areas / spaces.. and they are in 4GB zones, because nobody counted with 32 bit OS usage, i thing that this problem was present even with 32 bit Linux.
> 13) I already linked Vogons thread about it.. there is my compatibility sheet in addition and Kamerat chipset vs videocards matrix (quite few test results are from me) - there are in these threads. For such only need MB boards, are only 2 working lines of cards.. Yamaha 7x4 and Aureal Vortex 1/2 nothing else.
> ⇗ https://docs.google.com/spreadsheets/d/1...c2xhYKK4l0/edit
> ⇗ https://docs.zoho.com/sheet/published.do...04bf92a9209e034 // Multiple tabs - as in Excel.
> ⇗ https://www.vogons.org/viewtopic.php?f=61&t=61044 // My ultimate thread about that, lots of bla, bla..:)
> 14) V5 - do you need Vooodoo 5 - in some PCI variant?
> 15) Intel too, even USB- Realtek lans.. but i never tough that its good idea had two 2 nics in machine with connected cables.. which are not in some team etc.. because was afraid what they would be stealing of connection and switching.. but yeah its true, that you can disable them in Windows, in Linux you can blacklist one too.. Im not only sure about router mac address to force static ip address.. if you can 2 Mac address to 1 static ip - i thing that minimally some routers not allow it.
> 16) There are some old Intels 10Gbit for servers, but they are i a bit expensive on ebay 50-100$ to just try, but once there would be cheaper 10Gbit router, it would make sense.. were stuck with 1Gbit for how much 15 years or so?
> 17) I never had problem there, its like SCSI, just connected only disc on it and it booted like from on board IDE port.. At least some Z97 MBs, had some controller even integrated on board.. these were fancy times - where on MBs were multiple USB3 controllers from different vendors and 2 storage controllers. I still have Z97 Asrock Extreme 4 MB machine with such combo and Marwell controller.. which is even booting from M.2 in PCI-E slots and its able to make 2500 MB/s, on board M.2 slot is limited to 1GB/s. its storage controller lovers paradise.
> 18) I did lots of reinstall so multi booting USBs (Sardu was first i thing which massively did it) are great with CDs i always a bit afraid that problems is connected with some reading errors.
> 19) AFAIK i read somewhere that Paragon guys are some ex Russian military guys which back in time made some Russian Dos or something like that.. Try to mail them, they will probably bundle it to some other product. XP cant boot from GPT, it needs MBR. I had this issue always connected with EFI, because it came with same time, i thing that EFI is needed to boot form GPT, there are if im not wrong some work around.. same as for M.2 boot for MBs which are not working it. agent_x007 on Vogons.. i thing had something like boot clover from some flash to boot M.2.. I saw him in this thread too.
> Im just using GPT loader for data disk and here 4 TB disc is working fine.

1) First I didn't say it would kill the thread. But at the time Diderius6 said it would kill the thread but no further explanation of what he meant.
Also the messages are now 4000+ and all these things would be easier if the thread could be separated properly once then a proper 1st page could have been done for each thread. For example ACPI, USB 3.0, et cetera could be moved out and let the main body remain for more general XP troubleshooting help. And trust me had I been able to fix the thread at 1500 messages total I think it would have been much easier. There are too many ongoing life issues right now to devote to it any further. The best I could do was create specific threads of files that I tested that works to make it easier to find. For example DK's ACPI. The person that normally would have handled it has retired. (Fernando). And LNB is already I assume pretty busy with everything else that happens on Win-Raid. The only suggestion I had at the time was to get temporary moderator rights to fix it as fast as I could. So at the moment no matter how much we want something then it's dragged on too long/late to fix it now.
MSFN interface I don't like as much to use compared to here.
2) Well don't do it. X299 runs too hot for fanless. X99 is a better project.
3) Server 2003 is very stable. I think XP is stable too just depends if you need more memory for programs where it suffers. I haven't yet gone the Dibya patch yet.
4) I know some prefer to use onboard rather than internal NIC. If slot real estate is an issue then get USB ethernet instead.
5) Better to get an older graphics card that works in DOS->98SE>XP and use one card only if possible. Less headaches. Set up a separate newer machine for XP->W10 for higher performance.
6) Asmedia lacks 4 port cards which is kind of limiting.
DK = Daniel_K
ymmv = another way of saying test it out and see what happens.
10) PCI-E PS/2 cards are a waste. You have to install the driver to use them. Buy one and see if it is true. I think they will NOT work without the driver installed first.
>>>11) I would like to see some proof.. for example i had it X99.. if my memory is working there is not even integrated iGPU within 5960X which i had. I tried lots of external videocards, even some few MBs PCI-E and i still had 900 MB and some Supermicro manual.. for which i dont have now link, really the end explained why, there are some memory areas / spaces.. and they are in 4GB zones, because nobody counted with 32 bit OS usage, i thing that this problem was present even with 32 bit Linux.<<<
I tried Haswell Xeon CPU in XP (no iGPU). I seem to recall having lots of memory same as Ivy Bridge or more since no iGPU. I will have to double check again sometime. X99 I have not tested maybe list the Make Model you bought tested this? This is a future project of mine.
13)Yamaha 7x4 and Aureal Vortex 1/2
Yes but can either of these cards boot up and play Sound Blaster digitized voice in native DOS not inside 9X Command Prompt window.
And what is the newest Intel / AMD chipset tested to work?
14) Only PCI versions are worth trying but I noticed a lot of PCI cards do not work properly in new motherboards (sound cards) are an example. There is an AGP to PCIe mod / adapter I heard for V5 6000.
15) Realtek ones seems to have better OS support and cost less. There is a dual ethernet port version I saw on eBay if you need team.
>>>16) There are some old Intels 10Gbit for servers, but they are i a bit expensive on ebay 50-100$ to just try, but once there would be cheaper 10Gbit router, it would make sense.. were stuck with 1Gbit for how much 15 years or so?<<<
Which is the Intel Model for it? I'll see if I can find it cheaper.
>>>17) I never had problem there, its like SCSI, just connected only disc on it and it booted like from on board IDE port.. At least some Z97 MBs, had some controller even integrated on board.. these were fancy times - where on MBs were multiple USB3 controllers from different vendors and 2 storage controllers. I still have Z97 Asrock Extreme 4 MB machine with such combo and Marwell controller.. which is even booting from M.2 in PCI-E slots and its able to make 2500 MB/s, on board M.2 slot is limited to 1GB/s. its storage controller lovers paradise.<<<
Link to Make Model you bought that works. You just plug the card in and no need to change BIOS settings and boots up on card?
18) Yeah I gave up on USB method for SkyLake+. Corrupted a 2TB external USB hard drive that I left connected somehow when it wasn't the target. Nightmare data recovery. Optical disc is the safest for newbies.
19) Sticking to MBR still. Best compatibility for legacy OS installations. Maybe one day Windows 11 GPT only installation I will dedicate to GPT.

#4127

Illen

> Zitat von ⇗ ruthan im Beitrag ¶ #4125

> State - proof of concept, no real list of features, but big todo list and donate link.. - Im skeptic.

I assume you can offer a better solution then.

#4128 | schreiberstein | Folks, have you heard about this? A brand new open source bootloader for Windows from XP to 10: ⇗ https://github.com/maharmstone/quibble Cheers, schreiberstein

#4129

ruthan

> Zitat von ⇗ Illen im Beitrag ¶ #4127

> > Zitat von ⇗ ruthan im Beitrag ¶ #4125

> > State - proof of concept, no real list of features, but big todo list and donate link.. - Im skeptic.

> I assume you can offer a better solution then.

This is not good argument.. i dont have to build own car to say that some future promise of some new shinny car are not too much believable.. I have even some training it in fortune telling, i backed some failed Kickstarter projects :)
Do you remember guy which were promising modern Intel HD drivers for XP almost in whole this thread..i can you promise lots of things, if you will send me some donates:)

#4130

Illen

> Zitat von ⇗ ruthan im Beitrag ¶ #4125

> This is not good argument.. i dont have to build own car to say that some future promise of some new shinny car are not too much believable.. I have even some training it in fortune telling, i backed some failed Kickstarter projects :)

I'm not arguing, I'm just waiting for your ideas. Since it seems like you've straight rejected it without even trying, I assumed you've a much better solution. Not sure what is going on here, but last time I was here, this thread was about experimenting, testing, and simply trying to get things working, not criticizing open source projects from a cover...

> Zitat von ⇗ schreiberstein im Beitrag ¶ #4128

> Folks, have you heard about this?
> A brand new open source bootloader for Windows from XP to 10:
> ⇗ https://github.com/maharmstone/quibble
> Cheers,
> schreiberstein

It was mentioned few messages ago, thanks anyway.

#4131

Illen

> Zitat von ⇗ ruthan im Beitrag ¶ #4125

> Do you remember guy which were promising modern Intel HD drivers for XP almost in whole this thread..i can you promise lots of things, if you will send me some donates:)

This is not how things work, you first make and share it, so the interested users can look at the sources or try it and if they like/appreciate it, they might consider a donation. There are freely available bootloader binaries for anyone to try, you are not forced to donate him anything. Mark Harmstone is known from making a Btrfs driver for Windows, and i can assure you, making IFS drivers isn't an easy task at all.

#4132

XPLives

> Zitat von ⇗ schreiberstein im Beitrag ¶ #4128

> Folks, have you heard about this?
> A brand new open source bootloader for Windows from XP to 10:
> ⇗ https://github.com/maharmstone/quibble
> Cheers,
> schreiberstein

For the moment you can still install DOS all the way up to Windows 10. So you would be losing DOS, Windows 3.1, 9X, 2000 if you go this route. If this is targeting UEFI only systems when the BIOS no longer available then maybe this will be interesting down the road to test out.

#4133

ruthan

> Zitat von ⇗ Illen im Beitrag ¶ #4130

> I'm not arguing, I'm just waiting for your ideas. Since it seems like you've straight rejected it without even trying, I assumed you've a much better solution. Not sure what is going on here, but last time I was here, this thread was about experimenting, testing, and simply trying to get things working, not criticizing open source projects from a cover...

I have not idea here, im waiting if someone else would be guinea pig:) I already doing too much stuff too deeply, i just like to game on everything so i have pretty big scope - today i can mess with XP, tomorrow can mess with old Amiga or Power Mac, next day with some old console modding.
There are people which really into XP architecture and boot loading. I just expressed my feeling based on project description, i could be wrong, of course. If description would be better, i would consider to try it myself, even when im not expert.
BTW i saw article about this project later on Phoronix, which has track record to inform about lots of fancy stuff, but are in reality lets say at least problematic, because of Linux enthusiasm. Other web sites are informing that is something working / done, Phoronix has articles that 2 more instruction and card would be OpenGL X.Y version capable for these 2 instruction you can wait and wait.. or informing over something which Michael never personally tested and info is just some authors PR reprint.. So im skeptic.

#4134

ruthan

To some more practical stuff? I have one annoying EFI feature for my multi booting, that is that boot order in Gigabyte bios is not part of bios profiles.. When i do specific boot order for profile and just ignored.
So when want to boot some OS just by changing bios profile, i have also change boot device order.. otherwise it will boot with wrong settings for wrong OS.. i would have to handle it through bootloader like Grub2 - which can its limits too - there is time count down to make a choice.. or machine will not booting into OS- when is started by Wake on Lan magic packet, without input.. i cant boot Mac OS through it (DOS, Win3-Win 10 and all Linux, BSD and Androidx86 are bootable from Grub2).
I wonder boot order is part of bios profiles for other manufactors?
There is also report that for someone else are PCI-E gen1 cards working with Z370 (Geforce 6600) + Ryzen - good news, is it could be also Gigabyte problem, or particular MB problems.. or depend on exact card. I tested Geforce 7600, 8400 and Radeon X800. When i place working card into 2nd, 3rd slot.. and select primary videocard slot to option to its slot (Gigabyte feature), im still getting picture on primary videocard, when i boot with it.. And check Win 10/7 device manager, there is not any new device, it act like there is just empty slot, PCI-E gen 1 cards are completely ignored. When i contacted Gigabyte i got classic - dont try to ask for support of 10+ years old videocard response, that is untested and unsupported.. but Gigabite 1st line of support in almost impregnable.
Good news is that Geforce 750TI (fanless) in 3rd long PCI-E slot is working with present modded files along site with Geforce 1070 (Win7+, MacOS and Linux), as XP GPU, i cant say that is was not working with unmounted files, but i had at the time Geforce 970, so no XP special GPU was needed.

#4135

ruthan

⇗ @XPLives
2) Fanless computers are my big hobby too, i hate to sit beside noise computer or console.. it mess with my concentration to work, game, watch movies etc. But im realistic in this.
But fanless X99 would be touch, unless you will cripple CPU power - X99 was nice for 8 cores CPU - which had 140 TDP, too much any stock Fan cooler, they can make 95W at best.
Here is X99 cpu list with TDPs:
⇗ https://www.msi.com/Motherboard/support/...G-7#support-cpu
You can get 2.0-2.5 GHz slimmer with 6/8 cores, or can get 3.GHz but only 4 cores - ie Haswell-EP E5-2623 v3 (105W) TDP.
X299 is quite similar - 140-160W. I had this problem even with Z370 - with 8700K (95W) it was possible to keep it no reasonable noise with some Noctua <800 PRM fans, but when i upgraded to 9990K - (in specs 95W, but in reality it has up to 165W TDP limit, Intel needed to win, there are lots articles about that:
⇗ https://www.anandtech.com/show/13544/why...ected-tdp-turbo
I had to move to water cooling and because Z370 was not realy designed for that i had to cap some PLx limits to lesser TDP, because otherwise VRM reported up to 120C+ even with fan near of them, i havent nerve to push it further. I know that Gigabyte MBs arent too much good at electric HW level, but when i bough my HW, it was highest possible MB. This was fixed with Z390.
So in reality X299 wouldnt be big difference for me from cooling perspective.
3) Server 2003 - ok its stable, but what about games compatibility, even when you have that - im reporting itself like XP hack? I want to use XP mainly because of problematic XP era games + programs and this could kill whole idea.
4) USB NIC - For WinXP, MacOS and Linux they are fine. Unfortunately these (most of them has Realtek chip) are still not in Linux kernel, was they are not working without heavy modding with Android x86. I spend lots of time with Win 98 USB Lan adapters, i even i thing got right one with is compatible with Win 98 (AX88772_772A), but i never got them working with newer MBs.. but rLoew had some working with other MBs. I think that could be problem with my ultimate Win98 install i has some networking issues even with PCI-E networking.. i had for example Broadcom 5721 working fine there, but after i mess with USB adapters, i wanst able to make them work any more.. I tried adapter to pass through Win98 virtual machine, no luck too. But made Win98 USB sound cards working - but also what some issues, when i was able to reach state of system when they worker for sounds, but not for music and i wasnt able to go back, even with lots of debugging and help of MSFN people.
5) On X58/X79 can run really everything from Dos to Win10.. with multiple videocards per OS.. only number of slots is limit and there are also some PCI-E extender and PCI adapters. Anything newer means no native DOS with sound, no DOS games under Windows 98 (PCI sound cards are still fine in native Win9x games).. unless have still LTP port and LPT2/3OPL for music.. but it still means no games sound, unless have has adlib mode..
More details i already posted to Win98 thread.
I tested it only on Z170, but i thing that on Z370 (if im not wrong even some reported success here) - you can get working sound, network and .. 3D graphics at least with PCI card and if for someone is Geforce 6, with with PCI-E cards.
Of course some PCI videocars are better for dos too.. Otherwise Dos results of new cards and platforms are mixed bug, i have thread and sheet about it:
⇗ https://www.vogons.org/viewtopic.php?f=63&t=62586
⇗ https://docs.zoho.com/sheet/published.do...49606de568c62b9
10) PS/2 addon on cards.. make them working in TextMode install would be real deal, later can still help some people with Intel only USB3 ports, which are not able to make new patches working. I order some USB2 PCI-E controller, which was recommended here, but i never tested one, so far was using Asmedia / Nec (aslo know as Renesas) / Etron USB3 cards for XP.
There are also some LPT cards, maybe they can work with LPT2/3OPL for Dos, it would be probably the same, if with driver and newer OS..
13) Yamaha 7x4 and Aureal Vortex 1/2
FX and FM is fully working as wrote up to X58/X79, about AMD you can find it in Kamerats matrix - VIA chipsets are newest, intel is much more compatible.
16) 10 Gbit - based on some inf files.. Intel X540-T1, Intel X540-T2 should be winners.. now probably eBay prices will go higher:)
17) ASM106x in IDE mode XP install. My bad memory.. Im not really sure, it worked with vanilla SP3, it i had to integrate ASM 106x driver through nLite - which could be done quickly. If you were look for unofficial XP iso with already bundled newer drivers or just pack for integration to your vanilla CD.. it almost always had Asmedia and Marwell drivers included.
Important thing is flash from DOS old IDE boot to controller.. because it comes with AHCI bios in 99% cases.. and its not some inteligent controller, where you can switch between IDE and AHCI mode just in some utility at boot time.
19) If we would be able to boot XP from NVME and GPT, i can get rid of MBR finally. and only use it for Win98 dedicated small drive. 3 primary partitions + extended partion is nighmare - i have quite few of Linux distros on exntended partitions and .. quite a lot Partitions and Imaging softwares - still has bugged extented partition support.
My OS drivers on my machines looks like this - lots of partitions, but less disk as possible, lots of people like os per disk, or use multiple partitions for 1 linux distro i dont. I remember that, my SteamOS - one partition mod was quite successful, becuase default install was 5 or 6 partition madness :)
⇗

#4136

schreiberstein

Haha, I did not see that post. Sorry.
⇗ @XPLives
Well, you can just use two disks, one with MBR and one with GPT and UEFI and then select which one to use at boot.
We still have the choice - and aside from recent Apple computers, I have not heard of mainboard manufacturers getting rid of CSM / BIOS, but I did not check.
I think the future will be a bare metal hypervisor solution, or even just a Linux KVM with GPU and PCI-E passthrough. The performance will probably be even better since the Linux kernel can utilize modern architectures much better in the background and the emulated I/O will also be a speed increase. GPU passthrough effectively means : NO UI LAG.
Cheers,
schreiberstein

#4137

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #4124

> So stop harshing "Fernando" about his decision. And please remember Fernando is retired.

⇗ @XPLives ...thanks for the history but I think you have misunderstood me. I support Fernando's decision and I know he is retired and does not need headaches. I admire Fernando, I am not taking shots at him.

> Zitat von ⇗ XPLives im Beitrag ¶ #4124

> Now you have your answer as to what "Modern" meant and to stop blaming Fernando as if he did not listen to me in the beginning there would be NO XP THREADS to complain about!

Once again, I am not blaming Fernando for anything, I'm on his side. I appreciate your history tour and you're right, I am a newcomer and likely speaking out of turn. If so, I apologize. However, I'm glad this thread has an XP focus.
Furthermore, I am used to the politics than goes on in some forums. I don't want to stick my nose in where it does not belong and I don't want to get into political discussions. You are right, it was YuriCN with whom I had the disagreement but I dropped it abruptly rather than turn it into a flame war.
Thanks again, for your explanation.

#4138

AbdullahTrees

> Zitat von ⇗ IntiMD im Beitrag ¶ #4108

> @AbdullahTrees
> ⇗ https://www3.zippyshare.com/v/Njphl3Sp/file.html
> Replace the original inf file from the 'for Hub' folder with the one in the link. The reason why this strange error happens is that there were no entries for NT 5.1 in original inf.
> Let me know if this works, and if it was enough to make it work and behaves stable, then it would be nice to let Fernando know so as to update the pack (or alternatively add a modified package alongside it)

Thanks, now my Unknown Device has an appropriate name, but the installation failed...
I replaced the .inf with the .inf that was inside the WHQL 'for Hub' folders...
And as far as stable goes, I wasn't really mentioning it as I just wanted to get the USB ports working, but I'm now having abnormal shutdowns ever since I installed the drivers in the 'For Controller' folder, the system sometimes gives a BSOD (DRIVER_POWER_STATE_FAILURE) and at other times it yields a screen like this
⇗
Not exactly what I'd call stable... I think this is due to having a controller driver but not having Hub drivers, and I hope the situation will sort itself out when I find the right hub drivers....
Thanks in Advance, looking forward to any more advice/files you can send me...

#4139 | ruthan | I found my old XP install log - so im now that for USB installation - i was using YUMI - ⇗ https://www.pendrivelinux.com/yumi-multiboot-usb-creator/ Im not sure about other notes - its saming that USB installers are using firadisk image and on it its txtsetup.oem - where is list of drivers which have to load from this image, through F6,F7 - if is in stall image already integrated Firadisk - this will fail - Im not really sure, if i used this or not, which my automatized Nlite installer (but i still have that image, if someone know what to check within).

#4140

diderius6

Today I make a big step forward,
to install any OS from win98, xp SP3, win10 on one laptop,
the Thinkpad T43.
I get a Kingston mSata 480 GB drive and an IDE to mSata adapter from Delock.
Big problem for me was, that I always could only enable 137 Gbyte on this mSata => IDE harddisk.
Even with neweste Bios no chance, also not with win10. The harddrive was always shown as a 128 Gbyte disk.
But now I flash a new modded Bios T43p-1YET65WW_SLIC2.1_no_1802_no_2010.iso and voila,
there is the full mSata disk with 480 Gbyte.
Write and read speed is at the limit of IDE 100, about 93 MByte/s
compi feels fast for any OS
Dietmar
EDIT: I make a copy of whole Bios before I flash, because there is always a risk!
⇗
diderius6 has attached files to this post

- ⇗ T43p-1YET65WW_SLIC2.1_no_1802_no_2010.rar

## Page 277

#4141

ruthan

Other thing which could help. I searched for cheap ebay USB3 to Nvme disk adapter, lots of adapter are only false advertisement M.2 Sata.. which are not working with NVME disk.
This one is working fine..~15 bucks
⇗
Its nice when you want to work with M.2 NVME disc on machine without enough M.2 slots, or when you dont want to place it inside.. or just need clone some other disc to M.2 NVME.
Something like case would be nicer, but i already tested quite few of them.. and its really hit and mis, if device is really NVME.

#4142 | Andalu | XP installs fine on the asus prime Q370M-C/CSM too. On five cards of the Intel 200/300-series chipsets that I tried the only one where I can't install XP remains the asrock H310M-HDV where I got the acpi A5 BSOD in almost all my attempts ...mystery.
#4143 | YuriyCN | Intel RSTe AHCI/RAID driver v4.7.0.1117 + PAE with FIX128 v0.48 = BSOD crashes with STOP code 0x0000000A sometimes (approximately 1 time out of 5-10) when starting Windows. Intel RSTe AHCI/RAID driver v4.7.0.1117 + PAE with WinXPPAE 2.0 = Starting Windows OK, but crashed GS CABer.

#4144

diderius6

After next *.inf mod in the legacy Vista 32 bit graphik driver 10-2-mobile_legacy_vista32-64_dd_ccc_mod.exe
I succeed to install every driver (sound, IDE HD, lan, wlan, grafik with full 3D support) for win98, xp SP3 and win10 32 bit
on the nice Lenovo T43p (T43 also) notebook.
Interesting, if there is any other notebook, where this can be done,
Dietmar
PS: The *.inf mod T43p is adding this line
"ATI MOBILITY FireGL V3200" = ati2mtag_M24, PCI\VEN_1002&DEV_3154
⇗

#4145

ruthan

Wow - if 3D is working in Win98 - can you run 3Dmark here? Do you thing that its possible to make other ATI PCI-E cards working? Last officially supported are X300-X850 line - Catalyst 5.8 to 6.2 driver, for 6.2 is driver name (6-2_wme_dd_cp_30314.exe) . I would be really nice to add.. for example X1300-X1950 line support or even later.
In XP is possible to use (officially) up to Radeon 3850, which even has AGP variant..

#4146

IntiMD

⇗ @AbdullahTrees Safe for me to say that these drivers contrary to what the requirements said aren't compatible with XP nor XP x64 at all. Fernando needs to fix that in the usb3 megathread.
In the meantime try testing whether the 1.1.0.0145 (2013-02-26) drivers work for XP/Win2K03 (they should, but let's make sure). Uninstall the non-working drivers beforehand.
IntiMD has attached files to this post

- ⇗ WinXPUSB3AMD2013.zip

#4147

diderius6

⇗ @ruthan
As wished, here it is. May be, other ATI PCI-e cards can be enabled too with *.inf mod,
but I have none^^,
Dietmar
PS: By the way, on the same compi T43p under XP SP3 3Dmark gives 11720 (!) points.
And win98 gets more points than win10^^.
⇗

#4148

YuriyCN

I found 2 ACPI.SYS files with the same size (239616 bytes) and the same internal version, but the contents of the files are different. The difference is only in a few places, 2-4 bytes were patched. I am sending you these 2 files in the archive -
Link removed by Fernando
Which of these files do you recommend to use?
EDIT by Fernando: Download link removed (publication of modded *.SYS files are not allowed here)

#4149

AbdullahTrees

> Zitat von ⇗ IntiMD im Beitrag ¶ #4146

> @AbdullahTrees Safe for me to say that these drivers contrary to what the requirements said aren't compatible with XP nor XP x64 at all. Fernando needs to fix that in the usb3 megathread.
> In the meantime try testing whether the 1.1.0.0145 (2013-02-26) drivers work for XP/Win2K03 (they should, but let's make sure). Uninstall the non-working drivers beforehand.

OHHH MYYY GOD!!!! Thank you so much for these drivers, ⇗ @IntiMD !!! Now I have 4 functional USB ports on my laptop, although I'm not sure whether the speed is USB 3.0 or 2.0 as I don't have a USB 3.0 device, hehe.
*never thought I'd be able to get this far, not a single Unknown Device!*
As for system stability, it has improved the second I uninstalled the non-functional USB 3.0 WHQL drivers, and now my PC can shutdown without BSODs. There's just one teeny-tiny problem though that I figured out: I can't hibernate or even go on standby. When I go to hibernate, 'Preparing to Hibernate...' shows, and the screen even goes dark, but all of a sudden an asterisk error pops up.
And going to standby freezes the computer at 'Preparing to standby...'
Although this is now a minor issue rather than a major one, I'll still actively ask for help and fix it as much as possible, as it is quite important... Makes me wonder what else could there be that is out of order due to these drivers...
Thanks in Advance,

#4150

IntiMD

> Zitat von ⇗ AbdullahTrees im Beitrag ¶ #4149

> > Zitat von ⇗ IntiMD im Beitrag ¶ #4146

> > @AbdullahTrees Safe for me to say that these drivers contrary to what the requirements said aren't compatible with XP nor XP x64 at all. Fernando needs to fix that in the usb3 megathread.
> > In the meantime try testing whether the 1.1.0.0145 (2013-02-26) drivers work for XP/Win2K03 (they should, but let's make sure). Uninstall the non-working drivers beforehand.

> OHHH MYYY GOD!!!! Thank you so much for these drivers, @IntiMD !!! Now I have 4 functional USB ports on my laptop, although I'm not sure whether the speed is USB 3.0 or 2.0 as I don't have a USB 3.0 device, hehe.
> *never thought I'd be able to get this far, not a single Unknown Device!*

Good to know that these drivers have worked perfectly fine! It's kind of weird why there was a NT5.1.1 mark at the controller drivers but no mark at the hub drivers, whereas the drivers weren't intended at all for NT 5.1 in the latest "xp-compatible" drivers offered, but nevertheless it works fine now.
As such, it would be nice for ⇗ @Fernando to include these drivers from post no. 4146 (¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (277)) into the USB3 megathread as confirmed working on XP.
As of that hibernation problem, it doesn't have to be the cause but you might want to try the modded acpi.sys drivers ⇗ Modded ACPI Drivers Depot 2000 XP 2003 2009
Make sure that you backup the original acpi.sys just in case.

#4151

AbdullahTrees

> Zitat von ⇗ IntiMD im Beitrag ¶ #4150

> Good to know that these drivers have worked perfectly fine! It's kind of weird why there was a NT5.1.1 mark at the controller drivers but no mark at the hub drivers, whereas the drivers weren't intended at all for NT 5.1 in the latest "xp-compatible" drivers offered, but nevertheless it works fine now.
> As such, it would be nice for @Fernando to include these drivers from post no. 4146 (¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (277)) into the USB3 megathread as confirmed working on XP.
> As of that hibernation problem, it doesn't have to be the cause but you might want to try the modded acpi.sys drivers ⇗ Modded ACPI Drivers Depot 2000 XP 2003 2009
> Make sure that you backup the original acpi.sys just in case.

How exactly does someone backup drivers? I could copy the acpi.sys file, but a surely part of a driver also includes messing with .inf files and changing stuff in the registry... Is copying the acpi.sys file enough?

#4152

IntiMD

> Zitat von ⇗ AbdullahTrees im Beitrag ¶ #4151

> > Zitat von ⇗ IntiMD im Beitrag ¶ #4150

> > Good to know that these drivers have worked perfectly fine! It's kind of weird why there was a NT5.1.1 mark at the controller drivers but no mark at the hub drivers, whereas the drivers weren't intended at all for NT 5.1 in the latest "xp-compatible" drivers offered, but nevertheless it works fine now.
> > As such, it would be nice for @Fernando to include these drivers from post no. 4146 (¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (277)) into the USB3 megathread as confirmed working on XP.
> > As of that hibernation problem, it doesn't have to be the cause but you might want to try the modded acpi.sys drivers ⇗ Modded ACPI Drivers Depot 2000 XP 2003 2009
> > Make sure that you backup the original acpi.sys just in case.

> How exactly does someone backup drivers? I could copy the acpi.sys file, but a surely part of a driver also includes messing with .inf files and changing stuff in the registry... Is copying the acpi.sys file enough?

Make a copy of the original. Rename the copy as "acpi.bak". Overwrite the unmodified acpi.sys file with the modified one from DK_ACPI\64 folder in the archive.
It's up to you to find out whether replacing acpi.sys was just enough to fix the problem.

#4153 | YuriyCN | I delete this post.
#4154 | ruthan | ⇗ @YuriyCN Is there difference between reboot and cold start? Are using Fastboot UEFI settings? From my experience reboot is now pure equivalent of cold start and some registry could be still filled with old bad data, fastboot it complicated even more, because reset even less devices.

#4155

YuriyCN

> Zitat von ⇗ ruthan im Beitrag ¶ #4154

> @YuriyCN
> Is there difference between reboot and cold start? Are using Fastboot UEFI settings? From my experience reboot is now pure equivalent of cold start and some registry could be still filled with old bad data, fastboot it complicated even more, because reset even less devices.

It does not depend on fastboot UEFI settings.
I use fastboot = disabled. But I tried enabled / disabled, no difference.

## Page 278

#4156

AbdullahTrees

> Zitat von ⇗ IntiMD im Beitrag ¶ #4152

> Make a copy of the original. Rename the copy as "acpi.bak". Overwrite the unmodified acpi.sys file with the modified one from DK_ACPI\64 folder in the archive.
> It's up to you to find out whether replacing acpi.sys was just enough to fix the problem.

Thanks for the link, I did what you said, aaaand this is what happened.
⇗ BSOD 0x0000007E
I was surprised you told me to copy the acpi.sys in the 64 folder, seeing as I use Windows XP SP3 32-bit, but then I tried using the acpi.sys from both of the folders, and none of them worked, they give a BSOD after the 'Windows XP splash screen with blue progress bar' ends.
Awaiting your response...

#4157

IntiMD

⇗ @AbdullahTrees Damn, my bad! For some weird reason thought that you were using the 64-bit edition. My mistake indeed.
So when you copied from the (now right) 32 folder the acpi.sys file and replaced the original one (after previously backing the original file up) with the modded one, it went BSOD? In this case it seems that this acpi.sys mod that you tried seemed to not be compatible with the laptop. What I would do now is to restore the original unmodified acpi.sys.
After restoring it, let's give this other "outer space" acpi.sys a try: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (215) (only x86 version, which should now suit you fine)
As always keep the backup of the original unmodified acpi.sys just-in-case and replace the file with this outer-space one.

#4158 | diderius6 | Here are the last and best acpi.sys for 32 and 64 Bit, for Intel and AMD Dietmar EDIT by Fernando: Attachments removed (publication of modded *.SYS files are not allowed here)
#4159 | YuriyCN | Intel RSTe AHCI/RAID driver v4.7.0.1117 + PAE patch with FIX128 = BSOD crashes with the code 0x0000000A sometimes (approximately 1 time out of 5-10) when starting Windows.

#4160

Andalu

⇗ @YuriyCN
I'm using the Intel RSTe AHCI/RAID driver v4.7.0.1117 + WinXPPAE 2.0 + USB3 driver modded. I started XP really many times (I'm doing some test with HD and SSD drives) but I never got any BSOD on my system (Asus Q370 and i5-8400 Coffee Lake).
I can confirm that the boot with the Universal 32bit Intel RST AHCI+RAID driver v11.2.0.1006 modded by Fernando is fastest than the RSTe AHCI/RAID driver v4.7.0.1117 (it takes half the time) and also the performances are better than the v4.7.0.1117 in all cases, even with the write cache enabled.

#4161

AbdullahTrees

> Zitat von ⇗ IntiMD im Beitrag ¶ #4157

> @AbdullahTrees Damn, my bad! For some weird reason thought that you were using the 64-bit edition. My mistake indeed.
> So when you copied from the (now right) 32 folder the acpi.sys file and replaced the original one (after previously backing the original file up) with the modded one, it went BSOD? In this case it seems that this acpi.sys mod that you tried seemed to not be compatible with the laptop. What I would do now is to restore the original unmodified acpi.sys.
> After restoring it, let's give this other "outer space" acpi.sys a try: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (215) (only x86 version, which should now suit you fine)
> As always keep the backup of the original unmodified acpi.sys just-in-case and replace the file with this outer-space one.

Okay, Windows didnt crash this time when I switched the acpi.sys, but it gave me a very wierd error at logon that was basically telling me that it couldn't log into my local account cause something was accessing it and thus made a temporary account for me: all changes made to it would be lost on shutdown. No idea why changing acpi.sys would cause something like this to happen, but other than that, no perceivable difference, still couldn't hibernate on the new acpi.sys.
⇗ @diderius6 :O are those for me? But my system doesn't have Ryzen, it is an AMD A10-4600M APU with Radeon(tm) HD Graphics... So which one from the 3 you uploaded should I try (I guess I'll try all 3 later when I have time...)

#4162

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4160

> @YuriyCN
> I'm using the Intel RSTe AHCI/RAID driver v4.7.0.1117 + WinXPPAE 2.0 + USB3 driver modded. I started XP really many times (I'm doing some test with HD and SSD drives) but I never got any BSOD on my system (Asus Q370 and i5-8400 Coffee Lake).
> I can confirm that the boot with Universal 32bit Intel RST AHCI+RAID driver v11.2.0.1006 modded by Fernando is fastest than the RSTe AHCI/RAID driver v4.7.0.1117 (it takes half the time) and also the performances are better then the v4.7.0.1117 in all cases, even with the write cache enabled.

1) With the driver v4.7.0.1117: the initial stage of loading Windows XP takes 3-4 seconds longer than when using the driver "v11.2.0.1006 mod Fernando". At the very beginning of the booting up, when 3 dots run under the logo, with the driver v11.2.0.1006 they run 1 time and Windows continues to boot, and with version v4.7.0.1117 they run 4-5 times and only then the booting up continues.
2) With the driver v11.2.0.1006 mod Fernando: if a DVD drive is connected, the LED HDD flashes periodically (1 time per second), even when the system is idle and there is no access to either the SSD or the DVD. Why is "HDD activity" displayed when the system is idle? But with version v4.7.0.1117 - no problem, LED is not blinking.
3) Please copy the files below (from your installed system) to one archive and send me:
c:\WINDOWS\system32\drivers - full directory, all files
c:\WINDOWS\system32\hal.dll
c:\WINDOWS\system32\ntkrnlpa.exe
c:\WINDOWS\system32\ntoskrnl.exe

#4163

Fernando

⇗ @IntiMD:

> Zitat von ⇗ IntiMD im Beitrag ¶ #4150

> As such, it would be nice for @Fernando to include these drivers from post no. 4146 (¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (277)) into the USB3 megathread as confirmed working on XP.

Why should I add these old AMD drivers to the thread about the latest/best USB 3.0/3.1 drivers?
Users, who want to install Windows XP nowadays will/ should look for suitable drivers within this Sub-Forum.

#4164

IntiMD

> Zitat von ⇗ Fernando im Beitrag ¶ #4163

> @IntiMD:

> > Zitat von ⇗ IntiMD im Beitrag ¶ #4150

> > As such, it would be nice for @Fernando to include these drivers from post no. 4146 (¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (277)) into the USB3 megathread as confirmed working on XP.

> Why should I add these old AMD drivers to the thread about the latest/best USB 3.0/3.1 drivers?
> Users, who want to install Windows XP nowadays will/ should look for suitable drivers within this Sub-Forum.

If there's no need to add them in the megathread then at least the "usable with WinXP" part should be removed in the H-Series section, so as to not mislead others.

#4165 | AbdullahTrees | ⇗ @IntiMD I'd like to ask where you found the USB 3.0/3.1 drivers that worked for XP, I'm curious. I wouldn't have ever found them by myself, cause the ones I were getting from DriverPack weren't working

#4166

IntiMD

> Zitat von ⇗ AbdullahTrees im Beitrag ¶ #4165

> @IntiMD I'd like to ask where you found the USB 3.0/3.1 drivers that worked for XP, I'm curious. I wouldn't have ever found them by myself, cause the ones I were getting from DriverPack weren't working

Found it in drp.su:
* lurked by the hardware identificators
* downloaded the zip file which actually didn't contain the pure drivers but rather the self-extractable exes from samlab
* extracted the 2 nt5 exes by 7-zip; uniextract2 would work fine too.
* while the inf files were identical in both of those nt5 (XP) exes, the 64-bit one contained the 64-bit drivers in both 64 and 32 bit folder and the 32-bit one contained the 32-bit drivers in both 64 and 32 bit folder.
* in order to fuse it into one, just like it was in pure drivers from the usb3 megathread, i just replaced the 64-bit folder with the 64-bit drivers and the 32-bit folder with the 32-bit drivers. The root files (inf, msi, cat) were intact.
* assembled into a zip file, then i attached that driver for you.

#4167 | Andalu | ⇗ @YuriyCN 1) here the same (total boot time on mechanical hard drive: 42 seconds with driver v4.7.0.1117 and 21 seconds with the driver v11.2.0.1006) 2) not so frequently, one time on 4/5 seconds 3) pm

#4168

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #3631

> WinXPPAE 2.0, a small utility to patch all kernel and hal files, supporting all languages and versions 5512 (SP3) and later:
> What's new:
> - thanks to @Mov AX, 0xDEAD, now includes HAL patches for ACPI Timer fix and proper memory management from Server 2003.
> - creates backups files (.bak) automatically
> ..............................................
> ..............................................

When using WinXPPAE 2.0, there are several problems that without this patch do not exist.
For example:
1) GS CAB'er with a patch does not start. Without a patch WinXPPAE this application works fine. Surprisingly, when using FIX128 v0.48, I got memory >4GB and normal work of GS CAB'er. The investigation revealed, that the problem is the hal.dll file (internal name halmacpi.dll) patched using WinXPPAE 2.0. When HAL.DLL patching with FIX128, the GS CAB'er works fine.
WinXPPAE 2.0 - ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (243)
gs_caber v1.1.5.7 - ⇗ https://www44.zippyshare.com/v/gjEdpzi4/file.html
FIX128 v0.48 - ⇗ https://www58.zippyshare.com/v/w4gsnb89/file.html
2) CHKDSK of the Flash drive connected via USB port stops working. CHKDSK is launched from the standard Explorer menu (see screenshot). At the very beginning, the scan freezes and the Explorer.exe process crashes. Without WinXPPAE 2.0, the CHKDSK works fine.
USB 3.0 driver (for Intel H110M) - ⇗ https://www104.zippyshare.com/v/NFOp8yLv/file.html

#4169

genieautravail

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4168

> When using WinXPPAE 2.0, there are several problems that without this patch do not exist. For example:1) GS CAB'er with a patch does not start. Without a patch WinXPPAE this application works fine. Surprisingly, when using FIX128 v0.48, I got memory >4GB and normal work of GS CAB'er. The investigation revealed, that the problem is the hal.dll file (internal name halmacpi.dll) patched using WinXPPAE 2.0. When HAL.DLL patching with FIX128, the GS CAB'er works fine.WinXPPAE 2.0 - Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (243)gs_caber v1.1.5.7 - ⇗ https://www44.zippyshare.com/v/gjEdpzi4/file.htmlFIX128 v0.48 - ⇗ https://www58.zippyshare.com/v/w4gsnb89/file.html2) CHKDSK of the Flash drive connected via USB port stops working. CHKDSK is launched from the standard Explorer menu (see screenshot). At the very beginning, the scan freezes and the Explorer.exe process crashes. Without WinXPPAE 2.0, the CHKDSK works fine. USB 3.0 driver (for Intel H110M) - ⇗ https://www104.zippyshare.com/v/NFOp8yLv/file.html

About CHKDSK, I have the same problem with an USB 3.0 external hard drive but with FIX128 not WINXPPAE...

#4170

YuriyCN

> Zitat von ⇗ genieautravail im Beitrag ¶ #4169

> About CHKDSK, I have the same problem with an USB 3.0 external hard drive but with FIX128 not WINXPPAE...

CHKDSK does not work that with WinXPPAE 2.0, that with FIX128.
GS CAB'er does not work with WinXPPAE 2.0, but with FIX128 it works fine.

## Page 279

#4171 | Andalu | ⇗ @YuriyCN chkdsk works correctly here with WinXPPaePatch 2.0 while GS CAB'er doesn't start giving a memory error. I haven't tried the fix128 0.48 patch yet.

#4172

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4171

> @YuriyCN
> chkdsk works correctly here with WinXPPaePatch 2.0 while GS CAB'er doesn't start giving a memory error.
> I haven't tried the fix128 0.48 patch yet.

CHKDSK
Maybe this is not WinXPPaePatch 2.0 problem, but USB driver bug in PAE mode... Please, check CHKDSK works when using my USB driver - ⇗ https://www104.zippyshare.com/v/NFOp8yLv/file.html
GS CAB'er
This is a 100% HAL.DLL problem patched with WinXPPaePatch 2.0.
I replaced HAL.DLL with a non-patched file (or patched with FIX128) and the GS CAB'er - worked.

#4173

Andalu

⇗ @YuriyCN
Sorry, I can't download from zippyshare, I got the 403 forbidden error message. Probably my ISP has blocked the access to this site and I don't want use a VPN to bypass the block. I downloaded previously the GS CAB`er via google search. What USB3 driver you are using? Is not an AMD USB3 driver attached on this thread?
About the WinXPPaePatch 2.0, daniel_k had said some time ago that it will never be a perfect patch and the issues are always possible. I think that a compromise can be accepted. In another system I'm using the chinese PAE patch that works fine (but, for example, the format command hangs always) but i must use a PCI card to have the usb3 function. And I will probably be forced to use the same PCI card on my new Coffee Lake system.

#4174 | IntiMD | ⇗ @Andalu not him but here's the driver zip file in particular. Check attachments. EDIT by Fernando: Attachments removed (publication of modded *.SYS files are not allowed here)

#4175

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4173

> @YuriyCN
> Sorry, I can't download from zippyshare, I got the 403 forbidden error message. Probably my ISP has blocked the access to this site and I don't want use a VPN to bypass the block. I downloaded previously the GS CAB`er via google search.

Please, check CHKDSK works when using my USB driver.
All files in one archive (fix128v48.zip + gs_caber_1.1.5.7.zip + USB3_WinXP_x86_PAEfix.zip)
EDIT by Fernando: Attachments removed (publication of modded *.SYS files are not allowed here)

#4176

Andalu

⇗ @IntiMD
thanks ;)
⇗ @YuriyCN
I confirm that chkdsk also works correctly with the amdhub30.sys (SHA-1: 60CD2A15EC1DA4E30E806AB69D24B5865260C17E) and amdxhc.sys (SHA-1: 1AE2108E29A528EFDA7F7497952298A406991E21) included in the "USB3_WinXP_x86_PAEfix.zip" packet.
⇗
gs_caber_1.1.5.7 doesn't work anyway. I tried fix128v48 on the fly :) and I got the "Fix Hal: crap" message. I'll try again in the next days.

#4177

daniel_k

⇗ @YuriyCN
There is nothing wrong with my WinXPPAE 2.0.
GS CAB'er crashes here with a fully updated ISO including all updates and hotfixes and NO PAE patch.
Doesn't matter if I unpack the .exe with upx -d, still crashes. UPX itself is packed and works just fine.
But you can fix it by setting Compatibility to Windows 98 / Windows ME, then GS CAB'er runs just fine.
Regarding Scandisk, as I've said before, the modded Intel drivers (based on amdxhc) has issues with PAE, even with "PAE fix" the USB controller hangs if there is intense disk activity.
Anything that touches devices plugged in any of the Intel USB ports are prone to issues if PAE is enabled. For use with PAE, you need an external USB3 card, this is mandatory.

#4178

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4176

> @YuriyCN
> I confirm that chkdsk also works correctly with the amdhub30.sys (SHA-1: 60CD2A15EC1DA4E30E806AB69D24B5865260C17E) and amdxhc.sys (SHA-1: 1AE2108E29A528EFDA7F7497952298A406991E21) included in the "USB3_WinXP_x86_PAEfix.zip" packet.
> gs_caber_1.1.5.7 doesn't work anyway. I tried fix128v48 on the fly :) and I got the "Fix Hal: crap" message. I'll try again in the next days.

1) Your FLASH drive (disk D:) connected via USB port? Judging by the screenshot, you are checking the system drive (SATA).
2) FIX128 must be installed on the original (non-patched system). Installing FIX128 after WinPAE is not possible.

#4179

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #4177

> @YuriyCN
> GS CAB'er crashes here with a fully updated ISO including all updates and hotfixes and NO PAE patch

GS CAB'er is really an application with strange problems. For example, for me, GS CAB'er also crashes on Windows XP SP3 Eng installed with clean MSDN image, but works fine on the pirated WinXP RUS build.
After patch hal.dll (with WinXPPAE 2.0) GS CAB'er application stops working, but after patch with FIX128 it works fine. I replaced only the hal.dll file separately and determined the dependency of GS CAB'er from the hal.dll.

#4180 | ruthan | I wonder is trim partition related, or whole disc related? Because in Adata SSD toolbox i see only whole driver, no specific partition..

#4181

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #4177

> @YuriyCN
> Regarding Scandisk, as I've said before, the modded Intel drivers (based on amdxhc) has issues with PAE, even with "PAE fix" the USB controller hangs if there is intense disk activity.
> Anything that touches devices plugged in any of the Intel USB ports are prone to issues if PAE is enabled. For use with PAE, you need an external USB3 card, this is mandatory.

I did some experiments and realized what was happening. First you must install the driver from the archive USB3_driver_Intel_100-series\ USB3_WinXP_x86_PAEfix then replace amdxhc.sys only. This file located in patch - c:\WINDOWS\system32\drivers
All necessary files in the attached archive.
My experiment results:
1. With file USB3_driver_Intel_100-series\1\amdxhc.sys - working Standby mode, but not working CHKDSK
2. With file USB3_driver_Intel_100-series\2\amdxhc.sys - CHKDSK works fine!!! But in 50% of cases Windows freezes at boot !! And when you exit the Standby mode, I get a black screen or BSOD:
EDIT by Fernando: Attachments removed (publication of modded *.SYS files are not allowed here)

#4182

Andalu

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4178

> 1) Your FLASH drive (disk D:) connected via USB port? Judging by the screenshot, you are checking the system drive (SATA).
> 2) FIX128 must be installed on the original (non-patched system). Installing FIX128 after WinPAE is not possible.

You are right, my mistake (grrr... damn hurry). I tried againg using the two file systems included in the "USB3_WinXP_x86_PAEfix.zip" and effectively 'chkdsk' doesn't work for the USB drives with the WinXPPAE 2.0 patch. I also installed the FIX128 0.48 patch and 'chkdsk' works normally.
But, at the same time, I can confirm that with amdxhc.sys (SHA-1: 6717C1872E9A53A1B8D2822E968A8228E3A67182) and amdhub30.sys (SHA-1: 653B25F98F70BA6CBFAADB0F5D61E9D69F507D4F) 'chdsk' also works correctly with the WinXPPAE 2.0 patch installed:
⇗

#4183

ruthan

> Zitat von ⇗ daniel_k im Beitrag ¶ #4177

> @YuriyCN
> Regarding Scandisk, as I've said before, the modded Intel drivers (based on amdxhc) has issues with PAE, even with "PAE fix" the USB controller hangs if there is intense disk activity.
> Anything that touches devices plugged in any of the Intel USB ports are prone to issues if PAE is enabled. For use with PAE, you need an external USB3 card, this is mandatory.

Do you thing that this problem could be solved in future, its new discovery, or known thing? Its someone looking into or its just dead end. Would it be more safe disable whole on board Intel USB3 at all?
For external USB3 controllers do you recommend old vendor drivers, or new ones modded from this thread? I have Asmedia a NEC ones.

#4184

daniel_k

> Zitat von ⇗ ruthan im Beitrag ¶ #4183

> Do you thing that this problem could be solved in future, its new discovery, or known thing? Its someone looking into or its just dead end. Would it be more safe disable whole on board Intel USB3 at all?

Can be solved if one manages to successfully patch some of the PAE friendly drivers listed below. I've tried, but gave up.

> Zitat

> For external USB3 controllers do you recommend old vendor drivers, or new ones modded from this thread? I have Asmedia a NEC ones.

ASMedia and TI work because their drivers were written by MCCI, properly supporting PAE.
VIA and Fresco Logic work because their drivers were written using WDF. The KMDF runtime takes care of PAE.
Etron driver PAE compatibility is unknown.
Renesas (NEC) has the same PAE issues. Up to socket FM2, AMD licensed Renesas IP, so basically all USB3 controller used were basically from Renesas.

#4185 | ruthan | Thanks for info. One more question i already installed you Intel USB3 drivers, how complety get rid of them, it thing that uninstall device in Device manager is not good enough?

## Page 280

#4186 | daniel_k | ⇗ @ruthan Uninstall from Device Manager, then delete the following files: \Windows\System32\Drivers\amdhub30.sys \Windows\System32\Drivers\amdxhc.sys

#4187

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #4184

> Can be solved if one manages to successfully patch some of the PAE friendly drivers listed below. I've tried, but gave up.

I think this problem can be solved, because there are 2 drivers each of which works partially correctly.
Intel USB 3.0 driver operation with the WinXPPAE 2.0:

#4188

bcwinit

> Zitat von ⇗ daniel_k im Beitrag ¶ #4177

> Anything that touches devices plugged in any of the Intel USB ports are prone to issues if PAE is enabled. For use with PAE, you need an external USB3 card, this is mandatory.

> Zitat von ⇗ daniel_k im Beitrag ¶ #4184

> Renesas (NEC) has the same PAE issues. Up to socket FM2, AMD licensed Renesas IP, so basically all USB3 controller used were basically from Renesas.

Just for reference, it doesn't seem to be enabling PAE itself that's the problem but rather the use of more RAM than the typical ~3.2GB limit (which ensures all addresses for drivers stay in a 32-bit range). This applies to 32-bit editions of Server 2003 that support 4GB or more of RAM and of course to patched XP 32-bit installations.
I've been using the Renesas/NEC controllers for over six years without any issues with PAE enabled and 6GB, then 8GB, then 16GB of RAM. Windows was not patched to allow more RAM to be used. Instead, a RAM drive that supports unmanaged memory (which requires that PAE be enabled) as well as page files at boot is used to make more then ~3.2GB available to Windows. This makes the entire "virtual memory" space consist of physical memory, although Windows is oblivious so it always reports ~3.2GB in the system info. It may not be the most elegant solution, and the performance isn't quite as good as it would be without the need for RAM-to-RAM paging to make use of all of the RAM, but it's perfectly stable and far better than having less RAM and any amount of page file capacity on an HDD/SSD.

#4189

YuriyCN

bcwinit
You can write this information on the forums for lamers. Here are specialists of a higher level, they all know this very well. It solves complex problems by patching the OS or drivers.
daniel_k
I went over several variants of the patched amdxhc.sys file and I didnt get normal operation with any of the files. In some cases Windows hangs when booted in PAE mode, in others the transition to standby mode does not occur, in others CHKDSK does not start on a flash drive, in others the device does not appear (defined as "unknown device") if Windows boots with a device already connected into the USB port.
In general, each file has its own issues during work, but there is not a single option for everything to work simultaneously. If possible, I ask you to modify amdxhc.sys so that the driver works stably in the system when using the PAE mode (either through WinXPPAE 2.0 or FIX128).

#4190

bcwinit

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4189

> bcwinit
> You can write this information on the forums for lamers. Here are specialists of a higher level, they all know this very well. It solves complex problems by patching the OS or drivers.

For clarity, my post wasn't targeted at daniel_k as if he didn't know what I was saying already. It was a general response with supplementary info since his posts made it sound like an absolute that PAE mode itself is a problem for the modified AMD xHCI driver and the NEC/Renesas xHCI driver.
I'm happy to write information on the forum for anyone, "lamer" in your opinion or not, who may be interested in testing or normally using daniel_k's modified AMD xHCI driver with little or no risk of the stability problems that you've been reporting.
There will always be more people reading than posting in a technical thread like this, and if some of them just want to use a driver they found here and get on with life that shouldn't be a problem.

#4191 | ppm007 | were can I get WINXPPAe 2.0

#4192

YuriyCN

> Zitat von ⇗ ppm007 im Beitrag ¶ #4191

> were can I get WINXPPAe 2.0

Here - ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (243)

#4193

IntiMD

⇗ @YuriyCN You have to realise though that daniel_k has taken down the attachments containing the PAE patch for reasons that might be solely known to him (due to stability reasons or more further work on it?). A friend of mine still has it in his storage so if he finds it, I'll reupload it.
CC:⇗ @ppm007

#4194

daniel_k

I was asked to delete all of my modified 3rd party drivers to avoid copyright issues here. I've been told that in the near future, all modified files that are copyrighted will be deleted.
Additionally, as WinXPPAE was completely written by me, I've decided not to make it available here anymore. I hope you respect my decision and do not upload it here anymore.
In the next days, all of my modded drivers and WinXPPAE will be available at MDL Forums' Windows XP / Older OS section (forums.mydigitallife.net). The Admin gave me his OK.

#4195 | daniel_k | ⇗ @bcwinit I knew about the RAM disk option, but what we are discussing here is the PAE as it is, as supported by Server 2003 Enterprise/Datacenter.

#4196

IntiMD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4194

> I was asked to delete all of my modified 3rd party drivers to avoid copyright issues here. I've been told that in the near future, all modified files that are copyrighted will be deleted.
> Additionally, as WinXPPAE was completely written by me, I've decided not to make it available here anymore. I hope you respect my decision and do not upload it here anymore.
> In the next days, all of my modded drivers and WinXPPAE will be available at MDL Forums' Windows XP / Older OS section (forums.mydigitallife.net). The Admin gave me his OK.

Alright, those are your modifications and it's your choice on how they're being distributed after all. At least something good came out of that situation - MDL has a larger userbase so you and your projects would be noticed more. Wish you luck on it.

#4197

YuriyCN

> Zitat von ⇗ daniel_k im Beitrag ¶ #4194

> I was asked to delete all of my modified 3rd party drivers to avoid copyright issues here. I've been told that in the near future, all modified files that are copyrighted will be deleted.
> Additionally, as WinXPPAE was completely written by me, I've decided not to make it available here anymore. I hope you respect my decision and do not upload it here anymore.
> In the next days, all of my modded drivers and WinXPPAE will be available at MDL Forums' Windows XP / Older OS section (forums.mydigitallife.net). The Admin gave me his OK.

This forum is dedicated to updating drivers, but you cannot post modified files on it. That's bullshit?
Please, then upload the files to free file hosting services with a long shelf life, but leave only the URL here. I really want to see a modified AMDXHC.SYS (for Intel Motherboard) in which there is a working CHKDSK with PAE mode.

#4198

Andalu

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4197

> ......I really want to see a modified AMDXHC.SYS (for Intel Motherboard) in which there is a working CHKDSK with PAE mode.

wasn't this image enough?
⇗

#4199

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4198

> ⇗

I do not have files with such MD5 hash.
Please, send me your amdhub30.sys and amdxhc.sys.

#4200 | infuscomus | ⇗ @YuriyCN I have these, should I PM you?

## Page 281

#4201

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #4200

> @YuriyCN
> I have these, should I PM you?

He has already got them ;)

#4202

Fernando

> Zitat von ⇗ daniel_k im Beitrag ¶ #4194

> I was asked to delete all of my modified 3rd party drivers to avoid copyright issues here. I've been told that in the near future, all modified files that are copyrighted will be deleted.

Just for clarification:
Only attached or linked drivers, whose *.SYS file code has been altered, will be deleted by the Win-RAID Forum team (to avoid any problems with the manufacturer of the original driver).

#4203

daniel_k

My last post here. Please read this:
INTEL END USER SOFTWARE LICENSE AGREEMENT
IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.
THE FOLLOWING NOTICE, OR TERMS AND CONDITIONS SUBSTANTIALLY IDENTICAL IN NATURE AND EFFECT, MUST APPEAR IN THE DOCUMENTATION ASSOCIATED WITH THE INTEL-BASED PRODUCT INTO WHICH THE SOFTWARE IS INSTALLED. MINIMALLY, SUCH NOTICE MUST APPEAR IN THE USER GUIDE FOR THE PRODUCT. THE TERM "LICENSEE" IN THIS TEXT REFERS TO THE END USER OF THE PRODUCT.
LICENSE. Licensee has a license under Intel's copyrights to reproduce Intel's Software only in its unmodified and binary form, (with the accompanying documentation, the "Software") for Licensee's personal use only, and not commercial use, in connection with Intel-based products for which the Software has been provided, subject to the following conditions:
(a) Licensee may not disclose, distribute or transfer any part of the Software, and You agree to prevent unauthorized copying of the Software.
(b) Licensee may not reverse engineer, decompile, or disassemble the Software.
(c) Licensee may not sublicense the Software.
(d) The Software may contain the software and other intellectual property of third party suppliers, some of which may be identified in, and licensed in accordance with, an enclosed license.txt file or other text or file.
As you can see, 99.99% of all software available here is theoretically being distributed/modified against Intel's EULA.
Even the Coffee Lake mod is a clear case, as they weren't originally intended for use with non-certified boards.

#4204

Fernando

⇗ @daniel_k:
Here is my statement:

1. Simple text files with the extension *.INF or *.OEM are documents, but no software.
2. All drivers, whose *.INF or *.OEM files have been customized by me, are offered with the suffix "mod+signed by Fernando" to make it absolutely clear, who is responsable for the customization.
3. Intel knows about my "mod+signed" drivers. Intel employees themselves have recommended to use them, if the original driver doesn't support the specific Intel device.

#4205

ruthan

I returned to my Gigabyte Z370 XP project with new discoveries, previously i machine installed only in MPS mode.. and i had problem with some not working MB devices,
because of not enough resources.
Daniel long time ago, fixed my F13 bios.
I changed MPS in device manager to ACPI just through load other driver - it survived reboot, all exclamation marks on system devices are no gone, what is good.. Second Geforce 750 Ti is working with original Nvidia install what is also good.
I used new acpi file and timer fixed, btw what timer tester should report,
its running by im not sure about result.
Before Intel USB3 fixes, i had Asmedia USB 3 working at least in MPS mode, with vanilla Asmedia drives. I have 2 Asmedia USB 3 controllers - on board and external.
Now i have strange problems, that Asmedia USB3 is not more working i tried new and old drivers.. Controller driver is fine, hub driver is also fine, but there is some composite USB device, which reports the error.
No USB3 device detected, same NEC USB3 external (72001, i updated firmware to last). I tried to force driver for it, but always getting that driver package is now include any driver for my devices.
In more modern OSes all its working.
This would be still quite ok, because my MB is supporting Y P/S2 cable (i tested thing also without it), but problem is that PS/2 keyboard is not working too, its working in bios, in grub and in WinXP boot menu, but not start OS booted.
I can see Standard PS/2 and mouse and keyabord device in Device manager, but bough has exclamation marks.
But OS seems to running fine, i can connect through remote desktop and do stuff.
I tried new modded Intel USB3 driver, also no luck, so i uninstalled it and deteleted files.. I through that i would able to completly disable Intel USB3 controller, i disable all 4 its BIOS settings, but its still detected. Maybe its disabling only onboard Asmedia controller.
I also have M.2 NVME which is not visible in Windows XP, its working fine in Windows 10. When i install in the same slot M.2 Sata its working fine.
Im not using any PAE patch. I have 2.5 GB of 32 GB available, what is still usuable..
Other strange thing that there is not Fernando Controller device which at at least in past was present, but just some PCI Device..
Here is list of unknow devices, i wonder about intel one? Its some managed controller? I tried to force NVME driver from Diderius on it.. but again, inf not include drivers for this device.. So its not probably NVME device.
When i translate with name is some something like simple communication for PCI bus.
Sitovy adapter - its Intel 219 Lan.
Radic videa - its second GPU - 1070 for Win7+.
Radic USB - means USB controller.
Sound is working fine, no bluescreens in 2D, Opera working fine for internet.
Any idea? Sorry for missing error codes (next time after weekend), im no by that machine now.. Maybe we can write some batch files to report filesizes, dates or versions of all installed important files, is someone now how to do it.. to post logs here, to make things cleaner.. Because without it as debugging very wild guessing.
⇗
⇗
⇗
⇗

#4206

YuriyCN

> Zitat von ⇗ Fernando im Beitrag ¶ #4204

> @daniel_k:
> Here is my statement:
> 1. Simple text files with the extension *.INF or *.OEM are documents, but no software.
> 2. All drivers, whose *.INF or *.OEM files have been customized by me, are offered with the suffix "mod+signed by Fernando" to make it absolutely clear, who is responsable for the customization.
> 3. Intel knows about my "mod+signed" drivers. Intel employees themselves have recommended to use them, if the original driver doesn't support the specific Intel device.

Dear developers, send these companies in the ass. Please collect all your modifications in one archive so that we can download and use. It is very important that nothing is lost. You make modifications due to the fact that companies did not write drivers for old operating systems. This is a global conspiracy, everyone is forcibly transferred to Windows 10, but many like the old OS (Windows XP, Windows 7).
EDIT by Fernando: Unacceptable message has been striked through by me.

#4207

Fernando

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4206

> Please collect all your modifications in one archive so that we can download and use.

The Win-RAID Forum team will not allow anybody to attach or link such archive within this Forum.
We do not want to risk, that this web site has to be closed due to an intervention of any chipset manufacturer.

#4208

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4198

> > Zitat von ⇗ YuriyCN im Beitrag ¶ #4197

> > ......I really want to see a modified AMDXHC.SYS (for Intel Motherboard) in which there is a working CHKDSK with PAE mode.

> wasn't this image enough?

I tested this driver. I confirm, no problems! It really works with CHKDSK.
But this driver is very unstable in PAE mode:
1. A device connected to a USB port is not detected in 50% ("Unknown Device" in Device Manager)
2. Windows often freezes when starting or shutting down

#4209

Andalu

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4208

> I tested this driver. I confirm, no problems! It really works with CHKDSK.
> But this driver is very unstable in PAE mode:
> 1. A device connected to a USB port is not detected in 50% ("Unknown Device" in Device Manager)
> 2. Windows often freezes when starting or shutting down

No issue here with that driver for both points you mentioned. I tried many times with 6 usb devices (4 external USB3 2.5" hard drive and 2 pendrive) connected at same time with no problems as well as the restart and the shutdown have always worked correctly.
Different behavior when XP boots with an usb device already inserted in any usb2/usb3 port, but you are already aware of that.
I don't know if a workaround can be found to bypass this problem, maybe to delay the USB3 driver loading during the XP boot could be a way?
For the moment, my Renesas/Nec pci-ex to USB3 card solved this issue.

#4210

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #4203

> My last post here.....

I'm sad to read this. It's a big loss for the forum.
Thanks so much for your great work

#4211

YuriyCN

I solved the previously described problem.
USB 3.0 driver forIntel 100-series - ⇗ https://www33.zippyshare.com/v/EmUcBIrn/file.html
Windows XP SP3 RUS LWOS v2 build 20.02 - ⇗ https://yadi.sk/d/u4G9oQajqTSeGQ this build with updates to February 2020.
Integrate USB 3.0 driver with nLite - ⇗ https://www.nliteos.com/download.html
As it turned out, you need to use this USB 3.0 driver with WinXP updated to 2020. On a clean MSDN image of WinXP SP3 - CHKDSK did not work with this driver. But on the WinXP LWOS (LWGAME, nCore project) with updates 02.2020 - CHKDSK works fine, including PAE mode!

#4212

Andalu

⇗ @YuriyCN
I tried the ISO updated at february 2020 but the problems seem to be unresolved, al least here.
I only added the acpi.sys (sha-1: 8EF48518B17DAAC4A90632A811FBFDC8183C325B) and the Universal 32bit Intel RST AHCI+RAID driver v11.2.0.1006 modded by Fernando to the ISO image with nLite. The XP installation ends normally.
I applied the WinXPPae 2.0 patch and installed the amdxhc.sys driver (sha-1: 61711270A0BF0AFC3AFC71047FE8F32643D6FD54). On restart, with no USB device connected to the board, XP boots normally and the whole ram has been correctly recognized. But the system hangs always on shutdown. Furthermore, with an USB device already connected to the USB3 port, XP boots correctly but the same usb device is not recognized as has always happened. I also tried with the amdxhc.sys (sha-1: 1AE2108E29A528EFDA7F7497952298A406991E21) with the same results.
The chkdsk utility has always worked, at least it.

#4213 | YuriyCN | We need to find a normal, most updated distributive of Win XP, integrate all the drivers and put it in public. Most people do not understand how to install the system on modern PCs. It's time to create ready solutions. For Russian-speaking people, I recommend using the "Windows XP SP3 RUS LWOS v2 build 20.02" - ⇗ https://vk.com/topic-28391636_35530104
#4214 | ruthan | Someone here mentioned that intel-218 drivers is working in XP, can someone pleas working driver?
#4215 | infuscomus | ⇗ @Andalu ⇗ @YuriyCN I made a windowsXP Ryzen edition - it's on pirate bay if you want to try it

## Page 282

#4216

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #4215

> @Andalu @YuriyCN
> I made a windowsXP Ryzen edition - it's on pirate bay if you want to try it

Unfortunately, the "Windows XP Ryzen edition" did not install on my Intel motherboard with the H110M chipset.
Please clarify how it is done "ACPI timer fix (thanks to daniel_k)"?? Where can I read about this information? What is the essence of the changes?

#4217 | Andalu | ⇗ @infuscomus I have not a Ryzen system. Thanks anyway ;)

#4218

infuscomus

⇗ @YuriyCN
how far into XP setup did you get? did you get past textmode setup?
any BSODs?
I'm not entirely sure how the hal timer fix works, ask ⇗ @diderius6 or ⇗ @daniel_k if you want to know how it works
I dug through the thread and found this one -
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197)
I'm sure there is a newer version somewhere in the thread though
⇗ @Andalu
I tried to include fixes for intel Z100/200/300 systems in this too, I don't have an Intel system myself so I'm not sure if they work.

#4219

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #4194

> In the next days, all of my modded drivers and WinXPPAE will be available at MDL Forums' Windows XP / Older OS section (forums.mydigitallife.net). The Admin gave me his OK.

⇗ @daniel_k ...Thanks for all your good work. Will keep an eye open at mdl.

#4220

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #4218

> @YuriyCN
> how far into XP setup did you get? did you get past textmode setup?
> any BSODs?
> I'm not entirely sure how the hal timer fix works, ask @diderius6 or @daniel_k if you want to know how it works
> I dug through the thread and found this one -
> ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197)
> I'm sure there is a newer version somewhere in the thread though

Text mode settings were successful. Next, the files are copied and the first reboot. Everything is fine. Further installation in graphical mode and again everything is ok. Then the second reboot and already at the 3rd stage of the installation I get BSOD. That is, the installation reaches almost completion.
The BSOD code was 7B as with unsuitable AHCI SATA drivers, but there are drivers, because the 1st and 2nd stages went fine. I tried to additionally enable the obviously working AHCI SATA Fernando mod driver - but this did not help. Therefore, I refused your assembly and took another from the LWGAME | NCORE project and integrated all the drivers into it. As a result, everything was normal.

#4221 | infuscomus | ⇗ @YuriyCN Do you know which driver setup used initially? was it the intel driver or storahci?

#4222

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #4221

> @YuriyCN
> Do you know which driver setup used initially? was it the intel driver or storahci?

I do not know. But some driver was definitely used. If there is no AHCI SATA driver, then we get a 7B BSOD at the 1st stage of installation. But I got a BSOD in stage 3. You need to figure out what happens in the final stage of installation.

#4223

ruthan

I wrote about this long time ago, but i wanst able to find the link:
X58-DOS (with real sound card sound)/Win98SE/WinXP/Win7/Win10 X58 machine, its not "real" multiboot because of you need some card exchanges for oses, i trying to make it working without it
⇗ https://www.vogons.org/viewtopic.php?f=25&t=56460
You can find here something about how to make NVME disk working without bios support through Clover
Update:
Funny is games speed comparision with 8700K, if you which that this X58 machine is slow.. you will suprised:
⇗ https://www.youtube.com/watch?v=skV9exEDM3w

#4224 | gordo999 | Something odd in my XP setup. I used the modded acpi.sys from this site to get XP going. It always failed with an 0XA5, indicating an acpi issue and the mod got it going. Recently, I did a repair install and the installer put the original acpi.sys back in the drivers folder. The system still boots with the original acpi.sys. Go figure!!!

#4225

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #4218

> I tried to include fixes for intel Z100/200/300 systems in this too, I don't have an Intel system myself so I'm not sure if they work.

I tried the ISO on my Q370 system:
- textmode setup ok;
- 1st reboot: first step of the GUI setup ok;
- 2nd reboot: XP hangs on a blank screen with only the mouse cursor visible but locked.
No changes on the next restart/shutdown.

#4226 | infuscomus | ⇗ @Andalu can you move the cursor? or is it completely frozen? I might look at removing the USB 3.0 files during setup, if that turns out to be the issue.
#4227 | Andalu | ⇗ @infuscomus the cursor is completely frozen even if the ps/2 mouse is powered. I only used the usb stick with the iso image, no other usb device connected to the board.
#4228 | ruthan | I have exactly same problem not not working input.

#4229

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #2751

> https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa5--acpi-bios-error ...

⇗ @daniel_k ...if you're still around. Had not noticed this post before but it is of interest to me. I fixed my 0xA5 errors using the acpi.sys file but I have noticed other BIOS-related errors, like when I tried to use a Cannon Lake INF package in an attempt to update my B360 chipset driver base. The INF contains all the correct hardware IDs for my chipset.
I put the error down to an older XP system not being aware of the newer BIOS on my B360-based motherboard. It does not make sense that my current BIOS is incomplete because it runs W10 and W7 without complaint. Therefore the problem seems to be in the ACPI components enumerating the BIOS.
Can you offer some advice on that? What XP components enumerate the BIOS? In my XP registry, there is a registry hive in HKLM\System\CurrentControlSet\Hardware that is only loaded when the system is live. It contains information about the BIOS. The data must be valid since it is loaded live from BIOS therefore the ACPI enumerating software must be incapable of reading it correctly.
ps. just occurred to me that the older enumerating software is looking in the wrong place for information in the newer BIOS. It would seem I need to use newer enumerating software.

#4230 | infuscomus | ⇗ @Andalu can i send you a copy of paragon rescue kit and a working XP install image? restore the image and see if it's working?

## Page 283

#4231 | Andalu | ⇗ @infuscomus no problem ;)
#4232 | Andalu | ⇗ @ruthan my mouse issue occured only during the XP installation with that specific ISO image. Never happened before with a ps/2 mouse for other ISO images. About your problem, have you already checked the bios settings? Is there the ps/2 emulation for keyboard and mouse?
#4233 | ruthan | Its gigabyte bios there some legacy usb and port 60 something, should they be enabled or disabled?

#4234

Andalu

> Zitat von ⇗ ruthan im Beitrag ¶ #4233

> Its gigabyte bios there some legacy usb and port 60 something, should they be enabled or disabled?

Your mouse/keyboard issue seems to be a bios related but I don't have your same board so I can't give you an exact suggestion. You have to go by attempts. The usb legacy should be always enabled. Have you also tried to set the "emulation of I/O ports 64h and 60h" on enabled and the 'fast boot' entry on disabled?

#4235 | ruthan | Yeah fast boot is disabled.. there is no any PS/2 specific settings.
#4236 | YuriyCN |
#4237 | infuscomus | ⇗ @Andalu Hi, I PMed you paragon rescue kit and an XP image.

#4238

Andalu

⇗ @infuscomus
I tried the ISO on my asus Q370:
at first attempt, I got the 0xA 'IRQL not less or equal' BSOD.
Replacing the acpi.sys with another mod version, XP boots normally but keyboard and mouse, both connected in two different ps/2 ports, don't work anyway (also in safe mode), even if their leds are on. There are no entries in the asus bios that can be related to the ps/2 emulation or similar.
Same behavior on the asrock B250, also with ps/2 emulation enabled in the bios.
Some drivers seem to be missing.

#4239 | infuscomus | ⇗ @Andalu any luck with USB ports? or not working? also, which acpi.sys did you use? - there are so many it's hard to keep track.

#4240

Andalu

⇗ @infuscomus
I have tried six other different versions of acpi.sys (5048 and 6666), same behavior.
No luck also using the usb mouse. Most probably the usb will work but my system needs to search and install the related drivers and with no input device I can't do anything. I'm always stuck at this point:
⇗

#4241 | ruthan | ⇗ @Andalu i was here, there is solution.. yoy need to make automated instalation, or integrated network drivers and enable remote desktop connection in nlite.. after that you can work with machine.. Or maybe you can just enable Remote desktop through some registry value..
#4242 | infuscomus | ⇗ @Andalu It's asking to install the PCI bus driver? you hardly ever see that! as ruthan said, If you have network access to it you can access it remotely and do the driver installation there. or otherwise, you can get a PCIE USB 2.0 card, connect everything to that and restart XP setup over again from scratch.

#4243

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #4238

> ...both connected in two different ps/2 ports, don't work anyway (also in safe mode), even if their leds are on. There are no entries in the asus bios that can be related to the ps/2 emulation or similar.

⇗ @Andalu ....Do you have PS/2 emulation? If so, you need emulation turned off when you have physical ports? Also, is your BIOS set for ACPI or legacy? Is CSM turned on?
I have never had a problem with PS/2 on my B360 chipset. I have two physical ports and both the mouse and keyboard always work.

#4244

Andalu

⇗ @infuscomus ⇗ @ruthan
thanks for your suggestions but I don't have both the network access to my system and a PCIE USB 2.0 card. I don't need to go deeper. Besides, it was just a test and it is not sure that XP can work 'perfectly' with that iso as expected, even with the drivers installation. At moment, I can be satisfied how pae and usb3 work simultaneously on my system. Of course, I needed to use a PCIE USB3 card to avoid PAE issues.
⇗ @gordo999
in the bios (asus makes no effort to improve it) there is not ps/2 emulation; both csm and legacy are enabled.
I never had those problems before, mouse and keyboard don't work only with that ISO.

#4245

ruthan

For these who dont follow our Win98 on modern system.. i only want to report that LInux - KVM - PCI-e / PCIe video cards passthrough + PCI sound cards is proven as working (you can use virtualized sound card too, but it has its flaws, or maybe USB one too - untested with Qemu, but tested with real Win98). Vitual Realtek 8139 is working too.
So all is ready to for using Windows 98 on any HW with device pass through virtualization support (for Intel:vt-d, for AMD: AMD-V ) on any desktop MB (i will not test it with laptors, but there are some external PCI / PCI-e boxss which you work too - ), where you have some free slots, if are willing to install Linux (other OSes dont support card passthrough) to some partition (30GB) to make it working, except initial setup, you could after ignore Linux part of its, its could be used just as "fancy bootloader" for you Win98 machine.. you course can pass through cards for WInXP, WIn7 and Wi10 too, its much let hassle.
Proof:
⇗ Windows 98SE on Modern Hardware (6)
Guide:
⇗ Windows 98SE on Modern Hardware (6)

## Page 284

#4246

gordo999

⇗ @Andalu ...your no mouse/keyboard problem is a tough one but you may find the answer in the ISO i386 directory in the txtsetup.sif file. It's a text file that can be loaded in a text editor. On one of my disks it lists [Mouse] as follows:
[Mouse]
msps2 = "Microsoft Mouse Port Mouse (includes BallPoint)",files.i8042,i8042prt
lgps2 = "Logitech Mouse Port Mouse",files.i8042,i8042prt
msinp = "Microsoft InPort Bus Mouse",files.inport,inport
msbpser = "Microsoft BallPoint Serial Mouse",files.sermouse,sermouse
lgser = "Logitech Serial Mouse",files.sermouse,sermouse
none = "No Mouse or Other Pointing Device",files.none,""
mouhid = "USB Mouse",files.mouhid,mouhid
msser = "Microsoft Serial Mouse",files.sermouse,sermouse
ps2 = "Mouse Port Mouse",files.i8042,i8042prt
sermouse = "Serial Mouse",files.sermouse,sermouse
USB = "USB Mouse",files.mouhid,mouhid
Also,
[Keyboard]
STANDARD = "XT, AT, or Enhanced Keyboard (83-104 keys)",files.i8042,i8042prt
kbdhid = "USB Keyboard",files.kbdhid,kbdhid
USB = "USB Keyboard",files.kbdhid,kbdhid
Make sure yours has not become corrupted somehow. It's unlikely that corruption would affect only the USB and PS/2 mouse and keyboard, however, but there may be something like the error I found after using nlite. Under the section [SetupData] it had listed my defaultdrive as being on the D:\ drive instead of C:\. It's actually supposed to be listed as DefaultPath=\WINDOWS, with no drive letter because earlier in the section SetupSourcePath = "\" is declared. That presuming your windows directory is called windows.
Also, you might check the setupapi.log on your installation. You can view it offline from another OS or use a boot disk like the modern Hiren's boot disk. The older ones won't boot into on a modern chipset since they are based on Win XP. Just thought that I may be able to mod one of their old disk with the newer acpi and sata drivers. :-)
It should tell you what problems it encountered during setup. Mine is located in the windows directory. Do a search for mouse and keyboard and check each reference. It claims to have found "PNP0F03" in c:\windir\inf\msmouse.inf. Make sure your line corresponds to your actual windir and that msmouse.inf is in the INF directory. It also lists PNP0F13 for compatible mouse drivers.
Same with keyboard.

#4247 | Opanje123 | Hello! I need to install Windows XP32 on motherboard N3160N-D3V. BIOS recognizes hard drives, but gives an error "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key". I tried to integrate the drivers AHCI in WinXP, but did not help :(
#4248 | ruthan | This means that your computer is not starting from boot cd / usb there you have win xp install.. So you have wrong boot order, or bad media etc..
#4249 | Andalu | ⇗ @gordo999 thanks for info and help but I can't access to the i386 folder because I don't have the ISO image. I have restored an XP image saved from another system, so I can't verify the txtsetup.sif file. In the setupapi.log everything about the driver installation and the paths of the keyboard and mouse seems to be correct. But it does not matter ;)

#4250

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #4249

> In the setupapi.log everything about the driver installation and the paths of the keyboard and mouse seems to be correct. But it does not matter ;)

⇗ @Andalu ...the only other thing coming to mind is an IRQ conflict. Two devices are trying to use the same IRQ, or possibly trying to access the same memory. Modern chipsets with an apic should not have that problem but sometimes there are several devices sharing the same IRQ.
The only practical way to check that with an offline machine is to move cards around in your PCI slots, or remove all cards except those you need, like the video driver. Here's a brief article outlining the idea using the registry.
⇗ https://helpdeskgeek.com/how-to/manage-irq-settings-windows/
You can access the registry in the offline machine from the registry of an online machine. Highlight Hkey_Local_Machine then look under the File menu at top of screen. Press Load Hive and direct it to %windir%\system32\config on offline machine. For the case in the article above, you would select the system hive in that directory then name it something unique like offline_system. It will show up under the HKLM key as offline-system. Then you can edit it as required. Remember to Unload it before shutting down regedit.

#4251 | Andalu | ⇗ @gordo999 Thank you again for your post, I will keep your valuable advice for a future need. I preferred to let that ISO go because, as already reported, while solving the mouse and keyboard problem, I'm not sure to avoid other issues related to the same ISO.
#4252 | Marwan | Hello ... I own a Lenovo g50_30 laptop. Can I install Windows XP on it? Are there drivers for it?

#4253

Fernando

⇗ @Marwan:
Welcome to the Win-RAID Forum!
I have moved your request into this already existing thread, where you can find a lot of information.
My answer to your question: Yes, it is possible to install Windows XP onto your laptop.
Good luck!
Dieter (alias Fernando)

#4254

gordo999

> Zitat von ⇗ Fernando im Beitrag ¶ #4253

> Yes, it is possible to install Windows XP onto your laptop.
> Good luck!Dieter (alias Fernando)

⇗ @Fernando ....it not only works, it works very well, thanks to you and the guys in the thread. I was told initially that it was impossible.
BTW...are you aware of 'right to repair' legislation in Europe. I have been advised that certain countries have enacted legislation giving consumers the right to have old equipment repaired. That's all I know. If it's correct, I am wondering how that might be extended to the right to have an OS like XP maintained by Microsoft.

#4255

YuriyCN

NVIDIA GeForce iCafe Graphics Driver 368.91 for XP 32bit
Supported cards:
Driver - ⇗ http://cn.download.nvidia.com/Windows/iC...ternational.exe
GeForce 1000 series:
GTX 1080, GTX 1070, GTX 1060
GeForce 900 series:
GTX TITAN X, GTX 980 Ti, GTX 980, GTX 970, GTX 960, GTX 950
GeForce 700 series:
GTX TITAN Z, GTX TITAN Black, GTX TITAN, GTX 780 Ti, GTX 780, GTX 770, GTX 760 Ti,
GTX 760, GTX 750 Ti, GTX 750, GTX 745, GT 740, GT 730, GT 720
GeForce 600 series:
GTX 690, GTX 680, GTX 670, GTX 660 Ti, GTX 660, GTX 650 Ti BOOST, GTX 650 Ti, GTX 650,
GTX 645, GT 645, GT 640, GT 630, GT 620, GT 610, 605
GeForce 500 series:
GTX 590, GTX 580, GTX 570, GTX 560 Ti, GTX 560 SE, GTX 560, GTX 555, GTX 550 Ti, GT 545, GT 530, GT 520, 510
GeForce 400 series:
GTX 480, GTX 470, GTX 465, GTX 460 v2, GTX 460 SE v2, GTX 460 SE, GTX 460, GTS 450, GT 440, GT 430, GT 420, GT 415

#4256 | ruthan | ⇗ @YuriyCN: Is somewhere real confirmation that its really working with Geforce 10xx?

#4257

YuriyCN

For NVIDIA (Windows XP):
nVidia Geforce iCafe Expresso 368.91 WHQL Desktop driver
Notes: ⇗ https://drivers.softpedia.com/get/GRAPHI...91-for-XP.shtml
Driver: ⇗ http://cn.download.nvidia.com/Windows/iC...ternational.exe
For AMD RADEON (Windows XP):
2015.09.30 version 300.100 - icafe-winxp-9.00.300.3010-beta1-br294594-sep24.exe
AMD Radeon HD 5000 Series
HD5450 / HD5550 / HD5570 / HD5750 / HD5770 / HD5830 / HD5850 / HD5870
AMD Radeon HD 6000 Series
HD6450 / HD6570 / HD6670 / HD6750 / HD6770 / HD6850 / HD6870 / HD6950 / HD6970
AMD Radeon HD 7000 Series
HD7750 / HD7770 / HD7850 / HD7870 / HD7950 / HD7970 / HD7990
AMD Radeon R9/R7 200 Series
R5 230 / R7 240 / R7 250 / R7 250X / R7 260X / R9 270 / R9 270 1024 SP / R9 270X / R9 280 / R9 280X
AMD Radeon R9/R7 300 Series
R7 360 / R9 370 1024 SP / R9 370X
All AMD Radeon APU Series
HD7480D / HD7540D / HD7560D / HD7660D / HD8370D / HD8470D / HD8570D / HD8670D / R7 series
Notes: ⇗ https://web.archive.org/web/201808170741...fe-unified.aspx
Driver: ⇗ http://radeon.ru/drivers/amd/xp/icafe-wi...94594-sep24.exe

#4258 | Andalu | It's a shame there is nothing to do for a RX550 to work in XP

#4259

gordo999

> Zitat von ⇗ ruthan im Beitrag ¶ #4256

> @YuriyCN: Is somewhere real confirmation that its really working with Geforce 10xx?

⇗ @ruthan ....if you mean is XP working with GeForce 10xx, I can only confirm that XP works fine with the driver 368.91. I had no trouble loading my GT-730 drivers and all the extras even though I did not remove the earlier GeForce driver set. The installation asks you if you want to do a fresh install.
What you have to watch is that the entire 368.91 package downloads, otherwise the installation will stop and claim there are files missing. I don't know how that is possible since the package comes zipped with an exe extension. However, my first d/l of the package had several files and folders missing. I suggest you download whatever package you need from Nvidia's site.

#4260 | ruthan | If you mean that this driver is working with Geforce 730 is nothing.. important is 10xx, i thing that if it would work we would know, it would be big thing.. This looks just like bugged release notes, probably through some copy/paste.. I checked some Guru3D thread about this release, there wasnt any positive info..

## Page 285

#4261 | IntiMD | ⇗ @ruthan IIRC the xp package doesn't even have the relevant HWIDs for 10xx gen in the .infs, and even if you add them and try to force the install on them, best case scenario would be 2d acceleration available but lack of 3d acceleration. worst case scenario it would fail to install the driver at all.

#4262

gordo999

> Zitat von ⇗ ruthan im Beitrag ¶ #4260

> If you mean that this driver is working with Geforce 730 is nothing.. important is 10xx

⇗ @ruthan ....from the 368.91 release notes....
"Supported cards :
GeForce 1000 series:
GTX 1080, GTX 1070, GTX 1060..."
If the 368.91 drivers support the GT-730 on XP they should support the 10xx series. Why would they not? What errors do you get when you try to load the 368.91 package? Does it install but the 10xx series card does not work? If so, I'd say your XP installation is not working correctly. You may have wrong or missing chipset drivers.
There was issue with the acpi driver before daniel_k fixed it. I don't recall the details but apparently it did not show the display driver. You might want to research that.
It took me several attempts to get 'different' driver packages loaded. The installer complained of missing files. When I finally got the proper package from Nvidia, with a good download, the good file had many more folders and files than the bad one. The good one loaded immediately with no errors and the GT-730 is working very well.
Sorry...I did not check to see which motherboard/chipset you have. Mine is an Intel B360 300-series chipset. I have presumed, apparently incorrectly, that the reference to 'modern' chipsets in the title of this thread means really new chipsets like the 300-series. XPLIVES had to straighten me out on that so maybe I spoke too soon.

#4263

gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #4262

> You may have wrong or missing chipset drivers.

⇗ @ruthan ...here's an example of what I mean. Recently, I did a repair install on my XP installation using an XP install disk slipstreamed with SP3. My Nvidia card and my Creating Xfi card were working before the repair install but after the driver packages for both could not find the Nvidia or Xfi cards. That was because the XP SP3 drivers lacked the proper chipset drivers for my 300-series B360 chipset. The PCIe ports were not being enumerated correctly.
I got them back again by slipstreaming the unofficial XP SP4 update with the XP SP3 disk. Somewhere in the SP4 update they have chipset drivers for my B360 chipset. I don't think they are drivers for the hardware ID but for the compatible hardware ID. With those chipset drivers installed the Nvidia and Creative boards started working again.
BTW...the SP4 unofficial update has SATA drivers signed by Fernando, so Harkaz, who created the SP4 updater, knows about these things. I did have to reinsert the ACPI mod by daniel_k to get around the 0XA5 ACPI error during installation. I also had to fix the unattend in nlite to allow the installation to stop at the point where a repair install is available. If it's marked as a full unattend it will not allow a repair install but will allow a parallel XP installation, which doesn't help a lot unless you want a clean install.
Another point to note. Anyone trying a repair install of XP should be sure to remove Internet Explorer first. It can be done in Add/Remove Hardware under add/remove Windows components. Otherwise the installtion will go into a loop in the final stage. You can also reboot into safe mode at that point and remove IE then.

#4264 | ruthan | Chipset doesnt matter.. Geforce 730 using same chip logic as Geforce 9xx card, 10xx is new architecture.. to make it working you need at least some new code.. Because Nvidia want to save some time and money they didnt wrote that code.. and unless someone hack their drivers it will never work. If it would work, we would have lots of success stories and videos around.. but we have only some release notes mistake.

#4265

XPLives

⇗ @Fernando

> Zitat von ⇗ Fernando im Beitrag ¶ #4202

> > Zitat von ⇗ daniel_k im Beitrag ¶ #4194

> > I was asked to delete all of my modified 3rd party drivers to avoid copyright issues here. I've been told that in the near future, all modified files that are copyrighted will be deleted.

> Just for clarification:
> Only attached or linked drivers, whose *.SYS file code has been altered, will be deleted by the Win-RAID Forum team (to avoid any problems with the manufacturer of the original driver).

Fernando, what caused this change of thinking? I seemed to recall many drivers were modified and uploaded here as far back or earlier than 8-1-2019. I assumed that somehow your site had some German immunity since your Intel SATA drivers seemed to be allowed although no sys modification and when diderius6 and daniel_k uploaded their modified files I assumed you were okay with it then or it was allowed due to some oversight being a German site.
What happened since then that caused this sudden enforcement?
Were you alerted by any of the driver companies directly to take them down? And if so which ones?
Most of the XP drivers that are modified seem to be defunct and no longer updated or old enough that no one really cares about anymore or as you put it once a 20 year old OS that no one has time for anymore so at best there is no profit involved for those companies as most have shifted towards Windows 10 drivers only.
Anyhow I'm just wondering what transpired as it seems starting February 29th, 2020 a lot of these files have been taken down. I think a lot of the continued popularity of this thread could be attributed to diderius' and daniel_k's contributions to this massive thread involving their files for newer systems.

#4266

XPLives

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #4203

> My last post here. Please read this:
> INTEL END USER SOFTWARE LICENSE AGREEMENT
> IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.
> THE FOLLOWING NOTICE, OR TERMS AND CONDITIONS SUBSTANTIALLY IDENTICAL IN NATURE AND EFFECT, MUST APPEAR IN THE DOCUMENTATION ASSOCIATED WITH THE INTEL-BASED PRODUCT INTO WHICH THE SOFTWARE IS INSTALLED. MINIMALLY, SUCH NOTICE MUST APPEAR IN THE USER GUIDE FOR THE PRODUCT. THE TERM "LICENSEE" IN THIS TEXT REFERS TO THE END USER OF THE PRODUCT.
> LICENSE. Licensee has a license under Intel's copyrights to reproduce Intel's Software only in its unmodified and binary form, (with the accompanying documentation, the "Software") for Licensee's personal use only, and not commercial use, in connection with Intel-based products for which the Software has been provided, subject to the following conditions:
> (a) Licensee may not disclose, distribute or transfer any part of the Software, and You agree to prevent unauthorized copying of the Software.
> (b) Licensee may not reverse engineer, decompile, or disassemble the Software.
> (c) Licensee may not sublicense the Software.
> (d) The Software may contain the software and other intellectual property of third party suppliers, some of which may be identified in, and licensed in accordance with, an enclosed license.txt file or other text or file.
> As you can see, 99.99% of all software available here is theoretically being distributed/modified against Intel's EULA.
> Even the Coffee Lake mod is a clear case, as they weren't originally intended for use with non-certified boards.

It's not entirely clear but were you notified to not upload your modified drivers from one of the driver companies or was it Fernando only?
I naturally and incorrectly assumed that the site being in Germany had some sort of immunity than if it were based in the United States which is why when diderius6 or yourself uploaded modified files I thought it was allowed.
This may not matter now being your last post here. But at the time I was considering to split this main thread into ACPI, USB 3.0, and XP Pro 64-Bit threads when it was around 2500 messages aside from the diderius6 and dencorso objections one major factor that played into me not splitting the thread had to do with you. When I realized the connection of where I had seen your name before involving your work on the Creative Labs drivers it gave me further pause and ultimately decided even though it would have been a lot of work and doable maybe with Lost_N_Bios' help it may have in some way jeopardized your own work or momentum on the drivers.
I had not yet had time to create my own XP dedicated forum site (maybe one day) but as long as you can continue your work and archive it on your own site or elsewhere I'm sure it will be continually appreciated. If you are able to write a guide on how to learn and perform these ACPI and USB 3.0 modifications it would probably help further the progress of it. I know trying to do this as a solo mission probably is a huge undertaking but perhaps others could then take up the slack and expand the efforts you've contributed thus far. As a fellow Asian as well as long you are able to persist you can accomplish your goal.

#4267

Fernando

⇗ @XPLives:
Here is my statement:

1. As Admin of this Forum I am responsable for everything, what is published here. It is my duty to take care about the adherence of the Copyright rules. Otherwise I risk, that the Forum will be closed by the related authority.
2. Nothing would have happened from my side, if the driver modder had given just the information within the Forum, that interested users may send him/her a PM.
3. The Copyright rules are world wide valid. So there is no "German immunity" regarding its adherence.
4. It makes a big difference, whether a Copyright violation is "allowed" or just "tolerated" by a certain chipset manufacturer.

5. > Zitat von ⇗ XPLives im Beitrag ¶ #4265

   > What happened since then that caused this sudden enforcement?

   It took some time until I had recognized, that some users had linked or attached modded drivers, whose hex code and digital signature had been manipulated. As soon as I had realized that, I did what my duty as Forum Admin is.
   Additional problem: The users of the related drivers got not even the information,
   a) that the driver itself (= *SYS file) has been modified and
   b) who had done the modifications.

6. > Zitat von ⇗ XPLives im Beitrag ¶ #4265

   > Were you alerted by any of the driver companies directly to take them down?

   Yes, but I will not publish the name of the Company.

#4268 | YuriyCN | According to Newtons Law 3, the force of action is equal to the strength of the reaction. They will receive a similar blow from consumers in response. Soon the time will come when users will stop buying Windows 10, remaining on the old OS, which is much simpler, more convenient and do not have unsolicited functionality.
#4269 | Outbreaker | If Linux gets more and more gaming support it will be soon by by for Windows. POP_OS! is a good example off improving the gaming experience on Linux. I would even pay 10% more for a Game that has a good native Linux support.

#4270

schreiberstein

Hey there!
After my GTX 780 died, I refrained from experimenting with bare-metal Windows XP on my Gigabyte Z390 Designare.
It wasn't a good experience overall anyway. My focus shifted to PCI-passthrough via KVM virtualization on Linux - But I was unable to pass through graphics cards to non-UEFI Windows guests (e.g. Windows XP i386).
I purchased a NEC based PCI USB 2.0 which worked in the native UEFI environment (during boot) and I was able to pass that to a Windows 10 guest.
However, there were so many IRQ/IOMMU group conflicts that I decided not to pursue this any longer.
(A KVM virtualized Windows XP guest starts in a split second though. Really really impressive, especially when compared to bare metal performance and boot time)
I would now be interested in building an AMD Ryzen X570 based system, paired with an AMD Radeon 7970 or 7950 (supports both Windows XP and latest MacOS, as well as Windows 10 compatible Adrenaline drivers).
Loosely following this thread, I have noticed that some folks on here are already on this platform. Is there any brand I should avoid or favor?
I'd like to ask about your experience with it, especially in comparison with other Intel systems.
Is compatibility better? At least the Windows 7 compatibility seems outright better. My Z390 board has this weird stutter-effects on Windows 7, regardless of what GPU I use.
Since I have an external box for traditional PCI cards, I would primarily use the NEC based USB2 chip for USB keyboard and mouse.
I would be thankful for any suggestions.
Cheers,
schreiberstein

#4271

gordo999

> Zitat von ⇗ schreiberstein im Beitrag ¶ #2946

> ⇗ @diderius6 ...I have just installed this *** HAL.dll and intelppm on my XP system and voila...This magically fixed all web browsers and some obscure game demos from 2005 that I attempted to run.

⇗ @diderius6 ... ⇗ @schreiberstein ...Just want to confirm that I had the same success using hal and intelppm. I had not paid much attention to those files and was having issues running Firefox on XP and with direct3D issues on games. The games would play sound fine but the video would stall so much the games became unplayable.
I am happy to report my Firefox browser now works perfectly and my games as well. Congratulations to all you guys who worked on this and thank you kindly. I should mention my system uses an Asus B360M with the Intel B360 chipset and an Intel i5-8400 processor. I am using an Nvidia GT-730 video card with a Creative Xfi extreme music sound card.

#4272

XPLives

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #4270

> Hey there!
> After my GTX 780 died, I refrained from experimenting with bare-metal Windows XP on my Gigabyte Z390 Designare.
> It wasn't a good experience overall anyway. My focus shifted to PCI-passthrough via KVM virtualization on Linux - But I was unable to pass through graphics cards to non-UEFI Windows guests (e.g. Windows XP i386).
> I purchased a NEC based PCI USB 2.0 which worked in the native UEFI environment (during boot) and I was able to pass that to a Windows 10 guest.
> However, there were so many IRQ/IOMMU group conflicts that I decided not to pursue this any longer.
> (A KVM virtualized Windows XP guest starts in a split second though. Really really impressive, especially when compared to bare metal performance and boot time)
> I would now be interested in building an AMD Ryzen X570 based system, paired with an AMD Radeon 7970 or 7950 (supports both Windows XP and latest MacOS, as well as Windows 10 compatible Adrenaline drivers).
> Loosely following this thread, I have noticed that some folks on here are already on this platform. Is there any brand I should avoid or favor?
> I'd like to ask about your experience with it, especially in comparison with other Intel systems.
> Is compatibility better? At least the Windows 7 compatibility seems outright better. My Z390 board has this weird stutter-effects on Windows 7, regardless of what GPU I use.
> Since I have an external box for traditional PCI cards, I would primarily use the NEC based USB2 chip for USB keyboard and mouse.
> I would be thankful for any suggestions.
> Cheers,
> schreiberstein

AMD has better DOS compatibility. Intel has better XP compatibility. Those were the most significant.
As for why your GTX 780 died could be due to old age/overheating from dirty fans.
Radeon 7000 HD series is pretty ancient but if it does XP and Mac OS natively then you should choose that than nVidia 700 or 900 series.
A GT 730 might be a better card for Intel system for fanless solution on the cheap for XP. Mac OS if can be made to work then this would be a good fanless hackintosh hybrid.
Not sure about Windows 7 stuttering problem. Most likely ACPI is no longer compatible on Z390 and needs a BIOS Mod. If it doesn't stutter in Windows 10 then you have your answer.

#4273

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #4272

> Not sure about Windows 7 stuttering problem. Most likely ACPI is no longer compatible on Z390 and needs a BIOS Mod. If it doesn't stutter in Windows 10 then you have your answer.

⇗ @XPLives ....The Z390 is a more expensive version of my B360. I have no issues with stuttering in W7 and have had no problems with it at all once the chipset drivers were updated and the USB driver from canonkong was installed. My GT-730 has worked on W7 from the start as well as my Creative Xfi extreme music card. I had W7 USB 3 running on an add-on card with a VIA chipset before installing the canonkong drivers.
With XP, I was getting complaints from XP that my i5-8400 processor had issues. Video on games would stutter and stop randomly and hitting the escape key often recovered from the stalls. No browser would run 100%. With Firefox 52, I got it to run by keeping the task manager open. Firefox would not respond to mouse clicks till I had clicked the mouse on task manager...go figure.
All of those problems cleared up when I installed hal and intelppm from this site.

#4274

XPLives

⇗ @gordo999
Sounds like using those 2 files will have the same effect as the BIOS Mod.
Go ahead and add a link to the proper post you found each driver. I'll have to check if these files fix any anomalies you had on my own system.
List which games would stutter and stop randomly before applying the two files.
When I have more time I will investigate this. For the moment I haven't used Firefox yet on the Z370. Mainly browsing on Ivy Bridge.
EDIT by Fernando: Unneeded fully quoted post and blank lines removed (to save space and for a better readability).

#4275

schreiberstein

⇗ @XPLives
I bought it used a few months prior to using it as my daily driver.
And then it just died with artifacts. It was clean and I did not game for more than an hour with it in total.
Then it just crashed my Mac system while doing some light text editing work.
Now, I cannot load the drivers or the system will hang. I attempted underclocking the RAM and core by replacing the BIOS, but I think the VRAM is bad.
Even in VESA mode I have artifacts that seem to be caused by bad video RAM.
I have lost my faith in Intel platforms. People advised me that I should go with a Pentium 4 / 775 system with i865 chipset for Windows 98 retro stuff, but I had nothing but problems with this Intel garbage. Same for other Intel based machines. Meanwhile, all my Socket 939 / AM2 machines are rock steady whenever I drag them out my basement. They POST very quickly, detect all attached drives, etc. Given that the AMD Vanilla hackintosh community is doing very good process, I think I will ditch Intel altogether in the foreseeable future.
Cheers,
schreiberstein

## Page 286

#4276

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #4274

> Sounds like using those 2 files will have the same effect as the BIOS Mod.
> Go ahead and add a link to the proper post you found each driver.

⇗ @XPLives ...it was post #2942 ..... ¶ #2947
Games were Myst 3 Exile and Myst 5 End of Ages. The first was barely playable but froze all the time requiring a reboot of the game. Myst 5 would not even start since it had no mouse at the page where you select New Game, etc. The video and sound was fine till that point just no mouse. Hal and intelppm fixed both.

#4277 | Outbreaker | Can someone send me the latest USB 3.0 driver files, acpi.sys ffile, Generic SATA/AHCI driver files and the WinXPPAE.EXE file?

#4278

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #4276

> > Zitat von ⇗ XPLives im Beitrag ¶ #4274

> > Sounds like using those 2 files will have the same effect as the BIOS Mod.
> > Go ahead and add a link to the proper post you found each driver.

> @XPLives ...it was post #2942 ..... ¶ #2947
> Games were Myst 3 Exile and Myst 5 End of Ages. The first was barely playable but froze all the time requiring a reboot of the game. Myst 5 would not even start since it had no mouse at the page where you select New Game, etc. The video and sound was fine till that point just no mouse. Hal and intelppm fixed both.

I had downloaded this before but never used it. I redownloaded it now to do a later test. I know one nVidia demo I tested did not work correctly with DK_ACPI.
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197)
Don't think I have Myst 3 Exile and Myst 5 at least off hand. Might be in one of my storage boxes. Any others games fixed?

#4279

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #2942

> PS: Here are the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem.

Please specify which timer problems are you talking about?

#4280 | ruthan | Look at these threads, it was before patches: ⇗ https://msfn.org/board/topic/178240-winx...comment-1161108 ⇗ https://msfn.org/board/topic/178110-xp-o...comment-1169100
#4281 | POE_UK | You can use EASY2BOOT to make a bootable usb XP drive, however i strongly advise against doing this, during installation EASY2BOOT installs very dodgy storage drivers that cause nothing but problems, including XP picking up on the fact that the install has been tampered with, a £10 optical drive and a good CDR disc is the way to do it.
#4282 | YuriyCN | When using hacked hal.dll and intelppm.sys from the halplusintelppmXPSP3.rar, I get an increase in the performance of my SSD drive from 180-190 MB/s to 250-260 MB/s. I have not noticed any other changes, so I recommend this patch for use - ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197)

#4283

YuriyCN

Additional tests in Performance Test 8.0 showed, that using hacked hal.dll and intelppm.sys improves performance:
SATA SSD = + 30%
CPU = +3%
2D = +5%
3D = 0%
Memory = 0%

#4284

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #2942

> @daniel_k @schreiberstein
> Here are the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem.

Hello diderius6!
In your message ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197) from Sat Oct 12, 2019 6:26 pm you proposed to use "the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem", and you attached the "halplusintelppmXPSP3.rar" archive with these files.
Please answer a few questions:
1) Could you please write in more detail what the essence of this patch is, what problem does it solve?
2) What hardware is it intended for?
3) Is the latest version of the corrected files attached to the message, or do you have a newer one?

#4285 | Andalu | ⇗ @YuriyCN Did you solve the issues encountered some time ago using the USB3 drivers and WinXPPae2 together?
#4286 | YuriyCN | Yes! This problem were resolved when I use WinXP with updates to 2018. On the clean MSDN image WinXP SP3 - the problems were not solved. Apparently, the reason was in some kind of sys-file and after the update was decided by itself.

#4287

Andalu

⇗ @YuriyCN
Good news from you too then
On my system, both USB3 driver and WinXPPae /all work without the issues recognized some time ago for the updated and not updated ISOs.
I solved the issues by replacing the existing hal.dll with the version of the package "halplusintelppmXPSP3.rar" and amdxhci.sys with the version of the package "amdxhc_pae_fix.rar". So far I have not encountered any other problems.
Here the screenshot referred to my updated system started with 6 USB devices already connected to the board and 'chkdsk' and 'format' fully functional (firefox also works with no mouse input stumblings):
⇗

#4288

YuriyCN

Hello diderius6!
In your message Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197) from Sat Oct 12, 2019 6:26 pm you proposed to use "the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem", and you attached the "halplusintelppmXPSP3.rar" archive with these files.
Please answer a few questions:
1) Could you please write in more detail what the essence of this patch is, what problem does it solve?
2) What hardware is it intended for?
3) Is the latest version of the corrected files attached to the message, or do you have a newer one?

#4289

ITriedOkay

Hello, is it still possible to request a modded ACPI.SYS for my PC?

> Zitat von ⇗ Outbreaker im Beitrag ¶ #4277

> Can someone send me the latest USB 3.0 driver files, acpi.sys ffile, Generic SATA/AHCI driver files and the WinXPPAE.EXE file?

Check your PMs.

#4290 | infuscomus | ⇗ @ITriedOkay have you tried the existing modded acpi.sys?

## Page 287

#4291 | ITriedOkay | ⇗ @infuscomus Yes... I tried ⇗ DK's version and ¶ Dietmar's version. No luck with either.
#4292 | infuscomus | ⇗ @ITriedOkay I'll PM you one last version - ⇗ @diderius6 called it the "outer space" version. If that doesn't work then we can only hope ⇗ @diderius6 comes back here one day to help you with it.
#4293 | ITriedOkay | The outer space version didn't work, the PC just goes into a black screen... The default acpi.sys yields this exact stop error: STOP: 0x000000A5 (0x00000011, 0x00000008, 0xF72D0240, 0x20160527)
#4294 | infuscomus | ⇗ @ITriedOkay curious that you got a black screen, it may yet still work have you integrated the outer space acpi.sys into your XP install media?
#4295 | ITriedOkay | It's not an install media actually, it's a VHD that has Windows XP pre-installed, which I boot directly on PCs. ⇗ This page will give you more information on how I'm doing this... I can already replace ACPI.SYS inside it with ease, if this is what you're asking.
#4296 | infuscomus | ⇗ @ITriedOkay Thats an unusual setup, I'd prefer booting off a physical drive myself. your XP installation might not be setup to use ACPI properly I'll PM you some XP install media to test

#4297

YuriyCN

> Zitat von ⇗ ITriedOkay im Beitrag ¶ #4293

> The outer space version didn't work, the PC just goes into a black screen... The default acpi.sys yields this exact stop error:
> STOP: 0x000000A5 (0x00000011, 0x00000008, 0xF72D0240, 0x20160527)

5 versions of the modified file ACPI.SYS + original version
The BEST version - ACPI+USB(all versions)\ACPI.SYS\acpi_1 (the best).sys
⇗ https://www67.zippyshare.com/v/bsNhCGhi/file.html

#4298 | infuscomus | ⇗ @YuriyCN your upload forgot to include the USB 3.0 Hub driver, and the inf file for installing the driver too.

#4299

Pill Monster

> Zitat von ⇗ Andalu im Beitrag ¶ #4210

> > Zitat von ⇗ daniel_k im Beitrag ¶ #4203

> > My last post here.....

> I'm sad to read this. It's a big loss for the forum. Thanks so much for your great work

Just saw this.
I sent DK a pm earlier & wondered why he hadn't responsed. Dunno what happened but it's a shame. Hope he returns

#4300 | ruthan | All lowlevel guys are gone for long time, because of forum copyright policy..

#4301

YuriyCN

> Zitat von ⇗ infuscomus im Beitrag ¶ #4298

> @YuriyCN
> your upload forgot to include the USB 3.0 Hub driver, and the inf file for installing the driver too.

This is the USB3 driver for modern Intel motherboards 100, 200, 300 - series. In theis archive driver for Windows XP and a separate patched file for PAE mode - ⇗ https://www34.zippyshare.com/v/JbI6WPAU/file.html

> Zitat von ⇗ ruthan im Beitrag ¶ #4300

> All lowlevel guys are gone for long time, because of forum copyright policy..

Please, give me the forum URL where the experts went.

#4302

gordo999

> Zitat von ⇗ ITriedOkay im Beitrag ¶ #4293

> STOP: 0x000000A5

⇗ @ITriedOkay ...0xA5 is an ACPI error. Maybe your system file checker is replacing the one you insert with the original. If so, you have to insert ACPI offline. On my system XP is on its own disk and I can start W7 and hot plug XP. Then I can insert a file like ACPI.sys from W7 without SFC replacing it.
I am presuming your system is running, maybe it's not. You can bypass the acpi error using the installation disk. Run the installation and when you see the prompt to hit F6 to load drivers, hit F7 instead. I hit it several times to be sure. The installation should run cleanly to the point where it asks you to hit R to enter repair mode. Don't go past that point, use F3 or whatever is indicated to get out of there. At least that will tell you if your system is good to that point.
BTW...if you do reach the point where you can hit R to enter repair mode, you will reach a command prompt. You might be able to insert the modded acpi from there. If you change directory to %windir%\system32\drivers, look at the size of acpi and compare it to the size of the modded acpi. They should be the same if you inserted it properly to the right directory.
If you get an 0x7F error before the R prompt, you have a problem with the SATA driver.
BTW...I have not seen a description of your system. Can you supply that?

#4303

gordo999

> Zitat von ⇗ ruthan im Beitrag ¶ #4300

> All lowlevel guys are gone for long time, because of forum copyright policy..

⇗ @ruthan ...it's not the forum copyright policy, it's the threats the low level guys received directly from Intel, I think it was. Daniel_k told us that. Fernando is just trying to follow a policy that will appease Intel.
I don't think anyone knows where the guys have gone.

#4304

ruthan

Well, i read here other version story - that Fernando was harassed by some unknown company, so he changed / forced policy, what piss off Daniel and other guys, but i can be wrong.
I wouldnt be surprised if it would be Intel or MS.
Is loss for everyone except maybe some layers and bullies, its like right to repair things.
If understand it correctly problem is that drivers had to have some security signature to work (Microsoft thing).. and maybe Intel or others vendors were not ok, that some modified drivers were signed as original Intel or whatever ones..

#4305

ITriedOkay

⇗ @YuriyCN
The acpi_1 file didn't work, the screen still goes black.
⇗ @gordo999
I get the BSOD with XP's default acpi.sys only, as for all the modded acpi.sys files I tried (which I have inserted offline) I just get a black screen.
Perhaps I need to elaborate more on ¶ my previous post... I'm not using XP as my main OS, it's simply a portable pre-installed image that I boot up directly on my PC and others. The steps to create it are briefly explained inside the spoiler:
1. Install XP in a virtual machine, on a fixed ⇗ VHD image. Disable pagefile, hibernation, and system restore.
2. Inside the XP machine, install ⇗ the SVBus driver like you would install a SCSI/RAID driver.
3. Through Device Manager, for all IDE and System devices that use a branded driver (e.g. Intel), update them to use XP's generic drivers. Restart the machine when necessary.
4. Shut down the machine, and copy the VHD to a USB stick with ⇗ GRUB4DOS 0.4.5c installed.
5. Boot from the USB, GRUB4DOS will start, mount the VHD to RAM and boot from there. After mounting is complete the USB can be removed.
I have booted this image countless times on several PCs, including modern-ish PCs (~2015) with no problem. I only faced the ACPI issue when I tried booting on my new laptop which was manufactured in 2019. FWIW the laptop is a Dell G5 5590.
⇗ @infuscomus
I think XP is setup correctly, see my reply to gordo above. The problem probably lies with my hardware being "non standard"... For example I tried installing Windows 7 at first and it didn't detect any of the internal drives, so I installed Windows 10 and the setup went fine. A similar case is possible with the ACPI and XP.

## Page 288

#4306

infuscomus

> Zitat von ⇗ ITriedOkay im Beitrag ¶ #4305

> For example I tried installing Windows 7 at first and it didn't detect any of the internal drives

^
this
XP likely has the same issue
we do have a generic AHCI storage driver for XP now - but I've never tried replacing it on an existing install, only new installs, so i'm not 100% sure how to install it on an existing system.
also, since you are getting A5 BSOD, you will still need the patched ACPI driver aswell.

#4307 | diderius6 | ⇗ @infuscomus You can change very easy to the generic STORAHCI driver, when you copy the needed files and run the *.reg patch to the registry via a second compi Dietmar

#4308

YuriyCN

> Zitat von ⇗ gordo999 im Beitrag ¶ #4303

> it's not the forum copyright policy, it's the threats the low level guys received directly from Intel, I think it was. Daniel_k told us that. Fernando is just trying to follow a policy that will appease Intel.
> I don't think anyone knows where the guys have gone.

It is unlikely that these threats came from Intel... Most likely from Microsoft. Intel still sells its hardware, and Microsoft transfers everything to Windows 10. Users who stay on Windows XP and Windows 7 - Microsoft are across the throat.

#4309

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #4307

> @infuscomus
> You can....
> Dietmar

In your message ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197) from Sat Oct 12, 2019 6:26 pm you proposed to use "the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem", and you attached the "halplusintelppmXPSP3.rar" archive with these files.
Please answer a few questions:
1) Could you please write in more detail what the essence of this patch is, what problem does it solve?
2) What hardware is it intended for?
3) Is the latest version of the corrected files attached to the message, or do you have a newer one?

#4310

AddFun

I tried moving my successful WinXP 32bit install from a Ryzen/X370 machine (thank you guys!) to a Z390/CoffeeLake machine. Surprisingly, the system/OS booted that XP cloned partition just fine. Problem is USB. I get to desktop and have no control. Supposedly this motherboard has dedicated USB2 ports but they are handled by the same Z390 chipset. This Z390 motherboard has no PS/2 ports. So, now the system boots and sits on the desktop and I cant do much. I have the latest (I think) amdxhc, amdhub30, etc files sitting in their respective directories but still no USB3.0. The New Hardware wizard pops up but I cant interact with it. Shouldn't USB auto config and self install?
Other than complex scripting tools, batch files, etc, how would you guys recommend I proceed? Install seems to be as stable and bootable as the Ryzen clone, just no USB3.0 (no KB/mouse). What am I missing?

#4311

ruthan

> Zitat von ⇗ AddFun im Beitrag ¶ #4310

> Other than complex scripting tools, batch files, etc, how would you guys recommend I proceed? Install seems to be as stable and bootable as the Ryzen clone, just no USB3.0 (no KB/mouse). What am I missing?

Someone wrote that you have to enable in port 60-64 USB feature, you can try it, otherwise solution, would be to buy USB-2 PCI-E addon card.

#4312

usa1ec

> Zitat von ⇗ AddFun im Beitrag ¶ #4310

> I tried moving my successful WinXP 32bit install from a Ryzen/X370 machine (thank you guys!) to a Z390/CoffeeLake machine. Surprisingly, the system/OS booted that XP cloned partition just fine. Problem is USB. I get to desktop and have no control. Supposedly this motherboard has dedicated USB2 ports but they are handled by the same Z390 chipset. This Z390 motherboard has no PS/2 ports. So, now the system boots and sits on the desktop and I cant do much................

Try installing this OS Windows XP SP3 RUS (update 02.2020 for Intel MB) - ⇗ https://yadi.sk/d/NWO5uafRjjsT2Q
Unfortunately, it is the Russian version of Windows XP SP3 with update feb 2020, but it integrates all the drivers necessary for a modern Intel motherboard + ACPI mod driver + SATA AHCI driver + USB 3.0 driver + PAE patch >4GB RAM.
During installation, the "Component Registration" stage will take a long time, during which (silent mode) the following are installed: Microsoft Visual C ++ x86 Redistributable (2005 + 2008 + 2010 and 2019, all editions), MSXML 4.0 Parser, Flash Player v32, DirectX 9 (June 2010), Microsoft .NET Framework (version 2.0 + 3.0 + 3.5 + 4.0). The component registration phase will take 15-20 minutes and this is normal! OS was tested on the Gigabyte GA-Z170-D3H motherboard (Intel Z170 chipset, LGA-1151 socket, i7-6700K processor, 8 cores @ 4GHz, 16GB RAM DDR4).

#4313 | AddFun | Tried that option before hand. No go. I have to figure somekind of way to automate driver install and skip the New Hardware wizard. Does WinXp have undocumented features or registry switches to enable unattended driver/device install post OS install?
#4314 | usa1ec | Try to install Windows XP SP3 RUS (update 02.2020 for Intel MB) - ⇗ https://yadi.sk/d/NWO5uafRjjsT2Q from the CD/DVD disc. If everything works, then take the drivers from it and integrate it into any English image with nLite.
#4315 | ITriedOkay | ⇗ @infuscomus I did try the AHCI driver but it's useless to me because my XP image boots entirely in RAM, it does not need any HDD. ⇗ @AddFun You can disable the "Found New Hardware" wizard using the method outlined ⇗ here (assuming you have SP3 which should have ⇗ this hotfix installed). Note that the driver that you want auto-installed should be somewhere XP can look, for example, the drivers folder in windows... Give it a try?
#4316 | infuscomus | ⇗ @ITriedOkay Try switching to a different RAMDisk driver - I've noticed with RAMDisk drivers that they all will only work on some systems but never on all. There are 3 RAMDisk drivers I know of - Imdisk, Firadisk, WinVBlk For ACPI A5 BSOD switch back to the outerspace ACPI driver since it didn't give you a BSOD

#4317

Pill Monster

> Zitat von ⇗ ITriedOkay im Beitrag ¶ #4315

> @infuscomus
> I did try the AHCI driver but it's useless to me because my XP image boots entirely in RAM, it does not need any HDD.

Please disconnect all your HDDs and boot up. Post results here. ;)

#4318

ITriedOkay

⇗ @infuscomus
I did use Firadisk and WinVBlock in the past years, until SVBus was released and turned out much better. But I'll try both of them again (with the outerspace acpi) and report back.
ImDisk does not apply in this situation because it's only usable from inside windows.
⇗ @Pill Monster
I'm using a laptop, disconnecting the internal HDDs from it will be extremely difficult if not impossible. FWIW almost every laptop I booted this image on, XP did not detect the internal HDDs but still ran fine... It's fairly safe to say that the HDDs are not the problem.

#4319

gordo999

> Zitat von ⇗ AddFun im Beitrag ¶ #4310

> Problem is USB. I get to desktop and have no control. Supposedly this motherboard has dedicated USB2 ports but they are handled by the same Z390 chipset.

⇗ @AddFun ....I got XP USB going on the B360 (same chipset class as Z390) using daniel_k's AMD USB drivers. Alternately, you can buy an add-on USB card and find XP drivers. For W7, I used Canonkong's USB drivers.
I use an add-on card with a VIA chipset and I found XP drivers on a Czech site. Now I have all my mobo USB ports running on XP as well as the VIA chipset ports. I only have 3 USB3 ports on the card but I use a powered 7 port USB extender run from one of the VIA ports. It's important than an extender have it's own power.

#4320 | ITriedOkay | ⇗ @infuscomus Neither Firadisk nor WinVBlock worked, as I suspected. Same result as SVBus.

## Page 289

#4321 | infuscomus | ⇗ @ITriedOkay can you try doing a normal XP install from scratch to a HDD/SSD on your system?

#4322

ITriedOkay

⇗ @infuscomus
Ok, I modified an XP ISO to use the outerspace acpi.sys and got a black screen after "Setup is starting", then the PC rebooted.
In case I made a mistake, that was my process:
1. Using cmd (on Windows XP) I ran the command makecab acpi.sys on the outerspace acpi.sys file, obtained a ACPI.SY_ file.
2. Using PowerISO, I replaced the old ACPI.SY_ in the I386 folder on the XP ISO with the one I just obtained.
3. Booted from the modified ISO.

#4323

infuscomus

⇗ @ITriedOkay
Oh! I see now!
PowerISO doesn't write the ISO boot record for XP correctly - it can do it but it's a bit of a hassle
instead use a program called nlite
⇗ https://www.nliteos.com/download.html
after downloading nlite
first extract the contents of the XP ISO into a folder
e.g.
C:\XPISO
next replace the existing ACPI.SY_ in C:\XPISO\I386 with the one you already made with makecab earlier
next extract SP3.CAB
C:\XPISO\I386\SP3CAB
replace the acpi.sys in C:\XPISO\I386\SP3CAB with the modded version and then rebuild with makecab
replace SP3.CAB with modded SP3.CAB
next open nlite
point nlite to C:\XPISO as source
click next
click bootable ISO then next
click make ISO
click next
click finish

#4324

Pill Monster

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4308

> > Zitat von ⇗ gordo999 im Beitrag ¶ #4303

> > it's not the forum copyright policy, it's the threats the low level guys received directly from Intel, I think it was. Daniel_k told us that. Fernando is just trying to follow a policy that will appease Intel.

> It is unlikely that these threats came from Intel... Most likely from Microsoft. Intel still sells its hardware, and Microsoft transfers everything to Windows 10. Users who stay on Windows XP and Windows 7 - Microsoft are across the throat.

Or Microsoft may be concerned with keeping a lid on the 20yr lie that to make use of over 4GB of memory, VM or physical, , required an upgrade to Server 2003 While at the same time Intel is concerned the public will find out their $2500 36bit Xeon was the only horse in the stable which could use over 4GB until C2D.
Meanwhile, in AMD64 land.....:P
Intel & MS still pay Wikipedia editors to misleading the public over that topic. Russonivich's statement blaming driver issues was just a marketing spin.
FWIW Do you guys know who Geoff Chappell is, or heard of him?
@Itriedok:
I was being a smart ass :P

#4325

Pill Monster

> Zitat von ⇗ ITriedOkay im Beitrag ¶ #4318

> @Pill Monster
> I'm using a laptop, disconnecting the internal HDDs from it will be extremely difficult if not impossible. FWIW almost every laptop I booted this image on, XP did not detect the internal HDDs but still ran fine... It's fairly safe to say that the HDDs are not the problem.

I was just being a smartass. :P
Ramdisks are basically....snake oil
Kinda like PrimoCache does same job as Windows File System cache.
But hey prove me wrong... :)

#4326

Pill Monster

> Zitat von ⇗ ruthan im Beitrag ¶ #4300

> All lowlevel guys are gone for long time, because of forum copyright policy..

I'm seriously sorry to hear that. On sites such as this one forum members with real technical knowledge are nothing but an asset, whatever their field.
Without them the community dies..

#4327

gordo999

> Zitat von ⇗ ITriedOkay im Beitrag ¶ #4322

> Ok, I modified an XP ISO to use the outerspace acpi.sys and got a black screen after "Setup is starting", then the PC rebooted.

⇗ @ITriedOkay ...My experience after 'Setup is starting', when things went wrong, was a BSOD with an 0x7F. That was related to the SATA drivers.
I am presuming you have started the installation disk from boot, watched the drivers loading, then setup has reached the stage where it is ready to install XP. In other words, the modded acpi has gotten you past the original stage where you got the 0XA5 error.

#4328

YuriyCN

diderius6
In your message ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (197) from Sat Oct 12, 2019 6:26 pm you proposed to use "the hacked hal.dll and intelppm.sys for XP SP3, which solve the timer problem", and you attached the "halplusintelppmXPSP3.rar" archive with these files.
Please answer a few questions:
1) Could you please write in more detail what the essence of this patch is, what problem does it solve?
2) What hardware is it intended for?
3) Is the latest version of the corrected files attached to the message, or do you have a newer one?

#4329 | infuscomus | ⇗ @YuriyCN see here ⇗ What exactly is the hal timer problem?

#4330

XPLives

⇗ @gordo999, ⇗ @ruthan

> Zitat von ⇗ gordo999 im Beitrag ¶ #4303

> > Zitat von ⇗ ruthan im Beitrag ¶ #4300

> > All lowlevel guys are gone for long time, because of forum copyright policy..

> ⇗ @ruthan ...it's not the forum copyright policy, it's the threats the low level guys received directly from Intel, I think it was. Daniel_k told us that. Fernando is just trying to follow a policy that will appease Intel.
> I don't think anyone knows where the guys have gone.

What / Which "Low Level" guys are you referring to that we have/had?
And where are these posts you are referring to that Daniel_K had said this?
The only thing I know is Fernando mentioned some company contacted him but did not mention what company nor mention specifically what driver (assuming it was a driver) or what file was the source of the complaint if it pertained to that. It would have been helpful if Fernando could notify me privately what company had the dispute originated and in regards to what was the exact issue as maybe some deal could have been worked out to buy/lease the source code or whatever was in dispute rather it just die there not knowing what happened and pissing everyone off. It's unclear what triggered the problem or if an alternate solution could be reached through negotiations with said company or companies.
And Daniel_K is missing so no idea if he was contacted first or Fernando about this to find helpful answers on what really happened and what was the timeline of events.
As for the assumptions made:

> Zitat von ⇗ ruthan im Beitrag ¶ #4304

> Well, i read here other version story - that Fernando was harassed by some unknown company, so he changed / forced policy, what piss off Daniel and other guys, but i can be wrong.
> I wouldnt be surprised if it would be Intel or MS.
> Is loss for everyone except maybe some layers and bullies, its like right to repair things.
> If understand it correctly problem is that drivers had to have some security signature to work (Microsoft thing).. and maybe Intel or others vendors were not ok, that some modified drivers were signed as original Intel or whatever ones..

It's doubtful it came from Intel as he didn't really work on Intel related drivers that were really essential or relevant and if they were concerning any of the Intel SATA drivers you don't even need those newer versions to install XP as the older ones work just fine or using Fernando's version. I find the simplicity of the older versions much easier to deal with than the newer bloated ones. And if anything Intel would benefit from his work selling more CPUs from more people willing to buy their CPUs to run older an OS on. Why stir up trouble and lose more sales over some dead drivers?
It's also doubtful it came from Microsoft as there are plenty of other drivers that fix problems with their OS being outdated and no longer supported that they would care. Even Fernando's slightly modified AHCI files didn't cause a problem and I'm assuming he's been doing this for over a decade. And even the "attempted" PAE fix for XP no one really used except maybe 1-5 people if I were to guess and even that patch had flaws and bugs and Server 2003 was already working perfectly so there was no need for it or for Microsoft to even care about XP running in a buggy state.
To them XP is dead and has been since 2014 or even earlier in 2009. Or if you go by their last service pack - Service Pack 3 (5.1.2600) / April 21, 2008 would be the last time Microsoft truly cared about XP in regards of support. Today they are more focused on Windows 10 domination and working to rid all users of Vista / Windows 7 / Windows 8.X off all their machines to even worry about a dead OS like XP. Even Windows 2000 is basically abandonware at this point. XP is just a cartoony GUI with more dependencies added with an annoying Windows activation that didn't exist with Windows 2000 and earlier.
I do suspect one company from a monopoly standpoint but why that company would even care baffles me if it were that one as none of their products currently support XP and would only benefit them. There is another company I also suspect since I know their work and what they are capable of but that's the only company I think that could strike a deal with if it was that exact one that contacted him/Win-Raid. Without knowing the exact details no one knows what happened as a happy solution could have been negotiated with more information.
Even after all that's said and done why any of those companies even cared about XP today is even more baffling if they are no longer are making updated drivers or products for XP or making any profit from it when they could negotiate a deal instead and generate something from nothing. And imagine if it was related to a driver they could perfect their own source code and make a better product.

#4331

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #4330

> And Daniel_K is missing so no idea if he was contacted first or Fernando about this to find helpful answers on what really happened and what was the timeline of events.

⇗ @XPLives ...see the following page, message 4203. Also 4194, a page or so before. Reading between the lines I'd say someone from Intel is behind this.
Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (281)

#4332

Zucker2k

I've been reading this thread for the last two days and going in circles trying, unsuccessfully, to install XP on my skylake laptop. So, before I totally give up on this seemingly impossible dream of running a lean OS on my laptop, I want to pitch a question to the knowledgeable folks on here:
1. Is it possible to install Windows XP on an HM170 chipset laptop (Intel Mobile Skylake)?
2. Does everything I need to make a successful install available online, or do I have to mod certain files myself?
All responses appreciated. Thank you.

#4333

AddFun

I was able to install it on a Ryzen system last year (after about 10-12 tries and various revisions of ACPI/AHCI drivers and what not). Then I moved the install to a Intel system. It's not a perfect science and there isn't a cooked/streamlined ISO provided that will accomplish this for you. (a tip, do NOT download any password protected "driver packages" or OS ISOs, from here or elsewhere, since its a common way to bypass malware scans since about, oh, 1998.)
That said, my Intel clone is still not working fully since my motherboard is USB only (no PS/2 or serial) so "technically" I have a WinXP system working on a modern intel system minus any interactivity. (I boot to desktop just fine)

#4334 | infuscomus | ⇗ @Zucker2k I sent you a PM with some tips

#4335

XPLives

⇗ @gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #4331

> > Zitat von ⇗ XPLives im Beitrag ¶ #4330

> > And Daniel_K is missing so no idea if he was contacted first or Fernando about this to find helpful answers on what really happened and what was the timeline of events.

> @XPLives ...see the following page, message 4203. Also 4194, a page or so before. Reading between the lines I'd say someone from Intel is behind this.
> Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (281)

*****
Post #4194
Wed Feb 26, 2020 8:59 pm (Last edited: Wed Feb 26, 2020 9:10 pm)

> Zitat von ⇗ daniel_k im Beitrag ¶ #4194

> I was asked to delete all of my modified 3rd party drivers to avoid copyright issues here. I've been told that in the near future, all modified files that are copyrighted will be deleted.
> Additionally, as WinXPPAE was completely written by me, I've decided not to make it available here anymore. I hope you respect my decision and do not upload it here anymore.
> In the next days, all of my modded drivers and WinXPPAE will be available at MDL Forums' Windows XP / Older OS section (forums.mydigitallife.net). The Admin gave me his OK.

*****
Post #4203
datumFri Feb 28, 2020 5:42 pm (Last edited: Fri Feb 28, 2020 5:43 pm)

> Zitat von ⇗ daniel_k im Beitrag ¶ #4203

> My last post here. Please read this:
> INTEL END USER SOFTWARE LICENSE AGREEMENT
> IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.
> THE FOLLOWING NOTICE, OR TERMS AND CONDITIONS SUBSTANTIALLY IDENTICAL IN NATURE AND EFFECT, MUST APPEAR IN THE DOCUMENTATION ASSOCIATED WITH THE INTEL-BASED PRODUCT INTO WHICH THE SOFTWARE IS INSTALLED. MINIMALLY, SUCH NOTICE MUST APPEAR IN THE USER GUIDE FOR THE PRODUCT. THE TERM "LICENSEE" IN THIS TEXT REFERS TO THE END USER OF THE PRODUCT.
> LICENSE. Licensee has a license under Intel's copyrights to reproduce Intel's Software only in its unmodified and binary form, (with the accompanying documentation, the "Software") for Licensee's personal use only, and not commercial use, in connection with Intel-based products for which the Software has been provided, subject to the following conditions:
> (a) Licensee may not disclose, distribute or transfer any part of the Software, and You agree to prevent unauthorized copying of the Software.
> (b) Licensee may not reverse engineer, decompile, or disassemble the Software.
> (c) Licensee may not sublicense the Software.
> (d) The Software may contain the software and other intellectual property of third party suppliers, some of which may be identified in, and licensed in accordance with, an enclosed license.txt file or other text or file.
> As you can see, 99.99% of all software available here is theoretically being distributed/modified against Intel's EULA.
> Even the Coffee Lake mod is a clear case, as they weren't originally intended for use with non-certified boards.

*****
Gordo999,
I read those previous messages before left by Daniel_K and never saw any direct connection. Although you can make the assumption there is some connection there. My thoughts are it was not from Intel because Fernando's modified SATA AHCI driver files never got taken down from Intel's demands. Daniel_K never contributed heavily with Intel modified drivers where they should chase after him directly. He did however modify the AMD USB 3.0 driver but nothing about that driver relates to Intel in any way and the device ID descriptions still to refer to AMD USB devices not Intel when installed.
The reason why I believe Daniel_K brought up the Intel license agreement was because he was making a point that Fernando's Intel modified drivers were allowed but his own modified drivers for some other company were not. I don't think he was finger point at Intel as being the complainer nor do I see any reason why Intel would complain since they already abandoned XP in every possible way since Ivy Bridge. Once they dropped the Intel HD Graphics driver support for XP for Haswell and later it became clear Intel didn't care and as soon as SkyLake was introduced killing off the eHCI ports was another axe to the head of XP making it tougher to use Intel USB ports for installing legacy OS more problematic.
So no I don't agree it came from Intel unless Daniel_K or Fernando verifies this. Since the Intel Chipsets have a higher % compatibility with XP versus AMD I find it less likely Intel would care about some driver modified for XP and as you know there was never a Intel USB 3.0 driver ever developed by Intel for 2K or XP so there is nothing there for Intel to complain about regarding Daniel_K. The only other DK modification of interest was a later version of the Intel RST SATA driver that I don't use because it requires two files instead of one. I find the simplicity of the older driver preferable. If Intel really cared about Daniel_K modifying this particular driver I wouldn't care as the older drivers work much better in my opinion. And there has been no possibility of hacking/modifying any later Intel HD graphics driver to work in XP thus far. I'm sure if it could be done Intel "might" be concerned if they really were against XP being installed on Coffee Lake and later chipsets. I don't see that happening and it is preferable to use a discrete graphics card instead due to better performance than any integrated Intel HD Graphics. Intel is in the business of selling CPUs and the compatibility is better than AMD when it comes to XP so I see no reason Intel would be against more users preferring to buy their CPUs to install a legacy OS. Even if Intel shut down Daniel_K's work it would have no impact. Fernando's modified SATA AHCI driver still exists so nothing has changed.

## Page 290

#4336

XPLives

⇗ @Zucker2k

> Zitat von ⇗ Zucker2k im Beitrag ¶ #4332

> I've been reading this thread for the last two days and going in circles trying, unsuccessfully, to install XP on my skylake laptop. So, before I totally give up on this seemingly impossible dream of running a lean OS on my laptop, I want to pitch a question to the knowledgeable folks on here:
> 1. Is it possible to install Windows XP on an HM170 chipset laptop (Intel Mobile Skylake)?
> 2. Does everything I need to make a successful install available online, or do I have to mod certain files myself?
> All responses appreciated. Thank you.

Without knowing what problems you encountered no one can troubleshoot without any visual proof of your problem.
But if I were to guess no laptop from SkyLake onward should work with XP. This could be due to the Intel USB 3.0 ports issue so you will eventually get stuck somewhere unable to use the mouse, touchpad, or keyboard. Second it might be using a UEFI BIOS with no CSM support. If these two obstacles exist then most likely XP cannot be successfully installed.
I would try something simpler to verify if it can even install a legacy OS on SkyLake laptop. If you can install FreeDOS onto SkyLake that would be a good indicator if your laptop has CSM support or not. If you can't boot to DOS at all then it's a dead end.
I also do not have anything newer than Ivy Bridge for laptops so I cannot test anything to confirm if SkyLake will work or not.
The other main issue even if you get it to install on your SkyLake laptop is why? What purpose are you using it for?
If it is meant for gaming then you are simply screwed. Nothing after Ivy Bridge laptop's have any XP capable driver for their graphics. It will most likely be 2D and very sluggish with the built in XP standard VGA driver. If you're not using the SkyLake laptop for any XP 3D graphics gaming then you are better off using Windows 7 or 10 and use some kind of Virtual Machine to run XP inside.
If you attach screen shots of your BSODs or what problems you are facing maybe some users here can walk you through getting it to work.

#4337 | XPLives | ⇗ @Pill Monster 2000 Advanced Server already had > 4GB memory support. And standard XP Pro 32-Bit could utilize above the 4GB range for a Ramdrive so it wasn't completely neutered. But what is the model number of this supposed $2500 36-Bit Xeon?

#4338

XPLives

⇗ @schreiberstein

> Zitat von ⇗ schreiberstein im Beitrag ¶ #4275

> @XPLives
> I bought it used a few months prior to using it as my daily driver.
> And then it just died with artifacts. It was clean and I did not game for more than an hour with it in total.
> Then it just crashed my Mac system while doing some light text editing work.
> Now, I cannot load the drivers or the system will hang. I attempted underclocking the RAM and core by replacing the BIOS, but I think the VRAM is bad.
> Even in VESA mode I have artifacts that seem to be caused by bad video RAM.
> I have lost my faith in Intel platforms. People advised me that I should go with a Pentium 4 / 775 system with i865 chipset for Windows 98 retro stuff, but I had nothing but problems with this Intel garbage. Same for other Intel based machines. Meanwhile, all my Socket 939 / AM2 machines are rock steady whenever I drag them out my basement. They POST very quickly, detect all attached drives, etc. Given that the AMD Vanilla hackintosh community is doing very good process, I think I will ditch Intel altogether in the foreseeable future.

Yeah that GTX 780 died because it was used and runs hot. Get a GT 710 or GT 730 if you want a fanless XP set up. As for your Hackintosh situation I can't help there if only certain graphics card work well for such a setup. If a GT 710 or GT 730 gets Hackintosh support then you are gold.
As for AMD go with a 990FX if you want the last best compatible for XP. You don't need a P4 for 98 retro stuff. I managed to get it working on Ivy Bridge which is way more powerful. Although Z370 could and does work but not recommended or easily done.

#4339

schreiberstein

⇗ @XPLives
Hey there!
I pulled the trigger and ordered myself one of these Chinese X99 motherboards (HUANANZHI X99-F8, Intel Xeon E5-2620 v3 (will probably upgrade later, ...) from AliExpress.
The reason why I did this is that all modern AMD ZEN based CPUs (Ryzen, Threadripper, ...) have a faulty implementation of the VME instruction set that make it unusable for NTVDM, Windows 98 DMA I/O among many other legacy things. It does not even work properly in a VM. This is true as of April 2020. Do not believe any false information that it had been "addressed". If you look into the forums, you see that it is still not working correctly. I am NOT getting myself into this mess, just because some RGB-tooting ga*mers drool over more FPS or faster 7zip results. Once these issues have been addressed, it will be worth consideration.
I did some experiments with an Intel Haswell Desktop motherboard I have (Intel DQ87PG, M-ATX, two PCI slots) with an i5.
Windows XP naturally ran without any of these annoying issues I encountered on Intel Z390.
In addition to that, the chipset still supports IDE-mode SATA, which had been completely removed from Skylake-era chipsets.
RLOEW Windows 9x AHCI driver works very well with that. You can leave AHCI enabled, but the driver depends on the IDE functionality being present in the chipset itself.
The "driver" will change some register values and switch back to IDE mode, while allowing to use up to 6 ports and DMA and seems to be more polished than just using IDE legacy mode from BIOS.
The system works quite well, so I figure it should be the same with an X99 based system.
Sadly, X99 seems to be a ticking time-bomb. Most motherboards die after a few years of use, from what I have read. Getting an X99 system is nearly as expensive as buying a new, much faster Ryzen or Intel Desktop system.
These Chinese motherboards seem to work reliable, are available at a low price and do not have any unnecessary gimmicks or marketing BS.
And they are FRESH. No 7 year old solder joints.
Since my desk is littered with KVM switches and cables, I will just use this machine to be my dedicated Windows machine.
I am considering REBELLION against all this modern stuff. I hate this constant change. I hate Mac OS Catalina for removing 32-Bit app support. I hate Windows updates and them breaking stuff.
There is NO REASON your app needs to be 300 MB large and consume 1 GB of memory when an older version just consumes 30 MB.
I hate these new PC cases, Aluminium sh*t, acrylic glass, LIGHTZZZ, PSU at the bottom (like the new gamerz in their bedroom gamez), no drive cages, ...
I also ordered an ATI FireGL V7100 (Basically a PCI-Express dual-DVI ATI Radeon X800 XT 256MB - also Dual-Link DVI support on (at least?) one of the ports) which is compatible with Windows 98 / ME, 2000, XP, ...
I might be getting an AMD Radeon HD 7950 or something similar for more modern systems and switch between the cards in UEFI BIOS, if it is possible.
You are right. The GeForce GTX 780 was not the best candidate for a long lasting desktop system.
Maybe I should have a look at a 730 or something.
I will keep you posted.
Cheers,
schreiberstein

#4340 | Zucker2k | ACPI issues. I did manage to install 32bit XP (haven't tried x64, yet). Anything ACPI crashes, so I settled on the i486 and with that option only one core is active in bios. Edit: With the kind help of @Infuscomus, of course.
#4341 | Mov AX, 0xDEAD | Hi guys After long winter/spring hibernation i back to do xp fun, now time for usb3+pae problem, i did tests with many vendors drivers and found ONE, that work at first sight, after couple of days i will public report
#4342 | infuscomus | ⇗ @Mov AX, 0xDEAD welcome back!
#4343 | ruthan | ⇗ @Mov AX, 0xDEAD Great, welcome back! My hardware is ready.. there are lots of enthusiastic testers, but we where short of developers in last months.
#4344 | Andalu | ⇗ @Mov AX, 0xDEAD nice to see you here again
#4345 | diderius6 | ⇗ @Mov AX, 0xDEAD Nice to see you again. I think, hibernation is not good for brain;)) Dietmar
#4346 | diderius6 | Few days ago I noticed, that Google does not translate a lot of websites now with the Firefox browser under XP SP3. There is a new browser basilisk for XP, which is based on last Firefox , can show HTML5 and translates websites correct Dietmar ⇗ https://o.rths.ml/basilisk/basilisk52-g4...d316c8-xpmod.7z

#4347

gordo999

> Zitat von ⇗ XPLives im Beitrag ¶ #4337

> 2000 Advanced Server already had > 4GB memory support.

⇗ @Pill Monster ...it was not true memory support as we would expect on a 64-bit system with 64 Gb RAM. They used the extended memory as a form of virtual memory. Rather than paging out RAM to disk, they were paging it into higher memory regions because the paging works faster in RAM than on disk.
PAE is a processor-based paging system. It does not enable more RAM for normal use, it has extended address features that can address addresses higher than 4 GB but for a pagefile system only. It's not possible to access RAM beyond 4GB using 32-bits. PAE has a very limited ability to store addresses beyond 4GB but it cannot address them directly by normal means.
PAE works with the memory manager to enable memory 'page swapping' to memory beyond 4GB. I don't know enough about this to agree or disagree with your point that the RAM beyond 4GB should have been made available to normal Windows users. I suspect that maybe you're right. I do know that RAM page swapping is required because 4GB is not enough for running an OS like XP with more than a trivial app like Notepad running. So, RAM pages get swapped (paged) to disk. With PAE, they get swapped to RAM beyond 4GB.
The question for me is how do you use PAE when it is enabled? You would need an app written to address it and another system module to run with the memory manager to use it. Server 2003 has that system module but as far as I know it is not available in a normal Windows OS. Maybe you could adapt it to run on a normal system, I don't know.
To be realistic, if you want to address 64 GB of RAM directly you need a 64-bit system. PAE relies on a 36 bit address capability and trickery.
This is similar to the old EMS/EMM memory managers with DOS. They found ways to swap memory out to external memory cards but those cards were never directly under DOS control. DOS could only address 640K RAM and with a bit of trickery, they managed to extend it to 1 MB.

#4348

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4341

> After long winter/spring hibernation

⇗ @Mov AX, 0xDEAD ...thanks for all your previous work and welcome back.
I saw your article on kernel debugging with XP using Net or USB. I have been trying with a serial connection via a USB to serial adapter (on a target with a B360 chipset with 2 serial ports), with the USB end at the W7 host. I've had it working well with W7 to W7 and W7 to W10 but so far, not with W7 to XP. Of course, it has currently stopped working altogether.
With Hyperterminal, I can send files both ways using the USB to serial adapter with XP as target but I have noticed recently that in windbg k-mode, the data goes to the target fine but gets corrupted from target to host. I am trying to get a good serial analyzer to find out why. The one I have is crippled.
When I first set this up, it did not work at all. Then I found a problem in the dual-booting system with W7 and W10. When I fixed it, k-mode debugging worked fine on both W7 and W10. I did not try it on XP at the time. Since I have upgraded W10 to 1909, it no longer works on W10 nor on W7. I was able to restart either W7 or W10 and have them break shortly after boot, then I could either trace or run the targets to the desktop. At the desktop, I was able to load and debug another app.

#4349

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4345

> Nice to see you again.

⇗ @diderius6 ...nice to see you too, and thanks for your previous work. Good to see ⇗ @infuscomus as well, although he has been around a bit more. Now if ⇗ @daniel_k would change his mind and come back,

#4350

Mov AX, 0xDEAD

Here tests of USB3.0 vendor's drivers in AIDA64 disk benchmark (linear reading test) on integrated USB3.0 Intel controler (H110/SUNRISEPOINT southbridge, DEV_ID=A12F):
4GB RAM Mode:
AMD 1.1.0.0145: works well
AMD 1.1.0.0276: not tested yet
ASMedia 1.16.58.1 (MCCI Based): looped LED activity on flashdrive, benchmark show no progress
Etron 0.119: hardcoded to max 16 enumerated ports, usb2.0 ports works, driver works well only after install, after reboot windows hangs on loading logo
Fresco Logic 3.6.9 (WDF based): works well, hardcoded to max 8 enumerated ports (intel controllers have 20+ ports, usb3.0 ports enumerated from 17+)
Intel 5.0.4.43 (Win7 backport): dont work, root hub is not enumerated
NEC/Renesas 2.1.39: dont response to inserted devices in ports
NEC/Renesas 3.0.23: not tested yet
Texas Instruments 1.16.3 (MCCI Based): hangs after some flashdrive activity
VIA 4.40 (WDF based): VIA HUB driver cannot start properly, hub driver hardcoded to max 16 enumerated ports
PAE/8GB RAM:
AMD 1.1.0.0145 dma64: works well (need amdxhci_adresscalc_fix)
AMD 1.1.0.0145 dma32: hangs after some flash drive activity + motherboard hangs when windows shutdowning (even hardware reset doesnt work after, motherboard instead do power cycle down-up)
Etron 0.119: not works, constant high load on cpu, windows get BSOD at shutdown
Fresco Logic 3.6.9.0 (WDF based): works well on some Intel controllers, on VIA not works properly

## Page 291

#4351 | infuscomus | ⇗ @Mov AX, 0xDEAD I've got daniel_k's AMD 1.1.0.276 if you want to test that too

#4352

Andalu

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4350

> PAE/8GB RAM:
> AMD 1.1.0.0145: hangs after some flash drive activity + motherboard hangs when windows shutdowning (even hardware reset doesnt work after, motherboard instead do power cycle down-up

Did you test with the 'amdxhc.sys' (SHA-1: 1AE2108E29A528EFDA7F7497952298A406991E21) from amdxhc_pae_fix.rar package and
the 'hal.dll' (SHA-1: 98026788984C5BA10644C0E451DD0D69A5F67A90) from the halplusintelppmXPSP3.rar package?
With these two files I no longer had similar issues ...at least for the moment
The Fresco Logic 3.6.9.0 driver does not install on my Q370 'real' system, not even via the 'have disk' option.
Can I try another way to install it?

#4353

diderius6

⇗ @Andalu
Can you please write a list with the SHA-1 numbers and the name of all files,
that you change from a normal XP SP3 install => XP SP3 with no limit of 4GB ram,
because I want to test real XP SP3 PAE also and I have a lot of motherboards
Dietmar

#4354

Andalu

⇗ @diderius6
Original files extracted from "en_windows_xp_professional_with_service_pack_3" iso:

    hal.dll		9146F89ECDC5F219A1F950D111330154FB508724
    halaacpi.dll	1F7BD1B7F695B84ABA47085619264CB28A27AE46
    halacpi.dll	43789EE6D9012AAF17B66C48D411A7D99778EF3E
    halapic.dll	FC8D17BE2612F9E0336BEB1B5B7E6BABBA225185
    halmacpi.dll	3CF2DD019633D45680B9CC93667143885D186828
    halmps.dll	72C7DA8F58886303BE9B17A5F9F472C741A11993
    ntkrnlmp.exe	6851C32E87B9992CF39C548554999DFA748B81C2
    ntkrnlpa.exe	0DB6A938A0224B5B69CDAF87ADC5AE4584538B13
    ntkrpamp.exe	508BAD3E4B6E1F2417D1639B8CDD3DF123FCB67E
    ntoskrnl.exe	CBB20AD29D7050282FE33A0D695C20C61C4CF533

Patched files with "/all" option (ntkrnlmp.exe and ntkrpamp.exe not yet renamed):

    hal.dll		020F03ED6B133765C879ADF248ED3D2D99109BD3
    halaacpi.dll	C7FBAF343C827E8A2F0BC9E30148F06697A3C86B
    halacpi.dll	AA6FC0C1AB163BCC55CC3CBAD368D3D6D3D9DC51
    halapic.dll	BA833399B2BBB51163AE702E7EC9D44F07F90589
    halmacpi.dll	BE202C78DBF4D59880AA6A9430BE05D4156D6764
    halmps.dll	30B791B03FBB67E0AC73E5B741DF950AEDF5CDF4
    ntkrnlmp.exe	1D17006333B45CF0A6C509977BEE0578DC36D5AB
    ntkrnlpa.exe	87ACB046620DDF80520F61B623BE793ED4414903
    ntkrpamp.exe	EFE2C3194AC3CF267E74B4942C42013C23CED2D6
    ntoskrnl.exe	D5A5D90ADE1D53150973742544EE39BC09C85BFD

Files renamed:

    ntoskrnl.exe	1D17006333B45CF0A6C509977BEE0578DC36D5AB
    ntkrnlpa.exe	EFE2C3194AC3CF267E74B4942C42013C23CED2D6

#4355 | diderius6 | ⇗ @Andalu Thanks a lot! Dietmar PS: By the way I will make small joke (idea from ⇗ @daniel_k ) to change disk.sys XP SP3 => Server2003 because via this way you can work with GPT disks.
#4356 | Andalu | ⇗ @diderius6 You're welcome I had already read about your intention for a new project, now I am pleased to see that it is starting

#4357

YuriyCN

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4350

> Here tests of USB3.0 vendor's drivers in AIDA64 disk benchmark (linear reading test) on integrated USB3.0 Intel controler (H110/SUNRISEPOINT southbridge, DEV_ID=A12F):
> PAE/8GB RAM:
> AMD 1.1.0.0145: hangs after some flash drive activity + motherboard hangs when windows shutdowning (even hardware reset doesnt work after, motherboard instead do power cycle down-up)

Driver "AMD 1.1.0.276" + РАЕfix in amdxhc.sys = all works fine on DEV_ID=A12F

#4358

Andalu

In my test on a board with an H110 chipset, in addition to the amdhxc.sys (SHA-1: 1AE2108E29A528EFDA7F7497952298A406991E21), it was also necessary to use the patched hal.dll as already happened for the other motherboards with 200 and 300 series chipsets that I have tried so far. Using the patched amdhxc.sys only, here's what happens if I run the chkdsk command for a removable disk drive:
⇗
So, in my case, I need to use both patched files to avoid the USB3 issues.

#4359 | mull | AMD USB 3.0 driver 1.1.0.145 can emulated CD-ROM on a USB flash drive install xp

#4360

Mov AX, 0xDEAD

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4357

> Driver "AMD 1.1.0.276" + РАЕfix in amdxhc.sys = all works fine on DEV_ID=A12F

> Zitat von ⇗ Andalu im Beitrag ¶ #4352

> Did you test with the 'amdxhc.sys' from amdxhc_pae_fix.rar package?
> With these two files I no longer had similar issues ...at least for the moment

amdxhc_pae_fix+hal_pae_fix not solve problem with amd driver, daniel_k many times told about it, controller still hangs. You can get this problem with 99% probablity running aida64 benchmark in special "no low mem" mode of windows. This test mode was made specialy to test software/drivers to work in pure PAE mode with 64 bit bus adressing (this mode require minimal 5Gb of installed RAM), amd failed this test :(
Description from DDK help:
The /nolowmem parameter loads the operating system, device drivers, and all applications into addresses above the 4 GB boundary, and directs Windows to allocate all memory pools at addresses above the 4 GB boundary.
just copy in boot.ini existing line and add at end :
xxxx="WinXP PAE NOLOW" /fastdetect /PAE /NOLOWMEM

#4361 | Andalu | ⇗ @Mov AX, 0xDEAD the USB controller hangs in "no low mem" mode here too. I was hoping to find myself in that 1%

#4362

Duke Solo

> Zitat von ⇗ gordo999 im Beitrag ¶ #4349

> > Zitat von ⇗ diderius6 im Beitrag ¶ #4345

> > Nice to see you again.

> @diderius6 ...nice to see you too, and thanks for your previous work. Good to see @infuscomus as well, although he has been around a bit more. Now if @daniel_k would change his mind and come back,

Regarding daniel_k, EULA requirements cannot apply to those who did not accept them. It's simple.
Just imagine, car manufacturers will forbid to disassemble them in your own garage :)

#4363

Andalu

⇗ @Mov AX, 0xDEAD
It took me a while, but I may have figured out what your intentions might be. If that's the case, it would be a great goal to achieve ;)
So, hoping to have effectively understood the meaning of your posts, below my tests with PAE/64GB RAM on a real Q370 machine in "no low mem" mode:
- AMD 1.1.0.0145: the usb controller hangs after some flash drive activity during and after the aida64 benchmark. XP hangs on shutdown.
- Fresco Logic 3.6.9.0 (FL1100 chipset): doesn't response to inserted devices in ports even if not in low mem mode. Explorer.exe hangs as well as the shutdown. So I didn't need to try the aida64 benchmark.
- Via 6.1.7600.5601 (VL805 chipset) (hardcoded to max 8 enumerated ports): works fine.
- NEC/Renesas 2.1.39 (0720201 chipset) (hardcoded to max 16 enumerated ports): works fine as for via card.
Here the screenshot for the Via card:
⇗
Let me know if I need to do any more tests to see if the PAE can work effectively without issues (and especially if I didn't understand anything ).

#4364

diderius6

I changed disk.sys and partmgr.sys from XP SP3 => Server2003 SP1 32 bit 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)
I can boot normal with those 2 changed files XP SP3 via MBR harddisk.
Always I take a look, that indeed those 2 files are loaded and not the old ones because of recovery of the XP SP3 5512 files.
But when I assign a letter with AOMEI to a 4 TB sata harddisk, formatted with GPT (via gparted 31),
on reboot the compi hangs
Dietmar
EDIT: It is not enough for to get GPT support in XP SP3 to change disk.sys and partmgr.sys.
By the way, partmgr.sys from WinServer2003 works only together with disk.sys from WinServer2003,
but both together can be used for XP SP3, but still no GPT support.

#4365

Mov AX, 0xDEAD

I found source of nonworking AMD usb3 driver in standart dma64 mode (no response to inserted devices in ports). This is fail of programmers, they made classic mistake with dropping HIGH part of 64 bit adresses.
they did this:

    xor ebx, ebx
    .....
    mov     ecx, [esi+458h] ; esi+458h = store of 64bit adress
    mov     eax, [esi+28h]
    mov     [eax], ecx ; low part
    mov     [eax+4], ebx ; dropped high part, zeroes.....

right code must be:

    mov     ecx, [esi+458h]
    mov     eax, [esi+28h]
    mov     [eax], ecx
    mov     ecx, [esi+45Ch] ; HIGH part of 64bit
    mov     [eax+4], ecx ; no more zeroes

After this fix driver(tested on 1.1.0.0145, 276 has same mistake) works in pae mode same like in nonpae mode, also pass "/nolowmem" mode.
Requirement: 1) hal_pae_fix 2) remove force_dma32 from driver, this "force" no more need. If you want keep dma32, driver still cant work properly in this mode under PAE
p.s. force_dma32 mean "and dl, 1=> and dl,0"

## Page 292

#4366 | diderius6 | ⇗ @Mov AX, 0xDEAD Waaoh, does this mean, from now I can use XP SP3 with RAM > 4GB without any restrictions? Can you please write a short list, which files I have to change for ACPI Multiprocessor on XP SP3 and ram>4gb, have a nice day Dietmar
#4367 | Mov AX, 0xDEAD | Andalu, thanks for report about of your hardware tests, i have only via card, but still cant start via or nec driver on intel hardware

#4368

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4366

> @Mov AX, 0xDEAD
> Can you please write a short list, which files I have to change for ACPI Multiprocessor on XP SP3 and ram>4gb

amdxhc.sys, new code will not fit old bytes, so you need find free space (at end on PAGE segment, extend it to 7e00 size)
change original bytes to "call my_patch nop nop....."
my_patch:

    Patch_DeviceContext proc near
    mov     eax, [esi+28h]
    mov     ecx, [esi+458h]
    mov     [eax], ecx
    mov     ecx, [esi+45Ch]
    mov     [eax+4], ecx
    retn
    Patch_DeviceContext endp

#4369 | Andalu | ⇗ @Mov AX, 0xDEAD what? You've already reached the goal? That's great!!!!! How to make this great finding easily accessible even for an ordinary mortal like me?

#4370

infuscomus

⇗ @Mov AX, 0xDEAD
is CFF Explorer an OK tool to extend the PAGE section? or is there a better solution?
in hexadecimal this patch would be?
look for

    8B 8E 58 04 00 00 8B 46 28 89 08

insert this on the end

    8B 8E 5C 04 00 00

so it's

    8B 8E 58 04 00 00 8B 46 28 89 08 8B 8E 5C 04 00 00

is this correct?

#4371 | ruthan | I wonder, isnt possible just create some *.exe utility which would check or target file crc is right and insert that HEX code inside? If it would be possible we can easily share and such patches and without any copyright violation. I know that rLoew patches worked this way.
#4372 | IntiMD | If you guys are wondering, daniel's finished moving his stuff to MDL (xp subsect)

#4373

Pill Monster

> Zitat von ⇗ XPLives im Beitrag ¶ #4337

> @Pill Monster
> 2000 Advanced Server already had > 4GB memory support. And standard XP Pro 32-Bit could utilize above the 4GB range for a Ramdrive so it wasn't completely neutered.
> But what is the model number of this supposed $2500 36-Bit Xeon?

Possibly you misunderstood me?
With

> Zitat

> "XP Pro 32-bit could utilize above the 4GB range"

- 4GB range of what?
Licensing caps aside, the maximum amount of RAM supported by XP is exactly equal to the maximum amount of RAM supported by the CPU, less hardware reserved.
XP Pro x86 officially supports 64GB of RAM.
RAM drives utilizing "hidden memory" I label snake oil because there are no hidden addresses that can be seen by RAM disk software but not the CPU.
RAM disks reside in something called a section object, the OS sees part of this section object - the WS partition. The CPU sees all of it and maps data in and out of the process view using pointers.
XP natively supports 36bit addressing using pae (Page Address Extension). Pae adds 4 bits to an address - two Page Table Directories and a PTD pointer.
Until SP2 enabled was the default boot mode. Hence why XP Pro x86 is not called XP Pro 32-bit.
PS the pm I sent you a few days ago was meant for another user.

> Zitat von ⇗ XPLives im Beitrag ¶ #4337

> But what is the model number of this supposed $2500 36-Bit Xeon?

I guess you had to be there.
⇗

#4374

infuscomus

> Zitat von ⇗ Pill Monster im Beitrag ¶ #4373

> XP Pro x86 officially supports 64GB of RAM.

^
source?
it's a 32-bit OS so it would've only ever officially supported 4GB of RAM

#4375 | diderius6 | Here is the link for all what you need for full USB3 on RAM > 4GB, thanks a lot for help Dietmar ⇗ https://forums.mydigitallife.net/threads...hardware.81607/ PS: I also think, that GPT on XP will work today just with small modification of my attempt.

#4376

Andalu

> Zitat von ⇗ diderius6 im Beitrag ¶ #4375

> Here is the link for all what you need for full USB3 on RAM > 4GB,
> thanks a lot for help
> Dietmar
> ⇗ https://forums.mydigitallife.net/threads...hardware.81607/

> Zitat von ⇗ diderius6 im Beitrag ¶ #4375

> PS: I also think, that GPT on XP will work today just with small modification of my attempt.

Another great goal achieved in such a short time???
That's great news!!!

#4377

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4370

> @Mov AX, 0xDEAD
> 8B 8E 58 04 00 00 8B 46 28 89 08 8B 8E 5C 04 00 00
> is this correct?

no, new code is bigger than old bytes

    open amdxhc.sys in any PE Editor
    look for PAGE segment
    it has virt_size=7DA2 raw_size=7E00, so we have 7E00-7DA2=5E free bytes in file ("in memory" size still 7DA2!)
    change virt_size to 7E00, now segment size "in memory" equal to size in file
    then look where ending original segment, virtual adress 39DA2
    so in virtual range 39DA2-39E00 you can store new proc Patch_DeviceContext
    in orginal code change 8B 8E 58 04 to call Patch_DeviceContext
    remain original bytes change to nops (90 90 ...)

#4378

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #4369

> @Mov AX, 0xDEAD
> How to make this great finding easily accessible even for an ordinary mortal like me?

learn ASM+IDA+PE Editors, DIY

#4379

Andalu

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4378

> learn ASM+IDA+PE Editors, DIY

there is the real possibility that I can take a lifetime to learn and above all the certainty that I will not live until a hundred years
However, I think I will start shortly

#4380

diderius6

I just succeed soso, to make a GPT harddisk work in XP SP3.
First, now I use the original very last versions of disk.sys and partmgr.sys from Server2003 (5.2.3790).
I notice, that a harddisk with GPT and 4 TB cant be given a device letter D in XP SP3.
Then I use a brandnew 2TB harddisk and format it with Gparted(vers 31) to GPT.
After struggeling with again crazy XP changes drivers back to original ones,
I rename in
C:\WINDOWS\system32\dllcache disk.sys => diskORI.sys
partmgr.sys => partmgrORI.sys
But even this is not enough, because the drivers are also in
C:\WINDOWS\Driver Cache
so I also rename whole folder
C:\WINDOWS\Driver Cache => C:\WINDOWS\DriverORI Cache
With AOMEI I can see now the 2 TB GPT disk. Now I can give via AOMEI this harddsik the letter D.
With cristalDiskmark5 I run a benchmark on this D:\ GPT disk, shows 201MB/sec.
And also in "Datenträgerverwaltung" in XP SP3 this GPT harddisk is now shown with letter D.
But the harddisk is still not shown as normal, I can only see C:\ , no D:\ there,
even I just run chkdsk on it, strange..
Dietmar
PS: I just see in registry, that only the name for Dosdevices is given for D:
but no Volume name.
Is here somebody, who knows how to give a Voulume name also for D: ?
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices]
"\\??\\Volume{2ad81ab8-86fd-11ea-b51b-806d6172696f}"=hex:4a,10,32,10,00,00,10,\
00,00,00,00,00
"\\DosDevices\\C:"=hex:4a,10,32,10,00,00,10,00,00,00,00,00
"\\DosDevices\\D:"=hex:44,4d,49,4f,3a,49,44,3a,80,cd,ad,f7,de,12,27,43,bb,74,\
90,10,9e,69,07,66
EDIT2: Yes, diskpart shows the same, no Volume for the GPT disk.
I just copy Moorhuhn:)) via comandline to GPT disk D:\ and this works.
EDIT3: With diskpart of win10 I found, that for some strange reasons the Volume on this GPT disk is marked as hidden.
But with diskpart of win10 I cant clear this attribute, diskpart gives message: Object wurde nicht gefunden, brr..
Now I am formatting this HD new with GPT under Geparted (vers 31).
⇗
⇗
diderius6 has attached files to this post

- ⇗ GPTforXPSP3.rar

## Page 293

#4381

Virgus

Hello everybody
I just found this post by reading Reboot.pro forums and I got really excited to the idea of having finally a "Resurrected XP edition"!
I'm not skilled enough unfortunately to dig into disassembly work but I'd like to contribute somehow.
In these years I collected some tweaks about extending RAM up to 128 Gb. I'm currently using the MOD to use 64Gb and I'm currently using it on my 8GB Laptop. I hope this zip might be useful for the project somehow (the original links might have been expired but I collected everything possible) !
I have a recent HP workstation and also a Dell i7 both with 32Gb and I'd love to be able to do some tests if you could point me to a summary of what's needed to install XP on one or both these machines. I'm not a pro like you, but I'm not a newbie either.
Cheers and thanks for the great news!
V.
Virgus has attached files to this post

- ⇗ Windows XP PAE Patches.zip

#4382

diderius6

Yessssssaaaa, I got it
GPT support under XP SP3.
Until now only for harddisks <= 2TB, but who knows:))..
Crazy, with win10 it was not possible to get rid of the hidden mark for the Volume.
So I format whole disk new with Gparted (version31),
chose as partitionstable GPT and NTFS as filessystem, nothing more(!).
And voila, now everything is ok
Dietmar
⇗

#4383 | ruthan | Paragon GPT loader - not free support bigger disk than 2TB, im using 4TB ones, so its breakable.

#4384

diderius6

⇗ @ruthan
Yes, I know, I have.
But because now, no other files are used, you can do boot from this GPT harddisk without any UEFI.
In next days I try the S4e method, for to have an XP SP3 bootet and running from a GPT disk
Dietmar
PS: May be for S4e it is just enough, to fake the SIGNATURE in the first 512 Byte of the GPT disk, hihi..
EDIT: From Wikipedia
In operating systems that support GPT-based boot through BIOS services rather than EFI, the first sector may also still be used to store the first stage of the bootloader code, but modified to recognize GPT partitions.

#4385

gordo999

Something I am missing here with the excitement about PAE. From the Intel manual:
"Physical Address Extension. Physical addresses greater than 32 bits are supported: extended page table entry formats, an extra level in the page translation tables is defined, 2-MByte pages are supported instead of 4 Mbyte pages if PAE bit is 1".
I think there is a typo here, I think they mean 4 Kbyte pages, not 4 Mbyte pages. Standard memory pages are 4Kbytes.
Normally the memory manager swaps memory pages of 4K from physical memory to the swap file on disk. With PAE, they have increased that page file size to 2MB. One problem... the memory manager is run by the Windows operating system not the processor, where PAE is enabled or disabled. In other words, it is ntoskrnl in XP that controls the memory manager. If it is written to use 4k pages in memory, how are you going to enable the 2MB pages made available by PAE without having a driver to work in conjunction with the memory manager? And how are you going to tell the XP memory manager to use RAM above 4GB.
User apps don't know anything about this page file swapping and it's not clear to me if the XP ntoskrnl knows anything about swapping pages to the RAM above 4GB in 2MG pages. As I understand it, W2003 32-bit does it using extra drivers supplied by Microsoft that enhance the ability of the memory manager. How is the extra memory going to be used? How is it going to be accessed?
Maybe there's something I am missing.

#4386

diderius6

I just test the PAE for XP SP3.
Thank you soso much to ⇗ @Mov AX, 0xDEAD and ⇗ @daniel_k :))!!
All works, USB3, USB2, on Asmedia, all Intel, USB mouse, as you can see on photo.
Until now no BSOD, no strange behavior.
I use the patched amdxhci.sys vers. 1.1.0.145.
This is the Intel board Asrock z370 fatality k6 with 32 GB ram, all avaible now in XP SP3.
And still the GPT harddisk is there;).
This XP SP3 boots via nvme from the Intel Optane 905P.
This is unbelievable fast, for example editing photos or Mathematica. Much faster than win10.
The Intel Optane 905P nvme device needs no trim at all. It is just a better device than any other SSD (but expensive).
With the WinXPPAE patch I patch original halmacpi.dll ver. 5512 and the ntkrpamp.exe version 5.1.2600.7581 .
Dietmar
PS: I try a small joke: I have an hacked ntldr with no 512 MB limit for ram boot of XP SP3 via ewf.
I am really courious, if this will run with a lot of RAM :)) now.
⇗

#4387 | Andalu | ⇗ @diderius6 Have you already tried the aida64 linear benchmarking in /lowmem mode?

#4388

diderius6

⇗ @Andalu
Until now not.
Is this possible with the free aida64 version,
have a nice day
Dietmar
EDIT: I am just running the test with linear reading from Intel USB3. All seems ok, benchmark is now running 12 min there.
But I noticed the first not good effect: When you plug in any USB device, it is recogniced at once.
But when you plug, unplug, plug, unplug, .. suddently the device on the Intel USB is not recogniced any longer.
This does not happen with the Asmedia driver 1.16.55.1 on the Asmedia USB3 ports
Dietmar
⇗

#4389

Andalu

⇗ @diderius6
I asked you because the same happens here with new amd drivers on plug, unplug, plug etc.
EDIT:
It just happened again, this time already during the first 'plugging' operation, on the sixth removable drive connected.
Both "my computer" and "computer management" hang. The system needs to be manually restarted.
I'm using the hal.dll from the hal_pae_fix package (SHA-1: 8CBEC120FEB93D855AB1ED6FAD9A8D8223CC0E9A)

#4390

diderius6

I switched off the power save function in the USB hubs.
Now the behavior is a little bit other:
One and the same USB stick now you can put in every USB slot plug, unplug.. as often as you want,
is always recogniced.
But when you use after this another USB stick, it is not recogniced and also then the first stick not.
So, may be it depends on the sleeping functions of XP. Because with time, it last from at once to about 5 sec,
until the stick is recogniced
Dietmar
PS: A BSOD I do not notice. And no crash when shut down. Only in the case of not recogniced USB stick "unknown device" is shown under USB in Device Manager.
EDIT: The same error for the amdxhci 145 driver happens also in non PAE mode (Ram <=4GB), means without the patched ntoskrnl.exe and hal.dll.
EDIT2: The amdxhci 276 vers. shows exact the same behavior as the 145.

#4391

Mov AX, 0xDEAD

¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Compilation of my previous post/reports/patches in ONE place, also included community patches/solutions (excluding AMD-related)
p.s. forum's html styles are bad, so probably you need override setting with Stylish/Stylus, this is my example, code and spoiler sections no more limited to fixed width:

    td.sidebar {
        width: 160px !important;
    }
    .hpm_spoiler {
        width: auto !important;
    }
    pre {
        width: auto !important;
    }
    .codelines {
        margin: 0px !important;
    }
    .bbcode_code,
    .codeblock {
        padding: 0px !important;
    }

#4392

Andalu

I have tried one more time my Via pciex to usb3 card (VL805 chipset - 4 usb3 ports - driver 6.1.7600.5601) in /lowmem mode, PAE /64GB and aida64 linear reading test:
all worked correctly even if I plugged, unplugged, plugged, unplugged etc. up to 6 removable devices for many times during the benchmarking which lasts just over 7 minutes.
Unfortunately, I got the error code 10 - "this device cannot start" when I tried to install the via driver also for the usb hub although the xhci driver installs correctly for the intel usb3 controller (DEV_ID: A36D)

#4393

diderius6

The ewf.sys filterdriver does not like PAE mode^^.
When I do USB-boot of full XPSP3 from a write protected USB3 stick (works only for FAT32 :))),
it asks, wether the original files are used and to put in the XP installations CD.
I cancel this question. Ram is shown <4GB even with the PAE files
and ewfmgr C: shows with the hacked ntldr, that in normal mode you can use 683 MB for the RAM-overlay,
and in safe mode 750 MB,
Dietmar

#4394

gordo999

Interesting article on PAE, DEP. and AWE. When PAE is enabled, DEP is automatically enabled. That COULD be a problem since DEP disables writing to a certain portion of memory. AWE is the feature used in server 2003 to page memory into extended memory beyond 4 GB.
DEP can be disabled using the /EXECUTE switch in boot.ini.
⇗ https://docs.microsoft.com/en-us/windows...dress-extension
Apparently Microsoft allowed access to memory > 4GB in XP SP1 but discontinued it because it messed up certain drivers, like on some games. If it was enabled, then maybe studying the SP1 ntoskrnl might reveal how to enable it again. If the idea is to emulate the server 2003 x86 access to RAM > 4GB, maybe studying the AWE feature might reveal how it's done.
A good article by Mark Russinovich on Windows memory in general, including virtual memory. Please note that the source is wayback machine and as you click on each link you need to wait while wayback transfers to another region. It gives a 302 error but below that error it shows that it is redirecting.
⇗ https://web.archive.org/web/201201010945...21/3092070.aspx

#4395 | Mov AX, 0xDEAD | Fresco USB3 v3.6.9 driver on VIA Controller don't work properly: 1) programmers made searching xECP structs with bug (patch: 0x22ad2 F4->EC), all usb3 ports was not enumerated 2) even after proper enumeration, driver make constant pauses at transfer, speed down to zero

## Page 294

#4396

diderius6

⇗ @Mov AX, 0xDEAD
Today I make a test with the 145 amdxhci USB3 driver.
I will set in Registry and in their *.inf file Loadordergroup=System Reserved and start=0,
also for usbstor.sys and the amd hub.
Another try is, to make use of the original intelppm.sys for to clearify, if the problem is really the sleepingstate of USB for this driver
Dietmar

#4397 | Andalu | ⇗ @diderius6 in my tests I have always used the original intelppm.sys

#4398

diderius6

To set Group=System Reserved and start=0 does not help for the amdxhci USB3 driver.
I noticed, that there is no Energy Save switch for the AMD USB 3.0 Root Hub,
only in all the other Hub
Dietmar
PS: Long time ago I found in the registry of XP SP3 a switch, where you can disable or enable any Energy Save for any device.
But until now I do not find it again.
EDIT: I found the switch and I put here content of the *.reg file for to reach this. But it does also not help.
Microsoft describes exact this problem for USB devices, when they are connected, disconnected and connected again, exact
as this happens with the amdxhci driver.
⇗ https://support.microsoft.com/en-us/help/817900
This problem occurs because of a race condition in the Selective Suspend feature of the USB hub driver. The Selective Suspend feature is designed to suspend the USB hub to efficiently maintain battery power. However, the Selective Suspend feature sometimes may not correctly wake up the USB hub.
EDIT2: "Save remove" of the USB device also not helps. Uninstalling of the USB driver not helps, Hub2 and HUB30 are shown as unknown devices after new install.
EDIT3: With my settings now, I can change about 20 times all different USB devices before "not recognice" starts.
May be, only BIOS mod can help, as we have done before, do get rid off loong Integers for USB3 device for sleepingstates.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\USB]
"DisableSelectiveSuspend"=dword:00000001

#4399 | Andalu | ⇗ @diderius6 even adding that setting, not much has changed here. The issue has already occured on the seventh removable drive connected: ⇗ "My computer" and "computer management" are completely blocked. Even the "device manager" does not correctly display the devices which are no longer powered.

#4400

diderius6

⇗ @Andalu
This problem stays also for me, only crash I dont have.
But the sleeping states of the USB hub are the reason for this behavior.
Next I try the z390 dark board. In its Bios, there is the Intel xhci device not mentioned.
And this will give a hint, if modding Bios can help
Dietmar
EDIT: The behavior on the Z390 EVGA dark board is exact the same. I check, that I have flashed the 0.92 version of the Bios.
Because only in Bios vers 0.92 is the xhci Intel USB device not mentioned in Bios.
So, the not awake of the USB hubs depends not on the xhci entry in BIOS.
On the z390 dark board with my settings I also can change about 20 times any USB device, before recognizing stops.
At once, when recognizing has stopped, the USB mouse does not work any longer and also the USB stick not.
On the z390 Dark board I can deinstall and install the amdxhci driver new on running XP SP3 after norecognice happend and then again all USB works,
is recogniced about 20 times.

#4401

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #4400

> @Andalu
> On the z390 Dark board I can deinstall and install the amdxhci driver new on running XP SP3 after norecognice happend and then again all USB works,
> is recogniced about 20 times.

I am using this USB3 driver. On my H110 motherboard, this driver works without BSOD crashes,
without any problems with PAE mode (16 GB RAM).
⇗ https://www.upload.ee/files/11579304/USB...PAEfix.zip.html

> Zitat von ⇗ Andalu im Beitrag ¶ #4397

> @diderius6
> in my tests I have always used the original intelppm.sys

When using a patched intelppm.sys, I get an increase of CPU performance up to +2..3%;
and +10...15% in increase of "Intel RSTe AHCI/RAID driver v4.7.0.1117".
As well as the use of patched hal.dll gives + 30% increase in "Intel RSTe AHCI/RAID driver v4.7.0.1117" performance,
but does not affect the CPU. More details - ⇗ What exactly is the hal timer problem? (3)

#4402

Andalu

⇗ @diderius6
here I don't get always the same behavior, I went from one!! to max 16 times before recognizing stops.
I've seen that my system doesn't like a particular usb3 flash drive: when inserted into a USB2 port it is not recognized and identified as unknow device.
When connected to a usb3 port it is recognized without any problems.
Installing a different amd usb3 driver version on running XP after norecognize happened doesn't help.
Here a screenshot, I never seen that icon for a flash drive :)
⇗

#4403 | diderius6 | ⇗ @Andalu This may have another reason. This behavior I have seen from an USB device, who needs too much current. This symbol I have never seen, looks like somebody put something on a screen;)) Dietmar

#4404

Andalu

> Zitat von ⇗ YuriyCN im Beitrag ¶ #4401

> I am using this USB3 driver. On my H110 motherboard, this driver works without BSOD crashes,
> without any problems with PAE mode (16 GB RAM)

even for me that driver worked without problems, however, according to Mov AX, 0xDEAD ¶ here, you should check the PAE >4GB in /lowmem mode while performing the linear test with aida64. In my case, I was able to verify that the USB controller stops working so I was not within the 1% chance of the block not happening

#4405 | Andalu | ⇗ @diderius6 the problem is that I didn't touch anything, that icon suddenly appeared I'm using the Q370 board only for tests. Only three programs installed. It doesn't even have an internet connection. Another similar flash drive that comes from the same packet, doesn't have the same issue

#4406

diderius6

⇗ @Andalu
Hihi, it is a Windows setup Icon.
Published on September 13th 2016 by Yakov .P.
Released under the Release to Public Domain license.
Icon for Windows XP, Vista and 7.
Dietmar

#4407 | Andalu | ⇗ @diderius6 never seen before, my system went crazy after too many usb recognitions

#4408

Mov AX, 0xDEAD

I continue to torment usb3 drivers, now i try backport integrated Windows 8 drivers (after imports fixes), these drivers require
WDF 1.11, this version wasn't released for Windows XP/2003(???), so need imports fix too, last ported version is 1.11.9200
Win8 Beta M1 - works in VMWare, on real hardware need disable check `MaxScratchpadBuffers==0 (jz .text:00016C1B => jmp)`
on Intel controller driver&hub start, no recognition to any inserted devices
on VIA controller driver&hub start, integrated usb2 hub recognized as UNKNOW DEVICE (0000,0000), no recognition to any inserted devices
Win8 Beta M2 - on real hardware driver recognizes inserted devices only on usb2 ports, devices in usb3 ports started with error code 10, in aida benchmark any flash storages hangs
Win8.0 - works on Intel & VIA hardware, PAE also works
Win8.1 - ...

#4409

diderius6

⇗ @Mov AX, 0xDEAD
Nice idea to try with Win8, Win8 backport works also for the STORAHCI driver. Problem there is WDF.
Another way would be, to find out, why after several connect<>disconnect the amdxhci USB3 driver stops working.
Because this does not happen with the H110 board (Skylake), it seems to depend on the kind of the Intel USB controller in the Coffee Lake chipsets (z370, z390)
Dietmar
Why did Intel release two Windows * 7 USB 3.0 eXtensible Host Controller (xHCI) drivers?
There are two different Intel® chipset platforms available for Windows 7. Each platform has its own USB 3.0 xHCI driver:
Intel® 7 Series / C216 Chipset Family
Intel® 8 Series / C220 Chipset Family / 4th Generation Intel Intel® Core Processor U-Series Platform I / O
EDIT: Maybe, it is possible to backport DriverVer=05/11/2017, 5.0.4.43 from Intel. This is a NEW version (V2) of the 5.0.4.43 Intel USB3 driver for Win7 32 bit.
I just see, that you test it for the H110 (Skylake) board. But maybe it works for coffeelake /kabylake.
"Intel 5.0.4.43 (Win7 backport): dont work, root hub is not enumerated"

#4410 | Andalu | I'm aware that I'm talking about a different kind of power supply connection, but with my VIA PCIEX to USB3 card I didn't have no issue in "no low mem" mode and PAE >4GB while at the same time the aida linear test was in progress. If there was a way to install this driver also for the intel controller :)

## Page 295

#4411

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4409

> I just see, that you test it for the H110 (Skylake) board. But maybe it works for coffeelake /kabylake.
> "Intel 5.0.4.43 (Win7 backport): dont work, root hub is not enumerated"

backported driver works in win8 on h110, also works in vmware winxp, so there is complex incompatibility, same code on real winxp hardware works diferent.
intel driver is BIG driver, 820kB vs etron 75kB, but it is our last hope

#4412

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #4410

> VIA PCIEX to USB3 card I didn't have no issue in "no low mem" mode and PAE >4GB while at the same time the aida linear test was in progress. If there was a way to install this driver also for the intel controller :)

VIA driver always works in PAE, even in vmware, but with intel hardware it has some trigger, hub driver get external command to unload. i still do not found who and when set this command
p.s. on my system driver has two problems:
- several seconds after booting no devices recognized, further no problems
- Sagem adsl modem cannot works properly in bulk usb mode

#4413

Andalu

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4412

> p.s. on my system driver has two problems:
> - several seconds after booting no devices recognized, further no problems
> - Sagem adsl modem cannot works properly in bulk usb mode

Just tried, no problems both when the 4 usb removable drives are already plugged during the booting and when connected after XP booting.
What is your adsl modem issue?

#4414

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #4413

> What is your adsl modem issue?

USB ADSL Modem has software switch to work in ISO or Bulk mode, in Bulk mode it loss connection after some time, in ISO no loss.
But ISO mode is slow and considerably eats cpu, this mode intended for mouse/keyboards with rare events, for mass tranfers bulk mode is preffered. In same time flash storages always works in bulk mode and haven't problem on VIA hardware/driver.
On intel hardware/driver same modem works in bulk mode prefectly.

#4415 | Andalu | ⇗ @Mov AX, 0xDEAD So, the best way out is to find a driver for the intel controller :) Can it be a power management issue? P.S: the usb adsl modem that i could try is an old model, no bulk or ISO mode, only a low quality connection :(
#4416 | infuscomus | ⇗ @Mov AX, 0xDEAD there is a symbols file for the texas instruments USB 3 driver - could that be of use to make a good USB 3 driver?

#4417

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4416

> there is a symbols file for the texas instruments USB 3 driver - could that be of use to make a good USB 3 driver?

.pdb helps only with reversing
to make good driver someone need write it in C language from scratch or port leaked win8/10 driver (sources are not full)

#4418 | reactosuser7 | This could be useful to test as an experiment to ReactOS (if you don't know about it is an Open Source Windows XP/Server 2003, still under development) . Thanks so much for this post!

#4419

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4409

> Intel® 8 Series / C220 Chipset Family / 4th Generation Intel Intel® Core Processor U-Series Platform I / O

@diderius ...you have to be careful with the Intel description. For example, they talk about both the 8th generation processor and the 300-series chipset. The 300-series chipset will work with the 8th gen processor but not all 300-series chipsets work with the drivers for the the 300-series.
For example, my B360 chipset is not listed on the 300-series list of compatible chipsets and it does not work natively with the driver. In fact, the installer rejects my chipset. I had to reverse the setup file to get it to load, only to get a code 10 error.
It was daniel_k's AMD driver that finally worked on my B360 chipset. I have all mobo ports working as well as VIA add-on card using XP drivers for the VIA card I found on the Net.

#4420 | YuriyCN | I noticed that the clock on my computer is not very accurate. In 1 day, time goes forward by almost 57-58 seconds!! The computer is turned on for about 12-14 hours a day. Could this problem be caused by the intelppm.sys (fix timer) or is it a bad quartz resonator on the motherboard (BIOS)?
#4421 | Mov AX, 0xDEAD | ¶ updated info about USB3 Win8 Beta M2 driver

#4422

Pill Monster

> Zitat von ⇗ gordo999 im Beitrag ¶ #4347

> > Zitat von ⇗ XPLives im Beitrag ¶ #4337

> > 2000 Advanced Server already had > 4GB memory support.

> @Pill Monster ...it was not true memory support as we would expect on a 64-bit system with 64 Gb RAM. They used the extended memory as a form of virtual memory. Rather than paging out RAM to disk, they were paging it into higher memory regions because the paging works faster in RAM than on disk.
> PAE is a processor-based paging system. It does not enable more RAM for normal use, it has extended address features that can address addresses higher than 4 GB but for a pagefile system only. It's not possible to access RAM beyond 4GB using 32-bits. PAE has a very limited ability to store addresses beyond 4GB but it cannot address them directly by normal means.
> PAE works with the memory manager to enable memory 'page swapping' to memory beyond 4GB. I don't know enough about this to agree or disagree with your point that the RAM beyond 4GB should have been made available to normal Windows users. I suspect that maybe you're right. I do know that RAM page swapping is required because 4GB is not enough for running an OS like XP with more than a trivial app like Notepad running. So, RAM pages get swapped (paged) to disk. With PAE, they get swapped to RAM beyond 4GB.
> The question for me is how do you use PAE when it is enabled? You would need an app written to address it and another system module to run with the memory manager to use it. Server 2003 has that system module but as far as I know it is not available in a normal Windows OS. Maybe you could adapt it to run on a normal system, I don't know.
> To be realistic, if you want to address 64 GB of RAM directly you need a 64-bit system. PAE relies on a 36 bit address capability and trickery.
> This is similar to the old EMS/EMM memory managers with DOS. They found ways to swap memory out to external memory cards but those cards were never directly under DOS control. DOS could only address 640K RAM and with a bit of trickery, they managed to extend it to 1 MB.

Page file or swapping does not allow access to over 4GB RAM. I will respond in more detail in some time..
To access 64GB of RAM requires an x64 processor. PAE according to Intel is a CPU with more than 32bits data bus, (so 36bit in practical terms). Xeon had 36, but Atlon64 had 40 address and 40 data.
⇗ @gordo999 I think you accidentally misquoted me - I did not say Advanced server had >4Gb Memory support that was XP Lives who said that...:)
Anyway >4GB doesn't imply 64bit as you suggest. It could mean 36 bit or 40bit or 48bit.

#4423

gordo999

> Zitat von ⇗ Pill Monster im Beitrag ¶ #4422

> Page file or swapping does not allow access to over 4GB RAM. I will respond in more detail in some time.....

⇗ @Pill Monster ...That's what I am trying to say. Normal page swapping with the XP memory manager is done using 4K pages and it is done to disk. It is a pure 32-bit system. PAE allows the size of the page files to increase in size by increasing the memory addressing space by 4-bits, to 36 bits. However, the normal x86 XP memory manager is not designed to work with PAE to access RAM > 4GB directly.
To use memory beyond 4GB meaningfully, you need extra drivers that work in conjunction with the memory manager, a system called AWE (Advanced Windowing Extensions). Another name often used for PAE (Physical Address Extension) is Page Address Extension. I think that's a better description of what PAE does, it increases the page size available to the memory manager and allows the pages to be stored in the extra RAM beyond 4GB. However, if an app is not written to use such features, I don't see how PAE alone will allow access to extra RAM on a normal 32-bit system.
How the system uses PAE to access RAM > 4GB is not clear to me. It appears you can use PAE to install a RAM disk but, as I understand it, a Ramdisk requires separate software/drivers to run it. Here's a link to people discussing this problem and one mentions what I suggested about the old DOS systems that software is required to 'trick' apps into thinking they had more memory. The EMM memory manager did it using a small area of DOS RAM to map memory to an external memory card.
⇗ https://superuser.com/questions/292207/i...sing-windows-xp
"Exceeding the 4GB cap is harder. It requires playing addressing tricks of the sort that used to be required in the days of 16bit systems. I have heard tales that it's possible to break this barrier in 32bit XP, but it requires much more than a simple registry edit. IIRC, the limit is compiled into the operating system directly. To get around it, you have to find a specific .dll file from a 32bit Server 2003 machine and use it to replace the equivalent file on your Windows XP machine. For this to work, the file has to be modified so that XP won't reject it and you have to use volume shadow copy to get it to replace the existing file. I don't remember and can't find the link now for which file you need or how to modify it. After this is accomplished, you should be able to make the same settings to 32bit XP that you can to Server 2003 to allow the higher memory cap. Of course, such a change is highly unsupported and violates your license agreement".

#4424 | ruthan | What about games compatibility, are all XP games running on Windows 2003, some just report that its not XP and refuse to install / start? Also XP still has some XP support, what about Win2003?
#4425 | Gelip | I tested WinXP SP2 x86 on a real computer - Thin Client Igel 4210 (VIA C7 CPU, AWARD 6.00PG BIOS) using UEFI32 emulator DUET and it works in UEFI + CSM: PC is old but bios UEFI32 is modern

## Page 296

#4426

diderius6

⇗ @Gelip
Waaooh, this is really cool:))!! Please describe step by step,
which files you used and the preparing of everything.
What about Graphik card and 3D?
Also very interesting, if nvme boot via the UEFI Bios files is now possible,
for a compi, which never heard anything about nvme before in its life;)
Dietmar
PS: Is there a special reason, why you use XP SP2?
Can you disable CSM in Bios for this kind of UEFI boot of XP?

#4427

Gelip

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #4426

> Waaooh, this is really cool:))!! Please describe step by step,
> which files you used and the preparing of everything.

As for the UEFI32 emulator, you have to compile it from sources - I used these: ⇗ vector-edk
How to build and what you need is described inside: ⇗ ReadMe.txt - you need Visual Studio 2005 and WinDDK 3790.1830
You can prepare a DUET pendrive with ⇗ CreateBootDisk.bat or with this installer: ⇗ Tianocore Uefi Duet Installer
When it comes to preparing WinXP x86 you need the files winload.efi and bootmgfw.efi from the test version of Vista Beta Longhorn 6.0.5219.0
To WINDOWS\system32 you copy winload.efi and to FAT32 pendrive file bootmgfw.efi (I changed the name to WinXP.efi ) and to the root directory of the pendrive the boot.ini file by adding the /usenewloader option.
Now just boot your compi from this pendrive - that's all

> Zitat von ⇗ diderius6 im Beitrag ¶ #4426

> What about Graphik card and 3D?

Igel has a VIA UniChrome S3 card integrated and after the driver installation 3D works.
I don't have a motherboard with legacy or UEFI 32-bit bios with a PCIe connector so I don't know but with WinXP x64 I tested AMD Radeon HD6450 and HD7450 so it will probably work with WinXP x86 as well.
P.S. I will be testing WinXP x86 with the UEFI32 DUET emulator on ThinkPad X61, IdeaPad S10e and Igel with old PCI S3 Trio, Virge and Matrox cards

> Zitat von ⇗ diderius6 im Beitrag ¶ #4426

> Also very interesting, if nvme boot via the UEFI Bios files is now possible,
> for a compi, which never heard anything about nvme before in its life;)

I think that there should be no problem if there are WinXP drivers. I recently bought a mSATA drive for the ThinkPad X220 and it works without problems in WinXP SP2 x64: ⇗ mSATA test on X220

> Zitat von ⇗ diderius6 im Beitrag ¶ #4426

> PS: Is there a special reason, why you use XP SP2?

In SP3 I do not like the service of network connections - it works differently than in SP2.

> Zitat von ⇗ diderius6 im Beitrag ¶ #4426

> Can you disable CSM in Bios for this kind of UEFI boot of XP?

No, UEFI32 or UEFI64 emulator does not work on computers with UEFI bios. Works only on legacy bios computers. In the video there is a test with Igel 4210 which has bios AWARD 6.00PG. The DUET emulator also works in the Qemu virtual machine - on this video tested DUET UEFI64:
In VirtualBox, VMware and MS VPC not work.

#4428

Mov AX, 0xDEAD

> Zitat von ⇗ gordo999 im Beitrag ¶ #4423

> However, the normal x86 XP memory manager is not designed to work with PAE to access RAM > 4GB directly

- winxp has pae kernel, only in this kernel available physical memory above 4gb, pae kernel can map > 4GB directly
- when progs allocating more memory, manager through pae choose it from any physical place (0-36GB), then map this physical piece to prog's local adress space (old dos EMM trick, in emm window size was fixed 64K, in ZX Spectrum 128 window was 16 kb)
- one process can't allocate more 2Gb of ram (3Gb if /3gb switch enabled), kernel limited to 2Gb (1Gb if /3gb switch enabled)
- AWE is software API same as EMM INTxx, applications can have many "windows" at same adress in local adress space and fast switch between
- 3rd RAM Disk software "we can access above 4gb!" is not magic, they also uses windows and switch from one to other when file stored in different window

#4429

Levvon

More than 4 years ago I already posted this information on the Ru-Board.com Forum, but it turned out to be unclaimed.
Loading Windows XP from GPT disks and accessing space beyond 2.2 TB are possible.
The only limitation is that the system and boot partitions must be entirely within the first 2.2 TB.
Method #1 (unreliable due to errors in the Paragon drivers)
It consists in creating HybridMBR using gdisk (GPT fdisk) and using the driver 'gpt_loader.sys' (Paragon GPT Loader).
HybridMBR is created using gdisk (GPT fdisk) in a special way, so that the BIOS or UEFI of the computer interprets hybrid disk partitioning as MBR and the loaded operating system already as GPT, thanks to the gpt_loader.sys driver (Paragon GPT Loader). For 32-bit driver version 8.0.1.0 there are patches [@hardwarefetish.com] that fix BSOD and high RAM consumption but do not fix file system corruption problems. Driver versions newer than 9.0.5.x are not suitable because they report that "This driver version doesn't support hybrid disk partitioning". Drivers can be extracted from the installers of Paragon GPT Disk Manager or Paragon HFS + for Windows.
Instructions for creating a HybridMBR:

- of the 3 available partitions (the 4th slot is used for protective partition) in HybridMBR it is enough to specify only the system and boot partitions;
- it is not necessary to specify the remaining partitions in HybridMBR because Paragon GPT Loader driver will subsequently provide access to them;
- DO NOT accept the offer of the utility to place a protective partition with the identifier 0xEE in the first slot created by HybridMBR;
- DO NOT allow the utility to mark the remaining space with another additional protective partition with the identifier 0xEE.

Method #2 (reliable, meets the UEFI Specification)
It consists in using a special ProtectiveMBR from the SYSLINUX v4.x+ distribution which converts GPT to NormalMBR on-the-fly in the RAM.
Like Method #1 these actions are performed directly on a loaded Windows XP operating system.

- for Windows XP SP3 (32-bit) disable Windows File Protection and in the 'system32\dllcache' and 'system32\drivers' folders replace the 'disk.sys' and 'partmgr.sys' files with similar files from Windows Server 2003 SP2 (32-bit) with GPT support;
- create HybridMBR as described in Method #1 but additionally assign the Legacy BIOS Bootable attribute to the system partition GPT which corresponds to the active partition in HybridMBR;
- on top of the newly created HybridMBR create a NEW HybridMBR with ONLY ONE protective partition with the identifier 0xEE exactly on active bootable partition space (in this case, HybridMBR will be a true ProtectiveMBR);
- from the distribution of SYSLINUX v4.x and newer execute the command 'syslinux.exe -m -f C: gptmbr.bin', where 'C:' is the letter of any partition on the target disk.

Proof Video:
vimple.co/8614e295604f4cfd9b0045f6422619d9
Reproduction Kit:
upload.ee/files/11625492/WinXP_GPT.zip.html

#4430

ruthan

Thanks, its nice source of info.
But Syslinux is much less used by Linux distros than Grub + change whole disk partition tables, means re-installation of others OSes or some migration etc. It looks problematic, time consuming etc, unless someone will create some conversion tool and even than, it would probably generate problems with standard partitioning tools.
So best scenario is probably keep XP only disk with 1 partition and in that case you still can keep it legacy, until we will get UEFI only bioses, or is there any other advantage to migrate it to EFI bootable HDD?
For me personally XP GPT main advantage would be in possibility add XP parition to GPT disk with lots of others GPT partitions without any special partitioning to get rid of special XP or MBR disks.. and boot every OS from one NVME drive..

#4431

Levvon

> Zitat von ⇗ ruthan im Beitrag ¶ #4430

> But Syslinux is much less used by Linux distros than Grub + change whole disk partition tables, means re-installation of others OSes or some migration etc. It looks problematic, time consuming etc, unless someone will create some conversion tool and even than, it would probably generate problems with standard partitioning tools.

Method #2 is as simple as possible and does not require the installation of third-party bootloaders, including SYSLINUX. The method only uses the ProtectiveMBR from the SYSLINUX distribution. The code of this ProtectiveMBR turns the GPT-table into NormalMBR-table on-the-fly in the RAM and does not affect the real MBR on the disk. You can use any relevant tool for installing ProtectiveMBR, not necessarily 'syslinux.exe'.

> Zitat von ⇗ ruthan im Beitrag ¶ #4430

> For me personally XP GPT main advantage would be in possibility add XP parition to GPT disk with lots of others GPT partitions without any special partitioning to get rid of special XP or MBR disks.. and boot every OS from one NVME drive..

That is exactly what I am proposing. If Windows XP is cloned/copied to an existing partition of GPT disk then only step 2 (exclusively with respect to setting the attribute Legacy BIOS Bootable to XP partition) and step 4 of Method #2 should be performed.

#4432

diderius6

⇗ @Levvon
Nice idea:))!!
Can you please write a Tutorial, step by step, what you have to do for to boot XP SP3 from a GPT harddisk.
I tested disk.sys and partmgr.sys (last versions from Winserver 2003 32 bit) and they work with GPT under XP SP3.
Have you tested, if this method can be used for to do UEFI boot of XP SP3 32 bit,
have a nice day
Dietmar

#4433 | Mov AX, 0xDEAD | ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (294) ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware updated info about generic Microsoft USB3 driver from Windows 8 We have another working USB3 driver for Windows XP !

#4434

diderius6

⇗ @Mov AX, 0xDEAD
Waaaoooohhhh:))..
This is a nice big step forward for future XP.
I tested today the modded AMD USB3 driver in MPS Multiprocessor Mode (means without any acpi)
but the same happened, not recognicing any USB device after some plug<>unplug.
So, I am very curious to test your modded Win8 USB3 driver for XP,
have a nice day
Dietmar

#4435

YuriyCN

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4433

> updated info about generic Microsoft USB3 driver from Windows 8
> We have another working USB3 driver for Windows XP !

I am pleased that a new USB3 driver has appeared.
Where can I download this driver to test it?

#4436

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4434

> but the same happened, not recognicing any USB device after some plug<>unplug

AMD driver probably is not generic as we assumed, there is nothing to say more. I think i can trace this issue if reproduce it sometime

#4437

diderius6

⇗ @Mov AX, 0xDEAD
I just make a test with the last version from ⇗ @daniel_k AMD USB3 driver on the nice Gigabyte H110M-2SH board.
I notice there also the plug <> unplug problem, even it is z170 (Skylake).
There, the board crashes after no USB device is recogniced any longer via the AMD driver.
I also noticed, that with a connected USB device, you can work as long as you want with the AMD USB3 driver,
I test this with linear read from AIDA64 many times one after the other. But AIDA64 crashes, when you connect, disconnect a lot of times other USB devices while AIDA64 is running
Dietmar
PS: Tomorrow I set up a Windbg session, may be it gives an advice for the USB3 crash.

#4438 | ruthan | ⇗ @Levvon Thanks i understand it in highlevel, but we need some step by step tutorial how to do that some step are not clear to me.
#4439 | infuscomus | ⇗ @Mov AX, 0xDEAD can you show us how you made your windows 8.0 USB 3.0 driver?
#4440 | Levvon | Windows XP @ GPT Proof Video: vimple.co/8614e295604f4cfd9b0045f6422619d9 Reproduction Kit: upload.ee/files/11625492/WinXP_GPT.zip.html

## Page 297

#4441

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4439

> can you show us how you made your windows 8.0 USB 3.0 driver?

same like usual - replacing mismatch imports to equivalents in original ms files
there about 7 files, i also made wdf 1.11 library compatible with Windows XP (convert Io(Dis)ConnectiInterruptEx->Io(Dis)ConnectiInterrupt, take code from DDK's intex.lib)

    wdf01000.sys v1.11.9200.20755 (win8_ldr.130621-1504)
     EtwRegister
     EtwUnregister
     EtwWrite
     PoGetSystemWake
     PoSetSystemWake
     IoConnectInterruptEx
     IoDisconnectInterruptEx

    WdfLdr.sys 1.11.9200.16384 (win8_rtm.120725-1247)
    patched to load WDF01_W8.SYS

    usbd.sys 6.2.9200.16384 (win8_rtm.120725-1247)
    _cookie_constant

    WppRecorder.sys 6.2.9200.16384 (win8_rtm.120725-1247)
    _cookie_constant

    USBXHCI.SYS 6.2.9200.16384 (win8_rtm.120725-1247)
     _cookie_constant
     EtwActivityIdControl
     EtwEventEnabled
     EtwRegister
     EtwUnregister
     EtwWrite
     IoGetDevicePropertyData
     IoQueueWorkItemEx
     IoSetDevicePropertyData
     KdRefreshDebuggerNotPresent
     KeGetProcessorIndexFromNumber
     KeQueryActiveProcessorCountEx
     KeQueryDpcWatchdogInformation
     wcsncpy_s
     ZwAlpcConnectPort
     ZwAlpcSendWaitReceivePort

    UCX01000.SYS 6.2.9200.16384 (win8_rtm.120725-1247)
     cookie_constant
     EtwActivityIdControl
     EtwRegister
     EtwUnregister
     EtwWrite
     IoQueueWorkItemEx
     KdRefreshDebuggerNotPresent
     KeGetCurrentProcessorNumberEx
     ObfDereferenceObjectWithTag
     ObfReferenceObjectWithTag

#4442 | Mov AX, 0xDEAD | I've got reports about increasing speed with win8 usb3 driver - i think this is auto enabled UASP mode Original drivers from manufacturers offer separate utils to enable uasp mode (VIA UAS Client or ASUS USB 3.0 Boost), speed after also increasing

#4443

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4437

> I notice there also the plug <> unplug problem, even it is z170 (Skylake).
> There, the board crashes after no USB device is recogniced any longer via the AMD driver.

yesterday i played with "plug <> unplug", after some time no more devices was recognized (last inserted detected as unknow device in d3 state), changing driver on live OS to fresco or win8 doesnt recover controller. Suprise from fresco because i know it do force reset and power cycle on all ports on loading, so seems controller even can't reset properly after touching by amd' hands (
No BSOD, no errors, just ports hangs, very hard to investigate...

#4444 | unique1188 | ⇗ @deSSy2724 off topic, but, this thread has almost 300 pages and this will be #4444 post. I am curious, is your PC ready and running as you first intended to build? ⇗ @Mov AX, 0xDEAD what part of Uzb do you come from if I may ask?

#4445

diderius6

This is the original driver for 32 bit from AMD for the Zeppelin Chipset x570.
This driver recognices only on each second boot any USB device
Dietmar
PS: But we have ⇗ @Mov AX, 0xDEAD :))..
diderius6 has attached files to this post

- ⇗ AMD2000068Zeppelin32BIT.rar

#4446

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4445

> This is the original driver for 32 bit from AMD for the Zeppelin Chipset x570

"Unoriginal" fake signed by "Edgard Roberto Viera/Riolin Limited" )
p.s. It is Etron v0119 usb3 driver with replaced IDs from Etron to Intel

> Zitat von ⇗ unique1188 im Beitrag ¶ #4444

> @Mov AX, 0xDEAD what part of Uzb do you come from if I may ask?

offtop: Tashkent city

#4447

Illen

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4442

> I've got reports about increasing speed with win8 usb3 driver - i think this is auto enabled UASP mode
> Original drivers from manufacturers offer separate utils to enable uasp mode (VIA UAS Client or ASUS USB 3.0 Boost), speed after also increasing

Windows 8 xHCI stack supports UASP, but to make any use of it, you also need uaspstor.sys and a storage device that supports it.

#4448

Zucker2k

> Zitat von ⇗ Levvon im Beitrag ¶ #4440

> Windows XP @ GPT
> Proof Video:
> vimple.co/8614e295604f4cfd9b0045f6422619d9
> Reproduction Kit:
> upload.ee/files/11625492/WinXP_GPT.zip.html

This deserves its own own thread. Well done!

#4449

Mov AX, 0xDEAD

I've found my little mistake in Win8 USB3.0 driver, please patch USBXHCI.SYS:
1) FF15E4B00300B001897E70=>897E70FF15E4B00300B001
2) 85338C33=>85338F33
3) recalc checksum
4) final sha1=c6d35c456e5b011603fae67472bf1a4aacf61b42
No more patches need, so driver now STABLE, let' name it as BETA1

#4450

Pill Monster

> Zitat von ⇗ gordo999 im Beitrag ¶ #4423

> > Zitat von ⇗ Pill Monster im Beitrag ¶ #4422

> > Page file or swapping does not allow access to over 4GB RAM. I will respond in more detail in some time.....

> @Pill Monster ...That's what I am trying to say. Normal page swapping with the XP memory manager is done using 4K pages and it is done to disk. It is a pure 32-bit system. PAE allows the size of the page files to increase in size by increasing the memory addressing space by 4-bits, to 36 bits. However, the normal x86 XP memory manager is not designed to work with PAE to access RAM > 4GB directly.
> To use memory beyond 4GB meaningfully, you need extra drivers that work in conjunction with the memory manager, a system called AWE (Advanced Windowing Extensions). Another name often used for PAE (Physical Address Extension) is Page Address Extension. I think that's a better description of what PAE does, it increases the page size available to the memory manager and allows the pages to be stored in the extra RAM beyond 4GB. However, if an app is not written to use such features, I don't see how PAE alone will allow access to extra RAM on a normal 32-bit system.
> How the system uses PAE to access RAM > 4GB is not clear to me. It appears you can use PAE to install a RAM disk but, as I understand it, a Ramdisk requires separate software/drivers to run it. Here's a link to people discussing this problem and one mentions what I suggested about the old DOS systems that software is required to 'trick' apps into thinking they had more memory. The EMM memory manager did it using a small area of DOS RAM to map memory to an external memory card.
> ⇗ https://superuser.com/questions/292207/i...sing-windows-xp
> "Exceeding the 4GB cap is harder. It requires playing addressing tricks of the sort that used to be required in the days of 16bit systems. I have heard tales that it's possible to break this barrier in 32bit XP, but it requires much more than a simple registry edit. IIRC, the limit is compiled into the operating system directly. To get around it, you have to find a specific .dll file from a 32bit Server 2003 machine and use it to replace the equivalent file on your Windows XP machine. For this to work, the file has to be modified so that XP won't reject it and you have to use volume shadow copy to get it to replace the existing file. I don't remember and can't find the link now for which file you need or how to modify it. After this is accomplished, you should be able to make the same settings to 32bit XP that you can to Server 2003 to allow the higher memory cap. Of course, such a change is highly unsupported and violates your license agreement".

> Zitat

> @Pill Monster .[quote]..it was not true memory support as we would expect on a 64-bit system with 64 Gb RAM. They used the extended memory as a form of virtual memory. Rather than paging out RAM to disk, they were paging it into higher memory regions because the paging works faster in RAM than on disk.
> PAE is a processor-based paging system. It does not enable more RAM for normal use, it has extended address features that can address addresses higher than 4 GB but for a pagefile system only. It's not possible to access RAM beyond 4GB using 32-bits. PAE has a very limited ability to store addresses beyond 4GB but it cannot address them directly by normal means.

OK, I'll respond as best I can without writing a thesis.... but this is not an easy topic to cover, and I suck at explaining anything technical. I'll post some links though. :)
The first thing you should be aware of is that the material published on MSDN (particularly the old site) or any MS or Intel related sites pertaining to memory relate almost exclusively to and is heavily biased toward Intel.
During the time period we are talking about Intel were trying to drive AMD into the ground with Microsoft's full co-operation and they almost succeeded.... but that's another story in itself.
AMD before K8 & Intel up until C2D (Intel64) used segmented memory (2GB kernel 2GB userspace). AMD64 (Athlon64 onward) with 40bit capability used a flat memory model. From Athlon64's release until Core Two Duo Intel and AMD CPU's handled memory management differently. Athlon64 supported 128GB RAM (actually more but MS don't officially support more than what they've tested ). SuperUser isn't a great source either. If anything check Stack Overflow, the info there is more reliable....different category of users.
A process lives in a virtual world inside the OS which lives in a virtual world inside the CPU - like a box within a box. What's fundamental to this is the CPU handles all address translation. The CPU is only part of the entire system with direct access to RAM, the CPU alone (with exception of a small part of the kernel) knows how much RAM is installed. Not the OS or any process.
Say you have XP installed on Phenom II with 32GB of RAM - def no need for a pagefile. What happens is when the process requests some data the first time it's mapped into memory and process view by the x64 CPU.
When the process reaches it's 4GB working set limit & requests data the CPU pages in the data and moves some other page from user to kernel (kernel is outside process view). That unmapped page is kept in RAM & the next time the process requests the same data it's already in RAM so the CPU TLB does a page table walk to find where in ram that data is then maps it back into process view. This is called page replacement policy....

> Zitat

> PAE works with the memory manager to enable memory 'page swapping' to memory beyond 4GB. I don't know enough about this to agree or disagree with your point that the RAM beyond 4GB should have been made available to normal Windows users. I suspect that maybe you're right. I do know that RAM page swapping is required because 4GB is not enough for running an OS like XP with more than a trivial app like Notepad running. So, RAM pages get swapped (paged) to disk. With PAE, they get swapped to RAM beyond 4GB.

I guess the simplest answer is that a 32bit processor has a 4GB limit, but an x64 (40, 48,52bit & so on) doesn't. The 4GB limitation is a hardware limitation of x86 (32bit) hardware.
That's all. It is not by design an Operating System limitation.

> Zitat

> The question for me is how do you use PAE when it is enabled? You would need an app written to address it and another system module to run with the memory manager to use it. Server 2003 has that system module but as far as I know it is not available in a normal Windows OS. Maybe you could adapt it to run on a normal system, I don't know.

Well as I mentioned applications have no knowledge or are even aware of RAM.

> Zitat

> To be realistic, if you want to address 64 GB of RAM directly you need a 64-bit system. PAE relies on a 36 bit address capability and trickery.
> This is similar to the old EMS/EMM memory managers with DOS. They found ways to swap memory out to external memory cards but those cards were never directly under DOS control. DOS could only address 640K RAM and with a bit of trickery, they managed to extend it to 1 MB.

This is not the case. Also 64bit is a misnomer anyway since last I checked the most any CPU can access is 57bit. The "x86" & "x64" part of Operating System's name is the support for either x86 or x64 CPU architecture. It's not memory support.
⇗ @gordo999 please check this link, it should be very helpful..
⇗ https://www.geoffchappell.com/notes/wind...ense/memory.htm

#4451

Pill Monster

> Zitat von ⇗ deSSy2724 im Beitrag ¶ #5

> 1. So, basically...... XP 32bit can only be installed to the MBR partition and nothing can change that BUT with help of 3rd party tools like this one (link below), XP can read/access other GPT partitions and I should be able to install programs/games normally to that GPT partitions, right?
> ⇗ https://www.paragon-software.com/de/tech...nts/gpt-loader/
> 2. For slipstreaming, just adding correct hardware IDs for the SATA AHCI controller of my mainboard is enough to install XP 32bit? Wat if my MBO has multiple AHCI controllers from different manufacturers, should I avoid Intels AHCI controller and use the others instead?
> 3. What is actually the disadvantage if I disable ACPI (desktop PC)? Would my CPU work always with full speed and never downclock when idle (Intels Turbo Clock technology) or what?. Is ACPI disabled system-wide (BIOS) or can it be only disabled for specific OS-es?
> 4. @Mov AX, 0xDEAD
> Are you trying to say that this user from this thread has ACPI disabled or what? How did he managed to install XP 32 bit with Coffe Lake MBO/CPU?
> ⇗ Windows XP 32bit SP3 now working with Z370 motherboard and Coffe Lake CPU

3rd party is usually best option when you want to do something that MS don't want you to do. ( Seriously).
for example GPT partitions can easily be cloned despite what MS library says. Just not with MS software.
Same with XP support for GPT, it's really up to ASmedia or Jmicron not MS
Also - are you guys with issues using the vanilla XP? Last night I checked tpb and only SP3 was listed. No SP1

#4452

infuscomus

I'm trying to get Mov Ax 0xDEAD's USB 3 driver to load during XP texmode setup.
Trying to start by getting KMDF 1.11 to load by adding them to txtsetup.sif,
wdfldr8.sys - loads fine
wdf01_w8.sys - fails to load, says "wdf01_w8.sys is corrupt"
I must've missed something - but the only dependencies I can see for wdf01_w8.sys are hal.dll ntoskrnl.exe and wdfldr8.sys
the driver loads just fine booted into windows

#4453

Mov AX, 0xDEAD

ported driver has original win8 bug:
In case of connection "storage->external hub->port on MoBo" when you safe remove storage, it will marked as yellow and wait for ejecting. But driver cannot detect physical ejecting and will show this phantom storage until you do some with this hub, insert or eject something to any ports. Win10 driver doesnt have this bug, Win8.1 not tested
Maybe its bug of firmware/chips in external hub, i dont know...

#4454

diderius6

⇗ @infuscomus
You can also try to build one txtsetup.oem for all the files and make a try with Nlite
Dietmar
PS: I notived, that USB boot is not possible. All drivers are loaded after first boot stage.
When you force them to boot earlier, USB boot hangs.
I think, this happens because of needed KMDF.

#4455

diderius6

I am just running a Windbg session on the ASRock Fatal1ty Z370 Gaming K6 board
for the modded AMD USB3 1.1.0.0145 driver.
After plug<>unplug USB hangs,
I got message from windbg
watchdog!WdUpdateRecoveryState: Recovery enabled.
And usbstor.sys is unloaded
Unloaded modules:
b83e0000 b83e7000 USBSTOR.SYS
b83d8000 b83df000 USBSTOR.SYS
b8328000 b832f000 USBSTOR.SYS
During a search with google they wrote:
"you have a
driver that's failing on a power transition to D0."
Dietmar

## Page 298

#4456

diderius6

For to set up a really good version of the Windbg session for XP SP3,
first I solved the timer problem for the checked version halmacpi.dll for XP SP3 and the normal checked ntkrpamp.exe.
Nice, works:))!
Now I get such a lot of output
Dietmar
diderius6 has attached files to this post

- ⇗ DebugXPSP3.rar

#4457

diderius6

Yepp, I can fix exact the timepoint,
when the USB device crashes. And direct before crash, the USB stick goes down D0 => D3 .
Dietmar

>     Wed
>      May  6 17:42:45.981 2020 (UTC + 2:00): Break repeatedly, break Once,
>     Ignore, terminate Process, or terminate Thread (boipt)? i
>     i
>     Wed May  6 17:42:45.981 2020 (UTC + 2:00):
>     Wed May  6 17:43:00.434 2020 (UTC + 2:00): RTL: Ignoring attempt to delete a pinned atom (c009)

>     0: kd> !devnode 0 1 usbstor
>     Dumping IopRootDeviceNode (= 0x8b974dc8)
>     DevNode 0x8b91ddb0 for PDO 0x8b91df10
>       InstancePath is "Root\LEGACY_USBSTOR\0000"
>       ServiceName is "USBSTOR"
>       State = DeviceNodeRemoved (0x312)
>       Previous State = DeviceNodeStarted (0x308)
>       Problem = CM_PROB_DEVICE_NOT_THERE

>     0: kd> !devnode 0x88d79e30
>     DevNode 0x88d79e30 for PDO 0x88c989e8
>       Parent 0x8b7eaed8   Sibling 0000000000   Child 0000000000
>       InstancePath is "USB\Vid_0000&Pid_0000\5&290e4c81&0&17"
>       State = DeviceNodeInitialized (0x302)
>       Previous State = DeviceNodeUninitialized (0x301)
>       StateHistory[02] = DeviceNodeUninitialized (0x301)
>       StateHistory[01] = DeviceNodeInitialized (0x302)
>       StateHistory[00] = DeviceNodeUninitialized (0x301)
>       StateHistory[19] = Unknown State (0x0)
>       StateHistory[18] = Unknown State (0x0)
>       StateHistory[17] = Unknown State (0x0)
>       StateHistory[16] = Unknown State (0x0)
>       StateHistory[15] = Unknown State (0x0)
>       StateHistory[14] = Unknown State (0x0)
>       StateHistory[13] = Unknown State (0x0)
>       StateHistory[12] = Unknown State (0x0)
>       StateHistory[11] = Unknown State (0x0)
>       StateHistory[10] = Unknown State (0x0)
>       StateHistory[09] = Unknown State (0x0)
>       StateHistory[08] = Unknown State (0x0)
>       StateHistory[07] = Unknown State (0x0)
>       StateHistory[06] = Unknown State (0x0)
>       StateHistory[05] = Unknown State (0x0)
>       StateHistory[04] = Unknown State (0x0)
>       StateHistory[03] = Unknown State (0x0)
>       Flags (0x00000030)  DNF_ENUMERATED, DNF_IDS_QUERIED
>       CapabilityFlags (0x00005402)  DeviceD2, WakeFromD0,
>                                     WakeFromD2, HardwareDisabled

>     0: kd> !devnode 0 1 amdxhc
>     Dumping IopRootDeviceNode (= 0x8b974dc8)
>     DevNode 0x8b7ee5b8 for PDO 0x8b85be50
>       InstancePath is "PCI\VEN_8086&DEV_A2AF&SUBSYS_A2AF1849&REV_00\3&11583659&0&A0"
>       ServiceName is "amdxhc"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0x8b7eaed8 for PDO 0x8b856918
>         InstancePath is "AMDUSB30\ROOT_HUB30\4&556f44c&7"
>         ServiceName is "amdhub30"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>         DevNode 0x8b6942d0 for PDO 0x8b662b20
>           InstancePath is "USB\Vid_174c&Pid_2074\5&290e4c81&0&3"
>           ServiceName is "amdhub30"
>           State = DeviceNodeStarted (0x308)
>           Previous State = DeviceNodeEnumerateCompletion (0x30d)
>         DevNode 0x8b693008 for PDO 0x8b66a890
>           InstancePath is "USB\Vid_174c&Pid_3074\5&290e4c81&0&23"
>           ServiceName is "amdhub30"
>           State = DeviceNodeStarted (0x308)
>           Previous State = DeviceNodeEnumerateCompletion (0x30d)
>            DevNode 0x88d79e30 for PDO 0x88c989e8
>           InstancePath is "USB\Vid_0000&Pid_0000\5&290e4c81&0&17"
>           State = DeviceNodeInitialized (0x302)
>           Previous State = DeviceNodeUninitialized (0x301)
>     DevNode 0x8b91f578 for PDO 0x8b91f6d8
>       InstancePath is "Root\LEGACY_AMDXHC\0000"
>       ServiceName is "amdxhc"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)

>     0: kd> !devnode 0 1 amdhub30
>     Dumping IopRootDeviceNode (= 0x8b974dc8)
>     DevNode 0x8b7eaed8 for PDO 0x8b856918
>       InstancePath is "AMDUSB30\ROOT_HUB30\4&556f44c&7"
>       ServiceName is "amdhub30"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0x8b6942d0 for PDO 0x8b662b20
>         InstancePath is "USB\Vid_174c&Pid_2074\5&290e4c81&0&3"
>         ServiceName is "amdhub30"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0x8b693008 for PDO 0x8b66a890
>         InstancePath is "USB\Vid_174c&Pid_3074\5&290e4c81&0&23"
>         ServiceName is "amdhub30"
>         State = DeviceNodeStarted (0x308)
>         Previous State = DeviceNodeEnumerateCompletion (0x30d)
>       DevNode 0x88d79e30 for PDO 0x88c989e8
>         InstancePath is "USB\Vid_0000&Pid_0000\5&290e4c81&0&17"
>         State = DeviceNodeInitialized (0x302)
>         Previous State = DeviceNodeUninitialized (0x301)
>     DevNode 0x8b91f7d0 for PDO 0x8b91f930
>       InstancePath is "Root\LEGACY_AMDHUB30\0000"
>       ServiceName is "amdhub30"
>       State = DeviceNodeStarted (0x308)
>       Previous State = DeviceNodeEnumerateCompletion (0x30d)

#4458

diderius6

May be, we can hack ntoskrnl,
for to overcome the problems with the AMD USB3 driver.
The sentence is in ntoskrnl RTL atom.c
Dietmar

    NTSTATUS
    RtlDeleteAtomFromAtomTable(
        IN PVOID AtomTableHandle,
        IN RTL_ATOM Atom
           )
    {
        NTSTATUS Status;
        PRTL_ATOM_TABLE p = (PRTL_ATOM_TABLE)AtomTableHandle;
        PRTL_ATOM_TABLE_ENTRY a, *pa;

           RTL_PAGED_CODE();
        if (!RtlpLockAtomTable( p )) {
            return STATUS_INVALID_PARAMETER;
                   }
        try {
            Status = STATUS_INVALID_HANDLE;
            if (Atom >= RTL_ATOM_MAXIMUM_INTEGER_ATOM) {
                a = RtlpAtomMapAtomToHandleEntry( p,
                                                  (ULONG)(Atom & (USHORT)~RTL_ATOM_MAXIMUM_INTEGER_ATOM)
                                                                                           );
                if (a != NULL && a->Atom == Atom) {
                    Status = STATUS_SUCCESS;
                    if (a->Flags & RTL_ATOM_PINNED) {
                        KdPrint(( "RTL: Ignoring attempt to delete a pinned atom (%x)\n", Atom ));
                                                              Status = STATUS_WAS_LOCKED;        // This is a success status code!
                                           }
                                   else
                    if (--a->ReferenceCount == 0) {
                        a = RtlpHashStringToAtom( p, a->Name, &pa, NULL );
                        if (a != NULL) {
                            if (pa != NULL) {
                                *pa = a->HashLink;
                                                   }
                            RtlpFreeHandleForAtom( p, a );
                            RtlpFreeAtom( a );
                                                   }
                                           }
                                   }
                           }
                   else
            if (Atom != RTL_ATOM_INVALID_ATOM) {
                Status = STATUS_SUCCESS;
                           }
                   }
        except (EXCEPTION_EXECUTE_HANDLER) {
            Status = GetExceptionCode();
                   }

        RtlpUnlockAtomTable( p );

        return Status;
    }

#4459

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #4456

> For to set up a really good version of the Windbg session for XP SP3,
> first I solved the timer problem for the checked version halmacpi.dll for XP SP3 and the normal checked ntkrpamp.exe.
> Nice, works:))!
> Now I get such a lot of output
> Dietmar

How to use the files (hal3.dll, ntos3.exe) you uploaded? They need to be renamed and put to c:\WINDOWS\system32. What problem do these files solve?

#4460

diderius6

⇗ @YuriyCN
These files ar only needed for debug of XP SP3, when you want to take a closer look, what happens with any driver.
With this files you have the minimal setup for a debug version
of XP SP3
Dietmar
PS: Just copy the files to C:\WINDOWS\system32
and add in boot.ini the line
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP ProfessionalAcpiDEBUG" /kernel=ntos3.exe /Hal=hal3.dll /debug /debugport=COM1 /baudrate=115200

#4461

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #4460

> @YuriyCN
> These files ar only needed for debug of XP SP3, when you want to take a closer look, what happens with any driver.
> With this files you have the minimal setup for a debug version
> of XP SP3
> Dietmar
> PS: Just copy the files to C:\WINDOWS\system32
> and add in boot.ini the line
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP ProfessionalAcpiDEBUG" /kernel=ntos3.exe /Hal=hal3.dll /debug /debugport=COM1 /baudrate=115200

Thanks, now I understand.
Do you want to solve the problem with the pm_timer fix here?
⇗ What exactly is the hal timer problem? (3)

#4462

diderius6

I noticed, that the HUB from the AMD driver can send devices to D3 state,
but has no possibilty to awake the USB device from D3.
I compare this with the Asmedia Hub. This can send and awake from D3.
Dietmar
AMD USB 3.0 Root Hub
PDCAP_D0_SUPPORTED
PDCAP_D2_SUPPORTED
PDCAP_D3_SUPPORTED
PDCAP_WAKE_FROM_D0_SUPPORTED
PDCAP_WAKE_FROM_D2_SUPPORTED
Asmedia USB Root Hub
PDCAP_D0_SUPPORTED
PDCAP_D3_SUPPORTED
PDCAP_WAKE_FROM_D3_SUPPORTED

#4463

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4456

> For to set up a really good version of the Windbg session for XP SP3,
> first I solved the timer problem for the checked version halmacpi.dll for XP SP3 and the normal checked ntkrpamp.exe.r

diderius6 ...Dietmar, are you talking about remote kernel debugging with windbg or local debugging? I've had no problem running windbg on XP SP3 locally, or doing full debugging sessions using Ollydbg version 1. My problem is getting it to run via a serial connection using a USB - serial adapter.
I already had a k-mode windbg session going between W7 as host and both W7 and W10 as targets using the same adapter. When I checked it recently it won't work at all on any OS. Trying to track down the issue and it seems the host sends data OK to the target but the serial data coming back from the target is distorted. Don't know if that has something to do with the drivers on the B360 chipset and the serial port. I have changed hal and intelppm, which has really improved the performance of XP but it may be causing a problem with the serial ports. Don't know, still working on it.

#4464

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4462

> I noticed, that the HUB from the AMD driver can send devices to D3 state,
> but has no possibilty to awake the USB device from D3.

diderius6 ...don't know if this is helpful.
Edit...not thinking clearly today, have a bit of a cold going on. Not covid or anything, just a sore throat and a fuzzy head. The USB device would have it's own Dx sleep state since the device can go into a sleep state while the mobo is fully awake. Since the sleep state is selectable usually, in Device Manager, it would seem the hub driver may have something to do with it. Of course, it could be anywhere from ACPI down.
The USB device has 4 conductors, 2 for power and 2 for serial comm. Obviously, the voltage to the device is fixed by the mobo and there is likely no separate Dx sleep state voltages for each USB device supplied by the mobo. You could verify that by monitoring the voltage to the device to see if it drops during a Dx state. If it stays the same, which is likely, the device is controlling the Dx state internally.
Therefore, the USB device must have an internal means of setting its Dx sleep state voltage. The signal to tell it whether to go into sleep mode or not comes from the Device Manager via ACPI, the XHCI driver and the hub driver. Since the data sent to the device is serial, it could be difficult to decipher it without a serial data/storage analyzer.
I'll leave the rest of the post in case it proves useful somehow, even though it is wrong.
My background is in hardware and I have traced out the circuits, on the mobo, for the sleep states you are talking about. Basically, each sleep state is a voltage level controlled by mosfets driven by a controller chip.
The inputs to these voltage level circuits are controlled by Hal and the drivers talk to the physical circuits/controllers through Hal. The highest level next to the OS executive is ACPI and all the USB drivers are in a tree with ACPI at the highest level, outside the executive. Th next level down from ACPI is the xhci driver, then the hub, then the device. You probably know all that better than I do.
From what I understand, the sleep states are controlled by ACPI. Most of the drivers we are using, like Hal, ACPI, XHCI, etc. have been modded. So, your sleep state problem could be in Hal, ACPI, XHCI, or maybe even intelppm.
I don't regard this as an easy problem to solve. On a mobo, you can check voltages and watch signals on a multiple input digital oscilloscope. However, the mobo is so densely packed, with traces suddenly going through the board to the other side, it's very difficult to work live on a mobo these days. Still, if you find the Dx sleep level input signal, you could bring it out with a conductor and attach it to an LED so you could check its state visually.
Then you could trace the drivers with windbg while toggling jump conditions to see where the Dx state was being blocked. Problem is, can windbg trace through ring 0 code? With softice, I could trace through any ring 0 code but whenever I try to enter ring 0 with windbg, at a sysenter, it kicks me out the other end. I have been told you can set a BP in ring 0 and windbg will stop at the BP. I don't know. I have traced through Hal with softice but I have never seen windbg do that. If it's possible, I'd like to know how.

#4465

diderius6

⇗ @gordo999
This problem with plug<>unplug and then suddently disconnect belongs to XP SP2 and XP SP3.
Hm, what changed from XP SP1 is the timer. So it may be really only a timer related problem.
Via USB boot also time plays an important role. Some people from reboot.pro introduced there during boot a time loop and can boot via USB a lot more motherboards. Microsoft themselves could not solve this problem. But they think also about a timer problem.
It is not Acpi related, because the problem is the same in MPS mode (without any Acpi)
Dietmar

#4466

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4465

> Some people from reboot.pro introduced there during boot a time loop and can boot via USB a lot more motherboards.

⇗ @diderius6 ....something just occurred to me. In digital electronics, there are conditions called a debouncing, latching, or race condition problem. The concept comes from the mechanical switches. When you press a mechanical switch, the contacts tend to bounce, causing the current to turn on and off rapidly until a positive connection is made. Rapid fluctuations in the voltage can throw the digital electronics out of sync and cause it to freeze.
They use an array of transistors, or a chip, to 'debounce' the switch action. It works by absorbing the first switch impulse, then latching the voltage at 5 volts, or whatever is required, so the +5 volts can't fluctuate. In other words, the switch contacts are connected to the debouncing circuit and the output of the debouncing circuit supplies a constant voltage after being activated by the first voltage spoke caused by the switch.
In a computer program they tend to use timers to do the same thing. So maybe the timer issue you mention has something to do with the USB problem. When you hot plug a device, like inserting or removing a USB device, it acts the same as a switch bouncing. The sudden insertion or removal causes voltages to fluctuate rapidly as spikes, and that can freeze the digital circuitry associated with the USB device.
A keybord is actually an array of mechanical switches. It would not be practical to provide individual solid state debouncers for each key therefore a timer is used in the keyboard driver in conjunction with each key press. When the driver detects a key press, it starts a timer to block out any bouncing in the keyboard key for a certain time period.
I imagine the same is done with USB devices perhaps in the hub driver, or further up the chain/tree, like in Hal. Whenever a USB device is inserted or removed, that action is detected with the first voltage spike and a timer is started to mask out the device digital data till the insertion/removal voltage spikes have settled down.
Here's a good article that explains hardware and software debouncing.
⇗ https://www.allaboutcircuits.com/technic...o-deal-with-it/

#4467

diderius6

⇗ @gordo999
This is really a nice idea!!!
I tested the AMD driver for USB3 when I boot XP SP3 from it. As long, as you do not disconnect the USB device,
it is rock stable. I do not have a single crash.
So, there may be a chance to prolong the time period for during plug<> unplug,
have a nice day
Dietmar

#4468

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4452

> Trying to start by getting KMDF 1.11 to load by adding them to txtsetup.sif,
> wdfldr8.sys - loads fine
> wdf01_w8.sys - fails to load, says "wdf01_w8.sys is corrupt"
> I must've missed something - but the only dependencies I can see for wdf01_w8.sys are hal.dll ntoskrnl.exe and wdfldr8.sys

After some tests i can say - current wdfldr8.sys is not ready for setup stage. It is loader for main wdf01_w8.sys, it look at registry \Registry\Machine\System\CurrentControlSet\Services\Wdf01_w8, read key ImagePath, then call ZwLoadDriver. So txtsetup.* must create these keys before loading usbxhci.sys/usbhub3.sys. As i know in txtsetup.oem we can use external *.inf (they probably will create keys), integrating drivers to setup is puzzle, i cant help with it in any way
Another option is link usbxhci.sys/usbhub3.sys/ucx0100.sys to wdf01_w8.sys directly, no more dependies to registry and services, but this job require assembler skills

#4469

infuscomus

⇗ @Mov AX, 0xDEAD
I was able to get KMDF 1.9 to load the VIA USB 3.0 driver in textmode thanks to help from the driverpacks.net forum team a number of years ago, it's a painful process getting it to work.
I tried the same process that worked for KMDF 1.9 with your modded KMDF 1.11 but unfortunately no such luck this time.
oh well, at least it works normally when booted into windows, so I'm happy with that.

#4470 | infuscomus | ⇗ @Mov AX, 0xDEAD are you going to try backporting the windows 10 USB 3.0 driver? edit: I got past the "wdf01_w8.sys is corrupt" error in textmode by doing a realignment of the file - hopefully I can load the USB 3.0 driver in textmode now, we'll see.

## Page 299

#4471

Mov AX, 0xDEAD

daniel_k found mistakes in PE headers in win8 usb3 driver, it caused loading errors in window installer
usbhub3.sys 0x350: 5442->0044, then recalc checksum
wdf01_w8.sys 0x2F8: F84A->004C, then recalc checksum

    340064116b210adf78239f1c171a69a07325c601    *UCX01000.SYS
    6b26c1252d7cc00e9b6e4c46ee773db03def4b90    *usbd_w8.sys
    7ea99282c304a13889b092eeb9f295ce1b681094   *USBHUB3.SYS
    c6d35c456e5b011603fae67472bf1a4aacf61b42     *USBXHCI.SYS
    18d4788bbf520e0c2f3ef95cbdd26f03fe519670      *WDF01_W8.SYS
    921913d31d9199d574d6fb77d077133002a1aff9    *WdfLdr8.sys
    ab0369d23c2a03a7c7d1769713770b3415761637  *WppRecorder.sys

#4472

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4470

> @Mov AX, 0xDEAD
> are you going to try backporting the windows 10 USB 3.0 driver?

No, i do not see reason until someone found serious bug in win 8.0 version, as i know only AMD X570 boards may have troubles, but it need more investigating

#4473

diderius6

I tried USB boot with the nice driver from ⇗ @Mov AX, 0xDEAD .
With Windbg I can see, that all files are loaded,
only the xhci driver not.
IOINIT: Built-in driver \Driver\USBXHCI failed to initialize - C000003A
Dietmar
IOINIT: Built-in driver xxxxxx failed to initialize − 0xnnnnnnnn
The boot start driver named xxxxxx returned a failure status 0xnnnnnnnn from its DriverEntry entry point.

#4474

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4473

> I tried USB boot
> IOINIT: Built-in driver \Driver\USBXHCI failed to initialize - C000003A

How to reproduce this "usb boot" ?

#4475

diderius6

In registry I set by hand in Services
usbstor Group System Reserved
Start 0
WDF01_W8 Group System Reserved
Start 0
USBHUB3 Group Boot Bus Extender
Start 0
USBXHCI Group Boot Bus Extender
Start 0
I think, that WDF01_W8 has to be loaded as the very first of all.
With this settings, all files are loaded,
only USBXHCI not
Dietmar
EDIT: Before USB boot, I show the USB device to the harddisk with the registry entries above, then I put this harddisk in this USB device.
EDIT: May be, the IOINIT message can be ignored.
The main reason is BSOD 0x7B for the harddisk in the USB caddy.

#4476

diderius6

>     Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
>     Copyright (c) Microsoft Corporation. All rights reserved.

>     Opened \\.\com1
>     Waiting to reconnect...
>     Connected to Windows XP 2600 x86 compatible target at (Fri May  8 22:14:46.687 2020 (UTC + 2:00)), ptr64 FALSE
>     Kernel Debugger connection established.
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Symbol search path is: C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386;SRV*c:\symbols
>     *⇗ http://msdl.microsoft.com/download/symbols;C:\symbols
>     Executable search path is: C:\localsymbols
>     Windows XP Kernel Version 2600 MP (1 procs) Checked x86 compatible
>     Built by: 2600.xpsp.080413-2133
>     Machine Name:
>     Kernel base = 0x80a02000 PsLoadedModuleList = 0x80b019e8
>     System Uptime: not available
>     WARNING: Inaccessible path: 'C:\WinDDK\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386'
>     Fri
>      May  8 22:14:48.843 2020 (UTC + 2:00): MM: Loader/HAL memory block
>     indicates large pages cannot be used for 80100000->8012777F
>     Fri May  8 22:14:54.453 2020 (UTC + 2:00): MTRR feature disabled.
>     Fri May  8 22:14:54.453 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.468 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.468 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.515 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.515 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.562 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.562 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.609 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.609 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.656 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.656 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.703 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.703 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.750 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.750 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.796 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.796 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.843 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.843 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.890 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.890 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.937 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.937 2020 (UTC + 2:00):
>     Fri May  8 22:14:54.984 2020 (UTC + 2:00): KiInitializeMTRR: OS support for MTRRs disabled
>     Fri May  8 22:14:54.984 2020 (UTC + 2:00):
>     Fri May  8 22:14:56.250 2020 (UTC + 2:00): IOINIT: Built-in driver \Driver\USBXHCI failed to initialize - C000003A
>     Fri May  8 22:14:56.250 2020 (UTC + 2:00):
>     Fri May  8 22:14:56.359 2020 (UTC + 2:00):

>     Intel Storage Driver Ver: 11.2.0.1006

>     Fri May  8 22:14:56.359 2020 (UTC + 2:00):
>     Fri May  8 22:14:59.437 2020 (UTC + 2:00):
>     *** Fatal System Error: 0x0000007b
>                                                  (0xB84C7518,0xC0000034,0x00000000,0x00000000)

>     Fri May  8 22:14:59.484 2020 (UTC + 2:00): Break instruction exception - code 80000003 (first chance)

>     A fatal system error has occurred.
>     Debugger entered on first try; Bugcheck callbacks have not been invoked.

>     A fatal system error has occurred.

>     Connected to Windows XP 2600 x86 compatible target at (Fri May  8 22:14:59.625 2020 (UTC + 2:00)), ptr64 FALSE
>     Loading Kernel Symbols
>     ...................................
>     Loading User Symbols

>     Loading unloaded module list
>     .
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     Use !analyze -v to get detailed debugging information.

>     BugCheck 7B, {b84c7518, c0000034, 0, 0}

>     Probably caused by : ntkrpamp.exe ( nt!IopMarkBootPartition+f5 )

>     Followup: MachineOwner
>     ---------

>     nt!RtlpBreakWithStatusInstruction:
>     80ac37ec cc              int     3
>     0: kd> !analyze -v
>     *******************************************************************************
>     *                                                                             *
>     *                        Bugcheck Analysis                                    *
>     *                                                                             *
>     *******************************************************************************

>     INACCESSIBLE_BOOT_DEVICE (7b)
>     During the initialization of the I/O system, it is possible that the driver
>     for the boot device failed to initialize the device that the system is
>     attempting to boot from, or it is possible for the file system that is
>     supposed to read that device to either fail its initialization or to simply
>     not recognize the data on the boot device as a file system structure that
>     it recognizes.  In the former case, the argument (#1) is the address of a
>     Unicode string data structure that is the ARC name of the device from which
>     the boot was being attempted.  In the latter case, the argument (#1) is the
>     address of the device object that could not be mounted.
>     If this is the initial setup of the system, then this error can occur if
>     the system was installed on an unsupported disk or SCSI controller.  Note
>     that some controllers are supported only by drivers which are in the Windows
>     Driver Library (WDL) which requires the user to do a custom install.  See
>     the Windows Driver Library for more information.
>     This error can also be caused by the installation of a new SCSI adapter or
>     disk controller or repartitioning the disk with the system partition.  If
>     this is the case, on x86 systems the boot.ini file must be edited or on ARC
>     systems setup must be run.  See the "Advanced Server System Administrator's
>     User Guide" for information on changing boot.ini.
>     If the argument is a pointer to an ARC name string, then the format of the
>     first two (and in this case only) longwords will be:
>         USHORT Length;
>         USHORT MaximumLength;
>         PWSTR Buffer;
>     That is, the first longword will contain something like 00800020 where 20
>     is the actual length of the Unicode string, and the next longword will
>     contain the address of buffer.  This address will be in system space, so
>     the high order bit will be set.
>     If the argument is a pointer to a device object, then the format of the first
>     word will be:
>         USHORT Type;
>     That is, the first word will contain a 0003, where the Type code will ALWAYS
>     be 0003.
>     Note that this makes it immediately obvious whether the argument is a pointer
>     to an ARC name string or a device object, since a Unicode string can never
>     have an odd number of bytes, and a device object will always have a Type
>     code of 3.
>     Arguments:
>     Arg1: b84c7518, Pointer to the device object or Unicode string of ARC name
>     Arg2: c0000034
>     Arg3: 00000000
>     Arg4: 00000000

>     Debugging Details:
>     ------------------

>     DEFAULT_BUCKET_ID:  DRIVER_FAULT

>     BUGCHECK_STR:  0x7B

>     PROCESS_NAME:  System

>     LAST_CONTROL_TRANSFER:  from 80a30d7b to 80ac37ec

>     STACK_TEXT:
>     b84c7080 80a30d7b 00000003 b84c73dc 00000000 nt!RtlpBreakWithStatusInstruction
>     b84c70cc 80a319e6 00000003 80085000 e2b94408 nt!KiBugCheckDebugBreak+0x19
>     b84c74ac 80a31f77 0000007b b84c7518 c0000034 nt!KeBugCheck2+0x574
>     b84c74cc 80d32863 0000007b b84c7518 c0000034 nt!KeBugCheckEx+0x1b
>     b84c7634 80d380f6 80085000 00000000 80085000 nt!IopMarkBootPartition+0xf5
>     b84c7684 80d341f1 80085000 b84c76a0 00034000 nt!IopInitializeBootDrivers+0x53e
>     b84c7830 80d31940 80085000 00000000 8bcdcda8 nt!IoInitSystem+0x82d
>     b84c7dac 80bd81ac 80085000 00000000 00000000 nt!Phase1Initialization+0xb12
>     b84c7ddc 80ae4212 80d30e2e 80085000 00000000 nt!PspSystemThreadStartup+0x34
>     00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

>     STACK_COMMAND:  kb

>     FOLLOWUP_IP:
>     nt!IopMarkBootPartition+f5
>     80d32863 8d85e0feffff    lea     eax,[ebp-120h]

>     SYMBOL_STACK_INDEX:  4

>     SYMBOL_NAME:  nt!IopMarkBootPartition+f5

>     FOLLOWUP_NAME:  MachineOwner

>     MODULE_NAME: nt

>     IMAGE_NAME:  ntkrpamp.exe

>     DEBUG_FLR_IMAGE_TIMESTAMP:  4802b3ce

>     FAILURE_BUCKET_ID:  0x7B_nt!IopMarkBootPartition+f5

>     BUCKET_ID:    0x7B_nt!IopMarkBootPartition+f5

>     Followup: MachineOwner
>     ---------

#4477

diderius6

With this settings in Registry
I get all drivers initialised and started,
but still 0x7B BSOD.

    usbstor Group System Reserved
    Start 0

    WDF01_W8 Group System Reserved
    Start 0

    USBHUB3 Group System Reserved
    Start 1

    USBXHCI Group System Reserved
    Start 1

Dietmar

#4478

diderius6

Because txtsetup.oem works ( ⇗ @daniel_k ) for the nice Win8 to XP SP3 USB3 driver,
I try tomorrow an entry
USB\Class_08&SubClass_06&Prot_62
into
CriticalDeviceDatabase of XP SP3
Dietmar

#4479

infuscomus

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4472

> only AMD X570 boards may have troubles

what kinds of troubles? nothing too serious I hope?

#4480

diderius6

⇗ @infuscomus
I test a lot of boards.
On all, the nice new USB3 driver from ⇗ @Mov AX, 0xDEAD ported from Win8 to XP SP3 works.
Only on the x570 board on half of the ports.
There are reports from Win10 on those USB3 slots of problems for the x570 boards.
I take a deeper look what is going on there.
When you install the new USB3 driver there new, all is ok.
But on next reboot it is gone, "unknown device",
brrr..
Dietmar
PS: May be that this can be overcome with an extra entry in CriticalDeviceDataBase. This I try today, first for USB boot.
EDIT: In this night ⇗ @daniel_k succeeds to integrate the KMDF driver in the XP Setup CD.
I want to do USB boot with it, the problem in this is, that nowhere it is described, how to set up a boot device with KMDF.

#4481

diderius6

First I try now
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\usb#Class_08&SubClass_06&Prot_50]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="USBSTOR"
Dietmar

#4482

diderius6

Now together with next one
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0c0330]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbxhci"
Dietmar

#4483

diderius6

And together with next one
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\usb#root_hub30]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="usbhub3"

#4484

diderius6

And with this one
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\usb#vid_174C&pid_1153]
"ClassGUID"="{36FC9E60-C465-11CF-8056-444553540000}"
"Service"="USBSTOR"

#4485

diderius6

And the last one
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\usbstor#DiskASMT____2115____________0___]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

## Page 300

#4486

diderius6

May be, that the KMDF also needs an entry in CriticalDeviceDatabase
but I found nothing about boot device for this.
It should look something like
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\root#LEGACY_WDF01_W8]
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"Service"="WDF01_W8"
Dietmar

#4487 | diderius6 | YESSSSSSSSSSSSSSSSSSSSSSSSSAAAAAAAAAAAAAAAAAAAAA:::))999)))))))))))))))))))))))):))))) I got it Boot XP SP3 from USB with the nice USB3 driver from ⇗ @Mov AX, 0xDEAD Dietmar ⇗

#4488

diderius6

How I reach this?
⇗ @daniel_k gives me the tip, that I just forget UCX01000.SYS.
This is really crazy, because this driver has no dependencies to xhci and usbhub3.
I make an easy test: I renamed UCX01000.SYS to UuuCX01000.SYS
and restart the compi. Oh, no USB device was recogniced any longer.
The rest was easy. Because of years with USB booting for XP, I get a feeling, what may work and what not.
I make a 7. entry in CriticalDeviceDatabase
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase]
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CriticalDeviceDatabase\root#LEGACY_UCX01000]
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"Service"="UCX01000"
and then I set in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
WDF01_W8 Group System Reserved start 0
UCX01000 Group Boot Bus Extender start 0
USBSTOR Group Boot Bus Extender start 0
USBXHCI Group Boot Bus Extender start 0
USBHUB3 Group Boot Bus Extender start 0
It is stable
Dietmar

#4489

usa1ec

> Zitat

> gives me the tip, that I just forget UCX01000.SYS.
> This is really crazy, because this driver has no dependencies to xhci and usbhub3.
> I make an easy test: I renamed UCX01000.SYS to UuuCX01000.SYS
> and restart the compi. Oh, no USB device was recogniced any longer.
> The rest was easy. Because of years with USB booting for XP, I get a feeling, what may work and what not.

Where can I download this USB driver.
Please give a URL?

#4490

skullteria

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4472

> > Zitat von ⇗ infuscomus im Beitrag ¶ #4470

> > @Mov AX, 0xDEAD
> > are you going to try backporting the windows 10 USB 3.0 driver?

> No, i do not see reason until someone found serious bug in win 8.0 version, as i know only AMD X570 boards may have troubles, but it need more investigating

Hey man, can you made this port for x64?

#4491

Mov AX, 0xDEAD

> Zitat von ⇗ skullteria im Beitrag ¶ #4490

> can you made this port for x64?

No, x64 for me is not funny as x32, i dont plan do anything for these OSes

#4492

infuscomus

⇗ @diderius6
I've been trying to get the USB 3.0 driver to start for GUI phase of setup (before the EULA) using a VM
I'm not having any luck so far
I added these to hivesys.inf

    HKLM,"SYSTEM\CurrentControlSet\Services\wdfldr8","ErrorControl",0x00010003,0
    HKLM,"SYSTEM\CurrentControlSet\Services\wdfldr8","Group",0x00000000,"System Reserved"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdfldr8","ImagePath",0x00020000,"\SystemRoot\System32\drivers\wdfldr.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdfldr8","Start",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\wdfldr8","Tag",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\wdfldr8","Type",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01_w8","ErrorControl",0x00010003,0
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01_w8","Group",0x00000000,"System Reserved"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01_w8","ImagePath",0x00020000,"\SystemRoot\System32\drivers\wdf01_w8.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01_w8","Start",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01_w8","Tag",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01_w8","Type",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","ErrorControl",0x00010003,0
    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","Group",0x00000000,"Boot Bus Extender"
    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","ImagePath",0x00020000,"\SystemRoot\System32\drivers\ucx01000.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","Start",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","Tag",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","Type",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","ErrorControl",0x00010003,0
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Group",0x00000000,"Boot Bus Extender"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","ImagePath",0x00020000,"\SystemRoot\System32\drivers\usbxhci.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Start",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Tag",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Type",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","ErrorControl",0x00010003,0
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Group",0x00000000,"Boot Bus Extender"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","ImagePath",0x00020000,"\SystemRoot\System32\drivers\usbhub3.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Start",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Tag",0x00010001,1
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Type",0x00010001,1

all the necessary files are in c:\windows\system32\drivers
on restart i check in regedit
in HKLM\SYSTEM\CurrentControlSet\Services\usbxhci under Enum I see INITSTARTFAILED
in HKLM\SYSTEM\CurrentControlSet\Services\ucx01000 has no enumeration
in HKLM\SYSTEM\CurrentControlSet\Services\usbhub3 has no enumeration
in HKLM\SYSTEM\CurrentControlSet\Services\wdfldr8 under Enum I see count 1
in HKLM\SYSTEM\CurrentControlSet\Services\wdf01_w8 under Enum I see count 1
any ideas?

#4493

diderius6

I just installed via the original english setup CD with mod from ⇗ @daniel_k XP SP3.
The very last version of acpi.sys vers.5048 does NOT work.
Only the very last version from acpi.sys from outer space )
helps.
All USB works from the beginning, meaning you have USB mouse!
Also the Asmedia ports have now the nice USB3 driver from ⇗ @Mov AX, 0xDEAD .
During make of this CD crazy things happen:
First I use Nlite. Even I make a binary check between 2 CDs and they are 100% identic(!!!)
the CD build with Nlite fails with error "UCX01000.SYS cant be found". This means, Nlite makes an error in the structure of the *.iso, brrr.. From this moment I use only the original *.iso file and work on this file direct with Ultra Iso.
And also very important is to use an original CD. When you use a CD with update package,
the warning about not signed drivers is not shown and so it fails. I think, this can be overcome on CD,
with a setup answer file, always to answer the question for to allow unsigned drivers with "YES",
Dietmar
PS: Thank you soso much ⇗ @daniel_k !!!
⇗

#4494 | Mov AX, 0xDEAD | To auto-install required usbd.sys(usbstor need it) add little magic to USBXHCI.inf: [GenericHub.Install.NT] ... Include=usbport.inf Needs=ROOTHUB.Dev.NT

#4495

skullteria

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4491

> > Zitat von ⇗ skullteria im Beitrag ¶ #4490

> > can you made this port for x64?

> No, x64 for me is not funny as x32, i dont plan do anything for these OSes

Well, you can make as favor, because i want integrate on Shorthorn Project Native driver.

#4496

Mov AX, 0xDEAD

> Zitat von ⇗ skullteria im Beitrag ¶ #4495

> Well, you can make as favor, because i want integrate on Shorthorn Project Native driver.

Hi skullteria
x64 is not important for me, so again No
You can backport yourself most drivers from win7/8/10 to xp/2003 if you know 386/x64 asm well, some times this is hard job, but most time it's boring job
You need replace missing import from *.sys files to selfmade equvalents, usualy replacing is easy if function is not important :

    xor eax, eax
    ret 4/8/10/...

Sometimes you will need more smart replace like IoConnectinterruptEx()->IoConnectinterrupt()
Not all drivers will works after, because new kernels contain new logic/frameworks/size of structs/enums/etc

#4497 | canonkong | ⇗ @Mov AX, 0xDEAD What about the USB ,ACPI, VGA drivers from win8.1/10 to WIN7?

#4498

diderius6

I do more tests with the nice setup CD for XP SP3 from ⇗ @daniel_k with the fantastic USB3 driver from ⇗ @Mov AX, 0xDEAD .
Whole install works for me only with the acpi.sys from outer space ). I use normal CD disk (best) and also USB install via firadisk.
The results where the same.
But now, when all is ready, I can also use the acpi.sys vers. 5048 (very last version).
On this board I build my very first working acpi.sys driver in December 2018.
This acpi.sys driver (only at 3 places changed against original) gives now BSOD 0x7B.
And I cant do USB boot with this installation on the same board. May be this is because of the changed iastor.sys driver
Dietmar
EDIT: I try the Setup CD on the crazy AMD x570 board. But only the USB devices are shown as bootable device.
So for AMD only the STORAHCI driver works.

#4499 | infuscomus | ⇗ @diderius6 did you try daniel_k's modded AMD 1.2.1.402 driver?
#4500 | diderius6 | ⇗ @infuscomus Is this modded AMD 1.2.1.402 for harddisk or for USB Dietmar PS: I do not find this driver.

## Page 301

#4501 | infuscomus | ⇗ @diderius6 it's an AHCI driver - I'll PM you

#4502

diderius6

With help from ⇗ @daniel_k I build a new generic Setup CD for XP SP3.
I have full USB from the beginning, thanks to nice driver from ⇗ @Mov AX, 0xDEAD .
This time I copy by hand file by file direct to the *.iso via Ultra Iso.
Now it uses the STORAHCI driver from ⇗ @skullteria which is the only harddisk sata driver,
that works on every motherboard, AMD or Intel.
Now I am just installing, until now everything is ok
Dietmar
PS: This is onyl one step away from a brandnew, really generic XP SP3, also with USB3 boot.
From feeling and testing the new installation I would say: This Setup CD is best of all, what we have ever seen for XP SP3.
1. Asrock Fatal1ty Z370 Gaming K6 (Intel) stable, fast, everything works at once.
2. ASUS Prime X570-PRO (AMD) fails install BSOD 0x00000096, when you use the installation from 1, now all(!) USB ports work.
This stop error 0x00000096 is caused by incompatibility of any of the hardware devices.
INVALID_WORK_QUEUE_ITEM
This means for a future generic Setup of XP SP3, that we need to find a mechanism, to do Setup only with the most necessary drivers. An other way would be, to integrate more drivers in the Setup CD. This error 0x96 happens, when a driver was first
recogniced, then deleted and then again deleted, because wrong recogniced.

#4503 | Outbreaker | ⇗ @diderius6 What entries did you use for the Generic USB 3.0 driver in the file DOSNET.INF, TXTSETUP.SIF and SETUPREG.HIV?
#4504 | diderius6 | ⇗ @Outbreaker I am not good in building setup CDs. Until yesterday I believe in Nlite, now not. So, you should ask ⇗ @daniel_k via message or ⇗ @infuscomus Dietmar
#4505 | Outbreaker | ⇗ @diderius6 Ahh okay, I thought you figured out how to use this USB 3.0 driver in the Windows XP Blue Text mode setup.

#4506

skullteria

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4496

> > Zitat von ⇗ skullteria im Beitrag ¶ #4495

> > Well, you can make as favor, because i want integrate on Shorthorn Project Native driver.

> Hi skullteria
> x64 is not important for me, so again No
> You can backport yourself most drivers from win7/8/10 to xp/2003 if you know 386/x64 asm well, some times this is hard job, but most time it's boring job
> You need replace missing import from *.sys files to selfmade equvalents, usualy replacing is easy if function is not important :

>     xor eax, eax
>     ret 4/8/10/...

> Sometimes you will need more smart replace like IoConnectinterruptEx()->IoConnectinterrupt()
> Not all drivers will works after, because new kernels contain new logic/frameworks/size of structs/enums/etc

OK! I will get my way, how ever

#4507

Outbreaker

⇗ @Mov AX, 0xDEAD and Others
How would you do this to get this new USB 3.0 driver to work on the Text mode setup and GUI mode Setup?

    <- "\i386\DOSNET.INF" File Entries ->

    [Directories]
    d1212 = "\i386\USB30DRV"

    [OptionalSrcDirs]
    USB30DRV

    [FloppyFiles.2]
    d1,usbxhci.sys
    d1,ucx01000.sys
    d1,usbhub3.sys
    d1,WDF01_W8.sys
    d1,usbd_w8.sys
    d1,WppRecor.sys
    d1,WdfLdr8.sy

    [Files]
    d1212,usbxhci.inf
    d1212,usbxhci.sys
    d1212,ucx01000.sys
    d1212,usbhub3.sys
    d1212,WDF01_W8.sys
    d1212,usbd_w8.sys
    d1212,WppRecor.sys
    d1212,WdfLdr8.sys

    <- "\i386\TXTSETUP.SIF" File Entries ->

    [SourceDisksNames.x86]
    "1212 = %%cdname%%,%%cdtagfilei%%,,"\i386\USB30DRV"

    [WinntDirectories]
    1212 = USB30DRV

    [SourceDisksFiles.x86]
    usbxhci.sys = 1,,,,,,4_,4,1,,,1,4
    ucx01000.sys = 1,,,,,,4_,4,1,,,1,4
    usbhub3.sys = 1,,,,,,4_,4,1,,,1,4
    WDF01_W8.sys = 1,,,,,,4_,4,1,,,1,4
    usbd_w8.sys = 1,,,,,,4_,4,1,,,1,4
    WppRecor.sys = 1,,,,,,4_,4,1,,,1,4
    WdfLdr8.sys = 1,,,,,,4_,4,1,,,1,4
    usbxhci.inf = 1212,,,,,,,1212,0,0
    usbxhci.sys = 1212,,,,,,,1212,0,0
    ucx01000.sys = 1212,,,,,,,1212,0,0
    usbhub3.sys = 1212,,,,,,,1212,0,0
    WDF01_W8.sys = 1212,,,,,,,1212,0,0
    usbd_w8.sys = 1212,,,,,,,1212,0,0
    WppRecor.sys = 1212,,,,,,,1212,0,0
    WdfLdr8.sys = 1212,,,,,,,1212,0,0

    [HardwareIdsDatabase]
    PCI\CC_0C0330 = "usbxhci"
    USB\ROOT_HUB30 = "usbhub3"

    [SCSI.Load]
    usbxhci  = usbxhci.sys,4
    usbhub3  = usbhub3.sys,4

    [BusExtenders.Load]
    WDF01_W8 = WDF01_W8.sys
    WdfLdr8  = WdfLdr8.sys

    [InputDevicesSupport.Load]
    usbxhci  = usbxhci.sys
    ucx01000 = ucx01000.sys
    usbhub3  = usbhub3.sys
    usbd_w8  = usbd_w8.sys
    WppRecor = WppRecor.sys

    [files.usbxhci]
    hid.dll,2
    hidclass.sys,4
    hidparse.sys,4
    usbd.sys,4
    usbport.sys,4
    usbxhci.sys,4
    ucx01000.sys,4
    WDF01_W8.sys,4
    usbd_w8.sys,4
    WppRecor.sys,4
    WdfLdr8.sys,4

    [files.ucx01000]
    ucx01000.sys,4

    [files.usbhub3]
    usbhub3.sys,4

    [files.WDF01_W8]
    WDF01_W8.sys,4

    [files.usbd_w8]
    usbd_w8.sys,4

    [files.WppRecor]
    WppRecor.sys,4

    [files.WdfLdr8]
    WdfLdr8.sys,4

    [FileFlags]
    usbxhci.sys =16
    ucx01000.sys =16
    usbhub3.sys =16
    WDF01_W8.sys =16
    usbd_w8.sys =16
    WppRecor.sys =16
    WdfLdr8.sys =16

    [InputDevicesSupport]
    usbxhci  = "USB 3.0 Host Controller",files.usbxhci,usbxhci
    ucx01000 = "USB Controller Extension",files.ucx01000,ucx01000
    usbhub3  = "USB 3.0 Hub Driver",files.usbhub3,usbhub3
    usbd_w8  = "Universal Serial Bus Driver",files.usbd_w8,usbd_w8
    WppRecor = "WPP Trace Recorder",files.WppRecor,WppRecor

    [SCSI]
    usbxhci  = "USB 3.0 Host Controller"
    ucx01000 = "USB Controller Extension"
    usbhub3  = "USB 3.0 Host Controller"
    usbd_w8  = "Universal Serial Bus Driver"
    WppRecor = "WPP Trace Recorder"

    [BusExtenders]
    WDF01_W8 = "Kernel Mode Driver Framework Runtime",files.WDF01_W8,WDF01_W8
    WppRecor = "WPP Trace Recorder",files.WppRecor,WppRecor
    WdfLdr8  = "Kernel Mode Driver Framework Loader",files.WdfLdr8,WdfLdr8

    <- "\i386\SETUPREG.HIV" File Entries ->

    ControlSet001\Services\usbxhci", "group", 0x00000000, "Input Device Support"
    ControlSet001\Services\usbxhci", "tag", 0x00010001, "4"
    ControlSet001\Services\ucx01000", "group", 0x00000000, "Input Device Support"
    ControlSet001\Services\ucx01000", "tag", 0x00010001, "5"
    ControlSet001\Services\usbhub3", "group", 0x00000000, "Input Device Support"
    ControlSet001\Services\usbhub3", "tag", 0x00010001, "5"
    ControlSet001\Services\WDF01_W8", "group", 0x00000000, "WdfLoadGroup"
    ControlSet001\Services\WDF01_W8", "tag", 0x00010001, "2"
    ControlSet001\Services\WppRecor", "group", 0x00000000, "Input Device Support"
    ControlSet001\Services\WppRecor", "tag", 0x00010001, "5"
    ControlSet001\Services\WdfLdr8", "group", 0x00000000 "WdfLoadGroup"
    ControlSet001\Services\WdfLdr8", "tag", 0x00010001, "1"

#4508

Mov AX, 0xDEAD

Hi,
I've got alpha/not_tested version of USB Attached SCSI (UAS) Mass Storage driver as companion to win8 usb 3.0 driver (also storport.sys backported from win8.0):
- speed is increased 170Mb/s -> 250Mb/s on external usb ssd drive
- yet does not work on Windows Setup + storahci.sys
- bsod at shutdown, in progress...

#4509 | canonkong | @Mov AX, 0xDEAD Its possible to make the ACPI from win8 to Xp or win7? Like some new platforms dont have fully support ACPI and will A5 BSOD, I tried to do that but fail.

#4510

Mov AX, 0xDEAD

> Zitat von ⇗ canonkong im Beitrag ¶ #4509

> @Mov AX, 0xDEAD
> Its possible to make the ACPI from win8 to Xp or win7?

i think possible fix missing imports in acpi.sys, but this "Frankenstein" will be work ? - nobody knows.
acpi.sys is not "device" driver, it is companion to kernel/pci/hal/???

#4511

diderius6

acpi.sys from Win7 will be not enough.
I have a crazy notebook,
where the first OS you can install with full acpi support is win8,
even I tried a lot
Dietmar
PS: Other option is to change there nearly whole Bios to an XP friendly version.
EDIT: I am going to write a Tutorial with the nice USB3 driver from @Mov AX, 0xDEAD for USB boot.
Oha, it is more difficult to make this generic, than I thought. But when you succeed it is stable!

#4512 | Dibya | best option is to patch existing ACPI driver of XP to detect ACPI 2.0 . I found ACPI sys from longhorn / Vista Beta is making certain IRQL function to fail in XP . ⇗ https://msfn.org/board/topic/176480-2-ti...comment-1135845 Actually i found disk.sys is responsible for GPT long back
#4513 | Outbreaker | ⇗ @Mov AX, 0xDEAD I got the USB boot fully working, but the USB 3.0 driver files will no play nicely with the "Joliet" file system format and will lead to a file not found error.
#4514 | infuscomus | ⇗ @Outbreaker you also mentioned there is a conflict with the kmdf files being named wdfldr8.sys and wdf01_w8.sys? ⇗ @Mov AX, 0xDEAD
#4515 | Outbreaker | ⇗ @infuscomus ⇗ @Mov AX, 0xDEAD Yes the question is, if a Windows XP ISO has already the Driver Frameworks 1.9 integrated should we overwrite the exiting "wdf01000.sys" and "wdfldr.sys" file with the USB 3.0 driver files "wdfldr8.sys" and "wdf01_w8.sys" or integrated them both together.

## Page 302

#4516

Mov AX, 0xDEAD

> Zitat von ⇗ Outbreaker im Beitrag ¶ #4513

> @Mov AX, 0xDEAD
> I got the USB boot fully working, but the USB 3.0 driver files will no play nicely with the "Joliet" file system format and will lead to a file not found error.

you can rename files as you wish, even to pure "DOS 8.3 ALL_IN_CAPS", but remember about cross links, if you change WppRecorder.sys->WPPREC.SYS you need update remain *.sys because name of this file hardcoded inside *.sys (also dont forget about checksum!)

#4517 | infuscomus | ⇗ @Mov AX, 0xDEAD would updating the import table to point to wpprecor.sys be enough? or would more edits be needed?

#4518

Mov AX, 0xDEAD

> Zitat von ⇗ Outbreaker im Beitrag ¶ #4515

> Yes the question is, if a Windows XP ISO has already the Driver Frameworks 1.9 integrated should we overwrite the exiting "wdf01000.sys" and "wdfldr.sys" file with the USB 3.0 wdfldr8.sys and wdf01_w8.sys file or integrated them both together.

I prefer separate ways, so backported "beta" wdf 1.11 will never interference with "original bugfree" wdf 1.7/1.9
All existing XP vendor drivers will still use wdf 1.7/1.9, only usb 3.0 driver will use wdf 1.11
I saw another version of driver, in it wdf 1.11 become full replacement of wdf 1.x

#4519

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4517

> @Mov AX, 0xDEAD
> would updating the import table to point to wpprecor.sys be enough? or would more edits be needed?

yes, this is enough, only import name matter

#4520 | Outbreaker | ⇗ @Mov AX, 0xDEAD Can you send me a USB 3.0 driver version with the file name "wdfldr8.sys", "wdf01_w8.sys" and "wpprecor.sys" for integration disc? Then i can test the "Joliet" file system format and also the boot compatibility with the Driver Frameworks 1.9.

#4521

Mov AX, 0xDEAD

> Zitat von ⇗ Outbreaker im Beitrag ¶ #4520

> @Mov AX, 0xDEAD
> Can you send me a USB 3.0 driver version with the file name "wdfldr8.sys", "wdf01_w8.sys" and "wpprecor.sys"? Then i can test the "Joliet" file system format and also the boot compatibility with Driver Frameworks 1.9.

I can't, do it yourself, it's not hard, you need any hex editor and any checksum fixer. Or ask someone other

#4522 | Outbreaker | ⇗ @Mov AX, 0xDEAD I can do it myself, but i think it wouldn't be a good idea to have X different versions flying around the internet. I have even 2 different .inf files and don't even know which one is the original.

#4523

diderius6

Here are the minimal settings for USB3 boot with the nice driver from ⇗ @Mov AX, 0xDEAD .
I prepared them from an brandnew XP SP3 install.
My problem in this is, I do not know, why they work and a brandnew installation, without this prepare, alone not
Dietmar
PS: Now I think, there is a hierarchy in XP: ENUM comes before CriticalDeviceDatabase.
diderius6 has attached files to this post

- ⇗ MoveUsb3boot.rar

#4524 | canonkong | ⇗ @Mov AX, 0xDEAD I think I had not fully fix the missing imports in acpi.sys, so it can not work. Maybe we can have a try and test.

#4525

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4510

> acpi.sys is not "device" driver, it is companion to kernel/pci/hal/???

⇗ @Mov AX, 0xDEAD ...you may know this already but from my understanding acpi.sys is the driver above PCI.sys. In the USB chain, PCI.sys is above XHCI.sys, and the hub driver.
ACPI.sys is between the system and the BIOS and it controls power management and Plug&Play device enumeration at boot.
⇗ https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/acpi-driver
Also, see this page on debugging ACPI:
⇗ https://docs.microsoft.com/en-ca/windows-hardware/drivers/debugger/introduction-to-the-amli-debugger

#4526

gordo999

> Zitat von ⇗ canonkong im Beitrag ¶ #4524

> @Mov AX, 0xDEAD
> I think I had not fully fix the missing imports in acpi.sys, so it can not work. Maybe we can have a try and test.

⇗ @canonkong ...I am trying to set up a serial kernel mode debugging session between a W7 host and XP as target on COM2. I'd like to trace the code in acpi.sys, and other drivers, but right now i cannot get a serial port connection from host to target.
I have verified that the serial ports are talking to each other both ways using hyperterminal and a serial communication application. I suspect there could be a problem with kdcom.dll which is loaded early at boot time to enable remote serial communication. It could be that a mod to hal or acpi.sys is blocking the communication between kdcom.dll and the system.
I'm using a mobo with a B360 chipset and an i5-8400 processor.

#4527

Mov AX, 0xDEAD

> Zitat von ⇗ gordo999 im Beitrag ¶ #4525

> ACPI.sys is between the system and the BIOS and it controls power management and Plug&Play device enumeration at boot.

MS did not tell full true )
Even some requests to usb driver go through acpi.sys, is saw this in callstack, so acpi is more than seems at first sight.
In "noacpi" hal.dll exist another way to passing requests, but i never used it

#4528

Mov AX, 0xDEAD

> Zitat von ⇗ gordo999 im Beitrag ¶ #4526

> I am trying to set up a serial kernel mode debugging session between a W7 host and XP as target on COM2. I'd like to trace the code in acpi.sys, and other drivers, but right now i cannot get a serial port connection from host to target.

- W7 & XP is cross compatible for kernel debugging, i think problem with com cables/ports, even if you see repeating chars in hyperterminal, for kernel debugging need 100% quality connection
- Debugging with COM is Pain&Tears because incredible slow speed. COM is still good if you just want get crashdump. Comfortable debuging require much more speed connections

#4529

usa1ec

> Zitat

> Here are the minimal settings for USB3 boot with the nice driver .......

Where can I download the full version of this nice driver?
Please URL.

#4530

infuscomus

⇗ @Outbreaker ⇗ @diderius6
outbreaker, do you think you could make your integrator script make a live bootable USB install of XP?
by this I mean, install XP to a USB drive and not get a 7B BSOD later
diderius6 did manage to get it working - i think change the load order of usbstor.inf to boot bus extender?
some registry files here -
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (302)
P.S
I got a wdfldr.sys BSOD trying to make KMDF 1.9 and 1.11 coexist on an XP CD.
I'm not saying it's impossible, just challenging to get working.

## Page 303

#4531

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4527

> MS did not tell full true )Even some requests to usb driver go through acpi.sys, is saw this in callstack, so acpi is more than seems at first sight.

⇗ @Mov AX, 0xDEAD ...I agree. The USB call stack is: ACPI....PCI...XHCI....USBHUB....device.
Look at it from a hardware view. Each sleep state is controlled by a different voltage controller on the motherboard (mosfets). Each voltage control stage needs a signal from the operating system to tell it to turn off or turn on. ACPI sends control signals via Hal to each circuit or device that needs to 'sleep'. So ACPI takes sleep state signals from the operating system and passes them to the circuits and devices. Therefore, the acpi driver has to be located between the operating system and the hardware devices, including the processor, the busses, like PCI, clocks, etc.
ACPI also enumerates each device through the PCI driver during boot. It tells pci.sys to enumerate each tree on the PCI buss. In the ENUM registry key in HKLM\Services there is driver information for each device. If you use windbg and the .load usb3kd.dll extension using .load usb3kd.dll in Win 7, you can follow the USB 3 tree from the hub through to acpi. I have done this with USB 3 but I'm not sure how well it works in XP.
For USB 3:
⇗ https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usb-3-extensions
For USB 2:
⇗ https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usb-2-0-extensions
I use !devnode 0 1 and !devobj to trace through the tree. By entering the parent object it will take you to the next highest object in the tree and you should get to acpi.sys at the top.
You are from Tashkent. Do you speak Uzbek or Russian? I translated part of this message into Uzbek. Does that make sense?
Siz Toshkent shahridansiz. Siz o'zbek yoki rus tillarida gaplashasizmi? Men ushbu xabarning bir qismini o'zbek tiliga tarjima qildim. Bu mantiqiymi?
Unga apparat ko'rinishidan qarang. Har bir uyqu holati anakartdagi (mosfetlarda) boshqa kuchlanish boshqaruvchisi tomonidan boshqariladi. Kuchlanishni boshqarishning har bir bosqichida operatsion tizimdan uni o'chirish yoki yoqish kerakligi haqida signal kerak. ACPI "uyqu" ga muhtoj bo'lgan har bir kontaktlarga yoki qurilmaga nazorat signallarini Hal orqali yuboradi. Shunday qilib ACPI operatsion tizimdan uyqu holatidagi signallarni oladi va ularni kontaktlarning zanglashiga olib boradigan qurilmalar va qurilmalarga uzatadi. Shuning uchun, Acpi drayveri operatsion tizim va qo'shimcha qurilmalar, shu jumladan PCI, soatlar va hk kabi protsessor, avtobuslar o'rtasida joylashgan bo'lishi kerak.
ACPI shuningdek, yuklash paytida PCI drayveri orqali har bir qurilmani sanab o'tadi. Bu PCI bussidagi har bir daraxtni sanashni pci.sys-ga aytadi. HKLM \ Services-dagi ENUM registri kalitida har bir qurilma uchun drayver haqida ma'lumot mavjud. Agar siz Win 7-da .bb usb3kd.dll-dan foydalanib windbg va .load usb3kd.dll kengaytmasidan foydalansangiz, siz USB 3 daraxtidan uyadan acpi-ga o'tishingiz mumkin. Men buni USB 3 bilan bajardim, lekin XP-da u qanchalik yaxshi ishlashiga amin emasman.

#4532 | dencorso | <off topic begins> ⇗ @gordo999 : I sure don't speak Uzbek, but if you translated English to Uzbek using any of (google, bing!, yandex), then probably the translation is no good, and I don't know of a machine translator able to do it decently. Now, to translate English to Russian or, even better, Russian to English, there's just one and only machine translator: DeepL. It's, hands down, the best one available for free, nowadays. And no, I'm not affiliated with it in any way, I just do hate bad machine translation with a passion! My native language, BTW, is Portuguese, if that info can be relevant in any way. Cheers! <off topic ends>

#4533

gordo999

> Zitat von ⇗ dencorso im Beitrag ¶ #4532

> <off topic begins> @gordo999 : I sure don't speak Uzbek, but if you translated English to Uzbek using any of (google, bing!, yandex), then probably the translation is no good, and I don't know of a machine translator able to do it decently.

⇗ @dencorso ...thanks for tip. The newer Google translation is pretty good for Chinese and some other languages if you translate, then translate back to English to look for errors. I wrote a lengthy email to a Chinese manufacturer and the woman on the other end said the translation was easy to read.
I feel badly for people on this blog who don't speak English as a first language. It's tough to communicate and I thought I'd try translating my English into their language to see how well it works. I don't know if ⇗ @Mov AX, 0xDEAD speaks Russian or Uzbek but I was able to communicate on a Russian board about hard drives using Google. The hard part is trying to learn the slang. For example, some Russians call a hard drive a 'screw' and a disk platter, a 'pancake'. So, I think a trick in translation may be to keep the English really simple with no slang.

#4534 | infuscomus | ⇗ @Mov AX, 0xDEAD do you think it might be possible to backport ntoskrnl/hal of windows 8 or 10 to work for XP? some functions were removed since XP, would it just be a matter of re-adding them back in?

#4535

diderius6

After crazy search for 3 days I found the reason for BSOD 0x7B for USB boot of the nice driver form ⇗ @Mov AX, 0xDEAD .
It is the sequence of those drivers, which was loaded first, second, third and so on.
XP SP3 itself sets UCX01000 to a later place, because it knows nothing about those drivers.
The result is BSOD 0x7B.
The working sequence is
1.) WDF01_W8
2.) USBSTOR
3.) UCX01000
4.) USBXHCI
5.) USBHUB3
Dietmar

#4536 | infuscomus | ⇗ @diderius6 how do you set the boot order so it works?

#4537

diderius6

⇗ @infuscomus
There are a lot of possibilities as long as the load order for the drivers above is kept.
I just test with success in its *.inf files for USB boot for XP SP3
1.) WDF01_W8 LoadOrderGroup = System Reserved StartType = 0
2.) USBSTOR LoadOrderGroup = System Reserved StartType = 0
3.) UCX01000 LoadOrderGroup = Boot Bus Extender StartType = 0
4.) USBXHCI LoadOrderGroup = Base StartType = 0
5.) USBHUB3 LoadOrderGroup = Base StartType = 0
Dietmar
PS: The StartType has to be always = 0 or you get BSOD 0x7B,
because then the driver for USB boot is not loaded at boottime.

#4538 | infuscomus | ⇗ @diderius6 thanks, I'll let outbreaker know so he can add this to his integrator script.

#4539

diderius6

I just test XPSP3 USB3 boot with the nice driver from ⇗ @Mov AX, 0xDEAD (with my settings above in each *.inf )
for the AMD board Fatal1ty AB350 Gaming K4 with Ryzen 3700X with 16 cores. Only with this board from AMD I'm happy.
Waaoh, boots at once. It is stable and fast
Dietmar
PS: No extra entries needed. Just use the two *.inf files here for generic USB XPSP3 boot on any mainboard.
⇗
diderius6 has attached files to this post

- ⇗ GenericUSBbootXPSP3.rar

#4540

diderius6

Waaooh, with this settings in GenericUSBbootXPSP3
even the most crazy board ASUS PRIME X570-PRO can now boot from USB
and all(!) USB ports work there at once. Until now, I never succeed for USB boot on this board.
And before, the USB ports there are unstable as much as possible on any OS. In Win10, this unstability remains..
Dietmar
PS: I hope, that soon ) we all have this nice driver from ⇗ @Mov AX, 0xDEAD .
This will give a boost for XP as much as this is possible.
EDIT: EVGA z390 dark board works also for USB boot of XP SP3 with this generic settings,
also on the Asmedia USB ports.
Asus Apex X works, also on Asmedia USB ports.
And USB boot works on each slot of the nice GA-H110M-S2H board:)).

#4541

canonkong

⇗ @Mov AX, 0xDEAD ⇗ @diderius6
I tried to make the USB from server2012(6.2.9200) to Xp/vista/win7. And the XHCI/HUB driver work very well on win7 with my Ryzen CPU & APU, X370/B450/X570 also work good.
But the UASP can not work. Even I found out all the KeInitializeSpinLock and fix them, but it is still Code 39 erro. What do I need to fix?
Thanks.

#4542

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4534

> @Mov AX, 0xDEAD
> do you think it might be possible to backport ntoskrnl/hal of windows 8 or 10 to work for XP?
> some functions were removed since XP, would it just be a matter of re-adding them back in?

i've experimented with injecting win7 kernel+hal+acpi to winxp, kernel started ok, but there is problems when kernel start requesting external *.sys, for example i got BSODs in pci.sys
offtop: ⇗ @gordo999, i can speak in russian only

#4543

Mov AX, 0xDEAD

> Zitat von ⇗ canonkong im Beitrag ¶ #4541

> @Mov AX, 0xDEAD @diderius6
> I tried to make the USB from server2012(6.2.9200) to Xp/vista/win7. And the XHCI/HUB driver work very well on win7 with my Ryzen CPU & APU, X370/B450/X570 also work good. But the UASP can not work

win8's UASP require win8's storport.sys or you need to patch UASP to make it compatible with previous storport.sys

#4544 | infuscomus | ⇗ @Mov AX, 0xDEAD if you still have that kernel, do you mind if I take a look at it?

#4545

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4528

> - need 100% quality connection - Debugging with COM require much more speed connections

⇗ @Mov AX, 0xDEAD ...thanks for response. I had kernel debugging running well with COM between a W7 host and both W7 and W10 as targets. It was fast enough for me at 115200 baud. My problem was buggy behavior with windbg. Sometimes the registers would not work correctly and I could not get certain extensions to load.
Right now, using a serial comm app I can clearly see the host sending data. It sends 00 00 00 00 00 69 69 69 69 69 etc, where the 0x69 is the ASCII letter i. It's waiting for a response. I need to find a way to send it a response so I can follow it from the serial comm app to see where it is being blocked.
At the moment, I need to fix a problem in XP debug mode. It can boot to the desktop and the mouse works for a while then the mouse and keyboard freeze. I'm wondering if it might be a problem between USB 3 and debug mode. In safe mode, there is no problem. Could you, or anyone, check to see if debug mode on XP runs to the desktop without freezing?
I have read that an exception can cause debug mode to freeze if the exception occurs before the host can connect.

## Page 304

#4546

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4542

> i can speak in russian only

⇗ @Mov AX, 0xDEAD ....I can understand your posts. I thought it might be helpful to you when discussing details if we tried to reply in Russian. If you need to reply in detail you could post details in Russian with a short English reply, as you do now. Maybe that is too complicated.
Я могу понять ваши сообщения. Я подумал, что вам будет полезно обсудить детали, если мы попытаемся ответить на русском языке. Если вам нужно ответить подробно, вы можете опубликовать информацию на русском языке с коротким ответом на английском языке, как вы делаете сейчас. Может быть, это слишком сложно.
BTW...this applies to anyone who speaks a language other than English. I speak Scottish but I don't mind making an effort to communicate in a different language.

#4547

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4535

> It is the sequence of those drivers

⇗ @diderius6 ....how do you determine the loading sequence? Is it done using the Start parameter as in:
ErrorControl
This is used if the service fails to startup upon boot.
Value Meaning
0x00 If this driver can't be loaded or started ignore the problem and display no error
0x01 If the driver fails produce a warning but let bootup continue
0x02 Panic. If the current config is last known good continue, if not switch to last known good
0x03 Record the current startup as a failure. If this is last known good run
diagnostic, if not switch to last known good and reboot
Start
This defines when in the boot sequence the service should be started. You can also set these by using the Services control panel applet.
Value Start Type Meaning
0x00 Boot The kernel loaded will load this driver first as its needed to use the boot volume device
0x01 System This is loaded by the I/O subsystem
0x02 Autoload The service is always loaded and run
0x03 Manual This service does not start automatically and must be manually started by the user
0x04 Disabled The service is disabled and should not be started
Type
This defines the kind of service or driver. They are loaded in the following order down the list.
Value Meaning
0x01 Kernel-mode device driver
0x02 Kernel-mode device driver that implements the file system
0x04 Information used by the Network Adapter
0x10 A Win32 service that should be run as a stand-alone process
0x20 A Win32 service that can share address space with other services of the same type

#4548

diderius6

⇗ @gordo999
This list is not complete. The entry TAG is missed there.
The higher the TAG number, the later the driver is loaded.
This is true in the meaning of the words, as I noticed.
I do not have any good information about the LoadOrderGroup.
Any way, System Reserved is loaded first of all and Base as a normal driver
Dietmar
PS: There are much more ways possible in XP: In CriticalDeviceDatabase it is enough to give the GUIDE number
and the name of the service. No special device needs to be declared there.
Other is in ENUM. There you have to give also the exact name of a special device, for which the driver is.
Before I thought that CriticalDeviceDatabase is the very first place, where XP looks for drivers.
But now I think it is Enum. How I find the load order? I have experience with different LoadOrderGroup.
But this time I noticed, that it is not enough. You also have to look at the TAG entry. 3 days work, brr..

#4549 | infuscomus | ⇗ @diderius6 sent you a PM I modded the script, can you see if this fixes the 7B BSOD with USB boot?
#4550 | canonkong | ⇗ @Mov AX, 0xDEAD Both storport.sys and uasport.sys code 39 erro, I thnk only find out KeInitializeSpinLock fix them is not enough. Can you share your modified storport.sys and uasport.sys for win7 or share some experiences about that? Thanks

#4551

YuriyCN

> Zitat von ⇗ gordo999 im Beitrag ¶ #4546

> Я могу понять ваши сообщения. Я подумал, что вам будет полезно обсудить детали, если мы попытаемся ответить на русском языке. Если вам нужно ответить подробно, вы можете опубликовать информацию на русском языке с коротким ответом на английском языке, как вы делаете сейчас. Может быть, это слишком сложно.
> BTW...this applies to anyone who speaks a language other than English. I speak Scottish but I don't mind making an effort to communicate in a different language.

Давно пора уже перейти на русский. Здесь половина специалистов общается на русском, но из уважения к остальным, приходится писать на английском. На русском будет проще и информативнее.

#4552 | diderius6 | ⇗ @YuriyCN Да, но не все понимают русский язык. Я могу читать и говорить по-русски :)), Дитмар

#4553

YuriyCN

> Zitat von ⇗ diderius6 im Beitrag ¶ #4552

> @YuriyCN
> Я могу читать и говорить по-русски :)),
> Дитмар

Отлично! Вообще никаких проблем! )))

#4554

Dibya

> Zitat von ⇗ infuscomus im Beitrag ¶ #4534

> @Mov AX, 0xDEAD
> do you think it might be possible to backport ntoskrnl/hal of windows 8 or 10 to work for XP?
> some functions were removed since XP, would it just be a matter of re-adding them back in?

Its impossible , ntoskrnl and hal are linked with ntdll and win32k.sys moreover Windows 8 kernel doesnt have same memory addresses as XP . Moreover Windows 8 kernel will break functioning of OpenGL ICD in XP .

#4555

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4552

> ⇗ @YuriyCN
> Да, но не все понимают русский язык.
> Я могу читать и говорить по-русски :)),
> Дитмар

⇗ @diderius6 ⇗ @YuriyCN ...Я могу сидеть Да и Нет на русском и шотландском. :-)

#4556

Mov AX, 0xDEAD

> Zitat von ⇗ gordo999 im Beitrag ¶ #4545

> At the moment, I need to fix a problem in XP debug mode. It can boot to the desktop and the mouse works for a while then the mouse and keyboard freeze. I'm wondering if it might be a problem between USB 3 and debug mode. In safe mode, there is no problem. Could you, or anyone, check to see if debug mode on XP runs to the desktop without freezing?

I saw only mouse lags with COM debugging, but never faced with total freezes with any usb3 driver, so probably you have some unique "freeze" issue

#4557

Mov AX, 0xDEAD

> Zitat von ⇗ canonkong im Beitrag ¶ #4550

> @Mov AX, 0xDEAD
> Both storport.sys and uasport.sys code 39 erro, I thnk only find out KeInitializeSpinLock fix them is not enough.
> Can you share your modified storport.sys and uasport.sys for win7 or share some experiences about that?

I have notfinished/unstable backport win8's storport.sys & uasport.sys for Windows XP :
- uasport works, but there is issue with reboot&shutdown inside storport, first it was BSOD 9F about missing PoStartNextPowerIrp calls, after fixing i get deadlock with "power irqs"
- original Win8 storahci.sys also works (on VM and real hardware )
EDIT: deadlock fixed, uasport.sys&storport.sys finished

#4558

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4548

> But now I think it is Enum.

⇗ @diderius6 ...thanks for info. I think enum is used during the boot stage when ACPI.sys instructs the Plug'n Play Manager to instruct pci.sys to enumerate devices attached to the PCI buss. Each pci buss has a node to which a device tree is attached, leading to a device or some kind of code object.
There are two main objects in a device stack or tree, the PDO and the FDO. In a USB tree, the pci driver creates a PDO (physical device object) which is nothing more than a code structure that holds information about the next object in the stack.
⇗ https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/device-nodes-and-device-stacks
"During startup, the PnP manager asks the driver for each bus to enumerate child devices that are connected to the bus. For example, the PnP manager asks the PCI bus driver (Pci.sys) to enumerate the devices that are connected to the PCI bus. In response to this request, Pci.sys creates a device object for each device that is connected to the PCI bus. Each of these device objects is called a physical device object (PDO)".
I mention this because you can trace the PDO (Physical Device Objects) and FDO (Functional Device Objects) 'structures" in windbg and follow the driver stack to the root. Note in one of the drawings in the article that acpi.sys is the root for pci.sys. I have noticed that while tracing through the USB stack that acpi.sys is always the the root driver for everything else.
Here's the key for the ENUM section in the registry:
"The PnP manager associates a device node with each newly created PDO and looks in the registry to determine which drivers need to be part of the device stack for the node".
That means, for each device node (USB, storage, sound cards, etc.), the PCI buss must create a PDO. For the next device object down the chain, the PDO creates and FDO for the object. That object then creates another PDO for the next object, which creates an FDO for the next object. It should be noted that acpi.sys creates a PDO for PCI.SYS.
There is a hyperlink for DEVICE OBJECT at the link above and if you follow that link it will show you the code structure for the device object. Using that, you should be able to trace into the driver code using windbg and get a lot of information that may tell you why a driver is not loading. I have not done that yet but I plant to.
The actual communication between devices is done with an IRP, which is really just another structure that transports data between the PDO and the FDO between device objects. If you watch this happening in windbg or Ollybdg, you can see memory sections being initialized with 00s then entire structures are moved/copied from one memory location to another.
Right now, I am trying to get a kernel debugging session going between a remote host computer and a target XP computer using a serial connection. Once that is established, you can trace through driver code and see what is actually happening. I've managed to trace into the Device Manager code related to 'Add New Hardware' and got into the code where it is reading the INF file. You should be able to catch the PnP manager reading the ENUM part of the registry.

#4559

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4556

> I saw only mouse lags with COM debugging, but never faced with total freezes with any usb3 driver, so probably you have some unique "freeze" issue

⇗ @Mov AX, 0xDEAD|p111729 ...I agree. It is freezing very late in the boot process at the desktop but not in Safe Mode. I am using the bootlogging in Process Monitor and another boot logger to see if I can identify the app that is causing the freeze.

#4560

YuriyCN

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4557

> - original Win8 storahci.sys also works (at least in VM on virtual sata controller, not tested on real hardware)
> I don't plan share it because it does not work well

Нужно учитывать криворукость пользователей тестирующих драйвера. Например, для успешной работы USB 3.0 (портированного с Win8) нужно выполнить одновременно 3 условия:
1) Выбрать правильный дистрибутив WinXP. Например я использую сборку с обновлениями по 2020 год - никаких проблем с портированным драйвером нет. Всё отлично работает! Но, если взять оригинал MSDN WinXP SP3 - то проблемы также есть. Видимо причина в каком-то измененном *.sys.
2) Обязательно использовать модифицированный ACPI.SYS (от 01.11.2019)
3) После установки драйвера, проверить чтобы оба компонента (xHCI контролле + Root Hub) были с установленного драйвера. Windows может заменить компонентом от другого драйвера, что вызовет проблемы.
Невыполнение любого условия, приводит к гарантированным глюкам. Выкладывайте ваш портированный SATA драйвер. Если он не убьёт файловую систему на HDD со всеми файлами - то готов его потестировать.

## Page 305

#4561 | canonkong | ⇗ @Mov AX, 0xDEAD Original Win8 storahci.sys also code 39 erro on real hardware. Although uasp does not work, but xhci and hub can work well. They work well on win7 system, which is better than the general USB driver modified by AMD 1.0.0.12. At least, they will not occasionally fail to recognize USB devices on DEV_15E1 DEV_15E0 like AMD 1.0.0.12.

#4562

Mov AX, 0xDEAD

Hi,
I fixed deadlock issue with backported Win8 UAS Mass Storage driver, there is two versions:
- uaspstor.sys for Win8's storport.sys v6.2.9200.16384, size(HW_INITIALIZATION_DATA) = 80h
- uaspstor.sys for Win2003's updated storport.sys v5.2.3790.4485 size(HW_INITIALIZATION_DATA) = 68h, SP2 version and older will not work
Deadlock fix implemented as "dirty" hack, at reboot & shutdown driver will not wait results from usbhub3 driver
For storahci.sys (and other drivers) deadlock fix not require, so uaspstor.sys linked to renamed storport.sys
PM if this backport is interesting to you
Existing patches:
1) ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (313)

#4563

Mov AX, 0xDEAD

> Zitat von ⇗ canonkong im Beitrag ¶ #4561

> @Mov AX, 0xDEAD
> Original Win8 storahci.sys also code 39 erro on real hardware.

Hi canonkong
Probable problem source:
storahci.sys compiled for win8 ddk storport framework, at time of start it fills HW_INITIALIZATION_DATA structure and transfers it to storport.
Only Win8' storport will return OK to Win8' storahci.sys, any previous version of storport will fail HW_INITIALIZATION_DATA checks and return error to driver => code 31,39 in DM
Skullteria version compiled for win7 ddk => compatible with win2003 storport.sys

#4564

ruthan

Just small discovery from - I had problem with NEC USB3 addon controller with Win10 and Z97 board - in installed lastest firmware tried zillion things.. but cca every 2nd boot it was not working - because i got message, that device not responded in desired time.. now i upgraded to Z390 same OS isntallation, drivers etc, only MB changed and its working everytime.
Some USB problems could be more that controller related, but there could be something with MB or chipset, i had on same MB - Asmedia - Internal and External and Intel controllers are never had same issue.

#4565

Mov AX, 0xDEAD

> Zitat von ⇗ ruthan im Beitrag ¶ #4564

> Just small discovery from - I had problem with NEC USB3 addon controller

My experience: usb3 hardware/design is low quality, i have VIA card with 3 damaged usb 3.0 ports + MB Intel with one damaged usb3 port + semi-burned external sata<->usb3 adapted + lenovo notebook with sometimes not being activated ports

#4566

ruthan

Otherwise i was searching for that "delta" patcher to enable distribute USB / System patches, without sharing whole modified files.
In theory, its should works same was as code diff. If you we will first check that everyone has right drivers and MS files (SP x and right CRC) to patch, you can compare original and modified files, create delta patch and distribute it freely and users can make patching.
I found so far 2 ways how to do it:
1) Xdelta-GUi - ⇗ https://github.com/Moodkiller/xdelta3-gui-2.0 its 64bit, but there is source - ⇗ http://xdelta.org/
2) bsdiff command if you like Linux.

#4567

diderius6

⇗ @infuscomus
I think, this will solve our problem how to install XP to any USB device.
It is from my past, but I cant remember it at all.
Little memory, that I sold an XP CD to a person in England in 2006,
just with this my own method
Dietmar
"The ngine.de tutorial is derived by Tubo from the original Dietmar's guide."
PS: One website for USB boot of XP survived 14 years:))
⇗ https://romardcajote.wordpress.com/windo...usb-stickdrive/
diderius6 has attached files to this post

- ⇗ XPSetupCDtoUSB.pdf

#4568

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4565

> ... semi-burned external sata

⇗ @Mov AX, 0xDEAD ...did you adjust it for maximum smoke?

#4569

gordo999

> Zitat von ⇗ gordo999 im Beitrag ¶ #4568

> [quote=Mov AX, 0xDEAD|p4565]
> ... semi-burned external sata

⇗ @Mov AX, 0xDEAD ...did you adjust it for maximum smoke? I blew up a motherboard once by putting a shorting clip on a fan header instead of the BIOS header. Could not see very well since it was dark inside the case but I sure heard it and smelled. Won't do that again.

#4570 | Outbreaker | ⇗ @diderius6 Nice one. Only the link in the PDF is dead/kaputt. And i think we could move the USBBOOT.INF entries into the HIVESYS.INF file or not.

#4571

diderius6

⇗ @Outbreaker
We can build a new USBBOOT.INF. To separate it, is much more easy.
⇗ @infuscomus sends me the one down here.
The problem, that start 0=>3 changes during install of XP is solved with it.
We need to think about, how to treat USBHUB3 and USBXHCI.
With WDF load they can stay with Group Base, but start=0.
I think, the lifting in the Tutorial should happen for them not at 2 places, I think only at one place.
Needs to be tested, if this one place is [BootBusExtenders] or [BootBusExtenders.Load]
Dietmar
PS: For me it is unclear, at which place you have to use
"Start",0x00010003,"0"
or
"Start",0x00010001,"0"
diderius6 has attached files to this post

- ⇗ USBBOOT.rar

#4572 | infuscomus | ⇗ @Outbreaker if you're still having trouble seeing the PDF DL here ⇗ https://ufile.io/upae1nwm

#4573

diderius6

This example from Microsoft for USB3 boot is a little bit strange, because with there own description there should be a 0x10 ??? May be this means: 0x4 for usb boot + 0x10 for USB3 = 0x14
Dietmar
Depending on the boot scenario, you can use the BootFlags registry value to control when the operating system should promote a driver's StartType value to 0x0 (SERVICE_BOOT_START). You can specify one or more (ORed) of the following numeric values, expressed as a hexadecimal value:
0x1 (CM_SERVICE_NETWORK_BOOT_LOAD) indicates the driver should be promoted if booting from the network.
0x2 (CM_SERVICE_VIRTUAL_DISK_BOOT_LOAD) indicates the driver should be promoted if booting from a VHD.
0x4 (CM_SERVICE_USB_DISK_BOOT_LOAD) indicates the driver should be promoted to if booting from a USB disk.
0x8 (CM_SERVICE_SD_DISK_BOOT_LOAD) indicates the driver should be promoted if booting from SD storage.
0x10 (CM_SERVICE_USB3_DISK_BOOT_LOAD) indicates the driver should be promoted if booting from a disk on a USB 3.0 controller.
0x20 (CM_SERVICE_MEASURED_BOOT_LOAD) indicates the driver should be promoted if booting while measured boot is enabled.
0x40 (CM_SERVICE_VERIFIER_BOOT_LOAD) indicates the driver should be promoted if booting with verifier boot enabled.
0x80 (CM_SERVICE_WINPE_BOOT_LOAD) indicates the driver should be promoted if booting to WinPE.
[service-install-section]
AddReg=add-registry-section
...
[add-registry-section]
HKR,,BootFlags,0x00010003,0x14 ; CM_SERVICE_USB3_DISK_BOOT_LOAD|CM_SERVICE_USB_DISK_BOOT_LOAD

#4574 | Outbreaker | ⇗ @diderius6 If it helps 'denial_k' is using "Start",0x00010003,"0" for this USB 3.0 integration.

#4575

infuscomus

> Zitat von ⇗ diderius6 im Beitrag ¶ #4573

> [add-registry-section]
> HKR,,BootFlags,0x00010003,0x14 ; CM_SERVICE_USB3_DISK_BOOT_LOAD|CM_SERVICE_USB_DISK_BOOT_LOAD

I am not sure if windows XP would understand this flag.
also, there is the issue of wdf01000 being needed for USB 3.0 to start

## Page 306

#4576

infuscomus

⇗ @Outbreaker
I'm tryng to get your script to set and keep a load order necessary for USB booting
it does this initially with hivesys.inf and later with modded usb.inf, usbport.inf and usbstor.inf but after setup things get changed and a 7B BSOD occurs
the problem in particular I think is kmdf - wdf01000
it moves to wdfloadgroup after setup
it should be Boot Bus extender
I'll PM you what I've changed so far.

#4577

diderius6

After I checked a lot of *.inf
I make just this as NEW usbboot.inf for USB3 boot via KMDF and hope it will work
Dietmar

    [usbservices]

    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01000","DisplayName",0x00000000,"Kernel-Mode Driver Framework 1.11"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01000","Type",0x00010001,"1"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01000","Start",0x00010001,"0"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01000","ImagePath",0x00020000,"system32\drivers\wdf01000.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01000","Group",0x00000000,"System Reserved"
    HKLM,"SYSTEM\CurrentControlSet\Services\wdf01000","ErrorControl",0x00010001,"1"

    HKLM,"SYSTEM\CurrentControlSet\Services\USBSTOR","DisplayName",0x00000000,"USB Storage Class Driver"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbstor","Type",0x00010001,"1"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbstor","Start",0x00010001,"0"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbstor","ImagePath",0x00020000,"system32\drivers\usbstor.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbstor","Group",0x00000000,"System Reserved"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbstor","ErrorControl",0x00010001,"1"

    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","DisplayName",0x00000000,"USB xHCI Host Controller"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Type",0x00010001,"1"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Start",0x00010001,"0"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","ImagePath",0x00020000,"system32\drivers\usbxhci.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","Group",0x00000002,"Base"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbxhci","ErrorControl",0x00010001,"1"

    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","DisplayName",0x00000000,"SuperSpeed Hub"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Type",0x00010001,"1"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Start",0x00010001,"0"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","ImagePath",0x00020000,"system32\drivers\usbhub3.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","Group",0x00000002,"Base"
    HKLM,"SYSTEM\CurrentControlSet\Services\usbhub3","ErrorControl",0x00010001,"1"

    HKLM,"SYSTEM\CurrentControlSet\Services\ucx01000","DisplayName",0x00000000,"USB Controller Extension"
    HKLM,"SYSTEM\CurrentControlSet\Services\Ucx01000","Type",0x00010001,"1"
    HKLM,"SYSTEM\CurrentControlSet\Services\Ucx01000","Start",0x00010001,"0"
    HKLM,"SYSTEM\CurrentControlSet\Services\Ucx01000","ImagePath",0x00020000,"system32\drivers\ucx01000.sys"
    HKLM,"SYSTEM\CurrentControlSet\Services\Ucx01000","Group",0x00000000,"Boot Bus Extender"
    HKLM,"SYSTEM\CurrentControlSet\Services\Ucx01000","ErrorControl",0x00010001,"1"

#4578 | infuscomus | ⇗ @diderius6 does this prevent wdf01000 from moving from Boot Bus Extender to Wdfloadgroup?

#4579

diderius6

⇗ @infuscomus
I am just building this CD.
Now without any other files for USB3 setup,
only my own^^
Dietmar
EDIT: What a crazy hard job.
I build really everything new. But after reboot I get still BSOD 0x7B, brr..^^
For all of the 5 entries in Services I get now Group Boot Bus Extender start=0
No Tag.
This cant work, because no sequence can be seen here.
This is a difference compared to normal USB2/3 boot, via KMDF USB boot you need to keep a sequence for all the drivers.
EDIT2: When I edit those entries by hand in registry, that they all have the correct LoadOrderGroup, install continues.
Now I have an XP SP3 Setup CD to USB3, but only with small correction by hand^^.

#4580 | Zucker2k | I came across this a while back. Hope you find it helpful: ⇗ http://report5.blogspot.com/2010/06/inst...-flashhard.html
#4581 | diderius6 | ⇗ @Zucker2k Yes, this works for normal USB install of XP. But not for KMDF drivers Dietmar
#4582 | Pill Monster | Can someone post a d/l link to XP without SP2 or SP3. All the ISO's on torrent sites have SP3 included. It's to test something.. TIA Actually I didn't check M$ own server...I'll do that now

#4583

ruthan

> Zitat von ⇗ Zucker2k im Beitrag ¶ #4580

> I came across this a while back. Hope you find it helpful:
> ⇗ http://report5.blogspot.com/2010/06/inst...-flashhard.html

Its only annoying - lots of manual things , when you have PC, where you dont need to modify files, its best just use Rufus USB / Sardu USB or YUMI USB, they are now good.. and if is something wrong, they are able to fix it.

#4584

Pill Monster

It's pretty easy to install XP from a USB drive just not with early versions. The later ISO releases included USB drivers that SP1 didn't have.
I installed SP3 on nF3/ nF4 boards from a flash drive.
Also I used ⇗ WinToFlash to create an XP bootable USB drive for my Sabertooth last week.

> Zitat von ⇗ ruthan im Beitrag ¶ #4583

> > Zitat von ⇗ Zucker2k im Beitrag ¶ #4580

> > I came across this a while back. Hope you find it helpful:
> > ⇗ http://report5.blogspot.com/2010/06/inst...-flashhard.html

> Its only annoying - lots of manual things , when you have PC, where you dont need to modify files, its best just use Rufus USB / Sardu USB or YUMI USB, they are now good.. and if is something wrong, they are able to fix it.

How did you do it in Rufus? I use Rufus but it didn't seem to work with XP...

#4585

diderius6

Yessssssssssssssssaaaaaaahhhhhhhhh:)))))))))))))))))!!!!!!!!!
Seems, that I am as good as in 2006.
I just install XPSP3 direct to an USB harddrive from Installations CD.
The nice USB3 driver from ⇗ @Mov AX, 0xDEAD is faster than any other.
Oh, what a fight with the settings of the KMDF driver.
And very nice, I can also use Firadisk USB install,
full installation for XP SP3 is now done in 3 min
Dietmar
PS: What I have done is to build really everything new from original en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso where I checked SHA1 before.
SHA-1
1C735B38931BF57FB14EBD9A9BA253CEB443D459
This gives me 5 services with Group Boot Bus Extender start=0,
no sequence. This is very similar to USB2 boot.
Then I add in HIVESYS.INF a new entry for usbstor.
And then, I give each service there a Tag number 1,2,3,4,5.
Tag 1 for wdf01000
Tag 2 for usbstor
Tag 3 for UCX01000
Tag 4 for USBXHCI
Tag 5 for USBHUB3
At the end, I have to delete the crazy usbstor.in_ in the i386 folder of the CD, because I have had put there a new usbstor.inf already and forgot to delete the old one,
Dietmar
diderius6 has attached files to this post

- ⇗ CDsettingsforUSBinstall.rar

#4586 | ruthan | Congrats. I would like to see some USB3 + other modern system patches (there were some acpi and timer etc patches).. ultimate package for existing system too. Im usually porting older installs to newer Hardware.

#4587

canonkong

⇗ @Mov AX, 0xDEAD
UASP seems to be working.
USB TO NVMe device on USB3.0 5Gbps port with UASP.
⇗
USB TO NVMe device on USB3.0 5Gbps port none UASP.
⇗
USB TO NVMe device on USB3.1 10Gbps port with UASP.
⇗
USB TO NVMe device on USB3.1 10Gbps port none UASP.
⇗

#4588 | infuscomus | ⇗ @diderius6 did wdf01000 switch from boot bus extender to wdfloadgroup again? or did you solve that?

#4589

diderius6

⇗ @infuscomus
Because I put all this 5 services in Group Boot Bus Extender with start=0,
they are like pinnend in this group.
And this was a problem for me, because before I chose the load order sequence only with the different groups.
But during testing with this crazy BSOD 0x7B i found, that XP SP3 listens in the meaning of the word to the sequence,
which is given by the Tag number. I think, this different in XP (gold), XP SP1, XP SP2.
As far as I remembe, earlier XP versions do not much care about the Tag,
Dietmar
PS: Look at the entries. May be, we dont neet usbboot.inf , because now the values are put 2 times in registry also via HIVESYS.INF .
This I test today in the afternoon because now I hurry to school:))!
EDIT: Yes, we do not need usbboot.inf any longer. I just test.

#4590

ruthan

Some good news. i have Gigabyte Z370 MB, where is PS/2 Y combo cable not working for both devices together, but with new Gigabyte 390 its working, so you can use mouse and keyboard during installation and USB3 debugging what is nice.
BTW im install that Z390 new MB and porting old installs, in Windows 7 i had almost everything except Intel USB3 working, there were USB3 drivers forWin7 on Win-Raid but where removed because of Intel, if someone has them, could you send them to me by PM pleas?
Hardware ID:
PCI\VEN_8086&DEV_A36D&SUBSYS_50071458&REV_10

## Page 307

#4591

Dibya

⇗ @diderius6
Awesome work . I cant believe we can install XP through USB3 . Thanks alot.
Well a friend of mine told their are source code of ACPI driver of some sort in XP WDK ⇗ https://winworldpc.com/product/windows-sdk-ddk/xp-nt-51
I didnt see the code though .
anyone can check if classpnp.sys from server 2003 sp2 break 2.2TB LBA limit in XP Disk stack .

#4592

diderius6

⇗ @Dibya
"anyone can check if classpnp.sys from server 2003 sp2 break 2.2TB LBA limit in XP Disk stack "
Please tell me a little bit more about.
Does this mean, we have a chance to see more than 2.2 TB on XP? Not to use drivers like the one from Paragon has the big advantage, that we can boot from them
Dietmar
PS: The thank goes to ⇗ @Mov AX, 0xDEAD .

#4593

Dibya

> Zitat von ⇗ diderius6 im Beitrag ¶ #4592

> @Dibya
> "anyone can check if classpnp.sys from server 2003 sp2 break 2.2TB LBA limit in XP Disk stack "
> Please tell me a little bit more about.
> Does this mean, we have a chance to see more than 2.2 TB on XP? Not to use drivers like the one from Paragon has the big advantage, that we can boot from them
> Dietmar
> PS: The thank goes to @Mov AX, 0xDEAD .

i found code in classpnp.sys that seems to allow 2k3 access 2.2tb plus storage upto 16tb in GPT .
Please backup every data before experimenting with XP
Me and rloew did research in it back in day but unfortunately our friend rloew left us
You can read here ⇗ https://msfn.org/board/topic/180215-rloe...as-passed-away/

#4594

Mov AX, 0xDEAD

> Zitat von ⇗ Dibya im Beitrag ¶ #4593

> i found code in classpnp.sys that seems to allow 2k3 access 2.2tb plus storage upto 16tb in GPT .
> Please backup every data before experimenting with XP
> Me and rloew did research in it back in day but unfortunately our friend rloew left us

No need to backup any data )
Today we have many VM engines, many of their offers dynamic size disk images, so inside VM we can create XXTb disk with real size on host about 100-200 Mbytes
Certainly we cannot fill these disks with data, but to test GPT/partitions i think it is enough. Another option is to use sector editors inside vm to walk on disk surface and simulate read access to any disk location

#4595 | Mov AX, 0xDEAD | Little survey: I'd like to hear from Forum Users what XP issues are most critical to you today ?

#4596

ruthan

I thing that is still the same, i lost of them, you cant probably fix:
1) Easily migrate XP to GPT driver with other OS and boot it from Grub2.
2) Read from other GPT drivers
3) No modern browsers support..
4) Only 2 monitors on Nvidia, i need 3.
5) Only 4 GB of RAM and so far problematic PAE for more, im ware limit 2GB per process but still loaded system would be much quicker with more ram and less swapping.
6) No Geforce 1xxx / 2xxx cards support / no modern Intel iGPU drivers
7) No Intel 219 Lan drivers

#4597 | Outbreaker | ⇗ @Mov AX, 0xDEAD When i look around then the most critical issues for now is to also get this WDF USB 3.0 driver to work at Setup boot and on a Live USB with a Windows XP that has Driver Framework 1.9 integrated.

#4598

diderius6

I just simplified my setup files for USB boot of XP SP3.
Copy the files from the package over to the folder i386 of an original XP SP3 CD (just replace them).
I use for this Ultra Iso. Nlite does not work. Nothing other is needed. Because I mod my Bios, I need no extra acpi.sys.
I tested my package with the original english XP SP3 CD.
en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso
The name of my package is
XPSetupCDtousb3byDietmar
Dietmar

#4599

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4589

> As far as I remembe, earlier XP versions do not much care about the Tag

⇗ @diderius6 ...Dietmar, where are the tags found in the registry?

#4600 | diderius6 | ⇗ @gordo999 They are in Services, when they are given. Numbers start from Tag = 1 (this service is then first of all loaded) and so on Dietmar

#4601

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4600

> They are in Services, when they are given.

⇗ @diderius6 ...thanks...never noticed that before.

#4602

ruthan

I migrated from Z97 to Z390. Windows 10 and Windows 7 are now working (i had to use unofficial Roline USB3 intel drivers) and classic Fernando Intel Sata drivers.
Android x86 and Linux are now fine too. So its WinXP 32 bit time.. and ok MacOS too - it would be worst.
Now when im trying to boot im getting classic ACPI crash:
⇗
I made migration from Z97 to Z370 on other machine, long time ago it was without patches and working PS/2 and it was hard. Now with new discovery it should be easier, in theory.
Now i want to make system booting with PS/2 without USB, i will messing with USB later, after system would be bootable. I dont want to reinstall im using same install till 2004 its highly configured and loaded, i setup all again would take too much time, in the past i always managed to migrate it to new HW.
So what i have to do (discussions)?
1) Replace some system files with APCI, HALTimer etc patches? Can someone PM me lastest and greatest for my system?
2) Its still necessary make special boot.ini entries for patched files, or not?
3) With patches, will it boot from Sata driver, out of box or not? I have installed some older Fernando Sata driver, it worked with Z97.. I can have in machine also Marwell Sata controller with already installed driver within XP so i can use it.. And anything of this will not work in can use Asmedia PCI-E Sata addon card with IDE bios. So i theory i need only fix ACPI thing to boot system and i can later mess with Sata.

#4603

Dibya

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4594

> > Zitat von ⇗ Dibya im Beitrag ¶ #4593

> > i found code in classpnp.sys that seems to allow 2k3 access 2.2tb plus storage upto 16tb in GPT .
> > Please backup every data before experimenting with XP
> > Me and rloew did research in it back in day but unfortunately our friend rloew left us

> No need to backup any data )
> Today we have many VM engines, many of their offers dynamic size disk images, so inside VM we can create XXTb disk with real size on host about 100-200 Mbytes
> Certainly we cannot fill these disks with data, but to test GPT/partitions i think it is enough. Another option is to use sector editors inside vm to walk on disk surface and simulate read access to any disk location

If you ask me , I will love to have full ACPI support on Ryzen for XPx64.
Newer GPU Driver .
Any one have debug symbol for Vista Sp2 ? I seems Microsoft removed them

#4604 | Zucker2k | x86, x64 ACPI Support For Sunrise Point (Skylake Mobile). ACPI support is the biggest hurdle for most.

#4605

genieautravail

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4595

> Little survey:
> I'd like to hear from Forum Users what XP issues are most critical to you today ?

Graphic drivers support for Intel and AMD APU !

## Page 308

#4606 | diderius6 | From today evening direct install XP SP3 to any USB medium is perfect:)) ⇗ https://www.zone62.com/downloads/softwar...comment_id=2220 Dietmar

#4607

Andalu

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4595

> Little survey:
> I'd like to hear from Forum Users what XP issues are most critical to you today ?

1. use integrated graphics;
2. have a better performing nvme driver;
3. access partitions larger than 2.2TB for the USB3 external hard disk drives also.

#4608

Mov AX, 0xDEAD

@Dibya

> Zitat von ⇗ Dibya im Beitrag ¶ #4593

> i found code in classpnp.sys that seems to allow 2k3 access 2.2tb plus storage upto 16tb in GPT .

sources of disk.sys and classpnp.sys available in DDK, so you easily check possible limits in these drivers

#4609

diderius6

⇗ @Mov AX, 0xDEAD
I think, to backport videodriver to XP would be nice,
but hard as much as possible. And nice would be a driver for lan i219
and a scsiport based nvme driver, because with this you can do ntbootdd boot of XP via nvme with every older compi.
From those 3 wishes I think the most easy is a new nvme.sys working with scsiport of XP.
For this you can use the code from OFA and change everywhere Storport entries against them for Scsiport.
Some of porting vice versa is written by Microsoft
Dietmar

#4610 | skullteria | Port directly WDDM driver is impossible without change win32k and get dxgkrnl working full. Can try port older version of nvdia, intel and amd XDDM drivers.
#4611 | mull | It is better to port WIN8 EMMC driver to XP

#4612

Gelip

> Zitat von ⇗ Gelip im Beitrag ¶ #4427

> No, UEFI32 or UEFI64 emulator does not work on computers with UEFI bios. Works only on legacy bios computers.

DUET32 (IA32) also works on UEFI64 bios - I checked it. This is my version of DUET32 with the IBM logo: ⇗ DUET IA32
⇗

#4613

diderius6

⇗ @Gelip
Hi,
please write a little bit more what you have tested until now and what can be reached with DUET IA32.
Can you boot XP SP3 with it?
Can you use the DUET IA32 file from you as a bootloader for legacy OS, working in pure UEFI 64 Bios surrounding
have a nice day
Dietmar

#4614 | infuscomus | ⇗ @diderius6 do you know of any open source CSM? that would be the best solution for legacy OSes like DOS/Windows 9x

#4615

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #4613

> Please write a little bit more what you have tested until now and what can be reached with DUET IA32.
> Can you boot XP SP3 with it?

Yes, you can boot WinXP 32-bit. Depending on the hardware, there may be a problem with the graphics card driver.

#4616 | diderius6 | ⇗ @infuscomus I do not know, where to find an Open Source CSM. But ⇗ @Mov AX, 0xDEAD told, that CSM is open source, so maybe it exists somewhere Dietmar
#4617 | diderius6 | ⇗ @Gelip Do you have an ready XP *.iso file for me, so that I cant test UEFI boot of XP SP3 Dietmar

#4618

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #4617

> Do you have an ready XP *.iso file for me,
> so that I cant test UEFI boot of XP SP3
> Dietmar

Oh, why don't you read my posts carefully?
For now, WinXP 32-bit can only boot under UEFI32 (same as WinXP 64-bit on UEFI64) but not install.
WinXP must be installed in legacy mode (CSM) and then you can run it using DUET32 (UEFI32):
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (296)

> Zitat

> When it comes to preparing WinXP x86 you need the files winload.efi and bootmgfw.efi from the test version of Vista Beta Longhorn 6.0.5219.0
> To WINDOWS\system32 you copy winload.efi and to FAT32 pendrive file bootmgfw.efi (I changed the name to WinXP.efi ) and to the root directory of the pendrive the boot.ini file by adding the /usenewloader option.
> Now just boot your compi from this pendrive - that's all

#4619 | Gelip | ⇗ @diderius6 --> In UEFI mode you can only boot OS from disk previously installed in legacy mode <--

#4620

diderius6

⇗ @Gelip
Hihi, I try to order this a little bit in my head:
First you make a normal, generic XP SP3 install with Fat32 on a compi with CSM.
And on this installed XP you use DUET32 (UEFI32) with 2 new bootloader files from Longhorn and new boot.ini entry (newloader).
At first you try this on this compi and its Bios with CSM enabled.
And when it works, it also should work with all CSM disabled in this Bios.
And when this is a generic XP SP3 it may start on another compi with a Bios, that has ONLY UEFI Bios boot option,
am I right now:))
Dietmar
PS: I think, it is possible to make an install *.iso with the correct efi files from this;))..

## Page 309

#4621

Gelip

> Zitat von ⇗ diderius6 im Beitrag ¶ #4620

> First you make a normal, generic XP SP3 install with Fat32 on a compi with CSM.

The system can be on any NTFS, MBR or GPT partition. The FAT32 partition is only needed to start in UEFI. At the moment, it is most convenient to use a FAT32 flash drive to boot WinXP from an NTFS partition.

> Zitat von ⇗ diderius6 im Beitrag ¶ #4620

> PS: I think, it is possible to make an install *.iso with the correct efi files from this;))..

I haven't tried it yet but I was thinking about it. The PantherXP or Shorthorn Project can be helpful here.

#4622 | Gelip | ⇗ @diderius6 WinXP cannot be installed under UEFI but can be deployed, e.g. using VMware: ⇗ Deploy WinXP The guide is for the 64-bit version but the same can be done with the 32-bit version. You install WinXP in VMware (legacy), implement drivers, seal the system, make a disk image to a file, write the image to disk in the target UEFI computer and boot from it.
#4623 | canonkong | ⇗ @Mov AX, 0xDEAD How do I need to do if I need to modify the win8 UASP to win7. I failed again and again, and now only can use VIA UASP on it, it can works well, but the 4K read/wtite are very slow.

#4624

Mov AX, 0xDEAD

> Zitat von ⇗ canonkong im Beitrag ¶ #4623

> @Mov AX, 0xDEAD
> How do I need to do if I need to modify the win8 UASP to win7. I failed again and again, and now only can use VIA UASP on it, it can works well, but the 4K read/wtite are very slow.

⇗ @canonkong
did you tested "uaspstor.w8 for storport.w2003" ? it works even on win2003 with original storport.sys, i think it must work on win7 with win7's storport.sys

#4625 | canonkong | ⇗ @Mov AX, 0xDEAD No, I an not have "uaspstor.w8 for storport.w2003" files. Can you share this file for me to have a test? Thanks. And to midify the win8 uaspstor.sys. In addition to removing all the SpinLock, what else do I need to modify?

#4626

diderius6

This is with a smoking USB port
left site is USB device with normal USBSTOR.SYS from XP SP3
and on the right site is the same USB device with nicccceee USBSTOR.SYS from ⇗ @daniel_k .
Waaaooohh;))))
Dietmar
⇗

#4627 | usa1ec | Hi, people! Send me this nice USB3 driver in PM. Pls, URL.
#4628 | infuscomus | ⇗ @Mov AX, 0xDEAD if possible, could you backport windows 8 storahci? ⇗ @Andalu and @intMD reported that the one we have now does not support TRIM
#4629 | Andalu | ⇗ @infuscomus here's what I talked about: ⇗
#4630 | Dibya | ⇗ @diderius6 ⇗ @Mov AX, 0xDEAD RTL219 is doable if we can analyze a bit . Reactos have e1000 driver ⇗ https://github.com/reactos/reactos/tree/...etwork/dd/e1000 We need to port it to e1000e ⇗ https://github.com/torvalds/linux/tree/m...et/intel/e1000e

#4631

daniel_k

⇗ @Andalu and ⇗ @infuscomus
Did you try my modded RSTe driver?
It certainly supports TRIM on Win7 and later. I believe it's an issue with XP itself or the lack of a lower filter driver.
Can't test it myself right now, what about trying storahci on Win7 to see if the driver really supports TRIM?
Remember to disable Driver Signature Enforcement during boot if on x64.

#4632

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4628

> @Mov AX, 0xDEAD
> if possible, could you backport windows 8 storahci?
> @Andalu and @intMD reported that the one we have now does not support TRIM

storahci_w8 already done, check release3.7z (storport_w8 is old version, but still works with storahci_w8)
Why you think storahci from skullteria doesnt support TRIM ? it was compiled from DDK sources and must have trim support
Anyway trim on winxp is tricky, need special software, but even TxBENCH/O&O Defrag not always trim partition properly - trimcheck.exe often show cleaned sectors with "saved" data (at least on my ocz arc100 ssd, barefoot3 controller)

#4633

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4632

> Why you think storahci from skullteria doesnt support TRIM ? it was compiled from DDK sources and must have trim support

To be fair, we didn't really see the code it was compiled from.
Are you sure that compiling the DDK source results in the same driver included on Win8?

#4634 | Andalu | ⇗ @daniel_k no problem with your modded driver, the trim works in XP also. P.S.: what a pleasure to read to you again
#4635 | daniel_k | ⇗ @Andalu Glad to know it works. ⇗ @Mov AX, 0xDEAD Based on the report from ⇗ @Andalu, XP, Vista and Win7 all require a filter driver to passthrough TRIM maybe?

## Page 310

#4636 | Andalu | ⇗ @Mov AX, 0xDEAD I recognized the trim issue only with the storhaci driver from skullteria. No issue with the modded RSTe 4.7.0.1117 driver by daniel_k and the RST AHCI+RAID driver v11.2.0.1006 by Fernando.
#4637 | infuscomus | ⇗ @daniel_k I am running an AMD Ryzen system for my XP install, would that be supported by your RSTe driver? I assumed it wasn't compatible with AMD. I still have your modded AMD 1.4.1.402 - did that support TRIM? I'm used to using TRIM manually in windows10

#4638

Mov AX, 0xDEAD

⇗ @daniel_k

> Zitat

> Are you sure that compiling the DDK source results in the same driver included on Win8?

no, i'm not sure, but i saw many trim-depend functions in sources, doubtfully they were specially disabled in DDK version
storahci sources was also extended in win8.1 DDK, i dont know what's was improved

#4639

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4635

> @Mov AX, 0xDEAD
> Based on the report from @Andalu, XP, Vista and Win7 all require a filter driver to passthrough TRIM maybe?

No, filter driver is "Intel way" to wrote drivers ) I dont know why they separated driver
win7/8/10 dont have any filter drivers to process trim

#4640

Mov AX, 0xDEAD

⇗ @Andalu

> Zitat von ⇗ Andalu im Beitrag ¶ #4636

> I recognized the trim issue only with the storhaci driver from skullteria

what software you use to send trim to drive?

#4641

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #4637

> I am running an AMD Ryzen system for my XP install, would that be supported by your RSTe driver? I assumed it wasn't compatible with AMD.

Actually I'm talking about storahci. To have a definitive answer as to whether it supports TRIM or now.

> Zitat

> I still have your modded AMD 1.4.1.402 - did that support TRIM?

Pretty sure it supports TRIM, at least on Win7+.

#4642

Andalu

⇗ @Mov AX, 0xDEAD
I used always the Adata SSD Toolbox for my crucial and samsung SSD drives, never got issue with the other sata-ahci drivers tried.
I just connected a kingston drive and the 'kingston ssd toolbox 2.0.93' give me the message: "no kingston drives found" with the skullteria driver installed.
Here the Adata report for the trim not working on the crucial ssd drive:
P.S.: I have yet to find out why I always have trouble posting files in this forum... and it only happens here
Andalu has attached files to this post

- ⇗ ADATA SSD ToolBox 3.0.11.txt

#4643

Fernando

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4639

> No, filter driver is "Intel way" to wrote drivers ) I dont know why they separated driver

1. Not all Intel RST drivers do contain an additional SCSI Filter driver named iaStorF.sys.
2. The SCSI Filter driver is neither required nor usable for "normal" SSDs, but older Windows Operating Systems up to Win7 natively don't let the TRIM command pass through the Intel SATA Controller to an SCSI disk drive. That is why Intel added the SCSI Filter driver.

#4644

Mov AX, 0xDEAD

> Zitat von ⇗ Fernando im Beitrag ¶ #4643

> [quote=Mov AX, 0xDEAD|p4643]
> 2. The SCSI Filter driver is neither required nor usable for "normal" SSDs, but older Windows Operating Systems up to Win7 natively don't let the TRIM command pass through the Intel SATA Controller to an SCSI disk drive. That is why Intel added the SCSI Filter driver.

Sorry, but i dont understand you, filter driver specialy block trim command before transfer to any disk controller for preWin7 OSes ? or it pass it to companion - main intel ahci/raid driver directly ?
i saw some time ago, this filter read setting from registry and has ability to block trim command if forced by user

#4645 | Fernando | ⇗ @Mov AX, 0xDEAD: The real SCSI SSDs need the UNMAP command for cleaning the SSD cells (= similar to the TRIM command regarding its function), but old Windows Operating Systems don't support the UNMAP command. The addition of the SCSI Filter driver helps to let the TRIM command pass through the Intel SATA Controller into the SCSI drives.

#4646

Mov AX, 0xDEAD

> Zitat von ⇗ Fernando im Beitrag ¶ #4645

> @Mov AX, 0xDEAD:
> The real SCSI SSDs need the UNMAP command for cleaning the SSD cells (= similar to the TRIM command regarding its function), but old Windows Operating Systems don't support the UNMAP command.

OK, this now clear, but most new RST (13.x.x. and up, not RSTe) drivers in their INFs support only AHCI/RAID controllers, no SCSI controllers, why still filter installed ?
EDIT: or in raid mode controller become scsi controller ?

#4647 | Fernando | ⇗ @Mov AX, 0xDEAD: All Intel RSTe drivers and the Intel RST ones from the v11.5 series up to the v15.9 series do contain the SCSI Filter driver. This permits the TRIM support for all SSDs (non-SCSI and SCSI). If the user runs a modern Windows from Win8 up, the driver named iaStorF.sys is installed, but will not be used. That is why the INF files contain different driver's course of action for Win7 and Win8-10.

#4648

diderius6

I compare the
STORAHCI driver from ⇗ @skullteria with the STORAHCI driver from ⇗ @Mov AX, 0xDEAD .
On the left is skullteria and on the right is move.
skullteria wins on harddisk and move on SSD
Dietmar
PS: Trim works only with the patched storport from Win 8.1.
⇗

#4649

daniel_k

⇗ @diderius6
Did you run the bench several times on HDD?
Please do a test for us, with storahci from skullteria, patch and use storport.sys from Mov AX, 0xDEAD, remember to fix PE checksum.

> Zitat von Mov AX, 0xDEAD

> i found issue in storport_w8: by default it force MSI Interrupts, fix to use standart interrupts:
> offset_132b3: C6 83 CC 09 00 00 01 => C6 83 CC 09 00 00 00

Check performance and TRIM.
⇗ @Mov AX, 0xDEAD
Interesting, it's a pattern, didn't really pay attention, but all MS AHCI drivers are "written" as an IDE/ATAPI controller driver, class {4D36E96A-E325-11CE-BFC1-08002BE10318}, don't really need a lower filter.
On the other hand, Win81 NVME driver is a SCSI controller driver.

#4650

diderius6

The patched storport.sys works now also for the OFA nvme driver (I use the faster and more generic version 1.3).
Here is first test of nvme Optane 905P compare
storport 5.2.3790.4173 against storport 6.2.9200.16384 with patch.
I repeat the compare 3 times, results are always the same.
So, the storport.sys (on left site here) from Server 2003 is always a little bit faster than the one from Win8.1 with patch
Dietmar
⇗

## Page 311

#4651 | daniel_k | ⇗ @diderius6 Thanks, so the Win8 storport is optimized for ... Win8 kernel. Does try TRIM work on NVME? Also try skullteria's storahci with MOV's storport. I'd like to know if the non working TRIM is because of the driver itself or storport.
#4652 | diderius6 | First I test Trim with Storport 4173 and ⇗ @skullteria STORAHCI. Does not work. Then I test patched storport from win8.1 and storahci from Win8.1 Works, I use the Naraeon tool and the Adata tool for this. Both work.
#4653 | daniel_k | What about patched storport from win8.1 and skullteria STORAHCI?

#4654

diderius6

⇗ @daniel_k
With patched storport from win8.1 and skullteria STORAHCI
the Naraeon tool fails (message "no supported device")
but the Adata tool works!!!
Is there an easy way, how I can test, if TRIM really happens
Dietmar
PS: Funny, on harddisk, the ⇗ @skullteria STORAHCI driver is even with patched storport from win8.1
much faster compared with storport from win8.1 together with Storahci driver from Win8.1;)).
On SSD, the combination of storport from win8.1 together with Storahci driver from Win8.1 is faster.
The result for SSD does not change at all with the combination patched storport from win8.1 and skullteria STORAHCI,
compared with storport 4173 from server2003. But suddently TRIM works!

#4655 | daniel_k | Dietmar, TRIM depends on storport then, it seems. Even if stornvme still cannot work, storport from W8 (not W8.1), proved to be useful.

#4656

diderius6

⇗ @daniel_k
On a Samsung 970 pro 1TB nvme disk, even with the patched storport from win8.1,
only with the Naraeon tool a Trim can be performed.
Now, the Adata tool tells, no compatible sata drive found:))
Dietmar
EDIT: Now I think, no Trim was performed under XP on the Samsung 970 pro 1TB nvme disk,
no matter which version of storport is used. The version 1.3 and 1.5 of the OFA nvme driver can not perfom Trim under XP SP3 until now.
The Adata tool tells just the truth.

#4657 | infuscomus | ⇗ @diderius6 does the AHCI driver perform TRIM correctly? or does it have this problem too?

#4658

diderius6

⇗ @infuscomus
For the STORAHCI driver from Move together with the patched storport from 8.1
Trim works.
And to 99% I am also sure, that it works with the STORAHCI driver from ⇗ @skullteria
but only in combination with the patched storport from 8.1
Dietmar
PS: Until now, no trim is possible for any nvme device under XP SP3. But there is hope;))..

#4659

genieautravail

> Zitat von ⇗ diderius6 im Beitrag ¶ #4654

> Is there an easy way, how I can test, if TRIM really happens

Try trimcheck
⇗ https://github.com/CyberShadow/trimcheck

#4660 | kukonosau | ⇗ @diderius6 Do you have acpi.sys for Windows Vista for Ryzen? Vista is unstable working and get BSOD sometimes.
#4661 | diderius6 | ⇗ @kukonosau For Vista I have no extra acpi.sys. Some months ago I see, that ⇗ @daniel_k works a little bit with Vista Dietmar
#4662 | skullteria | Yes, it will not work, because it is a feature only provided by storport starting Windows 8. So, I had to disable if version was less than 8. However, if i remember, has a check

#4663

infuscomus

> Zitat von ⇗ diderius6 im Beitrag ¶ #4658

> PS: Until now, no trim is possible for any nvme device under XP SP3. But there is hope;))..

our OFA NVMe driver was modified to work for 2003 storport - maybe this broke TRIM support?
does the original OFA NVMe driver work for XP with the modded storport?

#4664 | kukonosau | ⇗ @diderius6 Thanks. But where download @danielk acpi.sys for Vista x64 for Ryzen? Vista BSOD sometimes causes old acpi or no?

#4665

diderius6

⇗ @infuscomus
This is a nice idea about Trim for the OFA nvme driver. I found this in the description of the OFA nvme driver version 1.3.
So it seems, that Trim can start from Win8
Dietmar
Driver building:
- For Windows 7, Server 2008 R2, Server 2012(TRIM disabled) and Windows 8(TRIM disabled),
You may build the driver within WDK 7600, Windows 7 64-bit build environment or Visual
Studio 2012 when configured for Window7 in Project Property.
- For Windows Server 2012(TRIM enabled) and Windows 8(TRIM enabled)
You should build the driver within Visual Studio 2012 when configured for Windows8
in Project Property.
PS: I just test: The original, unmodded OFA nvme driver do not work with XP SP3, even not with the very last storport.sys from win8.1.

## Page 312

#4666

Andalu

⇗ @daniel_k
I noticed some strange behaviors when my system boots in /nolowmem mode with WinXPPAE_v2 >4GB when I tried to use the aida64 linear test or to launch the edit command via windows prompt.
The existing hal.dll file has the sha-1 F5C40501F9CE35BF482CB039A90C086627D0BE48
Here's the two screenshots taken in two different booting, in both cases the issue happens on the first usb3 stick plugged.
On the first the edit command doesn't work and aida64 also seems to be "out of mind":
⇗
On the second, even if the edit command works, aida64 doesn't detect the usb3 stick connected and the device manager also shows a yellow mark:
⇗
In both cases, the 'famous' gs_caber_1.1.5.7 program doesn't work.
With the hal.dll (SHA-1: 8CBEC120FEB93D855AB1ED6FAD9A8D8223CC0E9A) from the hal_pae_fix package, I never had the usb3 devices unrecognized. Sometime the edit command didn't work but, at least, gs_caber_1.1.5.7, has worked always :)

#4667 | Andalu | I also noticed some strange behaviors related to the "uaspstor.w8 for storport.w2003" driver but I need to know if I have the latest driver version.
#4668 | daniel_k | ⇗ @Andalu Thanks for your reports, I'll review them later.

#4669

diderius6

Hihi, XP SP3 is best
Dietmar
The reviews of Intel 10th gen Core i9-10900K are now officially out and we've seen that Intel manages to hold its forte in gaming and overclocking abilities when compared to the AMD Ryzen 9 3900X and the Ryzen 9 3950X. Apparently, Core i9-10900K has a lot more overclocking potential than the default 5.3 GHz all-core Thermal Velocity Boost, which can be harnessed via LN2 or liquid helium cooling. Asus's in-house overclocker Elmor has managed to achieve just that by being able to hit a whopping 7.7 GHz on all 10 cores while also managing 6.6 GHz DDR4 memory speeds on the Z490 platform.
The initial trial with LN2 resulted in a BSOD so the team opted to use liquid helium (−269 °C). While this did provide enhanced cooling, it also resulted in the failure of one the memory modules. The remainder of the experiment was therefore conducted with 8 GB single-channel memory. Elmor could ultimately push the Core i9-10900K running on the Asus ROG Maximum XII Apex motherboard to 7.7 GHz (7,707.62 MHz to be precise) at a voltage of 1.194 V.
Interestingly, Windows XP was the used as the OS so as to support the Asus Turbo V Core overclocking utility and the input devices were likely using the PS/2 interface. This could be due to the fact that Windows XP lacks drivers for USB 3.0 and many other on-board peripherals, which should minimize interference while pushing the CPU to the hilt.
Apart from the CPU, Elmor could also overclock the G.SKILL F4-4000C18-8GTRG to 3,332.7 MHz or effectively 6,665.4 MHz DDR. Similar such memory OC records have been achieved on the Z490 platform by other overclockers as well.
Of course, these records are only meant to prove a point and mean nothing to most mainstream users. We also do not know how stable the system actually was or what were the results of benchmarks. Elmor does shout "Cinebench" at one point, but no results have been published yet. All said and done, it is good to know that Intel's flagship CPU has excellent overclocking potential, which should lead to some neat results even on air or AiO cooling.
⇗ https://www.youtube.com/watch?v=rDWirGE0u44

#4670 | daniel_k | ⇗ @diderius6 Are you going to be the first one here to try XP on Intel 10th gen? Interesting, Intel planned to remove CSM by 2020, but all Z490 BIOSes still have it. Good for us!

#4671

YuriyCN

> Zitat von ⇗ Andalu im Beitrag ¶ #4666

> @daniel_k
> In both cases, the 'famous' gs_caber_1.1.5.7 program doesn't work.
> With the hal.dll (SHA-1: 8CBEC120FEB93D855AB1ED6FAD9A8D8223CC0E9A) from the hal_pae_fix package, I never had the usb3 devices unrecognized. Sometime the edit command didn't work but, at least, gs_caber_1.1.5.7, has worked always :)

In the file "hal.dll" (version 5.1.2600.5687), replacing the byte at offset 07B3C, to put byte 0xC3 instead of byte 0xC7 -- fix PM_Timer. Correction of the timer leads to an increase in the performance of the SATA AHCI driver up to 30%. I measure the speed of the SSD drive by copying a file of few gigabytes in size using Total Commander.
On Windows 7, the speed reaches 450 MB/s, but on Windows XP it is much lower - 180 MB/s. The speed limit is due to the SATA AHCI driver, because the SSD drive itself is much more productive. Replacing hal.dll with the patched one, I got a speed increase up to 260-265 MB/s. The byte at offset 07B3C has an effect. Fixing the remaining bytes does not affect performance, although I have 16 GB of RAM and use the PAE mode, maybe the "DMA32 PAE fix" on my processor and motherboard is not required.
You wrote a lot of technical information, but I'm not a hacker - I dont understand what to do about it. Can you make a ready-made solution - to patch the file ⇗ https://www.upload.ee/files/11521284/hal.zip.html and to fix PM_Timer, taking into account the normal operation of the PAE mode and the GS_Caber program, which stops starting when the patched file "hal.dll" is used. Or indicate which bytes at which offset are needed to fix, so that I can do it myself.

#4672 | ruthan | Z490 is not big deal, still not PCI-E gen 4 and best cpu in all cores load is consuming + 100 W in compassion with 9900K which is already power hungery. I thing that X299 is better choice, CPUs consume similar power and it has 40 PCI-E gen 3 lines instead of 16/20 of Z370/Z390/Z490.. it has otherwise same features and Quad channel memory doesnt hurt too.
#4673 | infuscomus | I'm thinking of upgrading to AMD Threadripper later this year I think it would be fun (and very silly!) to run XP on it too, if possible. has anyone here tried installing XP on Threadripper?

#4674

diderius6

We have a new alltime record for USB3 in XP SP3
using uaspstor.sys with the last mod from ⇗ @infuscomus .
Problem in this is only,
how to lock down the fire on my USB port ^^
Dietmar
PS: Speed is about 1032 MB/s , still I am cooling..

#4675 | Andalu | I haven't yet benchmarking an UAS device with this modded driver thanks to ⇗ @infuscomus but also for this driver I found a strange behavior on my system: once recognized as uas mass storage, the same device will continue to be recognized only if already connected during the XP booting. When connected post booting, it will no longer recognized. Nothing changes even plugging it to another usb port. When unrecognized, the only way to get another detection is to plug and then unplug any usb2/usb3 stick.
#4676 | Mov AX, 0xDEAD | Another storahci comparison of SATA SSD "OCZ Arc100" ⇗ Strange low storahci_skullteria's performance, i didnt use storahci.reg, so probably speed depend on it
#4677 | diderius6 | ⇗ @Andalu I think this happens because of the very big current for harddisks in USB clothes. The limit for USB3 is 800 mA and I think, the USB3 driver from Move just has something like a fuse, not to let your USB port burn Dietmar
#4678 | Andalu | ⇗ @diderius6 never had similar issue on another system where I used my UAS devices from long time.

#4679

Andalu

I started benchmarking the modded driver from infoscomus on a fresh XP installation using the nvme to usb3 adapter mounting my 970evo, but I have made a different test:
on the left the test made with the original WinXPPae2 hal.dll (sha-1 F5C40501F9CE35BF482CB039A90C086627D0BE48)
on the right the test with patched hal.dll (SHA-1: 8CBEC120FEB93D855AB1ED6FAD9A8D8223CC0E9A) from the hal_pae_fix package
⇗ ⇗
I had similar results with the uasport drivers from Mov AX, 0xDEAD. Unfortunately, with the modded driver from infuscomus, I also got two 0xC2 bsod on five benchmarking attempts (even without the patched hal).

#4680 | Mov AX, 0xDEAD | ⇗ @Andalu right screen is unreal, may be your "hal_pae_fix" package doesnt have hal_timer_fix ?

## Page 313

#4681

daniel_k

⇗ @Mov AX, 0xDEAD, ⇗ @diderius6 and all others:
I did it! NVME driver for XP!!
Ported from Win7!!!
With all due credit to ⇗ @Mov AX, 0xDEAD, for helping me!
Quick bench on Samsung 970 EVO:
⇗

#4682 | diderius6 | ⇗ @daniel_k Waaaaooohhh:))))!!! I want it soso much Dietmar PS: Спасибо большое :))!! ⇗ @Mov AX, 0xDEAD
#4683 | daniel_k | ⇗ @diderius6 Did a really quick test, seems stable, but consider it a beta. AIDA64 cannot read SMART attributes, I believe because XP doesn't officially supports NVME class devices. I'm so, so tired. This one was really tough for me, even with ⇗ @Mov AX, 0xDEAD's help.

#4684

diderius6

⇗ @daniel_k
I just booted:)) the Optane nvme 905P with your new nvme driver.
storport.sys has to be changed against yours.
Here are benchmarks left is Optane, right is 970 pro 1TB
niccccccccccccceeeeeeeeeee:))..
Dietmar
⇗

#4685

daniel_k

⇗ @diderius6
Where are the benchs, man?
Please do a complete comparison between this NVME.W7 and NVME.OFA and also test performance between storport.W8 and storport.W7 for SSDs/HDDs.
Anyway, this driver should solve the issues with Samsung NVMEs, which are not stable with OFA's driver.
Good night and see ya tomorrow.

#4686

diderius6

⇗ @daniel_k
Here are the first bench,
now I go to bed,
here is 3:00 at night,
and tomorrow I have school:))
Dietmar

#4687

Outbreaker

Dose someone know how to tell a driver .inf file to get the .sys files for the sp3.cab or driver.cab Archive (.\Driver Cache\I386\*)?
It works with some Windows .inf files like the printer drivers or the game controller drivers, but i didn't find anything to replicate this.
EDIT:
Now i remember again how i did it 8 years ago. I have to edit the DRVINDEX.INF and the LAYOUT.INF files too, and also put "LayoutFile=layout.inf" in the "[Version]" section of the driver *.inf file.

#4688

Andalu

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4680

> @Andalu
> right screen is unreal, may be your "hal_pae_fix" package doesnt have hal_timer_fix ?

I used the hal5687.dll from the hal_pae_timer_fix package and the results are correct now.
⇗
But I wonder which is the best hal.dll
It has become difficult to be sure which version of any file is the right one to use.

#4689 | Mov AX, 0xDEAD | Patch to fix yellow mark with Code 31 for UAS Driver (Windows 8 backport): change stor_uas.sys in folder storport_w8 and storport_w2003: 1) 65005C00520061006900640050006F00 => 65005C00550061007300700050006F00 2) recalc cheksum

#4690

Andalu

About the issue I encountered on my system trying the uasport drivers from ⇗ @Mov AX, 0xDEAD, I can be more precise now.
I made some tests on the following devices (UASP protocol supported):
- NVME to USB 3.1 adapter (Micron JMS580 chip)
- USB 3.0 to SATA III adapter (Asmedia ASM1153E chip)
- USB 3.0 External Case for HDD (Micron JMS567 chip)
The behavior is the same for all of them, no difference using an HDD, SSD or NVME disk:
when plugged for the first time, after the driver installation and the requested reboot, the device (stayed connected to the card) is correctly recognized as UAS mass storage and you can plug and unplug it without issues in this XP session.
But for the next reboots or shutdown, the same device will be detected again only if already connected during the XP booting. When connected post booting, it will no longer recognized. Nothing changes even plugging it to another usb port. When unrecognized, the only way to get another detection is to plug and then unplug any usb2/usb3 stick.
UAS device connected after the XP booting is not recognized:
⇗
usb2 stick correctly recognized while the UAS device remains unrecognized:
⇗
usb2 stick ready to be safely removed:
⇗
UAS device recognized again as soon as the usb2 stick is unplugged:
⇗
During the benchmarking the UAS device correctly recognized suddendly become an 'unknow device'. In the properties there is the error code 43 (windows has stopped this device because it has reported problems) and in the details I can see the "USB\reset_failure" message. Under the same conditions, with the modded driver from ⇗ @infuscomus, I got the 0xC2 bsod.

#4691

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #4688

> But I wonder which is the best hal.dll
> It has become difficult to be sure which version of any file is the right one to use.

Intel MoBo need hal.dll + pae_dma_fix + HAL_acpitimer_fix
AMD MoBo need hal.dll + pae_dma_fix
HAL_acpitimer_fix:
usualy one byte patch, like 0x79->0xEB, HaliAcpiTimerInit procedure
pae_dma_fix:
complex patch, HalGetAdapter procedure
halmacpi.dll SP3 version has version 5.1.2600.5512, last known version for Windows XP is 5.1.2600.5687

#4692 | daniel_k | ⇗ @diderius6 From what I've seen, performance is lower than OFA's. Anyway, it's final code from MS, highly compatible. Please don't forget to test TRIM on SSD/NVME.

#4693

canonkong

I found several USB expansion cards from different chip manufacturers (ASMedia, VIA, Etron, Renesas, Fresco Logic, Ti).
Tested using USB official own driver and WIN8 transplanted driver.
WIN8 transplanted driver works on each USB expansion card, and the performance is better than the official driver of each USB expansion card.
I will test its performance on the USB3.2 GEN2X2 20Gbps expansion card latter.
Etron USB3.0 expansion card
⇗
Renesas USB3.0 GEN2 expansion card
⇗
VIA USB3.0 expansion card
⇗
ASMedia USB3.1 10Gbps expansion card
⇗
ASMedia Official own drive
⇗
ASMedia with MOD driver
⇗

#4694

diderius6

⇗ @daniel_k
The problem in to test Trim under XP SP3 is,
that I do not know a single program for to trim nvme,
that works also under XP.
This is, because no driver for nvme for XP existed before.
May be here in the forum somebody noticed,
that his trim program works also under XP
Dietmar
PS: The Trim for nvme is different from the trim for SSD.

#4695

diderius6

⇗ @Mov AX, 0xDEAD ⇗ @daniel_k
Nice would be, to have a Tutorial and all the names of the used tools,
for backporting the nvme driver from Win7.1 to XP SP3.
Via this way, everybody can make some experiments for himself and
I can use it at school.
Dont know, how much work this will mean to write such a step by step Tutorial.
I would help you with this as good as I can
Dietmar

## Page 314

#4696 | daniel_k | ⇗ @diderius6 Sorry, but a guide would be too complex, as the backporting process is. In the mean time, another gift for you, latest Samsung NVME driver.

#4697

diderius6

⇗ @daniel_k
You never know, what you can reach, how big your power is,
until you try it:))
Dietmar
PS: I have done the experience in Mathematics, that when you try to explain to somebody a very complex Thema,
(I work in my free time on the Riemann Hypothesis, got already an amazing advantage there),
you have to rethink the whole process and at the end you are much better than before.
And the person, who listens carefull to you, at once tells you new ideas, you never had alone.
And even this may be a really hard work, you do not feel this..

#4698

diderius6

⇗ @daniel_k
First result for the Samsung nvme is, that this driver works with the for nvme patched version of storport from Win8.1.
This is very important, because this storport is generic as much as possible and works with all STORAHCI drivers.
With the storport.sys vers. 4173 from Server 2003, this nvme driver does not work.
With the patched storport from Win7.1 this Samsung nvme does not work, gives Code 10
Dietmar
PS: First I test the Samsung nvme driver on a 970 pro 1 TB from Samsung.
Some time ago, I heard, that from Samsung there was a Trim tool, which works under XP.
But I never got it.

#4699

Andalu

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4689

> Patch to fix yellow mark with Code 31 for UAS Driver (Windows 8 backport):
> change stor_uas.sys in folder storport_w8 and storport_w2003:
> 1) 65005C00520061006900640050006F00 => 65005C00550061007300700050006F00
> 2) recalc cheksum

The UAS mass storage devices are always correctly recognized in all conditions now. Many thanks ;)
Twice I still got the BSOD 0xC2 during the Crystalmark testing. Between yesterday and today already four times ... a little too much.
I'll try to change the benchmarking program's version.
The benchmarking tests for my 970evo mounted on the nvme to usb3 adapter are similar for both driver versions:
on the left the uaspstor.w8 - on the right the uaspstor.w2003
⇗ ⇗

#4700

daniel_k

> Zitat von ⇗ diderius6 im Beitrag ¶ #4698

> With the patched storport from Win7.1 this Samsung nvme does not work, gives Code 10

Didn't you make a mistake?
It works with my storport.w7 here.

#4701 | daniel_k | ⇗ @Andalu Just to confirm, with the standard Mass Storage driver (no UAS), there are no issues at all?

#4702

Mov AX, 0xDEAD

> Zitat von ⇗ diderius6 im Beitrag ¶ #4695

> Nice would be, to have a Tutorial and all the names of the used tools,
> for backporting the nvme driver from Win7.1 to XP SP3.
> Via this way, everybody can make some experiments for himself and

I dont think that someone after reading any guide can change logic/loading of the any driver
Нужны знания сразу в нескольких областях чтобы уметь преодолевать постоянно возникающие проблемы, из минимального нужно знать и уметь:
- редактирование PE файлов (секции, где хранятся в файле, как загружаются в память, адресация секций процессором, таблица "релоков")
- как устроены записии в секции import, как они меняются после загрузки драйвера
- базовые инструкции i386
- какие существуют варианты инструкций CALL и JMP и как они "работают"
- варианты передачи аргументов в стек и выравнивание стека
- умение пользоваться документацией DDK Win7/Win8
- знать хотя бы в общих чертах какие новые механизмы появлятся в новых ядрах/драйверах, например что такое MSI или ETW и как без этого можно обойтись в XP
Ну и самое главное - уметь создавать эмуляцию функций, которых нет в ядре XP, иногда это просто копирование существующего asm кода из новых ядер win7/8, а иногда нет такого кода в принципе и его нужно сочинять "с нуля"

#4703

diderius6

⇗ @daniel_k
I will recheck but I am sure, that everything is, as I wrote.
Here are the benchmarks: On the left is Intel Optane 905P and on the right is Samung 970 pro 1TB.
One thing is the same as 2 years ago, when I make intensive tests with the OFA drivers:
The Optane drive shows always the same values, no matter if you copy hours of large files.
BUT: All other nvme disks show a very bad result. After 10 min of copieing large files, the read and write rate goes down as much as possible and when you do not give them short time for to get fresh air, in the end a normal harddisk is much faster than any of this nvme disks, that I tested! Because of this, I put all nvme disks out of my compis and only the Optane device stays
Dietmar
PS: This test is representativ. This values you get as a middle of 10 times running the diskmark test.
⇗

#4704 | diderius6 | ⇗ @Mov AX, 0xDEAD Thank you very much for the explanation. My idea was, to write a step by step tutorial only for the nvme.sys backport. And when somebody has really interest, at once this Tutorial can be used for to do next steps alone Dietmar

#4705

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #4701

> @Andalu
> Just to confirm, with the standard Mass Storage driver (no UAS), there are no issues at all?

Until now no issue with the 'classic' mass storage devices, tried also with an UAS device connected.
Should I try something specific?

#4706 | diderius6 | ⇗ @Andalu Until now, I do not succeed to boot XP with the uaspstor.sys driver. And no idea, why not^^ Dietmar
#4707 | daniel_k | ⇗ @diderius6 Samsung NVME driver works with the Intel Optane?

#4708

diderius6

⇗ @daniel_k
yeppp, and works there much better than with their own product:)). Optane nvme disks are simple the best,
but expensive.
I just recheck all different versions of storport that I have.
ONLY the storport with nvme patch from 8.1 works for the Samsung nvme driver.
It is stable. And this are very good news, because this storport.sys is already integrated in the
XP Setup CD from ⇗ @Outbreaker
Dietmar

#4709 | daniel_k | ⇗ @diderius6 Good to know and insane at the same time! Samsung provides a generic NVME driver? Who would imagine that?! So, what's the best driver in your opinion (speed and stability)? OFA, MS or Samsung?

#4710

diderius6

⇗ @daniel_k
Not so easy to say. I still do not give up hope, to build from the OFA source code an nvme driver,
which supports trim under XP. And to make a scsiport based nvme as ntbootdd.sys from it.
But this may be crazy hard work.
Both your backported nvme drivers are stable. I do not have any crash.
So, from generic aspect I would chose the Samsung nvme driver.
But until now, I have not done enough tests for to make a decision
and in the end all of the nvme drivers for XP are nice
Dietmar
PS: The diskmark values for the speed of an nvme disk say nearly nothing.
They are all very fast. But with heavy load, all nvme disks show speed less than a harddisk.
Only the Optane nvme disks can keep there full power for hours.

## Page 315

#4711 | daniel_k | ⇗ @diderius6 I remember you had a problematic Toshiba NVME. Do you still have it? If you do, please the MS and Samsung drivers with it.

#4712

diderius6

Here are the benchmarks for the Toshiba RD400 nvme device, which was one of the very first. All work under XP SP3.
On left is OFA 1.3 middle Microsoft and right is Samsung.
As you can see, the OFA 1.3 driver is the fastest.
All driver work without any problem, just stable on the Toshiba RD400. Problem have been with the OFA 1.5 driver (here not tested).
This may depend on the nvme version of the Toshiba RD400 device. I think it is 1.0e and later nvme devices are 1.2
Dietmar
⇗

#4713

diderius6

I just boot XP SP3 from the Optane 905P with the Samsung nvme driver from ⇗ @daniel_k .
So, via storport.sys from 8.1 with nvme patch,
this is really generic and this storport.sys can be used for all the programs that use the storport.sys 4173 from Server2003
Dietmar

#4714

Andalu

⇗ @diderius6 ⇗ @daniel_k
I'm sorry for the delay in my reply.
I tried both OFA 1.3 and samsung nvme drivers (the ms driver fails to install on my system).
Here the benchmarking tests for my 970 evo nvme with XP installed and storport.sys from from Windows 8.0 RTM:
⇗ ⇗

#4715 | canonkong | ⇗ @daniel_k Both Samsung and Intel nvme drivers can be used as general nvme drivers. For hard disks without official nvme drivers, Samsung or Intel nvme drivers can be used.

#4716

canonkong

I tested the latest usb3.2 gen2x2 expansion card. The win8 portable driver can drive it perfectly, and it works normally, and the uasp function is no problem. Because there is no 20Gbps USB storage device on the market, I can only test with 10Gbps USB storage device. Even for 10Gbps devices, it is obvious that the test result of usb3.2 gen2x2 20Gbps card is faster than that of usb3.2 Gen2 10Gbps card, especially the continuous write speed.
⇗

#4717 | Mov AX, 0xDEAD | ⇗ @Andalu, ⇗ @diderius6 don't mess with "storport.sys from 8.1", only storport.sys from Windows 8.0 RTM and Windows 7 exist
#4718 | Andalu | ⇗ @Mov AX, 0xDEAD edited post, sorry for the mistake.

#4719

Andalu

Here the benchmarks for my nvme disks connected on the slot m.2 with the MS nvme driver thanks to @daniel_k.
XP booted from my crucial SSD.
Samsung 970 evo nvme:
⇗
Sabrent rocket nvme:
⇗

#4720 | Andalu | Here the benchmark for my crucial BX300 SSD with the Intel RSTe_4.7.0.1117 driver. ⇗
#4721 | daniel_k | ⇗ @Andalu Is it caching or something? Crazy results. Do you have timer patch installed?
#4722 | Andalu | ⇗ @daniel_k do I need to install the timer patch necessarily? I'm trying with the write cache disabled.
#4723 | ruthan | ⇗ @Andalu all are useless, nonsense numbers.. probably because of broken timer..

#4724

Andalu

Write caching disabled on the sabrent nvme.
⇗ ⇗
⇗ @ruthan
about the timer, can be enough these 2 shots?
I don't think the tests are useless at all since a change in the XP settings can be an useful information for other members reading as well.
edit: I forgot to report that PAE is not enabled and the hal.dll is the unmodified version 5512 as from SHA-1 reported.

#4725 | daniel_k | ⇗ @Andalu If timer is not the issues, something else is wrong. What are your system specs?

## Page 316

#4726

Andalu

⇗ @daniel_k
my system: Asus Prime Q370M-C/CSM - i5 8400 - 64GB of ram - integrated VGA - Crucial BX300 SSD and Samsung 970 evo nvme. Nothing else.
The strange results happen only with the MS nvme driver + Intel RSTe_4.7.0.1117 sata driver (today I also got an iastof.sys BSOD using the ramdisk software).
With the samsung nvme driver the results seem to be normal.

#4727 | daniel_k | ⇗ @Andalu There is something wrong with storport.w7? But this doesn't happen for ⇗ @diderius6?! He'll test the latest patch, lets wait for his reports.

#4728

diderius6

⇗ @daniel_k
I just make a test with the PAE patch from Daniel, so now the compi has 32 GByte.
This value is only correct shown with the Samsung nvme. I boot XP from OFA 1.3, Microsoft nvme Win7.1, Samsung nvme Win10(?).
The Samsung nvme has a filter driver secnvmeF.sys, which should enable NVME_PASS_THROUGH .
This gives information about the nvme disk, but I dont find anything if this is also good for Trim. Until now no tool under XP for Trim of an nvme device.
I noticed, that Daniel modded his last storport.sys from Win7.1. It makes the nvme driver from Microsoft a little bit faster.
All nvme drivers are stable for me. But only for the Intel Optane, the values that CristalDiskmark shows, are always the same.
On the left is OFA 1.3, always the fastest, in the middle is Microsoft nvme by ⇗ @daniel_k and on the right is the brandnew(?) Samsung nvme driver also with mod from Daniel. All nvme devices are faster with 32 Gbyte ram than with 4GB ram.
The test values are correct, valide for the Intel Optane 905P.
⇗

#4729 | Andalu | ⇗ @daniel_k with a ramdisk drive, Crystaldisk went into crisis, it will never have tested anything like it ⇗
#4730 | daniel_k | ⇗ @diderius6 Samsung NVME driver for Win7.
#4731 | daniel_k | ⇗ @diderius6 Did you try my storport.W7 with Samsung or OFA driver?

#4732

diderius6

⇗ @daniel_k
Waaaooh, your new storport.sys from Win 7.1 works now also with the OFA 1.3 nvme
driver,
in this moment is running benchmark:))
Dietmar
EDIT: For the OFA 1.3 driver, the benchmarks for storport from win7.1 or for storport from win8 are nearly exact the same.
EDIT2: The same is true for the Samsung nvme with its filterdriver. Hi Daniel, seems, that you are getting better every day:))!
I want Tutorial how to mod the nvme.sys!!!

#4733 | Andalu | ⇗ @daniel_k even changing the system, the results are similar: ⇗

#4734

daniel_k

⇗ @diderius6
What about the Samsung driver? Does it work with storport.w7?
⇗ @Andalu
That's odd, it seems to benchmark cached memory area.
Why does it happen to you and not for ⇗ @diderius6?
EDIT: What about SSDs? Are they affected by this behavior?

#4735

diderius6

⇗ @daniel_k
Your new storport.sys from win7.1 works for all nvme.sys drivers,
that are today on the market for XP.
The generic for nvme modded storport from win8,
still works not on the Microsoft nvme
Dietmar

#4736 | daniel_k | ⇗ @diderius6 That's great, however I'm getting crashes here! PAE is enabled? Please confirm SHA-1: 3487593D540EC4D4B21EA7FA8B16212C77C9818A
#4737 | Andalu | ⇗ @daniel_k also for my SSD the results are weird: ¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (315)
#4738 | daniel_k | ⇗ @Andalu Are you using the storport.sys with the hash above?
#4739 | Andalu | ⇗ @daniel_k of course!! (I hope to not have to upload another image also for that ) edit: see you later, sorry :(

#4740

daniel_k

⇗ @Andalu, ⇗ @diderius6 and ⇗ @Mov AX, 0xDEAD
Sorry for the confusion, it was my fault.
There was a corrupted usbxhci.sys which was causing random crashes.
storport.w7 works just fine, thankfully!
So, we've got them all:
- Generic MS Generic XHCI/USB3 driver
- Generic MS Generic/Samsung NVME driver
- Generic/Intel/AMD AHCI driver
- ACPI driver (needs improvements)
- UASP driver (needs more fixes?)
I think we are almost done.

## Page 317

#4741 | diderius6 | ⇗ @daniel_k The SHA-1 match your last modded storport.sys from win7.1. No crash at all. Yes, I have PAE enabled, 31.9 Gbyte I can see Dietmar
#4742 | daniel_k | Can someone please explain those crazy bench results ⇗ @Andalu is getting? If it isn't a timer issue, what could it be?!
#4743 | diderius6 | The nvme driver modded by ⇗ @daniel_k from Microsoft and the one from Samsung can both boot XP SP3 from the old Toshiba RD400 nvme disk. So, they are more generic than the OFA 1.5 driver modded for XP, because there XP hangs during boot Dietmar
#4744 | diderius6 | ⇗ @Andalu May be, that the problem goes to a loaded uaspstor.sys instead of usbstor.sys Dietmar
#4745 | Andalu | ⇗ @diderius6 uaspstor.sys is not present in my system now. I'm using the nvme driver from win7 and the Intel RSTe_4.7.0.1117 sata driver. Could you please explain how you conduct the tests? which version of XP are you using, which acpi.sys, if you have applied the hal timer patch, if you have disabled write caching etc. so I can try a common way in benchmarking.

#4746

diderius6

I have a generic german XP SP3 with all updates that I found in last years.
This XP SP3 runs on any compi:)). With boot.ini I can chose between MPS, acpi, acpi with PAE, acpi Debug and MPS debug. All with different hal.
I have no good memories at the RSTe_4.7.0.1117 sata driver.
Make a try with the driver from Skullteria or try to install the nice XP SP3 version from
⇗ https://www.zone62.com/downloads/softwar...comment_id=2220
Dietmar
PS: acpi.sys I can boot with original, with acpi.sys from outer space ) and with very last acpi.sys 5048.
The new nvme drivers are always stable. I have this XP on Optane nvme disk, on harddisk, on harddisk in USB encloser, on Samsung 970 pro, on Samsung SSD, on the Toshiba RD400 now,
and on about 20 other harddisks.

#4747 | daniel_k | ⇗ @Andalu A quick and dirty way to test other drivers are simply rename and overwrite the main driver file. For example, rename storahci.sys to iastora.sys and overwrite the file in the ISO. The filter driver is harmless.

#4748

diderius6

⇗ @Andalu
For tests I think is the very best a fresh installed XP. And before first test, make a copy of this XP, that you always have at start the same situation again
Dietmar
PS: Always to have the same fresh XP as before you can also do, when you copy the folder \System32
from an outstanding XP to a safe place. And then, just copy this folder System32 back.

#4749

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #4733

> even changing the system, the results are similar

There is only two answers - Caching or Timing
On WinTimerTester screen you use acpi timer (3.15Mhz), which is not disabled (enabled in bios ?)
So probably CrystalDiskMark can't disable caching when access logical disk on NVMe

#4750

Andalu

⇗ @Mov AX, 0xDEAD
even if on a different XP installation (XP-IE 2020.05.05)
but with the same acpi.sys version, I have no strange results with both OFA 1.3 and samsung nvme drivers:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (315)
⇗ @daniel_k ⇗ @diderius6
thanks for the tips

#4751 | ruthan | Crystal Mark is not only benchmark you can try other one, if results are different, or when you just copy the file, speed has to be different too.

#4752

Mov AX, 0xDEAD

> Zitat von ⇗ Andalu im Beitrag ¶ #4745

> @diderius6
> uaspstor.sys is not present in my system now. I'm using the nvme driver from win7 and the Intel RSTe_4.7.0.1117 sata driver.

uaspstor.sys uses stor_uas.sys(renamed storport_w8/w2003 with special patch) as storport.sys
nvme_w7 uses storport_w7 as storport.sys
RSTe_4.7.0.1117 uses storport_w7 as storport.sys
You need temporary change RSTe_4.7.0.1117 to other "nonstorport" driver to exclude interference with common storport.sys and repeat performance test
Disk drivers also live at CriticalDeviceDatabase and can be loaded even controller controlled by other driver, so need remove iastorA from this registry too
Dont forget to backup system32/config before changing boot disk driver

#4753

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4740

> @Mov AX, 0xDEAD
> - UASP driver (needs more fixes?)

Only one issue was found in UASP and already fixed, no more know issues
UASP driver can work with storport_w2003 or storport_w8, i dont tested uasp with storport_w7 yet, but will do and will report

#4754

Andalu

⇗ @Mov AX, 0xDEAD
another good tip, thanks ;)
I re-started with the safe stuff :), firstly I used my old, not updated Italian ISO. Then I did the bench for my Sabrent nvme first with the OFA 1.3 driver (on the left) and then with the nvme driver from Win7 (on the right). Write cache disabled:
⇗ ⇗
Not exciting results but, at least, the way seems to be the right one.
Now I have to change the sata drivers, hoping that the system won't give me a blank screen on reboot.

#4755

Andalu

Finally I got the real results for my Sabrent nvme with both nvme driver from win7 and RSTe 4.7.0.1117 sata driver:
⇗ ⇗
the results are better with the OFA 1.3 even in this case.
The next step will be to find a way to make work the storahci.w8 with the MS nvme driver.
I already got the 0x019 BSOD for three times.

## Page 318

#4756

ruthan

Ok im ready to debug with Z390 and existing installation, i just replaced and acpi.sys (to fix 005 bluescreen) and have to connect booting disk to Marwell Sata controller (driver was already installed with older MB) to fix 007 boot problem, otherwise i would have to use some Sata controler with IDE non AHCI mode. PS2 mouse and keyboard is working. BTW i dunno why but PS2 and mouse keyboard is working with all OSes except Win10 where only keyboard is working..
My problem so far, is that i see only 1 GB of 32 GB of mem in WinXP, so far, im no using any fixed hals.
Now i have to make make working more devices:
1) Intel Sata, i hope that generic drivers as older Fernando will work with Paragon GPT driver - i have main data as games on big GPT disks.
2) Addon Nec USB3
3) Intel USB3
4) Realtek USB Lan..
5) On board NVME if possible, i just would like to have possiblity read some files from other OSes..
After that "real" fan will start, 2nd WinXP GPU and bios profile. I tested in on Z370 machine, there is this working, but i have not local input, because of not working PS2 for some reason (maybe something wrong with custom bios from Daniel) and i have to test newer USB3 drivers for it, i also waited few months for PCI-E USB2 controller, but it never arrrived, so i would have to reorder it.

#4757

Mov AX, 0xDEAD

Hi,
My tests with storport_w7 by ⇗ @daniel_k:
- Power irp deadlock with uaspstor still occur, still need special version of storport
- uaspstor_w8+storport_w7 doesnt work because uaspstor_w8 uses storportextendedfunctions above 25
- uaspstor_w2003+storport_w7 work, need one-byte patch to avoid deadlock
- Storahci_w8+storport_w7 doesnt work because storahci_w8 uses storportextendedfunctions above 25
To coexist different versions of storport need:
1) rename storport.sys to stor_xxx.sys or xxx_stor.sys
2) in stor_xxx.sys change unicode "\Device\RaidPort%d" to unique string, like "\Device\UaspPort%d" or "\Device\NVMePort%d"

#4758 | canonkong | @Mov AX, 0xDEAD Maybe we can use VIA its UASP driver, it can support Xp/vista/win7 32/64bit and also can work well.

#4759

Mov AX, 0xDEAD

⇗ @canonkong

> Zitat von ⇗ canonkong im Beitrag ¶ #4758

> Maybe we can use VIA its UASP driver, it can support Xp/vista/win7 32/64bit and also can work well.

I wrote about important issue with VIA UASP driver on first page of topic, no fix at current moment

#4760 | canonkong | @Mov AX, 0xDEAD I used VIA UAS Driver on win7, it can support Safe Remove and work well. Maybe it needs to fix on Xp.

#4761

Mov AX, 0xDEAD

> Zitat von ⇗ canonkong im Beitrag ¶ #4760

> @Mov AX, 0xDEAD
> I used VIA UAS Driver on win7, it can support Safe Remove and work well. Maybe it needs to fix on Xp.

Win7 has other ways to recognize removable disks, WinXP depends only on driver and via driver say "no need safe removal"
Maybe this is OK, but if caching write is On we will get problem

#4762

daniel_k

⇗ @Mov AX, 0xDEAD
If stornvme.w7 + storport.w7 works on VirtualBox.
Can't you debug stornvme.w7 + storport.w8? Or maybe storport.w8 require an update like w7 had to support NVME?
What about porting storport.w81 as an all-in-one solution? I know you don't even have NVME, just asking.
Or even hacking ASMedia UASP?

#4763 | daniel_k | ⇗ @Andalu When you have some spare time, please test W7 with the NVME hotfix/driver, so we can compare performance against XP. That would be interesting.

#4764

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4761

> WinXP depends only on driver and via driver say "no need safe removal"

⇗ @Mov AX, 0xDEAD ...I remove it safely in XP anyway using Administrative Tools\Computer Management\Disk Management. Had a problem once with a sudden removal where the voltage transient caused by sudden removal may have written to the USB thumb drive, making it unreadable. I go into Disk Management, right click the thumb drive or USB external drive, and use Eject or Offline.
You might notice with a USB external drive that the drive light is still on even after safe removal while the drive is still plugged into a USB port. That means when you unplug the drive there is a possible voltage transient. Hopefully the heads are parked after safe removal but if they are not the heads can write to disk as the drive is unplugged from the USB port. That's because after the plug is pulled, with voltages turned on, the digital electronics is no longer synchronized to a clock and the circuits can do strange things. You can get around that by leaving the drive plugged in, if possible, and powering the computer down.
None of this is likely but after years in electronics/computers I have seen everything...almost.

#4765

XPLives

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #4670

> @diderius6
> Are you going to be the first one here to try XP on Intel 10th gen?

No, that would be me. But Did6 would get the overpriced XP compatible EVGA Z490 Dark.
Go with the cheapest 10th Gen CPU for testing. Then upgrade to the flagship 11th Gen CPU to max out the chipset.
Though money should be spent on Sapphire Rapids.
Still waiting for DDR5 and PCIe v5.0 before a full upgrade with 512GB or 1TB RAM.
Just like Ruthan, I'd wait till low wattage 12 or 16 Core 65 Watt Intel CPUs are released. I hate fans.

> Zitat von ⇗ daniel_k im Beitrag ¶ #4670

> @diderius6
> Interesting, Intel planned to remove CSM by 2020, but all Z490 BIOSes still have it.
> Good for us!

As for the talk of the BIOS's early demise, it won't happen just yet. Too many legacy users like ourselves pushing to keep it alive. Worst case Asus and AsRock would still carry legacy BIOS motherboards but probably charge more but produce less quantity.
And then you have AMD who may keep the BIOS alive if this is just an Intel push.
Daniel_K, nice to see another Asian back along with MOV AX back after the reported last posting. Just like the Creative Labs incident don't give up the fight.
XPLives

#4766

XPLives

⇗ @Mov AX, 0xDEAD

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4595

> Little survey:
> I'd like to hear from Forum Users what XP issues are most critical to you today ?

Off the top of my head the most critical and maybe most useful to add to XP functionality for modern purposes.
Probably ACPI.sys for Windows 2000 SP0 and XP SP0 to work on SkyLake+ generations.
>4GB memory application usage not in 4GB chunks found in Server 2003 Advanced Server 32-Bit with max memory expanded from 64GB to 256GB memory support.
Or a way to use Server 2003 Advanced Server 64-Bit memory support might be better. The idea is OS base memory not stuck at 3.2->4.0GB limit per process but expanded to 8.0GB/16.0GB/32.0GB which would be plenty or the entire 256GB.
4KB to 512 Byte Sector Translation native to allow Windows 2000 SP0 and XP SP to boot to internal drive up to 16TiB MBR. No need for GPT.
Windows 2000 SP0 and XP SP0 OS USB Bootable or off storage device so OS loaded entirely into RAM Drive. No need to wear out any UFD, SSD, or Hard drive.
Intel USB 3.0 stable XP driver can be installed on Windows 2000 SP0 and XP SP0.
NVME driver for Windows 2000 SP0 and XP SP0.

#4767

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #4763

> @Andalu
> When you have some spare time, please test W7 with the NVME hotfix/driver, so we can compare performance against XP.
> That would be interesting.

Here the results for the 970evo nvme with the samsung driver on Win7 just installed:
⇗
I am also posting those related to XP although aware that there is still something strange (I think due to the hal.dll of which I am still looking for the best version for all situations):
⇗

#4768 | daniel_k | ⇗ @Andalu Thanks for the benchs, always appreciated! You're using my patcher, right? If you do, it does automatically apply the timer fix. By the way, hal.dll is not protected by WFP (Windows File Protection).
#4769 | Andalu | ⇗ @daniel_k of course, your nice WinXPPae patch2. WFP is disabled by default.
#4770 | ruthan | ⇗ @Andalu Win 7 write performance should be higher.. Win XP data seems to be more accurate now.

## Page 319

#4771 | daniel_k | ⇗ @Andalu Run CPU-Z -> About tab -> Timers Please post a screnshot of the timers.
#4772 | Andalu | ⇗ @daniel_k that's here: ⇗
#4773 | Andalu | ⇗ @ruthan I had seen the lower results in W7. No substantial differences on three benchmarking tests.

#4774

daniel_k

⇗ @Andalu
There is nothing wrong with the timers.
Is it a clean install of Win7 just for testing?
If so, mind to install the NVME hotfix and run a bench, please?
NVME hotfix KB2990941
Then install KB3125574, as it includes updated NVME/Storport as pointed out by ⇗ @Mov AX, 0xDEAD

#4775

Andalu

⇗ @daniel_k
unfortunately my HDD with W7 is dead some week ago and I never installed it.
I forgot to install the SP2 and the hotfix.
About the timer, in the bios there is no HPET settings, only the "System time and alarm source" now configured on "ACPI time and alarm device" but I have already changed it to "Legacy RTC"
without success.

#4776

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4775

> @daniel_k
> unfortunately my HDD with W7 is dead some week ago and I never installed it.
> I forgot to install the 2 hotfixes.

What a shame that it died.

> Zitat

> About the timer, in the bios there is no HPET settings, only the "System time and alarm source" now configured on "ACPI time and alarm device" but I have already changed it to "Legacy RTC"
> but nothing changed.

Did you check the timers in CPU-Z after changing it to Legacy RTC?

#4777

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #4776

> Did you check the timers in CPU-Z after changing it to Legacy RTC?

Yesterday I tried almost everything: 3 different XP images, 3 SDD, 2 HDD, 2 nvme and, at end, also by updating the bios without success .... I was going to go crazy
However, I just re-checked changing the "System time and alarm source" setting in "Legacy RTC" but the timers visualized in CPU-Z are indentical as before.
The last thing to try should be the dsdt table but here I can't do nothing.

> Zitat von ⇗ daniel_k im Beitrag ¶ #4776

> What a shame that it died.

The worst thing is that I can no longer find the image partiton with W7 installed

#4778 | daniel_k | ⇗ @Andalu No need to mess with those timers if nothing changes, thanks for all the testing.
#4779 | daniel_k | ⇗ @Mov AX, 0xDEAD Interesting, on VirtualBox, MS NVME W7 driver only loads at first VM initialization. If you restart Windows, NVME won't start with an error code 10. Samsung NVME starts all the time.
#4780 | infuscomus | ⇗ @Andalu I'm just guessing here, but perhaps the "Legacy RTC" option in your BIOS isn't actually implemented in your BIOS? or implemented incorrectly? can you try "ACPI Time" or one of the other options listed in your BIOS, along with a patched hal.dll? see if that behaves correctly?
#4781 | Andalu | ⇗ @daniel_k for information only. Even with Windows7 updated the results seem to be similar to the previous ones: ⇗ Here with the MS nvme driver: ⇗

#4782

Andalu

> Zitat von ⇗ infuscomus im Beitrag ¶ #4780

> @Andalu
> I'm just guessing here, but perhaps the "Legacy RTC" option in your BIOS isn't actually implemented in your BIOS? or implemented incorrectly?
> can you try "ACPI Time" or one of the other options listed in your BIOS, along with a patched hal.dll? see if that behaves correctly?

I don't know how to see if the enabled "Legacy RTC" option is then actually applied in a correct way. There are no other settings in the bios that can be related to the timer.
Asus bios do not seem to be the best around. The hal.dll is already the patched version by WinXPPae2. No difference if replaced with another patched version.

#4783

daniel_k

Ported AHCI driver from Windows 7.
Needs some improvements as it conflicts with Standard IDE controller (if there is one installed).
Interesting that this driver supports TRIM, initializes really fast and is not a SCSI driver.
Tried to completely replace XP IDE drivers, but it crashes.
⇗

#4784

Doc.Brown

> Zitat von ⇗ XPLives im Beitrag ¶ #4765

> @daniel_k

> > Zitat von ⇗ daniel_k im Beitrag ¶ #4670

> > @diderius6
> > Are you going to be the first one here to try XP on Intel 10th gen?

> No, that would be me. But Did6 would get the overpriced XP compatible EVGA Z490 Dark.
> Go with the cheapest 10th Gen CPU for testing. Then upgrade to the flagship 11th Gen CPU to max out the chipset.
> Though money should be spent on Sapphire Rapids.
> Still waiting for DDR5 and PCIe v5.0 before a full upgrade with 512GB or 1TB RAM.
> Just like Ruthan, I'd wait till low wattage 12 or 16 Core 65 Watt Intel CPUs are released. I hate fans.

Seems XP works well for this new gen and without big problems if you look at this guide ⇗ https://community.hwbot.org/topic/196740-rog-maximus-xii-apex/
Some great overclockers submit great result with it also : ⇗ https://hwbot.org/submission/4446037_safedisk_superpi___32m_core_i9_10900k_4min_1sec_766ms

#4785

Andalu

⇗ @daniel_k
here are the new benchmarks for my 970evo nvme with both samsung and MS driver in windows7, this time with write cache enabled.
For those of yesterday it was disabled as displayed in the screenshots
Samsung driver (better):
⇗
MS driver:
⇗

## Page 320

#4786

daniel_k

⇗ @Andalu
Thanks, much appreciated!
Beware of benchmarking SSDs/NVMEs all the time, as the lifespan decreases with all those writes.
Samsung and OFA drivers are definitively faster, but for general use (at least during install), I'd stick with the MS ones.
Results on XP are always lower than Win7, probably expected as the later's kernel is optimized for newer systems.
Generic drivers are more compatible and reliable: Mov AX, 0xDEAD's XHCI driver proved this.
As I've said before, usually vendor specific drivers have hacks that may break functionality on other vendor's hardware.

#4787

daniel_k

⇗ @diderius6
Found something interesting.
Wrong device class affects functionality of drivers: with the current INF file, only the first device's SMART data can be read.
After changing the class code to SCSI and RAID Controllers, SMART atributes for all devices are available.
Device class in INF file for storahci is wrong:

    Class=hdc
    ClassGuid={4D36E96A-E325-11CE-BFC1-08002BE10318}

should be:

    Class=SCSIAdapter
    ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}

This is also true for RSTe drivers.
Please confirm this behavior on your systems.

#4788

diderius6

Hi ⇗ @daniel_k
I take a look at the original definition from Microsoft. They wrote that only this correct
SCSI and RAID Controllers
Class = SCSIAdapter
ClassGuid = {4d36e97b-e325-11ce-bfc1-08002be10318}
This class includes SCSI HBAs (Host Bus Adapters) and disk-array controllers.
Dietmar

#4789 | canonkong | It is working very well on B460+i5-10400... ⇗

#4790

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4787

> After changing the class code to SCSI and RAID Controllers, SMART atributes for all devices are available.

my storahci_w8 has this fault, I did not think that it matters )
historically ide/sata controlers were in the HDC class on old OSes

#4791

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4790

> my storahci_w8 has this fault, I did not think that it matters )
> historically ide/sata controlers were in the HDC class on old OSes

Yep, that is ridiculous that a class/GUID would change the behavior of a device.
I was about to bother you about an issue with my ported IDE/AHCI, but I fixed it myself after some thinking/reading.
At first, thought I did some mistake, but after porting the x64 version, gave me the same errors.
Will put everything together and send you a PM later, in case you want to take a look at it/try it.
Complete replacement of original XP IDE plus AHCI supporting TRIM/STANDBY IMMEDIATE in IDE and AHCI mode!

#4792

ruthan

I used it for some retro stuff.. but here is some nice tool to inject drivers to existing installation to make it bootable, its working from Win2000 to Vista for other Windows, computer, where disk is connected.
It has simple option to force use generic IDE drivers or import other drivers.
⇗ https://msfn.org/board/topic/181561-retr...comment-1182472
I now that before was possible to make same thing with some Regedit hive editing, but this is really simple GUI tool.. Hive is in Windows\System32\config

#4793 | canonkong | After testing for days, I am sure it is a very stable USB driver. USB card from ASMedia, VIA, NEC, TI, Etron chips all on the same mainboard together. ⇗ ⇗
#4794 | Andalu | ⇗ @canonkong If I'm not wrong, the only chipset that seems missing is the Fresco Logic, so I'm adding it :) here working in XP on a haswell board: ⇗ It works much better than the FL driver.

#4795

canonkong

@ Andalu
It can not support Fresco Logic Decive ID like:
ExcludeID=PCI\VEN_1B73&DEV_1000
ExcludeID=PCI\VEN_1B73&DEV_1400
ExcludeID=PCI\VEN_1B73&DEV_1009
But it can work for PCI\VEN_1B73&DEV_1100

#4796 | daniel_k | ⇗ @Andalu I remember you had an issue getting USB2 speeds even with XHCI enabled in BIOS. Did you try this W8 XHCI driver on that mobo to see if USB3 is properly enabled?
#4797 | daniel_k | ⇗ @canonkong What a massive and crazy testing machine you've got! Impressivel! This is real proper testing.

#4798

Andalu

⇗ @daniel_k
the 'crazy' motherboard was a B75 Ivy Bridge. Here are the sceeenshots for Ivy Bridge, Haswell and Coffee Lake boards:
Benchmarking a toshiba USB3 external hard disk drive 2TB
B75 Ivy Bridge
⇗
H97 Haswell
⇗
Q370 Coffee Lake (even with the write cache enabled the results are similar):
⇗

#4799 | Andalu | ⇗ @canonkong that's good to know ;) I was lucky to choose a card with the FL1100 chipset (but only thanks to the advice from ⇗ @daniel_k )
#4800 | infuscomus | ⇗ @canonkong So many slots!! where can I find a motherboard like that?

## Page 321

#4801 | canonkong | ⇗ @infuscomus It is ASRock H110 PRO BTC+ mainboard, it has 13 PCI-E slots, cost $40 USD on taobao.
#4802 | daniel_k | ⇗ @Andalu Thanks for the benchs. As I was expecting, the W8 XHCI drivers enables true USB3 speeds without any stupid "switch" driver. Just great!

#4803

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4802

> As I was expecting, the W8 XHCI drivers enables true USB3 speeds without any stupid "switch" driver. Just great!

I dont sure about old PantherPoint intel controllers (devid=1E31), they has ehci and xhci as separate controllers connected to same usb2 pins
BeOS(Haiku) usb3 driver has hack to switch ports
I have this controller on lenovo notebook, but never used it with win8. On WinXP usb3 controller was hidden by ACPI DSDT Code

#4804 | Andalu | ⇗ @Mov AX, 0xDEAD for both my B75 boards (DEV_1E31) it was necessary to apply the WPCRset trick as for the AMD XHCI driver.

#4805

ruthan

I had time to mess with XP existing installation porting on Z390:
What is good:
- from tree things which are making working system (Accelered graphics, Audio and Network), i have 1 - realtek HD audio is working. BTW are you using USB Lan adapters, or addon PCI-E cards?
- marwell Sata controller is working fine, im using some Asus 2015 driver - real driver is from 2011, i tried drivers from Win-Raid, from 2013, but i got 007B boot error
What is not good so far:
- RAM even when i installed Win-PAE-patch /4G i still have only 1GB of RAM, i dunno why.. im using 8 GB video card for 2D windows WinXP drivers, i need make other things working before i will add second XP videocard and i will mess with input switch and bios profiles. My CPU has not iGPU at all, in bios is reserved just 128 MB for iGPU.
Im using just patched hal from halplusintelppmXPSP3, not any special boot.ini hal files settings etc.
⇗
- NVME, i tried both drivers 1.3 and 1.5, but always getting Code 10, even after reboot. intelppm.sys and storport.sys where copied to system before installation.
⇗
- USB, i installed AMDXHCI XP 276-Final v3 driver.. USB3 controller fine, USB3 hub fine.. after that some AMD USB2 hubs starting to be detected - again with code 10 - i dunno if its typical or because i have some USB2 drivers in my monitors and some external USB2 and USB3 hubs.. And some devices as Web Cam where recognized.
After reboot - and WinXP loading screen, i got just black screen, after that my USB keyboard and mouse led starting lit what means that were somehow initialized, after that minute light is gone, screen is still black. I tried to use: amdxhc.sys and halmacpi.dll from PAE workaround folder - but its the same.
⇗
Otherwise i saw in package, SSE2 Updates Rollback folder, what it is for and how to use?

#4806 | infuscomus | ⇗ @ruthan this might be ACPI related - have you tried the modded ACPI driver?

#4807

diderius6

I just succeed to solve an crazy error about direct nvme boot Setup with BSOD 0x7B on the nice XP SP3 Setup CD at
⇗ https://www.zone62.com/downloads/softwar...comment_id=2220
I change WINNT.SIF in the i386 Setup folder and also in OEM folder the same to WINNT.SIF.backup with following content
Dietmar
; SetupMgrTag
[Data]
MsDosInitiated=0
[Unattended]
NonDriverSigningPolicy="Ignore"
DriverSigningPolicy="Ignore"
;FUI#[Unattended]
;FUI# Repartition=No
;FUI# WaitForReboot=No
;FUI# OemSkipEula=Yes
[GuiUnattended]
AdminPassword="*"
TimeZone=020
[UserData]
ProductKey=PD9WR-BDGBK-RPXKR-W3CK4-QHYF3
ComputerName=*
FullName="Unknown User"
OrgName="Unknown Organization"
[RegionalSettings]
LanguageGroup=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17
SystemLocale=0409
UserLocale=0409
UserLocale_DefaultUser=0409
InputLocale=0409:00000409,0409:00020409
InputLocale_DefaultUser=0409:00020409
[Identification]
JoinWorkgroup="WORKGROUP"

#4808 | fruitbat1001 | I am running a Ryzen 2600x on XP with the Zone 94 Integral Edition. How do I enable multiple cores?

#4809

Outbreaker

⇗ @fruitbat1001
You can do this with the "Optional Patch Integrator v*.cmd" Script. You can also use any Windows XP ISO you want, you only have to rename the ISO file to "Windows XP Professional SP3 x86 - Integral Edition 2020.X.X (Vanilla).iso".
⇗ https://www.zone94.com/downloads/softwar...comment_id=2418
Also take a look into the "Patches\ACPI drivers" folder for your "Ryzen 2600X" CPU if you run into problems with the default acpi.sys driver file.

#4810

diderius6

I make some more tests with the uaspstor.sys driver.
It is fast as much as possible on any USB port,
but unstable. May be because of too high current >800mA. It crashes whole compi or disconnects.
To boot XP SP3, I do not succeed with this driver
Dietmar
⇗

#4811

ruthan

> Zitat von ⇗ infuscomus im Beitrag ¶ #4806

> this might be ACPI related - have you tried the modded ACPI driver?

Im using - acpi 6666 - 2019.10.20#2 (Intel&Ryzen) - OuterSpace, without proper ACPI driver, i cant even boot.

#4812

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4803

> I have this controller on lenovo notebook, but never used it with win8. On WinXP usb3 controller was hidden by ACPI DSDT Code

If your acpi.sys supports all opcodes in the DSDT, change OSI string in acpi.sys from Windows 2001 SP2 to Windows 2012.

#4813

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4804

> @Mov AX, 0xDEAD
> for both my B75 boards (DEV_1E31) it was necessary to apply the WPCRset trick as for the AMD XHCI driver.

Now that you're using WDF 1.11, what about trying the HCSwitch drive one more time?
Just edit iusb3hcs.inf and change 6.1 to 5.1 and delete the following lines:

    [DestinationDirs]
    CoInstaller.CopyFiles = 11

    [HCSwitch.NT.CoInstallers]
    AddReg         = CoInstaller.AddReg
    CopyFiles      = CoInstaller.CopyFiles

    [CoInstaller.CopyFiles]
    WdfCoInstaller01009.dll

    [SourceDisksFiles]
    WdfCoInstaller01009.dll=1

    [CoInstaller.AddReg]
    HKR,,CoInstallers32,0x00010000, "WdfCoInstaller01009.dll,WdfCoInstaller"

Then install the driver (System Devices -> PCI Bus device).
Beware, backup before if needed as it may crash during boot.

#4814

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4812

> > Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4803

> > I have this controller on lenovo notebook, but never used it with win8. On WinXP usb3 controller was hidden by ACPI DSDT Code

> If your acpi.sys supports all opcodes in the DSDT, change OSI string in acpi.sys from Windows 2001 SP2 to Windows 2012.

I already thought about spoofing acpi.sys, but not tested on hardware, lenovo's dsdt is too smart, it hide Bluetooth device too )

#4815

diderius6

⇗ @ruthan
Take a normal harddisk
and install with Integrator v2.3.3b6
from website
⇗ https://www.zone62.com/downloads/softwar...comment_id=2220
After this, you know more
Dietmar

## Page 322

#4816 | Andalu | ⇗ @daniel_k when I try to update the XHCI controller (DEV_1E31) by the 'Have disk' option, I got the message: "The specified location does not contain information about your hardware".
#4817 | Andalu | ⇗ @diderius6 here too I had sometimes a sudden disconnection with the "Found new hardware" wizard started automatically ⇗

#4818

diderius6

⇗ @Andalu
For me this happens only with the uaspstor.sys driver
in combination with
USB\Class_08&SubClass_06&Prot_62
May be, that this is not the fault of the uaspstor.sys driver,
but just of the USB 3.1 ports, which can not give more than 800 mA current
Dietmar

#4819 | Andalu | ⇗ @diderius6 the same here, I talked about the USB UAS mass storage driver. Never had issues with the USB3 driver backported from Win8 (USB mass storage driver).

#4820

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4816

> @daniel_k
> when I try to update the XHCI controller (DEV_1E31) by the 'Have disk' option, I got the message: "The specified location does not contain information about your hardware".

The HCSwitch driver must be installed on the PCI bus device.

#4821 | Andalu | ⇗ @daniel_k just tried via "add new hardware" wizard but I got immediately the 0x0A1 bsod. On manually restart, I got the 0x07B bsod (even in safe mode).
#4822 | Andalu | ⇗ @diderius6 to be more precise, here's what happened two days ago with a nvme disk mounted on an usb3 adapter: ⇗

#4823

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4821

> @daniel_k
> just tried via "add new hardware" wizard but I got immediately the 0x0A1 bsod. On manually restart, I got the 0x07B bsod (even in safe mode).

Actually, you was supposed to choose update driver in Device Manager... not sure if this changes anything.

#4824

Andalu

⇗ @daniel_k
it installed correctly now but I got a 0x07B bsod on restart.
⇗ ⇗
Here a part of the modded iusb3hcs.inf:

    [Version]
    Signature="$WINDOWS NT$"
    Class=System
    ClassGuid={4d36e97d-e325-11ce-bfc1-08002be10318}
    Provider=%INTEL%
    DriverVer=05/21/2012,1.0.5.235
    CatalogFile=iusb3hcs.cat

    [Manufacturer]
    %STDDEV%=HCSwitch_PCIF,NTx86.5.1,NTx86.6.2

    [HCSwitch_PCIF.NTx86.5.1]
    %XHCI.DeviceDesc%=HCSwitch, *PNP0A08

    [HCSwitch_PCIF.NTx86.6.2]

    [SourceDisksNames]
    1 = %DISK_NAME%,,,""

    [PackageInfo]
    Name=iusb3hcs

    [SourceDisksFiles]
    iusb3hcs.sys = 1,,

    [HCSwitch.DriverFiles]
    iusb3hcs.sys

    [DestinationDirs]
    HCSwitch.DriverFiles     = 12

    [HCSwitch.NT]
    Include   = machine.inf
    Needs     = PCI_DRV
    CopyFiles = HCSwitch.DriverFiles

    [HCSwitch.NT.HW]
    AddReg = HCSwitch.AddReg

    [HCSwitch.AddReg]
    HKR,,"LowerFilters", 0x00010000, %ServiceName%

    [HCSwitch.NT.Services]
    Include    = machine.inf
    Needs      = PCI_DRV.Services
    AddService = %ServiceName%,,HCSwitch.ServiceInst

    [HCSwitch.NT.Wdf]
    KmdfService    = %ServiceName%, HCSwitch.wdfsect

    [HCSwitch.wdfsect]
    KmdfLibraryVersion = 1.9

    [HCSwitch.ServiceInst]
    DisplayName    = %XHCI_svcdesc%
    ServiceType    = %SERVICE_KERNEL_DRIVER%
    StartType      = %SERVICE_BOOT_START%
    ErrorControl   = %SERVICE_ERROR_NORMAL%
    ServiceBinary  = %12%\iusb3hcs.sys
    LoadOrderGroup = "Boot Bus Extender"

    [Strings]
    INTEL = "Intel"
    ServiceName       = "iusb3hcs"
    STDDEV = "(Standard system devices)"
    XHCI.DeviceDesc = "PCI bus"
    XHCI_svcdesc = "Intel(R) USB 3.0 Host Controller Switch Driver"
    DISK_NAME = "Intel(R) USB 3.0 Host Controller Switch Driver Install Disk"
    SPSVCINST_ASSOCSERVICE = 0x00000002
    SERVICE_KERNEL_DRIVER  = 1
    SERVICE_BOOT_START     = 0
    SERVICE_ERROR_NORMAL   = 1

#4825

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4824

> @daniel_k
> it installed correctly now but I got a 0x07B bsod on restart.

Thanks, what a dumb driver... will see if I can debug it later.

#4826

Andalu

> Zitat von ⇗ diderius6 im Beitrag ¶ #4818

> May be, that this is not the fault of the uaspstor.sys driver,
> but just of the USB 3.1 ports, which can not give more than 800 mA current
> Dietmar

I don't know if the issue can depend from the power. I tried booting with two UASP devices and two USB3 sticks already connected during the boot and I had not issues.
I got a blank screen only with five devices connected during the boot (2 UASP + 3 USB). Tried 3 times, no difference (5 devices are a bit too many)

#4827

ruthan

Some progress.
Its really about "right" driver i dont believe that my machine and porting to existing installation is something special.. but maybe only some additional driver adjustment (my guess are some files dependency.. which are not here, when you just install only clean driver..) are needed in compassion just just integration of drivers to cd.
I got new shipment :) of drivers:
Generic SATA+AHCI driver v1.3 - no lock, code 37 on device after installation, but
storahcisetup skullteria - its working, SSD and CD-ROM are fine, unfortunately its seems to not compatible wiht paragon GPT driver - or not at least without reinstallation (but i doubt that it will help, i will try to move GPT disk to Marwell controller).
USB - Generic USB 3.0 xHCI driver v1.1 (Windows 8)
Its much better that anything before, i finally hub installed all USB2 hubs without code 10, devices where find right after hubs installations.. Include mouse and keyboard and they worked right away. Even USB Lan was found and tried to connected to internet, but wasnt able to.. only keep trying.. i did not install driver for it, some Realtek 2016 driver was just found it system. Im not sure, if it was for my USB3 Gigabit lan, or just some for older USB2 100 Mbit lan.
Even after shutdown and boot to Win10, it seems that USB LAN adapter were stuck badly and not worked.
Unfortunately after reboot, got when Bluescreen when i should get Logon screen with error:
0x000000x8E (.. and some others see photo) . I wonder if is possible track, if problem is USB related (i didnt really mess with anything else in that boot session) and if possible to trace it to some device (there are some sub numbers). I had some incomplete USB driver for Web cam (MS HD 3000) before reboot, because driver installed need working internet.
If is not problem with device driver, it means that driver is much better, what others but still not good enough - still has some bugs.
⇗

#4828

ruthan

With Marwell Sata controller is data GPT disk working fine, so i can now access to my data.
Now i really need to solve that 1 GB of ram problem.. to make system good enough for usage, other things are "optimal", no show stoppers.
Optimal things:
- working USB - i can bypass it with better PS2 gaming and mice, now i have clumsy ones for install
- working USB LAN - again, i can bypass it with addon PCI-E NIC
- i also reordered new USB2 PCI-E controler with MOSCHIP, but it would take at least month until it will arrive from China
- make NVME drives readable
Otherwise timer - seems to work fine, no negative values.

#4829

diderius6

Via boot with the uaspstor.sys driver I succeed to go away from BSOD 0x7B. This is a copy from a working XP SP3, put to the uaspstor device. Everything is ok with the registry and the HIVE software and all the other files there. This error can be exact reproduced with another XP SP3 image also.
For service of uaspstor I use Group Boot Bus Extender start=0 and the same for XHCI and USBHUB3. Bye the way I noticed,
that Group System Reserved loads before Boot Bus Extender and this before SCSI miniport.
Now comes a BSOD, that I have never seen before.
SESSION3_INITIALIZATION_FAILED
BSOD 0x0000006F (0xC0000102, 0x00000000, 0x00000000, 0x00000000)
Dietmar
PS: It seems, that this driver has a problem to load correct the Hive software.
May be, that the driver uaspstor.sys has a problem with smss.exe.
EDIT: Before first boot with the driver uaspstor.sys I can load the hive "software" from that USB device on an external XP.
But after first boot, I cant load this hive "software" again by an external XP. This simple means, during boot with the uaspstor.sys driver,
the CRC checksum of the Hive "software" is destroyed.
This I get via F8 (Safe Mode):
⇗

#4830

Keegan

Hi Everyone,
I've been attempting to install windows XP on a modern device now for some time without success. My main issue is the BSOD 0x7B after the windows setup, is anyone able to assist?
I've tried a bunch of drivers for what should be the correct storage controller without success. I run in to the issue with some drivers whereby they are too large to fit on the 1.44mb floppy disk.
My setup:
- HP ProDesk 400 G1 SFF
- Intel Haswell H81 Chipset motherboard (DEV_8C02)
- 250GB SSD formatted
- Genuine XP CD
- USB floppy drive with 1.44MB floppy disks
- BIOS set to AHCI mode

## Page 323

#4831

diderius6

⇗ @Keegan
Try
⇗ https://www.zone62.com/downloads/softwar...comment_id=2220
This is a very nice generic XP SP3,
which runs on nearly every compi
Dietmar

#4832 | Keegan | ⇗ @diderius6 Thanks for your help, I would really like to avoid installing a cracked XP if possible. If I can't figure anything else out or get further assistance i'll give it a shot.

#4833

ruthan

I tried NEC \ Renesas USB3 addon card (PCI\VEN_1912&DEV_0014&SUBSYS_00000000&REV_03 - 720x - its combo 4 ports + 1 internal and its even has USB3 front header) with Generic UBS3 driver. Which is tricky one, even with Windows 10.. But i have no alternative, i have only VIA USB3 ones, which would be probably even worse, no Fresco.. ASM 3xxx which need longer than PCI-E 1x slot, which i would sacrifice, because other cards - i plan to use 3 GPUS for (Win98 (i dunno if physicaly but with KVM for sure) / XP and WIn7+) so long slots are full. So i would have order ASM 1xxx with only shame is that i never saw it with more that 2 port.
Regardless with NEC is working with XP even after reboot with USB LAN adapter, so im now online. Bluetooth and FLashdisk are working too. So problem is really with Generic USB + Driver and Intel USB3 controller, or Intel USB3 controller and in synergy with some type of device (i have lots of them.. even some TV sticks, Doplhin bar for WIi emulator, some remote etc, so maybe more complex text that someone did before).
Even if would be NEC more realiable.. it still sucks, because its not working for bios, so it would need still have to mess with 2 keyboards and mice. So, its getting better, with some annoyance i my XP setup could be ready for normal use, if someone will solve that 1GB of RAM problem.. Any ideas, in the history i saw some alternative hals etc, is it now dead thing?

#4834

ruthan

I have tried magic XP SP3 distro with these options:
- Integrated Sata/AHCI driver
- NVME 1.3
- ACPI patch
- PAE 4GB RAM patch
-Remove drivers packs base
I did not used USB3 driver to had room to mess with them later, i also disconnected all disc, include NVME to i dunno yet if it will working.. im now making clean disc image to have possibility easily return to point zero..
When i had NVME connected, install see target Sata disc as letter E and NVME which is GPT as unformated to MBR disc, so i get affair that it will try to install bootloader on it or otherwise mess with data.. I have computer under table and case is full of card, so disconnecting of NVME with special cooler was quite a mess. I still dream about standard bios feature to disable some disc without disconnecting.
I had some strange behavior when i tried to use target disc connected to Marwell controller, all setup copied all data.. but after that it returned to partition screen (target partition was still shown as unformated), there is small chance that disc sata cable, was wrongly connected, but i doubt it.. so maybe some script problem, when i tried to boot from disc some data where here.. When used Intel Sata on board port, it worked fine.
So far one big difference discovered, i see full 4.00 GB of ram.. that is difference.
Question why.. Is Win-PAE-Patch supposed to that? I have idea that my original install is not in english so maybe that is problem and patcher is not patching what supposed to, but im getting patching that patching was ok, except on presented files.
List of unknown devices seems to be same as with my existing install.. now i will try to mess with NVME a USB3.

#4835

gordo999

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4803

> On WinXP usb3 controller was hidden by ACPI DSDT Code

⇗ @Mov AX, 0xDEAD ...I wonder about that. I am using my mainboard (B360M chipset) to run XP, W7 and W10. Can I mod the BIOS for XP only? Also, is there anything in BIOS related to com ports and debugging mode?
I am thinking the BIOS may be coded to exclude XP, I don't want to change BIOS code that will affect W7 and W10. I know the Intel setup files for USB drivers are written to exclude versions of chipsets after Skylake. The code references Skylake.

#4836

ruthan

Other news..
- NVME driver installed a can see disc in disc management just fine and again question where could be difference?
- GPT loader is not really working with Universal Sata. I can see disc in Device manager or Disk list. I have smaller 256 GB which is at least listed in disc managment (but has not letter and its not possible to assign it because that is it thing GPT loader thing - which should be done automatically). Big data disc - 4TB disc i dont see at all - true is that with old install i have installed some 3TB+ disc unlockers.. which where bundled with MB software or i thing with Acronis etc. Maybe they are needed.
I guess that with Marwell Sata driver it would be ok, but need to test to be sure, if it is Sata driver thing (probably) or some unlocker is needed.
To magic distro:
- i thing that would make add some realtek HD optimal package to have sound out of box, there is just one old universal driver and virtually everybody have it onboard..
- at least some portable Pspad or Notepad++ would help too, there is option to install much stranger things in install Wizzard.
I discovered what means that SSE2 Updates Rollback package, its for CPU which are not supporting SSE2, that is not our thing.

#4837

gordo999

> Zitat von ⇗ Keegan im Beitrag ¶ #4832

> I would really like to avoid installing a cracked XP if possible.

⇗ @Keegan ...did not catch the beginning of your post...have you tried upgrading an installed XP SP3 to the unofficial XP SP4 upgrade? The SP4 upgrade has drivers that can help get you past the standard boot BSOD errors of 0xA5 and 0x7B. Then you can use daniel_k's AMD USB driver. I have done a repair install using the slipstreamed XP SP3 disk with the SP4 unofficial upgrade. It adds all the latest updates. I have daniel_k's USB driver integrated into the installation.
If you try a repair install you must first change a setting in nlite before merging SP4 with SP3, otherwise the repair option does not appear during repair install. I can look it up if it interests you. To my surprise, without the nlite change, SP4 installed a completely new XP installation in parallel with the existing one. I could boot from either installation.

#4838 | ruthan | Ok, its like a though.. with Marwell i can see 4TB disk is Disk management (un only as 2 TB one.. - i have to check on migrated machine if its ok or not.. maybe its just MS stupid forecast.. - if not some unlocker is really needed), but still not letter assigned and same as for smaller 256 GB disk. If my memory serves - integrated GPT loader demo is just 8.x and last version 10.x could be problem.. Or maybe integrated version has some other managment which i dont know.

#4839

ruthan

⇗ @Keegan - only other way is install it on older machine, virtual machine and migrate installation and use Sata controller with IDE bios and replace acpi.sys .. and after that install all new nice drivers, that is almost as my migration way of use old install..
But its really more time consuming and new more knowledge.
Or you can try inject Sata drivers (to bypass need of non AHCI controller for first boot) on your own to iso - where is proven that nlite is botched.. or with driver injector which i posted few days ago - but its unproven.

#4840

gordo999

> Zitat von ⇗ ruthan im Beitrag ¶ #4839

> where is proven that nlite is botched.. or with driver injector which i posted few days ago - but its unproven.

⇗ @ruthan ...I found out the hard way that if you use nlite on XP you have to use the XP version AND you have to run it on an XP installation. Otherwise it fails. I have run it on an XP virtual machine and on my current XP installation with no errors. If you run an XP integration on W7 or higher, it fails and if you use an nlite version higher than XP it fails on an XP integration.
I have used nlite successfully to integrate XP SP3 with SP4 and I have added drivers from this site with no problem. I used the same integrated disk to do a repair install of XP. Having said all that, I'd prefer to do it directly without using nlite so I could learn the proper process.

#4841

ruthan

Ok, with Generic USB driver on Intel USB3 controller - i simulated with clean install exactly same freeze - boot black screen. So its controller itself, or controller with combination with some device.. and its not USB lan and bluetooth because there are working fine with NEC controller. I installed only generic Windows inbuild drivers for my USB devices.. to it they were not recognized at all, or as HID devices.
I also tested Gigabyte and Asrock 3TB+ unlocker, so luck.. But i found that my GPT loader is really version 10, so it could be just old GPT loader version.. i will test it.

#4842

ruthan

So it like, i though with newer Paragon GPT driver, i can read and write from GPT disk fine, when from NVME what is nice.
It has some flaws:
- after installation it assign letter to virtually every partition even to EXT4 and HFS+ ones.. and EXT4 can be remove from disk console, but HFS+ dont, i always removed letter through some partition managers.. but it dont remember detail, it wasnt super easy.
- it love to mark partitions as dirty for scandisk checks.. and its deadly with combo when you have not working keyboard during boot, if im not wrong USB keyboard are usually initialized to at logon screen, so you can get very long checking pause.. or you have reset and connect PS/2 keyboard to skip, or somehow disable scandisk on boot.. or maybe make checking with other OS and do multiple reboots. Its annoying. Its checking every volume.. even if it can understand filesystem (what is quick its just 5-10s to).
- other problem is that all connected disk which are using GPT driver, are in system as portable and removable.. I never was crazy about XP disk hotplugin so i would prefer to disable it.
To my honor, i reported maybe 5 years ago to Paragon, that GPT loader is not working with some disc controllers, but bug is still open - other priorities, on discontinued product now.. bla, bla.

#4843 | Outbreaker | ⇗ @ruthan Was the Paragon GPTLoader v8 not the last version they put out? A user has even done some fixes for v8 ⇗ http://hardwarefetish.com/777-paragon-gpt-loader-3

#4844

infuscomus

⇗ @Mov AX, 0xDEAD ⇗ @daniel_k
testing nvme in VMWare and Virtualbox and the only driver that has worked so far is stornvme of windows 10
OFA nvme failed, Samsung nvme failed
even stornvme of windows 8 failed
can stornvme of windows 10 be backported?
edit:
I got stornvme driver of 10 to start by removing the security cookie, no crash this time, but no nvme drive shows up.
so is there something in storport of 10 that helps with nvme for VMs?
edit2:
I'm thinking to try and make a backport of storport 10
I can use some of the code from backported storport 8 that @Mov Ax 0xDEAD wrote but there are other functions in storport 10 that are called
extra functions called by storport 10:

    IoGetAdapterCryptoEngineExtension
    IoGetAffinityInterrupt
    ExReleaseSpinLockSharedFromDpcLevel
    PoFxIdleComponent
    IoDisconnectInterruptEx
    IoGetIoPriorityHint
    KeFlushIoBuffers
    EtwWriteTransfer
    ExAcquireSpinLockSharedAtDpcLevel
    ExAcquireSpinLockExclusive
    ExAcquireSpinLockExclusiveAtDpcLevel
    IoQueueWorkItemEx
    ExReleaseSpinLockExclusiveFromDpcLevel
    FirstEntrySList
    PoUnregisterCoalescingCallback
    PoRegisterCoalescingCallback
    PoFxRegisterCrashdumpDevice
    KeGetCurrentProcessorNumberEx
    ExReleaseSpinLockShared
    ExAcquireSpinLockShared
    MmAllocatePagesForMdlEx
    PoFxIssueComponentPerfStateChange
    KeGetProcessorIndexFromNumber
    KeQueryGroupAffinity
    MmMapIoSpaceEx
    PoFxSetComponentLatency
    IoPropagateIrpExtension
    ExReInitializeRundownProtectionCacheAware
    ExSetTimer
    ExDeleteTimer
    ExAllocateTimer
    ExCancelTimer
    PoFxRegisterComponentPerfStates
    PoFxPowerOnCrashdumpDevice
    IoReportInterruptActive
    IoReportInterruptInactive
    PoFxCompleteIdleCondition
    ZwQueryLicenseValue
    EtwSetInformation
    RtlComputeCrc32
    EmClientQueryRuleState
    KeQueryUnbiasedInterruptTime
    PoRegisterPowerSettingCallback
    ExReleaseSpinLockExclusive
    ExWaitForRundownProtectionReleaseCacheAware
    IoGetGenericIrpExtension

but I don't know which of these functions need code and which can be stubbed.

#4845 | daniel_k | Can't see the point of a working NVME driver on a VM? Problem isn't the driver, it's the emulated NVME controller.

## Page 324

#4846 | infuscomus | ⇗ @daniel_k can we be certain this behavior wouldn't ever occur on real hardware? earliest windows 10 1507 storport/stornvme work correctly in a VM would I be asking too much to ask for a backport of storport/stornvme 1507?

#4847

daniel_k

> Zitat von ⇗ infuscomus im Beitrag ¶ #4846

> @daniel_k
> can we be certain this behavior wouldn't ever occur on real hardware?
> earliest windows 10 1507 storport/stornvme work correctly in a VM

Please, please, there are no issues with the drivers.
Our goal is to get real hardware working, which has proven to be true.
If you do a web search for virtualbox and nvme, you'll find several problem reports and explanation as to to why it doesn't work on many builds of Win10 etc.
⇗ @diderius6's got NVMEs from Intel, Samsung and Toshiba working, with varying controllers.
⇗ @Andalu and I have Samsung NVMEs, which do work fine.
Do you even have a NVME driver to try? Seriously.

> Zitat

> would I be asking too much to ask for a backport of storport/stornvme 1507?

For me, way too much and I see no point of doing it. Unless ⇗ @Mov AX, 0xDEAD sees a reason for it and do it.
Newer versions are optimized for today's PCs, NUMA and the like, most missing imports are related to them.

#4848 | infuscomus | ⇗ @daniel_k OK, you've made your point, I'll stop asking.

#4849

ruthan

> Zitat von ⇗ Outbreaker im Beitrag ¶ #4843

> @ruthan
> Was the Paragon GPTLoader v8 not the last version they put out? A user has even done some fixes for v8 ⇗ http://hardwarefetish.com/777-paragon-gpt-loader-3

Last version is probably 10.0.16.12944 , i dunno why version 8 is integrated, if these patches are included or not.. i can only say that its not working for me, but newer version is ok.

#4850

ruthan

Ok i made working pae patch with old installation. Problem was logical, i installed patch from executed XP.. and these files are somehow protected, or restored after reboot. It would be nice to add some warning. Other there was only pro some old 486 hal, which im not using of course. Im not 100% sure if im using original file, or some already modified.
PAE will be enabled with RAM limited to 4Gb.
Patching ntkrnlmp.exe (Multiprocessor Kernel)... OK!
Patching ntoskrnl.exe (Uniprocessor Kernel)... OK!
Patching ntkrnlpa.exe (Uniprocessor PAE Kernel)... OK!
Patching ntkrpamp.exe (Multiprocessor PAE Kernel)... OK!
Patching hal.dll (Standard PC/Standard PC w/ C-Step i486 HAL)... Invalid file!
Patching halaacpi.dll (ACPI Uniprocessor PC HAL)... OK!
Patching halacpi.dll (ACPI PC HAL)... OK!
File halapic.dll (MPS Uniprocessor PC HAL) was not found.
Patching halmacpi.dll (ACPI Multiprocessor PC HAL)... OK!
File halmps.dll (MPS Multiprocessor PC HAL) was not found.
So only difference between my new and old install behavior is old now working NVME driver (code 10). I retested it after i made PAE working is still the same.
Update: Im using hal.dll from this thread which suppose to fix timers issues its from December 20, 2018, 22:20:18, so that is probably why, it was not patched.

#4851

daniel_k

⇗ @ruthan
Did you apply this?

> Zitat von Mov AX, 0xDEAD

> i found issue in storport_w8: by default it force MSI Interrupts, fix to use standart interrupts:
> offset_132b3: C6 83 CC 09 00 00 01 => C6 83 CC 09 00 00 00

Remember to fix PE checksum.

#4852

ruthan

⇗ @daniel_k Sorry, im a bit confused, this should be related to not working NVME or to something else?
I got storport.sys - from October 22, 2007, 15:36:20 ⇗ @diderius6 so its not pached by new discoveries. In StorPort v5.2.3790.4173 folder is same file. Also in storahcisetup (skullteria) is the same file so if exists something better / newer i dont have it. Same file i have in my existing installation.
But you are right magic distro has storport.sys + storahci.sys and which have date from time of installation or making installation ISO, other files in system32\drivers.. have proper (old) dates.
Should a i just overwrite it? And if yes just only storport.sys or storahci.sys too?

> Zitat

> Remember to fix PE checksum.

Its beyond my skills, i would need whole file to use.

#4853 | ruthan | I did binary comparision of storport.sys on both installations and they are the same. So patch is not applied probably anywhere.

#4854

daniel_k

> Zitat von ⇗ ruthan im Beitrag ¶ #4853

> I did binary comparision of storport.sys on both installations and they are the same. So patch is not applied probably anywhere.

That patch I told you about it's not for the Server 2003 version of storport.
It's for the W8 ported Mov AX, 0xDEAD storport.sys.
I'll send you a PM.

#4855

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #4816

> when I try to update the XHCI controller (DEV_1E31) by the 'Have disk' option, I got the message: "The specified location does not contain information about your hardware".

⇗ @Andalu ...may be overly simplified reply but that message indicates it did not find an INF file in that location that applied to your hardware. Check the INF file to makes sure it specifies your hardware and that your hardware is not listed as excluded. Could be a syntax error in the INF file.

#4856 | canonkong | ⇗ @daniel_k I tested the new MOD driver without WppRecorder. It is working very well for each USB expansion card from ASMedia, Etron, VIA, Renesas, Texas Instruments, Fresco Logic, also is working well on Intel and AMD USB devices. ⇗
#4857 | ruthan | ⇗ @canonkong Ok lots of controllers.. but what about devices ? Could you try some devices compatibility - i means mouse, keyboard, web cam, some complex device etc.. anything else that just flashdisk.. ? I have for example with Intel and some devices - blue / black screen after reboot.
#4858 | canonkong | ⇗ @ruthan Mouse, keyboard, U disk, mobile hard disk, USB decoder, USB wireless network card, USB Bluetooth device all working well. I want to test more usb device, but no more other USB devices I have.
#4859 | ruthan | @Canonkong: And you tested all of these on all controllers? I thing that Intel is most important.. because everyone has it on board. I plan do some testing too.
#4860 | canonkong | ⇗ @ruthan Yes, I tested all of these on all controllers, also test them on AMD X370/B450/X570 with APU/Ryzen CPU. For intel, I only have H110/B250 mainboards.

## Page 325

#4861 | ruthan | So i have to have something really ugly combination of devices.. to get black / blue screen.. i wanted to avoid it.. but it guess.. that i would have to install controller driver.. reboot.. install hub driver reboot.. and after one device after other try to reboot to find what is wrong. I only hope that just disable device would work, because other there is not way to block usb devices autodetection unless i will all disconnect at the start - what is additional hassle..

#4862

Andalu

> Zitat von ⇗ gordo999 im Beitrag ¶ #4855

> @Andalu ...may be overly simplified reply but that message indicates it did not find an INF file in that location that applied to your hardware. Check the INF file to makes sure it specifies your hardware and that your hardware is not listed as excluded. Could be a syntax error in the INF file.

already solved ¶ here, thank you. The inf was correct, I had to look for the PCI bus instead of the USB controller.

#4863 | daniel_k | ⇗ @canonkong Thanks for the tests, hopefully this driver wll be our final and best version ever!
#4864 | ExtremeGrief | Hi, I just saw this thread, but I don't want to read 325 pages. Can I get a guide or something, along with bug list and workarounds?
#4865 | fruitbat1001 | Check This Out if you are a beginner. Don't forget to integrate the required drivers: ⇗ https://www.zone62.com/downloads/softwar...ntegral-edition
#4866 | canonkong | ⇗ @daniel_k 10Gbps USB to NVMe device working on 20Gbps USB3.2 GEN2X2 expansion card. MS UASP driver is faster tha VIA UASP. ⇗

#4867

daniel_k

⇗ @canonkong
Really nice numbers!
As usual, all credits to ⇗ @Mov AX, 0xDEAD for the original patch. Just ported it to x64 and he helps me even if he doesn't care about x64.
VIA is known to have terrible drivers. Hardware is not that bad, using MS drivers (XHCI) is a completely different experience.
I know you're on Win7, but please really stress that drive. On XP, ⇗ @diderius6 and ⇗ @Andalu had problems:
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (321)
¶ Windows XP 32-Bit and Server 2003 32-Bit on Modern Hardware (322)
Does the drive you're benchmarking have hight current requirements?

#4868

gordo999

> Zitat von ⇗ Andalu im Beitrag ¶ #4862

> The inf was correct, I had to look for the PCI bus instead of the USB controller.

⇗ @Andalu ...The 0x7B error can be related to the disk controller. I know you are using NVME but when I get the 0x7B it's related to the Intel SATA AHCI Controller which is DEV_A352 on my B360 chipset. Here's what Microsoft has to say about 0x7B:
⇗ https://support.microsoft.com/en-ca/help...-inaccessible-b
I recall that my pci driver had an issue when the USB switch driver and coinstaller got installed along with it. Right now, all I have for a PCI driver is pci.sys with hardware ID ACPI\PNP0A08. It has a *PNP0A08 in that section as well. The pci.sys version is 5.1.2600.5512 (xpsp.080413-2111).

#4869 | canonkong | ⇗ @daniel_k I haven't encountered these problems yet. My USB to nvme device adopts jms583 chip scheme, and the bridging nvme device is Samsung's pm981a and sm961. This may have something to do with the system version itself.
#4870 | canonkong | I found an interesting phenomenon. My B250 motherboard can work normally without any xhci driver. However, they will be recognized as PS / 2 devices by the system, even though they are USB devices. Maybe we can do something with the bios. ⇗
#4871 | ruthan | They are bios related option USB legacy and Port 60-64 at least on Gigabyte board. I have similar problem PS/2 mouse is working everywhere (Bios, XP, Linuxes, XP, Windows 7) but not in Win10 on Z390.
#4872 | canonkong | ⇗ @ruthan Well, I see. I found that my Gigabyte x570 motherboard also has this function.

#4873

Andalu

The nice XP Integral Edition ISO installs fine also on the Sabrent Rocket m.2 nvme disk. For the first time on my system, the XP installation and the booting from a nvme disk is fastest then a SSD, thanks to the samsung driver from ⇗ @daniel_k and ⇗ @Mov AX, 0xDEAD
Never happened before with the OFA drivers.
Here the screenshots:
on the left, with the original intelppm.sys, the cpu temperatures is high even only with few working processes; on the right, with the modded intelppm.sys from the halplusintelppmXPSP3 package, the cpu temperatures become regular for the benefit of the system (and my ears):
⇗ ⇗

#4874

ruthan

Ok, i did other round ot testing with Intel USB3 on Z390 and clean install + Generic USB 3.0 xHCI driver v1.1
- Install driver for controller itself is ok, but when i installed USB 3 hub and disabled all USB2 hub installs and all USB devices - non had any driver, i simulated boot problem. So unless it depends that is some devices even contronected - regardless that it is disabled and without driver. Problem is hub driver.
My id, wonder is someone has exactly the same controller?
Controller - PCI\VEN_8086&DEV_A36D&SUBSYS_50071458&REV_10

#4875 | ruthan | BTW that WinXP scandisk is really annoying how its slow, how its possible that Win 10 scandisk is at least 10x faster? I dont thing that it is bruteforce, only probably not checking everything.

## Page 326

#4876 | Andalu | ⇗ @gordo999 I made that attempt using a hard disk drive (no nvme). I tried by installing a different sata/ahci driver (Intel RSTe_4.7.0.1117) without success, same bsod on restart even changing storport version (v5.2.3790.4485 and v6.2.9200.16384 both tried). It's not a real issue, it was just an attempt to verify the effectiveness of a new development from @daniel_k. Pci.sys and hardware ID are the same here too for all my intel boards.
#4877 | Andalu | ⇗ @ruthan no issue here with a similar usb controller: PCI\VEN_8086&DEV_A36D&SUBSYS_86941043&REV_10

#4878

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4821

> @daniel_k
> just tried via "add new hardware" wizard but I got immediately the 0x0A1 bsod. On manually restart, I got the 0x07B bsod (even in safe mode).

Hi, found the issue, finally!
iusb3hcs.sys is a WDF driver. KMDF Runtime (Wdf01000.sys) MUST be loaded first, then all drivers depending on it.
The way we've integrated Wdf01000.sys is not 100% correct.
iusb3hcs.sys is installed as a lower filter for the PCI bus device, which is one of the first drivers loaded during boot. As the KMDF Runtime isn't loaded yet, Windows cannot proceed to enumerate devices, hence the 0x7B boot error.
Copy the following text and save it as Wdf01000.reg then apply it.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000]
    "Group"="System Reserved"

This will make sure the service is loaded first.
Restart and install iusb3hcs.inf.
The driver will load, but is it going to work? Let us know!

#4879

daniel_k

On a side note, this may interest you.
By default, XP disables the USB port when the connected device is ejected. So the external disk/pendrive is powered off.
But originally, the ported XHCI driver is a Win8 driver, which behaves differently unless you apply the following registry key:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\usbhub\hubg]
    "DisableOnSoftRemove"=dword:00000001

#4880

Andalu

> Zitat von ⇗ daniel_k im Beitrag ¶ #4878

> The driver will load, but is it going to work? Let us know!

Same 7B bsod

#4881

ruthan

> Zitat von ⇗ Andalu im Beitrag ¶ #4877

> @ruthan
> no issue here with a similar usb controller: PCI\VEN_8086&DEV_A36D&SUBSYS_86941043&REV_10

Similar is not same. Well, i heard that it just working year back :) I thing that we are slowly getting here..

#4882

daniel_k

> Zitat von ⇗ Andalu im Beitrag ¶ #4880

> > Zitat von ⇗ daniel_k im Beitrag ¶ #4878

> > The driver will load, but is it going to work? Let us know!

> Same 7B bsod

It's because of naming scheme of WdfLdr8.sys XHCI driver.
iusb3hcs.sys expects WdfLdr.sys.
Open \Windows\System32\Drivers and copy WdfLdr8.sys to WdfLdr.sys and try again.

#4883 | Andalu | ⇗ @daniel_k it works!!... now ;)
#4884 | daniel_k | ⇗ @Andalu Finally! Check performance and if it changes those registers.

#4885

ruthan

I did one more round of WinXP stuff.
1) I tried SDI tool driver installer for some unknown devices, its always a bit risk and it was able to recognize and install driver to couple of devices.. i dunno it these are just null drivers (right names for device manager) or they are actually doing something:
PCI\VEN_8086&DEV_A323&SUBSYS_50011458&REV_10\3&11583659&0&FC // Intel Z390 Chipset SMBus Controller
PCI\VEN_8086&DEV_A323&SUBSYS_50011458&REV_10 //Intel Z390 Chipset SMBus Controller
PCI\VEN_8086&DEV_A324&SUBSYS_72708086&REV_10 // Intel Z390 Chipset SPI (flash) Controller
PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10 // Intel Z390 Chipset Thermal Subsystem
2) I now that is not probably not useffull to lots of people but.. tool for remove drive letters from Mac HFS partitions is Paragon HDD manager 2015.. there some demos and 2014 free version, so you can try them.
3) USB:
- tried to detect more devices with working NEC USB3 controller, so USB keyboard and mouse is working fine and Logitech unified controller problem too.. mouse + logitech these are connected through USB3 hub.. but what is interesting that for that hub.. i actually got multiple USB3 hub detections same as USB2 hub detection? Its this normal - it look like one hub is for port, or connected device.. I thing that windows 98 worked like that but i dont thing that Windows XP+ are working like that.
I also have some unknow device.. with has not proper name, just something about descriptor failing.. i will post details later, im now making disk image with a bit improved system.

#4886 | XPWELL64 | There are 6 different ACPI Booting Modes in my BIOS. These are Acpi1.0B,Acpi3.0,Acpi4.0,Acpi5.0,Acpi6.0,Acpi6.1. Acpi5.0 is selected as a default setting. Does it brick my BIOS? I'll select 1.0B. It is locked. I'm using InsydeH2O BIOS.

#4887

ruthan

I continued with testing, but failed device was now gone, tested Webcam, also worked, but USB mouse cursor was dead (it worked only after 1st isntall, after that 2 reboots nothing, but with my NEC controller it could be still Temporary).. and later not long after basilisk start, even PS/2 mouse cursor froze. It could be new devices drivers and my Nec controller is also not stable.. but i because Intel one is not working at all its best what i can now do. I better controllers are on the way.
Im testing NEC controller with Win10 too, so we will now, here as mouse working fine, only USB LAN never was reliable. I was suprised, but its working in bios, i had with other machine opposite experience.

#4888 | ruthan | @XPWELL i guess that you would have to check manual.. but for Windows XP, now with patches should work same settings as for new Windows or Linux.

#4889

Andalu

> Zitat von ⇗ ruthan im Beitrag ¶ #4885

> I did one more round of WinXP stuff.
> 1) I tried SDI tool driver installer for some unknown devices, its always a bit risk and it was able to recognize and install driver to couple of devices.. i dunno it these are just null drivers (right names for device manager) or they are actually doing something:

>     PCI\VEN_8086&DEV_A323&SUBSYS_50011458&REV_10\3&11583659&0&FC // Intel Z390 Chipset SMBus Controller
>     PCI\VEN_8086&DEV_A323&SUBSYS_50011458&REV_10   //Intel Z390 Chipset SMBus Controller
>     PCI\VEN_8086&DEV_A324&SUBSYS_72708086&REV_10 // Intel Z390 Chipset SPI (flash) Controller
>     PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10 // Intel Z390 Chipset Thermal Subsystem

> 2) I now that is not probably not useffull to lots of people but.. tool for remove drive letters from Mac HFS partitions is Paragon HDD manager 2015.. there some demos and 2014 free version, so you can try them.
> 3) USB:
> - tried to detect more devices with working NEC USB3 controller, so USB keyboard and mouse is working fine and Logitech unified controller problem too.. mouse + logitech these are connected through USB3 hub.. but what is interesting that for that hub.. i actually got multiple USB3 hub detections same as USB2 hub detection? Its this normal - it look like one hub is for port, or connected device.. I thing that windows 98 worked like that but i dont thing that Windows XP+ are working like that.
> I also have some unknow device.. with has not proper name, just something about descriptor failing.. i will post details later, im now making disk image with a bit improved system.

1) ¶ here are some answers to your questions
2) thanks for the info
3) can this image be useful? These are my three PCIEx to USB3 cards (Via, Nec, Fresco Logic) inserted at the same time on the Q370 board:
⇗

#4890 | ruthan | Did grand disconnection.. and with Intel USB3 + HUB im now booting so my problem has to be with some device.. and for error is probably enough that is just connected. I will have to connect one by one and make rebooting marathon..

## Page 327

#4891

ruthan

I found at least one "evil" device with not working with Intel USB3 + Win 8 driver, its USB TV stick.. Pinnacle 73e, even when i disconnect it once is driver installed im getting that black screen freeze, before logon window.
I would be later interesting if there would be same problem with NEC controller..
What is working:
Xbox 360 controller
Monitor USB2 hubs
Microsoft Webcam 3000 HD
Here is that evil driver maybe it will help with analysis.. It worked with XP fine for years.
ruthan has attached files to this post

- ⇗ PCTV 200Xe.zip

#4892 | ruthan | There has to be other evil device - Logitech unified dongle, or X360 controller without installed driver, it depends simply which ports are used..

#4893

Mov AX, 0xDEAD

⇗ @ruthan

> Zitat von ⇗ ruthan im Beitrag ¶ #4891

> I found at least one "evil" device with not working with Intel USB3 + Win 8 driver, its USB TV stick.. Pinnacle 73e, even when i disconnect it once is driver installed im getting that black screen freeze, before logon window.

what happened if tv stick inserted after windows was fully loaded ? what usbtreeview show on port ?

#4894

IntiMD

> Zitat von ⇗ ruthan im Beitrag ¶ #4885

> 1) I tried SDI tool driver installer for some unknown devices, its always a bit risk and it was able to recognize and install driver to couple of devices.. i dunno it these are just null drivers (right names for device manager) or they are actually doing something:
> PCI\VEN_8086&DEV_A323&SUBSYS_50011458&REV_10\3&11583659&0&FC // Intel Z390 Chipset SMBus Controller
> PCI\VEN_8086&DEV_A323&SUBSYS_50011458&REV_10 //Intel Z390 Chipset SMBus Controller
> PCI\VEN_8086&DEV_A324&SUBSYS_72708086&REV_10 // Intel Z390 Chipset SPI (flash) Controller
> PCI\VEN_8086&DEV_A379&SUBSYS_88881458&REV_10 // Intel Z390 Chipset Thermal Subsystem

Pretty sure these are the chipset null drivers. They can also be found in Fernando's Intel Chipset INF AiO pack under the Cannonlake-H folder (CannonLake-HSystem.inf for DEV_A323 and DEV_A324 + CannonLake_HSystemThermal.inf for DEV_A379.)

#4895

ruthan

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4893

> @ruthan
> what happened if tv stick inserted after windows was fully loaded ? what usbtreeview show on port ?

I cant simuate it. Once install driver and reboot even when stick is removed im still getting boot black screen, installation is dead - maybe i will be able to fix it in safe mode, but removing some zombie devices.. maybe not. Maybe is controller stuck in some state and reboot is not enoug, but i thing that in did power down.. or it need unplug eletricity for the moment.
Im also starting to thing that some installation order could have effect, im on the track to second not working devices.. and some patters, but so far i can say anything for sure. USBtree downloaded.

#4896

ruthan

Ok, i have at least some example that device detection failure:

      =========================== USB Port7 ===========================

    Connection Status        : 0x02 (Device failed enumeration)
    Port Chain               : 1-7
    PortAttributes           : 0x00000000

          ======================== USB Device ========================

    DriverKeyName            : ERROR_FILE_NOT_FOUND

            +++++++++++++++++ Device Information ++++++++++++++++++
    Device Path              : \\?\usb#vid_0000&pid_0002#6&1127c026&0&7#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
    Device ID                : USB\VID_0000&PID_0002\6&1127C026&0&7
    Hardware IDs             : USB\DEVICE_DESCRIPTOR_FAILURE
    Driver KeyName           : -
    Legacy BusType           : PNPBus
    Interface GUID           : {a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE)
    Enumerator               : USB
    Location Info            : Port_#0007.Hub_#0001
    Manufacturer Info        : -
    Capabilities             : 0x64 (Removable, SilentInstall, RawDeviceOK)
    Status                   : 0x01806400 (DN_HAS_PROBLEM, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
    Problem Code             : 43 (CM_PROB_FAILED_POST_START)
    HcDisableSelectiveSuspend: 0
    EnableSelectiveSuspend   : 0
    SelectiveSuspendEnabled  : 0
    EnhancedPowerMgmtEnabled : 0
    IdleInWorkingState       : 0
    WakeFromSleepState       : 0
    Power State              : D3 (supported: D0, D2, D3, wake from D0, wake from D2)

            +++++++++++++++++ Registry USB Flags +++++++++++++++++
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
     GlobalDisableSerNumGen  : REG_BINARY 01

            ---------------- Connection Information ---------------
    Connection Index         : 0x07 (7)
    Connection Status        : 0x02 (DeviceFailedEnumeration)
    Current Config Value     : 0x00
    Device Address           : 0x00 (0)
    Is Hub                   : 0x00 (no)
    Device Bus Speed         : 0x02 (High-Speed)
    Number Of Open Pipes     : 0x00 (0 pipes to data endpoints)
    Data (HexDump)           : 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
                               00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 02   ................
                               00 00 00                                          ...

        ---------------------- Device Descriptor ----------------------
    bLength                  : 0x00 (0 bytes)

          -------------------- String Descriptors -------------------
    String descriptors are not available  (because the device has problem code CM_PROB_FAILED_POST_START

I dont yet discovered which device is failing..
Im glad that i have not yet added XP videocard to machine, because i would probably now be mad from all that input switching.
Now i have plan to test all devices with Nec controller, after that get rid of it and change it for VIA with only 2 ports (so i will more dependent on external USB hubs).
I observation is that i never successfully booted with working Razer Death Adder mouse which is connected through extenal USB3 hub - on both NEC and Intel controller so suspecting problem here. Or it really needs install drivers, disconnect everything on Intel controller and reboot and after install devices.. or on individual ports on Intel controller..
Lots of testing, im only sure that USB3 with Intel controller is not working how it should be..

#4897

ruthan

Its like matrix solving i would have probably setup some online sheet with all results:
I lost my patience with half working NEC controller, so i replaced with VIA one (PCI\VEN_1106&DEV_3483&SUBSYS_34831106&REV_01)
First time i god working Razer mouse throught USB3 hub and other devices are fine too:
- Gigabyte KB
- Genius Remove
- Asus / Broadcom bluetootht
- Logitech Unified sticks for wireless devices
- Xbox 360 fake (its working fine, MS wanter 20 bucks for such adapte, unoriginal was fraction of price) wireless receiver

#4898 | ruthan | I hate USB3, keyboard on VIA controller is now working with XP, but dont with WIn10.. What is better MS or VIA driver?

#4899

gordo999

> Zitat von ⇗ daniel_k im Beitrag ¶ #4878

> iusb3hcs.sys is installed as a lower filter for the PCI bus device

⇗ @daniel_k ...lost tract which driver is which? I am currently running your amdxhc.sys and usbd.sys. They are working fine. Is there an advantage to converting to the 'switch' driver? And is that driver from W8? Thanks.

#4900 | ruthan | I have created online sheet with my USB debugging info - maybe someone will able to find some patern within: ⇗ https://docs.zoho.com/sheet/published.do...22a5b950420cb22

#4901

ruthan

Lots of testing done.. online matrix, when i put it to matrix if see that is actually much worse than i though.
With Intel - virtually only keyboard, usb mass storage are working, but even mouse after reboot. What is good that stucks are temporary if disconnect problematic device and reboot i can now login.. Its really shame because for example im using my front case ports, which are connected to Intel a lot.. and if connect something there - i for example have some game controllers here - you thing that distro is dead.. if you dont have knowledge that this is big no.no.
VIA is other matter - i never got black screen freeze is something is not working in can log into machine and all is fine.. only not working is Bluetooth dongle.. its not working even with Intel before reboot.. i abit suspect driver.. i have smaller one from net.. because Asus 500 MB driver is really scares me.. but with Nec is seemed as working (no exclamation marks at least and all virtual devices where installed).
Other not working is my Gigabyte USB keyboard its its picky one.. its working before reboot i a bit suspect, that problem could be USB2 hub in the way - i have to test it..
Is someone want to send some used drivers to debug, let me know. I found some 7 port powered hub to test - and migrate as much as possible devices to VIA controller.. but i need pause, life under desk phone as flashlight sucks..
If we want to minimize damage, we have to analyze if my mouse is so special that is not working, or not.. because for some users without PS/2.. no mouse is real problem.. A bit better are USB LAN adapter, no net, no fun, but you can at least bypass it with some additional NIC, if you have enough slots.
I will retest Pinnacle TV stick, if it is really one device, which cant lock system such way that even reboot not unlock it.. or i simply connected 2 locking devices and disconected only one.. but before i need make new image..

#4902 | mull | Universal 32bit Intel RST textmode driver v11.2.0.1006 mod+USB xHCI Host Controller (Windows 8.0 driver) Get error code STOP 7b 0x34, USB xHCI Host Controller (Windows 8.0 driver)+Generic SATA+AHCI driver Normal installation startup

#4903

diderius6

⇗ @mull
I also get sometimes during a new Setup of an original XP SP3 via Universal 32bit Intel RST textmode driver v11.2.0.1006
an unpredictable BSOD 0x7B.
Always it helps to change acpi.sys, but the underlying problem is Universal 32bit Intel RST textmode driver v11.2.0.1006 AHCI driver
Dietmar

#4904 | ruthan | ⇗ @mull - if you have PS/2 available i recommend install USB driver later after installation, its better to thing step by step.

#4905

ruthan

Ok, i some good news.. TV stick locks is also soft - so its gone about reboot.
I now with powered 7 Port USB 2 hub managed to get, all devices working.. because on Intel controller is really only keyboard.. i tested also USB flashdisk it working on Intel too, but that is.
I connected case USB3 ports to VIA controller and they are working too. I also fixed USB bluetooth on VIA controller - solution was powered hub. Only not working device with VIA controller is now Gigabyte keyboard - i tried it directly on with powered hub, its input is dead.. only backlight just lit.. its device, is not using any special driver, its just some complex HID device.
Because i was clever it the past i have new plastic USB covers, so it can lock.. evil Intel USB ports.. to not connect something to them by accident.. and lock WinXP by it.
But its life.. os its not so nice, how to it could be my cheap 7 port USB hub, when i manipulate with device, when machine is shutdown, actually power up machine.. I had at least one reboot, instead of shutdown.
BTW are these USB 3 controllers with 4 front ports + USB 3 front header fakes they are legit? I never had too much luck with them. Some manufactors, are only have 2 ports - Asmedia. Or 2 ports + header or 4 ports and no header..
Otherwise i had some perioding mouse cursor freezes with MS drivers for VIA USB3 in Windows 10, so i had to install VIA driver from WinRaid collection.

## Page 328

#4906 | canonkong | USB 3.2 GEN2x2 to NVMe device test. Because the CPU's single core performance is not very good, it does not run at the speed of 20gbps. But on the 3950x CPU, read and write speed ran to 2100MB/s! ⇗

#4907

Mov AX, 0xDEAD

# NTOSKRNL Emu_Extender

Library of missing functions for Windows XP/2003/Vista/7 NTOSKRNL.EXE
Project is intended to help in porting drivers from Windows 7/8/8.1/10 for work with Windows XP/2003/Vista/7
How-To:
1) Compile sources to make ntoskrn8.sys
2) Make corrections to target driver XXX.sys so that it loads ntoskrn8.sys instead of the original ntoskrnl.exe
3) If XXX.sys is driver made for Windows 8, change security_cookie to random value, security_cookie is constant 0x4EE640BB(x32) / 0x32A2DF2D992B(x64) inside file , change only first match !
4) Place ntoskrn8.sys to X:/Windows/sytem32/drivers/ folder
Compiling:
1) Install Windows 7 DDK v7.1.0 (download from Microsoft site)
1a) Original DDK header files has mistake with definintion of MmAllocateContiguousMemorySpecifyCacheNode, apply fix:
\WinDDK\Win7\inc\ddk\ntddk.h:
\WinDDK\Win7\inc\ddk\wdm.h:
#if (NTDDI_VERSION >= NTDDI_WIN2K)
typedef ULONG NODE_REQUIREMENT;
to:
#if (NTDDI_VERSION >= NTDDI_VISTA)
typedef ULONG NODE_REQUIREMENT;
2) Download project files to any local folder
git clone ⇗ https://github.com/MovAX0xDEAD/NTOSKRNL_Emu
3) Choose Target OS (XP, 2003, Vista or WIndows 7) for which OS Emu_Extender will be compiled. Keep in mind that depending on the target operating system the way of exporting the functions changes, if a function already exists in the kernel it will be simply redirected without injecting emulation code
4) Run shell: Start Menu\Programs\Windows Driver Kits\Win7 7600.16385.1\Build Environments\Windows XXX\YYY Free Build Environment
(XXX - target OS, YYY - target CPU)
5) In shell change current directory to local project folder
6) In shell type command BLD to compile project
7) Compiled ntoskrn8.sys will be in ntoskrn8/objfre_XXX_x86/YYY folder

# STORPORT Windows 7 Emu_Extender

This is Library of missing functions for Windows 7 STORPORT.SYS v6.1.7601.23403 to emulate Windows 8 STORPORT.SYS
How-To:
1) Compile ntoskrnl Emu_Extender
2) Place storpor8.sys to X:/Windows/system32/drivers/ folder
3) Make corrections to target xxx.sys so that it loads storpor8.sys instead of the original storport.sys
4) Place backported storport.sys from Windows 7 to X:/Windows/system32/drivers/ folder

# Ported drivers:

Windows 7's WDF 1.11 for Windows XP/2003
Last version for Windows XP/2003 is 1.9, but possible to backport 1.11 version:
1) Get files from Windows 7 Updates (KB3125574):

           WDF01000.SYS	v1.11.9200.20755
           WdfLdr.sys	v1.11.9200.16384

2) In WDF01000.SYS replace string ntoskrnl.exe to ntoskrn8.sys in import section
3) Recalc checksum
If need coexist with original WDF1.9 drivers:
4) Rename WDF01000.SYS->WDF01_W8.SYS, WdfLdr.sys->WdfLdr8.sys
5) In WDF01_W8.SYS replace string WdfLdr.sys to WdfLdr8.sys in import section
6) In WdfLdr8.sys replace unicode string \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d000 to \Registry\Machine\System\CurrentControlSet\Services\Wdf%02d_w8
7) In WdfLdr8.sys replace hex pattern F6 78 1B F6 to F6 EB 1B F6 (x32), to (x64)
8) In target driver xxx.sys replace string WdfLdr.sys to WdfLdr8.sys in import section
9) In .INF of ported driver add creating new service:

           AddService=WDF01_W8,,  WDF.AddService
    ....
                 [WDF.AddService]
           DisplayName    = "Windows Driver Framework v1.11 for XP/2003"
           ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
           StartType      = 3                  ; SERVICE_DEMAND_START
           ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
           ServiceBinary  = %12%\WDF01_W8.SYS
           LoadOrderGroup = Base

10) Recalc checksum of all edited *.sys
Windows 7's Storport.sys for Windows XP
Storport was released starting from Windows 2003, but possible to backport Windows 7 version:
1) Get files from Windows 7 Updates (KB3125574):

           storport.sys	v6.1.7601.23403

2) In storport.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section
3) Storport uses MSI interrupts, need to force use only legacy/non-MSI interrupts
x32 - replace hex pattern 8B 8E 3C 01 00 00 to B9 00 00 00 00 90 (mov ecx, [esi+13Ch] -> mov ecx, 0)
x64 - replace hex pattern 8B 83 C0 01 00 00 to B8 00 00 00 00 90 (mov eax, [rbx+1C0h] -> mov eax, 0)
4) Recalc checksum
Windows 7's NVMe driver for Windows XP
1) Get files from Windows 7 Updates (KB3125574):

           stornvme.sys	v6.1.7601.23403

2) MS Windows 7 NVMe driver require storport.sys from Windows 7, use backported one
Windows 8's USB3 driver for Windows XP
USB3 driver from Windows 8 require WDF 1.11, use backported one.
1) Get required files from Windows 8 (KB4534283/4556840, KB2984005, RTM ISO):

       ucx01000.sys         v6.2.9200.22453
       usbhub3.sys          v6.2.9200.21180
       usbxhci.sys          v6.2.9200.22099
       wpprecorder.sys      v6.2.9200.16384
       usbd.sys             v6.2.9200.20761

from Vista Beta/Longhorn 5456.5:

           ksecdd.sys v6.0.5456.5

2) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, wpprecorder.sys, usbd.sys change security_cookie to random value
3) In files ucx01000.sys, usbhub3.sys, usbxhci.sys, ksecdd.sys replace string name "ntoskrnl.exe" to "ntoskrn8.sys' in import section
4) Rename ksecdd.sys->ksecd8.sys, usbd.sys->usbd_w8.sys
5) In usbhub3.sys replace string name "ksecdd.sys" to "ksecd8.sys' in import section
6) In usbhub3.sys replace string name "usbd.sys" to "usbd_w8.sys' in import section,
7) Recalc checksum
Windows 8's STORAHCI driver for Windows XP
STORAHCI driver requires storport.sys from Windows 8, but possible to use storport.sys from Windows 7
storport.sys from Windows 7 more compatible with Windows Xp/2003 because it still call required PoStartNextPowerIrp
when processing power IRPs. Microsoft removed calls to PoStartNextPowerIrp in Windows 8's storport.sys, without this call
Windows XP/2003 kernel cannot finish current power IRP and start next IRP => it generate BSOD (0x0000009F).
Also storport.sys from Windows 7 has compatibility mode to allow old XP/2003 kernels write crashdumps through storport based disk drivers. In storport.sys from Windows 8 compatibility mode was removed, writing crashdumps possible only with new kernels.
Take attention:
WinWindows 8's STORAHCI + Windows 7's STORPORT may have significal performance drop and high CPU usage, there is no fix yet
1) Get files from Windows 8 (RTM ISO):

       storahci.sys v6.2.9200.16384

2) In storahci.sys replace string storport.sys to storport8.sys in import section
3) storahci.sys was compiled with Windows 8 DDK's storport.h and writes to new fields of _PORTCONFIGURATION_INFORMATION, these fields not exist in Windows 7's storport.sys
Need to skip these writes to avoid damaging structures in memory:
x32 - Replace hex pattern 83 A6 C8 00 00 00 00 to 90 90 90 90 90 90 90 (and dword ptr [esi+0C8h], 0 -> nop)
x32 - Replace hex pattern 83 8E CC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [esi+0CCh], 3 -> nop)
x64 - Replace hex pattern 44 89 B7 D8 00 00 00 to 90 90 90 90 90 90 90 (mov [rdi+0D8h], r14d -> nop)
x64 - Replace hex pattern 83 8F DC 00 00 00 03 to 90 90 90 90 90 90 90 (or dword ptr [rdi+0DCh], 3 -> nop)
If you compile storahci from sources (from Windows 8 DDK Samples), comment two lines:

       ConfigInfo->BusResetHoldTime = 0;
       ConfigInfo->FeatureSupport |= STOR_ADAPTER_FEATURE_STOP_UNIT_DURING_POWER_DOWN;

4) In storahci.sys change security_cookie to random value
5) Recalc checksum
Windows 7's MSAHCI driver for Windows XP
1) Get files from Windows 7 Updates (KB3125574):

       atapi.sys    v6.1.7601.23403
       ataport.sys  v6.1.7601.23403
       msahci.sys   v6.1.7601.23403
       pciidex.sys  v6.1.7601.23403

2) In ataport.sys, pciidex.sys replace string ntoskrnl.exe to ntoskrn8.sys in import section
3) pciidex.sys uses MS Internal/Undocumented HalDispatchTable way to call functions from Kernel/HAL,
For Windows XP/2003 x32 need to use compatible variant:
x32: replace hex pattern FF 50 3C to FF 50 40, same in asm code:

       mov     eax, ds:HalDispatchTable
         ...
       call    dword ptr [eax+3Ch] => call    dword ptr [eax+40h]

x64: replace hex pattern
1) FF 50 78 to EB 2A 90
2) offset +2Ch: CC CC CC CC CC CC CC CC to FF 90 80 00 00 00 EB CF, same in asm code:

           mov     rax, cs:HalDispatchTable
                 ...
           call    qword ptr [rax+78h] => jmp patch
    orig:
           mov     r10d, eax

    patch:
          call    qword ptr [eax+80h]
          jmp     orig

4) Recalc checksum
5) MSHDC.INF from Windows 7 may conflict with original mshdc.inf from Windows XP/2003
For example msahci enumerates IDE/SATA channels as InternalIDEChannel and compatible ID as *PNP0600.
Original mshdc.inf for *PNP0600 will install wrong Standard IDE/ESDI Hard Disk Controller driver
Intel RSTe Enterprise AHCI/RAID driver 4.7.0.1098 for Windows XP/2003 +
Intel RST AHCI/RAID driver (v11.x-15.x, last compatible 15.9.8/15.44.0) for Windows XP/2003
These drivers require storport.sys from Windows 7, use backported one.
1) In file iaStorA.sys/iaStorAC.sys/iaStorAVC.sys replace string 'ntoskrnl.exe' to 'ntoskrn8.sys' in import section (do not change second string 'NTOSKRNL.exe')
2) Recalc checksum
Download Sources
⇗ https://github.com/MovAX0xDEAD/NTOSKRNL_Emu
Implemented Func List v10 :

    _chkstk
    _i64toa_s
    _i64tow_s
    _itoa_s
    _itow_s
    _ltoa_s
    _ltow_s
    _makepath_s
    _snprintf_s
    _snscanf_s
    _snwprintf_s
    _snwscanf_s
    _splitpath_s
    _strnset_s
    _strset_s
    _strtoui64
    _swprintf
    _ui64toa_s
    _ui64tow_s
    _ultoa_s
    _ultow_s
    _vsnprintf_s
    _vsnwprintf_s
    _vswprintf
    _wcsnset_s
    _wcsset_s
    _wmakepath_s
    _wsplitpath_s
    _wtoi
    _wtol
    DbgkLkmdRegisterCallback
    EmClientQueryRuleState
    EtwActivityIdControl
    EtwEventEnabled
    EtwProviderEnabled
    EtwRegister
    EtwRegisterClassicProvider
    EtwUnregister
    EtwWrite
    EtwWriteString
    EtwWriteTransfer
    ExAcquireRundownProtectionCacheAware
    ExAcquireRundownProtectionCacheAwareEx
    ExAllocateCacheAwareRundownProtection
    ExDeleteLookasideListEx
    ExEnterCriticalRegionAndAcquireFastMutexUnsafe
    ExEnterCriticalRegionAndAcquireResourceExclusive
    ExEnterCriticalRegionAndAcquireResourceShared
    ExEnterPriorityRegionAndAcquireResourceExclusive
    ExEnterPriorityRegionAndAcquireResourceShared
    ExFreeCacheAwareRundownProtection
    ExfReleasePushLockShared
    ExfTryToWakePushLock
    ExGetFirmwareEnvironmentVariable
    ExInitializeLookasideListEx
    ExInitializeRundownProtectionCacheAware
    ExReInitializeRundownProtectionCacheAware
    ExReleaseFastMutexUnsafeAndLeaveCriticalRegion
    ExReleaseResourceAndLeaveCriticalRegion
    ExReleaseResourceAndLeavePriorityRegion
    ExReleaseRundownProtectionCacheAware
    ExReleaseRundownProtectionCacheAwareEx
    ExRundownCompletedCacheAware
    ExSetFirmwareEnvironmentVariable
    ExSizeOfRundownProtectionCacheAware
    ExWaitForRundownProtectionReleaseCacheAware
    IoAllocateSfioStreamIdentifier
    IoConnectInterruptEx
    IoDisconnectInterruptEx
    IoFreeSfioStreamIdentifier
    IoGetActivityIdIrp
    IoGetAffinityInterrupt
    IoGetDevicePropertyData
    IoGetIoPriorityHint
    IoGetSfioStreamIdentifier
    IoInitializeWorkItem
    IoQueueWorkItemEx
    IoSetActivityIdIrp
    IoSetDevicePropertyData
    IoSizeofWorkItem
    IoUninitializeWorkItem
    IoUnregisterPlugPlayNotificationEx
    KdRefreshDebuggerNotPresent
    KeAcquireGuardedMutex
    KeAcquireGuardedMutexUnsafe
    KeAlertThread
    KeAreAllApcsDisabled
    KeEnterGuardedRegion
    KeExpandKernelStackAndCallout
    KeGetCurrentNodeNumber
    KeGetCurrentProcessorNumberEx
    KeGetProcessorIndexFromNumber
    KeGetProcessorNumberFromIndex
    KeInitializeGuardedMutex
    KeInvalidateAllCaches
    KeInvalidateRangeAllCaches
    KeLeaveGuardedRegion
    KeQueryActiveGroupCount
    KeQueryActiveProcessorCount
    KeQueryActiveProcessorCountEx
    KeQueryDpcWatchdogInformation
    KeQueryGroupAffinity
    KeQueryHighestNodeNumber
    KeQueryLogicalProcessorRelationship
    KeQueryMaximumGroupCount
    KeQueryMaximumProcessorCount
    KeQueryMaximumProcessorCountEx
    KeQueryNodeActiveAffinity
    KeReleaseGuardedMutex
    KeReleaseGuardedMutexUnsafe
    KeRevertToUserAffinityThreadEx
    KeRevertToUserGroupAffinityThread
    KeSetActualBasePriorityThread
    KeSetCoalescableTimer
    KeSetSystemAffinityThreadEx
    KeSetSystemGroupAffinityThread
    KeSetTargetProcessorDpcEx
    KeTestAlertThread
    KeTryToAcquireGuardedMutex
    LdrResFindResource
    LdrResFindResourceDirectory
    LpcReplyWaitReplyPort
    LpcRequestWaitReplyPortEx
    LpcSendWaitReceivePort
    memcpy_s
    memmove_s
    MmAllocateContiguousMemorySpecifyCacheNode
    MmAllocateContiguousNodeMemory
    ObDeleteCapturedInsertInfo
    ObfDereferenceObjectWithTag
    ObfReferenceObjectWithTag
    ObGetObjectType
    ObQueryNameInfo
    PcwAddInstance
    PcwCloseInstance
    PcwCreateInstance
    PcwRegister
    PcwUnregister
    PoDisableSleepStates
    PoEndDeviceBusy
    PoGetSystemWake
    PoReenableSleepStates
    PoRegisterPowerSettingCallback
    PoSetDeviceBusyEx
    PoSetSystemWake
    PoStartDeviceBusy
    PoUnregisterPowerSettingCallback
    PoUserShutdownInitiated
    PsAcquireProcessExitSynchronization
    PsEnterPriorityRegion
    PsGetCurrentProcessWin32Process
    PsGetCurrentThreadProcess
    PsGetCurrentThreadProcessId
    PsGetCurrentThreadTeb
    PsGetCurrentThreadWin32Thread
    PsGetCurrentThreadWin32ThreadAndEnterCriticalRegion
    PsGetProcessSessionIdEx
    PsIsProtectedProcess
    PsIsSystemProcess
    PsLeavePriorityRegion
    PsReleaseProcessExitSynchronization
    PsSetCreateProcessNotifyRoutineEx
    RtlCheckPortableOperatingSystem
    RtlGetIntegerAtom
    RtlGetThreadLangIdByIndex
    RtlIsNtDdiVersionAvailable
    RtlQueryElevationFlags
    RtlQueryRegistryValuesEx
    RtlSetPortableOperatingSystem
    SeReportSecurityEventWithSubCategory
    SeSetAuditParameter
    SeSetAuthorizationCallbacks
    sprintf_s
    sscanf_s
    strcat_s
    strcpy_s
    strncat_s
    strncpy_s
    strnlen
    strtok_s
    swprintf_s
    swscanf_s
    vsprintf_s
    vswprintf_s
    wcscat_s
    wcscpy_s
    wcsncat_s
    wcsncpy_s
    wcsnlen
    wcstoul
    ZwAllocateLocallyUniqueId
    ZwAlpcConnectPort
    ZwAlpcSendWaitReceivePort
    ZwQueryLicenseValue
    ZwQueryVirtualMemory

    Comparing files ataport.sys and ../ATAPORT.SYS
    00000138: 68 69
    00000139: 35 1D
    0001B093: 6C 38
    0001B095: 65 73
    0001B096: 78 79
    0001B097: 65 73

    Comparing files iaStorA.sys and ../IASTORA.SYS
    00000159: 15 FD
    000687F9: 6C 38
    000687FB: 65 73
    000687FC: 78 79
    000687FD: 65 73

    Comparing files ksecd8.sys and ../KSECD8.SYS
    00000148: 44 45
    00000149: 18 00
    0005AEBB: 6C 38
    0005AEBD: 65 73
    0005AEBE: 78 79
    0005AEBF: 65 73

    Comparing files storahci.sys and ../STORAHCI.SYS
    00000140: 68 5B
    00000141: DC CA
    00000C2C: 83 90
    00000C2D: A6 90
    00000C2E: C8 90
    00000C2F: 00 90
    00000C30: 00 90
    00000C31: 00 90
    00000C32: 00 90
    00000C94: 83 90
    00000C95: 8E 90
    00000C96: CC 90
    00000C97: 00 90
    00000C98: 00 90
    00000C99: 00 90
    00000C9A: 03 90
    0000D000: 4E DE
    0000D001: E6 AD
    0000D002: 40 BE
    0000D003: BB EF
    0000D491: 74 38

    Comparing files storport.sys and ../STORPORT.SYS
    00000130: CB CC
    00000131: 5C 36
    00000132: 02 03
    00004E19: 8B B9
    00004E1A: 8E 00
    00004E1B: 3C 00
    00004E1C: 01 00
    00004E1E: 00 90
    0001D49B: 6C 38
    0001D49D: 65 73
    0001D49E: 78 79
    0001D49F: 65 73

    Comparing files uaspstor.sys and ../UASPSTOR.SYS
    00000140: 4B A3
    00000141: 25 D6
    00000142: 02 01
    0000E200: 4E DE
    0000E201: E6 AD
    0000E202: 40 BE
    0000E203: BB EF
    0000F189: 6C 38
    0000F18B: 65 73
    0000F18C: 78 79
    0000F18D: 65 73
    0000F24B: 74 38
    0000F27E: 2E 38
    0000F27F: 53 2E
    0000F280: 59 53
    0000F281: 53 59
    0000F282: 00 53
    0000F2FC: 6F 38
    0000F2FD: 72 2E
    0000F2FE: 64 73
    0000F2FF: 65 79
    0000F300: 72 73
    0000F301: 2E 00
    0000F302: 73 00
    0000F303: 79 00
    0000F304: 73 00

    Comparing files ucx01000.sys and ../UCX01000.SYS
    00000140: 0B 83
    00000141: 0A 17
    00014E00: 4E DE
    00014E01: E6 AD
    00014E02: 40 BE
    00014E03: BB EF
    00018D0F: 6C 38
    00018D11: 65 73
    00018D12: 78 79
    00018D13: 65 73
    00018DCC: 2E 38
    00018DCD: 53 2E
    00018DCE: 59 53
    00018DCF: 53 59
    00018DD0: 00 53
    00018E08: 57 77
    00018E0B: 52 72
    00018E0E: 6F 38
    00018E0F: 72 2E
    00018E10: 64 73
    00018E11: 65 79
    00018E12: 72 73
    00018E13: 2E 00
    00018E14: 73 00
    00018E15: 79 00
    00018E16: 73 00

    Comparing files usbd8.sys and ../USBD8.SYS
    00000140: 7D 8B
    00000141: 5E 5A
    00001600: 4E DE
    00001601: E6 AD
    00001602: 40 BE
    00001603: BB EF

    Comparing files usbhub3.sys and ../USBHUB3.SYS
    00000140: 62 A6
    00000141: 3C DF
    00000142: 06 05
    00009058: 75 EB
    00027C00: 4E DE
    00027C01: E6 AD
    00027C02: 40 BE
    00027C03: BB EF
    0004591E: 2E 38
    0004591F: 53 2E
    00045920: 59 53
    00045921: 53 59
    00045922: 00 53
    00045923: 90 00
    00045928: 2E 38
    00045929: 53 2E
    0004592A: 59 53
    0004592B: 53 59
    0004592C: 00 53
    0004592D: 90 00
    00045935: 64 38
    0004593C: 57 77
    0004593F: 52 72
    00045942: 6F 38
    00045943: 72 2E
    00045944: 64 73
    00045945: 65 79
    00045946: 72 73
    00045947: 2E 00
    00045948: 73 00
    00045949: 79 00
    0004594A: 73 00
    0004595B: 6C 38
    0004595D: 65 73
    0004595E: 78 79
    0004595F: 65 73

    Comparing files usbxhci.sys and ../USBXHCI.SYS
    00000148: 24 9C
    00000149: E1 EE
    0002A800: 4E DE
    0002A801: E6 AD
    0002A802: 40 BE
    0002A803: BB EF
    00034BC3: 6C 38
    00034BC5: 65 73
    00034BC6: 78 79
    00034BC7: 65 73
    00034D8E: 57 77
    00034D91: 52 72
    00034D94: 6F 38
    00034D95: 72 2E
    00034D96: 64 73
    00034D97: 65 79
    00034D98: 72 73
    00034D99: 2E 00
    00034D9A: 73 00
    00034D9B: 79 00
    00034D9C: 73 00
    00034FE8: 2E 38
    00034FE9: 53 2E
    00034FEA: 59 53
    00034FEB: 53 59
    00034FEC: 00 53

    Comparing files WDF01_W8.SYS and ../WDF01_W8.SYS
    00000138: A0 F7
    00000139: 5C 95
    0007655A: 2E 38
    0007655B: 53 2E
    0007655C: 59 53
    0007655D: 53 59
    0007655E: 00 53
    0007655F: 90 00
    00076567: 6C 38
    00076569: 65 73
    0007656A: 78 79
    0007656B: 65 73

    Comparing files WdfLdr8.sys and ../WDFLDR8.SYS (v1.11.9200.16384)
    .....

    Comparing files WdfLdr8.sys and ../WDFLDR8.SYS (v1.11.9200.16648)
    00000150: 32 B0
    00000151: F8 6B
    00000152: 00 01
    000011F2: 30 5F
    000011F4: 30 77
    000011F6: 30 38
    000022C9: 78 EB

    Comparing files wpprec8.sys and ../WPPREC8.SYS
    00000140: 04 12
    00000141: 23 1F
    00001E00: 4E DE
    00001E01: E6 AD
    00001E02: 40 BE
    00001E03: BB EF

#4908 | daniel_k | ⇗ @Mov AX, 0xDEAD, impressed! Thought you were on a break, but still working on something! Thanks for sharing it with us! Theoretically, functions from WppRecorder.sys can be added to ntoskrn8.sys, right?

#4909

daniel_k

> Zitat von ⇗ gordo999 im Beitrag ¶ #4899

> @daniel_k ...lost tract which driver is which? I am currently running your amdxhc.sys and usbd.sys. They are working fine. Is there an advantage to converting to the 'switch' driver? And is that driver from W8? Thanks.

Even with USB3 enabled in BIOS, 3rd/4th gen chipset require the HCSwitch lower filter driver to program certain device registers, otherwise you're limited to USB2 speeds.
Regarding USB3 driver, we are not using the amdxhc driver anymore, as it has issues after some plugging/unplugging.
⇗ @Mov AX, 0xDEAD ported the Win8 driver, which is a perfect solution, even supporting UASP (USB Attached SCSI Protocol), although is in alpha state yet. If you want it, drop me a PM.

#4910

daniel_k

⇗ @Mov AX, 0xDEAD
I'm getting this error when building:

    1>errors in directory c:\release0
    1>nmake : error: c:\release0\objfre_wxp_x86\i386\_objects.mac was changed
    during the build process and the build results may not be valid.
    Please re-build this directory.

I can compile OFA NVME driver, so no problem with my DDK install.
EDIT: Fixed by adding TARGETPATH=obj$(BUILD_ALT_DIR) below TARGETTYPE=EXPORT_DRIVER in sources file.

#4911 | infuscomus | ⇗ @Mov AX, 0xDEAD You're releasing this as open source?! Awesome! Thanks! edit: a question concerning cookie_const - what does a windows driver do with this value? why does it BSOD if we don't change it?
#4912 | diderius6 | ⇗ @Mov AX, 0xDEAD Is it possible to enable the Lan driver i219 from Intel under XP SP3 with this helper, have a nice day Dietmar

#4913

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4910

> Fixed by adding TARGETPATH=obj$(BUILD_ALT_DIR) below TARGETTYPE=EXPORT_DRIVER in sources file.

thanks for fix !
archive updated

#4914

Mov AX, 0xDEAD

> Zitat von ⇗ infuscomus im Beitrag ¶ #4911

> @Mov AX, 0xDEAD
> You're releasing this as open source?! Awesome!

Main benefit is MS "copyright" binary code avoidance as much as possible
Extender is not new idea, Dibya done his extenders before, but he used many stolen code from MS binaries(???)
(i dont know exactly where code taken, sorry Dibya if I'm wrong)

#4915

Mov AX, 0xDEAD

⇗ @diderius6

> Zitat von ⇗ diderius6 im Beitrag ¶ #4912

> Is it possible to enable the Lan driver i219 from Intel under XP SP3 with this helper,

I dont know, extender has only few implemented functions and is not full functionaly
If someone has time and C knowledge, he can add more missed imports.
LAN driver may depends on NDIS6 (another driver framework from MS), XP has only NDIS5

#4916

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4908

> Theoretically, functions from WppRecorder.sys can be added to ntoskrn8.sys, right?

Yes, ntoskrn8.sys can be multi router for export<->import from many *.sys/*.dll:
#pragma comment (linker, "/export:xxxxx=hal.xxxxxx")
#pragma comment (linker, "/export:yyyyy=ntoskrnl.yyyyy")
in case WppRecorder.sys all emulated funcs will be internal

#4917

diderius6

⇗ @daniel_k
I test, why I can boot an uaspstor device via USBSTOR.sys
but not via uaspstor.sys from win8 with storport from win7.1 .
The uaspstor.sys driver is not loaded early enough, even I set Group = System Reserved start = 0 Tag = 1 (means first of all).
This should move this driver to one of the earliest loaded drivers.
Always this driver uaspstor.sys loads after mup.sys, so this is second boot stage,
means uaspstor.sys not loaded at boot time.
This is the reason for BSOD 0x7B there
Dietmar
PS: With USBSTOR.sys this one is loaded first of all in first boot stage, means no BSOD 0x7B.

#4918 | daniel_k | ⇗ @diderius6 Don't know if it makes any difference, but remember that uaspstor.sys is a SCSI driver. During Setup, usbstor is loaded in [InputDevicesSupport], uaspstor should be in [SCSI], in theory.

#4919

daniel_k

⇗ @Mov AX, 0xDEAD
Does changing the function name from "decorated" to "undecorated", affects the behavior of the Extender?
For example, _IoGetDevicePropertyData@32 -> IoGetDevicePropertyData
This could help when compiling the Extender to any archtecture, if you know what I mean.
EDIT: Nevermind, I see it doesn't change anything, binary is identical.

#4920 | infuscomus | can you mix ASM with C code? or is this a bad idea?

## Page 329

#4921

Dibya

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4914

> > Zitat von ⇗ infuscomus im Beitrag ¶ #4911

> > @Mov AX, 0xDEAD
> > You're releasing this as open source?! Awesome!

> Main benefit is MS "copyright" binary code avoidance as much as possible
> Extender is not new idea, Dibya done his extenders before, but he used many stolen code from MS binaries(???)
> (i dont know exactly where code taken, sorry Dibya if I'm wrong)

I did modify XP files but none of my codes were from Microsoft . Mostly were from wine , some stub and few own implementation like GetTickCount64 , few were taken from OnecoreApi and BlackWingcat .
These do act like MS code but they arenot . Some are hijack job like sending FlsAlloc to TlsAlloc.
Their were Vista binaries though like MSVCRT.
Initial attempt i tried to copy vista code but they never worked (Those binaries never got out in wild).
By the way thanks for XHCI Driver It is awesome
If i ever get something like KernelEx for 9x , which will redirect all missing api to my dll from programs inside a specific program folder like FLStudio , I will release all my sources under BSD or Apache license.

#4922

Dibya

> Zitat von ⇗ infuscomus im Beitrag ¶ #4920

> can you mix ASM with C code? or is this a bad idea?

You can use inline assembly but dont try to copy Vista code on XP , it will fail

#4923 | ruthan | Maybe obvious for someone but i finally find how to real life its USB legacy option in the Bios - when is enabled i can quit WinXP boot disk check, because its slow as hell.. Its need for some versions of Grub2 too..

#4924

Mov AX, 0xDEAD

⇗ @Dibya

> Zitat von ⇗ Dibya im Beitrag ¶ #4921

> I did modify XP files but none of my codes were from Microsoft . Mostly were from wine , some stub and few own implementation like GetTickCount64 , few were taken from OnecoreApi and BlackWingcat .
> These do act like MS code but they arenot . Some are hijack job like sending FlsAlloc to TlsAlloc.
> Their were Vista binaries though like MSVCRT.

Sorry for mess, take my apologies
I just saw ExKernel.asm, it containts many deassembled chunks from some binaries (many from from BlackWingCat's files)

#4925

Mov AX, 0xDEAD

> Zitat von ⇗ daniel_k im Beitrag ¶ #4919

> @Mov AX, 0xDEAD
> Does changing the function name from "decorated" to "undecorated", affects the behavior of the Extender?
> For example, _IoGetDevicePropertyData@32 -> IoGetDevicePropertyData

First i used __declspec( dllexport ) instead .def to have undecorated names, but it works only if function has __cdecl calling convention, x32 WinAPI is not __cdecl, __declspec( dllexport ) make decorated variant. Finally i decided to use .def as uniform name translator.
_k8 suffix used for functions, already defined in DDK's *.h - i prefer to have C equivalents instead MS compatible binaries (procgrp.lib/intex.lib)

#4926

Dibya

"Mov AX, 0xDEAD"|p114478]⇗ @Dibya

> Zitat von ⇗ Dibya im Beitrag ¶ #4921

> I did modify XP files but none of my codes were from Microsoft . Mostly were from wine , some stub and few own implementation like GetTickCount64 , few were taken from OnecoreApi and BlackWingcat .
> These do act like MS code but they arenot . Some are hijack job like sending FlsAlloc to TlsAlloc.
> Their were Vista binaries though like MSVCRT.

Well you can't code cave in C language so I used to make dll of my code in visual studio 2010 and then use IDA and made in MASM compatible to remove extra junk and then I used to compile them in masm and then used hex editor to move my code to xp DLLs .
Then I used either rloew modexp / Blackwingcat pemaker to add a export entry .
Then fixed those broken subroutines and codes with Ida & Address fixer in pemaker .
Boom ! You got a extended kernel now .

#4927 | Outbreaker | HI. Dose someone know if the "secnvmeF.sys" file should be added to the "[SCSI.Load]" or "[BusExtenders.Load]" or "[BootBusExtenders.Load]" the funny thing is they all work.

#4928

asdf23451

> Zitat von ⇗ daniel_k im Beitrag ¶ #3962

> AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018
> - Fixed XP/Server 2003 compatibility by re-adding PoStartNextPowerIrp calls, luckily the code didn't really change after build 145, could find all proper locations for every call. Interesting info:
> ⇗ PoStartNextPowerIrp - ⇗ Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
> - Removed IoSetDevicePropertyData dependency, only found in Vista and later, doesn't affect functionality.
> - Removed BCrypt functions dependencies (Ksecdd.sys), only found in Vista and later and re-added code from build 145.
> - Combined hub and controller INFs into a single amdxhc.inf for easier installation and integration.

I'm looking for that driver, but I don't see any download on the post, could I get a link to the driver?

#4929

Outbreaker

> Zitat von ⇗ asdf23451 im Beitrag ¶ #4928

> > Zitat von ⇗ daniel_k im Beitrag ¶ #3962

> > AMDXHC 1.1.0.0276 Final Driver, dated Dec 4, 2018
> > - Fixed XP/Server 2003 compatibility by re-adding PoStartNextPowerIrp calls, luckily the code didn't really change after build 145, could find all proper locations for every call. Interesting info:
> > ⇗ PoStartNextPowerIrp - ⇗ Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE
> > - Removed IoSetDevicePropertyData dependency, only found in Vista and later, doesn't affect functionality.
> > - Removed BCrypt functions dependencies (Ksecdd.sys), only found in Vista and later and re-added code from build 145.
> > - Combined hub and controller INFs into a single amdxhc.inf for easier installation and integration.

> I'm looking for that driver, but I don't see any download on the post, could I get a link to the driver?

⇗ https://forums.mydigitallife.net/threads...hardware.81607/

#4930

infuscomus

⇗ @Outbreaker
from the original samsung nvme inf file - it is SCSI miniport

    [nvme_Service_Inst]
    ServiceType    = %SERVICE_KERNEL_DRIVER%
    StartType      = %SERVICE_BOOT_START%
    ErrorControl   = %SERVICE_ERROR_NORMAL%
    ServiceBinary  = %12%\secnvme.sys
    LoadOrderGroup = SCSI miniport
    AddReg         = pnpsafe_pci_addreg

#4931 | Outbreaker | ⇗ @infuscomus That's for the secnvme.sys file, but their is no LoadOrderGroup entry for the secnvmeF.sys file in the .inf file.

#4932

infuscomus

⇗ @Outbreaker
there is no loadordergroup for the filter driver in the original inf either - i'm assuming it's unnecessary.

    [nvmeF_Service_Inst]
    ServiceType    = %SERVICE_KERNEL_DRIVER%
    StartType      = %SERVICE_BOOT_START%
    ErrorControl   = %SERVICE_ERROR_NORMAL%
    ServiceBinary  = %12%\secnvmeF.sys

#4933 | daniel_k | ⇗ @Mov AX, 0xDEAD Are you working on the Extender? I plan to implement some imports, just want to make sure you already didn't.
#4934 | daniel_k | ⇗ @Outbreaker Filter driver is a kind of a plug-in that changes/improves behavior of a driver. Just integrate the driver and, during install, INF file will install the filter. Keep it simple!

#4935

Mov AX, 0xDEAD

⇗ @daniel_k

> Zitat von ⇗ daniel_k im Beitrag ¶ #4933

> Are you working on the Extender?
> I plan to implement some imports, just want to make sure you already didn't.

Yes, i work currently on all available stuff from intex.lib+procgrp.lib, missed win7/win8 functs (required for already ported driver) delayed for few days
You can download last develop version in Release3_devonly.zip if want to sync with me
important - fixed bug with calling convection of wcsncpy_s and added x64 compatible build setting, so w2003_x64 buld is OK on my machine (not sure about working state :)

## Page 330

#4936

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4935

> You can download last develop version in release2.zip if want to sync with me

Sure, where can I download it? I want to contribute somehow.
Are you planning to create a repository in your GitHub profile?

#4937

Mov AX, 0xDEAD

⇗ @daniel_k

> Zitat

> where can I download it?

first post about project on page #328

> Zitat von ⇗ daniel_k im Beitrag ¶ #4936

> Are you planning to create a repository in your GitHub profile?

I dont know how merge users' requests on github, so mainly i used it as "share" site
but i can create repository if it helps

#4938

daniel_k

> Zitat von ⇗ Mov AX, 0xDEAD im Beitrag ¶ #4937

> first post about project on page #328

You've just added it, thanks.

> Zitat

> I dont know how merge users' requests on github, so mainly i used it as "share" site
> but i can create repository if it helps

Me neither.
To add imports from other files, better to keep the code in another .c file, right?

#4939 | daniel_k | ⇗ @Mov AX, 0xDEAD Was Reading the MS docs regarding Power IRPs, uaspstor.sys calls IofCallDriver, but on OSes earlier then Vista, it must call PoCallDriver to pass a power IRP. However, after replacing the function, system won't start: BSOD 0xA: IRQL_NOT_LESS_OR_EQUAL

#4940

Sircam

I have a Lenovo G50-80 laptop.
Im trying to install XP x86 on the hard drive. I have integrated drivers into an ISO on a CD which now allow me to see the Hard drive in the XP setup but I can not get past that point.
The keyboard(internal and spare external) is not recognised. As soon as the setup displays "Setup is starting Windows" lights on the external keyboard turn off
Ive tried WinXP-IE_Optional_Patch_Integrator_v2.3.3b14.zip to integrate USB drivers. Are there any other drivers which someone can suggest to use?

#4941

daniel_k

⇗ @Mov AX, 0xDEAD
I've added stubs for all WppRecorder.sys, and it works fine.
However, unless I comment one of these lines in ntoskrn8.src:

    KeQueryGroupAffinity=		_KeQueryGroupAffinity@4
    KeQueryGroupAffinity=		KeQueryGroupAffinity

I get the following error:

    ntoskrn8.def : warning LNK4197: export 'KeQueryGroupAffinity' specified multiple times; using first specification

#4942 | infuscomus | ⇗ @Sircam I have an idea for what the problem might be - I'll PM you

#4943

gordo999

> Zitat von ⇗ diderius6 im Beitrag ¶ #4912

> Is it possible to enable the Lan driver i219 from Intel under XP SP3 with this helper,
> have a nice dayDietmar

⇗ @diderius6 ...ntoskrnl is not the main problem with LAN i219. Ndis.sys in XP has about 30 missing functions that are required by i219. Not all of them may be critical. Also, if you use ndis.sys from w7 there is another file required.
If you look at the W7 INF file for LAN i219, it is much more detailed than the the XP INF file for the older LAN driver. I have wondered about adding some of the W7 INF entries to the XP INF file or just entering them right into the registry. I guess it depends on how well you want XP to work with the features available in W7 i219 LAN hardware.

#4944

gordo999

> Zitat von ⇗ Sircam im Beitrag ¶ #4940

> I have a Lenovo G50-80 laptop....The keyboard(internal and spare external) is not recognised. As soon as the setup displays "Setup is starting Windows" lights on the external keyboard turn off

⇗ @Sircam ...did you integrate the USB drivers? Just noticed that infuscomus may have a solution for you.

#4945

ruthan

I probably find out why PS/2 is not working with Z370 old install build.. I met same error with Z390, its some Vmware leftover service, when i remove Vmware keyboard driver, all input except remote one from remote desktop apps is just not working.. Work around is not removing it, but i would like to get rid of it. I already tried VMware cleaner, but its not clean this one.
I also fixed not working PS/2 with Win10 and Z390 for some reason PS/2 Scroll mouse driver was installed when i force PS/2 Compatible driver, its no working fine.
Otherwise i had some annoying false detection with some modified drivers and Avira antivirus.. i submited false reports, mouse of them are now fixed.. and now more detected. Last one which is still detected is wdf01_w8.sys. Workaround is simply turn off antivirus for moment of manipulation with files, because otherswise this drivers are not copied where it should be etc.. you can ignore detection, but Avira design is stupid so its still complied about same file, is other locations.
BTW are you using some WinXP antivirus, i was using MS Security essesntials, but it can be updated by normal ways, but only with some annoying workarounds afaik, maybe is there something better?

#4946

ruthan

Exist some better than MS 2D driver universal driver for Windows XP? Im still debugging without WinXP GPU and scrolling speed is very slow..
Otherwise is there nice now too much known tool for removing some not more installed device from WinXP:
⇗ https://www.neowin.net/news/ghostbuster-1080/
I dunno if they can make some real problems, but it probably at least slowdown system. Of course be careful do backup, i has some build in create restore point on option but still. This could help with debugging and of course with migration older installs.

#4947

Mov AX, 0xDEAD

> Zitat von ⇗ ruthan im Beitrag ¶ #4946

> Exist some better than MS 2D driver universal driver for Windows XP? Im still debugging without WinXP GPU and scrolling speed is very slow..

⇗ 2D over VESA - Anapa VBEMP
SciTech SNAP Graphics

#4948 | ruthan | Thanks, but 1st one if im not wrong is only for Win9x, or not?
#4949 | canonkong | VISTA also work very well, what needs to fix is the UHD630. ⇗
#4950 | infuscomus | ⇗ @ruthan VBEMP NT/XP/2K version here - ⇗ https://bearwindows.zcm.com.au/vbemp.htm

Part 1 ◄ Part 2 ◄ Part 3 ► Part 4 ► Part 5