@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

@elfpipe

Quote:Don't you have Update 2 installed? If you did, the p5020sata.device would have been replaced by/changed to p50x0sata.device. (Not that I think it would help regarding smartctl, but there could be other fixes you are missing if you haven't installed the latest OS updates.)

Best regards,

Niels

BTW, if anyone reading this far is scratching their head over where/how to download the latest certificate bundle for Odyssey:

Go to https://curl.se/ca/
Download the cacert.pem file
Rename it to curl-ca-bundle.crt
Copy it to Odyssey's main drawer (replacing the old one of the same name)

Right now the latest one up there is from 20230110.

Best regards,

Niels

@LiveForIt (and others)

Yeah, I'm not really up to speed in development on Amiga, just thought I'd give it a quick go since I did have the SDK/compiler installed.

So please go ahead, the rest of you, if you like, and see if you can make it work .

Best regards,

Niels

@flash


So, not quite there, but pretty impressive.

Best regards,

Niels

@328gts

Quote:You probably should follow that good advice yourself, i.e. refer to SYS: instead of your specific boot volume name in your User-Startup (since you went in and fixed it anyway).

But I'm wondering about another thing: Was it really an installer that created that line in User-Startup? I'm guessing you are referring to the Enhancer installer, but I'm pretty sure it doesn't put anything into User-Startup about Power Prefs. Maybe you have put that line in yourself, taken from a thread on one of the forums (maybe a year or two ago?) where it was discussed? And maybe someone in that thread made the mistake of writing System: because that was what his boot volume was called? And then you just copied the line?

Just a theory, of course.

Best regards,

Niels

@amiganuts

If you can boot to WB you can use the NVSetVar command from a Shell instead.

Best regards,

Niels

@rjd324

Quote:Okay, then that's obviously not the reason.

What is the nominal download speed of your connection? I.e. what speed should you see? (As I wrote above, mine is 20 Mb/s.)

Best regards,

Niels

@rjd324

Are you sure it isn't the remote host that is limiting the speed? Either because their connection isn't faster than that, or because they want to let more people share the bandwidth, so they put a limit on each download connection?

I haven't noticed this myself. I usually download with Odyssey, e.g. from OS4Depot, and it normally runs quite close to my VDSL's nominal DL speed of 20 Mb/s.

Best regards,

Niels

The sensible way of mounting a network share is to do it from Network-Startup after the AddNetInterface line. I do that (with the old SMBFS and SMBMounter) by first having a line with "Wait 5 secs", then "GetNetStatus CHECK INTERFACES,RESOLVER,DEFAULTROUTE". This is not necessarily 100%, but works for me almost always. If WARN, I quit with a warning requester. Otherwise I move on to whatever I want to do with the network (e.g. fetching time via NTP). For the SMB share, I have this section:

CD
WBRun SMBMounter
CD SYS:

(I could also have used PCD, but since I know my current dir was SYS: at the start, I simplified it.)

SMBMounter is of course configured to automount whichever share I want up at startup.

Edit: BTW, can SMBMounter be used with the new SMB2?

Best regards,

Niels