Problem in using the RunOnceEx.cmd

  • Thread starter Thread starter karthikaravind
  • Start date Start date
K

karthikaravind

Hi,
I am using the cmdlines.txt and RunOnceEx.cmd method to install certain
applications.

unattended installation of XP gets over and in the first log on it executed
the RunOnceEx.cmd
and it says C:\install\FR30.msi is not found

I have placed the cmdlines.txt and RunOnceEx.cmd in $OEM$ folder

---------------cmdlines.txt start-------------------------------
[COMMANDS]
"RunOnceEx.cmd"
---------------cmdlines.txt end-------------------------------
---------------RunOnceEx.cmd start---------------------------
@echo off

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing Applications" /f

REG ADD %KEY%\005 /VE /D "Foxit Reader" /f
REG ADD %KEY%\005 /V 1 /D "%systemdrive%\install\FR30.msi /qn" /f

REG ADD %KEY%\050 /VE /D "Importing Registry Tweaks" /f
REG ADD %KEY%\050 /V 1 /D "REGEDIT /S %systemdrive%\install\regtweaks.reg" /f

EXIT
---------------RunOnceEx.cmd end---------------------------
These are the contents of the respective files.
I have placed FR30.msi and regtweaks.reg under $OEM$\$1\install folder

I could see the RunonceEx.cmd getting executed
But it says FR30.msi is missing
The registry tweaks are also not getting added.but no error message is
displayed

Some one please help me.

I am using win xp pro sp3 (slipstreamed).
I am testing this with VIrtual PC
 
Setting up our one image fits all hardware/locations at work I seem to
recall there being a problem with pathing with this method? Don't quote
me but I'm pretty sure we had to have everything that was required in
the same directory as cmdlines.txt and what it's calling.

BTW, not sure why you're doing all that with the registry, we use this
method to install a few agents on our deployed images prior to initial
startup (Altiris aclient specifically so that the 'job stream' can
continue for a full image/custom app deployment from a single drag/drop
for the desktop support guys), and we're not messing with the registry,
just running it all direct from the cmd file called by cmdlines.txt

One last comment, but sort of unrelated... Virtual PC? <spit spit>, just
use the VMWare solution, much nicer! :)
 
Remove %systemdrive% and hard code it c:\install\FR30.msi as a test.

I seem to remember and issue with the systemdrive variable. In mine I set
HOME=C:\install right after I set Key= and that seems to work..

i.e., REG ADD %KEY%\005 /V 1 /D "%HOME%\FR30.msi /qn" /f
 
Back
Top