76 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

In the end there is a Fix_7hdc.vbs
http://www.911cd.net/forums//index.php?showtopic=24245

Main features:
enable existing, but disabled drivers
install new drivers.

Runtime environment:
a PE3, this incluedes a Windows 7 installation DVD.
Default integrated tools like dism.exe are used.
No need to include a addional tool.

This require testing at real hardware.
Dism may install driver from a *.inf file or not.
Compare above [VMware.Mfg] [VMware.Mfg.NTx86] example.

You may use DriverPacks driver.
DP_MassStorage_wnt6-*.7z contain Vista and Windows 7 drivers.
Expand files yourself first.
Use default folders, or select folder at runtime.
default folder:
32 bit running PE use .\x86
64 bit running PE use .\amd64
Be aware, this refer to current running OS, not to offline windows.
If you boot a 32 bit PE and like to fix a 64 bit offline windows, set driver folder at command line.


The last read inf file is used at double HardwareID.
File system is alphabetically sorted at a NTFS partition. Use a NTFS partition.
This should prefer Windows 7 drivers.

@real1elmo
Do you boot a 32 bit PE 3 or a 64 bit PE?
Should I change default driver folder behaviour?

Good luck

Go to forum: Windows 7 Discussion

77 Reply by cdob

(7 replies, posted in Feedback and Support - DriverPacks Base)

Which HWID referst to mass storage controller? Compare OverFlow's signature.

There is no iastor 9.6 added to UBCD4Win.

Congratulations, you've found a new driver conflict.
Do you have spare time and RW media to do some testings?

Next suspects:
MegaINTL
i2omp
iastor
iastor2
iastor3
iastor8
megasr
mraid35x
raidsrc
sptrak

As for testing purposes edit your UBCD4Win\BartPE\I386\txtsetup.sif. Comment one line

[SCSI.Load]
...
;MegaINTL=MegaINTL.SY_,4

Create a new ISO image: select "PE-Builder", "Create &ISO image (F5)" at UBCD4WinBuilder
Do you get BSOD 0x7e still?

Go to forum: Feedback and Support - DriverPacks Base

78 Reply by cdob

(7 replies, posted in Feedback and Support - DriverPacks Base)

dpwul wrote:

Am using UBCD4WIN, the latest Driverpacks Base Program (just downloaded it) and the Mass Storage Drive Pack (latest version).

Name the version ever, latest version may out date the minute you write the sentence.

All went fine, uptil the point where there is a kind of small window about Shell Selection or something.
It takes a few seconds, that disappears and then I get an IASTORn.sy_ error.

BSOD 0x7e reminds to iastor 9.6 at non Intel AHCI hardware.

Which hardware do you use?
Which mass storage controller do you use?

Note: on other occassions it was iastor70.sy_

Read the true error may another driver.
First suspects: all iastorNN.sy_ files. Any other driver is questionable too.
A driver may work at most  hardware, but fail at specific hardware only.

UBCD4Win, DP_MassStorage_wnt5_x86-32_1011.7z, VMware Player 3 does work.

Does it have something to do that the iastorNN.sy_ files not expanded ?

No, compressed files are fine at this level.
Compare a default XP installation media: there are *.sy_ files.

Go to forum: Feedback and Support - DriverPacks Base

79 Reply by cdob

(16 replies, posted in DriverPack Mass Storage)

bonehead_coder wrote:

I can boot from the USB 3.0 port but once it is up, it is like the USB 3.0 port does not exist.

Does this refer to WinPE 3?
That's expected at default drivers. BIOS routines are used to load boot.wim to RAM.
PE boot from RAM disk. There is no USB 3.0 driver required to boot.
And without USB 3.0 drivers, a booted PE can't access USB 3.0 controller.

I build both a BartPE

Add drivers as a PEBuilder plugin. Compare previous link. Other users reported success. 
Be aware, old plugin refers to NEC drivers, not to Renesaes drivers.

and a WinPE 3 version.

This section is about: 'Windows 2000, XP and Server 2003 DriverPacks (wnt5_x86-32)'
Difficult to guess WinPE 3.

My latest try was with the WinPE (32 bit) and adding the MassStorage/Chipset 10.11 packs (via DISM).

There are no USB3.0 drivers at Vista/7 (x86) DriverPacks.
Use dism and include USB3.0 drivers yourself to boot.wim.

I have not tried adding the Chipset pack to BartPE version.

Don't do this.

Go to forum: DriverPack Mass Storage

80 Reply by cdob

(16 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

It's a Bus extender...

Actually it's not a bus extender. Driver inf use 'base'.

Default usbehci and usbhub are loaded at [InputDevicesSupport.Load].

Installation TO USB is a special case, hence the Bus extender.
And more settings are required.
http://www.911cd.net/forums//index.php?showtopic=14181
http://www.ngine.de/article/id/8


It will have to be added to mass storage as a bus extender

The big question: why are USB3.0 required at textmode?

Let's assume installing from a USB CD ROM drive. The manufactuer support this at USB 2.0.
Add USB3.0 support for this case. This includes install from a USB stick too.

Idea: use mass storage default [SCSI.load]. No need to change DriverPacks Base.
Include USB3.0 drivers to DriverPacks MassStorage. Marked as textmode, Base should include drivers by default.
This has to be tested.

Go to forum: DriverPack Mass Storage

81 Reply by cdob

(16 replies, posted in DriverPack Mass Storage)

@bonehead_coder

Can you clarify:
do you like working USB 3.0 drivers at fully installed XP?
do you require working USB 3.0 drivers at textmode part?

Does your BIOS support booting from USB3.0 ports?

How do you install XP?

@mr_smartepants
A ThinkPad W510 BIOS does boot BartPE from USB3.0 ports
http://www.911cd.net/forums//index.php? … p;p=161433

Added:
as for textmode part, I would try (not tested, here no USB3.0 boot BIOS)

[SourceDisksFiles]
nusb3xhc.sys=1,,,,,,,4,0,0
nusb3hub.sys=1,,,,,,,4,0,0

[HardwareIdsDatabase]
PCI\VEN_1033&DEV_0194 = "nusb3xhc"
PCI\VEN_1033&DEV_0194&REV_03 = "nusb3xhc"
PCI\VEN_1033&DEV_0194&REV_04 = "nusb3xhc"
NUSB3\ROOT_HUB30 = "nusb3hub"
NUSB3\CLASS_09 = "nusb3hub"
NUSB3\CLASS_09&SUBCLASS_00&PROT_01 = "nusb3hub"
NUSB3\CLASS_09&SUBCLASS_00&PROT_02 = "nusb3hub"
NUSB3\CLASS_09&SUBCLASS_00&PROT_03 = "nusb3hub"

[BusExtenders.Load]
nusb3xhc = nusb3xhc.sys
nusb3hub = nusb3hub.sys

[BusExtenders]
nusb3xhc = "NEC/Renesas Electronics USB 3.0 Host Controller",files.none,nusb3xhc
nusb3hub = "NEC/Renesas Electronics USB 3.0 Hub",files.none,nusb3hub

Go to forum: DriverPack Mass Storage

82 Reply by cdob

(9 replies, posted in DriverPack Mass Storage)

@ATechGuy
Does this driver match too?  144kb
http://ftp.us.dell.com/SAS-RAID/DELL_MU … 268778.exe


I have some real grumbles about the device I'd be happy to share in private.

What about sharing at Testing section?

Go to forum: DriverPack Mass Storage

83 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

real1elmo wrote:

Scenerio 3 HPxw8400 to HPz800

I booted a Z800:
native supported by Windows 7 64 bit
device: LSI SAS 3000 8 port
HardwareID PCI\VEN_1000&DEV_0058&CC_0100
driver: LSI_SAS.SYS

Do you boot from SAS hard disk?
Driver lsi_sas.sys is installed but disabled.
Open registry, and set service lsi_sas to boot start=0.

However machine is in usage already: hence no testing, reading only.
I'll get deep trouble if I break the machine.


To explore strange new worlds (TM):
Given a 32 bit Windows 7.
Existing disk swapped to a vmscsi hard disk.
Booting result to a BSOD 0x7B.

Add XP driver vmscsi:

dism /image:e:\ /add-driver /driver:F:\x86\scsi\vmscsi.inf /ForceUnsigned

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Found 1 driver package(s) to install.
Installing 1 of 1 - F:\x86\scsi\vmscsi.inf: The driver package was successfully installed.
The operation completed successfully.

However no driver added to Windows 7. And no registry setting is added.

vmscsi.inf adjusted and integrated

[Manufacturer]
;%VMWARE%=VMware.Mfg
%VMWARE%=VMware.Mfg,ntx86

;[VMware.Mfg]
[VMware.Mfg.NTx86]
%DEVICE%=DDInstall,PCI\VEN_104B&DEV_1040

Dism does install driver vmscsi now.
Files are copied to inf, system32\drivers and system32\DriverStore.
Registry is adjusted.

Windows 7 does boot with a XP vmscsi.sys now.

Conclusion:
Dism message "The operation completed successfully." refers to dism rules.
Message is missleading: a driver may be installed, or not installed.
A driver if installed, if a driver exist matching image.
If a driver is missing according to dism rules, no driver is added.

No, I won't support adding XP drivers to windows 7. That's at own risk.
General rule: broken input result broken output.

Go to forum: Windows 7 Discussion

84 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

real1elmo wrote:

Or did your test conclude that dism is capable of changing the start=3.

Test indicates, dism keep start=3 using mshdc.inf. Win7 won't boot from IDE that way.

My vote would be a combination of devcon, dism for the specific drivers, and regedit to set start=3 in a fix_7hdc.

Under construction.

Can you name more real life examples? Which hardware do you use?
Booting 64 bit PE 3.0. Do you repair 32 bit Windows 7 too?
Which mass storage controllers do you use?
Did you add mass storage drivers to PE 3.0? Which ones?
Does your PE contain pnputil.exe?

Go to forum: Windows 7 Discussion

85 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

real1elmo wrote:

Quick question how do I get dism to only load the driver that matches pe devcon results.

Quick answer: a simple question dosn't relate a simple answer.

Did you tried sysprep so far?

Compare HardwareID, search all *.inf files.
Select the most appropiate driver. Create PNP ranking, value date and HardwareID.

Expect some exceptions:
given different hardware versions, a certain *.sys driver matching PNP ranking may fail anyway.
Should not matter today. But what about several years in future?

Read: I've no idea to build a clean, always working solution.
A simple, half broken approach: value HardwareID only.

real1elmo wrote:

The reason it needed no driver was because the drive in the 670 was IDE.
Can DISM do that?

Let's investigate:

Does a Dell 670 use a ICH5 R and driver intelide.sys at IDE mode?

A  Windows 7 install.wim contains serveral mass storage drivers.
At installtation current appropiate drivers are set to boot start=0.
Driver not matching current hardware are set to demand start=3.

E.g. driver intelide is installed, signed and but not loaded at boot.
Booting fails, if you need intelide.sys at boot.
To make windows 7 bootable, open registry and set start=0.
That's a tiny change, no need for a full repair.

Given: booted PE and offline files at D:\Windows with intelide demand start=3

Dism /Image:D:\ /Add-Driver /Driver:D:\Windows\inf\mshdc.inf

Found 1 driver package(s) to install.
Installing 1 of 1 - D:\Windows\inf\mshdc.inf: The driver package was successfully installed.
The operation completed successfully.

Sad, intelide use demand start=3 still.

Dism /Image:D:\ /Add-Driver /Driver:D:\Windows\inf\mshdc.inf /ForceUnsigned
Dism /Image:D:\ /Add-Driver /Driver:D:\Windows\System32\DriverStore\FileRepository\mshdc.inf_x86_neutral_f64b9c35a3a5be81\mshdc.inf /ForceUnsigned

Still demand start.

How to configure boot start=0 using manufacturer or third party tool?

Should I create a fix_7hdc.cmd?
enable installed, but disabled mass storage drivers, e.g. pciide, intelide, msahci
Idea: read current available HardwareID and select driver from CriticalDeviceDatabase
Install addional driverr not supported. Use manufacturer tool dism instead.

Go to forum: Windows 7 Discussion

86 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

real1elmo wrote:

Scenerio 1:
I backup a win7 machine with ghost. The original machine was an HPxw8400 using IASTOR.sys already installed.  I restore the image to an old Dell 670 and try to boot it. BSOD!

Why do you swap hardware?
Why don't you use a universal imaging approach?

real1elmo wrote:

The reason it needed no driver was because the drive in the 670 was IDE.

Yes, Windows 7 is different to XP. IDE driver are available, driver start maybe non boot.
Adjusting driver start enables booting.

Why don't you use sysprep? Sysprep is integrated by default.
This enables IDE drivers too:

\Windows\System32\sysprep\sysprep.exe /oobe /generalize /shutdown

real1elmo wrote:

Can DISM do that?

I don't know, I doubt enabling existing IDE drivers.

If DISM is the way to go can you make a script that adds all the driverpack subfolders for mass storage

Use DISM /recurse http://technet.microsoft.com/en-us/libr … S.10).aspx
You may use DISM against offline image or a offline windows.
It's even possible to boot UBCD4Win and use DISM from a local installed Windows 7 32 bit.

and existing ones in winpe just in case.

Sorry, most likely I won't do this.

Another story:
given a broken motherboard. Windows 7 dosn't boot anymore.
Replace motherboard. Next BSOD 0x7b.
One approach: adjust mass storage drivers offline.

Go to forum: Windows 7 Discussion

87 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

Yes, I'm guilty as for fix_hdc.cmd.
Back then (PE1 and XP) there was no manufacturer tool.

Win 7 contains DISM by default. That's a manufacturer tool.
Why invent the wheel again? Any special reason?

Example: bootet PE and Windows 7 at F:\windows:

Dism /Image:F:\ /Add-Driver /Driver:G:\x64\M\Intel\1

Go to forum: Windows 7 Discussion

88 Reply by cdob

(32 replies, posted in Windows 7 Discussion)

real1elmo wrote:

FIX_HDC looks at the PE3 driver that is running (visible disks) and injects that registry info and driver to the HDD to make it not BSOD.

Which fix_hdc do you use?

Version from UBCD4WIN dosn't looks at running drivers.
There is no support for Win7, especial no support for x64 with signet drivers.

Can't you use dism or a similar application supporting Win7?

Go to forum: Windows 7 Discussion

89 Reply by cdob

(5 replies, posted in DriverPack LAN)

@phlegm
Adjust or replace driver .inf file.
Compare http://forum.driverpacks.net/viewtopic.php?id=4591

Go to forum: DriverPack LAN

90 Reply by cdob

(3 replies, posted in BartPE - UBCD4Win - WinPE)

@ceroni
As far as I know, graphics DriverPacks are not supported at BartPE.

Go to forum: BartPE - UBCD4Win - WinPE

91 Reply by cdob

(6 replies, posted in Universal Imaging)

jschafer wrote:

Does BSOD message mean..
Enabling Boot Logging.

That's not a BSOD 0x7b. Hence not a mass storage BSOD.
Ahcix86 is not the culprit.

Did you disable automatic reboot?

Did I misunderstood this?


If I could inject the amd ahci drivers another way.

Post #9 describe required registry settings
http://www.msfn.org/board/topic/135840- … _p__874231

Go to forum: Universal Imaging

92 Reply by cdob

(6 replies, posted in Universal Imaging)

jschafer wrote:

the laptop boots not to an immedate blue screen.  but it does blue screen after 10secs.

Do you get a BSOD message? Which one?

Go to forum: Universal Imaging

93 Reply by cdob

(22 replies, posted in BartPE - UBCD4Win - WinPE)

A generic low ranking HardwareID PCI\VEN_10DE&CC_0104 is used.
benefit: this match all nvidia RAID controllers.
drawback: this match all nvidia RAID controllers, even not supported ones

And ranking may load a old driver:

nforce 9.35 RAID txtsetup.oem

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_03F6", "nvatabus"

nforce 15.46 RAID txtsetup.oem

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_03F6", "nvgts"

Old and new driver match the same HardwareID.

Given a old motherboard with PCI\VEN_10DE&DEV_03F6:
CriticalDeviceDatase connect PCI\VEN_10DE&DEV_03F6 or PCI\VEN_10DE&DEV_03F6\* to nvatabus.

The same RAID transfered to a new motherboard with the same PCI\VEN_10DE&DEV_03F6:
After above simple fix both drivers are connected at CriticalDeviceDatase.
PCI\VEN_10DE&DEV_03F6* to nvatabus
PCI\VEN_10DE&CC_0104 to nvgts

PCI\VEN_10DE&DEV_03F6* has a higher priority.
Start=0 does load all 4 nvidia storage drivers.

Booting result is unkown.

Current approach should match most cases at real life.
A clean solution requires more work. I like testing results.
A working solution should be possible at all cases.
I'm looking forward to more user requests.

Edited:
Typo 104 106

Go to forum: BartPE - UBCD4Win - WinPE

94 Reply by cdob

(30 replies, posted in DriverPack Mass Storage)

darkspector wrote:

now on a 2540 but they have the same HWID far as I can tell.

HP offers Intel Matrix Storage Manager Driver 8.9.6.1002
http://h20000.www2.hp.com/bizsupport/Te … nvOID=1093
Can you try this driver?

And for testing purposes: try a boot CD.
BSOD 0x7B may relate to USB booting too.

Go to forum: DriverPack Mass Storage

95 Reply by cdob

(22 replies, posted in BartPE - UBCD4Win - WinPE)

urbanriot wrote:

System is now working, life is good, woohoooo!!

Thanks for report.
Always a pleasure to solve a riddle. Especial if half conditions are unknown.

I'm rather curious still: what did we accomplish really?

Rember the two Nvidia driver pairs:
old: nvatabus.sys and nvraid.sys
new: nvgts.sys and nvrd32.sys

There is used new driver pair at new hardware currently.

Unclear:
Does new driver pair support a RAID from old driver pair?

Question:
Does exist files nvatabus.sys and nvraid.sys at old RAID hard disks?

Go to forum: BartPE - UBCD4Win - WinPE

96 Reply by cdob

(22 replies, posted in BartPE - UBCD4Win - WinPE)

Debugger wrote:

Small mistake - not nvata.sys, but nvatabus.sys. nvata.sys is ATA driver.

Thanks Debugger for debugging.

@urbanriot
Boot Windows 7 disc.
Which Nvidia RAID drivers are at hard disk at directory %SystemRoot%\system32\drivers ?

Not tested, no hardware:
Backup existing files.
Copy current driver files nvgts.sys and nvrd32.sys to %SystemRoot%\system32\drivers\

Run fix_nvgts_RAID.cmd at %SystemRoot%\system32\config\

@echo off
rem insert Nvidia nvgts RAID settings to offline registry
rem created by cdob
rem run at directory %SystemRoot%\system32\config\

copy system system.%random%.sav
reg.exe unload HKLM\loaded_SYSTEM >nul 2>&1
reg.exe load HKLM\loaded_SYSTEM SYSTEM 

rem detect CurrentControlSet
for /f "tokens=3" %%a in ('reg.exe query "HKLM\loaded_SYSTEM\Select" /v "Current"') do set /a ControlSet=%%a
set ControlSet=00000%ControlSet%
set ControlSet=ControlSet%ControlSet:~-3%
echo. &echo ControlSet "%ControlSet%" used.

set ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
set CriticalDeviceDatabase=HKLM\loaded_SYSTEM\%ControlSet%\Control\CriticalDeviceDatabase
set Services=HKLM\loaded_SYSTEM\%ControlSet%\Services

echo on
@rem NVIDIA AHCI
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0106" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0106" /f /v "Service" /d "nvgts"
@rem NVIDIA RAID
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0104" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\PCI#VEN_10DE&CC_0104" /f /v "Service" /d "nvgts"

reg.exe add "%Services%\nvgts" /f /v "DisplayName" /d "NVIDIA nForce Serial ATA Driver"
reg.exe add "%Services%\nvgts" /f /v "Group" /d "SCSI miniport"
reg.exe add "%Services%\nvgts" /f /v "ImagePath" /d "system32\drivers\nvgts.sys"
reg.exe add "%Services%\nvgts" /f /t REG_DWORD /v "ErrorControl" /d 1
reg.exe add "%Services%\nvgts" /f /t REG_DWORD /v "Start" /d 0
reg.exe add "%Services%\nvgts" /f /t REG_DWORD /v "Type" /d 1

reg.exe add "%Services%\nvgts\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1


@rem RAID driver
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk________" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk________" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA_______Raid_Disk" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA_______Raid_Disk" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk_20_____" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#NVIDIA__Raid_Disk_20_____" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA____Raid_Disk_20" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\SCSI#__NVIDIA____Raid_Disk_20" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\*_NVRAIDBUS" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\*_NVRAIDBUS" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\*NVRAIDBUS" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\*NVRAIDBUS" /f /v "Service" /d "nvrd32"
reg.exe add "%CriticalDeviceDatabase%\*NVRAID20" /f /v "ClassGUID" /d "%ClassGUID%"
reg.exe add "%CriticalDeviceDatabase%\*NVRAID20" /f /v "Service" /d "nvrd32"

reg.exe add "%Services%\nvrd32" /f /v "DisplayName" /d "NVIDIA nForce RAID Driver"
reg.exe add "%Services%\nvrd32" /f /v "Group" /d "System Bus Extender"
reg.exe add "%Services%\nvrd32" /f /v "ImagePath" /d "system32\drivers\nvrd32.sys"
reg.exe add "%Services%\nvrd32" /f /t REG_DWORD /v "ErrorControl" /d 1
reg.exe add "%Services%\nvrd32" /f /t REG_DWORD /v "Start" /d 0
reg.exe add "%Services%\nvrd32" /f /t REG_DWORD /v "Type" /d 1

reg.exe add "%Services%\nvrd32\Parameters" /f /t REG_DWORD /v "BusType" /d 8

rem pause
reg.exe unload HKLM\loaded_SYSTEM

Go to forum: BartPE - UBCD4Win - WinPE

97 Reply by cdob

(22 replies, posted in BartPE - UBCD4Win - WinPE)

urbanriot wrote:

Unsure of the exact model, sorry, I'm not the one who originally did this. It was obviously nvidia, otherwise I wouldn't be able to read the RAID array from a Windows 7 disc.

Windows 7 CriticlaDeviceDatabase PCI#VEN_10DE&DEV_03F6&CC_0104 is connected to nvstor.
Windows 7 CriticlaDeviceDatabase *_NVRAIDBUS is connected to nvstor.

Nvidia XP drivers used a driver pair nvata.sys and nvraid.sys in the past.
And files nvgts.sys and nvrd32.sys currently.

Asus offers nvgts.sys and nvrd32.sys  too.

Which Windows XP driver relates to Windows 7 nvstor.sys?

urbanriot wrote:

I would be very interested in trying your update! (But as you said, other problem to solve first).  How do obtain it?  I was going to attempt the one in UBCD.

Sorry, it's at localhost so far only. Never tested so far.
Txtsetup.sif is processed to detect a valid driver. Idea: boot PE first and insert current used driver.
Therefore: fix_hdc won't insert a proper driver without a proper txtsetup.sif

F6 USB floppy:
Did you used a PE without nvgts.sys?
Which USB floppy do you use? Does XP txtsetup.sif contain USB floppy HardwareID?
http://support.microsoft.com/kb/916196
http://www.msfn.org/board/topic/82711-u … sb-floppy/

Are you familiar with offline registry?
There is another hint post #1565: http://www.msfn.org/board/topic/51140-i … _p__823780
Boot windows 7.
You have to load offline XP registry, adjust SYSTEM\CurrentControlSet to offline settings, import the registry settings.
Un load registry hive. And copy nvgts.sys and nvrd32.sys to system32\drivers\.

Go to forum: BartPE - UBCD4Win - WinPE

98 Reply by cdob

(30 replies, posted in DriverPack Mass Storage)

darkspector wrote:

I use a WD 320GB passport USB2.0.
It works fine in IDE mode and on previous laptops in AHCI mode.

Do you use USB3.0 or USB2.0 connector at HP 8540p?
Do you use the same USB connetor at IDE and AHCI mode?
No Windows does provide USB3.0 drivers out of the box.

mr_smartepants wrote:

Well I think the Intel RST 9.??6.??0.??1014 that supports your HWID is broken.  I've been playing with the new RST 10.0.0.1046 with great success.

Thanks for the hint.
I got a BSOD 0x7e at non Intel hardware at IDE mode with Intel RST 9.*.
RST 10.0.0.1046 does work fine again, no BSOD 0x7e at IDE mode.

Go to forum: DriverPack Mass Storage

99 Reply by cdob

(30 replies, posted in DriverPack Mass Storage)

darkspector wrote:

I'm having problems booting to Bart PE on HP 8540p via external HDD.

Booting a external HDD does cause BSOD 0x7b too.

Which external HDD do you use?
Which connector do you use? Do you use USB2.0, USB 3.0 or another connector?

Go to forum: DriverPack Mass Storage

100 Reply by cdob

(22 replies, posted in BartPE - UBCD4Win - WinPE)

urbanriot wrote:

The RAID array was built on a completely different board with a different onboard 'controller'

Which different onboard 'controller' did you use?
Did you used nvraid.sys or nvgts.sys at different onboard 'controller'?
Does nvgts.sys read a RAID created by nvraid.sys?

urbanriot wrote:

I need to change the controller information.

Nice a volunteer. I prepared a fix_hdc update years ago, supporting nvgts.
Never tested because of missing hardware.
You have to boot a PE first.

urbanriot wrote:

I'd F6 with USB floppy drive

You may use F6 with USB floppy at UBCD4Win.
Create a new UBCD4Win: don't add mass storage drivers. Boot and load F6 drivers.

urbanriot wrote:

Is there any way to 'integrate' that command into my PE disc?

Either edit setupreg.hiv as suggested. Buit compare file names.

Or add settings as a PEBuilder plugin.
Compare http://forum.driverpacks.net/viewtopic. … 133#p31133
Back then names nvgts, nvgts5 and nvgts6 was added.
You may have to adjust old plugin to current used file name.

Go to forum: BartPE - UBCD4Win - WinPE