Multiple Destination Directories Possible?

[binar]

Fellow Forum Members,
I have to screen capture 10 different windows and each PDF screen capture needs to go to it's own screen capture unique destination directory.

IrfranView does not support multiple destination directories in the Capture Settings Dialogue window. Can anyone out there recommend an alternate app that does support multiiple screen capture directories or a way I can make IrfanView support multiple screen capture directories?

I tried installing multiple installations of IrfanView with each install setup with a unique destination directory, but I discovered that IrfranView does not work very reliably with multiple installs. Any help will be greatly appreciated.

[matera]

You can use multiple INI files. That might help.

[us marriage]

Multiple Destination Directories Possible?

I know that subject has been mentioned a lot of times, but after reading through the topics, I have not found a solution to my task.

I use TC on a network with 100+ computers, and very often I have to copy a folder to numerous folders on various pc's on the network. Let me try to explain:

The destination folders are always the same on the network pc's i.e.
\\pc1\folder1
\\pc2\folder1
\\pc3\folder1
etc.
etc.

The ideal solution for me would be to have my source folder in one of the TC panes, select it, and the press a button (on the button bar) that would run a script to excecute the above copy action.

I know how to add a button to the bar, but I haven't figured out the script or command yet.

Can anyone lead me in the right direction?
_________________

[Skippybox]

You could place a shortcut to a batch file script such as this one in your SendTo folder. Then, just make a selection (or multiple selection) of files and/or folders, and choose the shortcut from the shell menu.

@echo off
:getfile
if "%~1"=="" goto end
if "%~n1"=="%~nx1" (xcopy %1 "\\server\share\folder\%~n1" /e /i /q) else xcopy %1 "\\server\share\folder\" /q
shift
goto getfile
:end
echo All done.
pause

Basically, the script shifts through your selected files/folders and one by one determines which they are in order to copy them correctly. You would need to expand it to accommodate all your network computers by inserting lines like this one:

if "%~n1"=="%~nx1" (xcopy %1 "\\server\share\folder\%~n1" /e /i /q) else xcopy %1 "\\server\share\folder\" /q

There are many other things to decide, like what feedback info you want and how the folders/files should be copied. I recommend examining the switches available for xcopy, in case you need to add/change any. You may also want to hide the console window. Due to the fact that this is a network application, you should test it carefully to make sure there are no problems.

Not sure how many terminals you are copying to, but you could map them to a drive letter for easier paths.

I am not familiar with TC, so you would need to make any adjustments necessary, if you want to integrate it with that program using selection parameters.

[divorce certificate]

Multiple Destination Directories Possible?

When you start contemplating to perform file management
operations over multiple directories for either the source or
the destination using XXCOPY, it is really time for you to
crate a batch file script. Since there is no limit on the number
of lines in a batch file, this technique is limitless in the
number of the directories you specify as well as the variation
you want to specify from one line to another.

By the way, XXTB#19 (http://www.xxcopy.com/xxcopy/xxcopy19.htm)
explains the switches useful in batch files.

--------------
Here's Kan's babbling of the day...

With XXCOPY, you can do a lot with one invocation. With the ever
increasing number of the command switches, the "perceived
difficulty" of using XXCOPY is probably increasing.

But, if we remind ourselves that XXCOPY is an extension of
Microsoft's XCOPY, the many switches that XXCOPY offers should
not intimidate that much.

One thing the designer of XXCOPY at Pixelab did not do was to
change the basic XXCOPY operation:

one-directory-source --> one-directory-destination

Certainly, we are *NOT* prepared to make it

multiple-directory-source --> multiple-directory-destination

In the case of multiple-destination as Jason inquires about, it
is not as bad as a multiple-source case which would be a total
disaster no matter what.

Probably, Jason's motivation is quite sound. That once you
figure out the basic copying operation (from src --> dst),
then, it is quite economical to extend this to

src --> dst2
src --> dst3
src --> dstn

In theory, this is true. But, in reality, there are just too
many XXCOPY operations which select the files by the
commonality of the source/destination situations (See the various
backup operations (the switches that starts with B like /BI)).

The multiple-destination operations would force other useful
switches to be discarded as exceptions which in turn cause
too much confusion that we do not want to deal with.

But, let me add one area which we might consider:

one-directory-source + one-directory-reference --> one-dst

This is where you make various comparison between a pair
of directories (SRC-DIR and REF-DIR) just like the way XXCOPY
now handles between the src and dst. Instead of copying the
files in the 1st directory to the 2nd, the operation will take
place to the third directory (DST-DIR).

A few users have suggested about this three-way operation.
This is useful and with a proper set of documentations and rules.
And it should be manageable. We can think of a number of
useful 3-way operations:
1. save the deleted files (by /Z) into a third directory
(just as how the RecycleBin works),
2. or to move the files to a third directory before they
are overwritten.
3. Or, simply compare the two and copy the selected files
to the third directory.

(I hope this would not open a can of worm...)