Zitat von Fernando im Beitrag #31

---

Instead of trying to switch from IDE to AHCI mode from within a running OS I recommend to do a fresh install of Windows XP in AHCI mode by integrating the AMD AHCI driver, which I had attached to >this< post.

---

Ok I'm trying again. Did a fresh NLite package including your modified driver and used WintoFlash to create the boot USB Key.
Rebooted the comp, activated AHCI in Bios and booted on the usb key. XP is installing now (copying the files from USB key - it's slow btw)
Keeping my fingered crossed hoping everything will be good at first rebbot

EDIT by Fernando: Unneeded parts of the fully quoted post removed (to save space)

Hello everybody!

After struggling with this AHCI over several months now, i found a very simple solution for everybody who doesn't want to reinstall XP with F6 / slipstream:

Zitat von Sweep14 im Beitrag #30

---

What can I do as I would like to avoid re-installing XP ?

---

and don't want to waste around 5 hours of installing, waiting, configuring, testing, compiling and everything wasting-time by reinstalling:

Zitat von Fernando im Beitrag #31

---

Instead of trying to switch from IDE to AHCI mode from within a running OS I recommend to do a fresh install of Windows XP in AHCI mode by integrating the AMD AHCI driver, which I had attached to >this< post.

---

I have the same hardware ASUS AM1I-A / Athlon 5350 Kabini, no SSD though... WDC20EURS HDD. What you need is devcon from www.microsoft.com and the official AMD SATA AHCI package (either on the disk, or in support.asus.com).

1. Unpack both in one folder (for fast and convenient operation)
2. Open command prompt cmd
3. Write:

devcon install rcxpahci.inf "PCI\VEN_1022&DEV_7804&CC_0106"

do not forget the quotes, otherwise you'll get in trouble (cmd treats "&" as command separator!)
4. In setupapi.log in your WINDOWS folder you can find the following (at the very bottom):

[2017/01/27 21:52:05 3292.198]
#-199 Executing "C:\Install\t00lsoft\devcon\devcon\i386\devcon.exe" with command line: devcon.exe install rcxpahci.inf "PCI\VEN_1022&DEV_7804&CC_0106"
#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_1022&dev_7804&cc_0106
#I022 Found "PCI\VEN_1022&DEV_7804&CC_0106" in c:\install\t00lsoft\devcon\devcon\i386\rcxpahci.inf; Device: "XP-AHCI Controller [scsiport]"; Driver: "XP-AHCI Controller [scsiport]"; Provider: "Advanced Micro Devices, Inc."; Mfg: "Advanced Micro Devices, Inc."; Section name: "rcxpahci_Inst".
#I023 Actual install section: [rcxpahci_Inst]. Rank: 0x00000000. Effective driver date: 01/08/2014.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [rcxpahci_Inst] in "c:\install\t00lsoft\devcon\devcon\i386\rcxpahci.inf".
#I320 Class GUID of device remains: {4D36E97B-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ROOT\SCSIADAPTER\0004".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [rcxpahci_Inst.Interfaces] from "c:\install\t00lsoft\devcon\devcon\i386\rcxpahci.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\SCSIADAPTER\0004".
#I163 Device not started: Device has problem: 0x0a: CM_PROB_FAILED_START.
#I121 Device install of "ROOT\SCSIADAPTER\0004" finished successfully.

5. Reboot & change to AHCI.

Devcon will execute the contents of the rcxpahchi.inf and you'll get in your device manager with a "non-working" SCSI controller.


That's obvious, because you're still in IDE mode.

However, the driver is installed in HKLM\System\CurrentControlSet\Services, and according to all the spam in MSDN it is in the loading boot sequence of different drivers. So when you restart your HDD will be detected properly (no 7B stop) and you'll login in (long live) Windows XP. I even think that it even doesn't matter what you write in the <hwids> section, because anyway devcon enumerates it in ROOT\SCSI\000x, but I haven't done a complex investigation It does matter, because if the "plugged" device (via software by devcon) doesn't match some of the HWIDs in the inf file it will fail to install (Section #I022 Found "PCI\VEN_1022&DEV_7804&CC_0106" in c:\install will report No matching HWIDs). After restart you can open device manager and delete the extra "XP-AHCI Controller [scsiport]" with yellow mark, because your HDD is enumerated and everything's fine.


You can even swap anytime between IDE and AHCI without hassle, because it doesn't replace the IDE/ATAPI controllers class driver with it's own [unlike some intel drivers] which sometime create trouble.

Keep in mind: If you have something removable attached in the USB [like I have a cardreader] when you switch the operation mode [AHCI/IDE] you should rearrange HDD BBS priority (boot priorities), because your HDD might end in the bottom, resulting in tripple fail and popping in BIOS and you might think that everythings f***ed-up, but it's a matter of little *flaws*.

This procedure might be useful for other driver packages, unfortunately I do not have that much hardware to experiment and report results.
UPDATE: have done couple of installations this way with JMicron JMB363, ASMedia ASM1061 and Intel's iaAHCI.
Technically, it's crazy to do a preinstall with slipstreamed drivers (just to install the drivers), because whatever it is doing the NTSetup during the GUI install phase with the devices it is doing it after regular late installation of drivers (like plugged USBs and so). If you want proof, you can see your SETUPAPI.LOGs (because they're limited around 1MBs in XP) to see even what setupapi.dll has been doing when you installed the OS. Preinstallation with slipstreamed drivers it's like reinstalling windows with your intended-to-use USB flash drive plugged in to be detected during hardware installation phase of GUI Setup part... It even bothers me why manufacturers recommend this... If you obtain a latest package for ASMedia ASM1061 driver (like in ASRocK support center) you can even see that this company has prepared a ASM106xV1410WHQL\Driver\XpS2k3\x86\PREPARE\asahxp_PRE.inf file to install their drivers in IDE mode. It's with a [DefaultInstall] and [DefaultUninstall] sections (right-clickable), which add necessary data to the registry (HKLM,System\CurrentControlSet\Control\CriticalDeviceDatabase\ and HKLM,System\CurrentControlSet\Control\CriticalDeviceDatabase\) for which some people say (and do) a FULL 5 HOUR PREINSTALLATION... Well I'd rather go out drink a beer and enjoy life instead of clicking, typing and waiting for progress bars to fill up...


Enjoy, and do not preinstall -- XP is far stable on it's own! Take good care for it and it might outlive you.

P.S. I have some pictures for the procedure, but i'm lazy enough now to deal with them. If there is an interest, I'll struggle to upload them. Done.

<3 for all.