Thanks for highlighting Avalanche (there's a typo - cfd should be xfd). Although I wrote it primarily for OS3.2, it seems to have gained quite some OS4 fans!

1. Use this: http://aminet.net/package/comm/tcp/mrwolf
(I wrote it, it can either use timesync.library or its built-in client - I recommend the built-in as it plays nicely with the NTP pool, whereas I can't guarantee timesync.library does - neither do I have any clue what TimeGuard does, IIRC it didn't work properly when I tried it many years ago)

2. Ensure Timezone Prefs is set to the correct region for DST switching (ignore the Enhancer crap - this is the timezone database which matters)

3. That should be it - it will sync in the background. Would recommended setting SERVER to a local NTP pool though.

@FirstNinja

How about a Discord bot which posts to the IRC and vice-versa?

That should be relatively simple to do, but would need an #irc channel set up on Discord (as you obviously can't mirror all channels to one)

edit - first link on Google: https://github.com/reactiflux/discord-irc

@rjd324Quote:

This is purely down to people not knowing how to write Installer scripts.

There's a copylib function which does version checking. This should *always* be used for 3rd party libraries, and can be used for executables or anything else containing a version number too.

Novice mode will *never* overwrite older versions when using this function.

Try SOCK_RAW

It's possible the 6.7 in the archive (which is the one I created the patches off of), and the 6.7 created from patching up older versions are different. I didn't check. I want to change the OS4 patch so it just copies the new binary over (there's not much advantage to using gpatch on ELF binaries), but that involves changing the Installer script significantly so I haven't bothered.

@xenic

It should update. Try copying the executables from the full archive back over and then running the update again.

@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.