TeraByte Unlimited

get rid of the echo off in that script as well as the backupscript1.cmd and
backupscript2.cmd .. add a pause at the end, setup the task scheduler to
interact with desktop and use the same user account, then launch it which
launches cmd.exe and opens a window so you can read what's there.

"tanstaafl" wrote in message news:[email protected]...

TeraByte Support(PP) wrote:
> Is the script file being blocked from running (e.g. by system security)?

No.

> If you can't tell any other way, add something to the script so you can
> find out if it's running. For example, output a "dir" listing to a file:
> @echo off
> dir c:\windows > c:\output.txt
> call backupscript1.cmd
> call backupscript2.cmd

Ok, tried this, and indeed, c:\output.txt is there and contains the dir
listing for c:.

But... nothing else happens. A cmd prompt window doesn't open, imagew64.exe
never launches, and the Task Scheduler says the Task was initiated and
started...

Also - maybe you missed the part where the individual scripts run just
fine??

The Task Scheduler is working. When I change the Task to only run one of the
individual .cdm files, that Imaging Task runs fine.

The problem *only* happens when I use the simple .cmd file that calls the
other two individual .cmd files (first one images the C:, the second one
images the D:).

I don't see how this can be anything other than a problem with running two
scripts from one?

Have you even tested this?

Have you tried changing the current directory to the folder with the scripts? When you run an Administrator Command Prompt the default path is usually C:\Windows\System32. Unless the scripts are in that location they wouldn't be found. If that's the case and you could see the Command Prompt window, you should be seeing an error message.

Try this:
@echo off
cd /d x:\myscripts
call backupscript1.cmd
call backupscript2.cmd

Where "x:\myscripts" is the path to the script files.