Fernando 1

There are different reasons why the ATI textmode drivers don't work for everyone.These are the main problems: missing HardwareID's (especially of some SB6xx chipset mainboards) USB floppy support entries within the TXTSETUP.OEM file, which may give users a BSOD and no separate 32/64bit TEXTSETUP.OEM files, which may cause the "cannot find the file xyz" message during the OS istallation. Regards Fernando

Do you remember the line, which was mentioned? It would be fine, if you could give me the text of the whole message. This may give me the chance to correct the "bad" line. Yes, I didn't remove any HardwareID, which was within te original INF and OEM files. It is normal, that the SATA hdd running in AHCI mode is shown as SCSI.Since NCQ is one of the main AHCI features, it is automaticly enabled, if your have set the SATA Controllers to AHCI mode. Regards Fernando

The SATA Controller, where your SATA hdd is connected, only needs 1 single SATA driver (that is the file with the extension ".SYS"). The place where Windows stores all drivers is the WINDOWS\SYSTEM32\DRIVERS folder. So you have to copy the appropriate SATA driver into that folder, but this action will not be sufficient to let Windows boot from the related SATA hdd. You have to change the registry settings as well.By the way: As jaclaz alredy has stated, you have posted your problem into the wrong Forum, because it has nothing to do with nLite. NLite is a tool, which has been developed for being used for the customization of original XP sources and not for the manipulation of an already exististing XP installation. Regards Fernando

Yes, you can take these files for the nLite textmode driver integration procedure, but you can use the 32bit RST driver you get from >here< as well. The content is exactly the same.Regards Fernando

Answers:1. As long as the SATA Controllers of your Notebook mainboard haven't been set to AHCI or RAID mode within the BIOS (SETUP), you do not need to integrate any driver or package from Intel. 2. If your SATA hdd is running in AHCI or RAID mode, you have to integrate just the small driver package. You can take the link to the v9.6.0.1014 WHQL certified 32bit (for XP) or 64bit (for XP x64)one. Not applicable, because the integration of the complete package is neither required nor useful. No, the complete RST package, which includes the RST driver and the RST Console software, is not "universal":The RST driver is only needed, if your system has an actual Intel Southbridge from ICH7R/M up, which is running in AHCI or RAID mode. All other Intel related systems neither need nor are able to use the RST driver and the complete RST driver/application package. The Intel RST Console software can easily be installed by running the EXE file once the OS is up, but I only recommend to install it, if your are using the SATA Controllers in RAID mode. Regards Fernando

Thank you for the link, but this driver doesn't support RAID at all.Regards Fernando

Is this just an unasked information for us or do you really want help?Here is my comment: The message you got has nothing to do with the topic of this thread. You only can expect help, if you give some basis infirmations about your hardware configuration (chipset, SATA mode), the special OS source you are using, which drivers you have loaded/integrated and what sort of other processing tasks you or nLite have done with it. Regards Fernando

You may be able to add them, but it wouldn't work.You should never try to integrate a 64bit driver into a 32bit OS and vice versa a 32bit driver into a 64bit OS. Otherwise you will run into problems while trying to install the OS. Furthermore the 32/64bit driver named IASTOR.SYS would be overwritten during the integration procedure, because both driver versions have the same name. Regards Fernando

Thanks for your searching, finding and uploading these new AMD AHCI/RAID textmode drivers for Windows XP/XPx64 dated 04/06/2010 (32bit) resp. 03/24/2010 (64bit).Since the original AMD textmode drivers v3.2.1548.37 only will support AMD SB7xx AHCI/RAID and AMD SB8xx RAID systems and have some needless entries within the TXTSETUP.OEM files, which may cause error messages regarding "missing files" while installing the OS,I have customized them. Here are the download links to the original and WHQL certified drivers, where I have just cleaned the TXTSETUP.OEM files: >32bit AMD SB7xx & SB8xx AHCI/RAID driver v3.2.1548.37 prepared for the XP integration< >64bit AMD SB7xx & SB8xx AHCI/RAID driver v3.2.1548.37 prepared for the XP x64 integration< Attention: These drivers will not work with AMD SB6xx chipsets, because the HardwareID's are missing! Users with an AMD SB6xx chipset mainboard, who want to use these newest AMD textmode drivers for Windows XP (32/64bit), may try one of these drivers, which have been customized by me: >32bit AMD SBxxx textmode driver v3.2.1548.37 for XP mod by Fernando< >64bit AMD SBxxx textmode driver v3.2.1548.37 for XPx64 mod by Fernando< Attention:These packages do contain the original 32/64bit AMD driver. I have only customized the associated text files with the suffix ".OEM" and ".INF". Due to the customization the driver has lost the WHQL stamp, but this doesn't have any effect on the function of the driver. Although I have done my very best, I cannot guarantee, that they will work for your system. You may try them at own risk. Good luck! Fernando

There are newer AMD textmode drivers for Windows XP available. The newest I found is v3.2.1540.35 dated 01/06/2010. I will do it.EDIT: Since Sp0iLedBrAt meanwhile found an even more actual driver version, I have deleted the download links with the AMD textmode drivers v3.2.1540.35. I will post the links to some customized drivers on the basis of the newest driver version 3.2.1548.37 as soon as possible.

Well I tried this and the same thing happens. However, I know the original xp cd is ok because I can install that on a single drive when I disable RAID. My guess is that the nlite cd's that I have made (I went through the process a few times) are ok, but for some reason the computer doesn't seem to like it when I try to load the os in RAID mode.Your report, that you got the same issue while running your SATA hdd's in RAID mode and trying to boot off the original (untouched) XP CD, verifies, that there must be something wrong with the MBR and the partition table entries of your active RAID partition (boot drive).Hoping, that you have already saved all important data of your RAID, I suggest to do the following: Download a tool like KillDisk for DOS (>Link<) and create a bootable floppy disk containing this tool. Run the MediaShield RAID Utility and break the RAID. You have to set both RAIDed hdd's to non-RAID hdd's. Set the SATA Controller to "IDE" mode. Boot off the prepared floppy disk and erase all data from both previously RAIDed hdd's. Enter the BIOS and set the SATA Controllers to "RAID". Enter the MediaShield RAID Utility, create a new RAID0 array with the defaut settings and set it as bootable. Enter the BIOS again and check, if the normal boot order (1. CD/DVD, 2. HDD) and the "HARD DISK BOOT PRIORITY" settings (RAID on top) are ok. Boot off your nLited XP CD with integrated nForce SATARAID drivers. Look, what happens. Good luck! Fernando

@ RBIRD7282: Another idea: Boot off the original (untouched) XP CD and look what happens. If you should come to the point, where the XP Setup asks, where you want to get the OS installed (but doesn't show your RAID partitions), there is something wrong with your nLited XP CD (bad media, burning speed too high, bad burning tool or error while copying the XP CD content onto your hdd etc.).

Additional questions:1. Have you set the RAID array as bootable? 2. Is the RAID in the top position of the BIOS "HARD DISK BOOT PRIORITY" settings?

@ RBIRD7282: It is not easy to help you, because there a lot of different possible reasons for your issue. Questions: 1. Which nForce chipset does your system have? 2. Are you running your SATA hdd(s) in AHCI or RAID mode? 3. Is your CD/DVD drive a SATA connected one? Here are some additional tips: You should use the standard BIOS settings regarding the timings (no overclocking). Unplug or disable all unneeded devices. Check your RAM sticks with Memtest. Use another CD/DVDROM drive or create a bootable USB stick with the XP image on it, if the BIOS gives you the option. Regards Fernando

Is it possible, that you have more than 3 GB of RAM? If yes, remove 1 stick and try the XP installation again.

@ RBIRD7282: I suspect, that you have put the directory for the XP processing or the driver folder for the integration onto your desktop. You should never do that. If you want to create a customized Windows XP CD by using a tool like nLite, you should create and use separate folders (named "XPCD" and "Drivers" or similar) in the Root of any partition of your hdd. Regards Fernando

@ jmr24: Here are some additional recommendations: You have to use a clean (=untouched) XP CD as source. Don't take any XP CD with a file named WINNT.SIF within the i386 directory! Let nLite do nothing else than the integration of the appropriate SATA_IDE driver folder as textmode driver and the creation of the ISO file. Unplug all unneeded devices inclusive the hdd's except the one, where you want to get XP installed. If you have more than 3 GB of RAM, remove 1 or 2 of them before you start with the XP installation (the removed RAM sticks can be reinserted once the OS installation is completed). Check your power supply (is it good enough?) and your BIOS settings (no overclocking at all during the OS installation!). Before you start with the XP installation, you should enter the BIOS and verify, that the SATA Controllers have been set to "AHCI" mode. If you should get a BSOD nevertheless, note the exact message. This may help to find the real reason for it. Good luck! Please report here about your results. Regards Fernando

@ jmr24: Welcome at MSFN Forums! This is what ASUS writes, the correct chipset name is nForce 730a. What means "didn't work"? Did you get a BSOD or did the XP Setup not detect your SATA hdd running in AHCI mode? No, it isn't. It is possible, that the nForce SATA_IDE driver v10.3.0.46 is the best for your chipset. You can get the driver from >here<. Good luck! Fernando

@ TeeTee: Welcome at MSFN Forums and thank you for having your heads up! It was the link, which was wrong.Now everything should be fine. Thanks again for your report! Regards Fernando

@ all viewers of this thread: Today I have updated my guide again. This is the changelog: new: nForce SATARAID and SATA_IDE drivers v11.1.0.43 WHQL (32/64bit) new: nForce SATARAID and SATA_IDE drivers v10.3.0.46 WHQL (32/64bit), especially for users with an MCP65 or MCP67 chipset new: modded "Actual nForce Driverpacks" v8.0 (32/64bit) updated: modded "NForce Performance Packs" v8.0 (32/64bit) updated: modded "NForce LEGACY Remix Packs" v5.9 (32/64bit) Any feedback is much appreciated. Have fun! Fernando

@ r0nan: Welcome at MSFN Forums! The error message you got indicates, that you have integrated a wrong Intel textmode driver arcitecture (32/64bit). If you want to get XP x64 installed, you have to integrate the 64bit version of the Intel textmode driver. Please check, if you really have used Windows XP x64 as source (the 64bit OS CD contains an AMD64 folder). Regards Fernando

@ ezudna: Welcome at MSFN Forums! This only happens, if the SATA Controller mode has been set to "AHCI" within the BIOS. Which link doesn't work? The simpliest way is to enter the BIOS and to set the SATA Controlles to "IDE" mode. Then you will not need to load/integrate any SATA driver.If you want to use the AHCI features, you should integrate the Intel AHCI driver into the XP CD as layed down within the start post of this thread. For more informations you may go >here<. Regards Fernando

!de nada Guaicaipuro!

@ Guaicaipuro: It is not easy to help you, because you didn't integrate the needed nForce SataRAID drivers by using nLite. Questions: Why didn't you follow my guide, which is layed down within the start post of this thread? Is your RAID array shown as "healthy" during the start up? Which error message do you get, when you hit F8 after having started the PC and choose the "Don't reboot at system failure" option? Regards Fernando

Exactly, I suspect, that there is still a special "Recovery" partition on the hdd, which contains the needed third party drivers to get the preinstalled Vista x86 runnning again after a crash.You should erase this "Vista x86 Recovery" partition and all will be fine.