Jaak wrote:

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.

Hello all,

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 smile

Does it help a little bit?

concerning my last post:

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)

OverFlow wrote:

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 wink).

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.

OverFlow wrote:

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

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

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 sad (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 wink

Jaak wrote:

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...

Hi all, hi Overflow,

today I have tested your changes thoroughly...

Only a few words: It ... WORKS !  smile

Many many thanks to the 'keyplayer' here in the forum wink

And thank you for your patience during my vacation.

regards
MrMorse

Hello OverFlow,

I am sorry for this long delay...

I have had holidays and are back now.

Because my work I can answer only next weekend.

OverFlow wrote:

and he wont tell us which controller he is using wink

On my MB are two sets of SATA connectors:

1. SATA1-SATA6
These use the "Southbridge: NVIDIA® MCP55PXE Chipset".
My hdds are connected to SATA1, SATA3, SATA5.

2. SATA7 and eSATA
They use the Sil3132-chip.
I have no devices connected there.

OverFlow wrote:

I see a SI 3112 here too...
what controler are you connected to and what mode are you useing
Raid ahci ect...

I use the OnBoard-controller of the mainboard "Abit AN9 32x" (there is only one revision).

The hdds are running in IDE-mode, called "Native IDE" in bios.

I'm appreciated about the quick reply

regards
MM

Hello OverFlow,

Thank you for this polite reception.

Yes, I posted the HWIDs in the UBCD-Forum.

Here they are for the chipset 590:

Mainboard "Abit AN9 32X" chipset nForce590SLI.

Command "devcon.exe hwids *CC_01* *Raid* *CC_02*" gives following result:



ACPI\NVRAIDBUS\3&2411E6FE&0
Name: NVIDIA nForceâ„¢ RAID Class Controller
Hardware ID's:
ACPI\NVRAIDBUS
*NVRAIDBUS
PCI\VEN_1095&DEV_3132&SUBSYS_31321095&REV_01\4&2C6EB151&0&0010
Name: Massenspeichercontroller
Hardware ID's:
PCI\VEN_1095&DEV_3132&SUBSYS_31321095&REV_01
PCI\VEN_1095&DEV_3132&SUBSYS_31321095
PCI\VEN_1095&DEV_3132&CC_018000
PCI\VEN_1095&DEV_3132&CC_0180
Compatible ID's:
PCI\VEN_1095&DEV_3132&REV_01
PCI\VEN_1095&DEV_3132
PCI\VEN_1095&CC_018000
PCI\VEN_1095&CC_0180
PCI\VEN_1095
PCI\CC_018000
PCI\CC_0180
PCI\VEN_10DE&DEV_036E&SUBSYS_1C22147B&REV_A1\3&2411E6FE&0&60
Name: Standard-Zweikanal-PCI-IDE-Controller
Hardware ID's:
PCI\VEN_10DE&DEV_036E&SUBSYS_1C22147B&REV_A1
PCI\VEN_10DE&DEV_036E&SUBSYS_1C22147B
PCI\VEN_10DE&DEV_036E&CC_01018A
PCI\VEN_10DE&DEV_036E&CC_0101
Compatible ID's:
PCI\VEN_10DE&DEV_036E&REV_A1
PCI\VEN_10DE&DEV_036E
PCI\VEN_10DE&CC_01018A
PCI\VEN_10DE&CC_0101
PCI\VEN_10DE
PCI\CC_01018A
PCI\CC_0101
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B&REV_A2\3&2411E6FE&0&68
Name: NVIDIA MCP55 Serial ATA Controller
Hardware ID's:
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B&REV_A2
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B
PCI\VEN_10DE&DEV_037F&CC_010485
PCI\VEN_10DE&DEV_037F&CC_0104
Compatible ID's:
PCI\VEN_10DE&DEV_037F&REV_A2
PCI\VEN_10DE&DEV_037F
PCI\VEN_10DE&CC_010485
PCI\VEN_10DE&CC_0104
PCI\VEN_10DE
PCI\CC_010485
PCI\CC_0104
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B&REV_A2\3&2411E6FE&0&69
Name: NVIDIA MCP55 Serial ATA Controller
Hardware ID's:
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B&REV_A2
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B
PCI\VEN_10DE&DEV_037F&CC_010485
PCI\VEN_10DE&DEV_037F&CC_0104
Compatible ID's:
PCI\VEN_10DE&DEV_037F&REV_A2
PCI\VEN_10DE&DEV_037F
PCI\VEN_10DE&CC_010485
PCI\VEN_10DE&CC_0104
PCI\VEN_10DE
PCI\CC_010485
PCI\CC_0104
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B&REV_A2\3&2411E6FE&0&6A
Name: NVIDIA MCP55 Serial ATA Controller
Hardware ID's:
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B&REV_A2
PCI\VEN_10DE&DEV_037F&SUBSYS_1C22147B
PCI\VEN_10DE&DEV_037F&CC_010485
PCI\VEN_10DE&DEV_037F&CC_0104
Compatible ID's:
PCI\VEN_10DE&DEV_037F&REV_A2
PCI\VEN_10DE&DEV_037F
PCI\VEN_10DE&CC_010485
PCI\VEN_10DE&CC_0104
PCI\VEN_10DE
PCI\CC_010485
PCI\CC_0104
6 matching device(s) found.

Hello,

I'm new here and I cannot find an isue concerning the chipset of the topic.

I use UBCD4Win (http://ubcd4win.com).

UBCD uses your latest 'DriverPack MassStorage'.

The newest release of UBCD is V3.20.
The version before was V3.13.


Now the problem:
When I use UBCD V3.20 my hdds could'nt displayed. They cannot recognize by your newest driver-pack (I think).
The UBCD V3.13 can recognize the hdds.
(What driver-pack is used: I don't know).

Please see the posting in the UBCD-Forum:
http://ubcd4win.com/forum/index.php?sho … 5&st=0

Is this issue known that your newest driver-pack doesn't support the 590SLI chipset?