Moving save game data to a network mount to play...

effervo

First time out of the vault
Hey there. Well, I did some searching and after going through 100 pages, couldn't find what I want to try to do. I'd like to get some feedback on if someone has already tried this, and if not, what you think would need to be done.

So, down to business.
OS I'm running is Windows 7 Ultimate and Windows 7 Pro, both 64-bit.
It's Fallout 2, updated with Killaps F2 Restoration project 2.1.2b, though I don't think the version should matter for what I'm' thinking of doing.

Now, what I'd like to try. I'd like to play Fallout 2 on both computers, one being a desktop, and the other being a laptop. I'd like to play the same game instead of having different games on both computers that I'm playing around the same time.

What does everyone think of the possibility of creating sym links to the SAVEGAME folder and posting it up on a network sharepoint. Both computers would have a constant connection to the server.

Do you suppose this would be a possibility? And obviously overlooking the chances of internet dropping and the game being corrupted in some way, do you see any other possible issues coming up?

This seemed like the most logical place to post seeing how this could be considered "technical". I'm sorry if it's not though!
 
When this game was released, I'd say "put it on some floppies". The savegame folders won't take up more then a few megabytes.
Just replace by USB stick.

If you want to go network (LAN):
- share the SAVEGAME dir on pc A, copy manually to/from pc B when needed.
- Share the top folder where you installed it, mount it as a network drive on the other pc, copy manually
- Share the Savegame dir on PC A, write batchfiles for PC B: "copy from A" or "copy to B".

Replace "pc A" by "server" when you want to go NAS.

If you're afraid of corruption: in above scenarios you save to the local disk, then afterwards copy to/from a remote location. You'd get a warning if something happens.

If you're working over internet, write a batch file to zip the savegame folder & mail it, or send it to a share, or whatever. Quite some options to achieve this.
 
Thank you for the write up boes_kameel, but the intention was to minimize the number of times the savegame has to be copied and to create a seamless flow.

For those wondering, creating Sym links from the local PC's to the network share works perfectly, If you're on gigabit ethernet, saving and loading is slightly slower than if the files are located locally, but the difference is maybe 3-4 seconds, so it's not a lot.

Besides slowness, it works perfectly.
 
Back
Top