NOTE: You can find two simple batch (*.bat) files for quick and easy usage from the Start\All Programs\Convert Doc\Example Batch Files. These will work without modification provided you installed in the default folder. One batch file is for 32 bit, the other for 64 bit operating systems.
HINT 1: It is highly recommended that you first attempt your task with the Graphical User Interface prior to attempting to create an equivalent command line. Reasons for this are:
Test using the user interface. It is much easier/faster to test than the command line.
Quickly test whether what you want to do can be done at all.
Become familiar with exactly what must be specified in the command line.
After performing the task in the user interface, you can very quickly test the command line by using the easiest of all approaches, by specifying a 'Conversion Job' file by using the /J switch.
HINT 2: It is a great idea, at least during the initial creation of the command line, to use the Verbose (/V) switch to see what the status of your conversion is and get any error messages. /V shows you a message telling you how the command line went. If you are not getting any message at all while using the /V switch, then see hint 3 below, as you are probably not even executing the program. If you prefer a log file instead of a pop up message box, use /L{LogFilePath} instead of /V.
HINT 3: If you see the following error:
"ConvertDoc
is not recognized as an internal or
external command, operable program
or batch file."
it is because the operating system can't locate ConvertDoc.exe.
Do one of the following to resolve it:
a) (Preferred method) Specify the full path to the executable. For example:
"C:\Program Files (x86)\Softinterface, Inc\Convert Doc\ConvertDoc.EXE" /J"D:\My Jobs\AcctBatch.SII"
Alternatively, if using a batch file, try something like this:
set CD="C:\Program Files (x86)\Softinterface, Inc\Convert Doc\ConvertDoc.EXE "
%CD% /J"D:\My Conversion Job Files\AcctBatch.SII"
Note: If you are using a 32 bit operating system, replace "Program Files (x86)" with "Program Files" in the above examples.
b) Set the path operating system variable to the location of ConvertDoc.EXE
HINT 4:Use fully qualified paths for any files you specify.
NOTE: You can however specify the current folder by using ".\" syntax. Use double quotes around the input and output files (/S and /T) if they are long file names.
NOTE: Copying ConvertDoc.EXE from the installation folder to some other folder is not likely to work well, so instead try one of the methods above.
HINT
5: Windows Vista, Windows 7
and newer: These operating systems use a feature called User Account Control
(UAC) to safeguard your computer. If you have UAC enabled and you are
specifying an output folder that is protected, the files will be created
in the %localappdata%\VirtualStore\
folder.
To find the output files type in %localappdata%\VirtualStore\
in Windows Explorer. If you think UAC is having an effect on the command
line you can quickly change the name of the program in your command line
from ConvertDoc.EXE
to ConvertDoc.Admin.EXE.
Doing this will enable a prompt to elevate security before the command
line is fully executed.
HINT 6: Command switches are case sensitive, therefore /F is completely different from /f.
HINT 7: You may use the following to specify a user independent path to files:
Path |
Typical Interpretation |
%USERPROFILE% or %HOMEPATH% |
C:\Users\UserName |
| %APPDATA% | C:\Users\UserName\AppData\Roaming |
| %LOCALAPPDATA% | C:\Users\UserName\AppData\Local |
| %MYDOCUMENTS% | C:\Users\UserName\Documents |
For example:
ConvertDoc.EXE /S"%AppData%\in\input.DOC" /T"%MyDocuments%\Out\output.PDF" /C12 /F9 /M2 /V
See also:
Specifying a 'Conversion Job' from the Command Line
Specifying a Conversion Task' from the Command Line
Examples: A Complete List of Command Line Examples