The Sims 3: Download All Updates at Once

Sunday, 19. December 2010

If you can not use the EA Download Manager or are unable (or unwilling) to install the incremental updates manually, there are “super” patches available officially from EA which will update you to the newest version from any version of the game.

These patches are listed on the Sims3 online forum, located here:

http://forum.thesims3.com/jforum/posts/list/175477.page

The “super” patches are about 400MB.

The manual incremental patches are available here:

http://forum.thesims3.com/jforum/posts/list/188505.page

For the purpose of archiving, at the date of December 19th, 2010 the following “super” patches were available at these links:

(region instructions further down)

Region 1
http://akamai.cdn.ea.com/eadownloads/u/f/sims/sims…s/TS3_1.18.9.009001_Update.exe
Region 2
http://akamai.cdn.ea.com/eadownloads/u/f/sims/sims…s/TS3_1.18.9.009002_Update.exe
Region 3
http://akamai.cdn.ea.com/eadownloads/u/f/sims/sims…s/TS3_1.18.9.009003_Update.exe
Region 5
http://akamai.cdn.ea.com/eadownloads/u/f/sims/sims…s/TS3_1.18.9.009005_Update.exe
Region 7
http://akamai.cdn.ea.com/eadownloads/u/f/sims/sims…s/TS3_1.18.9.009017_Update.exe

Find out your region by navigating to C:\Program Files\Electronic Arts\The Sims 3\Game\Bin and open “Skuversion.txt”
Do NOT change anything in this file. The last number in “Game Version” indicates your region. For example:
GameVersion = 1.12.70.006001
This game version would be region 1.

WordPress: Page Not Found on Permalink

Sunday, 26. September 2010

Remember: Please write in the comments area whether or not you had success with this solution, and share other ideas.

Issue: When clicking on “Older Posts” which brings you to the URL “page 2” (page2), you get a 404 error page.

Problem: Apache mod_rewrite is disabled –or– “AllowOverride” is set to “none” in your Apache configuration file for the virtual server.

Solution: In my case, the problem was with AllowOverride being set to none.

Simply look though your Apache configuration file, and change “none” to “all” for AllowOverride.

Here is an example of what this should look like:
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride all
</Directory>
<Directory /var/www/>
Options Indexes FollowSymLinks MultiViews
AllowOverride all
Order allow,deny
allow from all
</Directory>

WARNING: You should only change AllowOverride to all for the web directory. (Exclude all other items, such as CGI or usr/share/doc). Leave these alone!

Solution 2: This second option works, but does not fix the underlying problem.
Go to your Permalinks settings page in WordPress. Under “Custom Structure”, add /index.php before the line.
Eg:
/%year%/%monthnum%/%day%/%postname%/
should look like this:
/index.php/%year%/%monthnum%/%day%/%postname%/

All links will go through index.php. If you change these links back to not having index.php, they will still redirect properly.

Solution 3: Go without custom permalinks structures.
The disadvantage is that Google doesn’t like these, since the actual link tells Google nothing about the page. For higher ranks in searches, you should avoid this.
Simply go to the Permalinks settings page in WordPress, click “Default” and save changes.

A general reminder: It’s usually a bad idea to constantly switch permalinks. It places you farther behind in Google because your links are always becoming broken. Choose a structure, and stick with it!