Fernando 1

You should use the 6.25 to be on the safe side, but you can try the 6.67 (take only the SataRaid drivers!), because this package contains much better (=native 64-bit) SataRaid drivers for nForce3 250 chipsets too. AFAIK even for nForce3 chipsets you don't need to edit the TXTSETUP.OEM, if you take the 6.67 (unlike 6.66).EDIT: This misery is probably the reason for all your problems.On the Shuttle homepage I found these informations about the released BIOS versions for the Shuttle SN95G5v3 (don't know if you have v2 or v3): That testifies, that the first Shuttle BIOS, that supports x64 drivers, was the one from 24th march 2005. Maybe you had an earlier one.Did you now flash the newest BIOS from December 2005 or do you have another mainboard type, which requires other BIOS files? CU Fernando

You might need it, if you want to install the native 64-bit SataRaid drivers (from the nForce package v. 6.66 and higher). By the way: You have taken the SataRaid drivers off the 64-bit package v. 6.66 unless I have recommended to take the package v. 6.67 (see post No 1 of this thread). If you have read all sites and posts of this thread, you should have realized, that I keep my guide layed down in post No 1 always up-to-date. I don't know. AFAIK there have been different types of nForce3 chipsets. Only nForce3 250 supports a 64-bit OS.

You have to set the CD drive as first bootable device within BIOS. After having done that, boot and when you are prompted to press any key of your keyboard, do it. Then you are able to install the OS.If you can't see "press any key ...." during the booting, you did something wrong during burning your bootable CD. When you take Nero, just go to "Recorder", choose "burn image" and point to the nLited ISO file.

Have you seen my Edit one post above? I forgot to answer your first question.Good night! Fernando

Are you sure, that you have an actual Raid BIOS (v. 4.84)? Look at the second boot display!Did you use the actual version of nLite (v. 1.0 RC4)? Do you have a Creative soundcard? (if yes, disable it within your BIOS during the install of XP x64)? If you answered "yes" to the first 2 questions and "no" the the last, I suggest to start with the installation of the 32-bit version of Windows XP according to this post: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=356029 Choose a size of 15-25 GB for Windows XP, then you have still enough space for Windows XPx64 and your other datas. Reasons: 1. Windows XP is not as demanding as Windows XPx64 concerning the hardware and the correct drivers. 2. If you have a running OS on your Raid array, it is easier to detect your problem with XPx64. 3. As you will see, there is still a lack of drivers and applications running perfectly on a 64-bit system. In this case you can switch to Windows XP via bootmanager (dual boot system). After you have got a perfectly running Windows XP on your pc, you can start again with the installation of XP x64 (on the second partition D, choose 20-30 GB as size). Please post again, when you have any news (good or bad ones). Don't give up! We will get even XPx64 installed on your Raid array! Good luck! Fernando EDIT 1: You can prevent the automatic restart, when you press F8 during booting. There is an option called "disable automatic restart on system failure".The file ACPITABL.DAT is important to set the power management of you computer. ACPI should be enabled (within your BIOS and within the nLite setting "Computer type" you have to leave it as "automatic" or to choose "ACPI enabled"). By the way, did you try to install XPx64 with the SataRaid drivers off the package 6.25? EDIT 2: It's 4 o'clock in the morning in Germany now!

I you want, you can try to create a new nLited CD with the 6.25 drivers first (see Nr. 3 within my post from 09:54) and try to install Windows XPx64 this way.I really cannot believe, that your problems are due to the fact, that you did not do a low level format. CU Fernando

Yes, and then create your Raid array onto your clean disks.Good luck! Fernando

You said, that you reformatted both disks. Did you do it in "low level format"? This is very important, because otherwise you have rests of the old file structure on your Raid array.If you have not done it, I suggest to do the following: 1. Make a "low level format" of both hard disk (take the Seagate Tool). 2. Try a new install by using your nLited CD. If this fails: 3. Create a new bootable CD by nLite, but this time take the IDE\WinXP drivers from the 6.25 package (don't edit the TXTSETUP.OEM!). Good luck! Fernando

Do you use another pc now or do you have access to the files of the partition you installed XPx64?

Is your Rad array OK (declared as "healthy" on the second boot screen)?Was your Raid detected as 1 hard disk drive during the first (TEXTMODE) part of the install?

Which driver package did you take for the integration of the SataRaid drivers?

Hi Mike,do the following: 1. Try to boot in safe mode. If you succeed, you can have a look into your device manager (do you see any yellow question marks?). 2. If you cannot boot in safe mode, try to unplug any not needed device and to boot with only 1 RAM stick. A very good x64 antivirus feeeware is Avast!4 Home. It works like a charm on 32-bit and 64-bit systems, but I am not sure, that it works with a Server OS like W2k3. You have to registrate the software by giving your eMail address, but you don't have to pay for it and you will get no Spam.Download: http://www.avast.com/eng/download-avast-home.html CU Fernando

You should use the brandnew version RC4 (attention: this version only works with .NET Framework 2.0). If you take the 6.66 driver package, you have to integrate the PATARAID subfolder. This folder contents the same files as the LEGACY subfolder of the package 6.67. I personally prefer the 6.67 package, because some of the drivers are newer and better. Just point at the LEGACY subfolder and integrate both proposed and really required drivers (NVIDIA nForce Storage Controller and NVIDIA RAID CLASS DRIVER) as textmode drivers. After having done this, you can integrate the other drivers (SMBus, Ethernet, sound, graphics adapter, printer etc.) as "normal" drivers. No! No! Why didn't you integrate this Forceware driver into your nLited CD (unpack the package, point at one of the INF files and integrate it as "normal" driver)?Good luck! Fernando

Hi,here is my comment: 1. Some people report to have trouble with the integration of the Audigy 2 ZX driver. So if you want to be on the safe side, install them later (after you completed the install). 2. Concerning the integration of the nForce SataRaid drivers you did not read exactly what I have written in post No 1: If you integrate the IDE\WinXP\LEGACY folder, there is no need to integrate other IDE\WinXP subfolders (as SATA_IDE or SATARAID). 3. The idea to remove all other IDE Bus drivers (there are about 4 or 5 of them within the section "Hardware Support") was not bad, but this action is not necessary any more since version RC1 of nLite. 4. Not a good idea at all was it to edit the TXTSETUP.SIF. These entries only make sense within the WINNT.SIF. If you choose "UnattendedInstall" by nLite, these entries are automaticly done. There is no need to edit one of the SIF files, even if you don't choose "Unattended", because Nuhi has installed a special method to prevent the installation of the wrong MS standard IDE drivers. Please reply, if you succeed (or not....). CU Fernando

It seems to me, that you have a hardware problem.Try the following: Remove the second or more RAM sticks so there is only 1 stick left. Then try to boot again with your nLited CD. If the boot fails, look at your Sata cables and adaptors (broken/damaged?). Set BIOS settings as Default and unplug all USB devices, which are not necessary for the setup. Then try it again. Good luck! Fernando

Yes - no need of pressing F6 and no need for any floppy! I will do it for the next 24 hours.Please give a message, if you succeeded or not , CU Fernando

If you really have deleted the I386 directory from the folder with the nLited files and if you can not undo this action, you have to start the whole work again (from the beginning!).As I am not an expert in integrating software as WMP10, I cannot give any advise concerning the last question. If you have any further questions, please post it into the nLite forum. Reasons: This is the wrong forum for our discussion and I do not visit it very often. CU Fernando

You can't integrate the drivers by just copying the driver folder from your desktop and pasting it somewhere on your CD. The drivers have to be integrated into the system by several entries into SIF files (WINNT.SIF and TXTSETUP.SIF). nLite stores the drivers within the folder OEMDIR (since RC3) or NLDRV (until RC2). You will find that driver folder at the end of the installation within the WINDOWS folder. If you want you can delete the folder at that time, because the installed OS do not need these drivers anymore at that place.The text of the "last session.ini" only shows, which drivers were integrated by nLite and where they came from (origin path). This ini file is not important at all for the installation of the OS, but important to see what nLite had done during its processing. CU Fernando

If you use nLite 1.0 RC1 or later, you even can skip the section "Unattended". But if you want, you can choose all sorts of "Unattended Install" inclusive "FullUnattended".You are right - the nForce SataRaid drivers are not correctly digitally signed, but the installation succeeds nevertheless because of a trick within nLite (the interfering MS drivers have lost their priority by a manipulation of Nuhi).

You are welcome! CU Fernando

If you want to integrate the nForce SataRaid drivers into a bootable XP CD by using nLite, you have to integrate them as "TEXTMODE" drivers and to choose both proposed drivers (NVIDIA nForce Storage Controller and NVIDIA CLASS DRIVER). Normally both drivers are already marked by nLite, so - if you click "OK", both will be integrated.Here is a guide for the whole thing: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=356029 CU Fernando

The integration of the nForce SataRaid drivers into Windows XP and Windows XP x64 should work with your system.For the creation of XP x64 take the 64-Bit drivers v. 6.67 from here: http://downloads.guru3d.com/download.php?det=1192 Do exactly what I have written within post No 1. Good luck! Fernando

As you have already realized, both folders contain exactly the same SataRaid drivers!The NVIDIA nForce SataRaid drivers are not easy to install - you are right. But after several weeks of intensive tests and hundreds of failed installations I found an easy and safe way to integrate them into a bootable XP CD (see post No 1). Why do you make it even more complicated than it is? Thousands of owners of a pc with an nForce SataRaid system got Windows XP installed by using my guide within this thread. Take the LEGACY folder or the SATARAID folder (with the 3 added files) and just do it. If you have an nForce Raid system, this method should work for you too. Between the methods "LEGACY pure" and "SATARAID plus 3 files" there is only a small difference in the way , but no difference in the result. The answer is given within my first post of this thread: Additional I should mention, that my guide only works this easy way, when you do it with nLite v. 1.0 RC1 or higher. Nuhi has implementated a method into nLite, which prevents the installation of the wrong MS drivers during the GUIMODE part of the installation. You may try it, but why? It is much more complicated than the way I propose. If you have a SataRaid system, there is no cause to replace the "normal" Sata/Pata driver NVATABUS.SYS by the non-Raid driver NVATA.SYS. They are not totally identical, because they have different names and this has a good reason: the file NVATABUS.INF contains the install informations for the NVATABUS.SYS, while the NVATA.INF is specially designed for the NVATA.SYS. So both files need each other and may not be replaced crossover. Everything clear now? CU Fernando

When you integrate the LEGACY folder of the 6.70 package, you will get all needed drivers of this package (no need for an update later). Just to take the LEGACY folder is the easiest method. A little bit better for the install of a Microsoft OS is it to have the CAT files within the same folder. So if you copy the NVATABUS.INF, NVCOI.DLL and NVATA.CAT into the SATARAID folder and then do the integration of this completed SATARAID folder, it might be easier for MS to take the correct drivers. No editing is necessary! I would not propose this method, if you have an nForce Raid array, because the update of the Raid driver is not as easy as the update of a normal hardware driver.CU Fernando

That are really good news - Congratulations! This will be not a problem. Go into the device manager, open the IDE ATA/ATAPI Controller, right click on NVIDIA nForce4 Parallel ATA Controller > "driver update" > not automaticly > not search, have ... > show compatible hardware. There you will find the "Standard Dual Channel PCI IDE Controller". Choose it and install it.My personal impression about this MS driver: the nForce P-ATA (SW IDE) driver is better. I would only change this driver, if I would have a problem with it (any issue with my CDROM or DVD device), but until now everything was perfect with my IDE devices. CU Fernando