126 Reply by cdob

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

mr_smartepants wrote:

Added BartPE code to .ini.  All NV* folders are skipped for wxp, w2k3 sources.  NV\ RIS drivers are preferred at the moment for BartPE (requires testing).

Based on previous user reports:
can you edit nvnb5032.inf and disable Nforce 1 and Nforce 2 hardware?
Driver does load, but ping fails.

[Nvidia]
; DisplayName           Section       DeviceID
;%NVENETFD.DeviceDesc%  =  NVENETFD1.NDI,   PCI\VEN_10DE&DEV_01C3
;%NVENETFD.DeviceDesc%  =  NVENETFD1.NDI,   PCI\VEN_10DE&DEV_0066
;%NVENETFD.DeviceDesc%  =  NVENETFD3.NDI,   PCI\VEN_10DE&DEV_0086
;%NVENETFD.DeviceDesc%  =  NVENETFD3.NDI,   PCI\VEN_10DE&DEV_008C

This HardwareIDs are handled by nvrisxp.inf.

In addition e.g. nv5\nvetbus.inf contains PCI\VEN_10DE&DEV_0AB0.
The RIS driver dosn't support this HardwareID.

However both RIS nvnb5032.inf and nv5\nvetbus.inf use a child driver nvnrm.sys.
Of course the same file name, but different versions.
No idea to resolve the conflict so far. Further user testings are required.

Go to forum: BartPE - UBCD4Win - WinPE

127 Reply by cdob

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

OverFlow wrote:

add the RIS driver cdob pointed to by adding it to the  <UBCD4Win>\drivers\ folder and not use DriverPack LAN at all (disable or delete the DriverPack LAN plugin... does that work?

The RIS drivers are a plugin too. They go to <UBCD4Win>\plugin\.
E.g. <UBCD4Win>\plugin\DriverPacks.net\LAN\Nvidia_RIS\

Nvidia did release strange RIS drivers.
The newer release should support old hardware. However driver did load but ping failed.
The plugin includes old and new drivers, plugin adjust *.inf.

Last RIS driver is some years old.
A idea, not tested, no hardware: include RIS driver plugin and the newest non RIS driver (NV9 currently).

Go to forum: BartPE - UBCD4Win - WinPE

128 Reply by cdob

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

NVIDIA Network drivers use child drivers.
Example: nvnetbus.sys load nvnrm.sys
The name nvnrm.sys is encoded in nvnetbus.sys.

NVIDIA Network Resource Manager    nvnrm.sys
NV\nvnrm.sys  1.00.02.06753  857kb
NV1\nvnrm.sys 1.00.00.0442    56kb
NV2\nvnrm.sys 1.00.02.06565  901kb
NV3\nvnrm.sys 1.00.00.0482   256kb
NV4\nvnrm.sys 1.00.02.0652  1134kb
NV5\nvnrm.sys 1.00.02.06024 1079kb
NV6\nvnrm.sys 1.00.02.06764  868kb
NV7\nvnrm.sys 1.00.02.06789  934kb
NV8\nvnrm.sys 1.00.02.06767  920kb
NV9\nvnrm.sys 7.01.01.07108  280kb

Strange, file size goes from 56kb to 1134kb.
Does one nvnrm.sys support some NVIDIA hardware only?

A BartPE CD is read only by default.
There can be one file version only at CD.

LAN 10.03 plugin adds file nvnrm.sys 7.01.01.07108.
I understand, the plugin adds one file nvnrm.sys only. One out of ten at above example.
Does this create a version conflict?

There are much less conflicts at NVIDIA RIS drivers.
http://www.drowaelder.de/
http://www.drowaelder.de/winpe/ubcd4win … RIS-V2.Cab
NVIDIA didn't release new RIS driver the last years.

OverFlow wrote:

The UBCD4win team needs to work on the HWPnP plugin before sound will work reliably

Sound with and without HD Audio can be added. This is a manual task so far.
Add a sound plugin and a sound driver plugin relating to your hardware.

OverFlow wrote:

that is why the sound packs are somewhat disabled .

A plugin integration cause a lot of version conflicts: same file name.
I've no idea to resolve the conflicts.

Import drivers to a running PE is a approach.
This require a writable SystemRoot.
A filter driver can do this at CD. E.g. fbwf from XP Embedded, that's a non distributable file.

Unfortunately DriverImportPE is a commercial application in the meantime.

@ceroni
Try add NV8 only, delete all other NV NIC drivers.

Go to forum: BartPE - UBCD4Win - WinPE

129 Reply by cdob

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

froshcoach wrote:

In fact, I don't know that I even see a HWID for a network device:

DUh - I'm an idiot, it's right there (PCI\VEN_10DE&DEV_0057&SUBSYS_25011565&REV_A3\3&2411E6FE&0&50: Other PCI Bridge Device) but other pci bridge device?

Because this is NOT the network device.
This is a nvidia network BUS. That's a PCI bridge.
The nvidia network device is connected to this BUS device.

A average nvidia network driver use two drivers: a network bus driver and a network device driver.
That's not common and cause difficuties at a PE environment.

The previous mentioned NForceAll-RIS drive is one driver for this two devices. It's from a OEM distributed.
Unfortunately nvidia dosn't release a driver to public.
The RIS driver is some years old and may fail at current hardware or work still.

Go to forum: BartPE - UBCD4Win - WinPE

130 Reply by cdob

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

As known HP NC373i & NC373T uses Broadcom hardware.

Broadcom offers two different drivers: regular windows and RIS/WinPE drivers.
http://www.broadcom.com/support/etherne … remeii.php

HP relaese RIS/WinPE drivers too:
http://h20000.www2.hp.com/bizsupport/Te … taskId=135

The RIS/WinPE drivers are  for: "BartPE - UBCD4Win - WinPE"
The RIS/WinPE drivers should work at regular windows too, but this is not supported.

Go to forum: BartPE - UBCD4Win - WinPE

131 Reply by cdob

(10 replies, posted in Other)

OverFlow wrote:

Registry entries can be added from txtsetup.sif

txtsetup.sif

[HiveInfs.Fresh]
AddReg = hivedef.inf,AddReg
AddReg = hivesys.inf,AddReg

Setup process hivesys.inf at end of textmode and integrate settings to the registry.
Next setup reboot the machine.

However the machine has to boot first. If booting fails, setup won't reach end of textmode.
Adding registry settings to txtsetup.sif only, won't resolve nvgts.sys behaviour.

The setup loader setupldr.bin does read certain files.
Setup read the file setupreg.hiv and map this to HKLM\SYSTEM registry.
As indicated already setup process hivesys.inf at end of textmode and integrate settings to the registry.
At end of textmode setup, the registry contains both: setupreg.hiv and hive*.inf settings.
This settings are saved to %sytemroot%\system32\config\system.
Therefore at first reboot: settings from setupreg.hiv are available still.

NT to XP windows installation, WinPE, BartPE and LiveXP / nativeEx use setupreg.hiv.
Reg.exe can edit this file. Reg.exe is included in XP, but is missing in 2000.
The XP reg.exe works in windows 2000.
The edited setupreg.hiv file works from CD, USB or RAM loaded image.
This approach is tested thoroughly and used already.


To confuse you, there is another approach: don't edit setupreg.hiv but add a file migrate.inf
http://forum.driverpacks.net/viewtopic. … 915#p22915
Curtain settings can be added that way.
Most likely requiere are a migrate.inf and a edited hivesys.inf.
Setup read the file migrate.inf early, before driver loading.
This hasn't been tested at nvgst.sys still.

Overalll I prefer a edited setupreg.hiv, because this is the generic installation approach.

Go to forum: Other

132 Reply by cdob

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

VeeDub wrote:

I resolved the issue with W2K3 and Bart now loads the R194052 driver and I can see the drives attached to the controller. Which is obviously good.

There seems to be no XP drivers available, may be a "custom" version of the controller.

However when I add the driverpack, Bart fails to start, reporting a corrupt driver QL2300.sys

Update storport.sys
http://forum.driverpacks.net/viewtopic.php?id=3590

Go to forum: BartPE - UBCD4Win - WinPE

133 Reply by cdob

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

Well, what about R193679.exe?

However DP_MassStorage_wnt5_x86-32_907r2.7z contain this already.

Go to forum: BartPE - UBCD4Win - WinPE

134 Reply by cdob

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

The R194052 lsi_sas.sys is a storport.sys child device. 2003 provides storport.sys.
The R194052 driver requires 2003 files.


VeeDub wrote:

HWIDs from T310

    Name: SCSI Controller
    Hardware ID's:
        PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028&REV_08

The new T310 hardware requires a new driver.
The SAS 6iR use a LSI controller. Try a LSI SAS driver at XP files.

http://www.lsi.com/storage_home/product … index.html
http://www.lsi.com/cm/License.do?url=ht … ;locale=EN

There is a updated symmpi.sys 1.30.02.00.
DP_MassStorage_wnt5_x86-32_907r2.7z contain older symmpi.sys versions.
As for testing purposes disable the mass storage plugin and add the LSI driver manually.

Go to forum: BartPE - UBCD4Win - WinPE

135 Reply by cdob

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

To clarify:
most chipset drivers contains a *.inf file only. Default windows *.sys drivers are used.
*.inf creates a nice loocking device manager with nice names.

At PE windows setup load default drivers.
Appropiate windows drivers are running for chipset.
However device manager dosn't contain nice names.
Just ignore this a as for a recovery tool.

Strange the BSOD with chipset pack. Technically it's interesting to investigate.
Contrary so far I'm convinced it's not worth the effort.

Yes, don't include chipset DriverPack to UBCD4Win.

Go to forum: BartPE - UBCD4Win - WinPE

136 Reply by cdob

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

@jtroullier
Why do you add Chipset files to a PE?
Is there any special reason?

Go to forum: BartPE - UBCD4Win - WinPE

137 Reply by cdob

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

mgorbi wrote:

File ql2300.sys is corrupted.

Windows 2003 Server Standard Edition

Update storport.sys.
http://forum.driverpacks.net/viewtopic.php?id=3590

Go to forum: Feedback and Support - DriverPacks Base

138 Reply by cdob

(35 replies, posted in DriverPack Mass Storage)

compstuff wrote:

can I use the modified setupreg.hiv and hivesys.inf for all my future slipstreams or is this custom to just this NVidia install?

You may use the edited files at all systems: it's a generic install disks still

Go to forum: DriverPack Mass Storage

139 Reply by cdob

(35 replies, posted in DriverPack Mass Storage)

Thanks for report. Do you use a winnt.sif OemPnPDriversPath still?

Try edit setupreg.hiv and hivesys.inf only.

Go to forum: DriverPack Mass Storage

140 Reply by cdob

(35 replies, posted in DriverPack Mass Storage)

Nvgts.sys does require additional registry settings.
Compare http://forum.driverpacks.net/viewtopic.php?id=3638

Go to forum: DriverPack Mass Storage

141 Reply by cdob

(17 replies, posted in DriverPack Mass Storage)

dumpydooby wrote:

PCI\VEN_104C&DEV_803B

That's a Texas Instruments FlashMedia Controller.
This is not a classic Mass Storage device: used as boot devices.
Does DriverPack MassStorage support this kind of hardware?

Of course, a Intel driver won't support this hardware.

when I install vender's recommended drivers for it, I get a blue screen.

Does the hardware work at all? Did you used this hardware before?

Which BSOD do you get? Did you asked the manufacturer?

Which drivers did you used before?
Which drivers do you use now?

Try other drivers, a example
http://cdgenp01.csd.toshiba.com/content … driver.exe

Go to forum: DriverPack Mass Storage

142 Reply by cdob

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

I've different results: VMware Sever 1.0.5 and UBCD4Win 3.50, that's vmscsi.sys 1.2.0.6
Vmscsi.sys does work, the hard disk is available.

Do you use a BusLogic controller or a LSI Logic controller?

Notepad can create a vmx file.

Go to forum: BartPE - UBCD4Win - WinPE

143 Reply by cdob

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

steje wrote:

- Various VMware Server v1.05 built guest images...

;vmscsi.INF
DriverVer=08/17/2005,1.2.0.4

UBCD4Win v3.50 used vmscsy.sys v1.2.0.6. Strange this driver dosn't work in VMware Server v1.05 ?

steje wrote:

1.)  Is there "something to do" to get the "VMSCSI_SY_" driver included in the driverpack to actually work and load when booting a v3.50 ISO from a VMware guest image?

The "VMSCSI_SY_" 1.2.0.6 driver does work in VMware Player 2.5. There is nothing special to do.
I prefer VMware Player nice config GUI: a ini file smile

steje wrote:

2.)  Is there some process by which I can keep using the driverpack for everything that IS working, but SEPARATELY add the older vmscsi files that used to work under the Drivers\SCSIAdapter folder in some other manner

To clarify: Drivers\SCSIAdapter is supported still.
However mixing with other drivers may get unexpected results.
Therefore disable other mass storage drivers, use Drivers\SCSIAdapter only.

To downgrade one driver and using the driverpack plugin:
Compress vmscsy.sys: makecab.exe vmscsi.sys
Overwrite file UBCD4WinV350\plugin\DriverPacks.net\MassStorage\wnt5\VMSCSI_SY_

Go to forum: BartPE - UBCD4Win - WinPE

144 Reply by cdob

(19 replies, posted in DriverPack Mass Storage)

mindwarper wrote:

And guess what, that actually still works fine, when using F6 method though
That was what cdob wanted to know, isn't it?

Yes, this answers the question: does 3wDrv100.sys require PnpInterface? No, PnpInterface is not required. 
There is no need to add PnpInterface to setupreg.hiv, migrate.inf or hivesys.inf.

There has to be another reason. Next suspect is a driver conflict.
Different 3Ware driver may interfere.
Load order maybe importand: first loaded 3wareDrv.SYS may initialize the controller, later loaded 3wDrv100.sys dosn't connect to hardware anymore.

Edit mass storage ini, delete other 3Ware drivers, keep 3wDrv100.sys section [3C].

Go to forum: DriverPack Mass Storage

145 Reply by cdob

(19 replies, posted in DriverPack Mass Storage)

Can you do some addional testing?

3wDrv100.sys is a scsiport.sys child driver.

mindwarper wrote:

Here's the TXTSETUP.OEM info

value = Parameters\PnpInterface,5,REG_DWORD,1

Delete this line.
Does F6 floppy works still?

Go to forum: DriverPack Mass Storage

146 Reply by cdob

(19 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

in some cases the order in which the packs INI entries appear plays a factor...

Thank's for the hint.

Given: ICH7-M AHCI : PCI\VEN_8086&DEV_27C5&CC_0106

Booting UBCD4Win result:
textmode does work
gui is loaded
Next: BSOD 0x7E iastor89.sy_

txtsetup.sif

[HardwareIdsDatabase]
...
PCI\VEN_8086&DEV_27C5&SUBSYS_0F101179="KR10N"
PCI\VEN_8086&DEV_27C5&CC_0106="iastor89"

[SCSI.Load]
...
KR10N=KR10N.SY_,4
jraid=jraid.SY_,4
iteraid=iteraid.SY_,4
inic162x=inic162x.SY_,4
iastor89=iastor89.SY_,4
iastor78=iastor78.SY_,4
iastor70=iastor70.SY_,4
iastor55=iastor55.SY_,4

Load order changed

[SCSI.Load]
...
iastor89=iastor89.SY_,4
iastor78=iastor78.SY_,4
iastor70=iastor70.SY_,4
iastor55=iastor55.SY_,4
KR10N=KR10N.SY_,4

UBCD4Win does boot fully.

This approach may fail at hardware PCI\VEN_8086&DEV_27C5&SUBSYS_0F101179="KR10N"
No hardware to test.



As for S3000AH mbd at RAID mode:

Hardware ID's:
        PCI\VEN_8086&DEV_27C3&SUBSYS_348E8086&REV_01
        PCI\VEN_8086&DEV_27C3&SUBSYS_348E8086
        PCI\VEN_8086&DEV_27C3&CC_010400
        PCI\VEN_8086&DEV_27C3&CC_0104

Txtsetup.sif dosn't contain PCI\VEN_8086&DEV_27C3&SUBSYS_348E8086, therefore PCI\VEN_8086&DEV_27C3&CC_0104 does match.

PCI\VEN_8086&DEV_27c3 does match:
PCI\VEN_8086&DEV_27c3&SUBSYS_83521033="megasr"
PCI\VEN_8086&DEV_27c3&SUBSYS_34698086="MegaINTL"
PCI\VEN_8086&DEV_27C3&CC_0104="iastor89"


@VeeDub
Try a changed load order, txtsetup.sif

[SCSI.Load]
...
iastor89=iastor89.SY_,4
iastor78=iastor78.SY_,4
iastor70=iastor70.SY_,4
iastor55=iastor55.SY_,4
megasr=megasr.SY_,4
MegaINTL=MegaINTL.SY_,4
MegaIDE=MegaIDE.SY_,4
KR10N=KR10N.SY_,4

Or delete meagsr and MegaINTL lines.

Go to forum: DriverPack Mass Storage

147 Reply by cdob

(24 replies, posted in DriverPack Mass Storage)

azcoder wrote:

I made registry change to support 48 bit addressing and I still got the stop error.  I then booted UBCD4Win and ran FIX_hdc.

That's windows default driver with EnableBigLBA.

It seems like only the intelide.sys driver got updated.

This is not true. Most likely there are more settings updated.

At the same time I copied the AmdIde.sys file to windows/system32/drivers, Amdhdc.inf to windows/inf/oem15.inf and windows/inf/Amdhdc.inf, and AmdHDC.cat to windows/inf/catalog directories.

Why do you copy these files?

And rebooted into safe mode....

There was no abort this time?

That's nice.

I know before I had tried FIX_hdc and the registry fix together and I still got the stop error. This time I did not.

I doubt amdide file copy makes a difference. Windows dosn't load drivers that early without registry settings.

I think you ment F6 at F6 message.

I mean F10, if I write F10.
If you don't understand a suggestion, don't make assumptions. Search the net for given keywords. That's: F10 revocery console

 
Most likely this driver dosn't support Win2k anymore.

Go to forum: DriverPack Mass Storage

148 Reply by cdob

(24 replies, posted in DriverPack Mass Storage)

azcoder wrote:

I reinitialized my win2k partition back to the backup saved state, so these got removed.

That's sad news. I didn't exptected this.

azcoder wrote:

I made the registery changes and I still get the same stop code.

There are more settings required. Run fix_hdc too. Catch whole output text, post text. And post fix_hdc.log.

Are you sure atapi.sys is the correct driver for my hardware.

Yes, default driver does support a SB710. Dosn't XP use atapi.sys too?

The DriverPacks entry amdhdc.inf for AM1 is the one for my hardware.  I think it uses AmdIde.sys.

This is a second possibility. Sometimes a manufacturer adds features like hotplug, not supported by default ms drivers.

Is there a way to just install this driver?  Maybe using the same method in UBCD4WIN for the plugin that does FIX_hdc?

Use fix_hdc too.
Create a win2k installation CD, add drivers. Boot the CD. Press F10 at F6 message. Does recovery console list drives?
Boot UBCD4Win. Run "fix_hdc -?" to list options.
Set your win2k installation media as source media.

Go to forum: DriverPack Mass Storage

149 Reply by cdob

(24 replies, posted in DriverPack Mass Storage)

azcoder wrote:

the old system disk was 120 GB, not 160 GB.  Only the 2nd IDE drive was 160 GB.

Do you remember listed disk size at disk management?
Did you get around 130 GB or around 150 GB for 2nd IDE drive?

Did you used directory name \winnt at Win2k?

Does exist a file \winnt\system32\config\fix_hdc.log at new SATA drive?
Post the contents.

azcoder wrote:

I checked the old win2k system, and there is no EnableBigLBA parameter in the registery.

Then atapi.sys won't use the whole IDE drive.

azcoder wrote:

I also checked the current running WinXP, and it has the parameter, but it was set to 0.

XP is not 2K. XP dosn't use this setting anymore.

azcoder wrote:

I modified the /i386/hivesft.inf to set the parameter, but I still get the corrupt file error.

First you have to change setupreg.hiv at installation CD.

azcoder wrote:

I have not modified my current win2k registery to add the parameter.  What utility do you suggest I use?  I can not use regedit because I can not boot the system.

Yes, use regedit. Boot XP or UBCD4Win, run regedit.
Select the following subkey: HKEY_LOCAL_MACHINE
Click Load Hive from the Registry menu
open file \winnt\system32\config\system
Type name system_win2k for the hive you are loading
Make the necessary changes to the registry hive.
Select system_win2k and click Unload Hive from the Registry menu

Go to forum: DriverPack Mass Storage

150 Reply by cdob

(24 replies, posted in DriverPack Mass Storage)

azcoder wrote:

The old IDE drives were 160 GB each and the SATA drives were 400 GB each.  The new drives are also 400 GB SATA drives.  My initial message stated the old controllers were VIA and Promise.  The new one is AMD.  Win2k was happy before seeing the IDE and SATA drives.

Drives are greater 128 GB. Win2k dosn't support this devices out of the box.
Yes, I understand the old hardware. But this dosn't clarify used drivers.
Again the question: which driver did you used previously?
Did you used default Win2k drivers? Did you used atapi.sys ?
Did you added massstorage drivers?

Can you upload your system reg file? Be aware this may contain private data.

Run a search machine, keyword: EnableBigLBA

http://support.microsoft.com/kb/305098/

As for Win2k installation media: http://www.msfn.org/board/index.php?showtopic=75713

Go to forum: DriverPack Mass Storage