If you have encountered a bug please submit your report via the bug tracker. Additional debugging information is always very appreciated.
How to collect debugging information
- Create screen-shots
- This is highly recommended for reporting display related problems.
In addition they help to visualize the current state of your volume.
- Enable debugging output
- Use the dbgprint_level setting or the UD_DBGPRINT_LEVEL environment variable and set it to DETAILED
- Collect debugging output
- There are two ways:
- Using the DbgView program
- Using the log_file_path setting or the UD_LOG_FILE_PATH environment variable
How to create screen-shots
- Taking a screen-shot
- Hit [Alt]+[Print Screen] to save an image of the currently active window to the clipboard. You can use your favorite screen-capture tool too, a free one is Hardcopy.
- Create a PNG image file
- It is recommended to not paste the image from the clipboard into an Office document, but to create a PNG image of it by pasting into Paint or any other drawing program.
If you use Hardcopy you can save it directly.
How to enable debugging
- Debugging the GUI
- The dbgprint_level and log_file_path settings are contained in the options file, which you can access via the wrench icon of the tool-bar or the settings menu.
- Debugging the console utility
- Set the UD_DBGPRINT_LEVEL and UD_LOG_FILE_PATH environment variables before you execute the udefrag utility in the command prompt.
- Debugging the boot time utility
- Set the UD_DBGPRINT_LEVEL and UD_LOG_FILE_PATH variables before you execute the udefrag command in the boot time script.
The log file %windir%\UltraDefrag\Logs\boot-startup-phase.log is used internally to collect debugging information before the boot time script is executed.
Using the DbgView program
Don't forget to check the Capture Win32 item of the Capture menu of the DbgView program. Check one of the Log to file items of the File menu to create a log file you can send us.
Note that DbgView cannot capture information from the user mode driver during the Windows boot process. This is a well known DbgView limitation. The latest version of DbgView cannot be used on NT 4.0 either, check this page for an earlier version.
Disable debugging
For the GUI you just have to set dbgprint_level and log_file_path to an empty string.
For the boot time utility comment out the lines containing the definition of the UD_DBGPRINT_LEVEL and UD_LOG_FILE_PATH variables by adding a semicolon (;) at the beginning of those lines.
Creating a package to submit
It is best to ZIP your collected files into a single compressed archive, which will reduce the up- and download size immensely. If you do not own a ZIP utility, check out 7-zip.
Note that the Sourceforge trackers only allow uploading files of 256KB in size. For bigger files you may use one of the free file hosting services.