Fernando 1

If I wanted to do a Repair-Install (I never do this) I would have a non-nLited XPCD for this.It should be mentioned, that this method will not work, if you have hdd's, which are running in AHCI or RAID mode. Users with such hardware configuration have to integrate the needed textmode driver into the original CD, if they want to use the Repair option. EDIT: I am not sure about that.This is a statement I found here: A Repair Install will replace the system files with the files on the XP CD used for the Repair Install. It will leave your applications and settings intact, but Windows updates will need to be reapplied. If you want just to fix the MBR, you should choose the Recovery option. This way nothing else will be installed onto your hdds. Notice: To prevent any confusion I have deleted my original answer, because I obviously was wrong. Thanks to -X- for his reply!

When the Windows OS Setup detects a WINNT.SIF with an [unattended] section. Won't it re-add the services (and other things) nLite had removed?No, nothing will be really installed until you get the Repair option.After having repaired what you want, you can simply reboot and remove the CD.

@ bobmiers: Since johnhc has sent me a PM and asked me to have a look into this thread, I will try to help. At first step I need some further informations: Why did you integrate the SATARAID folder, which is only suitable for RAID users? Do you have enabled RAID within the BIOS? Why did you delete the partition and created a new one? If you want to reuse an already existing partition, you should just format it. Have you seen any error message? If yes, which error code did you get? The error message and the code may lead us to the reason for the BSOD. You will get the complete error message, when you hit F8 while rebooting and choose the "Don't reboot at system failure" option. Now we are at the most important point: The "HARD DISK BOOT PRIORITY" BIOS settings. Only the hdd, which is in the first place, will be the active one with a boot sector and the MBR.Each time, when you have changed the SATA cables or the hdd's, but before you are going to boot into an OS or off a CD/DVD/USB, you have to enter the BIOS and check the "HARD DISK BOOT PRIORITY" settings. Otherwise you may not be able to boot any OS. Notice: The HARD DISK BOOT PRIORITY has nothing to do with the order of the usual boot devices (1. CD/DVD, 2. HDD etc.).

Congratulations @ Forsti, that you solved your problems at least! Nevertheless I do not totally agree with your thoughts regarding the cause of your issues: The installation of a Windows OS by booting off an USB port works fine (if you do it the right way). I doubt, that this is the only possible explanation for your success. I still suspect, that your problems were caused by a wrong BOOT.INI entry (leads to the first error message) and a wrong HARD DISK BOOT PRIORITY order (leads to the second error message).Have fun with Windows XP on your new SSD! Fernando

@ majax79: Fine, that you succeeded with the XP installation by chosing the driver and Controller I had suggested. You have to install the Intel chipset (=INF) "drivers" which are managing the Intel System Management devices (SMBus Controller etc.). That is no problem at all since you got Windows XP up.The solution is very easy: Just download and install this package. It contains the actual Intel chipset device "drivers". After having done that, you will not see the yellow mark within the Device Manager anymore. No, the Intel textmode drivers (with the IASTOR files) have nothing to do with the SMBus Controller. You have done everything correctly.By the way: You can prevent the yellow mark within the Device Manager from scratch, if you integrate 2 different Intel drivers into the XP CD: 1. the Intel textmode driver as TEXTMODE (as you have already done) and additionally 2. the Intel chipset "drivers" (download link: see above) as PnP drivers. You will find the how-to details within my guide (first post of this thread). @ Forsti: It seems, that either the SSD has not been detected by the BIOS or that you have wrong boot settings within the BIOS of your mainboard. This is what I suggest: Open the mainboard BIOS and look into the "Advanced BIOS Features" section. There you will find different Boot order settings for 1. the Boot Devices (First/Second/Third Boot Device) and 2. the Hard Disk Drives (option name is "HARD DISK BOOT PRIORITY"). Before you are going to install Windows XP onto your new SSD drive, you should make sure, that a ) the SSD drive is listed and on the first position of the "HARD DISK PRIORITY and b ) the USB Floppy is set as "First Boot Device" and the HDD as "Second Boot Device". @ majax79 anf Forsti: Good luck for both of you! Fernando

@ Forsti: Since you don't have a mixed SATA/PATA configuration, you may choose "Ja". Before I am going to bed, I will give you a link to someone with a similar problem as you and his solution: http://forums.pcper.com/showthread.php?t=413517 Good luck and good night! Fernando

@ Forsti: If you can boot into any other OS, have a look into the C:\BOOT.INI file. It should look like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

@ Forsti: Look into my previous post, which I have edited after having seen your message. @ majax79: 1. You can leave the "OEMPreInstall" option enabled, since you have integrated the needed textmode driver (don't hit F6 while installing XP!). 2. As I told you, don't try all nLite options.

If you want to be on the safe side, you should let do nLite nothing more than1. integration of SP3 2. integration of the needed textmode driver 3. creation of the image file. @ Forsti: Welcome at MSFN Forums! Are you running the SSD SATA drive in RAID or AHCI Mode? Check the BIOS settings.You can get the JMicron textmode driver from here, but I doubt, that any textmode driver will solve your problem. I suspect, that your BIOS settings are not correct or the current BIOS version doesn't support SSD drives.

I can only certify the second statement, because I didn't try the "Prompt Repair" option myself.After pressing F10 you don't see the screen posted by -X-, but you get a Recovery Console with the options to recover or repair your system. Then you can decide (by editing a number), which of the listed detected partitions should be recovered (or repaired).

You can do it, if you want. Otherwise you can delete nLite's drivers folder named "NLDRV" manually once XP is up.

Why did you think so?

@ majax79: Thanks for your quick reply. Your SATA hdd should be connected by the Windows XP Setup, if you have integrated this actual 32bit textmode driver version, which I have linked within my guide. When the textmode driver popup came up, you should have chosen the "Intel® ICH7R/DH SATA AHCI Controller". I don't see any problem for you, if you have done it correctly. Good luck! Fernando

No, it doesn't work for Dell OEM disc.Why do you think so?Which driver did you take and which Controllers did you check while getting the textmode driver popup window?

@ majax79: The question is not, which INF file you need (nLite will copy all of them onto the CD), but which driver version you should take. Unfortunately you didn't write anything about your system (name of the mainboard/notebook/desktop computer and the Southbridge chipset). Since you have added a picture of the device manager and the driver used by the device "Intel® 82801GR/GH SATA AHCI Controller", this may help us. Please do a right click onto the Controller again, but choose the "Details" instead of the "Driver". Within the "Property" part you will see a drop-down menue. Choose the "HardwareID's" and do a picture of it.

Here is my enhanced statement after having tested it again myself:If you are booting off an nLited XP CD by having chosen any unattended install option except the "Prompt repair" one, you will not see the Recovery Console during the XP installion, but you will get it, if you press F10 while seeing the F6 textmode driver loading option. You have to wait until all in-box textmode drivers have been loaded, but then you will get the opportunity of doing repair and recovery tasks. Best wishes Fernando

@ Henrique-S: Yes, you can collect all post-SP3 Hotfixes you have downloaded from Microsoft Update Server and put all of them into the XP CD by using nLite, but I ask you: Why do you want to do that? The Windows XP CD you are going to create will be up-to-date just for several days (if you are lucky), but then you will need to download new hotfixes - or maybe even hotfixes to solve an issue of a previous already installed one. My opinion is, that you should not waste your time with these things. You wrote, that you want to install Windows XP onto at least 5 different computers. Why don't you start doing it? A lot of people here have given you a lot of advices. If you want to do everything at once, the risk is very high, that you will be disappointed with the result. And you will ask us, why the installation failed and we are trying to guess.

So we can forget about the step 2 using the RyanVM's since it all can be done with nLite?What g-force certainly meant was, that you may integrate any RyanVM Update Pack by using nLite.EDIT: g-force was quicker, I didn't see, that he was online too.

Yes, boot of the CD/DVD and hit the F10 button while seeing the F6 driver integration message at the bottom of the display. Then you will get the repair option.Update: My answer was not totally correct. You can get the Recovery Console (for fixing the MBR etc.) by hitting F10, but probably will not be able to do a "Repair Install", if you are booting off an "Unattended Install" XP CD. For further details you may look here.

Ask Microsoft for the answer. A direct update from SP0 to the SP3 version is not possible. You should only slipstream the SP3. If you try to slipstream the other SP's too, you may run into problems.

@ Henrique-S: If you read your linked MSFN Forum discussion carefully, you will realize, that it is not possible to install the SP3 pack from within an SP0 (=RTM) version of Windows XP, but that it is no problem to integrate the SP3 pack into an SP0 version of the OS. By the way: You will not be able to test your drivers by any VMWare installation, because the needed hardware is not present in reality.

@ Henrique-S: Since you are a newbee with nLite, I would like to give you some general tips: Before you start with the creation of an nLited XP CD you should check all your 5 computers, if they really will need any textmode driver. As johnhc already has written, Windows XP with integrated SP2 or SP3 doesn't need any special textmode driver, unless the SATA hdd(s) is/are set to AHCI or RAID Mode within the mainboard BIOS. If you are unsure about the BIOS settings, open the Device Manager of any running OS and look into the "IDE ATA/ATAPI Controllers" and - if present - the "Storage Controllers" sections for a controller with the word "AHCI" or "RAID" in the name. A system, which shows just Controllers named "Standard Dual Channel PCI IDE Controller", doesn't need and probably will not accept any extern textmode driver. The most important part of the nLite processing is the integration of the needed textmode driver, because otherwise the XP Setup will not detect the SATA hdd(s), which are set to "AHCI Mode" or "RAID Mode". All other device drivers can be installed without any problem after having completed the XP installation. Don't try to do everything at once. It may be a good idea to create an "All-In-One" XP CD/DVD, which is usable for all your computers, but remember: The more you customize your XP CD by using a tool like nLite, the greater is the chance of a failure during the later OS installation and the more difficult is the search for the reason. This is what I suggest for you: Start with the creation of an nLited XP CD just for your nForce chipset system. If you succeed, you may try to create a second XP CD/DVD, which is suitable for your Intel chipset mainboards. Don't use the "Unattended install" option unless you are sure about the different options. None of them, because all the files and packages you find there are outdated. The only difference between the "Intel® Matrix Storage Manager" and "Intel® Matrix Storage Technology" pages of the Download Center is the age of the presented drivers and applications. The actual name of the Intel AHCI&RAID package (containing the drivers and the Console application) is "Intel® Matrix Storage Manager", but you will not will find the newest version 8.9.0.1023 here, but only by choosing a hidden way (look here).Don't waste your time with these things. It doesn't make any sense to integrate the complete package of the "Intel® Matrix Storage Manager". Do what I have written within my Intel textmode driver integration guide and within my first post within this thread. No, you are mixing the version of the AHCI/RAID drivers of the Intel Storage Manager (actual: v8.9.0.1023) and the version of the Intel Chipset Device ("INF Utility") drivers (actual: v9.1.1.1014). All the links within my guide are leading to the already prepared and actual driver versions.Good luck! Fernando

@ Pookey: Additional informations: The absence of a visible repair option while booting off an unattended XP CD is not a bug of nLite, but a "feature" of the Windows Setup routine after the detection of a file named WINNT.SIF. As Kelsenellenelvian has written, you can get the "Repair" option nevertheless, if you hit F10 while seeing the F6 option at the bottom of the boot display. Even after having chosen the "Unattended Install" option it is possible to get the Eula license agreement during the XP installation. This is what you should do: Before you are going to create the ISO file, open the WINNT.SIF (is within the i386 directory) with notepad and set the line "OemSkipEula=Yes" to "OemSkipEula=No".

@ Henrique-S: The drivers, which are presented by ASUS are not actual and often not designed for being integrated into an OS CD. Since not the manufacturer of the mainboard (example: ASUS), but the manufacturer of the on board chips (example: Marvell) are the developers of the needed drivers, it is a good idea to have a look into the driver page of the latter company. Here is the link to the newest Marvell Network Controller driver for Windows XP: http://www.marvell.com/drivers/driverDisplay.do?driverId=202 As you will see after the extraction, there is no TXTSETUP.OEM file.

As I already have written, no Network Controller driver needs or uses a TXTSETUP.OEM file. If you see such file within a Marvell driver package, it is for a Marvell SATA Controller driver, but not for a Marvell Network Controller driver. So you have to integrate any Network Controller driver by choosing the "PnP Mode" instead of the "TEXTMODE" option. You may do it like this, but you will get more drivers and unneeded files onto your nLited CD than needed. The only driverpack which should be used with the "Multiple Driver" option, is the nForce chipset driverpack. Forget those TXTSETUP.OEM files, because the Ethernet drivers do not need them. Furthermore nLite doesn't show them at all. You just have to pick any INF file and nLite will copy all files and subfolders of the directory where you have hit the INF file. I think, that this is what johnhc meant.