
Directory Synchronizaton Utility, Version 1.2 Revised 23-Jan-1997
(See below for changes in the new version)
Now available on my web site:
http://www.*-*-*.com/
Click on the "Visual Reality Room" hotspot.
The Directory Synchronization program synchronizes the file contents of
two directories (and optionally any subdirectories) on a personal computer
running Microsoft Windows.
The program comes in two versions:
A 16-bit version, SYNCDIR.EXE, is written in Visual Basic 3.0,
and runs under Microsoft Windows 3.*, Windows 95, or Windows NT.
A 32-bit version, SYNCDI32.EXE, is written in Visual Basic 4.0,
and runs under Microsoft Windows 95 or Windows NT (version 3.51
or later).
The following supporting .ZIP files are included:
SOURCE16.ZIP contains the Visual Basic 3.0 source code for SYNCDIR.EXE
SOURCE32.ZIP contains the Visual Basic 4.0 source code for SYNCDI32.EXE
DLL16.ZIP contains the runtime dynamic link library, VBRUN300.DLL,
needed to run SYNCDIR.EXE
DLL32.ZIP contains four DLL's needed to run SYNCDI32.EXE
HELPFILE.ZIP contains the help file source
The help file SYNCDIR.HLP runs with the 16-bit version of WINHELP.EXE,
and provides the documentation for both SYNCDIR.EXE and SYNCDI32.EXE.
The following is excerpted from SYNCDIR.HLP:
The program compares file names and modification dates for
a Source Directory and a Target Directory (and optionally
any subdirectories).
If a newer file is found in the source directory,
the program replaces the matching file in the target directory.
(Optionally, older source files may also replace newer target files.)
If a file exists only in the source directory,
the program copies the file to the target directory.
The program will optionally delete any files that exist
only in the target directory.
An option allows the synchronization to operate in both directions
between the two directories.
Prior to copying or deleting any files, the program prompts the user
for final confirmation. Upon completion of any copies or deletions,
the program displays a log window that describes all file actions
that were performed.
(The confirmation dialog and log window do not appear if the
Automatic option is enabled and the NotifyUser option is disabled.)
An option allows the program to automatically check for any
file synchronization, or to wait for the user to complete
a synchronization dialog. In this automatic mode, the program
may also launch another application upon completion.
This program may be used for the following purposes:
Program Copy Management:
Automatically copy updated files from a shared file server directory
to a directory on the computer's hard disk.
File Backup:
Copy revised files from a working directory to a backup directory
on another disk or on a file server.
Dual Computer File Coordination:
Use a diskette as a transport mechanism to move data files,
in both directions, between an office computer and a home computer.
The user may also design variations and combinations of these techniques.
CHANGES TO SYNCDIR, VERSION 1.2 23-JAN-1997
(32-bit only): Allow quoted long filename containing blanks on command line
for the initialization file. For example, the following are all legal
command lines:
SyncDi32.exe "Long File Name.ini"
SyncDi32.exe "Long File Name.ini" SectionName
SyncDi32.exe LongFileName.ini
SyncDi32.exe LongFileName.ini SectionName
(16-bit and 32-bit) The Log window now includes a "Print Text" button,
which sends the log text to the default printer.
(16-bit and 32-bit) New option ShowErrorMessages (default is "Yes").
If set to "No", then message boxes during file copy and delete
operations are suppressed, and the operation continues to the next file.
Any errors are still shown in the log window upon completion,
if NotifyUser is set the "Yes".
(16-bit and 32-bit) New option ProcessHiddenFiles (default is "No").
If set to "Yes", then files with the System or Hidden attribute set are
processed. If set to "No" (the default), these files are ignored during
copy or delete operations.
(16-bit and 32-bit) New options AlternateRunDirectory and
AlternateRunCommand, which default to match RunDirectory and RunCommand.
If any files are copied or deleted, the AlternateRunDirectory and
AlternateRunCommand are used. If no files are copied nor deleted, the
normal RunDirectory and RunCommand are used.
The intention is for the AlternateRunCommand to run any registration
code needed by an updated system being synchronized from a server
directory to a local execution directory on the desktop.
The normal RunCommand simply runs the unmodified application.
The AlternateRunCommand would first register any updated files, then
would itself launch the updated application.
This program and its source code have been donated to the public domain
by the author, Rick Rutt, who can be contacted by electronic mail at: