@nbache

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

Right, fixed the last of the issues (I hope).

2.53 is available now.

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

@khayoz

The logic behind starting iconified, is that the application can then run in the background, and perform scans at scheduled times. These can be set up from the preferences editor.

Personally, I don't use it either, but it was requested many years ago.

@all

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.

Simon

OK, so after a bit of a marathon, I found the problem.

It appears that later updates to application.library now always use the V2 interface in the docky routines.

As I was trying to keep 4.0 compatibility, I was using the "old" tag values, which is what threw up the error. So it seems I am no longer able to keep compatibility with 4.0, but as I very much doubt anyone is actually using that now, I can't see it being a real problem.

Testing it here looks fine on both machines, so 2.52 should fix this problem.

As for updates not showing up, that's very weird. There shouldn't be any reason to stop anyone seeing it unless you have the latest version????

As for connection problems to www.amiupdate.net, I'm lost with this. One day it seems to work, next it doesn't. I'm no DNS wizard, but AFAICS everything looks like it should work, so....

In order to stop this in the future, I have implemented a simple "nslookup" which should hopefully stop this ever again. 2.52 will be an absolute minimum for this to work, but should be future proof.

Fingers crossed.

I just want to test things a bit more before making it public. I will also update the full archive on the "downloads" page to include this new version,so everyone should be able to get it one way or the other.

Thanks for you patience

Simon

That is very strange, I have checked and I'm definitely passing the right tags.No-one else has reported the problem, and my "public" sam440 is fine.

So I've no idea why it's only you...

Simon

OK, after quite a snowball of issues and such, 2.51 is available.

Hopefully it should work OK. I've tested it locally here on two machines and it seems good. I'm keeping my fingers crossed everything works as it should.

Simon

@amigakit

I must admit, a 4-colour screen grab really isn't selling that product :)

Simon

And the more complex you get inside a seriously critical function like OpenWindowTagList(), the worse the experience for the user.

Simon

Personally, I think the morale of the story is to just avoid anything Enhancer related.

Apart from the obvious hijacking of system components, which just confuses users, it doesn't seem to be the most stable software out there.

YMMV, of course...

Simon

So people want to start a fund to host Amiupdate somewhere else?

No-one ever asked me if I needed money to host it, I did it off my own back with my own money, let alone the amount of time spent developing it. Luckily I had some help years ago, but now it's down to me.

When it goes down, through no fault of mine, all of a sudden the pitch-forks are out and I'm enemy number one...

Your getting something for nothing here, be thankful for what you get, if anything.

I'm not under contract to supply any service here, and if that stops, so be it. It's back now, at the original location, as it always was.

It's out of my control, and I'm slowly working my way back to restoring all the original services. Unfortunately I have to go to work to pay my bills, including hosting this service. If this doesn't fit in with your schedule, then I apologise, there's only so much I can do.

Simon

@vintagewatches

I've never been a fan of anime, but in fairness, I'd say if this was in a much higher resolution, it would be commercial quality.

The artwork is sublime, and a credit to the originating artist.

It's a "yes" from me!

Simon

Joerg is onto something here, unfortunately he's in the wrong place. Instead, check the "sitelist" file in the AmiUpdate directory (usually SYS:System/AmiUpdate) and see if there are any login details there you might be able to use...

Simon

AmiUpdate uses the xadmaster.library to unpack archives, so as long as you choose a supported archive format, there shouldn't be a problem.

Simon

This is the usual way to do it. Done it many times myself over the years.

https://www.ebay.co.uk/itm/29304325857 ... D%3D%7Ctkp%3ABFBM1LCribhg

Simon

@Chris

I'll try and get some time over the weekend to look into that.

Simon

@khayoz

Unfortunately, not yet. Work is still ongoing on finalising V1.0

Simon

Hopefully this should be fixed now.

Sorry for the inconvenience.

Simon

On the bright side though, I'm liking the slight increase in font size.

I'm not getting any younger, you know... :)

Simon

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

I would suggest to check/change the 2032 battery. Sounds like it might be on the way out...

Simon