[Fernando 1]

TeamMCS, on Sep 9 2005, 03:19 PM, said:

I'm not 100% with you as... (sorry for being a touch simple)
There's no txtsetup.oem file in the IDE folder (I dont even have a SATA RAID folder?!).
I can do the required modifications once I've created my slipstreamed image but not before. Is that how I should go about it?

Do the following:
1. Take the nForce package 6.66 for WinXPx64 (yes, you can use these drivers for nForce3 systems!)
2. Open the subfolder SATARAID within the path IDE\WinXP.
3. Open the file txtsetup.oem with the editor, go to the section [Files.scsi.BUSDRV] and replace the name nvrdx64.inf by the name nvatax64.inf
4. Store and close the changed file.
5. Now begin to work with nLite
6. Integrate the folder SATARAID from the package 6.66 as TEXTMODE drivers (both drivers which are presented by nLite, should be integrated).
7. Then integrate the other needed nForce3 drivers (SMBus, LAN, Gart etc.), but you have to take these drivers from the package 6.25!
The rest can be done as I explained in the first post of this thread.

If you have any trouble or if something is not clear, please ask. I will try to help you.

Good luck!
Fernando

This post has been edited by Fernando 1: 09 September 2005 - 08:44 AM

[TeamMCS]

Fernando 1, on Sep 9 2005, 02:41 PM, said:

TeamMCS, on Sep 9 2005, 03:19 PM, said:

I'm not 100% with you as... (sorry for being a touch simple)
There's no txtsetup.oem file in the IDE folder (I dont even have a SATA RAID folder?!).
I can do the required modifications once I've created my slipstreamed image but not before. Is that how I should go about it?

Do the following:
1. Take the nForce package 6.66 for WinXPx64 (yes, you can use these drivers for nForce3 systems!)
2. Open the subfolder SATARAID within the path IDE\WinXP.
3. Open the file txtsetup.oem with the editor, go to the section [Files.scsi.BUSDRV] and replace the name nvrdx64.inf by the name nvatax64.inf
4. Store and close the changed file.
5. Now begin to work with nLite
6. Integrate the folder SATARAID from the package 6.66 as TEXTMODE drivers (both drivers which are presented by nLite, should be integrated).
7. Then integrate the other needed nForce3 drivers (SMBus, LAN, Gart etc.), but you have to take these drivers from the package 6.25!
The rest can be done as I explained in the first post of this thread.

If you have any trouble or if something is not clear, please ask. I will try to help you.

Good luck!
Fernando
<{POST_SNAPBACK}>

Thanks very much, do the instructions stay the same whehter or not you are using PATA or SATA?


Just to reiterate: I'm using a PATA RAID 0 system.

Looking at the TXTOEMsetup file within the PATA folder, all the changes have already been made...

This post has been edited by TeamMCS: 09 September 2005 - 09:08 AM

[Fernando 1]

TeamMCS, on Sep 9 2005, 03:59 PM, said:

Thanks very much, do the instructions stay the same whehter or not you are using PATA or SATA?
Just to reiterate: I'm using a PATA RAID 0 system.
Looking at the TXTOEMsetup file within the PATA folder, all the changes have already been made...

I did not know, that you have a PataRaid system.
In this case take the PATARAID subfolder.
As the changes within the txtsetup.oem file were only reported for SataRaid owners, I would propose to let the txtsetup.oem file as it was. So reverse the changes you have made within this file.

[TeamMCS]

Fernando 1, on Sep 9 2005, 03:19 PM, said:

TeamMCS, on Sep 9 2005, 03:59 PM, said:

Thanks very much, do the instructions stay the same whehter or not you are using PATA or SATA?
Just to reiterate: I'm using a PATA RAID 0 system.
Looking at the TXTOEMsetup file within the PATA folder, all the changes have already been made...

I did not know, that you have a PataRaid system.
In this case take the PATARAID subfolder.
As the changes within the txtsetup.oem file were only reported for SataRaid owners, I would propose to let the txtsetup.oem file as it was. So reverse the changes you have made within this file.
<{POST_SNAPBACK}>

hmm, I've already created an Nforce 4 (raid driver) + nforce 3 slipstream disk and it just got stuck in a reboot phase... I'll give it another go and get back to you..


On a related note: Did anyone else using PATA on NF3 see the same problem, could there be a service or driver that I'm installing which could be screwing this up?

[Fernando 1]

TeamMCS, on Sep 9 2005, 05:23 PM, said:

On a related note: Did anyone else using PATA on NF3 see the same problem, could there be a service or driver that I'm installing which could be screwing this up?

There will not be so many people with exactly your system trying to install XP x64.
Try it again with the manipulated textsetup.oem file. Maybe this will work.

[TeamMCS]

I finally gave up on this idea, its just not working. I've gone through an arm load of CDs trying various variations but alas..




Thanks for all your help - and patients.

[Fernando 1]

TeamMCS, on Sep 13 2005, 12:12 PM, said:

I finally gave up on this idea, its just not working. I've gone through an arm load of CDs trying various variations but alas..

I can understand your reaction. It is really frustrating to spend such a long time and at least to be unable to install a correct working OS.

But there is a reason to be optimistic. In the very next future, maybe within the next days, we will get a new version of nLite´with
- full XPx64 support and
- full integration of the nVSataRaid drivers (no "handmade" changes necessary).

Pay attention to this forum within the next days!

CU
Fernando

@ TeamMCS:
The problem for you is to find the best driver combination and TXTSETUP.OEM entries to let the system correctly identify your PataRaid system within the first (TEXTMODE) part of the installation.
If you have a floppy disk drive, you don't need to create and burn a lot of CD's.
Just start booting with your original XPx64 CD and try to integrate different driver combinations via F6 method. When your Raid0 array has been correctly detected (as 1 hard disk drive), then you have gotten the right driver combination suitable for the integration of these drivers into a bootable XP x64 CD by nLite.

This post has been edited by Fernando 1: 13 September 2005 - 06:23 AM

[Fernando 1]

Important information for all users, who want to integrate the nForce Sata/Raid drivers into a bootable XP x64 CD by using nLite:

There is no need any more to take the nLite version Beta4, which had an issue with the installation of the Internet Explorer (32-Bit and 64-Bit).

I found an easy method to integrate the nVRaid drivers by using nLite Beta5.

Look into the first post of this thread!

Cu
Fernando

This post has been edited by Fernando 1: 13 September 2005 - 01:14 PM

[TeamMCS]

Yeah thanks for everything.


How would I update the RAID BIOS?

[Fernando 1]

TeamMCS, on Sep 15 2005, 06:02 PM, said:

How would I update the RAID BIOS?

By updating your mainboard BIOS. The Raid BIOS is a part of it.

[TinTin]

Slipstreaming XP installation worked for me, but my nvRAID RAID0 acted weirdly after the installation.

1) it shown me the desktop once i've logged into the windows, however it takes another 2 minutes for my other desktop components to pop up, e.g. icons & task bar.

2) it was achieving some amazing writing speed but read speed was terrible. It loaded and verified my client data in BF2 2 times slower than a P4 530 PC w/ 80 GB Seagate SATA HDD

3) i can't seem to o/c my machine. I o/c'd that just a little and the system can't boot to windows. Array werent being detected and i had to delete it. After that i can't even slipstream the Windows no more! NOW i can't even format the HDDs..
it says my HDDs are damaged in the XP installations when it failed to format, however i could still format the HDDs w/o a hitch in my P4 530 system..

WTH is going on...




__________________________________________________
my rig: AMD Venice 3500+ | GA-K8N-Pro sli | 2X WD1600JS | 1GB DDR | e-vga 7800GT

This post has been edited by TinTin: 15 September 2005 - 08:29 PM

[Fernando 1]

TinTin, on Sep 16 2005, 03:27 AM, said:

Slipstreaming XP installation worked for me, but my nvRAID RAID0 acted weirdly after the installation.
1) it shown me the desktop once i've logged into the windows, however it takes another 2 minutes for my other desktop components to pop up, e.g. icons & task bar.
2) it was achieving some amazing writing speed but read speed was terrible. It loaded and verified my client data in BF2 2 times slower than a P4 530 PC w/ 80 GB Seagate SATA HDD
3) i can't seem to o/c my machine. I o/c'd that just a little and the system can't boot to windows. Array werent being detected and i had to delete it. After that i can't even slipstream the Windows no more! NOW i can't even format the HDDs..
it says my HDDs are damaged in the XP installations when it failed to format, however i could still format the HDDs w/o a hitch in my P4 530 system..

1) When you install Windows XP or Windows XP x64 on a system with firewire and ethernet ports, it is not unusual, that it takes a few minutes after the last reboot until you can work with your computer. You can prevent this behaviour, if you deactivate all network options (Microsoft Network etc.) of all firewire and LAN ports during the installation.
2) I don't know the reason for your low speed. What shows your Device Manager (everything OK there?)?
3) When you delete your Raid array, you cannot boot anymore, because the system looses the Master Boot Record (MBR). You have either to reconfigure your Raid array or to install a new MBR. If you have a system, which is overclocked to the limit, it might be possible, that you get trouble after the installation of a 64-Bit OS, because it needs some more resources.

If you want help, please answer the following questions:
1. Did you install XP x64 into a seperate partition?
2. Have you formatted this partition, before you installed XP x64?
3. Which NVIDIA driver package did you use?
4. Is your BIOS up-to-date?
5. Are you sure, that your mainboard, your hard disk drives and your RAM don't have any issues?

[TinTin]

First of all thank you for the quick reply

Everything in D.Manager is fine and i was achieving some amazing speed in HDTach. Burst speed was 250MB/s, squential read average around 120MB/s, random access was 13.2 & read speed was 94MB/s. Just that the CPU utilization rate skyrocketed at 8%.

Also i did reconfig the array, but still i can't format the hdds, either in RAID or in single drive mode. But i can do that on the other machine with the same drive.

I had BIOS v. F4 loaded n was installing with NV package for X64, 6.66. So i guess it may be the problem of the MB?

My ram did work fine, it was the corsair VS 1GB CL2.5.

This post has been edited by TinTin: 16 September 2005 - 07:55 AM

[Fernando 1]

TinTin, on Sep 16 2005, 02:52 PM, said:

I had BIOS v. F4 loaded n was installing with NV package for X64, 6.66. So i guess it may be the problem of the MB?

What kind of motherboard do you have? Is it an nForce3 or nForce4 board?
Did you install XP x64 onto a clean, formatted partition?

To verify if your RAM is ok, make a memtest!

[Fernando 1]

The RC1 version of nLite 1.0 has brought some important changes, which make it easier than ever to integrate the x64 nVRaid drivers into a bootable Windows XP x64 Edition CD.

That is the reason why I have just edited the new method within post No 1 of this thread.

CU
Fernando

[stinart]

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?

(Yes i was in the wrong thread Fernando)

[Fernando 1]

stinart, on Oct 7 2005, 02:14 PM, said:

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?

If you use nLite 1.0 RC1, there is no need any more to edit something or to choose "unattended install" etc.
For details look into post No 1 of this thread.
My tip is to take the LEGACY subfolder of the nForce chipset driver package 6.67 for the Textmode Driver integration.
If you still have any troubles, post it here. But without any details about your current system (chipset of your board, Sata or Pata hard disk drives, Bios version etc.) it will not be easy to help.
CU
Fernando

[stinart]

I'd followed the guide from the first page , but it brings the same result:"xxxx.sys not found" in x64 setup screen.

MSI Neo2 k8n platinum(nf3 ultra)
4.82 bios version(i don't think it's the problem)
2x sata disks in raid0

This post has been edited by stinart: 07 October 2005 - 08:19 AM

[Fernando 1]

stinart, on Oct 7 2005, 03:18 PM, said:

I'd followed the guide from the first page , but it brings the same result:"xxxx.sys not found" in x64 setup screen.
MSI Neo2 k8n platinum(nf3 ultra)
4.82 bios version(i don't think it's the problem)
2x sata disks in raid0

The Raid Bios version might be a problem, when you use the 6.67 driver package. New Raid drivers need a new Raid Bios (v. 4.84 or higher).
As you have an nForce3 chipset, I suppose, that you have edited the TXTSETUP.OEM file. This was reported by a user with an nForce3 board, but he used the PATARAID subfolder from the6.66 package. Maybe the TXTSETUP.OEM files are different.

Which chipset driver package and which subfolder did you use?

[stinart]

I used the 6.67 ->ide->legacy driver and i hadn't changed the txtsetup.oem because the nvatax64.inf that you mention to add was already written in the [Files.scsi.BUSDRV] field.I tried 6.25 raid driver too, but again in the x64 setup screen i get a "nvraid.sys not found" error and all stops there.
tnx for your assist.

This post has been edited by stinart: 07 October 2005 - 09:19 AM