So I finally got to check the ATA IDE devices running on my computer right now. They are listing as 8C80 and 8C88.

None of the .inf files have those...so Im wondering...how is it that my SATA drive is even communicating and running/booting at all?

Looking at the fernandos .inf file, I was expecting to see a 8C82 or 8C83 device...im not seeing at all...

but as for CAD and the stuff i need to run...its running circles around my old system. :-) :-) and regardless, this forum rocks!!!

Thank you for that .inf

The other inf files I looked at are the download links on page 1, post one of this thread:

>Universal 32bit Intel MSM textmode driver v8.9.8.1005 mod by Fernando<

>Universal 32bit Intel RST textmode driver v11.2.0.1006 mod by Fernando (corrected at 08/26/2014)< (This is the one I thought was for my setup)

Right now, I think my system is performing really good...the thing is, someday however Im going to be forced to "upgrade" to Windows 7 for application compatibility issues beyond my control...in which case I will prob doa dual boot, which is why I think these other drivers are needed.

edit: Oh yes, I understand the two different inf are for the different controllers, much appreciation. How are things over in Germany?

I was successful in using the device manager and Updating Device using that .inf.

After updating and rebooting, both devices now show up as:LynxPoint-LP SATA Controller 1 (Non-AHCI/Non-RAID) & LynxPoint-LP SATA Controller 2 (Non-AHCI/Non-RAID).

When I ried setting BIOS to AHCI is BSOD'd on me, so I reset to IDE mode.

Question is: How does one get them to be AHCI so one can Dual Boot when installing Windows 7? - Or is that only possible via a fresh XP install and slipstreaming?

What im actually considering doing is installing Win 7 64 on a completely separate SATA or SS drive and just booting to the device I want upon startup...I dont really need to have both OS's on one HD.

Im probably going to have to go that route anyway - Ive got 16GB of ram, and XP 32 obviously can only access under 4 of it...add to that my 2GB graphics card and there is insult to injury.

XP is so nice and fast...not looking forward to its eventual death at all. Your help has given me a while longer however!!! :-) Thank you!

OK, That is kinda the directions I was thinking...especially the "Might boot" (hehe). That being said...I happen to have a brand new SATA drive which I really would like to use rather than my 3-1/2 yr old 300GB SATA drive.

At this point, the .inf's i updated have put my devices into the LynxPoint position...with no true differences (that I can ascertain) from the "Standard Dual" device drivers.

it wont be tomorrow, but...I will attempt this approach.

Now...again, off topic, 4GB RAM for 32 Bit - makes sense...18EB (18 Billion GB) Ram access addresses for 64 Bit buses...total scam. why are we not given 36, 38, 40...Buses...?? Kind of like how Pentiums were given 20 and 24B buses prior to the true 32B bus?

I mean...the math would say...if we really want true 64B, then hard drives must be able to handle pagefiles BILLIONS of times bigger than 32B buses...as well as the processor needing to be able to process that same info...

16B = 64K of memory...20B = 1MB, 24B = 16MB, 30B = 1.1GB 32B = 4GB....64B = 18B GB (like 18Billion 1GB cards....its like a city block of 1GB ram modules)

Why have they done this to us? Why not a simple memory bus increase of 100X (34B) or 10,000 (36B) ? Its at least physically manageable...64B...its not possible without true quantum/atomic processing...not enough physical space nor processes per second to even search more than 1% of the available bandwidth...

and now I understand why my 32B applications of same exact version run multiples faster than the 64B versions...we were capped at 4G memory...we just needed a multiple of 10... (of 33B buses) to take us to 40GB, or 34B to 400G...but instead they took us 18 Billion times beyond...without even the means to "read the ma" literally.

sorry...

and thank you for your help...i was once a owner of a decent sized ISP in Portland Or...sold it...kind of floated with the wind...and now am back "into it" so o speak...

OK, makes perfect sense.

On the other issue, of rying to force the AHCA driver...if I set a restore point before I do that, even if it BSOD's wont I be able to boot back to last known good setup? Or can it even screw that up?

May I ask you whats your take on the real issue at hand here: is your goal to keep XP going as long as possible, or more of just a hobbie?

I went to do a paypal donation, but its in Euros and Im in US...will it work, or will the bank get more $$$ in conversion fees than its worth?

Haven't been here for a while, but I would like to share a solution that fixed my problem. Integrating the proper SATA drivers with nLite brought no luck (BSOD with the 07 error). I think that something was wrong with the XP image I used :( I googled up a different solution - enabling AHCI after the installation of Windows, described on http://www.blah-blah.ch/it/how-to-s/enable-ahci/. The author did this for an ICH-10 chipset, but it worked for mine (Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller).

1. FIRST OF ALL, check under "Start => Settings => Control Panel => System => System Restore", that the option Turn off system Restore on all drives is not active, and that the drive where your Windows resides is being monitored. This will allow to undo the changes by pressing F8 when Windows reboots, if anything goes wrong.
2. If you are able to start up Windows and don't have AHCI enabled you probably have in your BIOS the IDE-mode enabled, right? If not, enable it and start up Windows as usual.
3. Now start by downloading the drivers from the Intel homepage - they're called Intel Matrix Storage Manager and can be found here.
4. Now that you have the drivers, e.g. in "C:\temp", create in there a new directory, e.g. "C:\temp\unpacked".
5. Open up a MSDOS-shell and unpack the drivers into the new directory by using the "-A -P" flags, so in my case it would be...
iata82_enu.exe -A -PC:\temp\unpacked
6. Where you unpacked the files you should now see that there are files called "IaStor.sys", "iastor.inf" and "iaAHCI.inf".
7. Now, this probably is not needed and it won't do anything at all, but as I did it (while I was still experimenting) and everything is now working, you should do it as well - you never know: rightclick on "iaAHCI.inf" and choose "Install". Do the same with the "iastor.inf"-file. Nothing should happen - the system should act as if nothing has happened.
8. Now the real fun starts: go to "Start => Settings => Control Panel => System => Hardware => Device Manager", search in the list for "IDE ATA/ATAPI controllers" and in there you should see a couple of entries including your IDE controllers - something like "Intel ICH10 family....serial ATA controller". It might be that you see two such entries.
9. Select one of the "Intel ICH10 family....serial ATA controller"-entries, click with the right-mouse button and select "Update driver".
10. Answer "No, not this time", then "Install from a list or specific location (Advanced)", then "Don't search. I will choose the driver to install.", then "Have a disk".
11. A new window should appear asking you where the drivers are. Click on "Browse" and select the directory where the "IaStor.sys" & Co. were unpacked.
12. You should now see a list (or at least 1 entry) of different AHCI-ICH-controllers including the one you have - if not, deselect the checkbox which makes the system list only the compatible drivers.
13. Search for your ICH-controller. Have a look at the manual of your motherboard if you're not sure which one it is.
14. Once you found & highlighted your AHCI-controller ("Intel(R) ICH10R SATA AHCI Controller" in my case), click on "Next". At this stage Windows a message box will pop up showing a warning about not being able to verify the compatibility of those drivers. Just smile and continue the installation.
15. Now the system will install the drivers and it might take a looong time. Have a beer in the meanwhile as in my case I had to wait for about 20 minutes.
16. Once the driver has been installed, go back the the device manager, select (if you have it) the second "Intel ICH10 family....serial ATA controller"-entry and do again exactly the same. In my case the installation of the driver finished this time immediately.
17. After the drivers have been installed, reboot the machine, go into your BIOS, change the settings for your HDD-controller from "IDE" to "AHCI" and start up Windows again.
18. If your Windows XP manages to boot then it means you did everything right - if the installation of the AHCI-drivers wouldn't have been successful your PC would now hang or reboot continously. If this happens go back to your BIOS, change AHCI back to IDE and boot Windows. If Windows still doesn't want to wake up, keep the key "F8" pressed at the very beginning when the OS boots to bring up a menu and choose the "Last good known configuration" to undo the changes described above.
19. Not finished yet: once Windows is up you should see in the taskbar that something is being installed - you might get the bubbles saying that some new HDDs have been found. Additionally if you look in the Device Manager at the "IDE ATA/ATAPI controllers" you should see that all you have listed in there is just a "PCI device". Again, be patient and have one more beer.
20. Again after ~10 to ~20 minutes Windows should tell you that it found new hardware, the AHCI-controller. Still wait until Windows asks you if you want to restart the PC.
21. Accept to restart it and after the reboot everthing should be ready. Under "IDE ATA/ATAPI controllers" you should now see your AHCI controller ready.

I have problem instaling windows xp to my new PC. When windows setup loading finish, emerges lberfdc. sys is corrupted. How do to fix it?

EDIT by Fernando: Post title customized