TeraByte Unlimited

the manual states .....
Log Results to File – Select this option to make Image for Windows log the details of the restore operation. By default, Image for Windows saves the log as IFW.LOG in the IMAGEW64.EXE program folder. You can use program settings or the /logfile or LogFile options to specify an alternate location for IFW.LOG. Note that Image for Windows must be able to write to the specified folder to save the log.

My program is run out of :
@e:\Program Files (x86)\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for BootIt\win>
this is where imagew is located.
I use a IFW environmental that is set to logfile:\IFD.LOG; ... among other settings.
Normally the log file is written to E:\IFD.log, but under some circumstances, the log is written to the root of the drive where the BACKUP file is being written to. This seems to happen when the the following is invoked to do a manual IFW operation : IMAGEw /ue

Here is the log file from my I:\IFD.LOG produced by imagew on I:
--------------------------------------------------------------------------
[2016-04-16 9:45:12 PM] e:\Program Files (x86)\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for BootIt\win\IMAGEw.EXE /ue
--------------------------------------------------------------------------
[2016-04-16 9:46:11 PM] Image for Windows 2.99-00
[2016-04-16 9:46:11 PM] Starting ...
IMAGEw.EXE /b /d:w6@0x1 /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-LEXAR64MB-(M)-" /max:4GiB /v /comp:11 /filetpl:"$~YYYY$-$~MM$-$~DD$-$~HHMM$-LEXAR64MB-(M)-" /hash
[2016-04-16 9:46:12 PM] Backup: Drive 6 (F:) LEXAR64MB Partition (01) 61 MiB FAT-16
[2016-04-16 9:46:12 PM] To: I:\2016-04-16-2146-LEXAR64MB-(M)-.TBI
[2016-04-16 9:46:58 PM] INFO: Total Sectors:125889 Total Allocated:88420
[2016-04-16 9:46:58 PM] INFO: 88420 Sector(s) backed up
[2016-04-16 9:46:58 PM] Validating: LEXAR64MB Partition (01) 61 MiB FAT-16
[2016-04-16 9:46:58 PM] From: I:\2016-04-16-2146-LEXAR64MB-(M)-.TBI
[2016-04-16 9:46:59 PM] Operation Completed with Error Code 0
[2016-04-16 9:46:59 PM] Stop

My program execution log file is written to e:\ :::: (normally IFW would append its log to this one)
=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-04-16 9:45:12 PM ===========================
=============================================================================
Script Name : e:\Program Files (x86)\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for BootIt\win\bui9.TBS2016-04-12 v10.10
Environment : WINDOWS - Option Locking: 0
Backup : LEXAR64MB
Comments : NONE
Run Command : IMAGEw.EXE /ue
Options : EXEC,REST,LEXAR64MB,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:\IFD.LOG;sch:1@0x2:\;;v;wco;filetpl:$~YYYY$-$~MM$-$~DD$-$~HHMM$-LEXAR64MB-(M)-
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Why is the log file being written to the root of the Backup file drive ??? And note it is the IFD.log as my environmental requests, just an unusual location !

yes, there is no drive letter on the log file you gave so it will use the
current directory when written. Using the UI and choosing a target location
by browsing to it will change to that directory.


"tas3086" wrote in message news:11403@public.image...

the manual states .....
Log Results to File - Select this option to make Image for Windows log the
details of the restore operation. By default, Image for Windows saves the
log as IFW.LOG in the IMAGEW64.EXE program folder. You can use program
settings or the /logfile or LogFile options to specify an alternate location
for IFW.LOG. Note that Image for Windows must be able to write to the
specified folder to save the log.

My program is run out of :
@e:\Program Files (x86)\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for
BootIt\win>
this is where imagew is located.
I use a IFW environmental that is set to logfile:\IFD.LOG; ... among
other settings.
Normally the log file is written to E:\IFD.log, but under some
circumstances, the log is written to the root of the drive where the BACKUP
file is being written to. This seems to happen when the the following is
invoked to do a manual IFW operation : IMAGEw /ue

Here is the log file from my I:\IFD.LOG produced by imagew on I:
--------------------------------------------------------------------------
[2016-04-16 9:45:12 PM] e:\Program Files (x86)\TeraByte Unlimited\TeraByte
OSD Tool Suite Pro for BootIt\win\IMAGEw.EXE /ue
--------------------------------------------------------------------------
[2016-04-16 9:46:11 PM] Image for Windows 2.99-00
[2016-04-16 9:46:11 PM] Starting ...
IMAGEw.EXE /b /d:w6@0x1 /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-LEXAR64MB-(M)-"
/max:4GiB /v /comp:11 /filetpl:"$~YYYY$-$~MM$-$~DD$-$~HHMM$-LEXAR64MB-(M)-"
/hash
[2016-04-16 9:46:12 PM] Backup: Drive 6 (F:) LEXAR64MB Partition (01) 61 MiB
FAT-16
[2016-04-16 9:46:12 PM] To: I:\2016-04-16-2146-LEXAR64MB-(M)-.TBI
[2016-04-16 9:46:58 PM] INFO: Total Sectors:125889 Total Allocated:88420
[2016-04-16 9:46:58 PM] INFO: 88420 Sector(s) backed up
[2016-04-16 9:46:58 PM] Validating: LEXAR64MB Partition (01) 61 MiB FAT-16
[2016-04-16 9:46:58 PM] From: I:\2016-04-16-2146-LEXAR64MB-(M)-.TBI
[2016-04-16 9:46:59 PM] Operation Completed with Error Code 0
[2016-04-16 9:46:59 PM] Stop

My program execution log file is written to e:\ :::: (normally IFW would
append its log to this one)
=============================================================================
=================== New Operation Starting
===========================
=================== Date: 2016-04-16 9:45:12 PM ===========================
=============================================================================
Script Name : e:\Program Files (x86)\TeraByte Unlimited\TeraByte OSD Tool
Suite Pro for BootIt\win\bui9.TBS2016-04-12 v10.10
Environment : WINDOWS - Option Locking: 0
Backup : LEXAR64MB
Comments : NONE
Run Command : IMAGEw.EXE /ue
Options : EXEC,REST,LEXAR64MB,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW:
u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:\IFD.LOG;sch:1@0x2:\;;v;wco;filetpl:$~YYYY$-$~MM$-$~DD$-$~HHMM$-LEXAR64MB-(M)-
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
=

Why is the log file being written to the root of the Backup file drive ???
And note it is the IFD.log as my environmental requests, just an unusual
location !

Thanks for your quick reply, the log file location change was confusing. Just a quick follow-up.

1) If the UI location that I selected for the backup.tbi file was a hidden non-windows available/configured partition/drive (no drive letter), would the log file have been written to it, or to some another location?

2) Had I done a restore rather than a backup, would the log be written to the backup-to drive location, as it was the last UI location selected?

3) Do the same log file location rules apply to the IFD and IFL versions?

Your're original response ..........
yes, there is no drive letter on the log file you gave so it will use the
current directory when written. Using the UI and choosing a target location
by browsing to it will change to that directory.

It only uses the OS for writing the files so it has to be an OS file path
which is what controls the "current directory".

To control the absolute location of the file, use a full path and not a name
only, or just use the default which will go to the program folder.

"tas3086" wrote in message news:11405@public.image...

Thanks for your quick reply, the log file location change was confusing.
Just a quick follow-up.

1) If the UI location that I selected for the backup.tbi file was a hidden
non-windows available/configured partition/drive (no drive letter), would
the log file have been written to it, or to some another location?

2) Had I done a restore rather than a backup, would the log be written to
the backup-to drive location, as it was the last UI location selected?

3) Do the same log file location rules apply to the IFD and IFL versions?

Your're original response ..........
yes, there is no drive letter on the log file you gave so it will use the
current directory when written. Using the UI and choosing a target location
by browsing to it will change to that directory.

as you are changing the logfile location, is it possible for an additional change to accept a 0x000:\filename format location. This would enable log creation to os unavailable locations.

not now you can't. has to be an os drive path.

"tas3086" wrote in message news:11421@public.image...

as you are changing the logfile location, is it possible for an additional
change to accept a 0x000:\filename format location. This would enable log
creation to os unavailable locations.