0.8.0

Some bugs with handling older files have been resolved.
More information provided to the user. In many situations previously if something failed, either nothing would happen or it would just get logged in the background with no obvious sign to the end user. Now there is some information provided if it can't unlock the file, or if an older file (like a V3.20) is presented and it can't be recovered (yet, I'm still trying to figure out a way)

0.7.0

Added in some basic logging and cleaned up some code that would cause the program to crash when an error occurred (it now logs it and moves on). The logging is pretty basic, it just creates a pv-unlocker.log file in the same folder as the executable and writes out any errors.

0.6.0

There might be a bit more cleanup, but this is a base working version I'm willing to release. If I don't find a lot more bugs, or feel there are some issues that need reworking, I may end up tagging this as 1.0 later.

Usage, launch the application (you can launch it on with a list of files as a parameters ie pv-unlocker *.mer)

Click the Select Files button, and select the files you wan to check.
It will list the names of the files, with the version number next to it, and a lock icon.
If the file is locked / protected it will show as a locked icon in red, click on it, and it will unlock it.
If the lock icon shows as unlocked and green, it's not protected.

This safely unlocks MER files down to version 5.
I have recently discovered a way to unlock v4 MER files so they can be recovered as a project, however there might be some limitations. In my test so far, the alarm triggers all come through but not the messages. I'm not sure what else might fail.