Page 2 of 2
Re: Network-Startup Script
Posted: Mon Nov 12, 2012 10:36 pm
by nbache
cha05e90 wrote:Of course only AmiUpdate is started, because you don't detach it from your script. So nothing will happen, until you manually quit AmiUpdate (and Simplemail afterwards). It should read:
Code: Select all
Run >NIL: SYS:Utilities/AmiUpdate/AmiUpdate
Run >NIL: APPLICATIONS:SimpleMail/SimpleMail
Run >NIL: PPLICATIONS:Jabberwocky/Jabberwocky
Or you could use WBRun to start them, that way they will still be started as Workbench programs, just like they were from WBStartup.
Best regards,
Niels
Re: Network-Startup Script
Posted: Mon Nov 12, 2012 11:03 pm
by dan.hutch
@cha05e90
Thanks! That's done the trick.
Hopefully WBStartup items will have a 'wait for network' option or similar in the future.
Re: Network-Startup Script
Posted: Tue Nov 13, 2012 12:23 pm
by MichaelMerkel
dan.hutch wrote:@Raziel
I leave all the other application to WBStartup...because running it so early may lead to more problems because of not yet loaded dependencies
I've always done the same in the past but the network never seems to be ready soon enough for WBStartup now.
Take it this checks system time against the network time server specified in Time Prefs?
in my opinion no single of that programs should "fail" just because the network is not yet started or connected.
e.g. amiupdate - if no network is "online" - well, just don't check for updated. and as soon as the network is available -> do the check.
this is how the programs *should* work. each of them.
simplemail -> well, the same.
regards...
michael
Re: Network-Startup Script
Posted: Tue Nov 13, 2012 7:57 pm
by ChrisH
cha05e90 wrote:Code: Select all
Run >NIL: SYS:Utilities/AmiUpdate/AmiUpdate
Run >NIL: APPLICATIONS:SimpleMail/SimpleMail
Run >NIL: APPLICATIONS:Jabberwocky/Jabberwocky
I would suggesting using WbRun for Workbench programs:
Code: Select all
WbRun SYS:Utilities/AmiUpdate/AmiUpdate
WbRun APPLICATIONS:SimpleMail/SimpleMail
WbRun APPLICATIONS:Jabberwocky/Jabberwocky
N.B. Also, AmiSystemRestore won't spot AmiUpdate doing anything unless it is run using WbRun. (This is something I need to fix.)