1 Feb 2011 11:45
Re: Scheduler type 'startup' only run once per Windows session?
I've now been able to pinpoint this problem (i.e. commands scheduled for "startup" are not run) to when PowerPro is restarted after crashing. That means that when PPro is closed normally by shutting down the system or closing it manually, evertything works fine, but when it crashes and I manually restart it, it won't run any startup commands (at least on my system). Can anyone confirm this? My monitor list now picks this up and runs the startup script belatedly so that I can avoid any error messages, but I think this would still be worth fixing if possible. Thanks Phil --- In power-pro@..., "brucexs" <brucexs <at> ...> wrote: > > They run every time PowerPro starts, at least in all my tests. Although these tests are on XP, I don't think this function can depend on the Windows version. > > Possibly you are using different command lines with different pcf files from the startup group when you restart manually? > > > --- In power-pro@..., "phkiefer" <philippkiefer <at> > wrote: > > > > I use a 'statup' scheduler to run a script that, among other things, defines some global variables used by hotkeys etc. This all works fine the first time PowerPro is run, but when it crashes and I re-run it, PowerPro does not seem to execute the startup script and I get error messages about undefined variables until I manually run my startup script from the command line. > > > > My conclusion would be that 'startup' schedulers are only run the first time PowerPro is launched in a given Windows session, but not subsequent times. As this seems to contradict the information in the help(Continue reading)
RSS Feed