Tool updated to 2.6 :
 * Added REG file for Island Paradise EP
 * Minor fix : no unnecessary script launch when it's the first launch (config file edition)

To install the patch, there one solution :
Install base game, patch it and copy content ("The Sims 3" folder) into "App" folder of my script (replace old files).
EA doesn't share unpacked content of its update, so we MUST install the base game to patch it.
But good news, there is nothing to do for EP/SP
So yes, just install base game, patch it and copy content.

You need to modify REG files ONLY if you want to replace the (fake) CD key by your real CD key. It's optionnal because all game+expansions work without any modification.
I'm sure that your problem is related to the version of your base game : for every newer expansion "installed", you need to patch the base game to detect and load the new expansion. But there is a problem. My script cannot allow users to manually patch the base game even if portable game is loaded.

The only way I know to patch your portable base game is to install the base game (The Sims 3), patch it to the latest version and copy (or move) the updated base game into the App folder.
Or, more easily, you can install the base game (and only the base game : The Sims 3) into the App folder (you can use options when you install the game to specify where the game will be installed. Please use US name -> The Sims 3). You will be able to patch the game manually

Don't forget to re-install the latest NO CD patch !

100% right

Is it what you want?

Maybe a torrent in preparation but not sure... it would be a big torrent !

Thank you very much ! Were you able to test the tool? I try to have most possible feedback to make a most compatible possible tool. 

Hi everyone !
I've made a script to allows anybody to play to The Sims 3 game with expansions/kits and saves EVERYWHERE (a computer with Windows OS is required), from an internal/external hard drive, USB key, etc.
In other words, this tool make your game "portable". Installing the game again and again just becomes a bad memory !

Content of the archive :
"App/" -> Where the game, kits and expansions have to be placed (with english name).
"Data/" -> Where personal files like save files are REALLY stored.
"Script/" -> Where script files are stored. You don't have to modify anything in this folder and sub-folders.
"Read me - Lisez-moi.txt" -> A file that explains how to use the script.
"The Sims 3 Portable - Menu.exe" -> This app is used to launch the menu (hidden script). Automatically run as administrator.
"The Sims 3 Portable - Menu (Run as admin).cmd" -> This file is used to launch the menu (visible script). Works on 32 and 64 Bits Windows but needs to be run as administrator explicitly (right-click on the file).


How it works?
1. It loads your save directory ("Data/[Your_Username]/The Sims 3 Portable/*" into "[Current User]/Documents/Electronic Arts/*". Existing saves are backed up and restored when game (or any game app) is closed.
2. It loads registry keys and values are suitables to the current script path. So, you can move your game and the game still works ! Registry keys are backed up and restored.
3. It temporary associates Sims3Pack file type to the portable game. When the portable game, the portable launcher or the "pause" is launched and active, you can install your Sims3Pack files like if the game were installed.
4. A menu of options is available. You can launch the game, the Sims 3 Launcher, a "pause" instead of the game, open save folder, etc.
Here the options :
5. You can easily modify the language and disable any kit or expansion !
6. No need to install DirectX. Required DLL is copied into the bin folder of The Sims 3.
7. No key required with a proper fix !
 
How can we use it?
Before all, your session must have ADMINISTRATOR RIGHTS to allows registry modifications. The script programs ask you to have access to these rights, but if you directly run a BAT or CMD file, you need to do it with administrator rights (right-click on the file).
If you don't understand what I wrote, it's not important.
1. In "App" folder, you have to paste (or move) your game and kits+expansions with ENGLISH names even if you want to play with another language. Exemple : "App/The Sims 3" ; "App/The Sims 3 Ambitions" ; "App/The Sims 3 Katy Perry Sweet Treats" ; "App/The Sims 3 70s, 80s, and 90s Stuff"...
Names of game, kits and expansions have to correspond to the names of the REG files in the "Script/Profile/The Sims 3". Any folder that doesn't correspond to these REG file names won't be loaded, so you can disable an expansion or kit just be renaming it.
Or the list of names is available here :
2. You have to launch the script. Application "The Sims 3 Portable - Menu.exe" can load the script menu and then ask you to enter a letter of your choice (each letter corresponds to an option) and validate it by pressing the "Enter" button of your keyboard. For the first time, you have to leave the field blank and press the "Enter" button without any letter (this normally launch the game).
3. After the first launch of the script, the game is not launched as expected but a file "The Sims 3.ini" is created and opened to be edited.
Add the new line applang=en-US into this file and save it. You can enter the language code you want (en-us,fr-fr,es-es,es-mx,de-de,it-it,nl-nl,sv-se,da-dk,no-no,fi-fi,pl-pl,pt-pt,hu-hu,cs-cz,pt-br,el-gr,ru-ru,ko-kr,zh-hk,ja-jp). Note that if applang variable is not defined in this file, the game will be launch with the default language : french.
4. Now, you know how to open the menu to have access to options or to launch the game ! Re-open the menu and press "Enter" without any letter specified.
If you're not on a weird computer, the game starts and you can play !


Note : You can install your PACKAGE files into "Data/Common Mods (The Sims 3)" directory ! This directory will be loaded into each save of the game, excepted if the "Mods" directory already exists.
Patching the game will be very difficult. The simpliest way to patch the game is to install base game anywhere, patch it and copy the content of the game into the "App/The Sims 3" directory.
You can add you own REG file into the "Script/Profile/The Sims 3" folder to load a new kit or expansion ! Be careful, name of this REG file has to be the same than the name of the kit/expansion folder (in "App").
You can also add the cd key corresponding to the game into these REG files : modify
[HKEY_LOCAL_MACHINE\SOFTWARE\Electronic Arts\Sims\The Sims 3 [Title]\ergc]
@="ENTER YOU CD KEY HERE, WITHOUT MINUS SYMBOL (-)"
Exemple :
[HKEY_LOCAL_MACHINE\SOFTWARE\Electronic Arts\Sims\The Sims 3 Seasons\ergc]
@="12345ABCD6789EFGH0123"
(It's not a real key !)
/!\ You have to insert a cd key (even a fake like ABCDEF...) for "The Sims 3.reg" if you want to install Sims3Pack ! If there is no cd key, an error will occurs.

DOWNLOAD :
http://jheberg.net/captcha/the-sims-3-portable-kit-v27/
http://ezcw3m.1fichier.com/
http://uploaded.net/file/z3ripmz0

I'm sure that "skuversion.txt" is not a core file because when you edit this file, game version is not changed (but when you edit "default.ini", it does). Furthermore, "skuversion.txt" is not present in the "Game/Bin" folder in the DVD (or ISO file). It's added by the installer when you install the game — and I don't use installer because I manually move files/folder and add registry keys (by the way, no more cd key to specify !)
"Default.ini" is no regenerated but disabling this file causes a game version display bug in the launcher. Game starts normally.
As my others suggestions, it's another detail, but it's very easy to modify.

All the best for your project(s) !

Yeah, I don't like to add extra-files in my Windows folder too ^^

I didn't know that other languages (excepted Chinese, Japanese, Korean and Thai) use "The Sims 3" I thought each language had its title.
I think my way will work with all languages (or an error could occur for asian languages, but it will be surprising) and your updater could be universal !

I'm ok with your explanation. However, users should not use desktop as a normal folder and only place shortcuts there, but it is their job ! Instead of "%data%", I thought "%data%/Eletronic Arts/%locn%" was a better path. I think game (mods) files should not be mixed with docs files - I know that is just my point of view. Often, I move my save dir on my external hard drive.

Oh, and one more thing ! "skuversion.txt" file is not a necessary file for the game. It can be deleted, modified and the game will still work. "Default.ini" contains the same information (GameVersion = X.X.X.X) and is a more relevant file It's just a detail, but a tool is made of details !

And I've forgotten one important thing : nice work for your updater, it really works and is very usefull. I work with a lot of BAT scripts too and it is a funny game for me to share tips to others who really want to improve their scripts and skills. Confronting your scripts to public is a very good way (the best?) to do it !

Yes ! The path where the script (BAT) is placed is not a default place where the script looks for commands, such as EXE or other CMD or BAT files.
A script can automatically find commands in specials paths contained in the variables %PATH%, %CD% (current dir) and maybe %TEMP% and others... But "script path" isn't one of these.

I've seen cd /d "%docs%" in your script so %CD% variable (which is a default path where the script can find commands) is not the "script path" anymore when it verifies if commands exist.
The script can recognise wget(.exe) and unzip(.exe) ONLY if they are located at %docs% path

There are 3 solutions:
1. In your script, rename all wget and unzip calling commands by %~dp0wget.exe and %~dp0unzip.exe commands.
2. In your script, at the beginning, add the command set path=%~dp0;%path%. This operation add the "script path" to defaults paths where the script can find commands, even if "Current Dir" is defined elsewhere. So have not to modify your script, just add this line and your script can work everywhere.
3. I think this is the best solution BUT it's the solution which requires most modifications. You should NOT use CD command.
Exemple :
becames
(and be carefull there is an unecessary space after %ver% !)

I know that for some reasons (especially when you use parenthesis), using a path with special caracters (like (, ), &, ...) into a FOR or IF commands can cause unexpected errors when script executes the command.
The only solution I know is to change "Current Dir" before the FOR or IF command. But there is a better way than CD command, use PUSHD command !
This command is compatible with Vista, 7 and 8 and I think with XP too but has one thing more than CD command, you can reverse your "current dir" variable to the old "current path" with de POPD command. In other words, you can temporarily change "current path" with PUSHD and restore it with POPD.


Suggestions :
1. I've not read entirely your script but I know that you have to define the save path according to language, and it's complicated because you have to translate the name for every languages ! EA engineers are not very smart...
I suggest this little piece of script :
Find "Mods\Resource.cfg" in all sub-folders of "%docs%\Etectronic Arts" and if it found, set locn variable with the current name of the sub-folder. It will NOT correctly work if there are more than 1 sub-folder where "Mods\Resource.cfg" can be found because ONLY the last scanned sub-folder will be returned and set into the variable.
To be perfect, all commands where you have to use locn variable should be replaced with this FOR command that I've suggested and set "locn=%%a" would be replaced by the command(s) you want.

2. You were confronted with the "Wow6432Node" problem when you used the REG command. I suggest to use this code :
And when you need to use REG command, you can insert archtype variable into the path :

3. I've noticed that "AwesomeMod Updater" folder is created into %docs% folder. Why not the "script dir" ? I think that it would be preferable

You can increase your script compatibility by replacing each "wget" and "unzip" words by "%~dp0wget.exe" and "%~dp0unzip.exe".
"%~dp0" is the source path where the script is launched from (= where the script is placed).
So you can use CD command (I prefer PUSHD) as often as you want, "%~dp0" variable won't change
Supported for all NT OS.

(I had to do this modification for me because wget and unzip were not recognized commands.)