You are not logged in. Please login or register.
I am just curious how other people are doing this.
what i have done is entered into
sysprep.inf
[GUIRUNONCE]
command0="C:\SAD\DriverPacks.net\DP_Install_Tool.cmd"Is there a better way?
Last edited by JustusIV (2009-07-03 07:42:28)
When i did this, i had to hit cancel on all the driver found new hardware prompts before it would proceed.
Still looking for tips.
Last edited by JustusIV (2009-07-04 06:24:33)
RunOnceEx is probably better and how I coded it in the alpha of BASE 
How about calling DP_Install_Tool from a different batch file?
I would like to run DP_Install_Tool then do some things via batch after it completes but it seemed to just take over the batch file and the rest would never run 
Maybe i as doing something silly i dont know.
P.S.
Thanks for all the help you have sent my way.
Maybe i should tell you guys how i am trying to run my universal image and you can tell me if there is better ways to do it.
use the command "Call" to run the script from a batchfile
Call %SystemDrive%/DriverPacks.net/DP_Install_Tool.cmd
that way it will return to your batchfile after the script exits.
Perfect, that's what i did not do. I will give it a whirl. Thank you!!!!
use the command "Call" to run the script from a batchfile
Call %SystemDrive%/DriverPacks.net/DP_Install_Tool.cmd
that way it will return to your batchfile after the script exits.
This did not appear to work. Here is what i have. My file simply just ran the DP_Install_Tool and never ran the rest of my code. I have been using the file without the first call for a long time with no issues. Any ideas on what i am doing wrong?
firstboot.cmd
Call C:\WINDOWS\system32\DP_Install_Tool.cmd
@Echo off
c:\windows\system32\wsname /N:$SERIALNUM
reg add "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Runonce" /V runforme /d c:\windows\system32\secondboot.cmd
c:\windows\system32\shutgui /l /y /t:60 /rTry this alternate...
Start /wait "%SystemRoot%\system32\DP_Install_Tool.cmd"
You did not really put the driverpacks in System32 did you? Oh my... M1 or M2?
PS always use %SystemRoot% instead of hardcoding C:\Windows - That is a very bad habit to get yourself into .
Once again i will have to give this a whirl tomorrow as i am not at work. I admit hard coding C:\windows is a bad idea but....
Whats the big deal on the system32 dir? I have started a habit of throwing a bunch of stuff in there, very handy for cmd tools etc
BTW m1. i dont really understand the difference between the two for SAD.
about a gig of disc space more required for M1 however you can use devpath for KTD like features...
However since after the install the drivers are not needed and should be deleted it really doesn't matter where you put them since you will delete them... I would not put anything i was going to delete in system32... just in case
Appears to work accept i needed a title in there.
start /wait "Insert title here" "%SystemRoot%\system32\DP_Install_Tool.cmd"Although i don't really know if i need this because of the issue of "Found New Hardware Wizard".
see post
http://forum.driverpacks.net/viewtopic.php?id=3859
Last edited by JustusIV (2009-07-08 01:10:07)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.015 seconds, 10 queries executed ]