When running dbmlsync on Windows Mobile, if you are using encrypted communication streams you must use the -pd option to ensure
that the appropriate DLLs are loaded at startup. Otherwise, dbmlsync does not attempt to load the DLLs until they are needed.
Loading these DLLs late is prone to failure due to resource limitations on Windows Mobile.
The following are the DLLs that need to be loaded for each communication protocol:
You should specify multiple DLLs as a semicolon-separated list. For example: