When you turn on Debugging under Amulet Settings / Diagnostics, Amulet downloads a utility called DebugView (dbgview.exe) from
www.sysinternals.com which is used to capture debug output to a logfile where it can later be analysed or sent back to us as part of a bug report.
A recent upgrade to DebugView (v.477) has introduced an option change which is not compatible with the default Amulet settings. This won't affect anyone who has already been using debug mode on Amulet, since they will be using an older version of DbgView.exe.
If you've just installed Amulet on a clean system, then follow these steps to ensure DebugView works correctly for you:
Edit the file "C:\Program Data\Amulet Devices\Amulet.ini" (this is a hidden folder), and find the line that reads as follows:
DebugOptions = /f /l "{AmuletData}\Logs\Amulet.log" /a /n /t
Edit this line to read like this:
DebugOptions = /f /l "{AmuletData}\Logs\Amulet.log" /p /n /t
The changes are that the semicolon at the start of the line is removed, and the /a option near the end is changed to /p.
After this, kill any instance of DbgView.exe you can see running in Task Manager, then restart Media Center and Amulet will use the correct debug options.
If you are not sure whether or not you are affected by this, manually start the file "C:\ProgramData\Amulet Devices\DbgView.exe" and check the version under Help / About. If it is v4.76 or earlier, you don't need to make any changes. If it is v4.77 or later, then you need to make the change described above.
To add to the confusion, when the new DbgView.exe is started with the old Amulet options, it launches in a special Agent mode which, confusingly, displays its version as v4.75. If you see this, then you are still running DbgView v4.77.
The next release of Amulet will transparently handle all of this, so the above steps are only an interim measure, needed if you are using debug logs to track a possible problem with your Amulet installation.
