kev_147 Posted November 29, 2006 Share Posted November 29, 2006 (edited) I have an automated build DVD and launch WPI via RunOnceEx using the following command line:%SYSTEMROOT%\System32\mshta.exe \"%CDDRIVE%\$OEM$\WPI\WPI.HTA\" options=useroptions.js config=config.js check=Corporate_Build timer=30Now the above command used to work in earlier versions, but now WPI launches, but doesn't automatically set the timer to 30 seconds and choose the Corporate_Build configurations.After testing I have found that if I put the WPI folder at the root of the DVD then the following command line works: (Note: $OEM$ has been removed from the command line) %SYSTEMROOT%\System32\mshta.exe \"%CDDRIVE%\WPI\WPI.HTA\" options=useroptions.js config=config.js check=Corporate_Build timer=30Does anyone have any ideas why this is happening? Is it happening to anyone else?I don't mind having the WPI folder at the root of the disc, but am concerned that there may be a bug in there somewhere and thought I should bring it to light. Edited December 8, 2006 by kev_147 Link to comment Share on other sites More sharing options...
AlBundy33 Posted November 29, 2006 Share Posted November 29, 2006 At first you should try the following command%SYSTEMROOT%\System32\mshta.exe "%CDDRIVE%\WPI\WPI.HTA" options=useroptions.js config=config.js check=Corporate_Build timer=30(removed the \ after WPI.HTA)If this doesn't work you could try the following way to start WPI via RunOnceExCreate WPI_RunOnceEx.cmd in that directory where WPI exists.Add the following line to this file:REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\999" /v 1 /d "%~dp0WPI\WPI.hta" /fAnd add the following lines to your cmdlines.txt in $OEM$-directory.[COMMANDS]"\path_to_cmdfile\WPI_RunOnce.cmd"Good luck.Al Link to comment Share on other sites More sharing options...
mritter Posted December 1, 2006 Share Posted December 1, 2006 You have to specify the full path for the options and config files. ....wpi.hta options=c:\path\path\options.jsand so on. Link to comment Share on other sites More sharing options...
kev_147 Posted December 8, 2006 Author Share Posted December 8, 2006 (edited) Thanks for you comments guys, appreciated.I am not convinced though. I have WPI working with parsed commands in the example below and that doesn't state the full path. Note for Albundy33, the backslash on the end of WPI.Hta was not plain text, it was a break out within the registry command, ie informed the registry to treat everything between the 1st and 2nd \" as being within quotes.My apologies as I forgot to type in the 1st \" in my original post, have just edited it now. duh!!*******************************************************REM ========================================REM | This Section determines the CDROM DriveSetLocal enableextensionsSET CDDRIVE=%~d0REM=========================================REM | This Section configures the variables used within this scriptSET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceExSET ADDITIONAL_APPS=%KEY%\410REG ADD %KEY% /V TITLE /D "Phase 4" /fREG ADD %ADDITIONAL_APPS% /VE /D "Additional Applications" /fREG ADD %ADDITIONAL_APPS% /V 1 /D "%SYSTEMROOT%\System32\mshta.exe \"%CDDRIVE%\WPI\WPI.HTA\" options=useroptions.js config=config.js check=Corporate_Build timer=30" /fEndLocalEXIT********************************************************** Edited December 8, 2006 by kev_147 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now