TeraByte Unlimited

Hi - I run IFW on via a scheduled .BAT file in the middle of the night on an XP (Sp3) machine. Sometimes in the morning there's the error

"invalid option /b".

I run the same script by left-clicking it and it runs fine.

Does that resonate with anyone? Obviously /b (it's the first option) is a valid option. Any idea what's tripping IFW up. (this is only since I upgraded to 2.69).

I don't expect anyone to solve, but debugging tips would be helpful.

thanks
/j

Can you post what the IFW log shows for the task when it fails and when it completes successfully?

[ 2/29/2012 3:15:11 am] /b /uy /enc:1 /pw:xxxx /d:w0@0x1 /f:E:\backups\full\c_6_ful\c_6_ful0 /max:698MiB /v
[ 2/29/2012 3:15:11 am] Invalid parameter: /b
[ 3/01/2012 4:50:57 pm] Program exiting with error code 61
--------------------------------------------------------------------------
[ 3/01/2012 4:54:04 pm] /b /uy /enc:1 /pw:xxxx /d:w0@0x1 /f:E:\backups\full\c_6_ful\c_6_ful0 /max:698MiB /v
[ 3/01/2012 4:54:04 pm] Image for Windows 2.69 (GUI)
[ 3/01/2012 4:54:04 pm] Starting ...
imagew.exe /b /uy /d:w0@0x1 /f:"E:\backups\full\c_6_ful\c_6_ful0" /max:698MiB /v /enc:1

Not sure it helps 8-}
/j

How often does the error occur?

Is the computer already running when the task runs or is it waking up to run it?

What is the IFW command line from the BAT file (mask out your password)?

What version of IFW were you using before you installed 2.69?

Is the task being launched from the Windows Task Scheduler or is it some other scheduler?

What type of drive is E: (internal, USB, eSATA, etc.)?

it's happened every time the job tried start from the scheduler (2 weeks now). Computer is running 24x7. No sleep, standby, etc. (it's a desktop)

"D:\Program Files\TeraByte Unlimited\Image for Windows\V2\imagew.exe" /b /uy /enc:1 /pw:xxxx /d:w0@0x1 /f:"E:\backups\full\c_6_ful\c_6_ful0" /max:698MiB /v

before 2.69 - not sure, probably 2.4x or 2.51?
Windows Task Scheduler
E is a partition of the same internal SATA drive as C and D (because of old history, Windows is on the D drive, and the C drive is a small (primary) partition.
/j

The only version that doesn't take /B is the restore only version (tbirest).
Try changing /b to /v and see if it then says one of the other options are
invalid.

"jeffw_00" wrote in message news:1604@public.image...

it's happened every time the job tried start from the scheduler (2 weeks
now). Computer is running 24x7. No sleep, standby, etc. (it's a desktop)

"D:\Program Files\TeraByte Unlimited\Image for Windows\V2\imagew.exe" /b
/uy /enc:1 /pw:xxxx /d:w0@0x1 /f:"E:\backups\full\c_6_ful\c_6_ful0"
/max:698MiB /v

before 2.69 - not sure, probably 2.4x or 2.51?
Windows Task Scheduler
E is a partition of the same internal SATA drive as C and D (because of old
history, Windows is on the D drive, and the C drive is a small (primary)
partition.
/j

Hi - I don't think I've explained the problem. (and sorry for the delay in responding, life's had the better of me recently).

IFW is invoked from a DOS .BAT script (I've supplied the relevant lines of the script previously). This batch script is called from task scheduler. If I go into task scheduler and tell it to run it now, it runs fine. However, when it runs in the middle of the night, triggered by task scheduler, I get the error. The only difference is what is triggering it. This happens only in the newest release. To do your experiment I would have to set up a script that is called by task scheduler, and if it failed i don't think it would tell us anything we don't know. It ALWAYS works when, through the menus, I select start -> setting -> control panel -> task scheduler -> [backup job] -> run

But when there is a timed start to the job, it now -always- gives me the error.

There is only one account on the machine, and it's always logged in. So the job always starts under the same credentials.

very puzzling. But I'm sure you guys will solve it. you're the best 8-}

/j

delete the task and recreate it or use the schedule backup option in the
program to set it up. /b, provided it's not using some foreign character
set for / or b (hex dump the ifw.log to check for that), is accepted except
for in the restore only version. Of course if you have /b in your password,
that will be a problem, you'd need to enclose it with quotes. Clicking "run
now" should be no different than when it runs other than the user being
signed in/running in foreground.


"jeffw_00" wrote in message news:1741@public.image...

Hi - I don't think I've explained the problem. (and sorry for the delay in
responding, life's had the better of me recently).

IFW is invoked from a DOS .BAT script (I've supplied the relevant lines of
the script previously). This batch script is called from task scheduler.
If I go into task scheduler and tell it to run it now, it runs fine.
However, when it runs in the middle of the night, triggered by task
scheduler, I get the error. The only difference is what is triggering it.
This happens only in the newest release. To do your experiment I would have
to set up a script that is called by task scheduler, and if it failed i
don't think it would tell us anything we don't know. It ALWAYS works when,
through the menus, I select start -> setting -> control panel -> task
scheduler -> [backup job] -> run

But when there is a timed start to the job, it now -always- gives me the
error.

There is only one account on the machine, and it's always logged in. So the
job always starts under the same credentials.

very puzzling. But I'm sure you guys will solve it. you're the best 8-}

/j

ok - I uninstalled/reinstalled everything and deleted/recreated the task - we'll see what happens when it next triggers...

thanks
/j

So I deleted the task from task manager, uninstalled IFW. Downloaded a new copy of IFW 2.69, installed it. re-added the task, and power-cycled the computer. Last night it tried to run for the first time. I looked this morning, and IFW was running, and in front of it was a little grey window

X Invalid parameter : /b

So I did start -> control panel -> scheduled tasks -> full_backup -> run

and it started up and runs fine.

I am so baffled.... but perhaps it's not an IFW issue....

/j