--diagnoselog
--diagnoselog LogFile --diagnoselog *
The --diagnoselog command allows diagnostic information to be written to the file specified by LogFile. To turn on diagnostic mode, the --diagnose command is used. There are two versions of the --diagnoselog command.
The first version allows you to specify the log file name, LogFile. If LogFile contains spaces in the file name, LogFile must be enclosed in double quotes.
The second version of --diagnose log allows you to log the output to the active debug monitor program. To specify this option, the * (asterisk) character is specified after the --diagnose log option. An example of a debug monitor program is DebugView available at http://www.sysinternals.com. The debug monitor will capture all of the log information, allowing you to generate logging information without having to create a log file.
Examples:
twainsave --diagnose 1 --diagnoselog c:\Test\diagnose.log --filename test.bmp twainsave --diagnose 1 --diagnoselog "c:\Test\My Logs\diagnose.log" --filename test.bmp twainsave --diagnose 4 --diagnoselog * --filename test.bmp
Note that the second example enclosed the file path c:\Test\My Logs\diagnose.log in double quotes because of the space in "My Logs". The third example demonstrates the --diagnose log option to write the diagnostic output to the active debug monitor.
Please note that you must have write access to create log files. If this is not an option, you can try the --diagnoselog * option and run DebugView to observe the log output.
|