Try calling the scripts with a command to interact with the desktop.
Wpkg when run as a service it cannot interact with the desktop.
psexec.exe provides a -i option to interact with the remote desktop
(www.sysinternals.com <http://www.sysinternals.com>), this may solve the
problem.
Ironically if you run wpkg as a services under Local System with
'interact with desktop' checked the it does just that, only problem is
now you dont have credentials too access the network. Often face a
similar problem with command line only programs the dont have a silent
option, however you can get around this by piping the output to null
(ie: command.exe "install stuff"* >null)*
--
Michael Chinn
User Support Officer - Information Technology
Great Barrier Reef Marine Park Authority
PO Box 1379
TOWNSVILLE, QLD 4810
Ph 07 47500874 Fax 07 4772 6093
[EMAIL PROTECTED]
================================================================================
If you have received this transmission in error please notify us immediately
by return email and delete all copies. Any unauthorised use, disclosure or
distribution of this email is prohibited.
================================================================================
Michael Mills wrote, On 15/06/2007 00:17:
> I use AutoIT to automate application installations during login. I only use
> this for major package installation.
>
> It appears that some scripts that work when run directly (whether from a UNC
> path or a mapped drive) do not work when called from WPKG.
>
> I have attempted using both the mapped drive and UNC approach in WPKG with
> the same result, the AutoIT script runs, but when it launches the program
> using the RUN command inside AutoIT, the script fails claiming that it can't
> find the file to work on. I have noticed that these tend to be scripts
> written to be in a subdirectory and are calling a parent directory [ run
> ("../runme.exe") ]. The statement is that it can't find the application to
> run.
>
> Again, when I run it manually it runs without problems. I am confused as to
> figure out how to troubleshoot this as WPKG is obviously executing the script.
>
> Thanks for any help
> Michael
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> wpkg-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wpkg-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
wpkg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wpkg-users
