Dave-H

Thank you! What do you think @jaclaz?

Oops, hadn't seen your previous post @jaclaz! The forum page was sitting there for ages and for some reason it didn't flag that there had been another post. OK, I will do it again with the driver from the IN1VDO11WW1 package, or are you saying I should be using the IN1AHC20WW1 package? Sorry to be so confused with all these different packages which all look like different versions of the same thing to me!

OK, I force installed the Ahcix86,sys RAID driver onto XP using driver inject on 8.1. All went successfully, but still BSOD 7B on XP startup in AHCI mode. Still starts OK in IDE mode thank goodness! The controller is still showing "Standard Dual Channel PCI IDE Controller". ahcix86.sys is not present in the system32\drivers folder. amd_sata.sys is in the folder, but doesn't seem to be being used. It identifies as "AHCI 1.2 Device Driver".

OK, I've now removed all the AMD software, and the controller is now back to being the Microsoft "Standard Dual Channel PCI IDE Controller". I've also lost the driver for the HD audio bus and the USB 3 controller, but I know I can now put them back from the AMD package, and they work! I'm intending to now use the "AMD_WinXP_KV_KB_BON_Jan13_2014.exe" package as it is I suspect the last XP version if it's from 2014, newer than the Lenovo package.

Sorry for muddying the waters with the graphics problem, you are absolutely right that I should be concentrating on just one issue at a time! I've been working on drivers for the graphics and touchpad at the same time and getting in a confused mess. The ACHI issue really does have the highest priority at the moment as at present I am having to switch the controller mode between operating systems, with is annoying. I have been confusing myself by installing different drivers in the hope of hitting on one which works, which is obviously not a very scientific way of going about it! I did install from IN1VDO11WW1, but then tried other AMD Catalyst packages too, mainly to try and find a graphics driver which worked, but they installed other drivers too. This included most recently the "AMD_WinXP_KV_KB_BON_Jan13_2014.exe" software suite package that @RainyShadowlinked to in a previous post (as an aside it is really beyond annoying that this forum doesn't number its posts!) This being apparently from 2013 seemed to be newer than the IN1VDO11WW1 (signed 2011) package. I will now uninstall everything and start again! I should be able to roll back to the generic Microsoft IDE driver (I hope!) Sorry for the mess, I should know better after all the times I've solved problems with people here in the past, including you @jaclaz Cheers, Dave.

Well I thought I had! The driver in Device Manager changed from the generic one to an AMD one, even though it;s running in IDE mode at the moment. I was assuming that the AMD driver is AHCI capable as well, it's just not using that mode at the moment, but would if it was seeing the right device ID.

Thanks again! I uninstalled the VBEMP driver, sorry I really should have found that page myself with the details of how to do it! Annoyingly it's trying to find a graphics driver every time I boot up now, even though I've ticked the "do not ask again" box umpteen times! So, if the device SATA controller ID does change according to the BIOS setting, why when I put the BIOS to AHCI just it just BSOD when I run XP? Shouldn't it detect the change and load the correct driver, assuming it's on the system of course?

Unfortunately all the INF files in these drivers don't include my hardware ID, which is PCI\VEN_1022&DEV_7800. They contain 7801, 7802, 7803, 7804, but none of them contain 7800! I've done some more research, and that 7800 ID seems to be always listed as "AMD SATA Controller (IDE Mode)". The other IDs are listed as "AMD SATA Controller (AHCI Mode)". Now I know the hardware supports AHCI because it does on Windows 8.1. However, on XP it seems to be identifying as an IDE only device. Is it possible for its device ID to change depending on BIOS settings or something like that?!

Thanks @jaclaz! I tried what you said, but used the file linked to by @RainyShadowearlier as I think that's the one that also had drivers for USB 3.0 so may be more up to date. In that file, the path is Packages\Drivers\SBDrv\hseries\AHCI_svr\XP\ It seems to contain the same set of files. Trying to update the controller from there just produced "couldn't find a better driver than the one already installed". Looking in the RAID folder instead, the ahcix86.inf file does not contain a reference to my hardware ID, which is PCI\VEN_1022&DEV_7800. Should I try just adding it?

I tried running the MSI file in the ACHI driver package, and it just said it wasn't designed for my OS. I suppose I could hack the MSI file with Orca, but I very much doubt if it would do any good. I did find a package for AMD-based Lenovo machines called "IN1VDO11WW1.exe". This supposedly contains XP drivers for all the AMD devices. It won't install the graphics driver sadly, but it did install several others. My SATA controller driver is now "AMD SATA Controller (IDE Mode)". This sort of implies that there is an ACHI mode as well, but how do you switch it? Just selecting AHCI on the BIOS certainly doesn't work, it just BSODs again. I then tried the driver you found, and that updated some more devices, including USB 3.0, which is good. It still didn't install a graphics driver though. The devices I am still now missing drivers for are the graphics, Ethernet controller, and one "Unknown device". How do you uninstall the VBEMP driver? I can't see anything on the documentation pages about how to get rid of it! If I remove the device, it just puts the non-functioning driver back again, and there's the added annoyance that I have to OK its use on every boot! There's certainly no option in Add/Remove programs to uninstall it, and it doesn't appear in the HP System Diagnostics analysis either so I can't remove it there. I got two more SNP files from SDIO, this time when running XP. I don't know why it generated two of them, I suspect they are identical but I've attached them both just in case! Cheers, Dave. 2020_03_24__12_42_41__NETBOOK_state.snp 2020_03_24__12_42_44__NETBOOK_state.snp

Thanks again. That driver doesn't look very promising, but I will give it a try! It's a Catalyst driver, not a Radeon driver, but you never know! Backup now 75% done...........

The backup is about a third of the way through! I will try running SDIO on XP once it's finished, and attach the new analysis file.

Glad things are not too awful where you are @jaclaz. I'm now using Windows 8.1 to do an ISO backup of all three partitions on the machine, which will take a long time! I already had tried installing the AHCI driver using the Device Manager, but it just said that the INF file had no information about my hardware. I will try again with the MSI file. I also tried the VBEMP graphics driver, and it went through the motions of installing, and then said the device couldn't start (code 10). I used the 20 version as the documentation said that was best for flat screen displays. @RainyShadow did you say there was another possible graphics driver somewhere? Once the backup is done, I will have another go. I'm just so pleased to have finally got into Windows XP at all! Cheers, Dave.

Thank you, that worked! I also set the IntelIDE service to disabled for good measure, and removed everything from the registry "run" key that I was worried about. XP has now started, in IDE mode. It's complaining that it needs to be reactivated, but that's a minor issue! Now to try to configure it to run in AHCI mode. I guess just installing that AHCI driver that @RainyShadowattached earlier should do the trick? P.S. @jaclaz I hope things are OK for you and yours at the moment.

Oh dear, that doesn't sound good! I'm wondering if perhaps something is trying to run on boot with is crashing the system, I would imagine that the Intel Application Accelerator is still trying to run for instance, which is now incompatible. It doesn't BSOD instantly like it did with the 7B error, it does try to load, although the progress bar is stopping and starting, and eventually it produces the 7E BSOD. As I can access the XP registry in 8.1 using Registry Workshop, do you think it's worth trying to remove all the startup items there? @jaclaz or anyone else any ideas?

OK, I tried that. Windows 8.1 now blue screens on the OS selection menu, but if I select XP on the menu when in AHCI mode and then go into the BIOS after it reboots to XP and select IDE mode, it does work. I'm still getting a BSOD on Windows XP though, this time 0x7E instead of 0x7B. Incidentally, if I had run DriverInjection as an Administrator in the first place, do you think I would have had to still change the permissions on the system hive file? Do you think i should now put its permissions back to as they were before? I can obviously easily remove myself as a user on the file permissions, but how do I change the ownership back to what it was before? Before I changed it, it said "unable to display owner", and I'm not sure you can clear ownership once you've set it.

Oops, yes of course I meant AHCI! Just off out now, but I'll let you know how it goes later. Thanks, Dave.

No, it's still on ACPI. I can't run 8.1 with it in IDE mode.

Well the process apparently completed successfully, but I'm still getting an immediate 7B stop error when I try to run XP.

Ah-ha, thank you, I should have thought of that!

Hi again @RainyShadow! I'm now trying to use DriverInjection to put the AMD AHCI driver onto the XP system. Once I got my head around it, all went well until I came to load the system registry hive on the XP system. First I couldn't access it, so I took ownership of the "system" file and gave myself full control. Now it loads OK, but then just puts up an error message "Error 1x2: Error loading structure." Any ideas? Thanks, Dave.

Sorry, still configuring other bits of Windows 8.1, then I'm going to bed! I'm not sure about using floppy disks, there is no facility for that on this machine of course! Where do I get the SDIO video driver?

Thanks! Sorry, what do you mean by "F6 floppy image and the extracted files from inside." I already have a video driver from bearwindows which is apparently a generic driver which should work. Is the SDIO one different? Cheers, Dave.

Thanks again! The file from Snappy Driver Installer is attached. The X102BA and X102B are the same thing. There is a lot of confusion around that! 2020_03_21__22_05_49__X102BNETBOOK_state.snp

Thanks @RainyShadow! I don't fancy your first method too much as it's a small netbook, not a desktop, so physically moving things around isn't straightforward! I'll certainly try it if all else fails. I can boot into Windows 8.1 in AHCI mode with no problem, and I used to do that in XP too, using the Intel Application Accelerator. Doing the research, it looks as if XP supports AHCI with no problem, as long as it has the right driver installed. Unfortunately all the information I've found about configuring that driver depend on actually being able to boot into XP in the first place, which at the moment I can't do! I can access all the XP files in 8.1 of course, and I should be able to access the XP registry in 8.1, using Registry Workshop. If I did that and changed the entries in the XP registry to match your file, is it possible that it would work? I'm not at all sure whether XP has the right drivers installed, the Application Accelerator may have been overriding things. Is there any way of checking that in the XP file system? Thanks, Dave.