Version 2.49 was released not long ago. Installation went well, all was fine.
This morning AU told me there is another update (update.library and Update Prefs) so i installed them.
Now i get a crash on every start, after AU checked for updates, always the same, some end_handler and the reason is update.library (53.19)...reverting to the last version now (53.18).
Crash log for task "SYS:System/AmiUpdate/AmiUpdate"
Generated by GrimReaper 53.19
Crash occured in module update.library at address 0x7F4EF5D4
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003
There was a problem saving the submitted bug (), please try again.
Sorry, can't add it to the bug tracker
Here are the details:
Crash: v2.49 offers an updated update.library (also v2.49) but after installation AmiUpdate crashes
v2.49 offers an "updated" (determined by date) update.library of the same version (2.49). After installing this, AmiUpdate crashes reproducably in end_handler and the reason is that "updated" library.
Crash log for task "SYS:System/AmiUpdate/AmiUpdate" Generated by GrimReaper 53.19 Crash occured in module update.library at address 0x7F4EF5D4 Type of crash: DSI (Data Storage Interrupt) exception Alert number: 0x80000003
Update library in the latest update seems corrupt. its size is only 56144 bytes while previous ones are around 1Mb (1121860 bytes for the previous one).
Yes, and the same goes for the prefs_updates (as mentioned in the other thread). The one in the separate archive is 145172 bytes, while the one in the full update is 151060.
I'm wondering why there has to be a separate product for the library and the prefs program, when everything is already in the main archive. Much too much that can go wrong this way - and as we have seen, Murphy's Law is still in effect.
No idea what's going on here. I spent ages testing it all out in different situations and it worked perfectly here (despite what others may think!).
Anyway, I have removed the separate updates from the database now, so all the components in the main archive should gel together (they do here, at least).
Sorry for the confusion.
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
For me AmiUpdate stopped working long ago.. for some unknown reason (at least for me), the language is broken along with the buttons that have all the text weird inside... any idea on how to fix this problem??
nope. it doesn't work.. honestly i don't remember when it started but after an update the buttons and the translations were messy. I also tried to update italian catalog from os4depot but nothing changed..
I also tried to reinstall AmiUpdate from the link few post above but nothing.. to give you an idea, if I click the "Thanks/Grazie" button it shows the info window of the archive. If I press the "Abort/Interrompi" button it download the archive. It always tell me that it cannot download/synchronize with the server but it does instead and it show a string that is part in italian and part with a format symbol like "%s" ..
Try setting your language to English (i.e. remove the languages in Locale Prefs and let it default to English).
Then with your older AmiUpdate search for updates using the English UI and get the new 2.49 AmiUpdate as well as the latest Italian locale for it (and/or whichever other locale you may want).
Deselect any and all other updates, so they don't interfere for now.
You may get an error and some Grim reapers when trying to exit AmiUpdate, but just ignore them and do a reboot.
Afterwards, you should be able to set you preferred language(s) again, and hopefully the texts will be where they should.
thanks, in english it works fine like it should but when i put italian, all the options are messy.. don't know why. At least, with my workbench in english, everything is fine and it is ok for me :) thanks for the help
You need an updated Italian catalog. Isn't one offered when checking for updates? I'd recommend to delete the Italian catalog manually and then check again.