Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Integration of nvRaid drivers into XPx64 and W2k3x64

* * * * * 2 votes

  • Please log in to reply
374 replies to this topic

#351
FlorisT

FlorisT
  • Member
  • 4 posts
  • Joined 20-May 07
Ok, i'm pretty desperate right now. Tried everything I could think of, and it still doesn't work. Here's the situation (please don't be afraid to read this amount of text, I tried to give as much info as I could);

Specs:
AMD Athlon 64 3500+
ASUS A8N-SLi Deluxe
2x Kingston ValueRAM 512MB (Dual Channel)
2x Hitachi Deskstar 7K250 250 GB (Raid0, nvRaid)
[2x Samsung SpinPoint T166 500GB (Raid0, Silicon Image, not attached to avoid extra problems)]

Software/drivers:
6.86_nforce_winxp64_international_WHQL
nvRaid version 4.84

Story:
After my previous Windows version (XP Pro 32-bit) had worked pretty good for about a year, I thought it might be a good idea to clean my disks and try Windows Vista. So I did. Had some trouble with Silicon drivers at first, but I got it to work. Although the looks of Vista were good, I hated it because of the change in menuing. So I trew Vista off. Next thing I did was completely formatting my 2 hitachi's, and then trying to install Windows XP Pro 64-bit. Here all the trouble began. At first I had to load the Silicon Image drivers, but NONE of them worked (I've really tried every single driver, at every single website at the net). My PC kept hanging at the point of "Setup cannot copy file: Si3114r.sys" and so on with the rest of the driver files. Pretty desperate and tired of making new floppy's all the time, I searched for another way to get the drivers loaded.
I couldn't find one, but what I read was that I could also use the black SATA-ports at my motherboard, which weren't Silicon Image's ports, but nVidia's. New driver to try!! Again, downloaded all drivers for nVidia raid setup to be found at the net, and again without succes! Same point of hanging, although now with files like "nvRaid.sys". Time for another way.
Then I saw the method with nLite. I gave it a try, and it worked... although not entirely.

Problem:
When I putted the nLite edited Windows XP Pro 64-bit DVD in my PC, it worked very well. My PC didn't hang at a file it couldn't copy, it even completed the Windows installation! I thought my life was useful again, and that I would be soon welcomed by the Windows startup sound, as the PC was rebooting after it's installation. Here my feelings were hurt again. Just before the moment when you see the Windows XP logo at a black background with the loading bar underneath it, a blue screen of death suddenly appeared. Rebooting didn't work, it came again. I even formatted the disks again I tried installing Windows again, but with the same result; a f***ING blue screen!!

*** STOP: 0x0000007B (0xFFFFFADFE480F3C0,0xFFFFFFFFC0000034,0x0000000000000000,0x0000000000000000)

Solutions:
I really don't know what to do anymore. It's just so annoying! Can anybody please help me. Post a reply, send a PM or email. Any help would be grately appreciated! :unsure:


How to remove advertisement from MSFN

#352
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

Problem:
When I putted the nLite edited Windows XP Pro 64-bit DVD in my PC, it worked very well. My PC didn't hang at a file it couldn't copy, it even completed the Windows installation! I thought my life was useful again, and that I would be soon welcomed by the Windows startup sound, as the PC was rebooting after it's installation. Here my feelings were hurt again. Just before the moment when you see the Windows XP logo at a black background with the loading bar underneath it, a blue screen of death suddenly appeared. Rebooting didn't work, it came again. I even formatted the disks again I tried installing Windows again, but with the same result; a f***ING blue screen!!

It is not easy to help you with the BSOD, because this might have hundreds of reasons.
My advice: Check your BIOS settings regarding overclocking and check your RAM sticks with MEMTEST or try to get Vista x64 installed with just 1 RAM stick.

Regarding your previous error messages "Setup cannot copy file xyz" I have an idea:
Is it possible, that you used a modified (not clean) XP x64 CD as source?
Look into the i386 directory of your source CD (not the freshly nLited one). If you find a file named WINNT.SIF, I know the reason why you got the messages "Setup cannot copy file xyz.": The WINNT.SIF file contains the command for an unattended install. If Windows Setup finds a WINNT.SIF file, it is not able to copy the files of the drivers loaded by F6/floppy.
Solution: You have to use a clean (original) XP x64 CD as source.
If you create a bootable XP x64 CD by using a tool like nLite and you choose the "Unattended Install" option, you have to integrate the nForce textmode drivers. The F6/floppy method does not work with the "Unattended Install" option.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#353
FlorisT

FlorisT
  • Member
  • 4 posts
  • Joined 20-May 07

It is not easy to help you with the BSOD, because this might have hundreds of reasons.
My advice: Check your BIOS settings regarding overclocking and check your RAM sticks with MEMTEST or try to get Vista x64 installed with just 1 RAM stick.

Regarding your previous error messages "Setup cannot copy file xyz" I have an idea:
Is it possible, that you used a modified (not clean) XP x64 CD as source?
Look into the i386 directory of your source CD (not the freshly nLited one). If you find a file named WINNT.SIF, I know the reason why you got the messages "Setup cannot copy file xyz.": The WINNT.SIF file contains the command for an unattended install. If Windows Setup finds a WINNT.SIF file, it is not able to copy the files of the drivers loaded by F6/floppy.
Solution: You have to use a clean (original) XP x64 CD as source.
If you create a bootable XP x64 CD by using a tool like nLite and you choose the "Unattended Install" option, you have to integrate the nForce textmode drivers. The F6/floppy method does not work with the "Unattended Install" option.


Thanks for your reply! My RAM is fine, which I can tell because it worked yesterday, before I started formatting. I really need XP, because my ISP (internetprovider) doesn't support Vista yet (kinda weird 'eh?).
What you tell about my XP cd can be correct, because it isn't a clean CD. But when I looked for the WINNT.SIF file, it wasn't to be found. So if it isn't there, my cd should work properly, right? Or is it useful to create a clean DVD and try that?

#354
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

Thanks for your reply! My RAM is fine, which I can tell because it worked yesterday, before I started formatting.

A 64bit OS like XP x64 is more sensitive regarding the RAM timings than a 32bit OS like XP.

What you tell about my XP cd can be correct, because it isn't a clean CD. But when I looked for the WINNT.SIF file, it wasn't to be found. So if it isn't there, my cd should work properly, right? Or is it useful to create a clean DVD and try that?

Yes, you should always take a clean source. I bet, that you will succeed with the installation, when you create a new nLited Cd with integrated nForce SataRaid drivers according my guide (first post).
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#355
FlorisT

FlorisT
  • Member
  • 4 posts
  • Joined 20-May 07

Thanks for your reply! My RAM is fine, which I can tell because it worked yesterday, before I started formatting.

A 64bit OS like XP x64 is more sensitive regarding the RAM timings than a 32bit OS like XP.

What you tell about my XP cd can be correct, because it isn't a clean CD. But when I looked for the WINNT.SIF file, it wasn't to be found. So if it isn't there, my cd should work properly, right? Or is it useful to create a clean DVD and try that?

Yes, you should always take a clean source. I bet, that you will succeed with the installation, when you create a new nLited Cd with integrated nForce SataRaid drivers according my guide (first post).


Ok, I'll give it a go tonight. Thanks, and I'll let you know if it worked. :thumbup

#356
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06
Damnit... I have a (big) problem.

I already had a x86 Windows XP version installed and I decided to give x64 a go, since it was collecting dust on the shelf. Anyways, I used nLite to include the nForce 4 raid drivers, like you said on the first page. So when the CDR was finished burning, I decided to go for it. Anyways; after selecting the partition to install x64 Windows XP version (on Z:) and after installing Windows XP x64 it rebooted and now I am getting a disk read error?!

Also F8 does not work, cause this disk read error keeps popping up?!

Well I am going to redo the cd with nLiteos and hopefully I can make it work again. Cause this is really a problem for me, when I lose my stuff (both company stuff and personal stuff).

Any ideas what may went wrong here?!

Thanks for your input, I will check back later, going to make a new slipstreamed windows xp x64 cd asap...

#357
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06
Okay just to make sure; I added the following drivers:

TXT - BUSDRV SCSIAdapter
TXT - RAIDCLASS SCSIAdapter
PNP - HDC

And the nvidia ethernet and smbus drivers as PNP...

This should be correct right?

#358
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06
Argh....

Again I get the same error:

A disk read error has ocurred.
Please press CTRL+ALT+DEL to reboot.

...damnit.

I really hope I am not screwed here.

Let's go over it one more time;

After preparing the the CDR with nLite, it boots from the CDR without problems and starts the Windows XP X64 installation. I do NOT press F6 and wait for the installation to prepare the files. Then I am presented with all the partitions on the RAID 0 HD's (yes they are all there). Then I select the last partition, since I want Windows XP X64 to be installed on it (in my case the last partition is Z:). Then it starts the installation and all looks well. After a short while it says it want's to reboot the PC, which is fine... But then I get the disk read error for some stupid reason.

I really hope I missed something here... I am pretty sure my HD's are in excellent state and do not have any errors of any kind. So please, please advice here....

I will try to create a new nLite cd (yes, again) using the old Legacy method... Maybe that will work.

#359
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64
@ HHawk:

You mean, that the OS Setup cannot read the CD?
Then you should burn the CD Image again, but with lower speed.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#360
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06
Will all due respect, if you had read my postings (or at least the last one), you would have read the HD's gave the error... Not the CDR. The CDR is fine!

/edit

I have found something, which I am going to try out:

I had this problem installing x64 on a VIARAID 0 setup, asus A8V mobo.
the problem is definately with MS installer writing an invalid bootsector. not bios,etc...
(prehaps there is a workaround with tweaking bios,changing clustersize, but ultimately the problem is still with ms)
ok so this is the only solution that worked for me:
indeed fixboot is the solution BUT
-fixboot from the recoveryconsole of x64b cd(with integrated raiddriver) did not work
-fixboot with partition table doctor did not work(and i ended up losing 10 gb using ptd,not recommended)
Solution:
-after installing x64, the "Disk Read Error Occured" appears
-startup recovery console WITH XP32bit CD!(with integrated raiddriver) use fixboot
-you should now be able to reboot (dont forget put the the x64 cd back) and finish the installation!


I am building my X86 Windows XP cd as we speak, so I can try fixboot like the person above mentioned... HOPEFULLY this wil work... :S

Edited by HHawk, 22 May 2007 - 02:37 PM.


#361
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06
f*** I am screwed, cause that didn't work either... Argh...
And I am just to scared to use the FIXMBR command, cause of the possibility that I lose all my data on the 5 partitions.

...or is FIXMBR save to use on a RAID 0 system with 2 HD's (with several partitions)?

Please advice, cause the only other solution I currently see, is that I hook up another HD, reinstall Windows XP X64 / X86 on that one and backup all my data (which is quite impossible 480 GB or something).

Sigh....

#362
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

And I am just to scared to use the FIXMBR command, cause of the possibility that I lose all my data on the 5 partitions.
...or is FIXMBR save to use on a RAID 0 system with 2 HD's (with several partitions)?

This is absolutely safe, even with a RAID array.
You will just get a new written MBR, no other datas will be touched.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#363
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06
You sure mate?

Cause I already tried to give the command in the Recovery Console and gave me some kind of warning about loss of data, or something similar like that.

Nevermind, I found what I meant:

If an invalid or nonstandard partition table signature is detected, you will be prompted whether you want to continue. If you are not having problems accessing your drives, you should not continue. Writing a new master boot record to your system partition could damage your partition tables and cause your partitions to become inaccessible.


I got prompted to continue. And I really do not like the sound of that last line...
...but you say it's safe?

Let me know, thanks.

#364
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

You sure mate?
Let me know, thanks.

I have often done that without getting any problems.
Store the boot files (boot.ini, ntldr and ntdetect.com) somewhere before you run the fixmbr command.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#365
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06

You sure mate?
Let me know, thanks.

I have often done that without getting any problems.
Store the boot files (boot.ini, ntldr and ntdetect.com) somewhere before you run the fixmbr command.


Thanks for the answer, but I already gave it a go... But alas, when I reboot my PC, that **** message popups again "Disk Read Error"...
...I am now going to install a HD (20 GB) and install Windows XP on it, so I can start backing up stuff (which seems impossible, since I have 480 GB of stuff on my PC). Oh well, if anybody knows a possible solution to my problem, please share it with me...

Thanks so far...

#366
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

Thanks for the answer, but I already gave it a go... But alas, when I reboot my PC, that **** message popups again "Disk Read Error"...
...I am now going to install a HD (20 GB) and install Windows XP on it, so I can start backing up stuff (which seems impossible, since I have 480 GB of stuff on my PC). Oh well, if anybody knows a possible solution to my problem, please share it with me...

Have you already tried the FIXBOOT command?

EDIT: If this doesn't repair your boot sector, you might have a hardware problem (hdd or RAM?).
Another idea: Try to boot off the 32bit Windows XP CD with integrated nForce sataRaid drivers.
When the XP Setup shows you the correct RAID partitions, format the partition, where you tried to install XP x64 and do a fresh install of Windows XP.
Maybe you get a proper MBR this way.

Edited by Fernando 1, 22 May 2007 - 04:23 PM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#367
HHawk

HHawk

    Newbie

  • Member
  • 10 posts
  • Joined 03-March 06

Thanks for the answer, but I already gave it a go... But alas, when I reboot my PC, that **** message popups again "Disk Read Error"...
...I am now going to install a HD (20 GB) and install Windows XP on it, so I can start backing up stuff (which seems impossible, since I have 480 GB of stuff on my PC). Oh well, if anybody knows a possible solution to my problem, please share it with me...

Have you already tried the FIXBOOT command?


Yeah I gave that several times a go...

1. From the Recovery Console from the Windows XP X86 version (after including the raid drivers).
2. From the Recovery Console from the Windows XP X64 version (after including the raid drivers).
3. Same as 1, but after FIXMBR command.

All without succes, but I have another option, which I am going to give a go. I also purchased some time ago Windows Vista X64. So I am going to try installing that and see what happens... Probably the same error again, but I am going to try it anyways.

If that does NOT work, I will have to reinstall Windows XP X64 / X86 on the small HD and start backin up stuff...

I only wish what is causing this... Cause I am going banana's. I already spend over 4 hours trying to fix this... :( :( :(

#368
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

All without succes, but I have another option, which I am going to give a go. I also purchased some time ago Windows Vista X64. So I am going to try installing that and see what happens... Probably the same error again, but I am going to try it anyways.

Are you sure, that you get Vista x64 installed onto your nForce RAID without loading any special nForce SataRaid drivers? Vista x64 is not easy to install because of the lack of really working nForce SataRaid drivers.
Which nForce chipset does your motherboard have?
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#369
FlorisT

FlorisT
  • Member
  • 4 posts
  • Joined 20-May 07
Ok, got my machine running now! Thanks to you, Fernando!! At the and it really was the XP cd that was wrong. Using a clean XP + floppy's did the magic. Still got a lot of problems though, like my internet doesn't work, can't find my extra added harddisks, but that's for another topic, right? Thanks for the help!

#370
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

Ok, got my machine running now! Thanks to you, Fernando!! At the and it really was the XP cd that was wrong. Using a clean XP + floppy's did the magic. Still got a lot of problems though, like my internet doesn't work, can't find my extra added harddisks, but that's for another topic, right? Thanks for the help!

Fine, that you succeeded at least!
CU
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#371
Alpo

Alpo
  • Member
  • 1 posts
  • Joined 10-June 07
My situation. I am not running a 64 Windows Osys, will this help me - as this string is extensive please be specific to my issue and system configuration.

Motherboard: MSI K8N Neo4-f (NEW)
Processor: AMD Athlon X2 3800+ Dual Core (NEW)
Memory: (2) Corsair CMX512-2700C2
Drives: (2) Seagate 160GB 8MB SATA HD (NEW)
Video: ATI Radeon X1650 Pro 512Mb (NEW)
Sound: Sound Blaster Audigy 2ZS
OP Sys: Windows XP Professional Version 2002

I am trying to setup a Raid of my two Seagate Drives on a fresh setup of Windows XP Professional. I setup my motherboard Bios as instructed – The only changes from the Optimized default were to change the Boot Sequence to CD/Floppy/Hard Drive, and to enable the SATA Raid. Upon restart the Bios did detect the Drives and prompted an “F10” to create the Raid array, which went perfectly as described. Upon the next restart the Windows XP Pro CD was detected and the installation began. The first screen prompted for “F6” to install the Raid Drivers. Per provided instruction the two Drivers were installed from the floppy created from the supplied ESI Motherboard CD without issue. The Windows installation continued, the Array was detected and I was prompted to Format the array, which I did. The Format proceeded through completion and the Windows installation re-continued loading various files to a point where I am again prompted for the very same Raid Drivers I installed from floppy earlier after hitting “F6”. This time Windows states it cannot copy the files even though the same Floppy is still in the Drive, the exact screen message reads “Cannot copy the file:nvraid.sys” (nvraid.sys being just one of the drivers loaded earlier, the same prompt appears for each of the drivers). Numerous attempts all end the same.

Work arounds attempted:
• I remove and install the Floppy numerous times.
• I bypass the installation of the Drivers, which does allow for the completion of the Windows file copy process but ends with a Blue Screen of Death eventually.
• The latest Drivers were obtained from the MSI website – no success.
• Per Forum research, the drivers were attempted to be loaded twice, and after the prompt stating windows already had them they were loaded yet again – no success.
• Also per forum research only the first Raid Driver was added without the Storage driver – no success.

I have since successfully loaded my copy of Windows XP Pro without Raid. All components are found to be working status-quo after that installation indicating no Hardware issue.

I have seen numerous discussions on this error searching the web for “cannot copy the file:”, some of which date back years. I cannot believe that Microsoft and Nvidia have not worked together and solved this issue, or that the multitude of knowledge out there has not found a sustained work around for it. As stated there has been some varying but spurious successes using the aforementioned methods, but not for all who have attempted them including myself. These are expensive items whether they be the Operating System or internal components, I expected quality but I now have a system that does not perform as expected.

#372
disintegration

disintegration
  • Member
  • 1 posts
  • Joined 24-August 07
Thanx to Fernando... This definitely works if you follow the instructions in the first post.

tools: m2n sli with Nvidia 570 chipset, 4 320GB Seagate SATA HDDs, XP Pro x64, Vista Home Premium x64, nLite v1.4, winrar, nero.

I had a little trouble getting nlite to streamline sp2 in, so I just added the sataraid subfolder and the ide_raid subfolder as explained in the first post, and I was able to install xp onto a raid 1 set with NO problems, sp2 after the install. I had already installed vista on another mirror, so I just physically disconnected those drives before creating the 2nd mirror and installing xp. Afterward, I reconnected the vista drives and both mirrors showed healthy. I choose an OS by setting the corresponding mirror to bootable in MediaShield. After all hardware was configured, each OS insisted on doing a diskcheck at first boot and now all is working perfectly with no further diskchecks.

I bought XP to run ProTools, and I plan to use a free partition on the vista mirror to record audio to, because Digidesign recommends you don't record to the system drive. But I need to free up space on the vista mirror, so I'm pointing most of my data folders to an empty partition on the xp mirror (69). It seems like a somewhat convoluted way to go about things, but it works.. and I think it's cool.

Edited by disintegration, 24 August 2007 - 08:27 PM.


#373
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

My situation. I am not running a 64 Windows Osys, will this help me - as this string is extensive please be specific to my issue and system configuration.
I am trying to setup a Raid of my two Seagate Drives on a fresh setup of Windows XP Professional. I setup my motherboard Bios as instructed – The only changes from the Optimized default were to change the Boot Sequence to CD/Floppy/Hard Drive, and to enable the SATA Raid. Upon restart the Bios did detect the Drives and prompted an “F10” to create the Raid array, which went perfectly as described. Upon the next restart the Windows XP Pro CD was detected and the installation began. The first screen prompted for “F6” to install the Raid Drivers. Per provided instruction the two Drivers were installed from the floppy created from the supplied ESI Motherboard CD without issue. The Windows installation continued, the Array was detected and I was prompted to Format the array, which I did. The Format proceeded through completion and the Windows installation re-continued loading various files to a point where I am again prompted for the very same Raid Drivers I installed from floppy earlier after hitting “F6”. This time Windows states it cannot copy the files even though the same Floppy is still in the Drive, the exact screen message reads “Cannot copy the file:nvraid.sys” (nvraid.sys being just one of the drivers loaded earlier, the same prompt appears for each of the drivers). Numerous attempts all end the same.

At first I have to beg your pardon for my very late response. Reason: I have not been at home for several weeks and your post disappeared within the nLite forum....
Little side note: This would not have been happened, if you would have posted within this thread, which is the correct one for your problem, because you are not planning to create a bootable CD with the 64bit version of Windows XP.

Now to your problem:
Within my instructions (first posts of both threads for XP 32bit and 64bit) you don't find any advice to hit the F6 button during the OS installation and to load any driver from a floppy disk. Contrary to this I suggest to integrate the nForce SataRaid drivers into the bootable XP CD by using nLite.

If you create a bootable CD by nLite or a similar tool and use the "Unattended Install" option (for example by just editing the user name or the CD key), the Windows Setup routine "forgets" all drivers you will load via F6/floppy while installing the OS. This is a wellknown issue of the Windows Setup routine!
The users have 2 options to prevent this Windows Setup issue:
a ) by booting off a Windows OS CD with integraed TEXTMODE drivers (without hitting F6 during the installation) or
b ) by booting off a Windows OS CD without using any "Unattended Install" modifications (no WINNT.SIF file within the i386 directory of the CD) and using the F6/floppy option.
Unfortunately the latter option leads very often to an endless reboot at the end of the installation. That is why I always recommend to integrate the nForce Sataraid drivers into a bootable OS CD.

Thanx to Fernando... This definitely works if you follow the instructions in the first post.
tools: m2n sli with Nvidia 570 chipset, 4 320GB Seagate SATA HDDs, XP Pro x64, Vista Home Premium x64, nLite v1.4, winrar, nero.
I had a little trouble getting nlite to streamline sp2 in, so I just added the sataraid subfolder and the ide_raid subfolder as explained in the first post, and I was able to install xp onto a raid 1 set with NO problems, sp2 after the install. I had already installed vista on another mirror, so I just physically disconnected those drives before creating the 2nd mirror and installing xp. Afterward, I reconnected the vista drives and both mirrors showed healthy. I choose an OS by setting the corresponding mirror to bootable in MediaShield. After all hardware was configured, each OS insisted on doing a diskcheck at first boot and now all is working perfectly with no further diskchecks.
I bought XP to run ProTools, and I plan to use a free partition on the vista mirror to record audio to, because Digidesign recommends you don't record to the system drive. But I need to free up space on the vista mirror, so I'm pointing most of my data folders to an empty partition on the xp mirror (69). It seems like a somewhat convoluted way to go about things, but it works.. and I think it's cool.

Thanks for your description how you managed to get a perfectly running dual boot system with your nForce Raid array.
This may help other users with similar problems.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#374
Kallin

Kallin
  • Member
  • 2 posts
  • Joined 12-October 07
I'm about to throw my computer out a window :P

First I was unable to get the XP installation going due to the install refusing to read the drivers from the floppy.
I found this here thread and followed the instructions. After burning off a new disc with the drivers integrated windows installed, but now endlessly reboots (the message is displayed so quickly I cannot read it).

My system is the Asus P5N32-E SLI (a 680i chipset). I downloaded the latest 64-bit xp drivers from nVidia, 9.53_nforce_680i_winxp64_english_whql.exe.
I did one disc with just the SATA Raid driver installed in textmode, and I did another with both the Sata Raid in textmode and the other one in pnp. The same problem occurs each time.

Can anyone suggest any further steps?

Thanks.

BTW, here are the details of the drivers I obtained from nvidia:

Ethernet Driver (v60.24) "WHQL"
Network Management Tools (v60.26) "Sedona"
SMBus Driver (v4.57) "WHQL"
Installer (v5.17)
WinXP IDE SataRAID Driver (v6.91) "WHQL"
WinXP IDE SataIDE Driver (v6.91) "WHQL"
WinXP RAIDTOOL Application (v6.91) "Sedona"

And I tried both 1.3.5 and 1.4RC2 of nlite.

#375
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • Joined 03-June 05
  • OS:Windows 7 x64

I found this here thread and followed the instructions. After burning off a new disc with the drivers integrated windows installed, but now endlessly reboots (the message is displayed so quickly I cannot read it).
My system is the Asus P5N32-E SLI (a 680i chipset). I downloaded the latest 64-bit xp drivers from nVidia, 9.53_nforce_680i_winxp64_english_whql.exe.
I did one disc with just the SATA Raid driver installed in textmode, and I did another with both the Sata Raid in textmode and the other one in pnp. The same problem occurs each time.
Can anyone suggest any further steps?

This has probably nothing to do with the nForce IDE drivers.
My suggestions:
1. Check, if you have flashed the latest mainboard BIOS version.
2. Hit F8 while booting and choose the advanced option "don't reboot at system failure". Then you can read the error message, which may help to find the issue reason.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users