Application: GameSave Manager
Category: Utilities
Description: With GameSave Manager, you can easily backup, restore and transfer your gamesave(s).
Download GameSave Manager Portable 3.1.455.0 Development Test 1 [7.18MB download / 11.9MB installed]
(MD5: FE6C5FD87DAF9FBD7F1D64DF67821399 )
Permission to portiblize:
Hello,
Sure thing; I'll adjust the PortableApps page of the site to recognise you as the maintainer when I get time. I can host the download too.
--
InsaneMatt | Project Leader | http://www.gamesave-manager.com
Release Notes:
v3.1.455.0 Development Test 1 (01-08-2018)
- Updated to v3.1 build 449
v3.1.449.0 Development Test 1 (08-11-2017)
- Updated to v3.1 build 449
v3.1.442.0 Development Test 1 (03-30-2014)
- Updated to v3.1 build 442
v3.1.431.0 Development Test 1 (02-09-2014)
- Updated to v3.1 build 431
v3.1.406.0 Development Test 1 (12-05-2013)
- Updated to v3.1 build 406
v3.1.388.0 Development Test 1 (10-16-2013)
- Updated to v3.1 build 388
v3.1.373.0 Development Test 1 (09-18-2013)
- Updated to v3.1 build 373
v3.1.355.0 Development Test 1 (09-12-2013)
- Updated to v3.1 build 355
v3.1.335.0 Development Test 1 (07-21-2013)
- Updated to v3.1 build 335
v3.1.328.0 Development Test 1 (06-09-2013)
- Updated to v3.1 build 328
v3.0.302.0 Development Test 1 (03-20-2013)
- Updated to build 302
v3.0.290.0 Development Test 1 (02-03-2013)
- Updated to build 290
v3.0.280.0 Development Test 1 (12-24-2012)
- Updated to build 280
v3.0.265.0 Development Test 1 (12-08-2012)
- Updated to build 265
v3.0.253.0 Development Test 1 (11-26-2012)
- Updated to build 253
v3.0.238.0 Development Test 1 (10-25-2012)
- Updated to build 238
- development test build reset to 1
v3.0.212.0 Development Test 7 (10-10-2012)
- Updated to build 191
v3.0.191.0 Development Test 6 (09-27-2012)
- Updated to build 191
v3.0.179.0 Development Test 5 (09-21-2012)
- Updated to build 179
v3.0.157.0 Development Test 4 (09-08-2012)
- Updated to build 157
v3.0.153.0 Development Test 3 (09-05-2012)
- internal build only
- fixed launcher not backing up settings properly - thanks to Gord Caswell, from PortableApps.com
- various other small fixes
v3.0.153.0 Development Test 2 (08-22-2012)
- Updated to build 153
v3.0.144.0 Development Test 1 (07-28-2012)
- Updated to build 144
v3.0.140.0 Development Test 1 (07-23-2012)
- Updated to build 140
v3.0.132.0 Development Test 1 (07-19-2012)
- Updated to build 132
v3.0.125.0 Development Test 1 (07-15-2012)
- Initial release (Re-release?)
- Created new launcher for 3.x version GameSave Manager
- Updated to build 125
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
GameSave Manager updated to v3.0.132.0. As usual, let me know if you have any problems running this.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
App updated to v3.0.144.0
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
App updated to v3.0.153.0
However, I've noticed an issue. This program saves a directory called settings in the App\AppName directory. Would it be correct in saving this in the AppNamePortable\Data directory and copying it to the App\AppName at program startup, then copying it back after it closes, or should I be moving it back and forth.
As it sits right now, every new release deletes your settings including your custom entries. Since this is not desired, what is the correct way of fixing?
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Update the settings\config directoriesMove line to move to \settings instead of \config.
Note: I'm checking this out, I've got more comments to come, but that's the specific question you asked.
When I updated this to v3.0, I used the launcher from kai.inouye's v2.3.700b launcher. There was a lot of stuff in the launcher.ini, that I didn't understand. The one thing that I did understand was that the executable that the launcher was looking for had changed. So I changed the first line to reflect the new name, but left everything else alone. I meant to come back to this, but wanted to understand what I was doing first. I now know that the rest was to handle just this problem. I also had to make a new launcher using the PA launcher, and redo the icons, as those had changed too.
For some reason, I cannot seem to understand the manual, even though I have the appropriate section of the the launcher.ini manual open in a different window. Therefore, I'm looking for examples doing what I need done, so I can learn and stop pestering you good folks.
I'm re-installing the old one, so I can see if I can figure out what is being done. I put a copy of kai.inouye's v2.3.700b launcher in my Dropbox here, if you want to compare the two. One will overwrite the other even though one is version 2.x series and one is version 3.x series.
If I understand you correctly, the launcher.ini file should look like below.
[DirectoriesMove]settings=%PAL:AppDir%\GameSaveManager\settings
but the next line in the old launcher.ini file has me stumped. It is below.
settings="%APPDATA%\GameSave Manager 2"I believe these are where my mistakes are. I've gotten very little feedback to date (none for this program, other than yours), so I've been trying to catch my own mistakes. I would be and am thankful for any input you have. Peace...
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Ok so have you ever seen this error? How do I preserve the settings, if I can't move the directory?
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Move the contents of whatever it is you need from settings. The
Data\settingsfolder also hasAppNamePortable.ini, you don't want to move that too. Only move what you need to.Forgive me if this is a stupid question, but I'm not seeing Data\settings\AppNamePortable.ini
Due to the size of my response, I posted my comment on pastebin, at
http://pastebin.com/tw0JubFj.
Let me know if I messed that up, ok? Thanks..
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
I'll post an update script, and fixed launcher.ini, later today for you.
Thanks Gord
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Ok, let's get started:
I'm starting from the current release you have up, not from the stuff you pastebin'd.
Here's the files to update: appinfo.ini, GameSaveManagerPortable.ini
Also, add this file as Other\Source\PortableApps.comInstallerCustom.nsh
Additionally, seperate comments follow:
appicon.ico should include the following sizes:
You're missing the 8-bit ones, and should remove the 96px one.
As well, remove appicon_48.png and appicon_256.png from App\AppInfo
Finally, remove DefaultData, since you're not using it.
One last thing: Update the package using the Application Template 2.4, the help images as well as some other random files throughout need to be updated.
In the future, (ie., once there's a new build from the publisher) please have the package version using a schema that allows for smooth updating from version to version. For an explanation of what I mean, see my blog post on the topic.
Ok I replaced my original appinfo.ini and GameSaveManagerPortable.ini with the ones you put here. I also added to the Other\Source\ directory the file "PortableApps.comInstallerCustom.nsh" without the quotes. I actually think I understand what the custom installer is doing (it's mostly plain text), but I would't have had a clue on the proper syntax. A question about the custom installer. I would keep that there in later releases, in case someone didn't update their copy yet, correct?
If I understand the bit about the appinfo.ico correctly, I should have the 16px, the 32px, and the 128px, both in 8 bit and 32 bit? I tried to find an example of this as I'm curious how to name them. I checked FileZilla, ClamWinPortable, CrystalDiskInfoPortable, & HiJackThisPortable. The all seem to use just the 32 bit. Is there a better example? For now, I deleted appinfo_48.png, and appinfo_256.png. The ones remaining are 32 bit. So should I redo those 3 PNG's as 8 bit?
I've updated the help file, as you suggested, and used the v2.4 template, and copied the specific files into place. I believe in your blog, your suggesting that for PackageVersion, instead of matching the DisplayVersion, I should have the PackageVersion smaller that the DisplayVersion. For example, if InsaneMatt's newest version of GSM is v3.0.162, then I should have a DisplayVersion of 3.0.162.0, but a PackageVersion that is higher than the last one, but lower than this one (like 3.0.154.0). Do I have it right, or am I still screwed up?
I'm sorry that this required so much work. I really don't mean to be such a pain in the backside. For a while, I'm just going to continue updating what I have, but not releasing anything else, until I understand better. Thanks for all you help and patience. Peace..
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to v3.0.157.0
See notes for details
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to v3.0.179
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GameSave Manager v3.0.191.0
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GameSave Manager v3.0.212.0
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
you should reset your dev test version when you update the base app.
That's what I was doing originally, but when I read Gord Caswell's blog located here, I thought I was doing it wrong.
So if the author updates, but you do not change the laucher, it the dev test should not increment?
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
The main point Gord was getting at in that blog was that apps end up with the same PackageVersion when leaving dev test and being released officially.
Whether you change the launcher or not, when you update the base app you should reset the dev test to 1.
As an example, lets say you were releasing version 1.0 of an app, it would be dev test 1. On updating the launcher, it would be dev test 2, then dev test 3 and so on. When you then go and release 1.1 of the base app the dev test number goes back to 1 as you are now releasing the first dev test of version 1.1. So your history would look something like this:
1.1 dt 1 (newest)
1.0 dt 3
1.0 dt 2
1.0 dt 1 (oldest)
To clarify what I blogged about:
The specific numbering schema which is ideal for this app is as follows:
PackageVersion=3.0.211.1
DisplayVersion=3.0.212.0 Dev Test 1
If you updated the launcher, but stayed with the same base app version, it would change as follows:
PackageVersion=3.0.211.2
DisplayVersion=3.0.212.0 Dev Test 2
Otherwise, if you updated the base app (let's pretend to 3.0.564.0), no matter whether you also updated the launcher or not, it would change as follows:
PackageVersion=3.0.563.1
DisplayVersion=3.0.564.0 Dev Test 1
Does that make a bit more sense?
That makes a lot more sense to me. Thank you for the clarification.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GameSave Manager v3.0.238.0
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GameSave Manager v3.0.253.0
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GSM 3.0.265.0. Sorry for the delay. Router died so I've had no internet at home for a week.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Updated GSM to v3.0.280.0.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to v3.0.290.0
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
this app seems to be updated alot
i wonder why
dosn't it seem odd for a program to be updated so often
i'm not wierd, i'm just different
updated fairly often, but not nearly as often as, say Calibre. Also, v3.0 was a major rewrite, so I believe some bugs were introduced. A lot of new features were added over the v2.3 version.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GSM v3.0.302.0.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GSM v3.1.335.0.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
hello, may you update the application?
and please, fix "settings lost" problem
to GSM v3.1.355.0. Also, for m-alice, is it certain settings, or all of them? It should have been saving them. I'll look into it.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GSM v3.1.388.0.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GSM v3.1.431.0.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
to GSM v3.1.442.0.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Sometimes the program forget about settings (after autoupdate)
I'd wager you didn't exit properly on the previous run. That will leave the settings in the GameSaveManagerPortable\App\GameSaveManager\settings directory and that directory will be wiped on upgrade. To ensure this doesn't happen, be sure to fully exit all apps before unplugging your drive or restarting/shutting down Windows. The PA.c Platform will automatically close all your apps politely and warn about any it can't on exit.
For the Dev: You can handle situations like a crash then upgrade by adding an installer.ini with these contents:
[DirectoriesToPreserve]
PreserveDirectory1=App\GameSaveManager\settings
That will preserve the directory and allow the PA.c Launcher to recover from a crash on next start.
Sometimes, the impossible can become possible, if you're awesome!
for the tip.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
I seem to be able to launch multiple instances of GSM. Is this by design? Either way, thank you for creating and maintaining this!
@bill_gagliardi
Official Latest Stable Release v3.1 (Build 449) 24th July 2017
Please, ... made the portable version.
I have very limited internet access, until about Sunday, the 6th. Unfortunately, I'm out of town. I have it made. I just don't have access to update the download. I didn't bring my laptop with me (gotta be the only time I haven't brought it with me). I'll update the link when I get home...
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
It appears that Mollom won't let me update this. Any chance of getting it unblocked??
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
We have no control over Mollom at all. It's either on or off for all forum stuff with zero configuration options.
I adjusted the original post to remove the separate preview version and one of the links. Each additional link increases the likelihood of it getting flagged. Though it appears to use IP address and neighborhood heavily as well.
Sometimes, the impossible can become possible, if you're awesome!
Thanks John, that seemed to do it. App is updated to 3.1.449.
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
Updated to v3.1.455
Bill G.
Frozen St. Paul, MN
land of the frozen mosquito
nvm
Are there any plans to continue updating the app?