201 Topic by compstuff

(4 replies, posted in 3rd Party DriverPacks)

INFO:   RETURN: DriverPackagePreinstallW  (0xE000020B)
INFO:   Preinstalling 'c:\d\3\mon\nec\nl171v.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
ERROR:  Failed to open c:\d\3\mon\nec\nl171v.inf. (Error code 0xE0000003: The syntax of the INF is invalid.)

Go to forum: 3rd Party DriverPacks

202 Topic by compstuff

(1 replies, posted in DriverPack LAN)

My install is fine but noted this in the log:

INFO:   Preinstalling 'c:\d\l\am1\amdl7n5.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
ERROR:  Failed to open c:\d\l\am1\amdl7n5.inf. (Error code 0xD: The data is invalid.)

Go to forum: DriverPack LAN

203 Topic by compstuff

(1 replies, posted in DriverPack WLAN)

The install is fine but noted these errors in the log:

INFO:   Preinstalling 'c:\d\w\a2\oemsetup.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
ERROR:  Failed to open c:\d\w\a2\oemsetup.inf. (Error code 0xD: The data is invalid.)


INFO:   Preinstalling 'c:\d\w\u3\oemsetup.inf' ...
INFO:   ENTER:  DriverPackagePreinstallW
ERROR:  Failed to open c:\d\w\u3\oemsetup.inf. (Error code 0xD: The data is invalid.)

Go to forum: DriverPack WLAN

204 Reply by compstuff

(2 replies, posted in DriverPack WLAN)

OverFlow wrote:

use search LOL - ROFL smile wink tongue

Is it a replacement or a supplement?

You're right... always remember search is your friend :-)

The instructions worked like a charm and sure enough pointed me to the correct folder but determining replacement or supplement is a little confusing still but I'll get it lol

Thanks for the Team invite and WOW lots more reading material :-)

Go to forum: DriverPack WLAN

205 Reply by compstuff

(41 replies, posted in News)

mr_smartepants wrote:

Yeah, I did get them, but I haven't had a chance to look through them yet.  I'm having issues of my own today! >:(

Trust me...I completely understand smile

Go to forum: News

206 Topic by compstuff

(2 replies, posted in DriverPack WLAN)

I am a little confused by this pack... no .ini file structure like the other packs I have been playing with and the same .inf name in many subfolders... I would like to experiment with a new Broadcom driver but I'm not sure how.

The driver would obviously be a "BRx" but do I just create a new folder named BR10 and copy the files in there or am I supposed to update one of the existing "BRx" folders  and if so how do I know which one?

Go to forum: DriverPack WLAN

207 Reply by compstuff

(18 replies, posted in DriverPack Sound)

OverFlow wrote:

a simple solution would be a two step process

integrate the main packs and use SAD for the 3rd party DriverPack

tongue

Thats a really good point and one I haven't explored before. I have been so used to creating 1 DVD with everything on it that I got spoiled. I know we may still have some trouble with integrating too many items so this may be a solution for now... I will continue to report back

Go to forum: DriverPack Sound

208 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

Guys your knowledge base on this stuff is incredible and I REALLY appreciate all the help!!!

I'm sure you will understand when I say that this particular board and set of problems beat the crap out of me but out of stubbornness and my desire to get this all correct for the bigger picture I stuck with it. Right now I REALLY need to get that system up and running and I'm also running some tests on a Latitude E6500 and a D630 so I will have to hold off until the weekend on the rest of this testing but I will do it and report back... h*ll I need to buy more DVD's since I blew through so damn many lol ...plus I need to absorb what dumpydooby wrote before I try it... and I'm sure I'll have questions big_smile dumpydooby if you're game I would be more than happy to try the RVMI addon

Go to forum: DriverPack Mass Storage

209 Reply by compstuff

(41 replies, posted in News)

compstuff wrote:

I sent the Finisher log, the setupact log and the setuperr log but I have to keep breaking the files and sending in parts due to character count limitation the others are too big to do that way

mr_smartepants did you get the logs OK? ...I know it was a pain due to the multiple parts but it was the only way...

Go to forum: News

210 Reply by compstuff

(18 replies, posted in DriverPack Sound)

Now that I got the Mass Storage worked out I have used both packs A & B on my latest installation of this motherboard/chipset and it worked perfectly.

Go to forum: DriverPack Sound

211 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

cdob wrote:

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

Try edit setupreg.hiv and hivesys.inf only.

Took me awhile to get to it but the I removed the OemPnPDriversPath and it loaded the installation just fine... I did NOT complete the install but I figured that because it didn't BSOD it was fine... hope that helps

EDIT: I decided to run it to completion just to make sure the SATA drivers loaded and they did

Go to forum: DriverPack Mass Storage

212 Reply by compstuff

(41 replies, posted in News)

I sent the Finisher log, the setupact log and the setuperr log but I have to keep breaking the files and sending in parts due to character count limitation the others are too big to do that way

Go to forum: News

213 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

cdob wrote:

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

Try edit setupreg.hiv and hivesys.inf only.

OK.. I will try that on my next run shortly... need to report a few other issues first... also I have a few questions that hopefully someone can help with:

Since my goal is to create generic install disks can I use the modified setupreg.hiv and hivesys.inf for all my future slipstreams or is this custom to just this NVidia install?
If I need to use the OemPnPDriversPath still can this be included in all my winnt.sif installs with no negative repercussions?

Go to forum: DriverPack Mass Storage

214 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

compstuff wrote:

From the other thread ATechGuy said the following is needed... should I modify the HIVESYS.INF???

open i386\HIVESYS.INF in a text editor
under: 
Code:
HKLM,"SYSTEM\CurrentControlSet\Services\ultra\Parameters\PnpInterface","5",0x00010003,1
add:
Code:
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","ErrorControl",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Group",0x00000002,"SCSI miniport"
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Start",0x00010003,4
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Tag",0x00010003,60
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Type",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts\Parameters",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts\Parameters\PnpInterface","5",0x00010003,1
save and exit

WOW!!!!!! The changes to the HIVESYS.INI file seemed to have done the trick and the disk is FINALLY installing big_smile
I will finish the install and report back plus now I have some questions on how to proceed from here with the creation of "generic" install disks...

Go to forum: DriverPack Mass Storage

215 Reply by compstuff

(41 replies, posted in News)

mr_smartepants wrote:

Thanks.  DriverPacks Finisher doesn't install PhysX, but it lets me see different aspects post-install.
Like which .inf was used to trigger the install.
Only the newer drivers auto-install PhysX from the .inf.  The older ones (v93.71) won't.

Could you also include all the C:\Windows\setup***.log files too?

Haven't forgotten you... just haven't been able to get past my mass storage problem yet so I never get to the graphics... I  will try it in IDE mode today

Go to forum: News

216 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

From the other thread ATechGuy said the following is needed... should I modify the HIVESYS.INF???

open i386\HIVESYS.INF in a text editor
under: 
Code:
HKLM,"SYSTEM\CurrentControlSet\Services\ultra\Parameters\PnpInterface","5",0x00010003,1
add:
Code:
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","ErrorControl",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Group",0x00000002,"SCSI miniport"
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Start",0x00010003,4
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Tag",0x00010003,60
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Type",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts\Parameters",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts\Parameters\PnpInterface","5",0x00010003,1
save and exit

Go to forum: DriverPack Mass Storage

217 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

Still trying to figure this out and looking for any errors I may have made:
When I ran setPnpInterfaceNvgts.cmd I noticed this and wondered if it was OK:
C:\Y\!Slipstream\_XPBuilds\_10-14-09\P5N7A-VM-DP\I386>copy setupreg.hiv setupreg.hiv.3065.sav
        1 file(s) copied.

C:\Y\!Slipstream\_XPBuilds\_10-14-09\P5N7A-VM-DP\I386>reg.exe unload HKLM\loaded_SYSTEM

Error:  The parameter is incorrect.
All other lines completed successfully

I have two additional questions:
1) How does nLite add the drivers without adding or going through the reg file changes?

This next one is the same question from the other thread you directed me to follow:
2) Can I integrate the driver with nLite and also use Driverpack to add the rest of the drivers? kambing said he tried it and it didn't work! Any idea?

Go to forum: DriverPack Mass Storage

218 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

OK.. here is my latest update:
I created my new source files/folders and copied the setPnpInterfaceNvgts.cmd to the \I386 directory. I ran the command. I copied my drivers to $OEM$\Drivers\NVIDIA,  then modified my WINNT.SIF

OemPnPDriversPath="Drivers\NVIDIA\sataraid;Drivers\NVIDIA\sata_ide"
OemPreinstall=Yes
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

Then I integrated the driverpacks including the massstorage that I modified with the new NV7 drivers.
The system copied the files, formated the drive, copied the files, booted to XP for a second and then BSOD

Go to forum: DriverPack Mass Storage

219 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

you do this in the I386 folder of your source either before or after you add the mass storage drivers with DriverPacks BASE... (before you create the ISO)

What is this actually doing to the installation ISO... I don't understand what changes it's making...

Does this make any changes or have any effect on the host system where I am actually creating my integration and ISO ...sorry if
these are dumb questions... maybe I am a little shot from this particular round since I can't get anything to work the way I expect

Go to forum: DriverPack Mass Storage

220 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

OK so I copy his code:

copy setupreg.hiv setupreg.hiv.%random%.sav

reg.exe unload HKLM\loaded_SYSTEM
reg.exe load HKLM\loaded_SYSTEM setupreg.hiv

reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts5\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts6\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts7\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1 

reg.exe unload HKLM\loaded_SYSTEM.

...and create a setPnpInterfaceNvgts.cmd from it

but where and how do I run it? What does this mean:Try run setPnpInterfaceNvgts.cmd at \I386 directory: ...do I copy the setPnpInterfaceNvgts.cmd to the \I386 directory and then "run it" at some point during the install?

Go to forum: DriverPack Mass Storage

221 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

if the device does not have legacy support then you MUST add the registry entries to the Hive... (Thanks nvidia)

I'm not understanding how and when to actually add the reg changes...

I'm also not understanding how nLite managed to work with the drivers... do they add the reg changes you're referencing?

Go to forum: DriverPack Mass Storage

222 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

compstuff wrote:

Ok I just tried it again and no luck... the drivers I used are definitely good because I did a test with nLite and also tried the basic F6 mode and they worked so I am thinking this must be a mistake I have made. I am going to try a few more things and then give up on the mass storage before I shoot myself lol yikes

EDIT: I THINK I found an error in my ini file... I accidentally deleted the PCI\ from the hwids... I rewrote the ini and am trying it now

Well I made the changes and ran the test and once again it failed....

cdob wrote:

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

Cdob, that was a great find thank you... I must admit after reading this a half dozen times I am still a little confused regarding the registry changes... the OENPnP I understand but will this not work without the reg changes?

Go to forum: DriverPack Mass Storage

223 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

Ok I just tried it again and no luck... the drivers I used are definitely good because I did a test with nLite and also tried the basic F6 mode and they worked so I am thinking this must be a mistake I have made. I am going to try a few more things and then give up on the mass storage before I shoot myself lol yikes

EDIT: I THINK I found an error in my ini file... I accidentally deleted the PCI\ from the hwids... I rewrote the ini and am trying it now

Go to forum: DriverPack Mass Storage

224 Reply by compstuff

(35 replies, posted in DriverPack Mass Storage)

I have been swamped at work lately and haven't been able to test anything but I am going to try again today and wondered if my pack changes above looked correct or not?... when I tried them they didn't work but I will double check today.

Go to forum: DriverPack Mass Storage

225 Reply by compstuff

(2 replies, posted in DriverPack CPU)

mr_smartepants wrote:

It won't hurt to have it, but yes, you can exclude it from Intel installs.

It's small and rather minor but since I am running into the problem with too many packs I wanted to experiment... plus this one board is beating me up pretty good and I can't seem to give in :-)

Go to forum: DriverPack CPU