TeraByte Unlimited

I'm using IFW 2.20c. I've had a working setup for the past 4 years - I was backing up my system to a drive on our server. For several reasons I decided to add an external drive to my system and use that for the backup instead of the server drive. It works fine, extcept that nothing is written to the log file.

Here is a my command line:
"C:\Program Files\TeraByte Unlimited\Image for Windows\V2\imagew.exe" /b /uy /um /d:w0@0x2 /f:"F:\Blackwell C\Sunday (Full)" /v

And here are the relevant ini file lines:

[OPTIONS]
LogFile="F:\Log.txt"
PHYLockUseReg=0x1

The log file (log.txt) is there, but no new data has been written to it since I moved it from the network drive. Also, there is no ifw.log file showing up anywhere.

Any suggestions?

Thx

Is your posted command line from a script file (.BAT or .CMD)? Does it work if you specify the logfile option on the command line (e.g. /logfile:"F:\Log.txt")?

Does the INI file have anything set for LogLevel or SaveLog? If so, what?

Does it write to the log file when using the GUI? Is the Log Results to File option selected?

Is there a specific reason you're still using 2.20c? The current version is 2.70.

also check permissions....

"jamos" wrote in message news:1902@public.image...

I'm using IFW 2.20c. I've had a working setup for the past 4 years - I was
backing up my system to a drive on our server. For several reasons I decided
to add an external drive to my system and use that for the backup instead of
the server drive. It works fine, extcept that nothing is written to the log
file.

Here is a my command line:
"C:\Program Files\TeraByte Unlimited\Image for Windows\V2\imagew.exe" /b
/uy /um /d:w0@0x2 /f:"F:\Blackwell C\Sunday (Full)" /v

And here are the relevant ini file lines:

[OPTIONS]
LogFile="F:\Log.txt"
PHYLockUseReg=0x1

The log file (log.txt) is there, but no new data has been written to it
since I moved it from the network drive. Also, there is no ifw.log file
showing up anywhere.

Any suggestions?

Thx

Thanks Paul. Adding the /logfile:"F:\Log.txt to the command line fixed the problem. I am running this from the scheduler, the command line is used there.

Only using 2.20c because that's what was current when I purchased it; will upgrade soon if I can find the time.

Jim Johnson
Practice Manager
Animal Health Associates
http://www.animalhealthassociates.org
541-345-1544