This article describes the best way to report a bug you discover during the beta test.

The bug itself can be described in the beta forum, which is useful for others who may be seeing the same thing; it helps us build a picture of how common or rare it might be.

To help us fix the bug, however, the number one tool is the Amulet debug log. Enable the debug log under the Diagnostics page in the Amulet Settings app within Media Center. Once enabled, Amulet will log debug information to disk files in the folder "C:\ProgramData\Amulet Devices\Logs", creating a new file for each day. While not essential, it's a good idea to restart Media Center after enabling debugging, to ensure that all the startup activity is properly logged.

Important: If you are running Amulet v3.01 or an earlier software release, and installed after September 2011, please read this article about a change you need to make to the Amulet configuration file in order for the debug log to operate correctly.

It is safe to leave debugging on at all times; the effect on performance is minimal, and especially during beta testing, it's very useful to have the log file available if a difficult-to-reproduce bug should occur.

Logfiles are automatically recorded using the DbgView utility (which Amulet installs the first time you enable debugging); it sits in your system tray as a spyglass icon and can be opened by double-clicking that icon if you want to review the most recent debug log activity.

The easiest way to send us a logfile is to use the "Report a bug" option on the desktop Start Menu -> Amulet -> Troubleshooting submenu. This will gather the two most recent logfiles and several other operational files used by Amulet into a ZIP file which is then emailed directly to our bug database where we can review it. If your bug pertains to something related to a particular media file, you may like to include media index files also (there is a tickbox at the bottom of the bug report form for this).

All bugs reported are also archived on your local disk and can be accessed via the Report a Bug form using the button in the upper right corner; this is useful if for some reason a bug report can't be delivered (some ISPs block outgoing mail to third-party mail servers); you can then manually email the bug file.

In the absence of a full debug log, another useful file to reference is "C:\ProgramData\Amulet Devices\AmuletErrors.txt". This logs any serious errors Amulet encounters during operation, regardless of whether or not debugging is enabled.

Otherwise, general bug reporting principles apply. Answer as many of the following questions as you can:

• What were you doing when you noticed the bug?
• Can you reproduce it at will?
• Does it happen with multiple types of media, or just a specific program / channel / song / movie?
• Was this working for you previously and has suddenly broken?
• Is there anything else unusual about your system that you think may be relevant?

I am not finding where to enable debugging. In media center, under Amulet Voice Remote, Settings... there is no Diagnostics page. Am I in the right spot. I checked under the Settings page for Media Center itself and there was nothing for Amulet there either.

It's the last or second-to-last tab on the Settings page of the Amulet Remote section of 7MC. There are a bunch of options with checkboxes, it says not to change them unless instructed to do so by support.

The only menu options I have there are General, Listener, Talker, Talker Volumes, General Volumes, and Extras.

Chris, it sounds like you are running the old 2.17.50 release software rather than the new beta. See this thread for download details.

With the beta software, when you enter the settings page, you should see a status page like this screenshot:

This image is hidden for guests. Please log in or register to see it.

The original software doesn't include the status info.

That explains it. Remember when I said I'm more of a dive right in without reading instructions type of guy.....
I'll have some new stuff (including debugging) for you guys tomorrow.
Thanks!