[Fernando 1]

azaze1, on Jul 17 2006, 07:29 PM, said:

Should the contents of the $OEM$\$$\OemDir folder contain ONLY inf files from the SATARAID folder, or every file from that folder, or just specific files?

If you are using the OemInfFiles method to enforce the installation of not correctly digitally signed drivers (as the nForce SataRaid ones), you should put all files of the LEGACY subfolder into the OEMDIR folder (although not all of them are really needed). If you have no LEGACY subfolder, you may take the content of the SATARAID subfolder, but you have to add the NVATABUS.INF (from another package) and the files NVCOI.DLL and NVATA.CAT (from the SATA_IDE subfolder).

The OemInfFiles method does only work, when you additionally create a file named WINNT.SIF (situated in the I386 folder) with an OemInfFiles section. This section should look like this:

[OemInfFiles]
OemDriverFlags=1
OemDriverPathName="%SystemRoot%\OemDir"
OemInfName="nvraid.inf","nvatabus.inf"

This post has been edited by Fernando 1: 17 July 2006 - 05:04 PM

[MatthewK_78]

Okay, I've been going crazy trying to figure out why I couldn't get past a STOP 0x0000007B blue screen of death during textmode setup of WinXP SP2-slipstreamed. Wasted several CDs trying different versions of NVRAID, etc.. Finally got ahold of a floppy drive and tried it that way - SAME !@#(% THING. Booted into UBCD4WIN and ran "Windows XP Setup" under Applications thinking that would solve the problem -- still wouldn't boot into the 2nd stage of setup on the drive (system froze).

So I finally figured out what the problem was. I don't usually use a CD/DVD drive in my system, I use an external USB drive bay. Normally this works fine for everything. It even boots into UBCD4WIN. But for whatever reason the WinXP SP2 textmode setup doesn't like it at all. Hooked it up to my IDE port on the motherboard, problem solved.

Or so I thought; you see, I want to have 16k cluster sizes (formatted it in UBCD4WIN). Now I was getting a "Disk read error occurred - Press Ctrl Alt Del to restart" error message when trying to boot to the drive for 2nd stage setup. But guess what, I found a solution to that problem too. Look in this thread (basically you can't use SP2, you have to use SP1 or earlier to install -- there is also an alternative fix by replacing some files): http://forum.abit-us...ead.php?t=63931

I hope this helps someone out there, I've been going nuts over trying to figure this out for the past day or so.

This post has been edited by MatthewK_78: 19 July 2006 - 03:20 AM

[tianchg]

Thanks a lot, it give me a great help for my failure of installation XP

This post has been edited by tianchg: 19 July 2006 - 10:57 PM

[dnihilist]

nm...

This post has been edited by dnihilist: 21 July 2006 - 04:54 AM

[Fernando 1]

dnihilist, on Jul 21 2006, 05:33 AM, said:

nm...

What does that mean? Which language is it?

[Cybertronic]

nm = nevermind

[Fernando 1]

Cybertronic, on Jul 21 2006, 02:30 PM, said:

nm = nevermind

Thanks, with your help I have learned something again today!

[MouseAT]

I followed the instructions for integrating Server 2003 drivers, and it seemed to work and install OK. Unfortunately, for some reason, my IDE DVD-ROM disappeared after install, and wouldn't reappear until I ran the chipset driver install routine. This involved copying an entire CDROM worth of data over to the PC using a USB pen drive.

Now I can work around this issue if necessary, but it's annoying and I'd like to fix it for future reinstalls. Has anyone any idea what went wrong, or how to resolve this?

[Fernando 1]

MouseAT, on Jul 22 2006, 04:12 PM, said:

I followed the instructions for integrating Server 2003 drivers, and it seemed to work and install OK. Unfortunately, for some reason, my IDE DVD-ROM disappeared after install, and wouldn't reappear until I ran the chipset driver install routine. This involved copying an entire CDROM worth of data over to the PC using a USB pen drive.

That was not necessary.
The reason why your IDE DVD-ROM disappeared after the installation of W2k3 was an incompatibility of your IDE device and the nForce Parallel ATA Controller.
There are 2 easy ways to solve the problem.
At first you should look for new firmware of your IDE DVD-ROM device and - if available - flash the new one.
If there is no new firmware or the firmware update does not change anything, you should replace the nForce Parallel ATA Controller by the MS Standard Dual Channel PCI IDE Controller.
Open the device manager and then the section "IDE ATA/ATAPI Controller".
Then do a right click on the nForce4 Parallel ATA Controller and click "update driver software" > "Browse my computer for driver software" > "Let me pick from a list..."
When the option "Show compatible hardware" is enbled you now can see the "Standard Dual Channel PCI-IDE Controller" as fully compatible hardware. Choose it and go ahead > Done.
After the next reboot you will see your IDE DVD-ROM within the device manager.

[MouseAT]

OK, that makes sense. I'll have a look for updated firmware - failing that, I'll try replacing the IDE controller driver next time.

Thanks for the help.

[Cr4z33]

What if I want to use the Microsoft drivers and not the nVidia ones?

I had to restore the default Microsoft ones, because that f***ing Safely Remove Hardware service was continuously plugging/unpluggling my SATA II hard drives - even the C drive !? - and I had to run the Recovery Console twice...

Now
I gave a look at the Microsoft driver details and it lists ATAPI.SYS, PCIIDE.SYS and PCIIDEX.SYS.
Considering these files how can I integrate them so that the Windows XP Professional installation is able to install on my SATA drives without the need of external drivers?
What other file - i.e. .INF, .CAT, etc. are needed for them?

[Fernando 1]

Cr4z33, on Jul 25 2006, 01:45 PM, said:

What if I want to use the Microsoft drivers and not the nVidia ones?
I had to restore the default Microsoft ones, because that f***ing Safely Remove Hardware service was continuously plugging/unpluggling my SATA II hard drives - even the C drive !? - and I had to run the Recovery Console twice...
Now
I gave a look at the Microsoft driver details and it lists ATAPI.SYS, PCIIDE.SYS and PCIIDEX.SYS.
Considering these files how can I integrate them so that the Windows XP Professional installation is able to install on my SATA drives without the need of external drivers?
What other file - i.e. .INF, .CAT, etc. are needed for them?

Although you didn't mention your hardware config, I assume, that you have an nForce4 SataRaid system.

What you mean are the MS Standard P-ATA(=IDE) drivers for the device named "Standard Dual Channel PCI-IDE Controller". These MS drivers are already "in-the-box" with Windows XP. If you want to install them, there is no need for external drivers or files.
It is no problem to replace the "NVIDIA nForce4 Parallel ATA Controller" by the "Standard Dual Channel PCI-IDE Controller":
a ) open the device manager and open the section IDE ATA/ATAPI-Controller
b ) right-click on the NVIDIA nForce4 Parallel ATA Controller and choose the "update driver software" option
c ) within the following 3 windows always choose the lowest option and click "Continue"
d ) when you enable the option "Show compatible Hardware" within the last pop-up window, you can choose the "Standard Dual Channel PCI-IDE Controller" as fully compatible IDE Controller.
e ) after the next reboot you will have the MS Standard P-ATA drivers instead of the nForce P-ATA drivers.

What I don't understand is your "Safely remove hardware" story. Which service was continuously plugging/unpluggling my SATA II hard drives? Can't you just stop/disable this "service"?

This post has been edited by Fernando 1: 25 July 2006 - 06:47 AM

[Cr4z33]

Fernando 1, on Jul 25 2006, 01:38 PM, said:

What I don't understand is your "Safely remove hardware" story. Which service was continuously plugging/unpluggling my SATA II hard drives? Can't you just stop/disable this "service"?

No way, I need that for my USB/Firewire drives.

About the IDE issue I know that, but I also know I have to supply some drivers when Windows installation starts - I am talking about the F6 stuff - otherwise Windows won't detect any SATA / SATA II hard disk.
For some reason the setup doesn't use the Microsoft drivers.

[Fernando 1]

Cr4z33, on Jul 25 2006, 06:17 PM, said:

About the IDE issue I know that, but I also know I have to supply some drivers when Windows installation starts - I am talking about the F6 stuff - otherwise Windows won't detect any SATA / SATA II hard disk.
For some reason the setup doesn't use the Microsoft drivers.

If you have an nForce4 mainboard with the option of using SataRaid and PataRaid ports and if you have created an nForce4 array, you have no chance to install the MS IDE drivers at the beginning or during the OS installation.
The only possibility you have is to replace the NVIDIA P-ATA by the MS IDE drivers (for details see my last post) after the complete installation of the OS.

[Cr4z33]

Fernando 1, on Jul 25 2006, 07:01 PM, said:

The only possibility you have is to replace the NVIDIA P-ATA by the MS IDE drivers (for details see my last post) after the complete installation of the OS.

Exactly what I am doing atm and so will I do then in the future.

[buzzeke]

I had a bluescreen using NLITE today too, (0x0000007b 0xbacc3524). All windows setup was passed, but just before entering Windows it gave me the BSOD.

Anyway, I read most of the posts here for integrating NForce SATARAID drivers and found that my problem was lying with the NForce SATARAID drivers. (I have a new system MSI K9N NEO (Nforce 550 chipset), AMD AM2 - 4600+, Asus 7900GT. I changed my drivers from the ones on the MSI site to the ones on my CDROM I got with the NForce chipset.

What I did was kept the SCSI/RAID drivers in windows (Deleted all other standard drivers, except SCSI/RAID). And used the shipped drivers (found under folder \nVidia\System\MCP55). Slipstreamed again using WXPPRO (int SP2), unattended, made iso with CDIMAGE, booted and no problems anymore.

Hope this helps for some of you

[Fernando 1]

buzzeke, on Jul 27 2006, 04:46 PM, said:

I had a bluescreen using NLITE today too, (0x0000007b 0xbacc3524). All windows setup was passed, but just before entering Windows it gave me the BSOD.
Anyway, I read most of the posts here for integrating NForce SATARAID drivers and found that my problem was lying with the NForce SATARAID drivers. (I have a new system MSI K9N NEO (Nforce 550 chipset), AMD AM2 - 4600+, Asus 7900GT. I changed my drivers from the ones on the MSI site to the ones on my CDROM I got with the NForce chipset.
What I did was kept the SCSI/RAID drivers in windows (Deleted all other standard drivers, except SCSI/RAID). And used the shipped drivers (found under folder \nVidia\System\MCP55). Slipstreamed again using WXPPRO (int SP2), unattended, made iso with CDIMAGE, booted and no problems anymore.

Thank you very much for your troubleshooting report.
It would be very important to know, which nForce IDE driver version you used at least (check the "properties" of the NVRAID.SYS by right-clicking on the file) and which driver subfolder you integrated.

@ all users with an nForce 590/570/550 chipset and an nForce RAID array:

As I cannot test my guide with these new nForce chipsets, I am very interested to get feedback from you.

• Did you succeed with the integration of the nForce SataRaid drivers by using nLite?
  
• Which chipset driver packages did you use?
  
• Did you try to integrate just the SATARAID instead of the LEGACY subfoder? If yes, did the integration succeed?

[the_vandyl]

okay..i followed the latest install guide in this thread, when i got through with the install i rebooted and the windows boot screen popped up real faint and now it reboots infinitely at this same point everytime

the bios info at the bottom of the page says: 07/06/2005-NF-CK804-6A61FD49C-00

IT'S A DFI Lanparty UT NF4 ULTRA-D mobo

i have 4 hitachi 250Gb SATA drives in raid 0+1 and running @3.0gbs

I'm using nLite 1.01 and integrated the following drivers:
NVATABUS.inf
NVRAID.inf

those are the only two things i saw in the window for selection in nLite....the SATARaid and IDE folder contained everything, but it only chose those two things for install

the readme in the nvraid folder states this:

This Win2K/XP nForce (C19/CK804 and C51/CK804) driver package consists of the following components:

Audio Driver (v4.62) "WHQL"
Audio Utility (v4.51)
Ethernet Driver MCP51 (v50.11) "WHQL"
Network Management Tools MCP51 (v50.11)
SMBus Driver (v4.50) "WHQL"
Installer (v5.01)
Win2K IDE Legacy Driver (v5.52)
Win2K IDE SataRAID Driver (v5.52) "WHQL"
Win2K IDE SataIDE Driver (v5.52) "WHQL"
Win2K RAIDTool Application (v5.52)
WinXP IDE Legacy Driver (v5.52)
WinXP IDE SataRAID Driver (v5.52) "WHQL"
WinXP IDE SataIDE Driver (v5.52) "WHQL"
WinXP RAIDTOOL Application (v5.52)


what is going on here and how can i remedy this hellish nightmare...i had similar problems with my last pc

[Fernando 1]

the_vandyl, on Jul 29 2006, 03:40 AM, said:

okay..i followed the latest install guide in this thread, when i got through with the install i rebooted and the windows boot screen popped up real faint and now it reboots infinitely at this same point everytime
the bios info at the bottom of the page says: 07/06/2005-NF-CK804-6A61FD49C-00
IT'S A DFI Lanparty UT NF4 ULTRA-D mobo

As I have exactly the same motherboard, I suppose, that the present BIOS version of your mobo does not support the integration of the new nForce SataRaid drivers.
My advice:
1. Check your nLited XP CD, if you have integrated the correct IDE\WinXP driver subfolder (only the LEGACY works with your board, don't use the SATARAID or SATA_IDE one!). If necessary, create a new nLited XP CD with integrated LEGACY subfolder off the 6.70 or 6.85 chipset driver package as TEXTMODE driver.
2. Download the newest BIOS for your motherboard dated 2006/04/06 (look here: http://us.dfi.com.tw/Support/Download/bios...=A&SITE=US)
3. Flash the new BIOS named NF4LD406.BIN (look into the tutorial for BIOS flashing at http://www.dfi-stree...rum/index.php?)
4. Restore the necessary RAID and SATA entries within your BIOS.
5. Install Windows XP by using the nLited CD. If Windows Setup asks for CAT files, just skip. This has no influence at all for a successful installation.

Good luck!
Fernando

This post has been edited by Fernando 1: 29 July 2006 - 03:55 AM

[the_vandyl]

i have the 704BTA from OCZ Tony, which is better and more stable than the 0406...the 0406 has some good fixes but overclocking isn't supposed to be as nice with it...i'm also wondering if having multiple session log files in the same folder can be causing issues with the CD