Quote:
|
Originally Posted by JScones
No, you've got to rollback immediately AFTER you exit SH3. Otherwise, this is what happens:
1. You rename SH3 - GW to be your primary SH3
2. You run SH3Cmdr which rolls back and then loads files into this installation of SH3
3. You exit SH3
4. You rename this SH3 installation back to SH3 - GW then rename SH3 - NYGM to be your primary SH3
5. You run SH3Cmdr which rolls back into this installation of SH3 the files that it backed up last time and then loads new files
See what's happened? The files SH3Cmdr backed up when you ran SH3 (- GW) have now been restored into SH3 (- NYGM).
But if you rolled back immediately after exiting SH3 and prior to any SH3 installation folder renaming, you'd never have this problem.
And no there is no problems with having multiple installations of SH3Cmdr. There's instructions on how to do this in the SH3Cmdr sticky.
|
Hi JSCones!
First of all, may I say what a superb job you've done in creating SH3 Commander! Too often a programme which works well gets not much positive feedback, but anything with a slight hitch attracts mega-reams of criticism! I wanted to add my positive thoughts! I've been using it for a few months now, with absolutely NO problems....so long as I remember to "rollback"!!!
I've actually had 4 seperate SH3 installations, all with corresponding SH3Cmdr insttalls "to match"! Only once did I get a "cross-pollination", which was entirely down to my own stupidity!!
My question is this:
Is there any way in which you could build some kind of "perform auto rollback on close" feature into any future versions of SH3Cmdr??
I guess the answer will probably be a "no", or you would already have implimented it!!
This aspect seems to me to be the main cause of any problems which users have, in running SH3 through SH3 Cmdr. Everything else does exactly "what it says on the tin"!!!
Congratulations on a fine programme, and keep up the great work!
Regards,
Dave