Ausgezeichnet! =D

This driver worked!! Now I can see my arrays, AND manage them with the raidtools package from 11.1.0.43!!! This is great! =D

Hey guys,

I have a question, I have an Asus M3N78 PRO motherboard, I created a RAID5 array with 4 disks, set it to bootable, its MediaShield ROM BIOS 10.0.0.31 RPT IDP.
I then proceed to boot Windows Server 2016 Standard, and it doesn't see my disk, no problem that's normal, I just need to load the RAID drivers right? I load the original from Asus website, it recognizes the drivers and loads it but after it's still not showing my disks, I Google and find this forum, tried every link with diferente drivers, all load the inf files as compatible, it loads, but still doens't see my disks.

What can I do to solve this? As Windows server 2016 is based on W10.

How can I check? On the motherboard I got no specific reference, neither on the manual, or the asus description page. None on the BIOS.
Thanks

EDIT: I tried from the first topic:

1. "NForce4 WHQL Driverpacks for Vista/Win7"
1. "Latest nForce Driverpacks for Win7-10"
2. "Special nForce RAID Driverpacks for Win7-10"
3. "Special nForce2-4 LEGACY Driverpacks for Win7-10"

Inside the IDE folder, Win764, sataraid
Or IDE, sataraid

They show up, compatible with the hardware, it loads but then nothing it doesn't see the RAID.

nVidia advertised some chipsets with integrated graphics directly with the model number of the graphics core.

All information taken from wikipedia:
- nForce 400 / GeForce 6000
- nForce 600 / GeForce 7000
- nForce 700 / GeForce 8000

So the chipset "GeForce 8300" is a MCP78 with GeForce 8300 graphics core.

Zitat von Fernando im Beitrag #403

---

I totally agree with you.
What we currently not know is, whether a clean install of the "Creator's Update" onto an nForce RAID array will work. I just have compared the content of the scsidev.inf files v10.0.14393.0 (v1607) and v10.0.15063 (v1703). Both are dated 06/21/2006 and their content is identical.
So it seems to me, that problems are foreseeable.

---

Hi All,
With regards to the "Win10 Update makes nForce RAID arrays unaccessable" and the special "scsidev.inf" procedure for getting it working on Windows 10 etc.... Errrmmmm I was just doing some googling and I found a group who creates updated releases. When I tested quite a recent version - it found my nVidia Array. I was able to format it. It appears to work like it did originally before the "Anniversary Update" issues started :)

The release in question is "Windows 10 X64 8in1 Build 15063.11 v1703 RS2 ENU APR 2017 {Gen2}"

I'll do another install to make sure I am 100% correct and report back... but it actually looks like the issue may have been resolved? Unless its the way they build their images. I wonder if MS have incorporated a fix?

Kind Regards,
Kenny

Zitat von Zelphium im Beitrag #402

---

At this point it seems the best solution is to use the Windows Creators Update, it's due in 4 days (April 11th) and presumably will have the same drivers as the preview of the same build that works on nForce.

---

Zitat von Device Manager RAID/SATA devices:

---

Driver Provider: NVIDIA Corporation
Driver Date: 1/6/2017
Driver Version: 10.6.0.24
Digital Signer: Microsoft Windows

---

I don't need the Windows RAID tool, so I am hopefully good to go, if Sleep/Hibernate still works... :-/

Update: Yup, no issues with sleep and resume.

Hi all,

just to add my experiences with creator's update: it does NOT work with my pc (NVIDIA Nforce 7 afaik) . Setup exited with an error as when installing 1607 last autumn; and starting from DVD is no option because I want to keep my programs and data. But it's not the same error than before; this time installation proceeded until "first boot" and didn't stop in "safe_os" phase. So Zelphium and jwhickman may be right presuming creator's update solves the old driver problem; however I've possibly got an additional specific issue.

volba

EDIT by Fernando: Unneeded fully quoted post removed (to save space)

In post #311 you say

Zitat von Fernando im Beitrag #311

---

To make it as easy for you as possible to create your individually customized Win10 v1607 ISO file, I have prepared and uploaded everything you may need (except the ISO file itself) into my OneDrive folder named "Test files for nForce RAID users".

Here is the link: >Test files for nForce RAID users<This is what you will find there:

1. The MS in-box INF file named scsidev.inf v10.0.14393.0 mod+signed by me (usable with 32bit and 64bit Win10 v1607 Editions)
2. Some especially modified NVIDIA nForce SATARAID drivers, all of them in 2 slightly different variants:
___a) "for mod scsidev" (for being used together with my mod+signed scsidev.inf file for customizing the Win10 v1607 ISO file, the INF files do not contain the word "Array")
___b) "for orig scsidev" (may be used once the OS is successfully installed to prevent later problems during a Windows Update, INF files additionally contain some HardwareIDs of the original MS in-box scsidev.inf file incl. the word "Array")
These are the drivers I am offering:
___32/64 bit nForce SATARAID drivers v9.99.09 mod+signed by me
___32/64 bit nForce SATARAID drivers v10.6.0.23 mod+signed by me
___32/64 bit nForce SATARAID drivers v11.1.0.43 mod+signed by me

---

After announcing Windows 10 prof. Insider Preview Build 16232, actually you can not make a clean install of that Build anymore on the following
Nforce Chipset Mainboards:
Asus Striker 2 Formula
Asus Striker 2 Extreme
Asus Striker 2 NSE
The Computer does not run into the Setup main menu and restarts (reboots) all the time
weather you use a raid array or an ahci drive (does not make a difference)!
And yes... the boot image is okay, because it runs under the XFX Mainboard with Nforce Chipset 780 SLI!
On the following Mainboard it is still possible to make a clean install of Build 16232 or higher (Build 16241)
XFX Mainboard with Nforce 780 SLI Chipset even on raid 0 array drives (modified install.wim and boot.wim with NTLite)...
Tested last Weekend on July the 15th and 16th!
I need a reply if somebody has made the same experience?!?