@MartinW

Yep, I've seen the bug, reported it.Looked through the code, and found the problem.



The code to save the details was commented out!!!!


I've no idea when or why this happened, but at least it will be fixed in the next release....


Simon

@MickJT

I'd say "Thanks for the report", but you didn't. Anyway, seems a later version of PHP changed certain aspects which lead to this. Hopefully it should work as expected now.

Simon

Well, I'm not sure about "recent", it was 2018 :)

Anyway, I've updated the autodoc, and you can grab it here:
http://codebench.co.uk/sysiclass_doc.lha

Simon

If it's local, then there may be a possibility that your preferences may be screwed up.Have a look in ENVARC:sys/update.prefs, maybe something has corrupted the XML file...

Simon

@Amiguy

You don't say which server you are connecting to when you get this error. I have tried all the ones I can think of, and no errors here.

Sorry...

Simon

Many many years ago, when I was running my Amiga 4000, I did what I could to update it, both in software AND hardware.

I added an accelerator, memory, hard disk controllers, video cards, I/O cards etc.

Many "people" said it wasn't an "Amiga" anymore.

I tended to disagree with them, stating that if it can run AmigaOS, then is it not an Amiga?

In those days, it was 3.1, but I still feel that logic stands.

I now run an "NG" system (quite a few actually), but they all run AmigaOS. Not a clone, but the result of upgrade work, over years, that many people have undertaken. Just like 3.5 and 3.9, but those were not shunned as "not AmigaOS", simply regarded as upgrades.

So my machines run the latest AmigaOS, on hardware that was designed to run it, and it runs well (most of the time). You may run "AmigaOS" on emulation, or like me, some hybrid hardware designed around AmigaOS.

Whichever way you cut it, if it runs AmigaOS, it's an Amiga IMO.

I don't class MorphOS or AROS as "AmigaOS" purely because they are not. Better they may be, but AmigaOS they are not. I liked my "Amigas" back in the day, and I still like them now. I never found a reason to switch to any other derivative because I was content with what it was, when it was.

The same holds true now. I regard an Amiga as a machine that can run AmigaOS. As this site is "Amiga" based, surely from my logic, that includes topics about any platform running "AmigaOS", not some clone, for the good or the bad.

I have nothing against either MorphOS or AROS, I have no interest in them simply because they are not AmigaOS, which was the point of this website, no?

If the users here say it IS of interest to them, then the admins have to go with that decision in my view.

Just my 2p....

Simon

@smarkusg

Most of the localisations are now hosted on os4depot. I suggest to look there for language files you require.

My aging memory tells me there /was/ a Polish translation, although how recent it is, I've no idea.

Simon

@Raziel

AmiUpdate database updated for you.

Simon

Right, after a short support session with another user that was not getting the update, we found out that he was using "amiupdate.net" as the public server on an older version.

So the advice still sticks:

If you are trying to update to 2.53, PLEASE use "codebench.co.uk/amiupdate_website" as the public server, and the update will come through no problems. After that, you can go back to "amiupdate.net" and everything should be fine once you are running 2.53+

Simon

@Petrol

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

@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