Fernando 1

What happens, when you try to install the complete Intel Matrix Storage Manager Package v8.9.0.1023?By the way: The Intel Matrix Storage Manager Console doesn't really make sense unless you have an Intel RAID system. OK, then it is verified, that the mainboard has an Intel ICH9R Southbridge chip.As a consequence you will be able to use the "regular" WHQL signed Intel textmode driver.

@ jdub: Irrespective of the ICH9 Controller details (with or without "R") the main question is, if you can turn on the "AHCI Mode" within the mainboard BIOS or not. If you can, the modified version of the Intel AHCI drivers should work fine. On the other hand you will not be able to get any Intel AHCI driver installed, if you don't have the BIOS option to run the Intel SATA Controller in "AHCI Mode". Nevertheless I would try to check the sort of your Intel Southbridge. Please open the Device Manager and give me the DeviceID (DEV_xxxx) of the Intel SATA AHCI Controller, which usually is within the "IDE ATA/ATAPI Controllers" subdirectory. It is part of the HardwareID's you will get by doing a right click onto it > "Properties" > "Details" > "Property" > "HardwareID's".

I am sorry, but the hoster MediaFire is temporarily down.Here is an alternative link to the requested driver: http://www.german-winlite.de/wbb/index.php...721ea11b301c0c7

Nobody needs to read any of these pages unless the start post of the thread, which contains all informations and will always be up-to-date. No, I recommend to take that driver, because it is the only one, which will support ICH9R and ICH9 chipsets without "R". I don't understand, what you mean with "R version". I recommend to integrate the "32bit Intel textmode driver v8.9.0.1023 mod by Fernando". When you get the textmode driver popup window, you should check all Intel SATA AHCI Controllers with "ICH9" within the names (ICH9R and ICH9).Good luck! Fernando

The .INF files are stored within the WINDOWS\INF directory, but if you are searching for a specific INF file of a driver you have installed, you will not find the original INF file name there.All Windows Operating Systems rename the INF files of the installed drivers to OEM0.INF, OEM1.INF, OEM2.INF etc.. Only the INF files of the Windows OS in-box drivers will keep their original names. Best wishes Fernando

@ BriantK: Welcome at MSFN Forums! Your problem can easily be solved. It was a good idea to post a screenshot of the Vista Device Manager, because it shows, that the laptop of your friend has an Intel ICH9M Southbridge and that the SATA drive is running in AHCI mode. So you should create a Windows XP CD with integrated Intel textmode driver according to the start post of this thread. When you come to the integration procedure, you need just to check the device named "ICH9M-E/M SATA AHCI Controller". The .SYS files are the real drivers, the .INF files are text files, which contain the instructions about how to get the driver installed and working, the .DLL files are just co-installer files. Don't worry about the fact, that nLite will just show the INF file while integrating the driver. It will copy all files of the driver folder onto the XP CD. You will find the needed 32bit driver within my guide (first post of this thread). The drivers I have uploaded are the newest and currently best Intel SATA drivers and will fully support the Compac laptop of your friend. The only reading material you will need is my guide within the first post of this thread. Don't try to do that. Since the laptop of your friend does support the advanced features of AHCI (NCQ and hot plugging) and the installation of Windows XP with integrated Intel AHCI driver will easily be done, why should he run XP without AHCI support?Good luck! Fernando

Yes, but this EXE file is not easy to extract and the needed textmode driver files are not easy to find within the extracted package.

@ Prot: Welcome at MSFN Forums! If your boot RAID device is connected with the Marvell Controller, you have tio integrate the Marvell RAID driver as TEXTMODE. You are right. Intel doesn't provide any Marvell 61xx RAID driver with the absolutely needed TXTSETUP.OEM file, but I found a suitable driver set for you. Download and unzip this package and integrate it as textmode driver (don't mix the 32bit and 64bit Drivers/Controllers, just integrate 1 of them depending on the OS you want to install). I am nearly sure, that your Marvell RAID and its partitions will be detected by the OS Setup. Good luck! Fernando

I am not sure about that, because the actual ATI AHCI/RAID drivers (download link) are dated 05/22/2009.

@ actor: Welcome at MSFN Forums and thanks for your feedback. You are right regarding the SB driver versions. 9-4 means Catalyst 9.4 and 9-8 would be part of the Catalyst 9.8 series. It would be interesting to know, if the newest ATI SB7xx AHCI/RAID drivers named WHQL_SB7xx_RAID_XP_WS03_3.1.1540.127.zip a ) really are as new as the Catalyst display driver v9.8 and b ) will support your special SB7xx chipset. ATI's SB7xx AHCI/RAID drivers v9-4 natively do support much more SATA Controllers than the later ones. EDIT: I'm sorry, I was wong regarding the name of the ATI AHCI/RAID driver.

@ zilan: Welcome at MSFN Forums! No, the v6.99 drivers will not work with all actual AHCI supporting nForce chipsets (MCP65 and up). I do not recommend to do that, because the previously integrated textmode drivers, which have to be present within the i386 directory of the XP CD, might be overwritten this way.If you want to create a Windows XP CD, which can be used with nearly all available AHCI/RAID systems, you should not do it by using a tool like nLite. In this case I recommend to take the Mass Storage package and use the DriverPacks integration method by using DP Base. For further details you may look here. This will not work as you have thought.It is not a good idea to integrate different textmode driver versions of the same vendor by using a tool like nLite. Since the Intel textmode drivers v5.5.1035, v7.8.0.1012 and v8.9.0.1023 all do contain the driver named IASTOR.SYS, only the last integrated one will be usable during XP Setup. All the other ones will be overwritten.

Windows 2000 does not fully support AHCI. Not really (see above).

Both drivers are old and replaced by better ones.If you will ever do a fresh XP installation, you should slipstream the actual Intel ICH10R SATA AHCI driver (as textmode driver) and the Intel Chipset =INF Drivers (as PnP driver). You will find the download links of both drivers (already prepared for the integration) within my guide. You can integrate both drivers, but I don't think, that it is really needed. Why do you think so? According to your posted screenshot you are currently running the SATA hdd in AHCI mode. The yellow marks just show, that there are still some device drivers needed to get all your hardware running.

Please open the "SCSI and RAID Conrtrollers" section too. Which devices do you see there?

... our you have done something wrong.Do have access to any Windows OS on your computer? If yes, open the Device Manager and post the names of the Controllers you see within the "IDE ATA/ATAPI Controllers" and - if present - the "Storage Controllers" sections.

@ p45ts: Welcome at MSFN Forums! Here are my recommendations for you: 1. When you are precessing your XP CD source by using nLite, you should leave the "Computer type" settings as they are per default ("automatic"). 2. If you have an Intel ICH10 (without "R") chipset mainboard, you may integrate the 32bit Intel textmode driver, which has been customized by me (Download link). 3. To avoid any problems during the XP installation, you should remove 2 GB of RAM (just for the installing procedure). Good luck! Fernando

That probably will not work. Why is it painful to insert for some seconds a W2k CD while installing Windows XP?

Welcome at MSFN Forums! You can prepare the upgrade version of XP by using nLite with no problems, but you will be asked to insert the CD with the platform OS (W2k for example) while installing Windows XP. Nevertheless it will be a clean install, because no file of the inserted platform OS CD will be installed. Have fun! Fernando

Any change of the hardware system is a good opportunity to do a fresh and clean OS install. This way you will get the best possible performance and 100% appropriate drivers. The time you are losing by reinstalling your prefered software and tools is much less than the time you will lose within the next years by sticking with an old and fragmented registry. Furthermore you will be able to select more actual and maybe better driver and software versions than those you have used for the last 8 years.

@ Breezy: Questions: 1. Are you sure, that the SATA hdd of your Fujitsu-Siemens LIFEBOOK T4220 is running in AHCI Mode? 2. If yes, does it have the BIOS option to disable the AHCI Mode? 3. Which of the listed Intel SATA Controller(s) have you enabled while integrating the Intel textmode driver? 4. Why do you want to install XP ontop of an older and probably not AHCI supporting XP installation? 5. Which error message did you see, when you get the reboot loop? (Tip: You will get the entire error message, if you hit F8 while rebooting and choose the advanced option "Don't reboot at system failure".)

And here is the direct link to the Windows XP (32bit) MegaRAID driver v6.51.32:http://www.lsi.com/DistributionSystem/Asse...gned_driver.zip

Take this driver I have prepared for ATI SB6xx and SB7xx chipsets:32bit_ATI_AHCI_RAID_driver_for_XP_mod_by_Fernando.zip Integrate it as textmode driver by using nLite. That will work for you. Good luck! Fernando

@ Pazzi: Welcome at MSFN Forums! Yes, but nevertheless you did something wrong while integrating the ATI SB600 textmode driver.Did you get the textmode driver popup window? If yes, which Controller did you enable? The message "Setup cannot load AHCIx86.inf" is quite normal, if you have chosen the "Unattended Install" option and then trying to load th textmode driver via F6. This doesn't work. If Windows Setup detects a WINNT.SIF file within the i386 directory, it expects, that all needed textmode drivers are integrated intio the CD. It loads the driver from the floppy disk after using the F6 option, but then it forgets the path.

im not trying to integrate drivers by using nlite and i post my message another topic and the moderators moved it here.Ok, it was not my intention to criticise you.By the way: Why did you insist on integrating drivers into the driver.cab file, which belongs to the OS itself? Which disadvantage do you expect, if you just integrate them by using a tool like nLite?

@ kurmud and Seanmick: You are welcome! Fine, that you succeeded at least and that I was able to help you. @ all: This thread has now more than 1 million views - I am overwhelmed! When I started it in July 2005, I did not expect, that it will be that popular. Regards Fernando