Fernando 1

Which S-ATA driver did you integrate and which S-ATA Controller did you highlight when you got the textmode driver popup window?

You are right, I didn't realise, that brotherik wanted to change the user name during the unattended install.

Just add a "new user" within the section "User" of the "Unattended" part of nLite processing. You can give the "new user" any name and all rights you want and even set the autologon to this "new user".

Thanks for your report clearing up, that your issue had nothing to do with the integration of the nForce IDE drivers into a bootable XP CD.

mara, you should remove the picture or replace it by another one, because everyone can read the CD key of your OS. CU Fernando

@ TheSarge: Did you succeed or not? You only can help other users, if you are posting what you have done and the results of your efforts. @kunstlerleben: What are you going to do? Maybe you should try to get help somewhere else, because your problem has nothing to do with the integration of the nForce drivers.

You should be able to get Windows XP SP2 installed without slipstreaming any drivers. Windows Setup is not able to use the slipstreamed nForce SATA_IDE drivers during the TEXTMODE part of the installation.You may nevertheless create a new bootable CD by burning the nLited ISO file again (with reduced speed). Another option: Try to boot off your original XP SP2 CD and look what happens.

That's really weird!Your CD is bootable, otherwise you would never get the Windows Setup screen. Is it possible, that any key of your keyboard is blocked or something laying on it? That might be an explanation why you don't see the message "Hit any key to boot off CD" and it's just booting off CD. If you have a second keyboard, replace your current one and start again booting off CD.

May be you have to start the installation from scratch, because it was unexpectedly interrupted by removing the OS CD.Nevertheless you shoould have a look into the BOOT ORDER settings within your BIOS. First bootable device should be CDROM and second bootable device should be the hdd with the MBR.

Before you do anything else, try to boot off the already used CD again and let it inserted until the XP installation has been finished.

That was the mistake - the CD is still needed by Windows XP Setup during the GUI part of the installation.

Thanksfor your reply.Is it possible, that you reinserted the wrong CD while rebooting? Please insert the correct nLited CD again, restart the computer and look what happens.

So the error message was misleading...Maybe you have inserted a (wrong) not bootable CD. Please explain what happened. You wrote, that the error message came at the point where it should load GUI. That means, that you could boot off the nLited CD and copy the files during the TEXTMODE part of the installation. Questions: 1. Did Windows Setup detect your hdd's? 2. Where you able to decide where (which partition) you want to get XP installed? 3. Did you get the error message exactly during the first reboot or earlier/later? 4. Did you hit F6 while rebooting?

If this happens after the first reboot while installation, you obviously have forgotten an inserted floppy disk and have set the floppy drive as first bootable device.Suggestion: Remove the inserted floppy disk from the floppy drive and set the CDROM drive as first bootable device within the mainboard BIOS. After a reboot from your nLited CD the interrupted XP installation should continue.

No, this would make no sense for you (unless you have more than 1 hdd).The important task for you is to get a working OS installed. If you would create a RAID, things would get even more complicated than now without RAID.

If you don't have any nForce RAID array, there will be no need to integrate the SATARAID driver folder, because Windows XP Setup will detect your S-ATA hdd(s) automaticly. What you can do is to integrate the SATA_IDE folder of your used nForce chipset package, but this is a PnP and not a textmode driver.

Do you have created any nForce RAID array?

I get these error mesages during the initial loading of drivers (the phase right before Windows would ask you to insert your F6 disks if you had pressed F6 right when Windows Setup had stared). Are you sure, that you used the correct driver for Windows XP?If yes, I recommend to do the following: 1. Download the nForce driver package again (to prevent, that the driver really was corrupted). 2. Integrate the SATA_IDE subfolder (instead of the SATARAID one) of the chipset driver package as PnP driver. Please report here, if you succeeded this way.

Ok. That means, that you would not need to load any textmode driver while installing Windows XP. Windows Setup is not able to use the nForce RAID driver, because it does not detect the RAID at this stage of the installation.You can do the following: 1. Create a new nLited CD with integrated nForce S-ATA driver by just enabling the "NVIDIA nForce Storage Controller" within the textmode driver popup window. 2. After having finished the XP installation you can run the installer of your used nForce chipset driver package and choose the "MediaShield" driver installation.

I have never seen or heard about such error message.To exclude an issue of the brandnew nLite version, I recommend to retry it with the previous version 1.4 RC2 (if you have access to that version). Furthermore I need some additional informations: 1. Do you have an nForce RAID array? 2. If yes, a ) are you going to install Windows XP onto the RAID array? b ) do you have any hdd outside the RAID? 3. Did you only integrate the SATARAID subfolder or did you try to additionally load the SATA_IDE drivers (as PnP)?

What you need is a real textmode driver (with a TXTSETUP.OEM file included) suitable for the controller where your hard disk drive is connected.Look into your Dell manual to find the exact name of the controller. Then search for the textmode driver, which will be needed to get Windows 2003 installed onto your Dell. I have already searched for you and found this site, where you can download a CERC textmode driver suitable for Windows 2003. Check if this is the correct driver for your controller. After having downloaded the driver package (it is an EXE file) you have to unpack it (by right clicking with WinRar or 7-zip). Then you can integrate the content of the extracted driver folder as textmode driver into your bootable Windows 2003 CD by using nLite.

Textmode (=Controller) drivers have a file named TXTSETUP.OEM. If your driver package doesn't have such file, it is no textmode driver, but a PnP driver. If you integrate a PnP driver, you don't need to add more than one INF file (nLite will copy all the other files automaticly). No, either the TXTSETUP.OEM is present (then it's a textmode driver) or not (PnP driver). You can't transform a PnP driver to a textmode one by just creating manually a txtsetup.oem file.

When you are going to integrate a textmode driver folder content (with a file named TXTSETUP.OEM in the folder), you get a popup with a list of available Controllers and the option to choose the one or more you need. That is what Nuhi meant.

Thanks for clarifying that. I personally have never unchecked OemPreinstall, when I created a bootable OS CD with integrated textmode drivers, but I have read the advice, to uncheck it, a few times within this forum.

When you integrate any textmode drivers, you should a ) uncheck "OemPreinstall" during processing with nLite and b ) don't hit F6 while installing the OS.