The 2.52 update is now live. I've noticed there are a number of bugs on the bug tracker that could do with checking. So if you have any outstanding ones, and have some time, please recheck with 2.52.
The new version 2.52 was not displayed via AmiUpdate 2.51, I downloaded it from the AmiUpdate website and installed it.
AmiUpdate 2.52 now works very well again. The prefs settings can be set and saved. "Start iconified (recommended)" via AmiDock works
Thank you very much for the new version. AmiUpdate 2.51 did not show the 2.52 update, so I downloaded the full 2.52 archive and installed that.
As others already said, 2.52 now works flawlessly. No more error messages, and it also showed two additional updates that I never saw with 2.49, 2.50 or 2.51.
i had the 2.49 version on my pegasos and couldn't 'see' anything newer. i download v2.52 from your page, use the installer and it works fine. it even found the latest dopus update!
Another error has crept in, namely when you start the search via the prefs there are also error messages. Very few people will do this, but the bug is there.
Is there a way to donate to their work? PayPal would be ideal...
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
Started up 2.51 on my X1000 and it offered the update to 2.51. After selecting Yes, downloading and rebooting, 2.52 works just fine again with AmiDock.
Thanks for all your good work with this,
Valiant@Camelot AmigaOne XE, 800Mhz, 1GB, 9250 Radeon, OS4.1u7 Sam440ep, 666Mhz, 512Mb, 9250 Radeon, OS4.1u6 A1-X1000, 1.8Ghz, 1GB, 9250 Radeon, OS4.1x A1-X5000/40 2.2Ghz, 2GB, Radeon HD 7700, OS4.1 FE ud 2
Amiupdate 2.52 (current latest version) If you go in preferences and than verify now, you got same errors than public 2.49 version. Amiupdate now finds two updates, Dopus and another but once selected do not install any update for real. Once you load a new scan same updates are found.
@Rigo what about Codebench? Are you planning to release new version in a short time?
I've noticed there are a number of bugs on the bug tracker that could do with checking. So if you have any outstanding ones, and have some time, please recheck with 2.52.
That reminds me: Is there any way to search in the bug tracker for entries by a specific person (e.g. myself )?
For those that are not seeing the update in the list, please enable the "Add extra info to log" menu, and check the AU.log in RAM: after a scan. Search for "AmiUpdate", and the log /should/ tell you why it feels this update is not required.
I can't understand why some see it, and some don't. More info needed, I'm afraid.
With regard to the MD5 sums changing, most likely that's because I compile everything cleanly prior to release just to be on the safe side, and there may be some file changed that doesn't affect the program, but may be enough to alter the MD5 sum. Better it works, than checksums being different, no? Basically if it has the same version number, it's functionally the same.
As a side-note: a last minute application interface conflict was found, so I've just released Update prefs 53.17 as well.
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
The whole bug tracker definitely needs some serious love but that's a job for another time, unfortunately.
That said, do you not see the "My Bugs" button at the top once logged in?
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
21:23:35 Synchronising with server: 'www.amiupdate.net'...
21:23:35 Testing for active network connections...
21:23:35 Found interface RTL8139, testing...
21:23:35 Interface is currently configured, checking state...
21:23:35 Interface is UP, check complete
21:23:35 Trying to connect to: amiupdate.net on port: 80
21:23:35 Connected
21:23:35 HTTPFetch error: Transferring the file was not possible due to a previous error
...
21:23:43 Synchronising with server: 'www.amiupdate.net/SdkServer'...
21:23:43 Testing for active network connections...
21:23:43 Found interface RTL8139, testing...
21:23:43 Interface is currently configured, checking state...
21:23:43 Interface is UP, check complete
21:23:43 Trying to connect to: amiupdate.net on port: 80
21:23:43 Connected
21:23:43 HTTPFetch error: Transferring the file was not possible due to a previous error
21:23:43 Synchronising with server: 'amiupdate.codebench.co.uk'...
21:23:43 Testing for active network connections...
21:23:43 Found interface RTL8139, testing...
21:23:43 Interface is currently configured, checking state...
21:23:43 Interface is UP, check complete
21:23:43 Trying to connect to: amiupdate.codebench.co.uk on port: 80
21:23:43 Connected
21:23:43 HTTPFetch error: Transferring the file was not possible due to a previous error
I assume by the server names, you are using an older version of AmiUpdate?
Rather than change all your settings around, download the latest archive from here and install it manually.
This is most likely a problem caused by the redirection issues surrounding the subdomains and forwarding. 2.52 cures this internally.
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
When I run my current version (2.49) it doesn't detect any updates.
I downloaded the version you linked above, but when I try and run the installer, it stops:
"COPYFILES: Couldn't copy file 'DockStrip' in line 116.
DOS Error Type: Unable to access a file or drawer -- object in use"
I tried manually copying across AmiUpdate from the archive, but when I run it it crashes.
Also perplexed by update library. Both the version I have and the version in the archive have the same version string 53.19 but different dates and differnt file sizes.
Did you have AmiUpdate running when you tried to update it? You need to close that down before reinstalling with the latest downloaded version. It will then be able to update itself while running as was the case previously.