Search options (Page 51 of 213)

it is preferable to do it all in one step windows setup is better than dpinst. IDK why...

i use an external dvd usb when a pc does not have a dvd or if i am in my office i use RIS...

Please post your response to the other thread.
Since the two issues seem to be related let's not bounce back and fourth LOL.

http://forum.driverpacks.net/viewtopic. … 850#p37850

I replied to his other post with a similar response.

I belive yhe fix is to include chipset drivers via devpath and a local source
I think making chipset drivers available to mini setup resolves the issue

I'd save even more time if people bothered to read the documentation
- this ain't your private help desk
- from the Rules and Posting Guidelines, This is not now nor was it ever a Noob friendly site.

Stay tuned, I need to nail down a few loose ends with DriverPacks BASE, once that is done I will be starting a tool to add drivers to W7 (and it will probably be compatable with Vista, but i am not going to kill myself to achieve Vista compatability ).

The Win 7 Driver tool for DriverPacks will be the basis for a new Siginet tool (to be named later) but it will be like the RVM Integrator in fit form and feel. We (Wim Leers AKA Bâshrat the Sneaky and myself AKA  Jeff Herre) will create an open source Python application to integrate drivers with NT6 platforms, much like DriverPacks BASE does for NT5. I intend to write it in such a way as for it to be easily forked into the new Win7 Integrator (or whatever we end up naming it) We have been laying the ground work for this application over at http://future.siginetsoftware.com/. Bâshrat the Sneaky, mr_smartepants, Muiz and I are all on the siginet development team. In as much as we are all volunteers whom are working for nothing / free it takes a while to find the spare time to devote to creating a quality app. like DriverPacks BASE or RVMI.

But trust me it will happen! Look for it in a location near you soon!

Did you read our docs from the home page?

http://driverpacks.net/docs/miscellaneo … -dism-muiz.
http://driverpacks.net/docs/miscellaneo … er-attempt

Also check out the Microsoft Deployment Toolkit (MDT).

All of these will require WAIK from MS. If you download the MDT then WAIK is downloadable from the MDT GUI.

You could also use DPINST.exe (MS).

from your log

566.2010-04-15 15:07:51 : <EXEC> Executing all commands (1) for exception [S3].
567.2010-04-15 15:07:51 : <EXEC>    Executing command 1 of 1: "%DPSROOT%\D\S\S3\sma3.exe"
568.2010-04-15 15:08:46 : <KTD>  KTD will not be applied, the DriverPacks will be deleted.
569.2010-04-15 15:08:46 : <CLNP> Deleted "C:\hwids.dat"!
570.2010-04-15 15:08:46 : <CLNP> Deleted "C:\DPsFnshr.ini"!
571.2010-04-15 15:08:46 : <CLNP> Deleted "C:\devcon.exe"!
572.2010-04-15 15:08:46 : <CLNP> Deleted "C:\makePNF.exe"!
573.2010-04-15 15:08:46 : <CLNP> Deleted "C:\pmtimer.exe"!
574.2010-04-15 15:08:46 : <CLNP> Deleted "C:\*.ins"!
575.2010-04-15 15:08:46 : <CLNP> Deleted "C:\DSPdsblr.exe"!
576.2010-04-15 15:08:46 : <CLNP> Deleted "C:\mute.exe"!
577.2010-04-15 15:08:46 : <CLNP> Deleted "C:\DriverPack_*.ini"!
578.2010-04-15 15:08:46 : <CLNP> Deleted "C:\DP_Install_Tool.cmd"!
579.2010-04-15 15:08:47 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
580.2010-04-15 15:08:47 : Program terminated.

looks like they were deleted ?
and the commmand to run the installer for the sound card was run.
perhaps the installer for the sound card is responsable for the driver popup?

where did these come from
- DevPath.exe
- hwids.txt
- setup.txt

those are not copied by SAD nor DriverPacks BASE so they won't be deleted

the finisher is deleted after a reboot - did you reboot before checking?

It looks like you used an M1 source.
An M1 source will not be deleted by the finisher unless you modify the DP_Inst_tool.cmd
REM or delete the following line.
"Echo DPsRootDel  = "false"            >> %DPFL%"
IE
REM Echo DPsRootDel  = "false"            >> %DPFL%

since an M1 source is not copied / extracted it is treated just like the 7zip archives with a M2 source - originals are not deleted. However if you remove the DPsRootDel  = "false" line then the finisher WILL delete your M1 file set.

SAD M2 is the answer for most of the main packs... IF you have already integrated Mass textmode

I would include chipset and LAN via devpath. since most drivers depend on chipset it should be available to minisetup. Failure to do so may require you to run SAD twice. IE if chipset is not installed then any devices that depend on chipset will need reinstalled after chipset is installed (cut down or eliminate re-enumeration).

So integrate Mass textmode. Devpath Chipset, CPU, and LAN. SAD M2 for Graphics, Sound, WLAN and Mass (for PnP mode drivers).

I did not think you were a noob . I meant it in so far as you clarified it. You, just like me, have a unique perspective to sysprep with DriverPacks. It's the perspective of unfamiliarity, again that is a GOOD perspective for creating a guide... you are more likely to avoid the pitfalls of making assumtions and skipping over provideing details of seemingly obvious steps.

To the best of my knowlege those files are not modified by the DriverPacks.

But just because I am not aware of something does not indicate that it is either true or false. I learn new stuff everyday
Your results would lend both of us to belive they are being replaced by one of the driver installs, you are in a better position to narrow it down to a single pack / driver. If you tell me which pack i can use the HWID to figure out which driver. If i know which driver i can carefully read the drivers INF file and see if I can figure out what is being done by that driver as it is installed. I would prefere not to have to look every one of them up and read them all .

PS You told a fib... you are not using the latest (official release) packs
http://driverpacks.net/driverpacks/windows/xp/x86
10.04.x are out for LAN and Graphics A and B. See how that can be confusing

first off you are under a false impression. DriverPacks Finisher does not install drivers... it installs non driver related software like the ATI control panel or Nvida control panel, sound cards often have mixers and things of that nature that are installed via Setup.exe files. the finisher calls setup programs that are sometimes required but are not related to the driver installations. Again the finisher does not install drivers AT ALL. it simply "finishes" the installs (call a setup.exe or *.msi if required - and very few drivers require it.) and removes the DriverPacks. As the name implies "finishing" the install... otherwise we would have named it the DriverPacks installer .

second. I will assume you are using LAN 10.04.1 (you did not state which version of LAN, or any of the other packs that you used. ['the latest' is not helpful since we update packs every day IE latest official release, latest nightly, latest Release Candidate, latest Beta... latest what??? (Vague and over broad)] - Either provide your DPs_BASE.log (which lists them) or specifically state the name and version(s). Leaving it to us to Guess / assume does not help you, nor does it help us to help you .

LAN 10.04.1 supports PCI\VEN_14E4&DEV_1677 =  Broadcom NetXtreme 57xx Gigabit Controller 
In folder \D\L\B1\ with an INF of b57win32.inf  DriverVer   = 07/31/2009,12.2.2.0

There are no DriverPacks Finisher calls for [B1] in the DriverPack_LAN_wnt5_x86-32.ini. So removing the DriverPacks Finisher call from your install will make no difference to your results. (except the DriverPacks and releated files will not be removed)

Since this is a Dell it is possible that that specific driver (Broadcom Reference driver) is not compatible with the Dell NIC.
We often find that Dell will modify their chips in such a way that they will not work with a reference driver. Of course this is a license violation by dell (OEM chips MUST be able to work with the Chipset manufacturers reference driver to maintain their (Dell's) license to re-manufacture) But who is going to sue Dell .

- Have you verified the MD5 checksums / file sizes of your downloads? (Un7zip will NOT report an error on a corrupt file)

Just to be sure this is the issue try a reinstall without the DriverPack LAN included. does the issue disappear?

If so:

1) Please download the driver from Dell and test it... if that works please link us to the known working driver. We will attempt to add the dell driver to a nightly pack, and offer it to you for testing.

2) It is also possible that an older version worked. We updated the broadcom driver in 10.02 so LAN 8.12.1 may work. (Since it contains a different / older driver.  DriverVer   = 06/19/2008,10.85.0.0) http://driverpacks.net/driverpacks/wind … lan/8.12.1

If not: Can you tell us which pack it is? (process of elimination)

Thanks for your feedback and we look forward to helping you.

Welcome to DriverPacks,
Have an awesome day!

you guys are more than welcome to do that. If you each detail what you do and works for you then perhaps we can merge two or three How to's into a single Tutorial. that tutorial can be put on the home page (the "Doc" section of the home page is a 'wiki' style page that you guys can edit to . So let's pool our experience here into several 'how i do it' style posts. perhaps between the currently active members [QuadDamage, Registered, Detard, ssx4life, etc...] we can make a current and flexible outline for people to use. Obviously it will need to be worked on quite a bit. Some people will want to use OLSP other will not. Some people will start with a DriverPacks slipstreamed source and not need to use OLSP or -bsmd. some people will opt for KTD / SAD M1 with DevPath. Others will opt for SAD M2. the many ways to get there will have to be outlined so a user can choose thier best option and then fine the details to implement the best options for them. No small task. DriverPacks is based on teamwork, as a team perhaps you crazy sysprep dudes can pull it off. We will certainly be here to help, as always!

Jeff

Same answer as given to that bug report

If the files were not missing then DriverPacks BASE would not report them as missing .

We have been unable to figure out how to fix user error as yet

start over by copying your original hologram-ed windows XP CD to your HDD... Run DriverPacks BASE on that.
Now there are no errors.

Your source is corrupted... as DriverPacks BASE already told you.

It is not really even important which file it found missing... BASE is not capable of doing a full verify on your source. If one file is missing it is reasonable to assume that others are also missing.

Since we can not provide you with a valid source it is beyond our ability to fix.
(Again this is not a DriverPacks error it is an error with your source)

You need to start over with a clean source.