You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
Technically this is wrong
exc_1_+hwids = 1
exc_1_+hwid1 = "HDAUDIO\FUNC_01&VEN_8384&DEV_7691"
exc_1_+hwid2 = "PCI\VEN_10DE&DEV_01D7"
you did not index the counter
exc_1_+hwids = 2
exc_1_+hwid1 = "HDAUDIO\FUNC_01&VEN_8384&DEV_7691"
exc_1_+hwid2 = "PCI\VEN_10DE&DEV_01D7"
The finisher has issues with HDAUDIO\ device ID's this may fail if you use HDAUDIO\ as a HWID trigger.
(Mr_smartepants said this in his last post.)
I did not realize there was a Setup.exe file involved... that makes a difference.
Looks fine...
you cant do this with finisher exceptions... By the time the finisher runs it is too late the driver is already installed.
you Must handle this in the drivers inf file... however if you modify the inf then you will most likely break signing...
But modifying the inf is your only option...
an easier solution would be to buy One DVD reader and hang it on the machines without a DVD drive.
Quickest easiest first...
Putting SAD on a thumb drive does not solve the issue.
Putting the whole install on a thumb drive may not work either since if the machine is so old it has no DVD it may not boot from USB either.
No the best solution is to create a DVD installation disc and just hang an IDE DVD ROM on machines that have no DVD ROM.
related topic here... (stickied in this forum) http://forum.driverpacks.net/viewtopic.php?id=4631
code tags added to your first post... "edit" your post to take a peek at how that is done. It keeps the threads from being so long. 
Thanks Mike, Excellent details and feedback...
Welcome to DriverPacks.
actually that is an "Option". although it is a manual option...
We don't support attended installs...
open the winnt.sif and remove the [Unattended] section including the header... That's it... repair option restored.
Of course now you have an attended install...
good teamwork~
I understand what you are saying... but the one time i need the driver that i did not include... it will cost me way more than the one minute I would potentially save PLUS it would take time to omit them. The script to remove them is in the forum you linked to... it's a RVMI add on.
The biggest reason not to do it is man power... We don't have enough man hours to properly maintain the existing packs. Adding more work, in the form of a new pack, is just more work we don't have time for. On the other hand if you were willing to take on this task yourself I might be persuaded to consider it
http://forum.driverpacks.net/viewtopic.php?id=4631
there is the discussion about the VirtualBox driver...
You guys rock... that is the kind of feedback that really makes updating mass storage much easier.
Well Mass storage is only about 5 meg total... Even if we could cut that in half (not likely) it would only save about 2 meg of file copy...
There is almost no benefit for the effort.
I vote no... not worth the effort.
Since the philosophy of the DriverPacks is to include ALL drivers it is also against our projects main goal...
So really, really no, it's not going to happen.
PS feature requests should go in the feature requests forum... Moved.
the problem is that drivers that depend on other drivers will fail with SAD.
This is not an issue when slipstreaming the DriverPacks into the source.
With the MS tool DPINST.exe there are limits that do not exist with windows setup.
I don't recomend attempting to install a clean system with SAD. it is good far adding a device or for updating existing drivers.
If you insist on a software first install then it will take several passes with reboots in between. For example a HD Audio driver depends on teh HDA bus to be installed first. if the HDA bus is not installed then the HD sound driver will not install. (because teh device does not exist). Same goes for like a SCSI tape backup. You must first install the SCSI adapter driver reboot then install the Tape driver.
Using SAD on a machine with no drivers may take three passes and two reboots.
the reason is simple all devices are conected to the chipset driver... the chipset driver must be installed first (pass one with SAD), then the machine msut be rebooted then the devices that are connected to the chipset can be installed (pass two with SAD). This is not a bug or a shortcoming with SAD. It is simply the way PnP works... think of it like building a pyramid, you can't put the capstone on first, you must start at the base and work your way up to the top one level at a time.
If you don't like this then use the DISC method to slipstream the DriverPacks into your source... That is what it's for
you can NOT make changes to your source after you run DriverPacks BASE on it...
if DriverPacks was not the last step in your process before creating the ISO / Disc then you can NOT update the mass storage drivers.
It sounds like you made changes after you added the DriverPacks... If that is so then you must start over with a clean source.
this is stated in the tutorial .
When I did a build with UBCD4WIN v3.50, it always detected with no prob.
With v3.60, I get a "Windows cannot load the device driver for this hardware.
PCI\VEN_10DE&DEV_03EF&SUBSYS_26091019&REV_A2\3&2411E6FE&0&38: NVIDIA Network Bus Enumerator
can you please post your HWIDs juanpaul?
thanks for sharing these excellent details, and for your determination in solving the issue yourself. most helpful.
Especialy letting us know which version of the driver worked. *(and which ones do not)
If you provide the HWID we can certainly fix it in the next release
can you test a pack for us if need be?
Welcome to DriverPacks.net sir, have an awesome day.
Jeff
because there is a limit to the number of mass storage drivers that can be used at one time... each newer version of windows has a higher limit than its predecessor... So by useing a newer version you can include more mass storage drivers without crashing...
Further... the limits in SysPrep are half what they are for Disc and RIS installations. IE 4096 / 2048.
I must warn you that substituting files from another OS is a violation of the MS EULA and is Piracy. We at DriverPacks.net do not condone or recomend the illegal use of MS software. However IF you have lots of licenses (like a school with site licensing) you could burn an extra license specifically for each of your installation disks. Similar to the way BartPE is licensed. For most people using a w2k3 64 server license to do installs is a bit pricey 
.
the sound recorder is supposed to play the Ding sound... to let you know it's finished...
sounds like it worked as designed... IDK what else would be useing sound recorder at that time... strange.
again the ding sound is supposed to alert you that SAD completed successfully...
did you manage to add the driver to BartPE manually? (as I described)
- That is to say there were no warnings or errors reported by PEBuilder?
It is important to note here that BartPE is not a windows replacement.
Some things are Extremely difficult to make work in a Pre-installation Environment (PE).
Many times they are simply not worth the effort... anything is possable... How much time do you have to devote to it?
Think of it as trying to run windows XP programs in windows 98. Some may work no problem others may not work at all.
We are being patient... you weren't banned were you? 
Why (in the world would you do this)? is a totally valid question... no offense intended
you should Extract them from the *.7z archives (Packs) Into the existing SAD folder... "Driverpacks.net\D\"
then you should be able to run DP_Inst_tool.cmd on a Vista or Win7 box...
Let me know if you have trouble...
DVD are very slow... but you could do that. I wld use a USB thumb drive or a USB HDD.
you CAN'T use DriverPacks BASE to add the Vista drivers... you will have to do that manually.
You can use DriverPacks BASE to create the folder structure and extract the files you need.
(Do this by selecting the smallest DriverPack we offer... CPU and selecting Method 1) (Hit slipstream and EXIT DriverPacks BASE)
It does not matter that the CPU pack is for XP... Vista will simply ignore it.
Once you have created the SAD folder (with only the CPU pack) (and Exited DriverPacks BASE).
Then MANUALLY download and MANUALLY extract the VISTA drivers into the SAD folder you created with BASE.
Test and report.
If what you wanted was possible then we would not have provided you with DriverPacks BASE... Why would we bother?
If there was an easy way to do it then we would not be the only ones to offer an app to add them to your installation media.
Use DriverPacks BASE to add the DriverPacks... that is why it is provided.
It's simple and has a proven track record. Seven years and millions and millions of installs.
Have a great day.
the vista drivers need to be downloaded manually...
I belive that BASE 10.x should work with SAD and Vista Packs
Simply create (or use an existing) SAD folder M1...
I Would Select CPU pack M1 and SAD... This creates folder structure and files...
Extract all the vista packs you desire to \DriverPacks.net\D\ (Just ignore the existing CPU files)
that should work with Vista... the DPINST.exe we use is 2.1 and should be compatible with Vista and Win7.
See how that works for you...
Thanks Romeo91... looks good I'll see if i can find a test case for it
We still don't accept drivers from third parties like rapid share or other...
you will have to post a link to the original download at Dell or it will not be added. You must also include the HWID of the device.
BASE internaly exits itself after it writes and calls this script...
This has always worked in the past, and i did not change it... perhaps it is related to updates in AutoIt.
the worst thing of it is I can't go back and update the 8.12.5 code for everyone...
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.263 seconds, 9 queries executed ]