Help - Search - Members - Calendar
Full Version: Integration of NVIDIA nForce Raid (and SATA) drivers
MSFN Forums > Member Contributed Projects > nLite
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29

   
Google Internet Forums Unattended CD/DVD Guide
RickSteele
WhiteWizard,

"I tryed the floppy with the WinXP/Legacy folder from the 6.70 but keep reciving the error."
nforce4, as with all of NVIDIA's chipsets, are very finnicky and compatability does not seem to be a consideration.

Try this; enable the NVIDIA controller in the BIOS, enable RAID for only those drives you will connect, reboot saving changes on the SiiL controller.
When up and running on the SiiL controller enter Device Manager and right click the "Unknown Device", hit update drivers, point to your F6 floppy disc and allow the drivers to be installed.
Reboot, then reboot again; only this time enter BIOS setup and disable the SiiL controller. Reboot, saving changes, shut down your PC manually when it will boot no further. Move your drives to the nforce controller, power up your PC and turn it on. Make sure your HDDs are plugged into the correct SATA plugs; ie: SATA 1, SATA 2....so forth.
If this works, reboot a final time into Safe Mode and run the 6.70 setup.exe.
Also you must remember that the nforce4 F6 option shows 2 driver classes when you hit "S" for select; you must hit the first one and enter, then hit "S" again and select the second choice and hit enter again-then, continue on.
rabidfan
Danke schön Fernando!

Your method worked perfectly for me, save one detail. I had one SATA drive outside my RAID array, and Windows insisted on trying to install the boot files to that drive. Once I disconnected that drive, Windows installed great! I had so much frustration trying to get my system up and running this weekend, what a relief to finally find your guide Monday.
Fernando 1
QUOTE (rabidfan @ Jan 10 2006, 03:40 PM) *
Your method worked perfectly for me, save one detail. I had one SATA drive outside my RAID array, and Windows insisted on trying to install the boot files to that drive. Once I disconnected that drive, Windows installed great! I had so much frustration trying to get my system up and running this weekend, what a relief to finally find your guide Monday.
Thank you very much for this comment.
That is a bad, but wellknown behaviour of the Windows Setup. If you have a hard disk drive outside the Raid array, it tries to install the OS on this device, even if you have set the RAID array as first bootable device. The only possibility to prevent this is to unplug the extra hdd(s) during the install of the OS.
I think, that I should mention this in my guide (first post of this thread).

CU
Fernando
RickSteele
rabidfan
"Your method worked perfectly for me, save one detail"

Learn something new everyday
Fernando 1
QUOTE (rabidfan @ Jan 10 2006, 03:40 PM) *
Your method worked perfectly for me, save one detail. I had one SATA drive outside my RAID array, and Windows insisted on trying to install the boot files to that drive. Once I disconnected that drive, Windows installed great! I had so much frustration trying to get my system up and running this weekend, what a relief to finally find your guide Monday.

QUOTE (Fernando 1 @ Jan 10 2006, 04:42 PM) *
Thank you very much for this comment.
That is a bad, but wellknown behaviour of the Windows Setup. If you have a hard disk drive outside the Raid array, it tries to install the OS on this device, even if you have set the RAID array as first bootable device. The only possibility to prevent this is to unplug the extra hdd(s) during the install of the OS.
I think, that I should mention this in my guide (first post of this thread).
Done!

CU
Fernando
-.-PhanTom-.-
QUOTE (Fernando 1 @ Jan 9 2006, 12:28 PM) *
QUOTE (-.-PhanTom-.- @ Jan 9 2006, 11:59 AM) *
small correction to this part>
CODE
Users with an nForce4 AMD/Intel SLI X16 mainboard may take the SATARAID subfolder of the new nForce chipset driver package 6.82 (download it from here), but they have to add the NVATA.CAT and the NVCOI.DLL (from the SATA_IDE subfolder) and the NVATABUS.INF (from the LEGACY subfoder of the 6.70 package) prior to the integration.

Actually the NVCOI.DLL file is already in the sataraid folder of the 6.82 drivers - same date, same size
Thank you for the information. I will check it and correct my guide regarding this point if necessary.

CU
Fernando

EDIT: I checked the nForce driver package 6.82 and found, that there is no NVCOI.DLL within the SATARAID folder. For this reason I did not change the quoted text within my guide (post No 1).


Ahh..sorry... stupid of me to post when so tired, hehe
Got confused about NVCOI.DLL and idecoi.dll ...ups
Will see if I can get your method to work -thnx
RickSteele
Users with an nForce4 AMD/Intel SLI X16 mainboard may take the SATARAID subfolder of the new nForce chipset driver package 6.82 (download it from here), but they have to add the NVATA.CAT and the NVCOI.DLL (from the SATA_IDE subfolder) and the NVATABUS.INF (from the LEGACY subfoder of the 6.70 package) prior to the integration.

Does not work for me on A8N32-SLI Deluxe-Microsoft drivers for ATAPI still installed and DVD-RW recognition during setup is through command line only; ie: G:\....... or H:\.........
Also, on one occasion only I got endless reboots after GUI finished.
Fernando 1
QUOTE (RickSteele @ Jan 17 2006, 03:24 PM) *
CODE
Users with an nForce4 AMD/Intel SLI X16 mainboard may take the SATARAID subfolder of the new nForce chipset driver package 6.82 (download it from here), but they have to add the NVATA.CAT and the NVCOI.DLL (from the SATA_IDE subfolder) and the NVATABUS.INF (from the LEGACY subfoder of the 6.70 package) prior to the integration.
Does not work for me on A8N32-SLI Deluxe-Microsoft drivers for ATAPI still installed and DVD-RW recognition during setup is through command line only; ie: G:\....... or H:\.........
Also, on one occasion only I got endless reboots after GUI finished.
@ RickSteele:
That is interesting. As I don't have a SLI X16 mainboard, I cannot test it.
My tip: Try to integrate the nForce SataRaid drivers off the 6.70 package and update the drivers after the successful install. That should work. Please give a feedback!
EDIT: I assume, that your DVD-RW device, where you are booting from, is connected to an IDE port. Otherwise you have a known problem. The CD/DVD booting device should be IDE connected, otherwise you can get conflicts with the fresh installed Sata drivers.

@ all users with a SLI X16 mainboard:
Please report about your experience with the 6.82 driver package.

CU
Fernando
RickSteele
My tip: Try to integrate the nForce SataRaid drivers off the 6.70 package and update the drivers after the successful install. That should work. Please give a feedback!

Migrated from A8N-SLI Premium and 6.70 drivers-4 WD 74G Rapters all installed in the correct sequence; ie: SATA 1, 2..etc..and the RAID array was recognized and valid. Endless reboots at logon; I would imagine due to the conflict in the ATAPI drivers-one using nforce switched and the other calling for default MS.

EDIT: I assume, that your DVD-RW device, where you are booting from, is connected to an IDE port. Otherwise you have a known problem. The CD/DVD booting device should be IDE connected, otherwise you can get conflicts with the fresh installed Sata drivers.

They are all IDE.


Also, I'm not sure this belongs here but, on nuhi's web page in the FAQ section is a reference to 4KB stripes not bootable/working at all in winXP pro. That is how I run my array-4KB stripes ever since I was able to on the A8N-SLI Premium-BIOS update added this option; and right now I am typing this reply on an ASUS A8N32-SLI Deluxe, 4 WD74G Rapters in RAID 0 using a 4KB stripe. Never any problems and much quicker than 16 and up.
Fernando 1
QUOTE (RickSteele @ Jan 17 2006, 05:48 PM) *
Also, I'm not sure this belongs here but, on nuhi's web page in the FAQ section is a reference to 4KB stripes not bootable/working at all in winXP pro. That is how I run my array-4KB stripes ever since I was able to on the A8N-SLI Premium-BIOS update added this option; and right now I am typing this reply on an ASUS A8N32-SLI Deluxe, 4 WD74G Rapters in RAID 0 using a 4KB stripe. Never any problems and much quicker than 16 and up.
So you succeeded finally?
How did you do it (F6 or nLite)? Which nForce SataRaid driver version did you install?
RickSteele
Fernando 1

"So you succeeded finally?
How did you do it (F6 or nLite)? Which nForce SataRaid driver version did you install?"

Either way on either mobo using 6.65, 6.70 on the Premium and 6.82 on the A8N32..., with or without F6, or nlite. The driver concern only affects the ATAPI drives for me and their recognition/functionality during and immediately after setup.

Also, I owe you an apology. I've just now completed a fresh install on the A8N32-SLI Deluxe modifying the sataraid folder in the 6.82 driver set as you outline in your guide, nliting winXP pro using these modified drivers and voila; here I am typing this with the NVIDIA ATAPI sw drivers installed. All went perfectly. The nvide.nvu must also be copied-setup looks for it-popup as before..........

I do not know what I did wrong before. I also had an issue with creating bootable DVD's. nuhi is working with me on this one in another thread so........I'm just wondering if this is gone too.

The F6 method on this mobo I found very unstable for the ATAPI only; ie: the DVD-RW never seemed to operate smoothly as before on the Premium mobo. Possibly the MS drivers do not play well with nforce and the 6.82 contain no NVIDIA sw drivers even though manual installation in safe mode asks you if you wish to install....The MS ones remain on reboot.

Thanks for your interest and patience; sorry again for my error.

One last thing that might be of interest: no more "ReinstallBackups" sans quotes in system32 with this install; and upon entering Safe Mode to manually install the 6.82 on this A8N32-SLI Deluxe using the same folder I pointed nlite 1.0rc5 to during driver integration for my ISO, the NVIDIA sw drivers installed this time-I copied the entire "Legacy" folder to the 6.82 from the 6.70 and also copied the requesit files from there to the 6.82 sataraid folder; so go figure!
Fernando 1
QUOTE (RickSteele @ Jan 18 2006, 05:28 AM) *
Also, I owe you an apology. I've just now completed a fresh install on the A8N32-SLI Deluxe modifying the sataraid folder in the 6.82 driver set as you outline in your guide, nliting winXP pro using these modified drivers and voila; here I am typing this with the NVIDIA ATAPI sw drivers installed. All went perfectly. The nvide.nvu must also be copied-setup looks for it-popup as before..........
Hello RickSteele,
I have to thank you
a ) for the correction of your earlier comment about my guide concerning the use of the 6.82 driver package on SLI X16 systems and
b ) for your notice, that the Windows setup asks for the NVIDE.NVU file, if you integrate the SATARAID driver subfolder (As a result of your post I have clarified this point within my guide).

CU
Fernando
-.-PhanTom-.-
QUOTE (Fernando 1 @ Jan 17 2006, 04:02 PM) *
@ all users with a SLI X16 mainboard:
Please report about your experience with the 6.82 driver package.

CU
Fernando


Just installing VMWare again ..gonna test it there first...then prob a full fresh install...this first NLited install on new system seems to have some quirks I can't really figure out...sucvh as Windows Installer service not starting as it should (even when it's set to automatic)
RickSteele
PhanTom
[/quote]

Just installing VMWare again ..gonna test it there first...then prob a full fresh install...this first NLited install on new system seems to have some quirks I can't really figure out...sucvh as Windows Installer service not starting as it should (even when it's set to automatic)
[/quote]

Firstly when nliting if you are slipsreaming sp2 into a previous winXP build, complete this first by itself and exit nlite; then relaunch nlite and slipstream all of the hotfixes/updates; exit nlite again and defrag/reboot. At this point slipstream WMP10 if you use it afterwhich launch nlite and slipstream all WMP10 updates; defrag and other than updating this folder with the new monthly hotfixes/updates, do nothing else with it and save it as "winXP....original" or whatever name you wish-sans quotes and backup to CD-RW/DVD-RW. Now you have an unmodified base os completely up to date. Create another folder and name it winXP... or whatever, copy all of the "...original" folder to here and nlite customizations in this one. Now, if an nlited custom install fails you at least have a fully updated os to install-albeit using F6.

If you do not slipstream the sp alone I have found that the files-especially in gp-do not show as updated-no end to the grief-your concern was among my experiences.

Also, follow fernando's driver integration guide using 6.82 and some files/one folder from 6.70. My ASUS A8N32-SLI Deluxe is running beautifully on a 4kb stripe...and fast.
deliriou5?
I just spent 2 hours reading as much of this as i can, and i have to say im thoroughly confused. wacko.gif

Im trying to integrate the 6.70 sata raid drivers into an xp install.

I follow the setup in the first post, but after reading further it seems this is the incorrect way to do it, or that it hasnt been update in sometime?

Another question, what is 'text mode' , nlite rc5 wont let me insert the whole sataraid folder(which is how i thought you were to do it according to the guide.)

This is the most frustrating driver install i have ever had, drivers should just work, especially from corp. like nvidia. realmad.gif sorry bout the rant.
nite0859
This method works! Thanks!

Using Windows XP with SP2 - Corp. Edition.

Procedure:
1. I copied the contents of the entire CD to a directory named G:\XPCD .
2. I used NLite to remove the IDE drivers from G:\XPCD .
3. I integrated BTS's driverpacks, as well as the user created TV packs and my own packs, included MassStorage, using Method 1 to G:\XPCD .
4. Using Notepad, I edited TXTSETUP.SIF & DOSNET.INF . I deleted all references to 'NVRAID' and 'NVATABUS' that BTS's driverpacks had inserted. This also included deleting the HWID (Hard Ware IDs) references.
5. Using the instructions outlined on the first post of this thread, I copied filed FROM the 'Legacy' folder to the 'Sata' folder. In addition, I copied the contents of the 'SmBus' folder to the 'Sata' folder. Version number : v6.70 .
6. Using NLite, I 'added' drivers. All I did was point NLite to the 'Sata' folder that contained the files from both the 'Legacy' and the 'SmBus' folders.
6a. If you re-check the DOSNET.INF & TXTSETUP.INF files with Notepad, then you'll see how and what NLite interjects in order to make the nForce 4 drivers work. (Example, you'll see : d1,nvraid.sys ....as well as... d9,nvraid.sys and what not ...)
7. After all of this, I added RyanVM's updatepack as well as several other updatepacks using RyanVm's integrator. (I'm not sure if this was in the right order, but it does in fact work.)

Thanks again. I can now boot my father in law's NF4 computer with only this CD. thumbup.gif
Fernando 1
QUOTE (deliriou5? @ Jan 19 2006, 02:52 AM) *
Im trying to integrate the 6.70 sata raid drivers into an xp install.
I follow the setup in the first post, but after reading further it seems this is the incorrect way to do it, or that it hasnt been update in sometime?
The first post is up-to-date.
I did not describe a correct and a wrong way, but 2 different ways to integrate the nForce SataRaid drivers.
If you have an nForce4 mainboard (with a Raid BIOS version 4.84 or higher) and if you want to use the easiest method, just integrate the IDE\WinXP\LEGACY subfolder as textmode driver (no preparations at all necessary!).
QUOTE
Another question, what is 'text mode' , nlite rc5 wont let me insert the whole sataraid folder(which is how i thought you were to do it according to the guide.)
The first part of the Windows installation is called "TEXTMODE" (like DOS, that means without any GUI). Mass storage (= "textmode") drivers, which are not present within the OS CD, have to be loaded within this TEXTMODE part of the installation (i.e. by F6/floppy). Otherwise Setup will not detect the unknown mass storage devices (in this case: your RAID array).
Remark: If you are integrating a driver by using nLite, you should not "insert" a folder, but just point to the content of a driver folder.
QUOTE
This is the most frustrating driver install i have ever had, drivers should just work, especially from corp. like nvidia. realmad.gif sorry bout the rant.
I totally agree with you. Exactly this is the reason why I have written this guide (to make it as easy as possible for you!).

CU
Fernando
-.-PhanTom-.-
Ok, did a fresh install again using the X16 method....seemed to work..kinda..
However, Silicon drivers were not installed, and the 3 hdds I have on the non-sillicon SATA controller appear with a "Safely remove hardware" icon in the taskbar....why the hell is that?and how do I get rid of them there...?
Hmm and just see that the "disk manager" from Computer Management in Administrative tools is totally gone!!!???...WTF...

CODE
[Main]
Env = 1.0 RC5 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 2
Target = Windows XP Professional Sp2 - build 2180 - English (United States)

[Tasks]
Remove Components
Unattended Setup
Integrate Drivers
Hotfixes and Update Packs
Patches
Tweaks
Create a Bootable ISO
Options

[Components]
;# Applications #
Accessibility Options
Briefcase
ClipBook Viewer
Defragmenter
Internet Games
Pinball
;# Drivers #
Asynchronous Transfer Mode (ATM)
Cameras and Camcorders
Display Adapters
Display Adapters (old)
Ethernet (LAN)
IBM Thinkpad
InfraRed
ISDN
Logitech WingMan
Microsoft SideWinder
Modems
MultiFunctional
Portable Audio
Printers
Scanners
SCSI/RAID
Sony Jog Dial
Sound Controllers
Tape drives
Toshiba DVD decoder card
Wireless Ethernet (WLAN)
;# Hardware Support #
ALI IDE Bus Driver
ATM Support
Battery
Bluetooth Support
Brother Devices
CMD IDE Bus Driver
Gravis Digital GamePort
Intel IDE BUS Driver
Joystick Support
Logical Disk Manager
Modem Support
Multi-port serial adapters
PCMCIA
Secure Digital host controller
Sony Memory Stick
Toshiba IDE Bus Driver
VIA IDE Bus Driver
;# Languages #
;- Keyboard
Albanian keyboard
Arabic (101) keyboard
Arabic (102) AZERTY keyboard
Arabic (102) keyboard
Armenian Eastern keyboard
Armenian Western keyboard
Azeri Cyrillic keyboard
Azeri Latin keyboard
Belarusian keyboard
Belgian (Comma) keyboard
Belgian (Period) keyboard
Belgian French keyboard
Bengali (Inscript) keyboard
Bengali keyboard
Bosnian keyboard
Bulgarian (Latin) keyboard
Bulgarian keyboard
Canadian French (Legacy) keyboard
Canadian French keyboard
Canadian Multilingual Standard keyboard
Chinese (Simplified) - Microsoft Pinyin IME 3.0 keyboard
Chinese (Simplified) - NeiMa keyboard
Chinese (Simplified) - QuanPin keyboard
Chinese (Simplified) - ShuangPin keyboard
Chinese (Simplified) - US Keyboard keyboard
Chinese (Simplified) - ZhengMa keyboard
Chinese (Traditional) - Alphanumeric keyboard
Chinese (Traditional) - Array keyboard
Chinese (Traditional) - Big5 Code keyboard
Chinese (Traditional) - ChangJie keyboard
Chinese (Traditional) - DaYi keyboard
Chinese (Traditional) - New ChangJie keyboard
Chinese (Traditional) - New Phonetic keyboard
Chinese (Traditional) - Phonetic keyboard
Chinese (Traditional) - Quick keyboard
Chinese (Traditional) - Unicode keyboard
Chinese (Traditional) - US Keyboard keyboard
Croatian keyboard
Czech (QWERTY) keyboard
Czech keyboard
Czech Programmers keyboard
Devanagari - INSCRIPT keyboard
Divehi Phonetic keyboard
Divehi Typewriter keyboard
Dutch keyboard
Estonian keyboard
Faeroese keyboard
Farsi keyboard
Finnish keyboard
Finnish with Sami keyboard
French keyboard
FYRO Macedonian keyboard
Gaelic keyboard
Georgian keyboard
German (IBM) keyboard
German keyboard
Greek (220) keyboard
Greek (220) Latin keyboard
Greek (319) keyboard
Greek (319) Latin keyboard
Greek keyboard
Greek Latin keyboard
Greek Polytonic keyboard
Gujarati keyboard
Hebrew keyboard
Hindi Traditional keyboard
Hungarian 101-key keyboard
Hungarian keyboard
Icelandic keyboard
Irish keyboard
Italian (142) keyboard
Italian keyboard
Japanese Input System (MS-IME2002) keyboard
Japanese keyboard
Kannada keyboard
Kazakh keyboard
Korean Input System (IME 2000) keyboard
Korean keyboard
Kyrgyz Cyrillic keyboard
Latin American keyboard
Latvian (QWERTY) keyboard
Latvian keyboard
Lithuanian IBM keyboard
Lithuanian keyboard
Malayalam keyboard
Maltese 47-key keyboard
Maltese 48-key keyboard
Maori keyboard
Marathi keyboard
Mongolian Cyrillic keyboard
Norwegian keyboard
Norwegian with Sami keyboard
Polish (214) keyboard
Polish (Programmers) keyboard
Portuguese (Brazilian ABNT) keyboard
Portuguese (Brazilian ABNT2) keyboard
Portuguese keyboard
Punjabi keyboard
Romanian keyboard
Russian (Typewriter) keyboard
Russian keyboard
Sami Extended Finland-Sweden keyboard
Sami Extended Norway keyboard
Serbian (Cyrillic) keyboard
Serbian (Latin) keyboard
Slovak (QWERTY) keyboard
Slovak keyboard
Slovenian keyboard
Spanish keyboard
Spanish Variation keyboard
Swedish keyboard
Swedish with Sami keyboard
Swiss French keyboard
Swiss German keyboard
Syriac keyboard
Syriac Phonetic keyboard
Tamil keyboard
Tatar keyboard
Telugu keyboard
Thai Kedmanee (non-ShiftLock) keyboard
Thai Kedmanee keyboard
Thai Pattachote (non-ShiftLock) keyboard
Thai Pattachote keyboard
Turkish F keyboard
Turkish Q keyboard
Ukrainian keyboard
United Kingdom Extended keyboard
United Kingdom keyboard
United States-Dvorak for left hand keyboard
United States-Dvorak for right hand keyboard
United States-Dvorak keyboard
United States-International keyboard
Urdu keyboard
US English Table for IBM Arabic 238_L keyboard
Uzbek Cyrillic keyboard
Vietnamese keyboard
;Arabic
Arabic (Algeria)
Arabic (Bahrain)
Arabic (Egypt)
Arabic (Iraq)
Arabic (Jordan)
Arabic (Kuwait)
Arabic (Lebanon)
Arabic (Libya)
Arabic (Morocco)
Arabic (Oman)
Arabic (Qatar)
Arabic (Saudi Arabia)
Arabic (Syria)
Arabic (Tunisia)
Arabic (U.A.E.)
Arabic (Yemen)
Divehi (Maldives)
Syriac (Syria)
Urdu
;Armenian
Armenian
;Baltic
Estonian
Latvian
Lithuanian
;Central Europe
Albanian
Bosnian (Latin, Bosnia and Herzegovina)
Croatian
Croatian (Bosnia and Herzegovina)
Czech
Hungarian
Polish
Romanian
Serbian (Latin)
Serbian (Latin, Bosnia and Herzegovina)
Slovak
Slovenian
;Cyrillic
Azeri (Cyrillic)
Belarusian
Bulgarian
FYRO Macedonian
Kazakh
Kyrgyz (Kyrgyzstan)
Mongolian (Mongolia)
Russian
Serbian (Cyrillic)
Serbian (Cyrillic, Bosnia and Herzegovina)
Tatar
Ukrainian
Uzbek (Cyrillic)
;Georgian
Georgian
;Greek
Greek
;Hebrew
Hebrew
;Indic
Bengali (India)
Gujarati (India)
Hindi
Kannada (India)
Konkani
Malayalam (India)
Marathi
Punjabi (India)
Sanskrit
Tamil
Telugu (India)
;Japanese
Japanese
;Korean
Korean
;Simplified Chinese
Chinese (PRC)
Chinese (Singapore)
;Thai
Farsi
Thai
;Traditional Chinese
Chinese (Hong Kong S.A.R.)
Chinese (Macau S.A.R.)
Chinese (Taiwan)
;Turkic
Azeri (Latin)
Turkish
Uzbek (Latin)
;Vietnamese
Vietnamese
;Western Europe and United States
;# Multimedia #
AOL ART Image Format Support
Media Center
Movie Maker
Music Samples
Old CDPlayer and Sound Recorder
Speech Support
Tablet PC
;# Network #
Client for Netware Networks
Communication tools
FrontPage Extensions
Internet Connection Wizard
Internet Information Services (IIS)
MSN Explorer
Network Monitor Driver and Tools
Network Setup Wizard
NWLink IPX/SPX/NetBIOS Protocol
Outlook Express
Peer-to-Peer
Windows Messenger
;# Operating System Options #
.NET Framework
Administrator VB scripts
Desktop Cleanup Wizard
Disk and Profile Quota
Disk Cleanup
Document Templates
DR Watson
Extra Fonts
FAT to NTFS converter
File and Settings Wizard
Manual Install and Upgrade
MS Agent
Out of Box Experience (OOBE)
Remote Installation Services (RIS)
Save Dump Utility
Search Assistant
Security Center
Tour
Web View
;# Services #
Error Reporting
Fax Services
Messenger
Remote Registry
Uninterruptible Power Supply
;# Directories #
DOCS
SUPPORT
;# Compatibility #

[KeepFiles]
msconfig.exe

[RemoveFiles]
blastcln.exe
clock.avi

[Options]
CABRecompress
ClassicSetup
BlackSetupBack
GuestName = ""
AdminName = "Admin"
ProfilesDir = "%SystemDrive%\Documents and Settings"
ProgFilesPath = "C:\Program Files"
TargetPath = "WINDOWS"
temp_dir = %USERPROFILE%\Local Settings\Temp
SrvpEnabled
CleanBiosInfo
AdvTweaks
isovol = WinLite
isoatt = -allow-multidot -relaxed-filenames -allow-leading-dots -N -l -d -D -joliet-long -duplicates-once -no-emul-boot -b boot.bin -hide boot.bin -hide boot.catalog

[Patches]
TcpIp = 100
UsbPoll = 500
DoUxTheme
DoSFC

[Services]
Alerter,4
ALG,3
AppMgmt,3
Browser,4
CryptSvc,2
DHCP,2
TrkWks,2
DNSCACHE,2
EventLog,2
HTTP,3
HTTPFilter,3
HidServ,4
CiSvc,4
IpInIp,3
IpNat,3
IpFilterDriver,3
PolicyAgent,2
Ip6Fw,3
NDProxy,3
NetLogon,3
Netman,3
NetDDE,4
NetDDEdsdm,4
NLA,3
xmlprov,3
NtLmSsp,3
SysmonLog,3
PlugPlay,2
ProtectedStorage,2
RasAuto,4
RasMan,4
RpcLocator,3
RemoteAccess,4
seclogon,3
SamSs,2
LanmanServer,2
SCardSvr,3
SENS,4
LMHosts,3
TapiSrv,3
Themes,2
VSS,3
AudioSrv,2
SharedAccess,2
Wmi,2
W32Time,2
LanmanWorkstation,2

[Tweaks]
Boot and Shutdown-Do not Parse Autoexec.bat
Boot and Shutdown-Setup Prefetch-Cache-Boot prefetching enabled
Disable Visual Effects-Disable: Animate windows when minimizing and maximizing
Disable Visual Effects-Disable: Slide taskbar buttons
Disable Visual Effects-Disable: Transitions and Shadows
Disable Visual Effects-Disable: Use a background image for each folder type
Disable Visual Effects-Disable: Use common tasks in folders
Disable Visual Effects-Disable: Use drop shadows for icon labels on the desktop
Explorer-Advanced Search: preconfigure options
Explorer-Change Explorer Folder View to: details
Explorer-Classic Control Panel
Explorer-Disable Autorun
Explorer-Disable Prefix: Shortcut to
Explorer-Launch folder windows in a seperate process
Explorer-Show all files and folders
Explorer-Show Drive Letters in front of Drive Names
Explorer-Show extensions of known file-types
Explorer-Use small icons in Explorer bar
File Open/Save Dialog-Disable File MRU-List
Internet Explorer-Disable Download Complete notification
Internet Explorer-Disable Market Place bookmark
Internet Explorer-Disable Media Player 6.4 created bookmarks
Internet Explorer-Enable Google URL-Search
Internet Explorer-Keep IE URL-History for-10 Days
Internet Explorer-Set IE-Cache limit to-20 MB
Internet Explorer-Set Internet Explorer to accept 10 connects at a time
My Computer-Add Device Manager to Context Menu
My Computer-Add Folder Options
My Computer-Remove Shared Documents
My Computer-Show details in Device Manager
My Computer-Show non-present devices in Device Manager
Network-Disable administrative shares
Network-Disable automatic search for network folders and printers
Network-Disable DCOM protocol bindings
Network-Disable LM HOSTS lookup
Network-Disable Microsoft-DS (close port 445 TCP/UDP)
Network-Disable restoring mapped network drives on logon
Network-Disable Simple File Sharing
Network-Hide PC in Workgroups/Domains
Network-Remove remote-computer NameSpace
Privacy-Clear most recently opened documents list on logoff
Privacy-Disable and Remove Documents List from Start Menu
Privacy-Disable Driver Update Internet prompt
Privacy-Remove Alexa Spyware
Security-Disable DCOM
Security-Disable Web Open With prompt
Security-Re-Enable user:pass URLs
Security-Screensaver Password-Protection-Enabled
Speed-Disable Info Tips on Files and Folders
Speed-Disable Optimize harddisk when idle
Speed-Disable Tracking of Broken Shortcut Links
Speed-Speed-up Access to AVI Media Files
Speed-Use Windows classic folders / No Tasks Sidepanel
Start Menu-Add Administrative tools
Start Menu-Disable popup on first boot
Start Menu-Reduce popup delay
Start Menu-Remove My Documents
Start Menu-Remove My Music
Start Menu-Remove My Pictures
Start Menu-Remove Search the Internet from Search
Start Menu-Remove Set Program Access and Defaults
Start Menu-Use small icons in Start Panel
Taskbar-Disable Balloon Tips
Taskbar-Disable Hide inactive icons
Taskbar-Disable Language-Bar
Taskbar-Hide Volume Control Icon in System Tray

[Unattended]
UnattendMode = FullUnattended
ComputerType = Automatic
HibernationNo
Resolution = 1280x1024
BitsPerPel = 32 bit (True Color)
Vrefresh = 60 Hz
DisableSRestore
MaximumDataStorePercentOfDisk = 12
DefaultThemesOff
DefaultStartPanelOff
DataExecProt = 1
DoProgFiles

[GuiRunOnce]

[Drivers]
G:\INSTALL\AMD64\DFI\NForce chipset Driver\nForce4_x16_6.82_winxp2k_english\IDE\WinXP\combined\nvatabus.inf,BUSDRV
G:\INSTALL\AMD64\DFI\NForce chipset Driver\nForce4_x16_6.82_winxp2k_english\IDE\WinXP\combined\nvatabus.inf,RAIDCLASS
G:\INSTALL\AMD64\DFI\Raid\SI3114r.inf,0
G:\INSTALL\AMD64\DFI\NForce chipset Driver\nForce4_x16_6.82_winxp2k_english\SMBus\nf4sys.inf,0
G:\INSTALL\AMD64\DFI\NForce chipset Driver\nForce4_x16_6.82_winxp2k_english\Ethernet\nvenetfd.inf,0
G:\INSTALL\AMD64\DFI\NForce chipset Driver\nForce4_x16_6.82_winxp2k_english\AudioDrv\nvmcp.inf,0
H:\IMAGE\Drivers\Dell Monitor\1905FP.inf,0
Emren
Hi board (and especially Fernando!)

I am about to get my feet wet with nLite! I am trying to install Win XP on a RAID 1 setup. My Win XP disk was included when I bought the PC, and comes pre-loaded with SP1 and some other OEM stuff. I have a ASUS K8N-E Deluxe MB, which is equipped with a nForce 3 250 Gb chipset. This MB actually has two different SATA controllers, both of which are capable of running RAIDs. The chipset itself has two SATA connectors, while the Silicon Image 3114 controller has an additional four connectors - so there's six connectors total directly on the MB.

1) Which controller should I use?

2) If I am to use the nForce controller, which driver should I use? I have been reading forums left and right about unified driver sets at nforcers.com and guru3d.com, but I am none the wiser.

3) Regardless of which controller/driver is recommended to me, is the guide in the top post still relevant to me?
Fernando 1
QUOTE (-.-PhanTom-.- @ Jan 19 2006, 02:32 PM) *
the 3 hdds I have on the non-sillicon SATA controller appear with a "Safely remove hardware" icon in the taskbar....why the hell is that
That is totally normal! All devices with hot-plugging capacity are shown in systray as "safely removable hardware".
Look here: http://www.planetamd64.com/index.php?showtopic=14090
QUOTE (Emren @ Jan 19 2006, 02:44 PM) *
1) Which controller should I use?
2) If I am to use the nForce controller, which driver should I use? I have been reading forums left and right about unified driver sets at nforcers.com and guru3d.com, but I am none the wiser.
3) Regardless of which controller/driver is recommended to me, is the guide in the top post still relevant to me?
My answers:
1. The nForce Raid controllers will have the better performance than the Silicon Image ones.
2. You can take the nForce SataRaid drivers off the 6.70 package (see my first post), but you have to take the other nForce drivers (GART, SMBus etc.) from another driver package. Although I didn't try it yet, you should also be able to take all drivers - inclusive the nForce SataRaid ones - off the new 8.22 Remix driver package. Important is, that you integrate all needed drivers and files (look into the driver package structure and compare it with my guide). If you don't have an actual nVRaid BIOS (v. 4.84 or higher), you should take the SataRaid drivers off the package 6.53.
3. Yes!

CU
Fernando
-.-PhanTom-.-
QUOTE (Fernando 1 @ Jan 19 2006, 04:27 PM) *
QUOTE (-.-PhanTom-.- @ Jan 19 2006, 02:32 PM) *
the 3 hdds I have on the non-sillicon SATA controller appear with a "Safely remove hardware" icon in the taskbar....why the hell is that
That is totally normal! All devices with hot-plugging capacity are shown in systray as "safely removable hardware".
Look here: http://www.planetamd64.com/index.php?showtopic=14090
Fernando


Hmm just find it strange that they didn't do this the first time I installed XP on this new machine...can't really see what I did differently, other than I remembered to copy the NVCOI.DLL (from the SATA_IDE subfolder) this time, which apparently is the cause of this behaviour......?

Any ide why my Silicon drivers isn't installed properly during setup?
Lemonzest
Worked great here on my Lanparty NF3 UT 250Gb (nForce3 raidbios 4.52) with driver version 6.22 (from 6.82 pack) and Nlite 1.0 RC5 smile.gif
Fernando 1
QUOTE (-.-PhanTom-.- @ Jan 19 2006, 04:58 PM) *
Any ide why my Silicon drivers isn't installed properly during setup?
No, if you integrated them correctly.
-.-PhanTom-.-
QUOTE (Fernando 1 @ Jan 19 2006, 07:16 PM) *
QUOTE (-.-PhanTom-.- @ Jan 19 2006, 04:58 PM) *
Any ide why my Silicon drivers isn't installed properly during setup?
No, if you integrated them correctly.


Hmmm just added them as PNP driver.... but maybe there has to be a hdd attached to the controller for XP to iniciate the install of this controller?
Fernando 1
QUOTE (-.-PhanTom-.- @ Jan 19 2006, 07:57 PM) *
Hmmm just added them as PNP driver.... but maybe there has to be a hdd attached to the controller for XP to iniciate the install of this controller?
Is it possible, that you did not enable the Sil Controller within BIOS (because you don't use them actually)? In this case it is clear, that the driver has not been installed.

CU
Fernando
-.-PhanTom-.-
QUOTE (Fernando 1 @ Jan 19 2006, 09:10 PM) *
QUOTE (-.-PhanTom-.- @ Jan 19 2006, 07:57 PM) *
Hmmm just added them as PNP driver.... but maybe there has to be a hdd attached to the controller for XP to iniciate the install of this controller?
Is it possible, that you did not enable the Sil Controller within BIOS (because you don't use them actually)? In this case it is clear, that the driver has not been installed.

CU
Fernando


yes, I made sure they were enabled in BIOS first... will do another test in a few minuttes
-.-PhanTom-.-
Ok, mystery solved. Had chosen the wrong Sil3114 driver....

Still gonna experiment with the x16 SATA install... I wanna see if I can recreate the first install that worked where I did NOT get the "Safely remove hardware" icon...will report back if I succeed
Fernando 1
QUOTE (-.-PhanTom-.- @ Jan 20 2006, 09:13 PM) *
Still gonna experiment with the x16 SATA install... I wanna see if I can recreate the first install that worked where I did NOT get the "Safely remove hardware" icon...will report back if I succeed
I don't think, that you can get a fresh install without that icon within the systray, but there should be a possibility to remove it after the end of the install.

In an other forum I have read, that the "Safely remove hardware" icon disappears, when the nForce P-ATA Controller is replaced by the MS Standard IDE Controller.
If you really want to try this, do the following:
a ) Go to the device manager and open the IDE ATA/ATAPI Controllers.
b ) Now open the"Properties" of the NVIDIA nForce4 Parallel ATA Controller and go to "update driver".
c ) Don't use the Internet and the automaticly search for the driver , then point to "not searching, but choosing yourself".
d ) Within the following window you should see 2 hardware devices, if you enable the option "show compatible devices".
e ) Choose the "Standard Dual ChannelPCI IDE Controler" and go to "next".
After a reboot the NVIDIA P-ATA Controller should be replaced by the MS Standard IDE Controller.
If the icon has not been removed and you want the nForce P-ATA driver back, replace the MS IDE driver by doing the same as above.

CU
Fernando
-.-PhanTom-.-
Ah yeah, that could be the reason indeed come to think of it....the first time I uninstalled the NVidia IDE drivers after reading posts where people recommended against installing them...
Just find it odd that they should have this influence on SATA hdds on SATA controllers.
I have no hdds on the IDE channels...only a DVD burner..
blank
hello all, i'm back with a new nf4 16x mobo and this bsod. I add nvraid form nforce 16x package, nvraid is working in txtmode but get bsod at first xp boot. I try with an old working project that working on my old nf4 mobo = same bsod. But i'm on something good biggrin.gif Xp boot correctly if i plug only my 2 disk from my raid0, if i add my third disk =bsod.
Fernando 1
QUOTE (blank @ Jan 21 2006, 10:21 AM) *
But i'm on something good biggrin.gif Xp boot correctly if i plug only my 2 disk from my raid0, if i add my third disk =bsod.
Do you get a BSOD even when you reconnect the 3rd hdd after the successful installation of Windows XP?
By the way: I have mentioned this behaviour of non-RAID hdd's during the install within my guide in the first post of this thread ("Tips" at the beginning).
blank
on my first attempt i have plug only my 2 raid disk and plug the third one before the first xp boot after install. The nvraid driver in nforce 16x package don't seem to be the same in classic packages, there no legacy folder. So i copy the content of sata-ide to sata-raid and integrate in to my cd like this. But i get bsod like i used to have before on nforce. So i remake the install with my working cd, all thing working without my third disk. I have install all drivers = all ok, hotplug the third disk to finish drivers setup all rocks !. But if i restart my comp with all driver pluggin i get bsod no.gif I can use the sillicon stata port but they are located far away on my mobo.
Fernando 1
QUOTE (blank @ Jan 21 2006, 04:11 PM) *
on my first attempt i have plug only my 2 raid disk and plug the third one before the first xp boot after install. The nvraid driver in nforce 16x package don't seem to be the same in classic packages, there no legacy folder. So i copy the content of sata-ide to sata-raid and integrate in to my cd like this. But i get bsod like i used to have before on nforce. So i remake the install with my working cd, all thing working without my third disk. I have install all drivers = all ok, hotplug the third disk to finish drivers setup all rocks !. But if i restart my comp with all driver pluggin i get bsod no.gif I can use the sillicon stata port but they are located far away on my mobo.
Either I did not really understand your reply or you did not read the question within my last post.
Now I have even more of them:
Before you reconnected your 3rd hdd, did you have a look into your device manager? Everything OK there?
Why did you need separate drivers for your 3rd hdd?
What sort of drivers did you install for the 3rd hdd?
Did you install them in safe mode?
What error message did you get?
Can you please give some informations about your system (mainboard and chipset, hdd details etc.)?
blank
my spec are: mobo an32-sli(nforce 4 16x) + a64 x2 3800+ and 1GB ram. I have 2 hitachi 80GB in raid0 on nvraid port 1/2 and 250 GB western. My nlited system work fine with the raid but get bsod every time i boot with my western disk plugin.

The first time i have install the system by the hand with a crap floppy and can get my comp work with all disk plug on nvraid port.
Fernando 1
QUOTE (blank @ Jan 21 2006, 05:39 PM) *
my spec are: mobo an32-sli(nforce 4 16x) + a64 x2 3800+ and 1GB ram. I have 2 hitachi 80GB in raid0 on nvraid port 1/2 and 250 GB western. My nlited system work fine with the raid but get bsod every time i boot with my western disk plugin.
The first time i have install the system by the hand with a crap floppy and can get my comp work with all disk plug on nvraid port.
Is one of the hdd's an IDE one or are all of them SATA connected?
If yes, did you use the NVIDIA Sata ports for all of them?
Did you put the Raid as first bootable hard disk device within BIOS (maybe the system tries to boot from your Western hdd, when it is connected)?
What is about the drivers you tried to install after you had reconnected the Western hdd?
m1ke78
Hello all.

I looked through the thread and didn't see this particular problem so hopefully it's not redundant. I'm running an ASUS A8N32-SLI Delux witn a 4400+ X2, 2 SATA seagates in RAID0.

I slipstreamed the raid drivers into xp using the nlite method with v1.0rc5 and everything seemed to go fine until I tried to install windows. During install I get a BSOD "unknown hard error Systemroot\system32\ntdll.dll" just after setup is finished loading files. I'm at a loss and have no idea what to do at this point. Any ideas on what I'm doing wrong would be great, thanks!
Fernando 1
QUOTE (m1ke78 @ Jan 21 2006, 11:51 PM) *
I slipstreamed the raid drivers into xp using the nlite method with v1.0rc5 and everything seemed to go fine until I tried to install windows. During install I get a BSOD "unknown hard error Systemroot\system32\ntdll.dll" just after setup is finished loading files.
I am nearly sure, that this error (never have seen or heard about such message before) has nothing to do with nLite or especially with the integration of the nForce SataRaid drivers.
My tip: If you google for "unknown hard error Systemroot\system32\ntdll.dll" you will find a lot of discussions about that error, for example here: http://www.annoyances.org/exec/forum/winxp/r1047757657

CU
Fernando
m1ke78
QUOTE (Fernando 1 @ Jan 21 2006, 03:36 PM) *
QUOTE (m1ke78 @ Jan 21 2006, 11:51 PM) *
I slipstreamed the raid drivers into xp using the nlite method with v1.0rc5 and everything seemed to go fine until I tried to install windows. During install I get a BSOD "unknown hard error Systemroot\system32\ntdll.dll" just after setup is finished loading files.
I am nearly sure, that this error (never have seen or heard about such message before) has something to do with nLite or especially with the integration of the nForce SataRaid drivers.
My tip: If you google for "unknown hard error Systemroot\system32\ntdll.dll" you will find a lot of discussions about that error, for example here: http://www.annoyances.org/exec/forum/winxp/r1047757657

CU
Fernando



ok I'll look into that problem elsewhere. One other thing I was hoping you could help with.

I gave up on the raid setup for the time being just to get the system up and running. After installing windows xp w/sp2, dual core driver/hotfix, and chipset drivers everything seems fine except when I try to run anything from the cd-rom. I can explore a cd and what not, but if I try to run a program off it I get "D:\Setup.exe is not a valid Win32 application". I've tried multiple cd's all with the same result (with 1 exception). The one difference I've encountered was the motherboard cd gives this error "Only part of a ReadProcessMemory or WriteProcessMemory request was completed". I don't think there's a hardware issue because I'm installing windows from a cd, there only seems to be a problem after windows has loaded.

I can deal with the raid issue and just run the system without raid for a while, but not being able to run cd's limits my use pretty heavily.

-Mike
Fernando 1
QUOTE (m1ke78 @ Jan 22 2006, 01:29 AM) *
I gave up on the raid setup for the time being just to get the system up and running. After installing windows xp w/sp2, dual core driver/hotfix, and chipset drivers everything seems fine except when I try to run anything from the cd-rom. I can explore a cd and what not, but if I try to run a program off it I get "D:\Setup.exe is not a valid Win32 application". I've tried multiple cd's all with the same result (with 1 exception). The one difference I've encountered was the motherboard cd gives this error "Only part of a ReadProcessMemory or WriteProcessMemory request was completed". I don't think there's a hardware issue because I'm installing windows from a cd, there only seems to be a problem after windows has loaded.
If your CD drive is OK, you should try to replace the nForce P-ATA Controller by the MS Standard Dual PCI IDE Controller.
Look here: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=453294
Here you can get informations about how to troubleshoot CD or DVD devices: http://support.microsoft.com/default.aspx?...b;EN-US;q218617

CU
Fernando
m1ke78
QUOTE (Fernando 1 @ Jan 21 2006, 04:37 PM) *
QUOTE (m1ke78 @ Jan 22 2006, 01:29 AM) *
I gave up on the raid setup for the time being just to get the system up and running. After installing windows xp w/sp2, dual core driver/hotfix, and chipset drivers everything seems fine except when I try to run anything from the cd-rom. I can explore a cd and what not, but if I try to run a program off it I get "D:\Setup.exe is not a valid Win32 application". I've tried multiple cd's all with the same result (with 1 exception). The one difference I've encountered was the motherboard cd gives this error "Only part of a ReadProcessMemory or WriteProcessMemory request was completed". I don't think there's a hardware issue because I'm installing windows from a cd, there only seems to be a problem after windows has loaded.
If your CD drive is OK, you should try to replace the nForce P-ATA Controller by the MS Standard Dual PCI IDE Controller.
Look here: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=453294

CU
Fernando



Thanks, I'll give that a shot. In the mean time I found a workaround by setting the ide controller transfer mode to "PIO only" instead of "DMA when applicable". I don't know enough to have any idea if that will slow data transfers but I'm assuming it will. Is there any drawback to leaving the transfer mode set to PIO only? The only device on that controller is the cd-rom. Thanks again for all your help so far and the guide. I wouldn't have even gotten this far without this thread.

-Mike
-.-PhanTom-.-
QUOTE (-.-PhanTom-.- @ Jan 21 2006, 09:48 AM) *
Ah yeah, that could be the reason indeed come to think of it....the first time I uninstalled the NVidia IDE drivers after reading posts where people recommended against installing them...
Just find it odd that they should have this influence on SATA hdds on SATA controllers.
I have no hdds on the IDE channels...only a DVD burner..


Well, seeing asI don't have any hdds on IDE channels, installing the default windows pata drivers did not remove the icon....but I bet it will be gone if I do the same for SATA drivers... (and looking at an image file from first install, I see that I somehow managed NOT to install nvidia SATA drivers as well...so they indeed are the cause of that icon appearing)
Question then remains if there are any performance/stability gains from using the nvidias hdd drivers at all?
Wouldn't want to loose performance or stability just because of a tray icon....
Fernando 1
QUOTE (m1ke78 @ Jan 22 2006, 01:43 AM) *
In the mean time I found a workaround by setting the ide controller transfer mode to "PIO only" instead of "DMA when applicable". I don't know enough to have any idea if that will slow data transfers but I'm assuming it will. Is there any drawback to leaving the transfer mode set to PIO only? The only device on that controller is the cd-rom.
You can try it, but I'm sure, that you will not be happy with a very low CD-ROM speed.

QUOTE (-.-PhanTom-.- @ Jan 22 2006, 03:01 AM) *
Well, seeing asI don't have any hdds on IDE channels, installing the default windows pata drivers did not remove the icon....but I bet it will be gone if I do the same for SATA drivers... (and looking at an image file from first install, I see that I somehow managed NOT to install nvidia SATA drivers as well...so they indeed are the cause of that icon appearing)
Question then remains if there are any performance/stability gains from using the nvidias hdd drivers at all?
Wouldn't want to loose performance or stability just because of a tray icon....
I bet, that you will get trouble if you try to replace the nForce4 Serial ATA Controller by the Standard Dual Channel PCI IDE Controller, although the MS device manager shows them as "compatible". That is exactly the error during the install of XP which causes the endless reboots at the end.
I would recommend to give the systray icon a chance (you may hide it with the task manager).
m1ke78
Just as a follow up, it appears that my slipstream problem is actually a bad motherboard. After googling the error it seems to be the equivalent of "Something in your hardware is borked". I've been getting random system lockups during post and earlier the board actually couldn't find the BIOS. It kept searching for a backup BIOS, after shutting it down for a few seconds it was fine on the next boot. I ran memtest and the memory was fine, seems like a bad mobo to me but I would hate to tear the system completely down if that's not really the problem.
Fernando 1
QUOTE (m1ke78 @ Jan 22 2006, 10:01 AM) *
Just as a follow up, it appears that my slipstream problem is actually a bad motherboard. After googling the error it seems to be the equivalent of "Something in your hardware is borked". I've been getting random system lockups during post and earlier the board actually couldn't find the BIOS. It kept searching for a backup BIOS, after shutting it down for a few seconds it was fine on the next boot. I ran memtest and the memory was fine, seems like a bad mobo to me but I would hate to tear the system completely down if that's not really the problem.
I'm hoping with you, that it isn't the mainboard which should be repaired or changed.
Before you bring it back to your vendor, check your cables (SATA and IDE) and your PSU. These hardware components are very often the reason for errors.

Good luck!
Fernando
blank
working for me now on my a8n32sli with xp64. I have had the sata-raid folder driver as txtmode and sata-ide folder driver as pnp. I plug my second driver on nforce sata port after first reboot.
Fernando 1
QUOTE (blank @ Jan 22 2006, 05:41 PM) *
working for me now on my a8n32sli with xp64. I have had the sata-raid folder driver as txtmode and sata-ide folder driver as pnp. I plug my second driver on nforce sata port after first reboot.
That is a very interesting variation for the installation of XP x64 with integrated nForce SataRaid drivers (but the wrong thread!).
Please give us answers to the following questions, because they might be helpful for other users:
What was the result with XP (32-bit)?
Which nForce driver package did you take for the successful install of XP x64?
Did you integrate the NVIDIA standard SATARAID subfolder or the one with the added files (NVATAX64.INF etc.)?

CU
Fernando
blank
for xp 32 i use the package: nForce4_x16_6.82_winxp2k_international, but i can do nothing with my 2 other nforce sata port, all driver i plug feel good in bios config but i have no driver under windows. I try a bunch of trick to get something work buy nothing get more. So i swicth to an xp64, get the nf4 16x package: nForce4_x16_6.82_winxp64_international, i made no changes on directory, no files were move, just add sataraid as txt and sataide as pnp.

First hust let's the raid disk plugs, instead xp will put boot file on disk ouside raid config. At the end of first steup part "dos like", i shutdown my comp, pluf my third disk, change boot sequence to start on raid en continue windows setup. Now i have all my disk plug on nforce sata port and working like a charm.
Fernando 1
QUOTE (blank @ Jan 22 2006, 07:43 PM) *
First hust let's the raid disk plugs, instead xp will put boot file on disk ouside raid config. At the end of first steup part "dos like", i shutdown my comp, pluf my third disk, change boot sequence to start on raid en continue windows setup. Now i have all my disk plug on nforce sata port and working like a charm.
Please explain a little bit more detailed what you have done.
As I understand you have 3 SATA hdd's.
1. They are all connected to nForce SATA ports. Two of them are put together to an nForce RAID array, the third is a single SATA hdd.
2. Before you start with the install, you unplug the non-Raid hdd (to prevent, that the XP setup puts the MBR files onto this hdd).
3. After the end of the TEXTMODE part of the install you shutdown your pc, connect your 3rd hdd and then you continue with the install.
4. This works with XP x64, but doesn't with XP x32.

Is this what you did and what happened?
What happened, when you reconnected your 3rd hdd after the successful end of the install?

EDIT:
QUOTE
So i swicth to an xp64, get the nf4 16x package: nForce4_x16_6.82_winxp64_international, i made no changes on directory, no files were move, just add sataraid as txt and sataide as pnp.
As nLite puts the driver files all together into the same OEMDIR folder, you would get the same effect, if you copy all files of the SATA_IDE into the SATARAID subfolder prior to the integration.
blank
QUOTE (Fernando 1 @ Jan 22 2006, 01:06 PM) *
As I understand you have 3 SATA hdd's.
1. They are all connected to nForce SATA ports. Two of them are put together to an nForce RAID array, the third is a single SATA hdd.
2. Before you start with the install, you unplug the non-Raid hdd (to prevent, that the XP setup puts the MBR files onto this hdd).
3. After the end of the TEXTMODE part of the install you shutdown your pc, connect your 3rd hdd and then you continue with the install.


this is what i do for x64 and working great, i haven't try it yet on xp32, last install on xp32 i plug my non raid drive at the whole end of windows install and get a bsod at restart like first debug on old nlite release. On xp32 nlited cd i had have just integrated sataraid driver.
Fernando 1
QUOTE (blank @ Jan 22 2006, 09:30 PM) *
this is what i do for x64 and working great, i haven't try it yet on xp32, last install on xp32 i plug my non raid drive at the whole end of windows install and get a bsod at restart like first debug on old nlite release. On xp32 nlited cd i had have just integrated sataraid driver.
Thanks for the reply.
When you got the BSOD after reconnecting the 3rd hdd at the end of the installation, did you try to boot in safe mode? If yes, did it fail?
Could you read the error message?
Google Internet Forums Unattended CD/DVD Guide
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.