@rjd324

I can't reproduce your truncation:



Quote:Perhaps because if you don't append, but just write, the first redirection (the STDOUT) locks the file so the second one (STDERR) can't write to it. And maybe they both try to verify that they can get their locks before either one starts to actually open (create) the file, because it seems to fail without even creating the file.

And that probably also means it wouldn't help using append only for one of them.

But I'm guessing.

Best regards,

Niels

@rjd324

Have you tried this?

dir xx >> RAM:p *>> RAM:p

Works for me.

Best regards,

Niels

@eliyahu

In the standard AmigaOS4.x installation of Ghostscript there is a script in SYS:Utilities/Ghostscript/Data/8.54/lib/ called ps2pdf.

I have no idea whether is can run under AmigaOS (it does look like it's part of something copied directly from the Linux GhostScript). It will at least require the sh shell, but if you have the SDK installed, it should be available.

Worth a try, at least as a starting point.

Best regards,

Niels

@geennaam

Quote:Well, also 4.1 Final Edition (4.1 FE) was a paid release. But the updates to that - Update 1, Update 2 (with HotFix) and a few later released single-module fixes - have all been free for registered users of 4.1 FE.

Best regards,

Niels

I must say I don't see how a simple announcement of a new MorphOS release is a problem here (although it would of course have been even better to have it in Free for all).

The only problem with it is when it is turned into a discussion about whether it should be here or not. (Oops, now I did it myself ...)

Best regards,

Niels

@Rolar

Quote:It can also be opened using the hotkey combination Ctrl Alt M, if that's any help.

Best regards,

Niels

Or, to be very simple and pragmatic:

This cannot work (as Colin explains above).
sPlayer = "APPDIR:Amiga:Utilities/FFmpeg/Generic/ffplay"

You can either do this (using the APPDIR feature):
sPlayer = "APPDIR:ffplay"

Or you can do this (using full static paths and not using APPDIR):
sPlayer = "Amiga:Utilities/FFmpeg/Generic/ffplay"


Best regards,

Niels

@Isense

Quote:It shouldn't do that, it should only turn off the monitor. Touching a key (I usually use a Ctrl key on its own) should get the display back.

If it really does turn off your whole machine, there's something wrong.

Best regards,

Niels

Download of newest certificates:

https://curl.se/ca/cacert.pem

Rename the file to curl-ca-bundle.crt and place it in Odyssey's main directory, replacing the former one (rename it first if you want to save it).

Odyssey is your best bet for most recent sites, but needs the latest certs. You also need to make sure you are using the latest version of Odyssey: 1.23 r5 (Jan 2 2022).

Even so, it is nowhere close to Firefox or other modern browsers on other platforms in terms of coping with the latest web tech..

Best regards,

Niels

@Deniil

Quote:Probably it works for everyone who hasn't changed the default volume name of RAM: (which is "RAM Disk" with a space).

Personally, as a beta tester, I have always found it useful to have the original name with the space, because it makes it very easy to find bugs in programs or scripts which fail to treat volume names and paths correctly.

But apart from that, I totally agree with you. Hardcoded default paths in applications are a nuisance, and if used, at least they should never contain explicit volume names (I believe e.g. Prefs/WBPattern also used to do that until someone finally addressed that bug).

Best regards,

Niels

Well, I believe I had it happening on X1000 as well. I would get corrupted files and disruption of the copying with error requesters while copying pictures from my camera with DOpus4, at least if there were many files involved.

But it started with some beta version of parts of USB and ended again in beta before any public release, IIRC, so this condition should have been seen only by beta testers.

Best regards,

Niels

@kas1e

The only UPS I have any experience with is the one I have:

https://www.amazon.co.uk/APC-Schneider ... 3735&s=electronics&sr=1-3

I've been very satisfied with it. But I don't use it for my Amigas (nor my PC), I only use it for my router, network laser printer, NAS disk and a small headless Linux server.

Best regards,

Niels

@tonyw

Same one as mine.

Best regards,

Niels

@Capehill

Quote:It's identical to the one I have in my C:.

Best regards,

Niels

@afxgroup

Quote:It's simply called top.

Best regards,

Niels

@Capehill

Quote:Yes, I get tasknames in the display.

Best regards,

Niels

It's still working for me on the latest beta kernel (not running the multi-core one though).

However, it doesn't seem to have any version string, and doing a C:Version on it made my system lock up. So don't do that .

The main functionality is apparently okay.

One piece of info for anyone using it: Use Ctrl-C to stop the auto-updating display and end the command.

Best regards,

Niels

It's probably a license issue. It doesn't seem like it would be a very complicated program to make.

Best regards,

Niels

@abalaban

Quote:I think you are referring to the CopyStore command. Yes, many AutoInstall scripts only use CopyStore for the main components and plain Copy for the rest, maybe to save space for the rollback? Personally, I don't use the rollback feature at all in AmiUpdate (rely on backups instead, so I'm in total control myself), so I don't have any opinion on whether that's a good idea or not.

Quote:This is not only a problem for newlib, but of every package which has an SDK component. To solve it completely, we would need to have a separate AmiUpdate database especially for all the SDK components and have each one depend on the relevant version of the package in question being installed. And then of course also maintain separate packages with only the SDK parts of those packages.

The alternative - which can be used already - is to create a new OS installation on a fresh boot partition when you decide to install an SDK, start with e.g. FE plus updates 1 and 2, then install the SDK, and follow up by letting AmiUpdate install any newer versions of packages including their SDK parts if found.

Best regards,

Niels

@rjd324

You can also use the Updates prefs program to tell AmiUpdate to keep downloaded archives, and to save them in a path on your disk (as opposed to in RAM:) - it's on the first tab page of the prefs in the lower half.

That way you can later check what was actually in the archive.

Best regards,

Niels