[wpkg-users] Dropbox autoit script problems

Martin Tille edv at gruene.de
Fri Mar 18 12:53:00 CET 2011


> Hi Martin,
>   Yes it appears that the autoit clicking isn't working when using wpkg.  I've checked event viewer log and cannot see any problems.  Is it possible to get a more detailed log from wpkg?
> Thanks
> Paul
> 
> Hi Paul,
> 
> please answer to the mailinglist too.
> If I understand it right, the script is starting but autoit isn't
> "klicking" the way it should be? Have you checked the event log, there
> are additional informations when wpkg is running quiet (Start -> Run
> eventvwr.exe).
> 
> Martin
> 
>> Hi Martin,
>>   I added the debug line and this is the result.  
>>
>> 2011-03-18 10:20:00 -> Starting WPKG on startup
>> 2011-03-18 10:20:00 -> Before create shared memory: successfuly done.
>> 2011-03-18 10:20:00 -> Create shared memory: successfuly done.
>> 2011-03-18 10:20:00 -> Set script security context: successfuly done.
>> 2011-03-18 10:20:00 -> Network resource required
>> 2011-03-18 10:20:00 -> Network resource: successfuly connected
>> 2011-03-18 10:20:00 -> Starting script action execution
>> 2011-03-18 10:25:14 -> Script action execution done.
>> 2011-03-18 10:25:14 -> Script execution: successfuly done
>> 2011-03-18 10:25:14 -> Network resource: successfuly disconnected
>>
>> You will see that it was sat on installing dropbox.  After 5 mins I killed autoit and the dropbox installer wpkg continued with an exit code returned non-successful value (1) on the command.
>>
>> Paul
>>
>> -----Original Message-----
>> From: wpkg-users-bounces at lists.wpkg.org [mailto:wpkg-users-bounces at lists.wpkg.org] On Behalf Of Martin Tille
>> Sent: 18 March 2011 09:43
>> To: wpkg-users at lists.wpkg.org
>> Subject: Re: [wpkg-users] Dropbox autoit script problems
>>
>>> Hi,
>>>
>>>   I followed the really good DropBox install package using AutoIt.  The
>>> problem I have is that I cannot get it to complete in WPKG.  It just hangs.
>>>
>>> If I run it from a DOS box it completes.  I have tried using both the
>>> SOFTWARE variable and replacing that with my full UNC path and manually
>>> it completes but using the WPKG client it doesn't.
>>>
>>>   Anyone got any ideas?
>>>
>>> Thanks
>>>
>>> Paul
>> Hi Paul,
>>
>> not without any debug messages. If you use the wpgk-client programm you
>> can set up debug and a debug file with wpgkinst.exe. If you use a self
>> scripted solution use the /debug flag and see about what it complains.
>>
>> Martin
Hi Paul,

/logLevel:[0-31]

Level of detail for log file:
use the following values:
Log level is defined as a bitmask. Just sum up the values of each log
severity you would like to include within the log file and add this
value to your config.xml or specify it at /logLevel:<#>.
Specify 0 to disable logging.
	  1: log errors only
	  2: log warnings
	  4: log information
	  8: log audit success
	 16: log audit failure
Default is 0 which will suppress all messages printed before log level
is properly initialized by config.xml or by /logLevel:<#> parameter.

/log_file_path:<path>
Path where the log files will be stored. Also allows specifying an UNC
path (e.g. '\\server\share\directory'). Make sure the path exists and
that the executing user has write access to it.
NOTE: If you set this parameter within config.xml please note that you
need to escape backslashes: '\\\\server\\share\\directory'.

Martin

P.S. I'm always confused if top posting or bottom posting.



More information about the wpkg-users mailing list