Fernando 1

Look into the "SCSI and RAID Controllers" section.Which devices are listed there? NVIDIA nForce RAID Controller onlySee attached screenshot. Thanks for the reply and the Device Manager screenshot. As far as I can see everything seems to be fine.What sort is that "unknown device"? Please try to find out the HardwareID of this device (> right-click onto the device > "Properties" > "Details")

Look into the "SCSI and RAID Controllers" section.Which devices are listed there?

If you don't install the OS onto a RAID partition, the OS Setup won't automaticly install the needed nForce S-ATA driver.Solution: Open the Device Manager and check within the "SCSI and RAID Controllers" section, if the "NVIDIA nForce RAID Controller" is correctly installed (by using the nForce RAID driver). If yes, do the following: 1. Open the "IDE/ATAPI Controllers" section of the Device Manager. You will see a lot of devices named "Standard Dual Channel PCI IDE Controller". 2. Check, which of them is managing your natively IDE connected devices (for example CD-ROM/DVD). 3. Right-click onto all other "Standard Dual Channel PCI IDE Controllers" - one after the other - and let the Device Manager show all compatible devices ("Update Driver Software" > "Browse my computer ...." > "Let me pick ...."). Choose the listed "NVIDIA nForce Serial ATA Controller". 4. After having replaced all "Standard Dual Channel PCI IDE Controllers" by the "NVIDIA nForce Serial ATA Controller" (UNLESSS the one, where your natively IDE devices are connected), you can reboot. Now your RAID array should be correctly detected by your OS. Good luck! Fernando

No, the TXTSETUP.OEM file is only needed for the installation process of the Operating System. Once the OS is up, it has all needed drivers (= SYS files) integrated and present within the WINDOWS\SYSTEM32\DRIVERS folder. When you want to get an OS installed onto a hdd, which is connected to an unknown Mass Storage Device Controller (no suitable driver present within the OS installation media, neither natively nor slipstreamed), you need to preload the textmode driver within the first (=TEXTMODE) part of the installation. During this step only the driver itself (the SYS file) and the associated TXTSETUP.OEM file (giving the needed informations about the Controller and how to "speak" with him) are needed. But during the GUIMODE part of the installation, when the hardware devices are detected and "installed", the OS Setup needs at least additionally one INF file to get the Mass Storage Controller proper installed. So at least the installation of Mass Storage Controllers and its driver is running within 2 steps (first needs the TXTSETUP.OEM, second needs an INF file), whereas all other devices are installed in just 1 step (during the GUIMODE part) and only need an INF file to get proper installed. You obviously did understand it the correct way.

Normally yes, it depends on the exact hardware configuration. No, only the "normal" device drivers (for graphics or Ethernet adapters, chipset devices, printers, scanners etc) are/should be PnP drivers. Textmode drivers are necessary for the detection of so-called "Mass Storage Device Controllers" (special S-ATA or RAID Controllers, where the hdd's are connected). Contrary to Vista the older OS Windows XP doesn't have in-box drivers, which are able to detect your Intel ICH7R or ICH7M S-ATA AHCI Controller. That is the reason, why you have to integrate or load the special Intel textmode drivers. The textmode drivers are needed for the detection of the hard disk drives and their partitions at the beginning of the installation process (just after loading the first files during the TEXTMODE phase), whereas all other (PnP) drivers are not needed until the hardware detection part of the OS installation (after the first reboot = during the GUIMODE part of the install). Textmode drivers for all pre-Vista Operating Windows Systems have a file named TXTSETUP.OEM, whereas PnP drivers just have one or more INF files (files with the extension ".INF").

What are you expecting?You already have written, that the TXTSETUP.SIF file edited by Benetnach wouldn't work. That is why I recommended to let nLite do this job. If nLite would not be able to do the correct settings within the TXTSETUP.SIF file, none of the big amount of nLite users would have succeeded with the integration of the Intel S-ATA driver. It seems to me, that Benetnach isn't sure himself, which sort of S-ATA Controller his system actually is using: Is it ICH8R or ICH9R or even a JMicron Controller?EDIT: I just have seen, that this is my post no 1000 - as times go by....

There must be an option within your BIOS to disable AHCI and to run the S-ATA Controller in IDE mode.After having switched the S-ATA mode from AHCI to IDE mode you should be able to get XP installed without any problems by booting off the original (not nLited) XP SP2 CD.

I am sorry, but I cannot help you.Since your motherboard has an nForce2 chipset and NVIDIA didn't develop any Vista nForce IDE drivers, which are supporting nForce2 RAID systems, you will not be able to run Vista with an nForce RAID system. Vista is not a useful OS for your hardware configuration. CU Fernando

I think, that you only need to choose the third of the listed Intel Controllers named "Intel® 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)", when you get the popup window while integrating of the textmode driver. No, it works fine for SATA II.

Although this problem is off topic, I will try to help you, but I need some informations:1. Which nForce chipset does your mainboard have (if you don't know, give me the name of the board). 2. Are you running Vista or did you try to install Vista and the hdd has not been detected by Vista Setup?

There is no need to edit any SIF file.You obviously have a computer with an Intel chipset, the S-ATA hdd is connected to an Intel ICH8R S-ATA Controller. Why don't you just create a bootable XP CD with integrated Intel S-ATA driver by using nLite according this guide? CU Fernando

It is not easy to understand the sense of your post and the consequences for users, who will get such an error message in the next future.As far as I understand you wanted to recommend the following: If you have updated a running Windows XP with SP3 and get an endless reboot at the end with an error message like Stop: c0000139 { Entry Point Not Found} The procedure entry point GdiGetBitmapBitssize could not be located in the dynamic link library Gdi32.dll, it is not useful to replace the broken file by any file of the same name. You have to take the file, which has been updated by SP3. You can find it within the WINDOWS\SERVICEPACKFILES\i386 directory of your OS partition. Is that correct?

Okay, I finished installing the new kernel32.dl and we still have no successful xp. Well it seems I will have to the clean install.So the solution I gave you helped, but did not solve the problem completely.Let us hope, that your hdd is not going to die.

Alright, I did exactly what is written down. "copy gdi32.dll C:\windows\system32" Because when i did exactly what is written on your post above and it came back with "Access Denied" I couldn't give you the exact command line, because I didn't know the drive letter of your corrupted XP partition. That is why I wrote "BootDriveLetter" instead of "C".

It will be very easy:When you are at point 5, enter the following: cd system32 ren gdi32.dll gdi32.old A: copy gdi32.dll BootDriveLetter:\windows\system32 exit

No, it is not an nForce IDE driver problem.Obviously the file named GDI32.DLL has become corrupted. You may try to repair the file by doing the following: 1. Boot off the Windows XP CD. 2. At the Welcome to Setup screen, press R to start the Recovery Console. 3. Press the number key that corresponds to the installation partition that you want to repair, and then press ENTER. 4. Type the Administrator password, and then press ENTER. 5. With the Windows XP CD-ROM still in the CD-ROM drive or DVD-ROM drive, type the following commands, pressing ENTER after each command: cd system32 ren gdi32.dll gdi32.old CD-ROM_or_DVD-ROM_Drive_Letter: cd \i386 expand gdi32.dl_ BootDriveLetter:\windows\system32 exit 6. Reboot and remove the CD I have found this solution for a quite similar problem here. Good luck! Fernando

Yes, I have tried " Safe Mode" and " Last known Configuration" and still get the reboots.At first step we need security regarding the reason for your reboots.So hit F8 again while booting and choose the option "no reboot at system failure". Then you will see the error message. I am afraid, that you will have to do a clean reinstall, because it seems, that the SP3 installation routine has replaced your needed and already correctly installed NVIDIA nForce Serial ATA Controller by the wrong MS Standard Dual Channel PCI IDE Controller. Exactly this is the reason for endless reboots of nForce sataRaid systems while installing Windows Operating systems.

Have you already tried to boot in safe mode (F8)?

When you are pointing to a clean (=untouched) and complete W2k3 x64 CD or to a copy of its content, nLite will detect the source properly.

Which error message did you get? This might be important to detect the reason for your problem. I have no idea, but it is never a good idea to transfer an OS installation from one system to another.You really should do a clean install of Windows XP.

At first step I recommend to boot the machine with the ghosted XP partition in safe mode (F8, without Network support). If you succeed, look into the Device Manager for errors or missing drivers.If you cannot boot in safe mode, I would do a fresh XP install. Since you don't have a RAID system, there is no need to integrate any textmode driver. The XP in-box IDE drivers will support the S-ATA hard disk drive. So you should be able to get Windows XP istalled with just a clean (=untouched) XP CD without integrating or loading (F6) any third party drivers. If you want, that the OS uses the special nForce S-ATA driver, you can integrate the content of the SATA_IDE folder of the nForce chipset package v11.09 (for MCP61) as PnP driver. You can try to integrate the SATARAID driver folder as textmode as well, but you should not highlight the NVIDIA RAID Class Controller, although it is shown as "required".

You are right, I misunderstood your question.If you want to use the AHCI features of your Intel S-ATA Controllers, you should either reinstall XP with integrated Intel S-ATA drivers (look here or do a Google search for a manual update method to the AHCI mode from within Windows XP.

You probably have to do a fresh install, if the repair function of your old ghosted OS doesn't work for you.Before I can give you any further advice, you should tell me, if you are using RAID or not. As far as I understood your post, you only have 1 single S-ATA hdd within your system. If this would be correct, you wouldn't need to integrate any NVIDIA textmode drivers.

What a surprise!

Have you tried any other nForce chipset drivers than those of NVIDIA's 11.09 pack? If not, you may have a look here.