The Commands->Debug menu item has cascaded submenu item that are used to open and close the fs_debug.log which provides some limited logging of functions. The log is generally a series of small dumps of variable values at certain predefined points in the function code. The event time is logged to the nearest 10 milliseconds. The submenu options are:
Note: A fs_dump.log should always be written on a system trap.
The log files will be located in the directory where the FS/2 *.INI files are stored except, on rare occasions, they may be written to the boot root directory when that directory can't be found.
All logging is appended to any existing fs_debug.log. To log a specific event, it is best to delete the file before starting the event.
When this command is used to open the fs_debug.log, all possible logging is enabled. This can produce a large file in a short time. More specialized logging can be enabled by using the following accelerator keys:
The above accelerators may be used in combinations. When a log function is enabled, the message window reports what function has been enabled.
A log open or close command may be sent while the program function is running.
The log functions should be closed (Ctrl 0) as soon as possible after logging some event to prevent excessive logging - which can be quite difficult to use for debugging if the log file is quite large and unnecessary events are logged.
Accelerator Keys:
Please contact the author through www.filestar.com, or direct email, for debug assistance on any problems encountered.