Files
GBM/GBM
Michael J. Seiferling a6341ffa76 Updates for issue #22
2016-03-11 16:26:20 -06:00
..
2016-03-03 19:28:04 -06:00
2016-03-11 16:26:20 -06:00
2015-11-08 16:06:31 -06:00
2016-03-11 16:26:20 -06:00
2016-03-11 16:26:20 -06:00
2016-03-01 23:27:42 -06:00
2015-12-09 18:25:47 -06:00
2015-11-08 16:06:31 -06:00
2016-02-21 22:31:27 -06:00
2016-03-02 10:22:09 -06:00
2016-03-02 10:22:09 -06:00
2015-11-08 16:06:31 -06:00
2016-03-03 21:16:17 -06:00

Game Backup Monitor v0.96 Preview Readme
http://mikemaximus.github.io/gbm-web/
gamebackupmonitor@gmail.com

March 4, 2016

Disclaimer:

This is beta release software.  You may still encounter some bugs.

New in 0.96

For more information regarding Linux support read the FAQ at http://mikemaximus.github.io/gbm-web/linux.html

- (Linux) Added Linux support via Mono!
- (All) Replaced System.Data.SQLite with the Mono.Data.Sqlite for cross-platform support.
- (Windows) Updated GBM's version of 7-Zip to 15.14 (2015-12-31)
- (All) Added the ability to set the 7-Zip compression level on the Settings screen.
- (Windows) GBM now deletes all user files to the Windows recycle bin by default.
- (All) Added the ability to clear and save the session log from the Tools menu.
- (All) GBM now auto-saves and clears the session log to %localappdata%\gbm if it reaches it's limit (2 MB).
- (All) The file size will be displayed in the session log after each backup.

The entire version history of GBM releases is available at http://mikemaximus.github.io/gbm-web/versionhistory.html

Important Upgrade Information:

A very small percentage of users may experience the following error message after upgrading to this version:

Column 'CompressionLevel' does not belong to table Table.

If you get this error follow these steps:

1.  Start GBM and click "Yes" to continue past the error. 
2.  Press CTRL and ~ (Tilde) to open the Developer Console.
3.  Enter the command exactly as follows (or copy & paste it) then click OK.

SQL Local PRAGMA user_version=95

4.  You'll receive confirmation that the command was executed.  Click OK and immediately close GBM via the File menu.
5.  Restart GBM and the error will no longer appear!