Fernando 1

@ htmjakob: eROM's troubles have nothing to do with your probem, which you have posted within >this< thread. The "import" button you get after the start of nLite is just for loading a previous nLite setting, which is absolutely not recommended, if you just want to integrate a Service Pack and a suitable AHCI/RAID driver into a Windows XP (32/64bit) CD.

If you want help, you should give us some informations about 1. your system (vendor and name of the mainboard or pc), 2. the SATA driver version you have integrated and 3. the SATA Controller you have selected during the integration process.

Hello eROM, welcome at MSFN Forum! 1. An original XP CD does neither contain the Marvell SATA3 AHCI driver named mv91xx.sys nor any INF or SIF file entries regarding this driver. You obviously have used an already processed XP CD as source or you have loaded a Last_session.ini of a previous processing procedure, when you started your work with nLite. It is very important, that you start with a clean (=untouched) Windows XP-CD as source and do not load any Last_session.ini. 2. If you should have integrated several different SATA drivers, you should start a new nLite session from scratch and integrate just the Intel AHCI driver (providing, that your system drive is connected to an Intel SATA port, which has been set to AHCI mode). 3. If your USB stick is not able to read the files, I recommend to change the USB stick or/and the ISO-to-USB transfer tool. Regards Fernando

The driver integration definitively should work by using the last version of nLite.Please post your problem into the nLite Forum by starting a new thread with a title like "nLite doesn't work for me" or similar. This way you may get help by some experts, who had helped Nuhi developing the tool nLite. Good luck! Fernando

Join >this< site and go into the "nLite" chapter. There you can download the actual nLite version 1.4.9.1 either as installer or as self-extracting archive. Both downloads are running fine.Regards Fernando

@ gipsyshadow: If you want to get all your currently in-use XP drivers for a later integration into a fresh XP CD, I recommend to download and use the tool Driver Magician (>Link<). If you want to get the newest drivers, you may try the tool DriverMax (>Link<). Regards Fernando

This will not work, because Win7 Setup doesn't accept any unsigned drivers.But this is not a big problem. Let Win7 Setup install the generic AHCI driver MSAHCI.SYS and update the AHCI driver later manually. nLite is still availabe and will work, but you can install XP onto an AHCI or RAID system by using the F6 method too.Regards Fernando

You will not get a list with the Intel SATA Controllers like with Windows XP, because Win7 doesn't read the TXTSETUP.OEM file. It will find the correct HardwareID's itself.Important: You have to force the installation of the "modded" driver by hitting the "Have Disk..." button. Otherwise the driver update fails with the message, that the "best" driver has been already installed.

The only person, who would be able to do it is Nuhi, the owner of that site, but he obviously has stopped any support regarding the web site nLiteos.com and the tool nLite.So I am sorry, but I cannot solve your problem. According to my knowledge it is absolutely impossible, that the Intel RSTe drivers do support TRIM, because TRIM is an ATA not an SCSI device command.Nevertheless it may be possible, that the RSTe drivers will automaticly clean the cells of an SSD, but they have to do it with the UNMAP command, which is the equivalent of the TRIM command for SCSI connected SSD. What I do not know is, if Win7 does already support the UNMAP command. AFAIK it will be implemented into the upcoming Windows 8. Regards Fernando

@ submix8c: Obviously yes! When I wrote my last post, it was not my intention to foil the already given support, but after having done a look into this thread I got the impression, that gipsyshadow is still far away from what he has intended to do: an unattended fresh install of XP with integrated SP3 and all the drivers for his laptop. Just to avoid any double posts, misunderstandings and unsettledness of the thread starter, I have deleted my suggestions from my last post. I am sorry to have bothered anybody. Regards Fernando

It is not always a good idea for an nLite newbee to start with the creation of an All-In-One XP-CD (as unattended install with integrated SP3, Hotfixes and drivers). The more you let nLite do the more you risk, that the later XP installation may fail.Furthermore I want to mention, that the Intel chipset "drivers" (better name: Intel chipset device software) are not absolutely needed for a proper XP installation. None of the Intel chipset "driverpacks" do contain any real driver (that are files with the extension .SYS), but just a big variety of information files with the extension .INF. Your special Intel chipset system will only be able to use a very few of them, but nLite will integrate them all. Good luck! Fernando

Without any details about your laptop (name and manufacturer) I am not able to answer your question. If you are running any Windows OS with that laptop, you can verify it by opening the "IDE ATA/ATAPI Controllers" and - if applicable - the "Storage Controller" resp."SCSI and RAID Controllers" section of the Device Manager. There you should see the SATA Controller(s) of your system. Do a right click onto the Controller > "Properties" > "Details" > "Property" > "HardwareID's". Give me the DeviceID (DEV_xxxx) and I will tell you, which special SATA Controller your laptop has. I suspect, that either your XP CD or your CD-ROM device is not ok.

@ DavidT: Welcome at MSFN Forum! Why not? The graphics adapter has nothing to do with the SATA AHCI or RAID Controllers.Regards Fernando

If you want help, you should writea ) what you did with nLite (which tasks, which drivers did you integrate and which Controllers did you enable) and b ) at which point of the nLite processing or the XP installation did you get an error and which message did you get.

Usually I take the tool 7-Zip, but some EXE-driverpacks (from Intel, AMD etc.) cannot be extracted this way.If 7-Zip doesn't work, I execute the EXE file and let the installer extract the package itself. Before I accept or start the installation procedure, I usually I find the extracted package either within a folder the installer has proposed or within my Temp folder.(User\Name\AppData\Local\Temp). Regards Fernando

Since I always extract and have a deeper look into all new AHCI and RAID driverpacks, I was astonished to find a folder named RST within Intel's actual RSTe drivers and software set. Surprisingly there was just a 32bit driver within the RST folder.After having read, that the RSTe drivers do not support Windows XP (32bit), I concluded, that the separately stored 32bit RST driver v10.5.2.1010 were designed for being used with Windows XP. By the way: Users with an X79 chipset mainboard, who want or have to install Windows XP, do not absolutely need to use the RST driver v10.5.2.1010. All Intel RST drivers except the v11.5 series (that are RSTe drivers) inclusively the latest v11.1.0.1006 will work, but the needed HardwareID's of the X79 SATA Controllers have to be added to the text of the iaAHCI.inf and TXTSETUP.OEM files. >Here< you can find some driverpacks, where I have already customized the INF and OEM files to make them compatible with nearly all Intel chipsets and Southbridges. If you want to try or just do a deeper look into the "modded" 32bit Intel RST driver v11.1.0.1006 dated 02/01/2012, you can download it from >here<. Have fun! Regards Fernando

If you had extracted the package correctly, you should see a folder named "RST". Open the folder "RST" and then the subfolder named "drivers". The RST driver v10.5.2.1010 is within the subfolder "x32". All Intel RSTe driverpacks are designed for Servers - as the X79 chipset mainboards.

You misunderstood the statement of Intel regarding the support of the Windows Operating Systems. As you have verified yourself, users with an X79 chipset mainboard are able to get Windows XP (32bit) installed, but they cannot use the "normal" Intel RSTe AHCI/RAID drivers for X79 chipsets, which do work simultaneously with 2 drivers named iaStorA.sys and iaStorF.sys. So they have to use a driver of the RST line instead, which contains just 1 driver named iaStor.sys. The AHCI and RAID drivers of the "Intel® Rapid Storage Technology Enterprise Edition" (named RSTe), which have been developed especially for X79 chipsets, do not support Windows XP (32bit). That is why Intel added the 32bit RST driver v10.5.2.1010 to their official RSTe packages just to make it possible to get XP running with X79 chipsets too. Regards Fernando

Hello Bob, welcome at MSFN Forum and thanks for your feedback! It's fine, that you succeeded with the XP installation and that you are satisfied with the Intel AHCI driver I have linked within my guide. This RST driver v10.5.2.1010 dated 10/27/2011 has not been modified at all. It is the actual Intel AHCI driver, which has been designed by Intel for X79 chipsets systems running Windows XP (32bit).This driver is part of Intel's newest official RSTe drivers and software pack 3.1.0.1085. After having extracted the set you will find the RST driver v10.5.2.1010 within the RST\drivers\x32 subfolder.. Regards Fernando

Why should I mention this special Intel SATA Controller? There are a lot of different Intel SATA AHCI and RAID Controllers, which you will not find within my guide. The reason is quite simple: Within the start post I have linked a big variety of different Intel AHCI/RAID driverpacks. The TXTSETUP.OEM files of all these driverpacks contain different Controllers and even different names for the exactly same Controller type. So any detailed information about the exact list of the supported Controllers will be more confusing than enlightening. The screenshot within the "Processing with nLite" section of my guide was taken while integrating the old Intel MSM textmode driver v8.9.0.1023. Just to clarify, that the picture is an example and not exactly what the user will see, I wrote this sentence above that screenshot: Since I started this thread in November 2007 all driverpacks, which I have linked within the start post, are packed with one of the best and most common archive tools named WinRAR and can easily be unzipped by other popular Zip tools. The archiving procedure lowers the package size and the download time.Although I have done that since 2007, none of the meanwhile 1.1 million visitors of this thread ever have criticized that. Just to avoid.that the user tries to integrate the RAR package, I have written this sentence at the bottom of the "Preparations" chapter: I really hope, that you succeeded with the driver integration nevertheless. Regards Fernando

In this case you do not need to integrate any driver. You will be able to get Windows XP properly installed by booting off the original XP-CD with integrated SP2 or - even better - SP3. No, the SATA Controllers will use the XP in-box IDE driver named PCIIDE.SYS.The Intel chipset device software (= INF Update Utility) doesn't contain any any real driver (= .SYS file) at all, but just information files (with the extension .INF). nLite will copy and integrate all INF files, which are within the folder named "All", but the XP hardware detection will only install the suitable and needed ones.Since Windows XP and XP Pro are using exactly the same drivers, you will save a lot of time, if you download a tool like DriverMax and let it collect all in-use drivers of your currently running Windows XP. After having done a fresh install of Windows XP Pro, you can easily reinstall all formerly used drivers.by offering the collected driver package.

All device drivers packages contain one or more INF files with the informations about how the associated real driver (=SYS file) has to be installed, but the INF files will not be read by the XP Setup during the first (=TEXTMODE) part of the OS installation. The XP Setup uses them during the hardware detection and this takes place within the second (=GUIMODE) part of the installation. Only the textmode driver packages additionally contain a file named TXTSETUP.OEM, which contains the needed informations to let the XP Setup detect the HDD/SSD already during the first (=GUIMODE) part of the installation procedure, that means before Setups starts the first reboot.. Although nLite doesn't search for the TXTSETUP.OEM file, it will detect and read it during the driver integration procedure. As soon as nLite has detected a file named TXTSETUP.OEM, it will show it as textmode driver. If the TXTSETUP.OEM file may support more than 1 mass storage Controller, nLite will present a popup window with all possible Controllers, and the user has to decide, which one he wants to be integrated. This will never happen with an INF file.

You will be able to get Windows XP or XP Pro installed without having integrated any device driver. Only exception: Your system HDD/SSD is running in AHCI or RAID mode. In the latter case you need to load (F6) or integrate the appropriate AHCI or RAID textmode driver, which contains a special textmode driver file named TXTSETUP.OEM.If the Setup of the original XP Pro CD with integrated SP3 should not detect your hdd, you have to integrate just the missing SATA AHCI or RAID textmode driver. Look into the "IDE ATA/ATAPI Controllers" or - if applicable - the "SCSI and RAID Controllers" of your XP Device Manager for the listed AHCI or RAID Controller and get the actual driver for it from the manufacturer of your mainboard or - even better - from the vendor of the SATA Controller Chip.. So you have just to integrate this single AHCI or RAID driver as TEXTMODE and to burn the created new ISO file as bootable CD. You cannot do that manually. If you want to extract all in-use drivers, you should let a tool like DriverGrabber do that.For a proper fresh OS installation you don't need all the extra drivers except the correct SATA driver for the AHCI or RAID Controller of your system, but you should grab the SATA driver from the vendor of the chipset and should not collect the needed files (INF, CAT, SYS and OEM) from within your currently running XP partition. Regards Fernando

@ all visitors of this thread: Today I have slightly updated the start post of this thread. Here is the Changelog: updated: modded 32/64bit "Actual nForce Driverpacks for XP" (now v9.0) updated: modded 32/64bit "Non-AHCI nForce Performance Packs for XP" (now v9.0) updated: modded 32/64bit "Special MCP65-67 nForce Driverpacks for XP" (actual: v9.0) updated: modded 32/64bit "nForce LEGACY Remix Packs" (now v9.0) changed: all download links (now all files are hosted on a quick ftp server) Any feedback is recommended. Regards Fernando

Which ones?You should only integrate the 32bit Intel RST driver v11.0.0.1032 WHQL and choose the listed " "Intel® ICH7M/MDH SATA AHCI Controller" while doing the integration with nLite. And what happened? Did the XP installation work?