@Antique

You can look on ntppool.org (it's probably no.pool.ntp.org)

@Thematic

Quote:

Yes, lowlevel.library is a CD³² library. AmigaInput has a compatibility layer for old software - whether it works or not I don't know! Certainly AmigaInput has always been flaky.

@Cageman

How about;


Adapted from the script you posted, but without a 3rd party command!

You can also get rid of the path in that LFORMAT but I can't remember the formatting command off-hand. It also needs double-quotes around the paths, I think that's *" but didn't add it as I'm not sure.

Maybe this should be a news article, but I just saw this about a new game engine:
http://www.indieretronews.com/2022/04 ... mes-good-because.html?m=1

@kas1e

Yeah, I built some SAS/C code with vbcc and it uncovered bugs that had been hidden. Some code should have never worked, just luck that it did. There's almost certainly a bug in there, which if you find will fix it for vbcc.

@kas1e

GCC 6 has problems, I tried compiling NetSurf with it some time back and the resulting executable didn't work. If you can get it building with vbcc that will be better, alternatively an older GCC version is more likely to be stable. Which compiler was it built with originally?

It may be worth also switching to the 3.2 NDK, in case there's some weird bug in the headers.

@Rigo

This is working now, thanks. Whilst you're here, can you look at the password change mechanism? If I try to change my password it just goes to a black screen and doesn't update.

I don't think there is a certificate, so your warning appears to be correct.

@Cyborg

... Which redirects to amiupdate.codebench.co.uk, which doesn't resolve.

@daveyw

There will be something running. Try booting with no WBStartUp - hold down shift (I think; may be ctrl) on boot.

Also be careful of ssh-handler, you'll need to dismount any shares mounted with that.

@daveyw

Correct!

And I wrote Mr.Wolf! It's an improved version of my earlier yFacts with a new name... and hopefully OS3 compatibility when I get round to it.

No, mine came from Maplins!
PyWWS definitely works with the WH1080, which is still available (unless they've updated it and kept the name). Anything which looks similar is *probably* going to work too.

Find something you like and ask in the PyWWS group, maybe? If it works with that it should work with the tools I uploaded. It may even be possible to run PyWWS (the old ones) on our port of Python - I've never tried.

@AmigaOldskooler

Yes, they both worked at the point I uploaded them

However, my weatherstation was generally connected to a Raspberry Pi running PyWWS, and hasn't actually been connected up since I moved.

I hit the "3" on the front page and it took me to the most recent unread post. I was expecting it to take me direct to page 3 (although actually most recent unread is more useful)

@trgswe

There's code in the SDK for building keymaps. I think the format on OS4 differs from OS3, but it's a long time since I've needed to create an OS4 keymap.

On OS3 I don't think there's any source code available, so you have to use a keymap editor!

@rjd324

Back-tick should be the top-left key under Esc - that's what's printed on the key. When I tested, it's Alt and that key for the back-tick.

I don't know what Commodore were thinking - I believe the British keyboard on all Amiga models have the back-tick on the top-left, but the keymap itself has the apostrophe there!

On the A600 and newer there are two blank keys they could have used to separate them out, and then corrected the keycaps.

@NinjaCyborg

If AmigaOS used XML across the board and we had an xmlparse.library which was simple to use and included with the OS - properly encoding and decoding strings and setting types etc - then I'd be less against it.

But instead we have a mishmash of open source libraries, none of which are particularly easy to use, and developers who aren't familiar with them or XML (I include myself in that*) but want to use XML as apparently it was cool around the early 2000s, even though it isn't really suitable for the intended task.

* I've never been much keen on XML, and every time I've had to try to deal with it it has been difficult to work with.

@Raziel

As an official component a Prefs editor is pretty essential. But it should probably have written the config in IFF PREF format like most of the other Prefs editors (excluding some of the newer ones which also use XML as NinjaCyborg noted).

The bonus is IFF parsing through iffparse.library is quite similar to how XML parsers work, but simpler, and probably both less memory intensive (the parser alone is smaller) and quicker.

@NinjaCyborg

XML is horrendous for parsing, it doesn't surprise me it causes problems. Why people insist on using it for config files instead of something more appropriate is beyond me.

Hint: if you don't have a complex application which necessitates nesting configuration options (and even if you do there are other solutions), you shouldn't be wasting your time using XML. There are plenty of other options, such as IFF, ToolTypes, INI, JSON, YAML. The first two in particular are preferred and easy to parse for Amiga applications.