Automatic starting of applications under W'

[bojan]

With SoundStepper software (and other other potential components of the future system in mind, like ASCOM, EK box, CdC, remote operation and so on), I am wandering how to automatically start all this after power up, with minimum intervention?
In old days batch file (Autiexec.bat) would do the job perfectly, but with windows, I never did anything like this.
Any help/idea is highly appreciated !

[supernova1965 (Warren)]

Hey Bojan,

In the windows start menu there is a folder labled startup if you put a shortcut to the program you want to start with windows it will start on Windows loading

[bojan]

Thanks Warren... of course I knew about startup but I didn't realise this will do this job .. getting old..

[[1ponders] (Paul)]

Ooooh Thanks Warren Handy one to know.

[bojan]

There is still an issue of passing parameters to application(s) (if this thing exists in W's at all..) and sequencing..

[rally]

Bojan,

You can still pass parameters (assuming that the app has been designed to accept them) in the shortcut
Where you specify the program to run, just add the parameters at the end

Windows allows a variety of scripting methods from simple text (like a DOS based batch file) that you manually launch or put into the start menu so it starts like autoexec.bat did, or you can to to GUI based script writers that can perform relatively powerful functions easily without programming skills through to Visual Basic scripts that can be as simple or as complex as you like . . etc etc
Windows can automatically execute a VBS script.

The Task Scheduler in Control panel also allows you to do this by creating a script via a simple GUI interface and follow the steps and specify when it is going to run - or how often it will run with parameters and other controls etc - this way it happens automatically.

Sequencing your apps in a script could be as easy as listing them in the order you want them to run, or creating a scheduled task that includes them.

In its simplest form it can nothing more than the batch files you are used to.

I am sure you can Google scripting with whatever version of windows you are running and get lots of examples.

Cheers

Rally

[bojan]

Hi Rally, Thank you - this is what I needed (to start doing something).
I will certainlt google and have a look.

In the meantime, and and assuming the ASCOM, CdC (or Stellarium) and other stuff is used by many people to control their mounts and other associated equipment, could someone post a specific example of how this is done?
I am mostly interested in the case of power failure and automatic recovery of the system.

Cheers,
Bojan

[g__day (Matthew)]

You can also use the register by using Run commands in the right spot, but a script as described above is likely the most user friendly idea.

You might be advised to have some wait states or status checks when you launch a program.

So an option is :

First of all launch the Group Policy Editor by clicking Start, then type gpedit.msc and hit Enter. Now navigate to the User Configuration > Windows Settings > Scripts(Log on/Log off) option

Double click the Logon option from the main window and click the Add button in the Logon Properties dialogue box.

Now add the program which you wish to start up in the Script Name, and set the Script Parameters option as you require.

Now I'm not sure if that runs scripts aschronously (in the background - without causing things to wait) and can see all network drives (only important if necessary programs / data aren't stored on the PC you are refering to and if the scripts run before any user signs on!

Also read http://stackoverflow.com/questions/6...user-logged-on

[Barrykgerdes]

All good info
A little more on the old DOS batch file
Win 7 does not always respond to *.bat it prefers *.cmd
Win 7 also does not like some obscure suffixes that are used by msys to store commands.

Barry

PS I am more interested in stopping startup commands that are added to the registry by spam type programs.