Bug reporting

Like all complex software, dvdisaster may contain bugs (programming errors) and incompatibilities with certain (drive) hardware and software setups. You are invited to tell us about any difficulties you encounter with the program or the documentation so that we can improve things in future releases.

To make sure that we are getting the right information, we have provided the following checklist for bug reporting:

Please check first that you are really experiencing a bug:

Make sure that you are using the latest genuine version from our download site at SourceForge. dvdisaster versions provided by third parties may contain functions and bugs which are not present in the original version (and we can't fix their problems).
Double check that the issue you have encountered is not already covered in the Questions and Answers section.
Please note that dvdisaster will only work with the (re-)writeable varieties of media, so seeing it reject DVD-ROM and BD-ROM is not an error. Also, CD-Audio, VCD, SVCD and multisession CD are not supported as well as all HD-DVD formats (complete list of supported media formats).
dvdisaster works only with real drives. Not supported are network drives, software drives (e.g. alcohol) and drives in virtual machines.

How to report issues with the program:

Please report your findings by sending an email to email address shown as graphics image

. Your report should contain:

Information about the operating system and dvdisaster version you are using;
the drive and media type(s) which exhibited the problem;
a textual description of the issue you encountered;
a screen shot of the error message and/or output which might provide further information about the problem;
differences between working and non-working configurations if the issue is experienced only on certain drives/computers;
a log file if you suspect that the issue is related to a drive or medium incompatibility.

How to create a log file: If you suspect incompatibilities with your drive and/or media as the cause of your issue, please activate the log file feature in the preferences dialog as shown in the screen shot. Then perform a scanning or reading action and attach the log file to your bug report. Thanks for your feedback!