Search options (Page 8 of 10)

As know there is a nForce Raid driver pair:
a "System Bus Extender" and a "SCSI Miniport"

In additon Nvidia released old and new driver pairs:
   SCSI Miniport System Bus Extender
old: nvatabus.sys  nvraid.sys
new: nvgts.sys     nvrd32.sys

To make it worse:
HardwareID *_NVRAIDBUS and *NVRAIDBUS are used for old and new drivers.
Hence a *_NVRAIDBUS may refer to a nvraid.sys or nvrd32.sys.

Does a old System Bus Extender nvraid.sys match both old and new SCSI Miniport?
Does a new System Bus Extender nvrd32.sys match both old and new SCSI Miniport?
Or how to concat the same HardwareID to different drivers?

Should be compatible HardwareID *NVRAID20.
This match a new System Bus Extender nvrd32.sys.

DP_MassStorage_wnt5_x86-32_810D.7z set txtsetup.sif

GenNvRaidDisk="nvraid"
*NVRAIDBUS="nvraid"
*NVRAID20="nvraid"
*_NVRAIDBUS="nvraid"

In addition there is another open question.
Does nvgts.sys require PnpInterface=5 at textmode setup?
Compare post
#3  http://forum.driverpacks.net/viewtopic.php?id=2629
#59 http://forum.driverpacks.net/viewtopic. … 03&p=3

@wolfi221268
Can you do some tests to proove or deny ideas?

You can use all DriverPacks at BartPE, as long as you integrate them yourself.
Mass Storage drivers integration is supported for BartPE currently.

@kickarse
Intel offers chipset drivers. These chipset drivers contain IDE part.

Intel IDE drivers are different. They don't add binary files.
*.inf file adds windows default driver: pciiide.sys or intelide.sys.

At windows textmode installation, pciiide.sys or intelide.sys matches hardware too.
No need to add Intel IDE at textmode part.

Strange, can you check again?

ich8ide.inf for compatible-mode:

and http://www.intel.com/Assets/PDF/specupdate/313057.pdf

Compare Post #42 http://forum.driverpacks.net/viewtopic. … 89&p=2

@OverFlow

NVida drivers are the real fun A lot of confusing. It's a driver nightmare.

Even more fun:
I don't own a NVidia chipset, following are assumptions based on user reports.
My assumptions maybe false, they are based on several independend user reports.

Nvidia released different RAID driver pairs:
old: nvatabus.sys and nvraid.sys
new: nvgts.sys and nvrd32.sys
There are nice conflicts.

Nvidia released  old and new driver pack for HardwareID PCI\VEN_10DE&DEV_0054&CC_0104.

Currently there are two error sources:

One is: missing PnpInterface=5 for nvgts.sys at registry
Txtsetup.oem set PnpInterface=5. Hence generic floppy driver use PnpInterface=5.
Most likely this is missing at BartPE and regular windows installation.
Again, this is importand: this goes both to BartPE and regular windows installation.

Setting is required at textmode.
This maybe setupreg.hiv at BartPE and at regular windows installation.
A PEBuilder plugin changes setupreg.hiv.

Another one is RAID configuration:
http://ubcd4win.com/forum/index.php?s=& … mp;p=62208

A major difference: %NVRAID_DESC% HardwareID is different.
old

new

Does BIOS or a driver set HardwareID GenNvRaidDisk or SCSI\*NVIDIA*Raid* ?
Does BIOS version matter?
Does NVidia release working drivers?

Does exist PCI\VEN_10DE&DEV_0054&CC_0104 and SCSI\*NVIDIA*Raid* in real?

I understand:
at HardwareID GenNvRaidDisk use: PCI\VEN_10DE&DEV_0054&CC_0104="nvatabus"
at HardwareID SCSI\*NVIDIA*Raid* use: PCI\VEN_10DE&DEV_0054&CC_0104="nvgts5"
This is not possible at a single txtsetup.sif.
DEV_0054 is a example, there are more DEV_* in quesiton.
A decision has to be taken.

@all
Some more HardwareID list would be nice.
Get devcon.exe http://support.microsoft.com/kb/311272
Open a command prompt and run: devcon.exe hwids *CC_01* *Raid*
Post output. Thanks.

I understand:
There are two departments: one hardware department and another driver department.
Intel driver dosn't support all hardware possibilities. AHCI mode is missing at some hardware. There are no technical reasons, it's about marketing.
A OEM or end user may use AHCI at own risk.

Well, I read some Intel pdf (written by hardware department) and compared 8.05 driverpack (based on driver department).
Thanks to Lancelot for ICH8 link.
 

Therefore missing addon:
[to I1] PCI\VEN_8086&DEV_24D1&CC_0106
[to I2] PCI\VEN_8086&DEV_2651&CC_0106
[to I3] PCI\VEN_8086&DEV_2824&CC_0106
[to I3] PCI\VEN_8086&DEV_2923&CC_0106

and all ICH10

Be aware: settings are not tested.

@OverFlow
I'm aware of two reasons for different driverpack version:
it's nice for testing purposes
dosn't use 2000, XP and 2003 use different drivers sometimes?

And setup dosn't find $OEM$ at root at a multi boot solution.

http://flyakite.msfn.org/unattended.htm

It would be nice, if DP_Install_Tool.cmd search OEM and $OEM$ the same manner, that's parallel to i386 folder.

Bad memory, I edited presetup.cmd too: sourcepath is read from $winnt$.inf.
Again tested at M2 solution only.

Today I tried driver from Post #6 at BartPE: booting fails, incorrect driver.
At second glance: link refers to a 64 bit driver.

There are 32 bit drivers too.
http://www.3ware.com/download/Escalade9 … nstall.zip

I doubt SCSI\Processor_* is required at textmode. Don't include this to ini file.

Slightly offtopic:
Funny txtsetup.oem

[HardwareIds.scsi.AMCC]
id = "PCI\VEN_13C1&DEV_1002","3wareDrv"
id = "PCI\VEN_13C1&DEV_1003","3wareDrv"
id = "PCI\VEN_13C1&DEV_1004","3wareDrv"
id = "PCI\VEN_13C1&DEV_1005","3wareDrv"
id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung

3ware did add HardwareIDs for high capacity floppies too.
Compare http://www.msfn.org/board/Using-a-F6-Dr … 82711.html
http://support.microsoft.com/kb/916196

@Galapo
Yes, actual idea was "to an offline system". Thanks for correcting.
Boot regular windows or PE: add driver and settings to \cmdcons.

How did you installed recovery console?
Did installation CD contain MassStorage Driverpacks?

I'm confused:

HP driver http://h20000.www2.hp.com/bizsupport/Te … ab51adc52c IDE\WinXP\sataraid\nvrd32.inf contains

%NVSTOR_DESC%=Crush11_Inst,PCI\VEN_10DE&DEV_037F&CC_0104

HP nvrd32.inf does NOT contain VEN_10DE&DEV_037E

HP IDE\WinXP\sataraid\txtsetup.oem contains

id = "PCI\VEN_10DE&DEV_036F", "nvgts" ; MCP55 OEM
id = "PCI\VEN_10DE&DEV_037E", "nvgts" ; MCP55 CHANNEL
id = "PCI\VEN_10DE&DEV_037F", "nvgts" ; MCP55 UNUSED

@profp62
Please run 'devcon.exe hwids PCI\CC_01*' and post output.

D\M\N\4IN\NVRAID4IN.inf contain

%MCP55S%=Crush11_Inst,PCI\VEN_10DE&DEV_037E&CC_0104

Does this driver support a Proliant ML115?

@all
nvgt.sys reminds to http://www.911cd.net/forums//index.php? … p;p=144486
At BartPE a additional registry settings is required: PnpInterface=5

Txtsetup.oem contain this registry setting too. Remember F6 floppy txtsetup.oem is the generic solution.
Does driverpacks require this registry setting too?

A PnpInterface search revealed:

http://www.phdcc.com/wdmbook/scsinotes.html

http://www.osronline.com/DDKx/storage/02mnport_0ihz.htm

Nvgts.sys contain string SCSIPORT.SYS. That's file SCSIPORT.SYS is the SCSI port driver.

Expand driverpacks massstorage and run

findstr /M /S "SCSIPORT.SYS" *.sys

There are a lot of files listed. Most drivers does not require a PnpInterface setttings.

Can anybody explain massstorage drivers?
Does exist drivers supporting Plug and Play mode only, but no legacy mode ?
Is nvgts.sys a example?