Vista 64-bit - Task Scheduler

March 2, 2009 at 06:27:42
Specs: Windows Vista 64
Firstly, this used to work just fine under Windows XP, but with Vista 64-bit doesn't appear to.

I have a task which I run in the Task Scheduler, and although the task runs and completes, and works, it only runs in the background, and does not ever show the CMD window which it always used to, and which I need to see in order to view output.

The box for running as hidden is unchecked, as it should be.

The program I am running is Perl, with a parameter provided to kick off a script. So, in the program field, it says "perl" and then in the parameters field, I have the location of the script. In the start-location field I have the directory of the script.

So, everything works, except for the fact that the CMD window running the script is not visible, but I really need to find a way to do it, since it used to work just fine under XP, with the exact same command.

Any assistance appreciated.

See More: Vista 64-bit - Task Scheduler

Report •

March 2, 2009 at 07:55:42
Is a -v option in the command line possible?

Report •

March 2, 2009 at 08:47:42

Thanks for the reply ... Do you mean as a "verbose" option? ....

If so, then no, not really ... (in fact -v is for version info' with Perl, but if you were referring to verbose, then I see what you were getting at) ... The script just directs all its output to screen by default, and you don't need to do anything for that to happen.

I wondered - if I fail to find a solution - whether it might even be possible to kick off the "cmd" command and then pass "perl _my_perl_script_and_parameters" to cmd ... but can't see a way to do that as yet either.

Report •

March 2, 2009 at 18:07:19
Yes, I meant verbose. I searched Google for
verbose in perl
and there were a lot of hits. One recommends using the debugger. Repeat the search to see the other results.

Report •

Related Solutions

March 2, 2009 at 19:28:52

Yes, verbose mode can be useful, but in this instance a bit of a red-herring I think, since I think it has nothing to do with the way that Vista does / does not show the cmd window when it kicks off the job.

In fact, for the purposes of this thread, you may just as well assume that the command is a batch job. It really doesn't matter too much what the job is; the fact is that Vista isn't displaying the cmd window.

Report •

March 3, 2009 at 07:03:15
I found a work around. It works if you do it in power shell, which is a free download from MS for Vista. However, it would probably be easier if you made it a power shell script instead or run power shell from a batch file. Play with it, see what works. The point is that it echos in power shell.

Report •

March 3, 2009 at 13:30:13
Okay, that sounds interesting, thank you. It's going to be a couple of days before I can play around with it, but thanks for taking the time to research and reply, I appreciate it, and I will post back on success/failure.

Report •

Ask Question