Helpful Hints For Creating a Command Line

NOTE: You can find two simple batch (*.bat) files for quick and easy usage from the Start\All Programs\Convert Document To Image\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 suggested you first attempt your task using the User Interface prior to attempting to create an equivalent command line. Reasons for this are to:

• Make sure what you want to do can be done at all

• Makes you aware of exactly what must be specified in the command line

• You can very quickly test the command line by doing the easiest of all approaches, specifying a 'Conversion Job' file by using the /J switch.

HINT 2: It is highly encouraged that at least during the initial creation of the command line that you 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 see the following error:

"CDTI is not recognized as an internal or external command, operable program or batch file."

It is because the operating system can't locate CDTI.exe. Do one of the following to resolve this error:

A) (Preferred method) Specify the full path to the executable. For example:

"c:\Program Files (x86)\Softinterface, Inc\Convert Document To Image\CDTI.EXE" /J"D:\My Jobs\AcctBatch.SII"

Alternatively if using a batch file you might try something like this:

set CDTI="c:\Program Files (x86)\Softinterface, Inc\Convert Document To Image\CDTI.EXE "

%CDTI% /J"D:\My Conversion Job Files\AcctBatch.SII"

Note: If you are using a 32 bit operating system swap "Program Files (x86)" with "Program Files" from the above examples.

B) Set the path operating system variable to the location of CDTI.EXE

Also, it is suggested you use fully qualified paths for any files you specify. 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 CDTI.EXE from the installation folder to some other folder is not likely to work well, so instead try one of the methods above.

HINT 4: 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 CDTI.EXE to CDTI.Admin.EXE. Doing this will enable a prompt to elevate security before the command line is fully executed.

HINT 5: Command switches are case sensitive, therefore /F is completely different from /f.

HINT 6: You may use the following to specify a user independent path to files:

For example:

CDTI.exe /S"%AppData%\In\TryMe.Doc" /T"%MyDocuments%\Out\TryMe.JPG" /4 100 /V

See also:

Using the Command Line

Complete List of Command Line Examples

Command Line Switch Specification

Specifying a Conversion Task

Specifying a Conversion Job

File Type Constants Specification