OverFlow wrote:I am not positive without looking it up...
i think dpinst automatically creates a log
even if it doesnt i am quite certain setupapi.log IS updated
so there is a full log available if needed.
as far as a log of the script...
it logs to the active window so if it hangs, you know where... 
(ummm unless you >null all the output! 
)
perhaps it would be easy enough to add somthing like...
@Echo off
REM Written by Jeff Herre AKA OverFlow rev08.05.27
REM A Script to use MicroSofts DPinst.exe with the DriverPacks.
REM Help and Support available at http://forum.DriverPacks.net
TITLE DriverPacks Installation Tool
Color 9f
Set LOG=%SystemDrive%\DP_Install_Tool.log
Echo.
Echo Searching current drive for the DriverPacks...
Echo fast detect. (is it the current drive?) >> %LOG%
FOR /f "delims=: tokens=1" %%i in ("%~dp0") do SET CDDRIVE=%%i:
IF exist %CDDRIVE%\$OEM$\$1\D goto M1Found
IF exist %CDDRIVE%\OEM\bin\un7zip.exe GoTo M2Found
Echo.
Echo Searching all drives now...
Echo alternate detection. (is it any available drive?) >> %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) DO IF EXIST "%%i:\$OEM$\$1\D" SET CDDRIVE=%%i:& GoTo M1Found
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) DO IF EXIST "%%i:\OEM\bin\un7zip.exe" SET CDDRIVE=%%i:& GoTo M2Found
Echo.
Echo The DriverPacks were not found ???
Echo The DriverPacks were not found ??? >> %LOG%
Pause
GoTo Done
:M2Found
Echo M2 Found >> %LOG%
Echo.
Echo Extracting the DriverPacks now...
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\ %LOG%
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\bin\*.7z %SystemDrive%\ %LOG%
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\ >> %LOG%
IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%\ >> %LOG%
COPY /Y %CDDRIVE%\OEM\DPINST.* %SystemDrive%\ >> %LOG%
GoTo Main
:M1Found
Echo M1 Found >> %LOG%
Echo.
Echo If you wish you may update drivers directly from the located M1 source
Echo Or you can use the DriverPacks and DP_Finisher with "Keep The Driver" option.
Echo If you choose Finisher and KTD then DriverPacks will be copied to "SystemDrive"
Echo.
SET /p TPP=Only DriverPacks or Finisher and DriverPacks? (O or F)
IF /I %TPP%==O Echo Running MicroSoft DPinst.exe without the DriverPacks Finisher now! >> %LOG%
IF /I %TPP%==O "%CDDRIVE%\$OEM$\$1\DPINST.exe" /c /s & GoTo Done
XCOPY /S %CDDRIVE%\$OEM$\$1\. %SystemDrive% >> %LOG%
:Main
Echo.
Echo Running MicroSoft DPinst.exe now!
Echo Running MicroSoft DPinst.exe now! >> %LOG%
%SystemDrive%\DPINST.exe /c /s
Echo.
Echo Running the DriverPacks.net Finisher now!
Echo Running the DriverPacks.net Finisher now! >> %LOG%
%SystemDrive%\DPsFnshr.exe
:Done
EXIT
Overflow, there is a much more efficient method for creating log files. I used it in my Presetup.cmd file that I posted here. Here is an example:
@Echo Off
Set LogFile=%SystemRoot%\MYAWESOMELOGFILE.LOG
@Call :MainScriptRoutine>"%LogFile%"
@REM * More stuff here if you want...
Goto :EOF
Exit
:MainScriptRoutine
@REM * put all of your above stuff in here (sans references to %LOG%)
Goto :EOF
Notice that I suppress the STDOutput of the pseudo-function that is being Called and stick it into a log file?
I suppose if you want that information to also be echoed back to the user, you could use Type %LogFile%.
This method will not work if your routine requires user interaction. If user interaction is required, I would recommend breaking up the routines and appending the log file using the same method, but with user interactions between each of the Calls to the routine. Personally, I put all user interaction at the beginning of the script and call the variables as needed once the script begins running.
Not saying you have to use that method, but it's a lot easier to manage than the deprecated DOS method. 
]]>
. I stand corrected then.