Reporting problems

What to do if you encounter problems using MiniDisc

Generally, MiniDisc is becoming quite stable these days. However, there is always likely to be something that I’ve missed, so...

If you do encounter problems, I would be grateful if you would submit an issue.

If MiniDisc crashes completely, then please follow the instructions below:

IMPORTANT NOTE: Running MiniDisc in debugging mode slows everything down drastically. Be patient when clicking on menus etc. as this will all take a LOT longer to perform as MiniDisc records details of what is going on in the ’DebugLog’ file. Suffice to say that I strongly suggest that you do not switch this option on unless it is entirely necessary to help me track down a bug.

1. Edit the file !MiniDisc.bin.SetDBState and alter the line: Set MiniDisc$DebugState "Off" to... Set MiniDisc$DebugState "On"

2. Re-run MiniDisc, and re-create the situation where the crash occurred. This will set MiniDisc to record debugging information into the file DebugLog within the !MiniDisc application directory.

3. Run the Obey file !MiniDisc.bin.GenLog. This will create a file called ErrReport within the !MiniDisc application directory. Note: This script generates a host of debugging information including the applications currently running in your machine. For this information to be useful, it is best run straight-away after your problem occurs. If your machine crashes after the error occurs, then you should generate the DebugLog as described above, reboot your machine, then re-create the situation JUST BEFORE where the problem occurred (i.e. load whatever other applications were running at the time) and then run GenLog.

4. Post the ErrReport file, along with as much information about your problem as possible as an issue.