AwesomeMod Updater (v2.8.3 - Updated 2013-10-16)
Matildarose:
Quote from: basbas on 2010 November 25, 20:24:34
Error code 1 would indicate that there is both a 32-bit AND a 64-bit registry entry of The Sims 3 in your registry, which is practically impossible. However, v2.2.2 ignores this error and just continues.
ETA: I tried that Custom Launcher thing in combination with v2.2.1 and it worked just fine, though.
Updated to v2.2.2
- Ignores error 1.
Updating to v2.2.2 is not necessary if you didn't have issues with v2.2.1.
Yeah, I'm not sure what happened there either. It works now, however!
basbas:
December 1
Updated to v2.2.3
Fixed check for AwesomeMod test version.
December 3
Updated to v2.2.4
Added 'continue anyway' option to the patch compatibility notice, as Pescado didn't update rtfm.txt for the latest patch. Could you fix this, Pescado?
basbas:
v2.3beta
At this point, I would consider v2.3 stable enough to replace v2.2.4. But, because of the issues with v2.2 after the release, I offer it as a beta version first. If I don't get any feedback or bug reports for one week or so, it will replace v2.2.4.
New in v2.3:
- The updater can now update itself. However, it will ask you if you want to apply the update or not.
- New way of finding the Documents\Electronic Arts\The Sims 3 folder: the updater finds the locale code (like en-US) in the registry and compares it with the new inculded file, locale.aweupd, which needs to be placed in the Windows directory.
- Built-in AwesomeMod test version download: downloading a seperate awetest version isn't required anymore.
- Other minor inprovements; see the Changelog for details.
So, please test this and give feedback.
v2.3beta - build 60 is included below. If I fix something in the next build, the updater will download it.
December 13: Updated to build 61. Build 60 will download it automatically.
December 14: Updated to build 62. Build 60 and 61 will download it automatically.
December 15: Updated to build 63 (final). Build 60, 61 and 62 will download it automatically.
Attachment deleted. Final version available in original post.
Matildarose:
I tried the newest version, if just to see if it no longer gives me an Error 1, but, unfortunately, it still does. The new file is in the windows directory and everything.
I'm... not even sure why I'm still getting this error, but eh, 64x systems just always seem to have weird stuff happening all around.
basbas:
Quote from: Matildarose on 2010 December 13, 03:42:58
I tried the newest version, if just to see if it no longer gives me an Error 1, but, unfortunately, it still does. The new file is in the windows directory and everything.
I'm... not even sure why I'm still getting this error, but eh, 64x systems just always seem to have weird stuff happening all around.
Build 61 hopefully fixes this. Unfortunately, build 60 checks for error 1 before checking for an update, so you'll have to download build 61 manually. Note, error 1 is an error which shouldn't occur on any computer, so there might be something wrong with your pc.
Other users of build 60 will be notified of the update. This is a nice check if that works, too.
Expected behaviour: screen with "Build 61 has been downloaded", pressing 1 will update it and then immediately start the new build. Pressing 2 will not update it and continue with build 60. Pressing 3 will exit immediately.
Does this work?
Hyper late edit: removed not-working link to build 61.
Navigation
[0] Message Index
[#] Next page
[*] Previous page