Yeah Rigo, this is what I saw at the VCF

The scheduled scan feature is a welcome addition.

@Rigo

Congrats ! And Thanks !

The scheduled scan was always there, it just needed the SCANDELAY tooltype value setting. But the tooltypes system was just too awkward to use, which is why the prefs editor was inroduced.

Enjoy!

Thanks Rigo AmiUpdate is a great application for a lazy guy like me
Wish more developers would use it.

That's what email is for, it's the perfect "pestering" tool :)

Simon

Thanks Rigo, AmiUpdate is a very nice app

@Rigo

The AmiUpdate AutoInstall isn't working, Installer gives error "unable to open script". AmiUpdate also didn't find the update until I clicked "scan", which is unusual.

edit I think the issue is you've "run" Installer from AutoInstall, meaning the script exits immediately and AmiUpdate deletes the archive it has downloaded/extracted before Installer has a chance to read the script or copy any files.

I would advise everyone to simply download the archive from the website and run the installer that is in it. Because of the vast changes made, it's very difficult for me to ensure that auto updates are still handled correctly.

EDIT: I have updated the archives with an AutoInstall that doesn't "run" the installer upon Chris' advice. The above still stands though :)

Simon

@Rigo
Thanks! Very appreciated!!

Great work Rigo.

I hope some day we will be able to do AmigaOS updates via AmiUpdate as well. AmiUpdate seems mature enough to tackle the job IMHO.

That remains to be seen :)

There have been some serious changes in operation in the underlying system, although visually the changes look purely cosmetic. Nothing a few coding sessions won't cure, I guess :)

Simon

The images on the GUI are not a trasparent PNG ?

They have a white background so they doesn't look very good on my theme, ok isn't a huge problem aniway ...

great news! it should be part of AmigaOS4.2 & beyond!...I use AmiUpdate all the time

I wanna start AmiUpdate iconified as menu without the showing of the AmiUpdate window and I don't want a dockicon but it should scan automatically after every reset. How can I realise it?
With the old version it works fine. With 2.0 I can only scan automatically with a dockicon or without a dockicon but with showing the AmiUpdate window. Or I'm to stupid?

No, you're not stupid. If you set the program to start iconified, as it says in the documentation, it will always show the docky.

Making it start as a menu was not something I thought anyone would ever want. I can look at this for the next version.

Simon

Nice one! Thanks for this update!

Well, true to form, there have been a few teething problems. So V2.1 is now available, and I have tested the AutoInstall and it works :)

Anyway, minor fixes to the images to allow custom themes, and to allow the iconification method of choice when starting up.

Thank you very much for your fast change and the iconification method. I get two times a crash with the autoinstall function during the installation of amiupdate 2.1. So I installed it manually, and it seems to work now.
But, it is right that au.log says only "Program started" and "Waiting for user input..."? I didn't see that amiupdate connect to the server automatically. I marked "Perform Self-Update check when started manually" and "Start iconified" as AppMenu. When I scan manually the au.log says connect and so on.
Doesn't scan amiupdate automatically after booting/a reset?

Thanks you Rigo !

I'm working on the italian translation, the locale files are the same for the 2.1 ?

The self-update stuff is not logged as it's an internal function.

The program will not perform a scan of the servers immediately when it is iconified unless the last schedule scan time was missed.

And to be honest, there really aren't enough updates in Amigaland to warrant scanning everytime the program starts up. :)

Simon

The prefs catalog did change very slightly, but the AmiUpdate files are the same.

Simon

Ok, thats an argument
But what happens when I missed the configured time e.g. 18 o'clock and start my sam at 18.01 o'clock? Have I wait til the next day then? I don't have a fixed time when I start/use my sam. Every day at an other time. A background scan every hour were great/perfect

@Rigo
Btw, there is only 2 amiupdate severs so far ? amiupdate.net and amiupdate.net/sdkserver ?

@gurus2000

No, as I said earlier, and is explained in the documentation, if the last scheduled scan was missed, AmiUpdate will scan immediately after starting. Otherwise it will wait until the scheduled time arrives. You can manually scan from the docky menu, or by uniconifying the program and scanning from there.

Simon

@kas1e

Yes, as far as you are aware, there are just the two :)

Simon

@rigo

Quote:

It doesn't quite work

As AmiUpdate is running, it fails to copy some files ("dockstrip" failed here). AmiUpdate probably needs to recognise when it is updating itself and make a point of quitting before the update starts.

Well, I tested here on my Sam, and it updated itself just fine.

I guess you'll just have to stick to installing it manually.

Simon

@Rigo

The AmiDock docky is cool. I want to have AmiUpdate always running, so have added to WBStartup, but I don't want to see the docky always so have set to iconify to menu. Will docky still appear when updates are available?

Update Prefs is neat by the way .

If the program is not iconified as a docky, then the status will not be shown in the dock.

Simon

@Gurus2000
Quote:

Same here, but manual update worked.

Awesome update

Thanks a lot, rigo

What i loke most is the little green icon showing an update is available...love it

here it fails to connect to the servers

Still does not run on OS4.0 Classic. Snoopy says it wants to open graphics.library V53 and that clearly fails.

good to hear. will try it out after vacation

This is strange : it works on my SAM, but on the A1 it fails to connect to the servers (I get a Ringhio warning saying "Connection to www.amiupdate.net failed"). Why ?

Sounds like the connect() call is timing out. I have no idea why this would be the case on your A1 when it works fine on your Sam board.

Simon

no, it is not timing out : AU starts, looks for a new version, then sits there. I click on "scan" and IMMEDIATELY I ged the ringhio messages that it can't connect...

Well, without more information, I'm as lost as you are. You can send me the log via PM, perhaps there is something in there that might tell us what is happening.

Simon