MSFN Forums > Integration of NVIDIA nForce Raid (and SATA) drivers

Fernando 1

Oct 7 2005, 01:02 AM

QUOTE (RickSteele @ Oct 6 2005, 11:47 PM)

Could not wait 'till Sunday and have just finished a complete fresh install.
Copied the nvata.cat, nvcoi.dll and nvatabus.inf to the sataraid folder prior to integration with nlite and let nlite create the initial answer file in the process, using his own OEMinf customization. The ATA/ATAPI drivers only showed up unsigned still, all others show WHQL as before so, nothing changed; has to be something in the way setup.exe registers the files because, as before, manual install rendered all drivers WHQL.

As you have seen yourself, there is no reason to copy these files into the SATARAID subfolder prior to integration. It is easier and at least safer to integrate just the LEGACY (package 6.67) or the PATARAID (package v. 6.66) subfolder without any changes.
With no kind of mixture of these files you will manage it, that the Windows XP Setup routine accepts the NVATABUS.SYS and NVRAID.SYS as WHQL-certified drivers. You can verify this at the end of the installation, when you have a look into the file SETUPAPI.LOG (you find it within the Windows folder) and search for those nForce drivers.
CU
Fernando

RickSteele

Oct 7 2005, 04:05 AM

@ Fernando 1

As you have seen yourself, there is no reason to copy these files into the SATARAID subfolder prior to integration.

Wrong; doing so integrates the NVIDIA sw drivers for my DVD/CDROM or ATA drives instead of allowing the generic MS ones-a performance bonus for me-and all ATAPI drives are properly recognized and useable within Windows Explorer during GUI setup and onwards-which was not the case before except through command line execution; also important for my personal setup routine; ie:during command file setup for app installs-mine is user attended and DVDROM recognition in Explorer is required. Finnally, these are not true SATA_RAID drivers and manual install does not install these for SATA drives.

NVATABUS.SYS and NVRAID.SYS as WHQL-certified drivers...

Refer the jpegs in my previous posts to you-they already are integrating the sata_raid folder as discussed-only the ATA/ATAPI are not showing signed, but, are stable and completely functional.

stinart

Oct 7 2005, 05:39 AM

Hey i'm a newbie here but i can't figure out what i'm doing wrong.I followed exactly the steps of the guide (edit the oem file,intergrade drivers,unattended setup with oem preinstall) but when the cd starts loading the drivers in the very first steps(blue screen),i always get the message 'nvrdx64.sys not found' and the setup ends there.Is something wrong with the nlite process?(i get a "p11" error message when i intergrade the drivers but i checked that they are in the cd after the process).Any ideas?

I have a raid+0 setup on a msi k8nNeo2 Plt.

Fernando 1

Oct 7 2005, 06:49 AM

QUOTE (stinart @ Oct 7 2005, 12:39 PM)

Hey i'm a newbie here but i can't figure out what i'm doing wrong.I followed exactly the steps of the guide (edit the oem file,intergrade drivers,unattended setup with oem preinstall) but when the cd starts loading the drivers in the very first steps(blue screen),i always get the message 'nvrdx64.sys not found' and the setup ends there.Is something wrong with the nlite process?(i get a "p11" error message when i intergrade the drivers but i checked that they are in the cd after the process).Any ideas?

Either you are in the wrong thread (the theme here is the integration of the nVRaid drivers into the 32bit OS Windows XP) or you have taken the wrong driver package (the file NVRDX64.SYS is a 64bit driver and only dedicated for Windows XP x64 Edition).
If you want to see the method how to integrate the drivers into a Windows XP x64 CD, look here:
http://www.msfn.org/board/index.php?s=&sho...ndpost&p=352404

QUOTE (RickSteele @ Oct 7 2005, 11:05 AM)

As you have seen yourself, there is no reason to copy these files into the SATARAID subfolder prior to integration.
Wrong; doing so integrates the NVIDIA sw drivers for my DVD/CDROM or ATA drives instead of allowing the generic MS ones-a performance bonus for me-and all ATAPI drives are properly recognized and useable within Windows Explorer during GUI setup and onwards-which was not the case before except through command line execution; also important for my personal setup routine; ie:during command file setup for app installs-mine is user attended and DVDROM recognition in Explorer is required. Finnally, these are not true SATA_RAID drivers and manual install does not install these for SATA drives.

Since I started this thread, my only intention was to give all users with an nForce SataRaid system an as-easy-as-possible guide how to integrate these weird drivers into a bootable CD without BSOD and reboot loopings at the end. The main thing is the result (that the integration succeed and the OS works) and not the way to go. Maybe your method (copying a lot of files into the SATARAID subfolder instead of just using the PATARAID subfolder) is better for you or shortens the installation time of the OS (I need 7-10 minutes with my system), but this might not be important for other users and especially for newbies.

QUOTE (RickSteele @ Oct 7 2005, 11:05 AM)

NVATABUS.SYS and NVRAID.SYS as WHQL-certified drivers...
Refer the jpegs in my previous posts to you-they already are integrating the sata_raid folder as discussed-only the ATA/ATAPI are not showing signed, but, are stable and completely functional.

Your jpegs in your previous posts are made after the complete installation of the OS (and a safe mode manual reinstall of the drivers?), but the problem occurs during the hardware detection at the beginning of the GUIMODE part of the installation. MS does not trust the NVIDIA drivers (look into the SETUPAPI.LOG).
@ RickSteele:
Let us stop this academic and totally useless discussion.
Be happy with your special and maybe better way to integrate the nForce SataRaid drivers and enforce your efforts to find a way to integrate the Creative Audio drivers.
But this is another theme and has nothing to do with this thread.
Good luck!
Fernando
P.S.: If you want to answer by quoting, you only have to cklick on the "Quote"-button with the yellow balloon on the right hand bottom place of the post.

bdunn13

Oct 7 2005, 03:35 PM

Fernando,

This worked perfectly with an EPoX EP-9NPAJ on 2 SATA drives running in RAID 0.

Thanks alot,
BD

RickSteele

Oct 7 2005, 03:36 PM

@Fernando 1

Let us stop this academic and totally useless discussion.

OK

Fernando 1

Oct 7 2005, 03:39 PM

QUOTE (bdunn13 @ Oct 7 2005, 10:35 PM)

This worked perfectly with an EPoX EP-9NPAJ on 2 SATA drives running in RAID 0.

QUOTE (RickSteele @ Oct 7 2005, 10:36 PM)

OK

I thank you both for your post!
CU
Fernando

swemson

Oct 9 2005, 08:58 PM

I used the nlite method to incorporate the sataraid drivers and managed to install. However I 'm getting the strangest error. I have two IDE HD's as well as a mirrored SATA raid disk. I had already installed XP PRO onto one of the ide drives.
If I make the raid HDD to boot device then i get 'DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER'
If I make the IDE HD the boot device I cget the select menu from BOOT.INI, when I select the version on the raid device, I get 'WINDOWS COULD NOT START BECAUSE THE FOLLOWING FILE IS MISSING OR CORRUPT: hal.dll' (note the ide xp pro can be selected ok)
If I make the dvd/cd the boot device ignore the 'press any key to boot from cd' I can then select either of the xp pro systems. The raid xp pro work oks but I dont want this to be my permenant config

I have re-installed but get the same result.
One strange thing the root directory of the raid disk did not get ntldr, ntdetect.com and of *.sys files, nor boot.ini. I've manually copied these from the other install.
I've tried BIOS versions 1012 1013 and 1014. I've installed the chipset stuff from 665
I've also tried the recovery console fixmbr and fixboot
I 've tried different copies of hal.dll, nothing seems to make any difference.
Sorry about the English/grammer it 4 in the morning, I need to get to bed after another long and fruitless n ight with this motherboard(ASUS A8N-SLI deluxe). This motherboard is going to find it self in a bin somewhere!

Fernando 1

Oct 10 2005, 03:00 AM

QUOTE (swemson @ Oct 10 2005, 03:58 AM)

I used the nlite method to incorporate the sataraid drivers and managed to install. However I 'm getting the strangest error. I have two IDE HD's as well as a mirrored SATA raid disk. I had already installed XP PRO onto one of the ide drives.
If I make the raid HDD to boot device then i get 'DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER'
If I make the IDE HD the boot device I cget the select menu from BOOT.INI, when I select the version on the raid device, I get 'WINDOWS COULD NOT START BECAUSE THE FOLLOWING FILE IS MISSING OR CORRUPT: hal.dll' (note the ide xp pro can be selected ok)
If I make the dvd/cd the boot device ignore the 'press any key to boot from cd' I can then select either of the xp pro systems. The raid xp pro work oks but I dont want this to be my permenant config

I am not an expert in manipulating boot managers and MBR's trying to combine several Operating Systems laying on different SATA (as Raid) and IDE hard disk drives, but AFAIK your problems have nothing to do with your mainboard and nothing to do with the integration of the nForce SataRaid drivers into a bootable CD.
The boot order is layed down in your BIOS (first boot device: X, second boot device: Y etc.). According to those BIOS settings your system searches for the first hard disk device with a Master Boot Record (MBR), which normally is the partition with the letter "C:\". It is impossible to have 2 MBR's onto 2 different partitions named C:\ parallel and to switch from the one to the other.
If you want to use your 2 Raid array HDD's (which should always be detected as 1 HDD!) with the option to switch via Windows Boot Manager to your IDE HDD's, you should do the following:
1. Configure your Raid array as you want and take the Raid array as first bootable hard disk boot device (or as the second, if you take the CDROM as the first one) .
2. If you cannot boot into your Raid array (as active boot partition C:\), repeat the installation of the OS onto the Raid array using your nLited CD with integrated nForce SataRaid drivers. After the successfull installation of the OS your IDE HDD's should be detected as well.
3. Now you have the possibility to create as many partitions as you want onto your IDE HDD's (but no disk device C:\) and to install the OS you want onto the newly created partitions of your IDE HDD's.
At the end of the procedure you have 1 MBR (on C:\, which is within your Raid array) and several partitions within and without your array.
Everything clear? If not, please ask an expert within an ASUS newsgroup or google around.
CU
Fernando

ZenLord

Oct 10 2005, 08:48 AM

Small question:

I managed to integrate these drivers perfectly (6.67) with nLite 1.0RC1, but as I'm a big fan of the BTS driverpacks, I wanted to add these packs to my cd. I did think integrating the masstorage drivers and the chipset drivers might mess up the installation, so I chose _not_ to integrate these packs.

However, when using the install cd I got an error message very quickly stating nvataraid.sys was missing. So I guess I shouldn't have integrated these packs.

Is there a way to integrate the 6.67 with nLite AND using the BTS driver packs (or some of them) without breaking the install? (f.e. by manually re-adding some lines in TXTSETUP after BTS integration has finished maybe?)

I hope BTS is able to tackle the problem with his (masstorage or chipset-)pack himself, because they are really priceless - my cd's however turn up worthless when I use them on an nForce4-platform

THX in advance!

Zl.

Fernando 1

Oct 10 2005, 09:42 AM

QUOTE (ZenLord @ Oct 10 2005, 04:48 PM)

Is there a way to integrate the 6.67 with nLite AND using the BTS driver packs (or some of them) without breaking the install? (f.e. by manually re-adding some lines in TXTSETUP after BTS integration has finished maybe?)

I have never tried this.
Ask Bashrat the Snaky himself. He is the expert concerning the BTS driver packs.

tan00001

Oct 12 2005, 02:02 PM

I have a Gigabyte K8N Pro SLI board and a Athlon64 X2 3800+ CPU(s). I tried the nLite generated CD, and it did not work for me.

In the end, I installed Xp 64 onto a regular IDE drive, then installed the raid driver, and then xcopy'ed (with /s/e/y/c/h options) everything onto the raid partition over an installation that would crash on bootup.
Then I ran "repair" from the nLite CD. That allowed me to boot into the raid installation, although with problems (e.g., system restore was gone, screen display would not do clear type font, etc.). Then I used a backup of the IDE installation to restore the system state under the RAID installation.

The xcopy cannot seem to be replaced with a restore. Restored results were not repaired successfully.

Now I have a nice and stable installation on the RAID partition. It's been running for less than 24 hours, but I have not seen any errors in the event log yet.

Fernando 1

Oct 12 2005, 03:25 PM

QUOTE (tan00001 @ Oct 12 2005, 10:02 PM)

I have a Gigabyte K8N Pro SLI board and a Athlon64 X2 3800+ CPU(s). I tried the nLite generated CD, and it did not work for me.
In the end, I installed Xp 64 onto a regular IDE drive,.........

This is the thread for the integration of the nForce SataRaid drivers into the 32-Bit OS Windows XP. If you really want to install Windows XP x64, you should discuss your problems within the XPx64 thread:
http://www.msfn.org/board/index.php?s=&sho...ndpost&p=352404

If you want help, you should give some more informations:
What did not work for you?
What happened during the install?
At which point of the installation did it happen?
Did Windows Setup recognize your hard drives or your Raid correctly?
Do you have a Raid array or only Sata drives?
Which drivers (version and subfolder) did you integrate as textmode drivers?

Bâshrat the Sneaky

Oct 13 2005, 10:42 AM

QUOTE (ZenLord @ Oct 10 2005, 03:48 PM)

Small question:

I managed to integrate these drivers perfectly (6.67) with nLite 1.0RC1, but as I'm a big fan of the BTS driverpacks, I wanted to add these packs to my cd. I did think integrating the masstorage drivers and the chipset drivers might mess up the installation, so I chose _not_ to integrate these packs.

However, when using the install cd I got an error message very quickly stating nvataraid.sys was missing. So I guess I shouldn't have integrated these packs.

Is there a way to integrate the 6.67 with nLite AND using the BTS driver packs (or some of them) without breaking the install? (f.e. by manually re-adding some lines in TXTSETUP after BTS integration has finished maybe?)

I hope BTS is able to tackle the problem with his (masstorage or chipset-)pack himself, because they are really priceless - my cd's however turn up worthless when I use them on an nForce4-platform

THX in advance!

Zl.

Hm... please post your problem in detail in the DriverPack MassStorage forum!

owenkun

Oct 21 2005, 07:43 AM

Moved post, sorry.

StingRay_NL

Oct 23 2005, 02:59 AM

On my EP-9NPA+ Ultra, with 2 Hitachi T7k250 160MB drives in raid0, and the 6.67 driver it works great! What also worked:

Unpack the 6.67 driver, copy the contents of the legacy dir to a floppy, go into sata_ide dir and copy the nvata.cat to the same floppy, go into the sataraid dir and copy the nvraid.cat to the same floppy. Then use the F6 method to load the raid drivers.

Thanks a lot Fernando! I had given up hope on the drivers later then 6.53.

dazkrlauwste

Oct 24 2005, 08:30 AM

I have an nForce3 250GB mobo and I wanna install Windows XP Pro SP2, should I just stick to the 5.10 chipset driver that are on the nvidia homepage or install the very latest chipset driver?

In the case of the latter which would that be?

Fernando 1

Oct 24 2005, 08:44 AM

QUOTE (dazkrlauwste @ Oct 24 2005, 04:30 PM)

I have an nForce3 250GB mobo and I wanna install Windows XP Pro SP2, should I just stick to the 5.10 chipset driver that are on the nvidia homepage or install the very latest chipset driver?
In the case of the latter which would that be?

Take the SataRaid drivers from the chipset driver package 6.67 (LEGACY folder) and the other drivers (SMBus, GART etc.) from the package 5.10.

dazkrlauwste

Oct 24 2005, 08:45 AM

OK, but why not take the other drivers from 6.67 as well?

Fernando 1

Oct 24 2005, 11:36 AM

QUOTE (dazkrlauwste @ Oct 24 2005, 04:45 PM)

OK, but why not take the other drivers from 6.67 as well?

Because the chipset driver packages 6.66 and 6.67 are not designed for nForce3 chipsets. You can see it, when you have a look onto the the drivers included. The GART driver, which is necessary for nForce3 boards, is missing in both packages.
Nevertheless you can use the nForce SataRaid drivers from the package 6.66 and 6.67 for nForce3 systems. They are much better than the ones from the package 5.10.
If you want to see the latest usable nForce3 chipset drivers, look here:
http://www.nforcershq.com/forum/latest-dri...-3-vt60240.html
CU
Fernando

new2slipstreaming

Oct 30 2005, 09:18 PM

Hello MSFN people, total newbie here

I have an Asus A8n-sli premuim motherboard (Nforce 4 chipset). I wish to install windows xp sp2 onto a RAID0 striped array (2xWD raptor 36 gig 10k rpm) to be used as my boot drive. I have tried without success the f6/floppy method and am also unsuccessful using the Nlite method as described by Fernando 1.

My BIOS is rev 1005 board revision 1.02
I have a new original copy of XP pro sp2.
I copied the contents of the a8n sli premuim driver cd to a new folder (nforce4).
I copied the contents of the XP pro sp2 cd to a folder (winxpsp2) and pointed nlite to its location.
I selected integrate drivers from the nlite menu options.
I went to the subdirectory LEGACY (from the driver cd folder) and chose the two files there as textmode.
I selected create ISO
I burned the ISO to a cd

The ISO cd loads ok but I still get the blue stop error screen.
I suspect that I am not doing the Nlite method correctly because I notice the xp install loading the scsi drivers after seeing it load my nvraid drivers. I am getting a blue stop error screen.

Questions.

How can I keep windows from loading these drivers over the top of my non WHQL-certified drivers?
I see the setup is loading files (nvidia raid class storage driver) and (nvidia storage class driver?) loading on the bottom of the screen, this is the textmode right?
If I select remove (windows) drivers from the nLite menu which drivers should I remove?

I'm probably in over my head here, but I was able to install this OS on the deluxe version of this board a couple months ago after some effort. Maybe I got lucky. I never registered this copy because I knew I would be getting this (premuim) version mobo.

This has probably been answered numerous times before but I cant seem to find the solution.

I searched the new ISO cd and did not find nvatabus.inf. Do I need to make a folder named OEMDIR that contains all the .inf flies for the nvraid drivers? If so, should I put this folder in the i386 folder? I thought nLite collected all files in the driver directory I pointed it to when I assigned the textmode drivers (IDE\WinXP\legacy)

Any suggestions would be much appreciated. Thanks, Chuck

Fernando 1

Oct 31 2005, 03:29 AM

QUOTE (new2slipstreaming @ Oct 31 2005, 05:18 AM)

I have an Asus A8n-sli premuim motherboard (Nforce 4 chipset). I wish to install windows xp sp2 onto a RAID0 striped array (2xWD raptor 36 gig 10k rpm) to be used as my boot drive. I have tried without success the f6/floppy method and am also unsuccessful using the Nlite method as described by Fernando 1.
My BIOS is rev 1005 board revision 1.02

Hi Chuck,
more interesting than your mainboard BIOS version is the version of your NVIDIA Raid BIOS (look onto the second bootscreen).You may need v. 4.84, if you want to install the new nForce Raid drivers.

QUOTE (new2slipstreaming @ Oct 31 2005, 05:18 AM)

Questions:
I see the setup is loading files (nvidia raid class storage driver) and (nvidia storage class driver?) loading on the bottom of the screen, this is the textmode right?
If I select remove (windows) drivers from the nLite menu which drivers should I remove?
I searched the new ISO cd and did not find nvatabus.inf.
Do I need to make a folder named OEMDIR that contains all the .inf flies for the nvraid drivers? If so, should I put this folder in the i386 folder? I thought nLite collected all files in the driver directory I pointed it to when I assigned the textmode drivers (IDE\WinXP\legacy)

Answers:
1. Right!
2. You may remove all IDE Bus Drivers within the section "Hardware Support", but normally this is not necessary with nLite 1.0 RC1.
3. If you have integrated the LEGACY subfolder during textmode driver integration, you will find all files of this folder within the I386\NLDRV folder of your ISO CD, but the files are compressed (NVATABUS.INF is named NVATABUS.IN_).
4. No, there is no need to create a special OEMDIR directory, when you use nLite 1.0 RC1.
Good luck!
Fernando

new2slipstreaming

Nov 2 2005, 08:16 PM

Thanks for the help Fernando 1. I finally realised why I was having trouble installing Windows.

I was using my SATA Plextor dvd drive on the SI controller. I had to throw in an 'old' IDE optical drive to get windows to install.

I should have remembered this from last time...

nLite rocks!

Mekrel

Nov 2 2005, 11:36 PM

Hi all,

I am having extreme problems with trying to get Windows setup to detect my raid array although I have had it working fine in the past by manually hacking txtsetup.sif with the same entries I did before.

It tells me setup cannot find any disks, so obviously something isnt going right at the moment, and Ive tried different ways.

Using nlite before reading this thread, and that didnt work. Manually doing it with hacking txtsetup.sif and I have used a few different versions users have reported and still no go.

I am using an Nforce3 DFI Lanparty 250GB UT board so the drivers I am using are obviously not the same as you with the nforce4. So I thought it would be a good idea, after you have researched quite abit into this - If I ask you to go over what im planning to do, as from reading the thread, the driver layout of the nforce3 drivers are different.

Today (2nd Nov) new nforce3 WHQL drivers were released, as per:

http://www.nvidia.com/object/nforce3_winxp_5.11

So I thought being as its WHQL it would be best to use these, and the driver layout is as follows:

as you can see, the files seem to be all in one folder, do I have to seperate them out (I.e look into the infs and find what files it needs, and put the Raid and ATA controller into seperate folders).

The Raid bios version is 4.52 and im pretty sure this is the latest version I can get, as I have the latest beta bios for this board.

Any help greatly appreciated

dale5605

Nov 2 2005, 11:42 PM

Mekrel, I think delete the raidtool folder and then just integrate that folder there.

Mekrel

Nov 3 2005, 12:01 AM

Hi dale5605

I have done that and integrated the drivers, and it has gave me two options to integrate which I told nlite to do both, and as a result have two entries in the driver list that are both text mode.

I know this is correct, and I also removed raidtool before too.

Just making the iso now, will report back in 20mins

Mekrel

Nov 3 2005, 12:54 AM

Nope, no good

CODE

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

[Tasks]
Integrate a Service Pack
Remove Components
Unattended Setup
Integrate Drivers
Integrate Hotfixes
Patches
Tweaks
Create a Bootable ISO

[Components]
;# Applications #
Accessibility Options
Briefcase
Charmap
ClipBook Viewer
Games
Internet Games
NT Backup
Paint
Pinball
Wordpad
;# Drivers #
Display Adapters (old)
;# Hardware Support #
Brother Devices
Smart Cards
;# 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
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
Danish keyboard
Devanagari - INSCRIPT keyboard
Divehi Phonetic keyboard
Divehi Typewriter keyboard
Dutch keyboard
Estonian keyboard
Faeroese keyboard
Farsi keyboard
Finnish 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
Marathi keyboard
Mongolian Cyrillic keyboard
Norwegian 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
Serbian (Cyrillic) keyboard
Serbian (Latin) keyboard
Slovak (QWERTY) keyboard
Slovak keyboard
Slovenian keyboard
Spanish keyboard
Spanish Variation keyboard
Swedish 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 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
Croatian
Czech
Hungarian
Polish
Romanian
Serbian (Latin)
Slovak
Slovenian
;Cyrillic
Azeri (Cyrillic)
Belarusian
Bulgarian
FYRO Macedonian
Kazakh
Kyrgyz (Kyrgyzstan)
Mongolian (Mongolia)
Russian
Serbian (Cyrillic)
Tatar
Ukrainian
Uzbek (Cyrillic)
;Georgian
Georgian
;Greek
Greek
;Hebrew
Hebrew
;Indic
Gujarati (India)
Hindi
Kannada (India)
Konkani
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
Afrikaans
Basque
Catalan
Danish
Dutch (Belgium)
Dutch (Netherlands)
English (Australia)
English (Belize)
English (Canada)
English (Caribbean)
English (Ireland)
English (Jamaica)
English (New Zealand)
English (Philippines)
English (South Africa)
English (Trinidad)
English (Zimbabwe)
Faeroese
Finnish
French (Belgium)
French (Canada)
French (France)
French (Luxembourg)
French (Monaco)
French (Switzerland)
Galician (Spain)
German (Austria)
German (Germany)
German (Liechtenstein)
German (Luxembourg)
German (Switzerland)
Icelandic
Indonesian
Italian (Italy)
Italian (Switzerland)
Malay (Brunei Darussalam)
Malay (Malaysia)
Norwegian (Bokmal)
Norwegian (Nynorsk)
Portuguese (Brazil)
Portuguese (Portugal)
Spanish (Argentina)
Spanish (Bolivia)
Spanish (Chile)
Spanish (Colombia)
Spanish (Costa Rica)
Spanish (Dominican Republic)
Spanish (Ecuador)
Spanish (El Salvador)
Spanish (Guatemala)
Spanish (Honduras)
Spanish (International Sort)
Spanish (Mexico)
Spanish (Nicaragua)
Spanish (Panama)
Spanish (Paraguay)
Spanish (Peru)
Spanish (Puerto Rico)
Spanish (Traditional Sort)
Spanish (Uruguay)
Spanish (Venezuela)
Swahili
Swedish
Swedish (Finland)
;# Multimedia #
Media Center
Movie Maker
Music Samples
Tablet PC
;# Network #
MSN Explorer
Web Folders
Windows Messenger
;# Operating System Options #
File and Settings Wizard
Framework
Search Assistant
Tour
Web View
Zip Folders
;# Services #
Windows Time
;# Directories #
DOCS
SUPPORT
VALUEADD
;# Compatibility #

[KeepFiles]
msconfig.exe

[RemoveFiles]
blastcln.exe
clock.avi

[Options]
ProfilesDir = "%SystemDrive%\Documents and Settings"
TargetPath = "WINDOWS"
AdvTweaks
;#ISO maker#
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 = 10
UsbPoll = 125
DoUxTheme
DoSFC

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

[Tweaks]
;# Boot & Shutdown #
Auto-End Tasks
Auto-Kill Hung Apps
Auto-Kill Hung Services
Applaunch & Boot enabled Setup Prefetch-Cache
;# Desktop,Taskbar & Startmenu #
Hide Internet Explorer icon
Show My Computer icon
None Status Messages
;# Explorer #
Add CMD SHELL:> to all Drives and Folders
Advanced Search: preconfigure options
Classic Control Panel
Disable Autorun
Disable Beep on errors
Disable Prefix: Shortcut to
Disable shortcut arrow
Remove Send To on context menu
Show extensions of known file-types
;# Internet Explorer #
Disable Internet Explorer link creation
Disable Media Player 6.4 created bookmarks
Disable Outlook Express link creation
Set Internet Explorer to accept 10 connects a time
;# My Computer #
Add Device Manager to Context Menu
Add Drive Cleanup to Context Menu
Add Services to Context Menu
Add Software to Context Menu
Show details in Device Manager
;# Privacy #
Disable and Remove Documents List from Start Menu
Disable Logging of executed programs
Disable User Process Tracking
Remove Alexa Spyware
;# Speed #
Disable Optimize harddisk when idle
;# Start Menu #
Disable Highlight newly installed programs
Disable popup on first boot
Expand Control Panel
Reduce popup delay
Remove Search the Internet from Search
Remove Windows Catalog from Start Menu
;# Taskbar #
Disable Language-Bar
;# Windows Media Player #
Disable auto-add music to library
Disable starting with Media Guide
Optimize fullscreen mode behaviour
Remove all context menu entries
Zoom video to windowsize

[Unattended]
UnattendMode = FullUnattended
ComputerType = Advanced Configuration and Power Interface (ACPI) PC
ProgFilesPath = "C:\Program Files"
HibernationNo
FirewallOff
Resolution = 1280x1024
BitsPerPel = 32 bit (True Color)
Vrefresh = 60 Hz
DisableSRestore
MaximumDataStorePercentOfDisk = 12
IISInstall = 1
DataExecProt = 0

[Drivers]
E:\My Documents\nForce_5.11_winxp2k_international_whql\IDE\WinXP\nvatabus.inf,BUSDRV
E:\My Documents\nForce_5.11_winxp2k_international_whql\IDE\WinXP\nvatabus.inf,RAIDCLASS
E:\My Documents\nForce_5.11_winxp2k_international_whql\SMBus\nvsmbus.inf,0
E:\My Documents\nForce_5.11_winxp2k_international_whql\MemCtl\nvmemctl.inf,0
E:\My Documents\nForce_5.11_winxp2k_international_whql\GART\nv_agp.inf,0
E:\My Documents\nForce_5.11_winxp2k_international_whql\Ethernet\nvenetfd.inf,0
E:\ManXPCD\$OEM$\$1\Drivers\04_Sound\CMHiTec.INF,0
E:\ManXPCD\$OEM$\$1\Drivers\05_GPU\CX_27256.inf,0
E:\ManXPCD\$OEM$\$1\Drivers\06_WDM\atixpwdm.inf,0
E:\ManXPCD\$OEM$\$1\Drivers\08_Monitor\VP171s-2.inf,0

[Hotfixes]
E:\UXPCD_Files\ProgramAddonsNETFramework.cab
E:\UXPCD_Files\ProgramAddonsAdobe.cab
E:\UXPCD_Files\ProgramAddonsJava.cab
E:\UXPCD_Files\RVMUpdatePack2.0.0.cab
E:\UXPCD_Files\RVMAddonsWMP10_1.3.cab
E:\UXPCD_Files\UnO_StartupCPL-v1.0_addon.cab
E:\UXPCD_Files\Kel_TweakUI_Addon_v1.1.cab

Fernando 1

Nov 3 2005, 05:14 AM

QUOTE (Mekrel @ Nov 3 2005, 08:54 AM)

Nope, no good

Hi Mekrel,
you have copied the whole content of your SETTINGS.INI with all removed languages into your post (a simple file attachment would have saved a lot of space), but you did not mention at all what happened during the install of the nLited XP CD.
If you want help, you should answer to the followng questions:
1. Is your Raid array "healthy" (look at the second boot screen)?
2. At which part did the installation fail?
3. What happened exactly?
4. Has your Raid array been detected correctly during textmode part of the installation?
Now a few words to the "brandnew" nForce3 driver package 5.11 you have used:
The IDE drivers are exactly the same as within the 5.10 package NVIDIA had published last year. The only new component within the 5.11 package are the ethernet drivers and they have nothing to do with Sata and Raid drivers.
CU
Fernando

dale5605

Nov 3 2005, 05:58 AM

Don't expect the NET framework addon to work either.

Hopefully it will be working soon.

sry for off-topic

Mekrel

Nov 3 2005, 10:28 AM

QUOTE (Fernando 1 @ Nov 3 2005, 12:14 PM)

QUOTE (Mekrel @ Nov 3 2005, 08:54 AM)

Nope, no good

Hi Mekrel,
you have copied the whole content of your SETTINGS.INI with all removed languages into your post (a simple file attachment would have saved a lot of space), but you did not mention at all what happened during the install of the nLited XP CD.
If you want help, you should answer to the followng questions:
1. Is your Raid array "healthy" (look at the second boot screen)?
2. At which part did the installation fail?
3. What happened exactly?
4. Has your Raid array been detected correctly during textmode part of the installation?
Now a few words to the "brandnew" nForce3 driver package 5.11 you have used:
The IDE drivers are exactly the same as within the 5.10 package NVIDIA had published last year. The only new component within the 5.11 package are the ethernet drivers and they have nothing to do with Sata and Raid drivers.
CU
Fernando

Sorry, I will recorrect that in a second

1. Yes my Raid Array is healthy
2. The installtion of windows does not even start, it tells me setup cannot continue as Windows could not find any hard disks
3. Windows loads the drivers, as the Nvidia drivers flash up when its loading the txtmode drivers. Then it says its loading windows, then it tells me that it could not find any hard disks and I can only press F3
4. No, thats the problem it will not detect the raid array although I know the hardware is setup correctly as if I do it via F6 - it works

Well I didnt know it was only the ethernet, I didnt check the 5.10 driver versions but as long as they are WHQL and they fix the net dropping in a few games then its fine

Fernando 1

Nov 3 2005, 11:43 AM

QUOTE (Mekrel @ Nov 3 2005, 06:28 PM)

3. Windows loads the drivers, as the Nvidia drivers flash up when its loading the txtmode drivers. Then it says its loading windows, then it tells me that it could not find any hard disks and I can only press F3
4. No, thats the problem it will not detect the raid array although I know the hardware is setup correctly as if I do it via F6 - it works

Thank you for your post.
New questions:
1. Do you only have 2 hard disk drives? If you have more, what sort (SATA/IDE)?
2. Which sort of controller is used by these hard disk drives (nForce Sata controller or nForce IDE Controller)?
3. Have you enabled these controllers within your BIOS?
3. Did you select both required drivers nLite proposed to integrate as textmode drivers (NVIDIA nForce Storage Controller and NVIDIA RAID CLASS DRIVER)?

Mei

Nov 3 2005, 03:45 PM

My current NVIDIA drivers pack contains :

CODE

This nForce Win2K/XP driver package contains the below components:

* Taken from many original nForce packages by NVIDIA
(SATA_IDE INF was modified from scratch by me)

Audio utility version 4.51
Ethernet NRM driver version 5.09 (WHQL)
Network management tools version 5.09
SMBus driver version 4.50 (WHQL)
Installer version 4.93
Win2K IDE SATARAID driver version 6.22 (WHQL)
Win2K IDE SATA_IDE driver version 6.22 (WHQL)
Win2K RAIDTOOL application version 6.22
WinXP IDE SATARAID driver version 6.22 (WHQL)
WinXP IDE SATA_IDE driver version 6.22 (WHQL)
WinXP RAIDTOOL application version 6.22

* Added from leaked nForce beta packages
Audio driver version 4.64 (WHQL)
GART driver version 4.40 (WHQL)
Memory controller driver version 4.40 (WHQL)

* Added from original ForceWare beta package by NVIDIA
Display driver (ForceWare) version 81.87

I tested it on NVIDIA nForce3 250Gb and NVIDIA nForce4 Ultra. The IDE/Legacy folder is currently not needed, but I think without it PATA RAID couldn't work. The latest Ethernet NRM 50.09 is not included because it doesn't seems to work. Perhaps it works only on nForce 410/430 southbridge.

Fernando 1

Nov 3 2005, 04:00 PM

QUOTE (Mei @ Nov 3 2005, 11:45 PM)

My current NVIDIA drivers pack contains :
.
.
I tested it on NVIDIA nForce3 250Gb and NVIDIA nForce4 Ultra. The IDE/Legacy folder is currently not needed, but I think without it PATA RAID couldn't work.

I don't know exactly what you want to say with your post. Did you succeed with the integration of the nForce SataRaid drivers by using your special mix? Do you have an nForce SataRaid or an nForce PataRaid system?
If you want to help Mekrel, you should explain, what you have done before you integrated the SataRaid drivers. Important may even be, what you have done with the SATA_IDE.INF and where you have got all those different drivers from.

Mekrel

Nov 3 2005, 09:01 PM

QUOTE (Fernando 1 @ Nov 3 2005, 06:43 PM)

QUOTE (Mekrel @ Nov 3 2005, 06:28 PM)

3. Windows loads the drivers, as the Nvidia drivers flash up when its loading the txtmode drivers. Then it says its loading windows, then it tells me that it could not find any hard disks and I can only press F3
4. No, thats the problem it will not detect the raid array although I know the hardware is setup correctly as if I do it via F6 - it works

Thank you for your post.
New questions:
1. Do you only have 2 hard disk drives? If you have more, what sort (SATA/IDE)?
2. Which sort of controller is used by these hard disk drives (nForce Sata controller or nForce IDE Controller)?
3. Have you enabled these controllers within your BIOS?
3. Did you select both required drivers nLite proposed to integrate as textmode drivers (NVIDIA nForce Storage Controller and NVIDIA RAID CLASS DRIVER)?

1. I have 3 Hard drives, and all of them are SATA. The board has 4 SATA ports and I am currently using port 1 for my stoarage drive and ports 3 and 4 for the raid (3 and 4 because they are locked for when I overclock, im at stock at the moment)

2. Well this is one part im alittle confused about, 2 of the ports are the nvidia ones (which I think are ports 1 and 2) and the 2 other ports (3 and 4) are Marvell SATA PHY ports. The weird thing is, Ive never seen any drivers for these SATA ports, so I think they dont need their own drivers and they are covered by the nforce ones.

3. Yes, all my controllers are enabled, but I will go and scan my bios now. They must be enabled for the raid to boot from, but its worth a check.

4. Yes, I selected both the Raid class controller and storage controller, they both have (required) after them

Edit: Still no good, all my bios settings are 100% correct....

Mei

Nov 4 2005, 03:54 AM

I think the best thing is to copy de /IDE/WinXP/sata_ide/nvata.cat to /IDE/WinXP/sataraid/nvatabus.cat

As the nvata.sys and nvatabus.sys seems to be the same file, the WHQL certificate of the former could work for the latter.

http://mei.planet-d.net/nf_ide_622.rar here is my 6.22 IDE folder already "patched" ... If anyone want to test.

Fernando 1

Nov 4 2005, 04:06 AM

QUOTE (Mekrel @ Nov 4 2005, 05:01 AM)

1. I have 3 Hard drives, and all of them are SATA. The board has 4 SATA ports and I am currently using port 1 for my stoarage drive and ports 3 and 4 for the raid (3 and 4 because they are locked for when I overclock, im at stock at the moment)
2. Well this is one part im alittle confused about, 2 of the ports are the nvidia ones (which I think are ports 1 and 2) and the 2 other ports (3 and 4) are Marvell SATA PHY ports. The weird thing is, Ive never seen any drivers for these SATA ports, so I think they dont need their own drivers and they are covered by the nforce ones.

These 2 points seem to be the critical ones. If you really use 2 different Sata Controllers at the same time, you will get trouble.
My suggestion: Unplug your Sata hard disk from Port 1 und try to install the OS only by using the Ports 3 and 4. If you succeed, you can add the third Sata hard disk.
After having googled, I found this:

CODE

Utility Image for nVidia and Marvell SATA RAID for NF3 board under Windows XP.
Remarks:
1. Installation at booting stage is required if you intend to boot from SATA RAID. Please check user's manual for installation.
2. This image is not required if you just take SATA HDDs as non-RAID devices.
3. If you need SATA RAID but don’t take SATA RAID as booting device, please install RAID driver from driver CD under Windows operating system. This utility is not required.

You can find it here:
http://www.dfi.com.tw/Support/Download/dri..._FLAG=A&SITE=US
CU
Fernando

EDIT:

QUOTE (Mei @ Nov 4 2005, 11:54 AM)

I think the best thing is to copy de /IDE/WinXP/sata_ide/nvata.cat to /IDE/WinXP/sataraid/nvatabus.cat
As the nvata.sys and nvatabus.sys seems to be the same file, the WHQL certificate of the former could work for the latter.
http://mei.planet-d.net/nf_ide_622.rar here is my 6.22 IDE folder already "patched" ... If anyone want to test.

Thank you for your help and the download link for your special driver mix, unless I don't think, that the missing WHQL certificate of the NVATABUS.SYS is the reason for Mekrel's problem. My system (nForce4+2xSata2 as Raid0) is working flawlessly without any WHQL-certified NVATABUS.SYS.
Nevertheless answers to the following questions might be interesting for us all:
Is your special driver mix suitable for all nForce chipsets (nForce2, nForce3 and nForce4)?
How is it possible to copy the NVATA.CAT into the NVATABUS.CAT? I have never seen a file named NVATABUS.CAT. (EDIT: Now I have seen this file NVATABUS.CAT within your driver package. The correct name is NVATA.CAT)

Mekrel

Nov 4 2005, 11:17 AM

Well I finally got it to work, but not using nlite although I think that nlite would have worked too.

because it was not clear what was causing it to fail, I always thought it were the XP CD's to I created another using Mass storage devices within winnt.sif which I found a MS guide for on their official site.

I rebooted with the CD, and it would not work

, so I retired for the evening and went to bed. I woke up this morning quite early and watched the Lord Of The Rings trillogy then came onto here and read about unplugging my drive from port 1.

Now, thats an interesting thought. In the past when I have had this working I do need to unplug my storage drive but Windows has always detected the raid when they are both plugged in. The only reason to unplug the one in the past, was windows would tell me that the partition (the raid array) was not suitable for Windows XP (or something to that description, I cannot remember the exact wording).

If I then unplugged the drive, it would let me use the raid array to install windows. So what happened to me this time around was quite weird, but unplugging the first device did work! So thanks

Now, If you want me to remake the CD but using nlite and then unplug the device to see if setup detects my disks, I can.

Thanks

Fernando 1

Nov 4 2005, 11:31 AM

QUOTE (Mekrel @ Nov 4 2005, 07:17 PM)

Well I finally got it to work, but not using nlite although I think that nlite would have worked too.
So what happened to me this time around was quite weird, but unplugging the first device did work! So thanks

Now, If you want me to remake the CD but using nlite and then unplug the device to see if setup detects my disks, I can.
Thanks

Congratulations, that you succeeded at least.
It makes me happy, when I detect the reason for an issue and when I can help somebody else.
If you like, you can repeat the successful install by using nLite. A perfect integration of the nForce SataRaid drivers is not the only advantage of this tool ....
CU
Fernando

Mekrel

Nov 4 2005, 11:39 AM

Well I dont wanna resinstall, but I did use nlite and then did the drivers manually, so I still have all updates added and certain things removed and reg twaks loaded via nlite.

but I will see If I can get it to detect the drives.

Anyway I recieved my 3800 venice today and my DFI SLI-DR Expert is on its way to me too.

caspanis

Nov 5 2005, 10:55 AM

Hi All,

I'm new to nLite and have been trying to install Windows XP on an ASUS A8N-SLI premium system with a RAID0 ( 2 X Seagate SATA drives 80GB) array. This array was set up in the motherboard BOIS and the Nvidia RAID bios. After these actions the two disks are seen as one disk by the motherboard bios.

I have tried using nLite according to the first post in this thread with the following results :
Note: The options selected are :
1) Service pack integration ,
2) Driver integration ,
3) Make ISO image

Also , I am using WHQL version 6.70 of the nvidia nforce drivers.

During the driver integration stage , I get the following message:

"D-Object reference not set to an instance of an object"

Nevertheless, the operation completes successfully but when attempting the install Windows complains about not being able to complete the install because no disks have been found . I am then only given the option to exit with the F3 key.

What causes these attempts to fail in the way they have ?

P.S. The disks are connected to port 1 and 2 of the Nvidia SATA controllers

Please help. Thanks in advance.

Best Regards,
Caspanis

Fernando 1

Nov 5 2005, 11:23 AM

QUOTE (caspanis @ Nov 5 2005, 06:55 PM)

During the driver integration stage , I get the following message:
"D-Object reference not set to an instance of an object"

Which nLite version did you use?

caspanis

Nov 5 2005, 11:55 AM

QUOTE (Fernando 1 @ Nov 5 2005, 12:23 PM)

QUOTE (caspanis @ Nov 5 2005, 06:55 PM)

During the driver integration stage , I get the following message:
"D-Object reference not set to an instance of an object"

Which nLite version did you use?

Hi ,

Firstly, thanks for the quick reply. When I tried this operation , I was using Nlite version 1.0 RC2

Cheers,
Caspanis

Fernando 1

Nov 5 2005, 12:34 PM

QUOTE (caspanis @ Nov 5 2005, 06:55 PM)

During the driver integration stage , I get the following message:
"D-Object reference not set to an instance of an object"

As long as I try to integrate the nForce SataRaid drivers I have never seen such a message.
Within German nLite Forum some users had posted the same thing and the answer was, that it was an issue in earlier nLite versions and should have been gone with RC1.
After having googled I found this discussion about the message you got:
http://www.webdeveloper.com/forum/archive/...hp/t-24691.html
Have you done any changes within TXTSETUP.OEM, TXTSETUP.SIF or WINNT.SIF?
Did you integrate just the content of the LEGACY subfolder as textmode driver or did you something else?

caspanis

Nov 5 2005, 12:45 PM

QUOTE (Fernando 1 @ Nov 5 2005, 01:34 PM)

QUOTE (caspanis @ Nov 5 2005, 06:55 PM)

During the driver integration stage , I get the following message:
"D-Object reference not set to an instance of an object"

As long as I try to integrate the nForce SataRaid drivers I have never seen such a message.
Within German nLite Forum some users had posted the same thing and the answer was, that it was an issue in earlier nLite versions and should have been gone with RC1.
After having googled I found this discussion about the message you got:
http://www.webdeveloper.com/forum/archive/...hp/t-24691.html
Have you done any changes within TXTSETUP.OEM, TXTSETUP.SIF or WINNT.SIF?
Did you integrate just the content of the LEGACY subfolder as textmode driver or did you something else?

Fernando 1,

I also found that at a German nLite forum , possibly itsthe same post.

I have made no changes within TXTSETUP.OEM, TXTSETUP.SIF or WINNT.SIF. All activity is detailed in the paragraph below.

It is curious that you should say this because this occurs when I integrate just the legacy folder as textmode driver only , but after completion , when I try to do install the error of not finding a hard disk comes up then the only option now is to exit with F3 key.

Noticing this I tried integrating the contents of the "sataraid" folder as well as the legacy folder in the hope that the install would be successfull. In all cases the same error occurs during the integration process.

As a additional question do I need to integrate any other folder in the IDE directory other than the "legacy" folder ?

Also after completion , there is a summary screen that details the size of various components at the bottom. In this area I see : Drivers 0.0 MB . I suspect it means that no drivers have been successfully integrated , am I correct ?

Looking forward to your continued help.

Cheers,
Caspanis

Fernando 1

Nov 5 2005, 01:19 PM

QUOTE (caspanis @ Nov 5 2005, 08:45 PM)

Noticing this I tried integrating the contents of the "sataraid" folder as well as the legacy folder in the hope that the install would be successfull. In all cases the same error occurs during the integration process.

If I would not have seen the other new thread in this forum, I would have been helpless.
I just have successfully created a Windows XP CD with integrated nVRaid drivers from the package 6.70 by using nLite 1.0 RC2. What might have been important is, that I have removed all Bus IDE Drivers within the section "Hardware Support".

QUOTE (caspanis @ Nov 5 2005, 08:45 PM)

As a additional question do I need to integrate any other folder in the IDE directory other than the "legacy" folder ?

No!

QUOTE (caspanis @ Nov 5 2005, 08:45 PM)

Also after completion , there is a summary screen that details the size of various components at the bottom. In this area I see : Drivers 0.0 MB . I suspect it means that no drivers have been successfully integrated , am I correct ?

Yes, that is really very suspect.

EDIT: Maybe it is worth to mention, that I already use .NETFramework v. 2.0.

nuhi

Nov 5 2005, 01:48 PM

I just read this fast but
"D-Object reference not set to an instance of an object"
is fixed in just uploaded RC3.
Finally managed to repeat the error...once you see it it's dead

caspanis

Nov 5 2005, 11:23 PM

Hi All,

Just tried to make CD again with the new nLite and it worked without a hitch ! I tried just the SATA RAID drivers with SP2 slipstream. I will now try to integrate other drivers !

P.S. I haven't actually tried an install yet but I am hopeful.

Thanks for all the help !

Cheers,
Caspanis

caspanis

Nov 6 2005, 02:16 AM

Hi All,

INstallation Failed After installer said "Starting Windows ..." I got the BLUE SCREEN OF DEATH with the message : "SESSION3_INITIALIZATION_FAILED"

Don't know what to make of this.

Once again , please help.

Best Regards,
Caspanis

Fernando 1

Nov 6 2005, 02:26 AM

QUOTE (caspanis @ Nov 6 2005, 07:23 AM)

Just tried to make CD again with the new nLite and it worked without a hitch ! I tried just the SATA RAID drivers with SP2 slipstream. I will now try to integrate other drivers !

That is a good message!
Anyhow I would like to know the following:
Which driver package version and which subfolder did you take?
Did you copy any file into that folder before you integrated the driver?

QUOTE (caspanis @ Nov 6 2005, 10:16 AM)

INstallation Failed After installer said "Starting Windows ..." I got the BLUE SCREEN OF DEATH with the message : "SESSION3_INITIALIZATION_FAILED"

I have never seen such message.
What did you change?
My suggestion: Burn a new CD from the Image and lower the burning speed.

Mei

Nov 9 2005, 11:23 AM

QUOTE (Fernando 1 @ Nov 4 2005, 04:06 AM)

Thank you for your help and the download link for your special driver mix, unless I don't think, that the missing WHQL certificate of the NVATABUS.SYS is the reason for Mekrel's problem. My system (nForce4+2xSata2 as Raid0) is working flawlessly without any WHQL-certified NVATABUS.SYS.
Nevertheless answers to the following questions might be interesting for us all:
Is your special driver mix suitable for all nForce chipsets (nForce2, nForce3 and nForce4)?
How is it possible to copy the NVATA.CAT into the NVATABUS.CAT? I have never seen a file named NVATABUS.CAT. (EDIT: Now I have seen this file NVATABUS.CAT within your driver package. The correct name is NVATA.CAT)

For the NVATABUS.CAT I was wrong I thought, I misunderstood how the WHQL certication works. I thought that the .CAT wasn't linked to a file but that a XYZ.CAT was used for the XYZ.SYS file. But NVATA.SYS and NVATABUS.SYS are 100% identical. So if a NVATABUS.CAT had existed it will be the same as NVATA.CAT.

The IDE remix (I've a little updated it since) could work from nF1 to nF4. I've tested it on nF3 250Gb & nF4 Ultra. It seems that the legacy folder can be a problem sometimes. I don't tested it on textmode.