Upon further research i notice that

PCI\VEN_10DE&DEV_037F&CC_0104

Is not supported by the  D\M\N\5\NVGTS5.inf - which is the INF for "nvgts5.sys"
It lists:

PCI\VEN_10DE&DEV_037F&CC_0101
PCI\VEN_10DE&DEV_0054&CC_0101
PCI\VEN_10DE&DEV_0055&CC_0101
PCI\VEN_10DE&DEV_044D&CC_0106

NOW... D\M\N\5\NVRD325.inf Does list your HWID! (somebody goofed) LOL

So if you could test this for me!!!!

extract the driverpack from

UBCD4Win320\plugin\DriverPacks.net\BASE\DriverPacks\DP_MassStorage_wnt5_x86-32_805.7z

to \DriverPacks\DP_MassStorage_wnt5_x86-32_805

and rename the folder to \DriverPacks\DP_MassStorage_wnt5_x86-32_806

edit  DriverPacks\DP_MassStorage_wnt5_x86-32_806\DriverPack_MassStorage_wnt5_x86-32.ini

replace the section [N-5]  with the section below

[N-5]
ms_count=2
ms_1_deviceName="NVIDIA nForce 520 RAID/AHCI Controller"
ms_1_tag="nvgts5"
ms_1_sysFile="nvgts5.sys"
ms_1_hwids="PCI\VEN_10DE&DEV_037F&CC_0101,PCI\VEN_10DE&DEV_0054&CC_0101,PCI\VEN_10DE&DEV_0055&CC_0101,PCI\VEN_10DE&DEV_044C&CC_0101,PCI\VEN_10DE&DEV_044D&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"
ms_2_deviceName="NVIDIA nForce RAID"
ms_2_tag="nvrd325"
ms_2_sysFile="nvrd325.sys"
ms_2_hwids="="PCI\VEN_10DE&DEV_037F&CC_0104,PCI\VEN_10DE&DEV_0054&CC_0104,PCI\VEN_10DE&DEV_0055&CC_0104,PCI\VEN_10DE&DEV_044C&CC_0104,SCSI\NVIDIA__Raid_Disk________,SCSI\__NVIDIA_______Raid_Disk,SCSI\NVIDIA__Raid_Disk_20_____,SCSI\__NVIDIA____Raid_Disk_20,*NVRAID20"
ms_2_isBusExtender=false
ms_2_exc_disableIfOS="w2k"

7zip to DP_MassStorage_wnt5_x86-32_806.7z (should default to this name)
base will see this as a newer version and use it automaticaly wink (you can leave 805 there) big_smile

from pebuilder go to the plugins page and select base and hit the config button...
ensure the new mass is there and enabled (hit 'refresh')

Build a disk and report back - I think your fixed... !!!

A team member may put up a test pack if we wait... wink up to you!

have a great day and thanks for reporting!

jeff

PCI\VEN_10DE&DEV_037F&CC_0104

is directly supported by mass storage pack DP_MassStorage_wnt5_x86-32_805

D\M\N\5

[N-5]

ms_1_deviceName="NVIDIA nForce 520 RAID/AHCI Controller"
ms_1_tag="nvgts5"
ms_1_sysFile="nvgts5.sys"
ms_1_hwids="PCI\VEN_10DE&DEV_037F&CC_0104,PCI\VEN_10DE&DEV_0054&CC_0104,PCI\VEN_10DE&DEV_0055&CC_0104,PCI\VEN_10DE&DEV_044C&CC_0104,PCI\VEN_10DE&DEV_044D&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

I belive that this is the version included with UBCD4Win 320 ...

it should work... which OS did you use to create your build xp or 2k3?
is the mass storage plugin enabled? ('config'ure base from PE builder 'Plugins' to be sure)
there were no errors or warnings during the build?

Title: un7zip.exe is not a valid win32 application error
Post: I get this error when trying to install XP after slipstreaming drivers, what went wrong?

the best answer i can give you is the obvious one...

You have provided Zilch for info on what you did
- can you please...
Read  "Before you post"  in my signature take note of what we consider the "minimum" info and format
This applies for ANY support questions... TY
Then take a moment to update your first post title. and then add the missing info to a new post.
It might also be helpful to know your process...
IE; RVM, Nlite, DriverPacks, burn...

did you test the file on the disk on another machine ? ? ?


the obvious answer is that the file on the cd is Corrupted   wink


IE un7zip.exe is not a valid win32 application error

I have looked at this further now
I discoverd that both of the drivers you have submited are already included in the 3rd party DriverPack

the modem is in \D\3\M\AC\21 in the modem pack

; Agere Soft Modem Setup File
DriverVer=03/09/2007,2.1.77.9

and is newer than yours (2.1.77)


the card reader is in \D\3\C\T\2

Provider="Gemplus"
DriverVer=09/14/2006,1.0.1.20

and Yours is newer... wink

updating the card reader pack and resubmitting is the "Awsome" route to take sir!
if you wanted to be DriverPacks hero of the day you could update and test and report back!

jeff

PS One of our dedicated 3rd party DriverPack MOD's might step in and merge them if we wait long enough... wink tongue lol

Welcome to our forum and thanks so much for giving back to the comunity!

please see this thread!  http://forum.driverpacks.net/viewtopic.php?id=587

RE standard folder layout at the bottom of the first post

card readers are currently in D\3\C

This Should be the new layout:
+D
---+3
------+C = SmartCard Readers
--------+T[x] = Toshiba
------+M = Modem Pack
--------+T[x] = Toshiba

where [x] is a single letter or number, if required

By sticking to existing conventions your pack can coexist with other users packs wink

Have an awsome day!

It is important for the code team to be able to let the translators know when new DriverPacks BASE features require language files updates.

Please, would all of the translation team members subscribe to this Topic

You will all be emailed when its updated and in this way we can contact all of the translators with one post...

IE BASE 8.08 adds three new options for Nvidia control panel.
these translation options need to be added or your language will show error messages.
not the end of the world i know... but still...

I assume that if you all knew that it needed to be done...

thus my idea of having everyone subscribe to this topic...

A single point of contact for the DriverPacks Translations Team

PS if your not in this list let me know http://forum.driverpacks.net/viewtopic.php?id=353


You guys make an important contribution to our project, and i appreciate it and each of you!


Thanks a Million

jeff

Jaak wrote:

sil too? I missed this.

yup

PCI\VEN_1095&DEV_3132

and he wont tell us which controller he is using wink

"It's the one on the MB..."

i thought the hwid was interesting for the 3132...  PCI\VEN_1095&DEV_3132&CC_0180

did we find that PCI\VEN_1095&DEV_3132&CC_0180 was generic Raid mode 5?
if so this doesn't coincide with Native IDE mode...
wonder if the order swapping technique will work (obviously only if he is using that controller)

We cant eliminate this as a possable solution until we know for sure that it's not the one in use... sad

we dont use per machine setups... we belive in one install disk to support all machines.
add all the packs with DriverPacks BASE and you should have no problems (that is how it is set up to work)

Thanks Sam! mr_smartepants is on vacation at the moment... (he has for sure earned one... yes?)
sit tight for a little bit and we will see that in a test pack.

have an awsome day

your both right wink big_smile tongue

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

i must agree...

It was not on lmy mind that a SAD disk would make KTD obsolite... but in thinking about it, you're correct

Why keep old drivers around when we can implement the newest ones at any time.... wink

bump

i thought it might just remove items from the packs making smaller packs then the finiser still works and KTD wink
as i think about it the packs ini will probably not need to be edited... wink
the packs could be given a name that would be the equivilent of a nightly.
IE add at least two charachters to the file name:  DP_MassStorage_wnt5_x86-32_805pr.7z  (pr for pruned wink )

this gives it a higher value (newer) than the original pack when we run DriverPacks BASE and it would be used for slipstreaming.

this might be a nice little add-on i could code
- i really see it as a stand alone app - similar to dpinst / SAD disk

don't look for this to show up right away wink

Can you please post your HWIDs for the 590...

this should actually be in the bartpe forum so i'll move it there...

Have a great day and thanks for letting us know about your issue.

Welcome to DriverPacks, We are glad your here and providing feedback!

I am always eager to consider options
sometimes they even lead to ideas that were not even part of the original idea wink
(brain-storming)

Helmi made the best point so far, we are of the mindset of every machine supported every time.

perhaps someone will also find this appealing and write a "Pack Pruner" application wink
this could easily be a stand alone app that lists folders with checkboxes and a description...
this app could be run prior to DriverPacks BASE for customizing the packs for a specific set of machines (or one).

Thanks for contributing - we never know where ideas are going to lead us!

wink

Thanks to both of you. You have each made excellent points smile , pro and con...

from the base side of things this would be cumbersome as the folder names and supported devices change...
this could be addressed - medium high difficulty
  base is blind to the contents of the packs - so we would need to pass pack folder device info to the base program and generate a HUGE list with checkboxes or whatever. and would require extracting and repacking the DriverPacks

most people use M2 and as such the packs are not extracted until the WinPE stage of setup...
this presents two options;
  modify the pack(s) in advance - extract, prune, repack and possibly have to modify the packs INI too...
  this might be scripted however we refer to above... medium high difficulty and very time consuming
  for each new pack that is modded.

  Modify the packs from presetup.cmd after extraction - a small script that deletes a list of folder names.
  this may also require the pack ini's to be edited (maybe not...) this is probably the easyest choice.
  the down side is the full packs are extracted and then pruned so there are some wasted resources. 

It is still early and i havent had a full cup of coffee yet... perhaps i have missed something wink

it seems to me the easy way to do this is for you to create a script that will be called from presetup
this script will delete a "list" of \D\x\x  folders from the target machine.

this script will need to be manually modified each time the team changes folder names. IE we would need a way to find the folder that contained the 3dfx driver folder to prune it. this would either take codeing and then adding additional INI entries or create new files that serve as an index for each pack. obviously this would not be backward compatable. this also has the down side of additional work for the DriverPacks team...

lets put this idea down as "under consideration, pending feedback"

Thanks 7yler

Always nice to have people contributing their 3rd party DriverPack and shareing the wealth with us

3,570

(8 replies, posted in DriverPack Sound)

you can change the folder names No Problem...

IDK if it will help you... but you can... big_smile

just be sure to update the packs INI if you do... wink

3,571

(2 replies, posted in DriverPack WLAN)

USB\VID_2019&PID_AB50\7&1D29BBF0&0&1

request is duplicate...

since Intel rolls out chipsets in June   July and August are big months for Intel drivers

This is True EVERY YEAR... and we already know it - of course... It's what we do... wink
We watch station drivers and know well in advance of thier release in fact... wink

Thank you for your interest and continued support. there is no need to request common drivers
IE no Intel Nvidia or ATI requests are ever neccessary

In as much as Intel releases thier new chipsets in june julyu land august are frought with driver issues in all packs. The dust usually doesn't settle till end of august or so, after all the bug fixes are out for the new drivers. wink In as much as all the other driver depend on Chipset and Mass Storage those are always first on the list. those are in process with the testing team and are "current" in the nightlies (beta packs)... once Chipset is stable and then mass we can concentrate on the other packs too like wlan and graphics (i bleive we are testing the current DriverPacks Graphics too wink

Don't worry we will get to the new WLAN drivers...

We like Stable DriverPacks - Current DriverPacks are a secondary concern
don't get me wrong we like to be current too... Of Course!!! tongue
but we try very hard not to release packs that have issues... big_smile


Again thanks for bringing this to our attention
- But we are well aware of Intels latest drivers (especialy this time of year)
- it is what we do... wink

Have an awsome day and thanks for being here and contributing!

jeff

3,573

(14 replies, posted in Software)

thank you for your time and handy script!

ill give it a live test over the next few days

i don't really care to test it in the GUI since it is normaly used during WinPE phase of setup.
so my criteria will be how much faster is it during WinPE (normal usage)
if it's faster and has similar "Fit, Form and Feel"
- perhaps we can consider just moving in that direction or offering it as a base option...

Once again, thank you for giving back to the comunity and shareing your quality ideas.

jeff

DriverPacks is not a plugin for nLite...

you can not add DriverPacks to your install with nLite.

tutorial in my signature on how to use the DriverPacks 

run nLite first
then run DriverPacks BASE to add the DriverPacks
then burn your disk
(DriverPacks must be the last step before burning your disk)


PLEASE NOTE:
the DP_Install_Tool.cmd is for updateing existing drivers on a running system not for a new install...
it is not designed for use during the windows installation - you will have issues like freezing, skipped drivers and BSOD's
tutorial on how to use DP_Install_Tool.cmd for a SAD (Stand Alone Drivers) disk is in the FAQ forum

you are asking for support for an unpopular program.

you are asking for support for that program at DriverPacks -
at the moment we dont have support for "sysprep" type installs - we do intend to add it

so your a little off topic for our forum (userbase), and asking about a program that is not favored by our limited sysprep userbase

we use the HWID's tool to identify hardware - that you should have been able to come up with if you had spent more than one minute reading a few posts here. obviously you didn't... or you would have realized your one question was out of place and the other was info you couldn't possably miss unless you didnt try.

the hwids tool simplifys the use of devcon a MS tool for reporting hardware ID's
hwids are used to ID hardware and then match them to drivers that contain that ID in thier INF
that is driver install 101

we dont really care waht the name of the device is, but... googleing the HWID will give you that answer if you need to know.

DriverPacks doesn't cater to noobs as a rule... and ones who are not willing to even do a basic search and read a few posts on thier own are usually ignored.

Sorry you did not get a response
sometimes it is better to not say anything if you cant say something nice

best of luck with your mission... if you figure it out perhaps you can pass it on to someone else who is in a similar situation. but that doesnt seem to be the case no one even chimed in with a "I would like to do this too!"

Have a nice day and i'm sorry you were not able to get the answer you needed.