Scheduler calling a schedule but dynamic parameters

[Edwin Knoppert]

To bad..
The lnk file is executed but not terminated (1 min).
Seems it uses it similar to a bat file.

I guess i have to terminate the process by using an additional app.
(The app which creates the link)

[Edwin Knoppert]

The filename change seems to work!

Just pick any file (the filedialog is forced) and then change to the lnk filename.
I just modified the lnk and executed again, the app executed by the scheduler used this new parameters fine.

Thanks!

PS, the lnk is written by another (PB) app and can be executed at other times.

[Edwin Knoppert]

Windows scheduler can start the PC from standby mode, that's a benefit.
Of course i could then do the rest but like i said, don't want to handle the exitprocess stuff myself.
Unless there is no better solution then exitprocess (API).

I'll try the 'typing' suggestion.

[Dave Biggs]

I tried to set it to call a shortcut file (.lnk) but it reads the lnk file and uses the settings from it.
It should execute the lnk and not explorer it.

Try typing in the target instead of browsing to it when editing the Scheduled Task eg..

"C:\Documents and Settings\Dave\Desktop\EditPlus 3.lnk" params

(Browsing to the link would yield "C:\Program Files\EditPlus 3\editplus.exe" in the task 'Run' box)

[Michael Mattias]

Instead of windows sheduler, write your own application to call CreateProcess with dynamic parameters at correct times?

Or put the "do something now" (on schedule) into your already-running application?

[Edwin Knoppert]

The scheduler starts and ends the application set.
If i want to use dynamic commandline parameters i could use an intermediate application.
That's not my first goal, i rather would instruct the scheduler or via other way the application to use the new commandline parameters.

If i use an extra app i need to terminate the app, i don't like that at this time.

[Michael Mattias]

???

How do you know it's "done," so you know it's time to terminate it; unless it's done, in which case you don't have to terminate it?

Me, I'd just CreateProcess or ShellExecuteEx, providing a command line parameters in the appropriate position and wait on the process object to be signalled.

Of course, the PB SHELL statement does that.

Inquiring Minds ... are confused.

MCM

[Edwin Knoppert]

I have a program which requires a dynamic commandline parameter.
The Windows scheduler calls this app at some point and terminates it when done.
I tried to set it to call a shortcut file (.lnk) but it reads the lnk file and uses the settings from it.
It should execute the lnk and not explorer it.

It's not my goal to use an intermediate application which terminates the actual application when done (the target app isn't written by me)

Any idea?