Some further instructions and tips for good beta reporting:
* Keep you messages short and to-the-point, a simple "Registry Manager hangs on jv16 PowerTools 2007 beta3 every time I open it" is a good bug report - it says the most important things: what happens, does it happen every time, instructions how to duplicate the problem and the exact version number of the program.
* If you are using a very common software setup, such as Windows XP or Windows 2000 there is no need to add information about your operating system to the report. But if you run a just-released or beta version of an operating system, such as Windows Vista, you should always mention that.
* If you are running a very common hardware setup there is no need to give specific details of your computer. If you run a the program in a clustered super computer using virtualization you should mention that, but there's usually no need to report if you are running Intel Pentium with n GB of memory and videocard x.
* Always remember to say whether the bug occurs every single time you use the product. Of course, saying this isn't necessery in obvious cases, such as typos in the user interfaces.
* Try to send many comments at one time in one post. Please use paraghraps and make the post easy to read, writing bug reports is not a poetry competition. Avoid very long posts, divide them to multiple posts for easier reading.