I agree it does sound like the actual kicking off of the task appears to be
working - any idea what would cause the window to not render? As thereis no
listing for the running task in the Task Manager Applications tab (only in
the processes tab) I can't get to the application that's executing.
I'll verify what I posted this morning later today when I get access to the
machine.
BTW - when you say run line, you want the command line text that I'm
entering right?
Yessir. The Run line for your ST.
If you launch the ST it should show up in TM as a process and it is
running. Trouble is, we don't know what you are running (yet) and may
be able to be more helpful if we knew - unless it is top secret. Some
things have special command line options to run as a ST wilently and
with no interaction needed.
This doesn't 'splain why it used to work unless your old SP2 comes
into the mix somehow.
Another thing you can do (I need to add this to my copy/paste ST not
so popular notes):
If your login account has no PW and you set up your ST to use some
other account with a PW, add a PW temporarily to your account and
change the credentials of your troublesome ST to run with your login
and PW and try to run it while you are logged in withthe same account,
then see if you "see" it and can interact with it. You can remove the
PW on your account later. Not reboot or anything required. Add a PW,
change the ST to match, test.
This is why I like to use CMD. Do the test with CMD (or calc). It
runs and keeps on running until you stop it giving you time to poke
around and figure out what is going on. There is no batch file needed
- it runs and goes away - big deal. You now know how to create a
batch file! You need something that runs and keeps running until you
stop it.
You have everything you need already, don't add more variables to the
mix...
