[Fernando 1]

noen, on Jul 20 2005, 11:07 PM, said:

Yes, the installation proces works completely.
It fails AFTER setup has finished (When the gui mode install completes and restarts to begin windows)
It hangs on loading acpitabl.dat, which after doing a lot of googling seems to be caused by loading an incorrect, corrupt or wrong driver set.
Actually I do have a question that isnt clear in your guide.
Yes I am 100% sure using the 6.66 64bit drivers.
I have the sata/pata folders as descrtibed. 
However there is no nvatax64.inf file int he sataraid folder, and there are two copies of the nvatax64.sys folder.
Which do I use, and do I put them all in the same single OEMDIR directory?

1. It is clear, that there is no NVATAX64.INF file in your SATARAID subfolder. That is why you have to take this file from the PATARAID subfolder to put in into the OEMDIR directory.
2. I don't believe, that you have 2 NVATAX64.SYS folders. What you certainly mean is, that you have such a file in both subfolders SATARAID and PATARAID. These 2 files are totally identical.
3. I believe, that your problem has nothing to do with the integration of the Sata Raid drivers, but with the GART drivers. As you should know, systems with nForce3 chipset need a GART driver. This driver is missing in the NVIDIA chipset package 6.66, because it was designed for nForce4 chipsets, which do not need any GART drivers.

My tip for you: Integrate the Sata Raid drivers with nLite 1.0 b4 as textmode drivers and the SMBus drivers from the package 6.66, but integrate additionally the GART drivers from another 64-bit chipset package (for example 6.25).

Good luck!
Fernando

This post has been edited by Fernando 1: 21 July 2005 - 03:41 AM

[Metalljens]

Can someone confirm which is the latest drivers that works with nforce3, 32 - and 64, integrated or not.

I have tried to up date to the new 6.66 32bit but they dont seem to work for me.
and yes im aware that the gart driver dont exist, but i cannot even update the raid controllers manually, the latest that works for me is 6.53, that works like a charm when slipstreaming windows xp with nlite too.

This post has been edited by Metalljens: 21 July 2005 - 10:48 AM

[Fernando 1]

Metalljens, on Jul 21 2005, 05:41 PM, said:

Can someone confirm which is the latest drivers that works with nforce3, 32 - and 64, integrated or not.
I have tried to up date to  the new 6.66 32bit but they dont seem to work for me.
and yes im aware that the gart driver dont exist, but i cannot even update the raid controllers manually, the latest that works for me is 6.53, that works like a charm when slipstreaming windows xp with nlite too.
<{POST_SNAPBACK}>

The situation for nForce3 user is really awfull - you don't have any official and WHQL-certified x64 drivers for your chipset at the moment and the last official 32-bit version is the old package 5.10.
As many users report, the driver package 6.66 (32-bit and 64-bit version) runs without any problems on nForce3 mainboards. The latest driver package version is 7.13.

Maybe you should wait a few days. NVIDIA seems to release a new (unified and certified?) driver within the next days.

P.S.: I would newer update a Raid driver on a running system. It may end with a loss of your Raid array.

This post has been edited by Fernando 1: 21 July 2005 - 11:14 AM

[Metalljens]

Yes, it really is awful.
But what i dont understand is how can some of the nforce4 standalone packages work with nforce3 while others dont?

As i said earlier updating manually wouldnt do it for me.

So i did like this, i copied the nvatabus.inf from pataraid to sataraid just like you said, then i ran the nvidia setup and just chosed to install smbus and ide, when it came to the part of installing the idedrivers, i choose to install the SW drivers it said that the existing files were newer than the ones i was installing, and asked if i wanted to overwrite them, (this is for the nvidia pata and the sata controllers) (the ones i had installed was from the 6.53, and the ones i tried to install are from the 7.13) i answered yes to overwrite them and it worked like a charm.

It seems as though i cant install the ethernet driver from anything newer than the 6.53 drivers, otherwise it just bsod when installing using nvidia setup program.
Havent tried to manually install it yet, it doesnt seem that important either.

Havent tried the audiodrivers though, because i use the realtek ones instead.


So i have now made a driver package with smbus- and idedrivers from 7.13
Ethernet drivers from 6.53 and gart drivers from, well dont remember which was the latest.

This is for Xp32! havent tried to slipstream these drivers yet i will try it soon.
as for Xp64 i shall try the same thing there.

This post has been edited by Metalljens: 21 July 2005 - 12:55 PM

[Fernando 1]

Metalljens, on Jul 21 2005, 07:52 PM, said:

It seems as though i cant install the ethernet driver from anything newer than the 6.53 drivers, otherwise it just bsod when installing using nvidia setup program.
Havent tried to manually install it yet, it doesnt seem that important either.
So i have now made a driver package with smbus- and idedrivers from 7.13
Ethernet drivers from 6.53 and gart drivers from, well dont remember which was the latest.

The mixing of drivers from different packages is no problem, when you try to integrate them with nLite. You only may get difficulties, when you install them by setup.
Here you can find a lot of things about nForce drivers:
http://www.nforcershq.com/forum/latest-dri...-3-vt60240.html

When you try to integrate your driver mix with nLite, I would not integrate any ethernet drivers. As you have written, you have difficulties to find a working driver. It will be easy to install this driver later (may be with the one from the coming nForce version 8.03?)

[Sucka]

Did it exactly as explained and got 2 BSOD's during the install. The problem i had before was a BSOD right when it's supposed to go the the desktop. Glad someone got it to work though

Edit: Got it to run all the way through, same exact problem as with floppy drivers. Instant BSOD before desktop loads. Sorry but no dice on this one folks.

This post has been edited by Sucka: 25 July 2005 - 01:19 AM

[Fernando 1]

@ Sucka:

What kind of hardware do you have (nForce3 or nForce4, Sata Raid or Pata Raid) and which nForce driver version did you use?

[Sucka]

Found working F6 drivers for RAID 0.

http://www.planetamd...hp?download=266

[Sucka]

Fernando:

DFI SLI-D 6/23-2
AMD X2 4400+
2x250 Hitachi 16mb NCQ RAID 0

Followed your guide all the way through and first two installs i got BSOD's and the third it fully installed, but i got that same old BSOD as it goes to desktop i had been getting before. I actually just found working drivers, so i'm all set!

This post has been edited by Sucka: 25 July 2005 - 02:10 AM

[Fernando 1]

Sucka, on Jul 25 2005, 09:04 AM, said:

DFI SLI-D 6/23-2
AMD X2 4400+
2x250 Hitachi 16mb NCQ RAID 0
Followed your guide all the way through and first two installs i got BSOD's and the third it fully installed, but i got that same old BSOD as it goes to desktop i had been getting before. I actually just found working drivers, so i'm all set!

You did not mention your mainboard and chipset, but only the BIOS version. But as I am an owner of a DFI UT Lanparty Ultra-D, I think, that we both have the same chipset (nForce4 Ultra).
It is clear, that you can install Windows XP x64 by F6/floppy method, when you use the NVIDIA chipset driver package 6.56 or older, the problems began with the drivers from version 6.66 and higher.
As I made my tests only with my Sata Raid board, I cannot give you a safe solution for your BSOD problem. It's maybe caused by other hardware (did you turned off all USB devices during setup?).

[Sucka]

Sorry, the SLI-D is an NF4 (all SLI is NF4).

I couldn't even get the drivers from any version to work. It took that specific set to work properly. The BSOD wasn't a hardware issue, but a compatibility issue with x64 and RAID on the NF4.

I'm amazed Microsoft would release this and not know that RAID didn't work?! Not to mention the fact you need to jump through hoops to figure it out.

[Fernando 1]

Sucka, on Jul 25 2005, 11:14 PM, said:

The BSOD wasn't a hardware issue, but a compatibility issue with x64 and RAID on the NF4.
I'm amazed Microsoft would release this and not know that RAID didn't work?! Not to mention the fact you need to jump through hoops to figure it out.

It seems to me, that Microsoft and NVIDIA don't like and don't trust each other. Maybe all our problems will be solved, when NVIDIA will present their first WHQL-certified 64bit SataRaid drivers for all nForce chipsets, that support 64 Bit.

[jarky]

okay I know this thread has gone cold but i need some help. I went through the steps in the first thread exactly and the disk boots up fine and reads my drives as 1 goes through the install reboots and goes through the gui install and reboots. At which point I get a windows load failure with options to boot normal, safe etc. no matter what I choose the computer tries and reboots and takes me right back to that safe boot screen.
please help me out here i'm using nlite v4 most current xp 64drivers but no go. I got no other option but to get this disk to work since I can't get my fdd to post.

[Fernando 1]

jarky, on Aug 3 2005, 09:48 PM, said:

I went through the steps in the first thread exactly and the disk boots up fine and reads my drives as 1 goes through the install reboots and goes through the gui install and reboots.  At which point I get a windows load failure with options to boot normal, safe etc.  no matter what I choose the computer tries and reboots and takes me right back to that safe boot screen.

As I have nearly the same hardware as you (DFI Lanparty NF4 Ultra-D as mainboard and 2 Samsung Sata2 hard disk drives), I am sure, that the [OemInfFiles] method is suitable for your system too.
Please have a look on your bootable CD and check, if you really have
1. a root folder named $OEM$ with a subfolder named $$ and a subsubfolder named OEMDIR,
2. the correct files within the subsubfolder OEMDIR and
3. the exactly correct changes of the WINNT.SIF file
as I described in post No 1.
Only a little mistake can be the reason for the issue you have described.

To help you, I need some more informations:
Did you integrate the files from the nForce SATARAID folder as TEXTMODE drivers?
Did you integrate other drivers than the nForce SataRaid ones? If yes, which drivers did you integrate by nLite?
Which NVIDIA chipset driver version did you use?
Did you disable the Silicon Image Raid controller?
Do you use any other problematic hardware devices?
Did you unplugg all USB devices during installation of the OS?

CU
Fernando

This post has been edited by Fernando 1: 04 August 2005 - 01:54 AM

[jarky]

Quote

Please have a look on your bootable CD and check, if you really have
1. a root folder named $OEM$ with a subfolder named $$ and a subsubfolder named OEMDIR,
2. the correct files within the subsubfolder OEMDIR and
3. the exactly correct changes of the WINNT.SIF file
as I described in post No 1.

Yup it's all right the 3 files you have listed in post 1 are at d:/$OEM$/$$/OEMDIR, I have typed out the new lines in the winnt.sif file at least 10 times I even copied directly from your post a few time just to be sure.

Quote

Did you integrate the files from the nForce SATARAID folder as TEXTMODE drivers?

YEs I did integrate as text mode drivers despite the pop up warning in nlite

Quote

Did you integrate other drivers than the nForce SataRaid ones? If yes, which drivers did you integrate by nLite?

No I didn't do any other drivers just the nvidia driver found in the SATA folder Which actually has nlite integrate 2 drivers

Quote

Which NVIDIA chipset driver version did you use?

6.66 for xp64

Quote

Did you disable the Silicon Image Raid controller?

Hmmm, Disable it? I didnt' know you could disable the SI controller. I never enabled it and have never had anything hooked up there. If it can be disabled I assume i'll find an option somewhere in the bios, I'll hunt for it.

Quote

Do you use any other problematic hardware devices?

My **** 3.5 fdd won't post, which is why i'm doing this.

Quote

Did you unplugg all USB devices during installation of the OS?

Yup the only thing pluged up is the HDs, 1 optic drive, keyboard and monitor

[Fernando 1]

@ jarky:

Did you enable NCQ (for Sata2 hard disk drives)?
Is it possible, that you stress your RAM and CPU too much by overclocking your system (a 64-bit system needs more resources than a 32-bit system)?
What is the reason for your problem with your floppy disk drive?

I think, that you have a problem with your board.
Try to unplug the floppy cable and disable the floppy controller in the BIOS.

[jarky]

I Don't know about ncq i only know how to enable it in windows. My HD are un jumpered straight out of the static bag. so that sata II enabled spead stream disabled, I have speed stream disabled in my bios as well. Should I activate those jumpers and enable in bios, I didn't think that would make a difference.

I don't think it's my oc settings the are not very extreme at this point and I tried reseting to optimum after my last reboot loop and got the same results.
I have A and B drives set to none at this point.
I hope it's not my mobo it would be a b***h to pull my water cooling rig out.

[jarky]

One question since our bios is at least similar. you asked id I had the silicon image controller disabled, where do I find the option to disable this controller. I looked and looked and I'm not seeing it. IN the bios raid menu I have sata 5 - sata 8 disabled, is that what you mean?

[Fernando 1]

jarky, on Aug 5 2005, 12:21 AM, said:

One question since our bios is at least similar.  you asked id I had the silicon image controller disabled,  where do I find the option to disable this controller.  I looked and looked and I'm not seeing it.  IN the bios raid menu I have sata 5 - sata 8 disabled, is that what you mean?

You are right: Our BIOS is nearly similar (I have the new official version 6-23), but our mainboard is different, because you have 2 RAID controllers (NVIDIA and Silicon Image). So there should be a possibility to enable/disable the NVIDIA or Silicon Image Raid controller within the BIOS. But I don't know where, because I don't have the SLI version of the DFI NF4 board.

[dale5605]

SATA 4-7 is the SIL. So disabling those would probably do the trick.