Question to Jeff
Could the "="=" have nulled that entire driver?

I belive so, yes.  It probably tried to match the = sign as a HWID. lol

which means that it picked up on another hwid from another section...?

are we still in this situation?

Question 1; adapted 805 with ms_2_hwids="=" (with jeff's string) worked.
Q2; 805 with ms_2_hwids=" (with jeff's string) didn't work.
Q3; 809C (which had corrected string, aka Q2, in it) did not work?

Q4; And 805 with the ubcd4win forum workaround works?

Q1: yes
Q2: right
Q3: right
Q4: yes

We have exactly the situation you describe.

Question 1; adapted 805 with ms_2_hwids="=" (with jeff's string) worked.
Q2; 805 with ms_2_hwids=" (with jeff's string) didn't work.
Q3; 809C (which had corrected string, aka Q2, in it) did not work?

Q4; And 805 with the ubcd4win forum workaround works?

So, in other words, I do not often run tests for ubcd4win, and (to be brutally honest) when I don't have the suitable hardware, a test I do on an issue about hardware I don't have it is of little use.

However, you are helping us glue together some facts about nvidia, and any workaround is better than none.
Thanks.

I must now ask that people whom CAN truly test PE and UBCD4WIN on nVidia platforms take a look at what causes the issue, and at this workaround.
I know that we do not cover all nVidia controllers because there is a problem in the INF files.
To explain; when I look at all the downloads I see where some section is duped, but another is not completely duped, so I had to make a choice and completely left out one mass storage driver because I see no other way. We are therefore actually missing a driver.
((I did not dare put its HWID into another.))

OK, big deal?
nVidia once had a few support folders in DriverPack MassStorage, and we added some in the last fourteen months, and frankly, it was a uphill battle since.

from UBCD-Forum I got an advice to create a new INF file.

I have to create following INF with following content::

File: "Device:\UBCD4WinV320\plugin\Drivers\nvgts.inf"

Content:

; PE Builder v3 plug-in INF file

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="Driver: NVIDIA nForce Serial ATA Controller - nvgts addon"
Enable=1

[SetupReg.AddReg]
0x4, "ControlSet001\Services\nvgts\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts5\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts6\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvrd325\Parameters\PnpInterface", "5", 0x1

After rebuild a new UBCD-CD my hdds were shown flawlessly

Does it help a little bit?

I test the 809c-driverPack with a fresh installed UBCD V320.

The result:

My HDDs are NOT displayed!

(Note: The networkadapter get the connect via DHCP and works)

now that is interesting... hmmm

did you try the link to 809c... (above)

Thanks for the detailed expaliation of your process it really helps!!!

Hello OverFlow,

I had tried 809c before. It failed.
I thought you was not really ready with 809c.

That was the reason that I tried the original 805 with your new N5-section WITH a typo correction (the result made me crazy ).

BUT:
Because yesterday I have tried a lot of combinations and I have no protocol to review my doing thoroughly I want to test once more with 809c to be completely sure.

I'll post my result asap.

did you try the link to 809c... (above)

Thanks for the detailed expaliation of your process it really helps!!!

um... it is solved and Jaak is correct there is a typo...

however the typo did not effect the users results... which were positive...

So the correction is a valid fix and the typo can be corrected by the team when implemented...

Hello together,

hm, I don't know how I start my explanation...**confused**

It's NOT solved...

OK, What I have done today:

I take the DriverPack_MassStorage_wnt5_x86-32.ini and correct the typo.
I applied the new driver pack as required.

I build a new ISO and start my PC with the chipset 590SLI.
And...I don't see my hdds (like in my first post).

Did I made a mistake?

To clarify that I install UBCD V3.20 in a new folder.

Test1:
- Unzip the "DP_MassStorage_wnt5_x86-32_805.7z"
- Correct "DriverPack_MassStorage_wnt5_x86-32.ini" like in post #11
- I leave the typo in it (like original)
- I zip the folder according to the description to a file "DP_MassStorage_wnt5_x86-32_806.7z"
- I delete file "DP_MassStorage_wnt5_x86-32_805.7z" from "D:\UBCD4Win\plugin\DriverPacks.net\BASE\DriverPacks"
- I copy "DP_MassStorage_wnt5_x86-32_806.7z" to "D:\UBCD4Win\plugin\DriverPacks.net\BASE\DriverPacks"
- I 'renew' the drivers according to the description
I build the ISO and burn it
==> Starting with CD works ok and I can see all my HDDs

Test2:
I do the same like above (yes, a new installation of UBCD V3.20)
BUT: Now I correct the typo (to "ms_2_hwids="PCI\....")
and build a new ISO.
After burning on CD and restart my PC The HDDs are not displayed !!!

Amazing. Incredible...

The typo HAS an impact to the functionality with nForce590SLI.

So, now you have the ball

however the typo did not effect the users results... which were positive...

So the correction is a valid fix and the typo can be corrected by the team when implemented...
and i think Jaak put a nightly up with the correction...

here http://dev.driverpacks.thesneaky.com/dr … 32_809C.7z

via [v1] commented
[NV-5] original commented and jeff's adaptation included

built on 809A I found in nightlies.
(( I had a "B" test here. on older Via.))

go find it.

hi

the code has an error

ms_2_hwids="="

Hm, but it seems it has no impact on my tests... (because I have no RAID?)

But you are right, it's weird...