Maybe -- but that's not as clean as startprogafterrouter because (a) the router startup time isnt a defined period so you run the risk of too long or too short and a future router config or firmware update breaking things, and (b) you would be subjecting yourself to that penalty every time the program started even if the router was already fully up (e.g. when loading changes to the program)

Its kind of like the old BiAmp Audia modules that enforced a 60 (or was it 120) second initialization delay because someone put the DSP on a power sequencer and rather than handle that in a sane way the fix was to make everyone wait a minute or two every time the program loaded before the module even started to do anything useful?

Get