AmiUpdate issues

A forum for general AmigaOS 4.x support questions that are not platform-specific
emulajavi
Posts: 17
Joined: Fri Nov 15, 2013 1:06 pm

AmiUpdate issues

Post by emulajavi »

Hi,

I’m having some issues trying to get AmiUpdate to update itself or even manually installing the latest version.

I’m on a X1000 with OS 4.1 Update 6 which was last used on November 2024.

My AmiUpdate version was 2.49. When I click on scan (active server www.amiupdate.net and the update.amigaos.net) it doesn’t offer any AmiUpdate updates (nor 3rd party updates).

If I manually try to install 2.55 it gets stuck just at the end

Image


I then have to power down the X1000. After that AmiUpdate doesn’t launch again.

I found a 2.47 version I had downloaded long time ago, and it installed perfectly overwritting the 2.55 files. It now launches fine, but still it doesn’t offer to auto update.

Why isn’t it offering to auto update to the latest version?

Will there be any logs in the system about what happened when it got stuck in the manual 2.55 installation?

Thanks!



edit: i attach au.log of 2.47 not being able to autoupdate

Code: Select all

miUpdate 2.47 (29.12.2019) Part of the AmiUpdate suite

Log opened on 5-6-2025 at 12:17:42

12:17:42 Performing online version check...

12:17:42     Requesting HTTP header file from server...

12:17:42     Trying to connect to: amiupdate.net on port: 80

12:17:42       Connected

12:17:42       Received HTTP header file...

12:17:42     Error 405 returned from HEAD request: 

12:17:42 Online version check completed.

12:17:42 Program started

12:17:42 Started system scan

12:17:42   Found host machine as: X1000

12:17:42   Synchronising with server: 'www.amiupdate.net'...

12:17:42     Requesting HTTP header file from server...

12:17:42     Trying to connect to: amiupdate.net on port: 80

12:17:42       Connected

12:17:42       Received HTTP header file...

12:17:42     Error 405 returned from HEAD request: 

12:17:42       HTTPFetch error: Transferring the file was not possible due to a previous error

12:17:42 Scan completed

12:17:42 Waiting for user input...

12:17:49 Starting uniconify...

12:17:50   Opening window...

12:17:52 Started system scan

12:17:52   Found host machine as: X1000

12:17:52   Synchronising with server: 'www.amiupdate.net'...

12:17:52     Requesting HTTP header file from server...

12:17:52     Trying to connect to: amiupdate.net on port: 80

12:17:52       Connected

12:17:52       Received HTTP header file...

12:17:52     Error 405 returned from HEAD request: 

12:17:52       HTTPFetch error: Transferring the file was not possible due to a previous error

12:17:52 Scan completed

12:23:24 Starting uniconify...

12:24:09 Started system scan

12:24:09   Found host machine as: X1000

12:24:09   Synchronising with server: 'update.amigaos.net'...

12:24:09     Requesting HTTP header file from server...

12:24:09     Trying to connect to: update.amigaos.net on port: 80

12:24:09       Connected

12:24:09       Received HTTP header file...

12:24:09       Basic Authorisation required for this update

12:24:09       User and Pass found in sitelist

12:24:09       Authorizing...

12:24:09     Trying to connect to: update.amigaos.net on port: 80

12:24:09       Connected

12:24:09       Received HTTP header file...

12:24:09         Failed to get filesize from header, Content-Length: tag missing

12:24:09     Starting file download (unknown size )

12:24:09     Trying to connect to: update.amigaos.net on port: 80

12:24:09       Connected

12:24:10     Synchronisation successful

12:24:11 Scan completed

12:24:33 Started system scan

12:24:33   Found host machine as: X1000

12:24:33   Synchronising with server: 'www.amiupdate.net'...

12:24:33     Requesting HTTP header file from server...

12:24:33     Trying to connect to: amiupdate.net on port: 80

12:24:33       Connected

12:24:33       Received HTTP header file...

12:24:33     Error 405 returned from HEAD request: 

12:24:33       HTTPFetch error: Transferring the file was not possible due to a previous error

12:24:33 Scan completed

12:24:35 Closing program


Last edited by emulajavi on Sun Jun 22, 2025 1:17 pm, edited 2 times in total.
emulajavi
Posts: 17
Joined: Fri Nov 15, 2013 1:06 pm

Re: AmiUpdate not autoupdating

Post by emulajavi »

Little update.

I’ve managed to get AmiUpdate to show the update and auto update: the trick was changing the server from amiupdate.net to codebench.co.uk/amiupdate_website

Then this is what appears as available updates:

Image

If I select the update of AmiUpdate it will update but after reboot, a second after launching AmiUpdate the system will get stuck requiring a hard reboot. (I then manually install AmiUpdate 2.47 to gain back access to AmiUpdate)

Also, if I update listbrowser gadget, lot of apps won’t be able to start giving an error. (I’ve used rollback to go before those 6 OS updates, and now apps launch again)
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: AmiUpdate not autoupdating

Post by nbache »

emulajavi wrote: Thu Jun 05, 2025 4:34 pmI’ve managed to get AmiUpdate to show the update and auto update: the trick was changing the server from amiupdate.net to codebench.co.uk/amiupdate_website
I use www.amiupdate.net without problems (on AmiUpdate 2.55).
emulajavi wrote: Thu Jun 05, 2025 4:34 pmIf I select the update of AmiUpdate it will update but after reboot, a second after launching AmiUpdate the system will get stuck requiring a hard reboot. (I then manually install AmiUpdate 2.47 to gain back access to AmiUpdate)
The problem with some previous versions of AmiUpdate and self-updating is that it steps on its own toes trying to update a module (the library, I think) while it's in use. It should be okay after a reboot, i.e. you shouldn't have to go back to an older version - that's like going from the frying pan back into the fire :-). And the problem should be fixed with AmiUpdate 2.55, so it shouldn't happen again - if you stick to 2.55+, of course.
emulajavi wrote: Thu Jun 05, 2025 4:34 pmAlso, if I update listbrowser gadget, lot of apps won’t be able to start giving an error.
Could you please list (at least some of) the programs which won't start after the update?
emulajavi wrote: Thu Jun 05, 2025 4:34 pm(I’ve used rollback to go before those 6 OS updates, and now apps launch again
Why roll back them all if it's only listbrowser causing problems? Please try installing the others again to make sure that is the only issue.

Best regards,

Niels
emulajavi
Posts: 17
Joined: Fri Nov 15, 2013 1:06 pm

Re: AmiUpdate not autoupdating

Post by emulajavi »

Hi @nbache

Thank you for your answers. I rolled back the 6 because I didn’t know if any of the other 5 could be causing problems like the freeze of AmiUpdate 2.55

I’ve now installed one by one the other five, testing after each that apps still launch normally.

Just after updating the listbrowser.gadget and letting AmiUpdate perform the soft reboot…

- Desktop was back without the AmiDock on the bottom right. No matter if I reboot, the dock does not come back.
- Right clicking on the top bar on ‘update software’ does nothing. AmiUpdate won’t launch.
- Trying to open one of the .pdf of the desktop (that opened fine before the update) shows and error
- trying to open USB Inspector shows an error
- Trying to open UnArc shows an error
- Trying to open Prefs:AmiSphere shows an error
- Trying to open Prefs:AHI shows an error
- Trying to open System_Rollback shows an error
- AmiStore opens fine.

Just by placing on SYS:Classes/Gadgets/ the old listbrowser.gadget (size 95.460 date 2013) and Ctrl+LAmiga+RAmiga to reboot AmigaOS, AmiDock appears again and all those apps launch fine.

So it seems that the updated listbrowser.gadget (size 99.936 date 2022) that AmiUpdate installs, breaks it all on my system. Maybe this new listbrowser.gadget depends on other file(s) to also be updated to work well?

listbrowser.gadget as only update selected
Image

update installed, just before soft rebooting
Image

after reboot, desktop without AmiDock
Image

error trying to open one .pdf
Image

update software… does nothing. AmiUpdate doesn’t appear
Image

error trying to open USB inspector
Image

error trying to open UnArc
Image

error trying to open AmiSphere
Image

error trying to open AHI
Image

error trying to open System_Rollback
Image

listbrowser installed by AmiUpdate (size 99 and date 2022)
Image

old listbrowser before updating (size 95 and date 2013)
Image

Thank you!
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: AmiUpdate not autoupdating

Post by nbache »

This looks strange.

The first thing that comes to mind it that somehow you've got a damaged listbrowser.gadget with the update, although I can't see why this would happen to you and not everybody.

Still, it's a possibility.

Try, wiht the new listbrowser.gadget installed, to open a Shell and enter "SYS:Classes/Gadgets" (without the quotes, of course). Then enter:

Version listbrowser.gadget FILE FULL

- you should get:

listbrowser.gadget 53.79 (16/07-2022)

Then enter:

md5sum listbrowser.gadget

- you should get:

a9cf55f171ee3478efe7d8c306515f31 listbrowser.gadget

For now, let's see what happens with those checks.

And BTW, did you go back to the newest AmiUpdate again? I don't necessarily trust that things are installed correctly with the older ones, so please make sure you're on 2.55.

Best regards,

Niels
emulajavi
Posts: 17
Joined: Fri Nov 15, 2013 1:06 pm

Re: AmiUpdate not autoupdating

Post by emulajavi »

Hi,

Thank you for your reply

The file seems to be fine

Image

Although the file is there (with the same exact name as the old version) it’s like the applications that rely on it aren’t able to use it, so AmiDock doesn’t appear, AmiUpdate doesn’t launch, etc

Is there anywhere a log file that can show what can be preventing AmiDock for launching?
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: AmiUpdate not autoupdating

Post by nbache »

Your best bet is probably to run Snoopy while trying to launch one of the programs.

Maybe it will show something interesting.

But remember that not everything shown as FAIL in Snoopy is a problem, it depends on the situation.

E.g. if a program is looking for some resource which can be in one of several paths (a typical example is a catalog), it may show FAIL for the first possible path and then okay for a subsequent one.

Still, this could reveal something we haven't yet considered.

Oh, one more thing. Could you try doing a

list listbrowser.gadget

in the SYS:Classes/Gadgets dir? It will show whether for some reason e.g. the R bit has been reset on the new file.

Here, I see:

listbrowser.gadget 99936 ----rw-d 16-Jul-22 15:26:24

Best regards,

Niels
emulajavi
Posts: 17
Joined: Fri Nov 15, 2013 1:06 pm

Re: AmiUpdate not autoupdating

Post by emulajavi »

nbache wrote: Fri Jun 06, 2025 10:35 am
Oh, one more thing. Could you try doing a

list listbrowser.gadget

in the SYS:Classes/Gadgets dir? It will show whether for some reason e.g. the R bit has been reset on the new file.

Here, I see:

listbrowser.gadget 99936 ----rw-d 16-Jul-22 15:26:24

Best regards,

Niels

Hi Niels,

Thank you.

The output is the same as yours. One other thing I’ve tested is to rename listbrowser.gadget to something else, to see what happens if the file listbrowser.gadget is not present inside the gadgets folder. And the applications give the exact same error as before.


Maybe the time has come for me to upgrade to 4.1 FE, to avoid having issues like this one…

Image
User avatar
nbache
Beta Tester
Beta Tester
Posts: 1744
Joined: Mon Dec 20, 2010 7:25 pm
Location: Copenhagen, Denmark
Contact:

Re: AmiUpdate not autoupdating

Post by nbache »

Oh, darn. I should have read your very first post more carefully.

So you're not even on FE? I had missed that.

In that case, forget everything I've written. Those updates don't apply to the older OS version.

And please, yes, do get, install and register FE, and then the updates to FE (update 1 should be installed manually, without using AmiUpdate).

I just don't understand how AmiUpdate (even an older version) could list those updates for you at all if you're on an older, not supported OS.

Best regards,

Niels
emulajavi
Posts: 17
Joined: Fri Nov 15, 2013 1:06 pm

Re: AmiUpdate not autoupdating

Post by emulajavi »

nbache wrote: Fri Jun 06, 2025 4:35 pm Those updates don't apply to the older OS version.
I have now made rollback of the 6 updates, installed back AmiUpdate 2.47, ordered a 4.1 FE copy for X1000, and once it arrives I will install it.

AmiUpdate offering those upgrades (certainly the listbrowser.gadget one and I don’t know if any of the other 5 could or not have any compatibility issues) for OS 4.1 Update 6… is what has caused the issues. Also, at least for me, AmiUpdate 2.55 might be incompatible with OS 4.1 Update 6.

Anyway… when they released 4.1 FE, they should have call it 4.2, to avoid confusion between OS 4.1 Update X and OS 4.1 FE Update X

Thank you very much for your help.
Last edited by emulajavi on Fri Jun 06, 2025 11:56 pm, edited 1 time in total.
Post Reply