Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Hello thanks i did not saw it at all, what i put in the systemdrive?

Last edited by symbios24 (2014-07-02 17:45:24)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

its in a great big text box... how can you miss it???

mr_smartepants wrote:

@echo off
START %systemdrive%\D\SAD2\DP_Install_Tool.cmd

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

i saw this and i put exactly what i saw i did not think that the systemdrive needs to be changed sorry so i put in the script:

@echo off
START D:\sources/$oem$/$1/D/SAD3\DP_Install_Tool.cmd

OR

@echo off
START %CDROM%\D\SAD3\DP_Install_Tool.cmd

I tried both options in the iso but they did not work hmm

the last attempt i did was with :

@echo off
START %CDROM%\sources\$OEM$\$1\SAD3\DP_Install_Tool.cmd /s
DEL %0

But did not work also, but when i run the the setupcomplete.cmd manual from the disc it setup`s the drivers normal
Any Help ???

Last edited by symbios24 (2014-07-03 19:25:30)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

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

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

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?
    Pondering potential pitfalls perplexing pack person.

Also looking for a copy of SAD2 v101203 for potential win2k support.
Is "SAD1" a part of DPs_BASE?

Thank you.

Last edited by TechDud (2014-07-04 15:49:48)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

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.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

mr_smartepants wrote:

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

my setupcomplete.cmd file path is "sources\$OEM$\$$\Setup\Scripts"

and my SAD3 path is "sources\$OEM$\$1\SAD3"

my contents of the setupcomplete.cmd is

@echo off
START %CDROM%\sources\$OEM$\$1\SAD3\DP_Install_Tool.cmd /s
DEL %0

i tried by adding the extra D folder

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

its not working.

Last edited by symbios24 (2014-07-04 21:35:59)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

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

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Hi again!  How are DriverPack.ini files supported by SAD3 in NT6?
Looking to be able to process exceptions via DPs_Fnshr, if practical (not for chipset/MS though, if i have that correct).

Last edited by TechDud (2014-07-05 07:49:12)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

I have not written finisher for nt6 yet... INI files are not yet used.
This will be a top priority once i start coding again. I thought i would have more time when my kids got older???

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

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

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

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Is possible use SAD3 with drivers pack solution?

I ask that because  DriverPacks use a single folder with all 7z files from all architectures.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Sydnelson wrote:

Is possible use SAD3 with drivers pack solution?

I ask that because DriverPacks use a single folder with all 7z files from all architectures.

DriverPack Solution can only be used with the driverpacks which are included with it. It won't be able to use the driverpacks from driverpacks.net because they don't have markers(folders named 6x86, AllXP, NTx64 and etc) which help DriverPacks pick the compatible drivers.

SAD shouldn't be used with driverpacks from DriverPack Solution because SAD installs drivers via DPInst which is notoriously bad at doing its job of finding and installing drivers. Since driverpacks from DriverPack Solution are not meant to be installed via DPInst, they contain drivers which can't be installed via DPInst(and theretofore SAD).

There's another application: Snappy Driver Installer. It can be used with any driverpacks because it doesn't rely on markers to find compatible drivers and doesn't have any drawbacks which the other applications have. In fact Snappy Driver Installer can do anything SAD/DriverPacks can do and it can do it better.
Here's the thread: http://forum.driverpacks.net/viewtopic.php?id=10794

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Thanks for responding BP. Good to see you.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Hello i have a custom made winxp disc with the old driverpacks program how can i add the sad3?? i just replace the old DP_Install_Tool.cmd with the new one? and also after the setup of drivers finish it deletes the files used will if i replace the old tool with the new one it will do the same or i need to do something more that replacing files?
in final words how do a i add it to a winxp cd that already has it but it`s a very old version(2009)
and a last one which one should i use sad2 or sad3?
thanks

Last edited by symbios24 (2014-10-05 21:35:15)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

the included version of SAD works just fine with windows XP. the newer versions support newer OS's.

the newer versions don't do a better job for XP. They simply work with NT6, and the original does not.

Why do you wish to KTD (Keep The Drivers), which is supported in all versions of SAD.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

i want to put a newer version of driverpacks program since the one included is too old and it`s not working with newer driverpacks as some of the require sad3,but i dont want to go from the beggining create the windows disc again so i`m asking how can i replace the driverpacks program in the windows disc(iso) with a newer one? just replace the folder or do something more?? In General words if i want to put winxp sad3 with the driverpacks in a winxp disc in the readme file of sad3 it says:

How to add ISO's:
%WinXP-Disc%\$oem$\$1\ (entire contents of SAD3 folder with all DriverPacks goes here %systemdrive%\)
%WinXP-Disc%\$oem$\$1\DP_Install_Tool.cmd
Call the Dp_Install_Tool.cmd from winnt.sif file which will go in %WinXP-Disc\I386\WINNT.SIF

what is the call thing i don't understand what i have to put in the winnt.sif file??

i searched in the disc that has the old driverpacks program in the winnt.sif file it has this:

[GUIRunOnce]
command9="%SystemDrive%\DPsFnshr.exe"
wucdcreator="wscript.exe %systemroot%\RunOnceEx.js"

so what i put for the sad3 in this file??

Last edited by symbios24 (2014-10-07 02:16:12)

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

[GUIRunOnce]
%SystemDrive%\Dp_Install_Tool.cmd

is the short answer... BUT what NT5 packs "require" SAD3???
Related help: http://unattended.msfn.org/unattended.xp/view/web/18/


this is going to require some detailed / specific instructions from me to make work...

IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.

There will be issues with the GUIRunOnce listed above... related to timing
http://unattended.msfn.org/unattended.xp/view/web/31/
Guirunonce runs AFTER user logon as that user, RunOnceEx runs PRIOR to user logon. If AutoLogon is enabled they will seem to run at the same time tongue. We will not be able to run commands after a command that requires / forces a reboot, the rest won't run or will be ended while running wink. I have similar requirements for my UAXP install and have working scripts big_smile.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

OverFlow wrote:

[GUIRunOnce]
%SystemDrive%\Dp_Install_Tool.cmd

is the short answer... BUT what NT5 packs "require" SAD3???
Related help: http://unattended.msfn.org/unattended.xp/view/web/18/


this is going to require some detailed / specific instructions from me to make work...

IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.

There will be issues with the GUIRunOnce listed above... related to timing
http://unattended.msfn.org/unattended.xp/view/web/31/
Guirunonce runs AFTER user logon as that user, RunOnceEx runs PRIOR to user logon. If AutoLogon is enabled they will seem to run at the same time tongue.
you should not run commands after a command that forces a reboot, the rest won't run or will be ended while running wink.

Thank you for your help can i put the silent switch /S in the end also? and where i put the driverpacks?? inside the OEM\NT5\x86 folder or i leave them in the main folder of sad eg. "OEM"

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

IDK until you answer my question

IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.

Are you trying to update a DriverPacks slipstreamed XP install disc?

or are you trying to add SAD3 as an additional feature to an Install / repair disc?

Help me to help you big_smile

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

OverFlow wrote:

IDK until you answer my question

IF a nt5x86 pack is SAD3 dependent. (This should NOT be the case.)
Please give details IE links to these packs and list of affected drivers.

Are you trying to update a DriverPacks slipstreamed XP install disc?

or are you trying to add SAD3 as an additional feature to an Install / repair disc?

Help me to help you big_smile

you mean you want the page that i get the driverpacks here?

if i give you the names will be easier

this are the new driverpacks

DP_Bluetooth_MS-Misc_wnt5_x86-32_1408061.7z
DP_Chipset_wnt5_x86-32_1308271.7z
DP_CPU_wnt5_x86-32_904.7z
DP_Graphics_A_wnt5_x86-32_1401181.7z
DP_Graphics_B_wnt5_x86-32_1408051.7z
DP_Graphics_C_wnt5_x86-32_1403071.7z
DP_Graphics_PhysX_wnt5_x86-32_1408051.7z
DP_LAN_wnt5_x86-32_1408061.7z
DP_MassStorage_wnt5_x86-32_1308271.7z
DP_Misc_wnt5_x86-32_1308272.7z
DP_Modem_wnt5_x86-32_1403111.7z
DP_Phone-Mobile_wnt5_x86-32_1406041.7z
DP_SmartCard_wnt5_x86-32_1403281.7z
DP_Sound_A_wnt5_x86-32_1406011.7z
DP_Sound_B_wnt5_x86-32_1406021.7z
DP_Sound_C_wnt5_x86-32_1406011.7z
DP_WebCam_wnt5_x86-32_1405281.7z
DP_WLAN_wnt5_x86-32_1408061.7z
DP_Graphics_ATi-TV_wnt5_x86-32_1310291.7z
DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z

and the old driverpacks i had before for xp are those that already available in the latest,in the driverpacks download page

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

All of those packs require SAD3??? I don't think so. What did i miss?

edit.....

did Techdud pack them with newer 7zip?... ack!

See this topic,

http://forum.driverpacks.net/viewtopic.php?id=5928

if he did we simply update the DLL on your disc, no problem.

Last edited by OverFlow (2014-10-07 05:58:10)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

Did you make any changes to your XP install disc after you added DriverPacks?

Did you fail to make a copy of the disc from immediately before you added DriverPacks?

if the answer to either of these questions is yes then it is unlikely that your mass storage drivers can be updated.
the other drivers may be updated simply by replacing them with newer versions big_smile (woo hoo)

it's that simple for all but mass storage big_smile

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

OverFlow wrote:

Did you make any changes to your XP install disc after you added DriverPacks?

Did you fail to make a copy of the disc from immediately before you added DriverPacks?

if the answer to either of these questions is yes then it is unlikely that your mass storage drivers can be updated.
the other drivers may be updated simply by replacing them with newer versions big_smile (woo hoo)

it's that simple for all but mass storage big_smile

i did not test my xp disc yet i have put the driverpacks only (without sad3) i will test them with the old dpinstall tool

another question are this driverpacks enough to detect any vga card old or new

DP_Graphics_A_wnt5_x86-32_1401181.7z
DP_Graphics_B_wnt5_x86-32_1408051.7z
DP_Graphics_C_wnt5_x86-32_1403071.7z

or i also need third party`s driverpacks too like this one for example??

DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z

and last i only update the 7-zip32.dll file replacing the old one right ??

thanks

Re: Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7)

i tested two of the listed packs, and the new dll was not required. techdud left them as they should be packed for DriverPacks BASE XP slipstream. Try it just replacing the packs first. (except mass storage, mass storage must be slipstreamed with DriverPacks BASE)

yes if you want to be able to support any video card, even really really old ones then add the 3rd party DriverPack.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.