1

(1 replies, posted in Vista / 7 DriverPack Mass Storage)

Welcome to DriverPacks.net arsh469,
As stated on the page that you downloaded it from, the support site for Driver Pack Solution is http://community.drp.su/
This is DriverPacks.net, We support our software and packs here.
We are not able to provide support for projects that we are not involved with.
Have a great day.

2

(9 replies, posted in Windows 7 tools)

@it wrote:

Hi only a newbie here, did this documentation ever happen.

@it

Yes, first post of this thread.
http://forum.driverpacks.net/viewtopic.php?id=5336

Called it!

BwaaHaaaHaaa!  THAT's funny right there.

Sounds like you broke your svcpack.inf or cmdlines.txt or txtsetup.sif file.

Are the addons installing in the image you tested before you integrated DriverPacks?
You ARE testing each stage before moving on to the next modification...right?
Are they "svcpack" or "ROE" addons?
http://www.msfn.org/board/topic/76913-c … vcpackinf/

6

(58 replies, posted in 3rd Party DriverPacks)

djuka88 wrote:

Can i make 3rd partty mass storage sata/ahci driver because my driver isn't listed in  mass storage drivers pack?

No, not Third Party DriverPacks.  But you could attempt to modify the dpms to add what it is missing.
dpms is a VERY difficult beast to tame.  The .ini contains many pitfalls and you WILL break your system is it goes wrong.

This is why we (continually) recommend people to start with a factory-fresh Microsoft hologramed CD image.
Any (ANY) image you download from the internet (unless it's from a microsoft.com source) WILL be tainted.
TUProgSt.exe

No.
The whole point of integrating dpms into the XP image with DriverPacks BASE is so that the system can "see" the hard drive at the beginning of the install (known as "textmode").  If dpms wasn't installed properly, the blue install screen of XP would say something like "No hard drives found to install onto".
Simply replacing the dpms archive on the image with a newer one will only provide updated drivers to the system once the XP installer has already began the install process.  Just because you haven't had any errors doesn't mean that it's a bug-free image, it just means that you were lucky.
SAD3 cannot replace DriverPacks BASE for what you need.  SAD3 can only upgrade the drivers AFTER the install has taken place.

symbios24 wrote:

my install finds always a harddrive achi or ide so i just replace the old masstorage pack with the new in this case??

NO!!!
This has already been explained to you several times now.
Don't touch dpms.
The ONLY way to update dpms in your XP install image is to rebuild the entire image from scratch and integrate the new dpms with DriverPacks BASE.
Did you build your own image or was it built by someone else?

10

(10 replies, posted in Other)

Did you use DriverPacks BASE for this XP install?  If not, then please do that.  When you do, then enable "KTD" option.  This will "Keep The Drivers" in the XP system so that future hardware MAY be installed without user interaction, though there's no guarantee.
Some hardware works with KTD, most do not though.

If you DID use DriverPacks BASE, please post your log files (instructions in the Read BEFORE you post. link in our signatures.)

Jeff (Overflow) is right.  We can't help you without specifics.  Tell us what you did and how you did it and what the specific problem is.  Can we duplicate your problem from the info you provided? No.
Help us help you.

I haven't tried it, but you could embed a symbolic link to point to the samba share where the DriverPacks are stored.
So , replace the x:\sad\nt5 and or x:\sad\nt6 folders with symlinks to point to the shared network folder.
http://msdn.microsoft.com/en-us/library … s.85).aspx

If you try it, report back your success/failure.

OverFlow wrote:

Happy Fourth of July! (Do you still celebrate mr_s? he is the only one lighting off fireworks today... lol)

I lit the fuse to my BBQ, that's about it. tongue

All you should need in the setupcomplete.cmd file is this:

@echo off
START %systemdrive%\D\SAD3\DP_Install_Tool.cmd /s

The whole point of putting the SAD3 folder in "\sources\$OEM$\$1\SAD3\" is because everything in the $1\ folder will be copied to the root of the systemdrive (C:\SAD3\) so there's no point in calling the tool using the %cdrom% variable because that just defeats the purpose of copying all the files to the drive in the first place.

Also, just in case you weren't aware, the setupcomplete.cmd file is executed at the end of the Win7 install automatically.

You could try changing the code in the setupcomplete.cmd file to the below (which is part of what I use myself), which will add a log file output so you can see what is going on.
Then post the contents of the "Install.log" file here.

@ECHO off & setlocal EnableDelayedExpansion
SET "O_LOGFILE=%systemdrive%\install.log"
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO (DIR %%i: && IF /I EXIST %%i:\sources\install.wim SET "CDROM=%%i:") >nul 2>&1
ECHO>>"%O_LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM%

:PROCESSOR
REM :: Detect OS bit-ness on running system.  Assumes 64-bit unless 64-bit components do not exist. 
SET "ARCH=64" & SET "ARCHP=x64"
IF /I NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" (
    IF NOT DEFINED PROCESSOR_ARCHITEW6432 (SET "ARCH=32" & SET "ARCHP=x86")
) 
ECHO>>"%O_LOGFILE%" 2>>&1 System architecture is %ARCH% bit.
:PROCESSOR_end

:Drivers
ECHO>>"%O_LOGFILE%" ......................
ECHO>>"%O_LOGFILE%" 2>>&1 Installing drivers.
IF /I EXIST "%systemdrive%\D\SAD3\DP_Install_Tool.cmd" (
  ECHO>>"%O_LOGFILE%" 2>>&1 SAD3 found at "%systemdrive%\D\SAD3\DP_Install_Tool.cmd"
  Start "" /max /separate %comspec% /c %systemdrive%\D\SAD3\DP_Install_Tool.cmd /s
  GOTO Drivers_end
)
IF /I EXIST "%CDROM%\SAD3\DP_Install_Tool.cmd" (
  ECHO>>"%O_LOGFILE%" 2>>&1 SAD3 found at "%CDROM%\SAD3\DP_Install_Tool.cmd"
  Start "" /max /separate %comspec% /c %CDROM%\SAD3\DP_Install_Tool.cmd /s
  GOTO Drivers_end
)
ECHO>>"%O_LOGFILE%" 2>>&1 SAD3 installer not found.
:Drivers_end

REM ::all processing finished, delete used files, and EXIT::
:CLEANUP
IF /I EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul
endlocal
REM :: (not needed) SHUTDOWN /R /T 25
DEL /F /Q %0% >nul
TechDud wrote:

Looks like my question got lost in the shuffle.
   bump --> http://forum.driverpacks.net/viewtopic. … 740#p57740

Release folder path:    ..\x64\All\M\ARECA\
Bigfoot:                      ..\x64\M\All\Areca\

Does SAD3 support this or other changes to folder tree?
  Can it cause some drivers to not be deleted when deleting other OS support?

Correct.
Bigfoot's packs break the "cleanup" function since the path doesn't fit the code search function.
The line(s) of code that do the searching look like this:

IF /I EXIST "%SystemDrive%\D\%F_CPUarch%\%F_OSType%"...<snip>

So if SAD3 is trying to delete/cleanup the "Server" folders on a x64 system, the target path would look like this:
C:\D\x64\Server\*

Any path outside that format would be skipped.

Your first line is using both forward & backslashes in the path.  That's wrong. \o/ tongue

The environment variable %systemdrive% will point to the drive letter where Windows is installed.  In most cases this is resolved to: C:
Please post the entire contents of your setupcomplete.cmd here.  Copy/paste (don't free type).  Use code tags.
Also copy/paste the entire path where your setupcomplete.cmd file & SAD3 folder is contained on your .iso

The instructions are in the first post.

Create the following folder structure to your Win7 disc:
{Win7-Disc source folder}\sources\$oem$\$1\D\SAD3 (entire SAD3 folder with all DriverPacks goes here)
{Win7-Disc source folder}\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd
Add the following code to the setupcomplete.cmd file.

@echo off
START %systemdrive%\D\SAD3\DP_Install_Tool.cmd /s
symbios24 wrote:

the script it self has the commands:

@echo off
START %systemdrive%\DP_Install_Tool.cmd /s
DEL %0

Please read the first post.  Your "start" line path is wrong.
It's expecting to execute a file that doesn't exist; C:\DP_Install_Tool.cmd /s

17

(11 replies, posted in Windows 7 tools)

Unfortunately, you're not going to be able to script DISM into installing drivers in a running OS (online) image.
DISM is meant as a tool for preparing deployment images.  Its use in a running OS is limited.
http://technet.microsoft.com/en-us/libr … s.10).aspx

The driver servicing commands can be used on an offline image to add and remove drivers based on the INF file, and on a running operating system (online) to enumerate drivers (only).

Bold emphasis is my addition.

What you want to do, you can (partially) with devcon.  http://support.microsoft.com/kb/311272
But it's clunky.
SAD doesn't scan for specific machine types, rather it uses DPInst to scan for installed hardware (HWIDs) and finds suitable matching drivers (ranked by: signed, version, date, etc.) before installing them.
You can build your own DriverPacks by using only the drivers you want from Dell and trim down the driver folder size considerably.
That would be my recommendation, same as Jeff's.

18

(50 replies, posted in Software)

Very nice!
Looks like SDI is going where I wanted to take SAD but I didn't have the time.
I'm watching...

Yes, you can add whatever drivers you want directly to your image using DISM/MDT or other tools but your "driverstore" folder will be massive and not easily purged.
I would still recommend our SAD utility but you'd have to add a runonce key to the registry to execute SAD and then have the script nuke itself and all folders once completed.  Shouldn't be too hard.

What Jeff forgot to mention in his above steps is to build an .iso after every step and do a test install in VM.
That way you can be sure that the preceding steps worked.
The worst thing for us in troubleshooting is for a user to say "DriverPacks broke my install" and then find out that he had 15 different steps with hundreds of addons/tweaks and DriverPacks was only a small part of the process. (and no backups or testing between steps).

21

(30 replies, posted in Software)

Remember, compressed archive size is only a small part of it.  Support for systems with restricted RAM is paramount.  DriverPacks would be useless on systems with limited RAM (256mb or less) if the dictionary size used exceeded the available RAM.
Read my test results from post#9 above and see for yourself.
http://forum.driverpacks.net/viewtopic. … 311#p40311

darky35 wrote:

mr_smartepants im interested in using SAD3 for a winxp x64 install ive got all my drivers for a install just wondering as nt5 only has a x86 folder what should i do so i can add mine after desktop?? is the script ok to just add a x64 folder and will it then unpack and use what is needed

No. 
DriverPacks do not support WinXP64.  Period.
SAD3 will explicitly scan for WinXP64 and exit if found.  WinXP64 is not supported.
However...
If you put your own drivers in \nt5\x64 and delete line 245 in the script it MAY work but it is unsupported.

:Method_Check
:: Double check for XP-64.  Delete the below line to force usage for XP-64 (NOT supported, you're on your own!).
IF /I "%F_OSBuild%"=="NT5" (IF /I "%F_OSbit%"=="64" GOTO Error1)

OUR project!  Not mine...OURS. big_smile

Fragbert wrote:

What do I need to do to get this to run in Win 8.1 x64? I see references to the script supporting Windows 8.1, but upon running, I get a "windows 8.1 Pro - which uses DriverPacks - not currently supported - please the exit program now" and prompt to exit

It's a simple fix...standby...

Here you go.  I forgot to upload the latest version.
http://www.mediafire.com/download/resi1 … -130825.7z

Well, color me impressed.