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 ;

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.

---

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.

---

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.

---

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.

---

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)

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.

---

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.

---

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.

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?

---

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?

---

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.

---

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

- 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...>

  [ 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

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)

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.

---

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.

---

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!

---

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
 		  	  

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.

---

[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

#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 ⇗ 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).

---

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.

---

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?

---

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.

---

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.

---

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.

---