@rwo

Quote:Correct.

So the font really should be present and openable on a standard OS4 installation.

Maybe his font is damaged in some way? Perhaps try copying it again from the OS4 CD and reinstalling it with System/TypeManager?

Best regards,

Niels

@LiveForIt

Quote:Odyssey has such a script, but that's to install the standard web fonts. The Bitstream fonts come with OS4.

Best regards,

Niels

@sadirux

Quote:No need for the hotfix if you install Update2 freshly downloaded. It already contains the fixes. The hotfix was only for those who installed the original Update2 which was found to have flaws.

The flawed version of the full Update2 archive was of course replaced by the fixed one as soon as the fixes had been tested.

Best regards,

Niels

@rjd324

The OS4 installation comes with AISS, but it's probably not the latest one, so maybe CompareDirs need some images which have been added to AISS later on.

Best regards,

Niels

I make nightly backups ...

(and I don't install Enhancer stuff - except the graphics drivers, and what I absolutely need for testing my translations, and never anything that replaces OS4 originals).

:shrug:

@rjd324

Quote:You don't need to do that. Just set the preferences to not enable the rollback feature, then CopyStore acts as a regular Copy.

Best regards,

Niels

@rjd324

Rigo should probably answer this himself for the sake of precision, but AFAIK, AutoInstall scripts are supposed to be executed only from within AmiUpdate, so calling CopyStore will find it in the current dir of AmiUpdate.

It's a design decision.

I wouldn't necessarily have made the same one, but it does (normally) get the job done.

Best regards,

Niels

And the capability to display PNG icons (rather than the standard icon format) was never part of the OS, it always required a third party add-on.

In spite of this, some authors have assumed that everybody had that add-on installed and provided their software with only PNG icons, not even a choice in the installation.

(No need to ask me whether I think that was a good idea ...).

Best regards,

Niels

@rjd324

If AmiUpdate (some version) has been installed correctly on your system, it will have CopyStore (some version) in the same directory.

If it's not there, there is something wrong with the installation, and the safest way to fix it is to start with a known good version (the aforementioned 2.47), install and configure that, and let it update itself (the full package) to the current version(s).

Also, there have been some versions (earlier than 2.47) of AmiUpdate which had issues with updating itself, but they are known to have been solved in 2.47.


Best regards,

Niels

@rjd324

CopyStore is part of the archive containing the full version of AmiUpdate.

It is in the top directory of the archive where also AmiUpdate itself is found.

On this page:

http://codebench.co.uk/amiupdate_website/index.php?page=downloads

- use the link to get the stable (2.47) vesion of AmiUpdate, install and configure it, and then let it perform updates of itself to the latest version. Depending on whether CopyStore was modified in a given update, it will also be updated when AmiUpdate is.

Best regards,

Niels

@VooDoo

No, usually it's "two more weeks".

The question is, of course: Is "soon" longer or shorter than "two more weeks"?

(Tune in in two weeks for the answer to this and possibly other questions ...)

Best regards,

Niels

Yes, I believe I mentioned this in another thread (not sure if that was to you, though).

But basically, never set the debug level higher than 4, unless a kernel developer or similar asks you to.

You will drown in useless (for us mortals) debug output.

Best regards,

Niels

@Magic

Don't forget it has to be a so-called "null-modem" cable, not a regular serial cable.

See more about the serial debugging features here:

https://wiki.amigaos.net/wiki/Advanced_Serial_Debugging_Guide

Best regards,

Niels

@rjd324

Quote:I believe so.

AFAIK, the QUIET option also here does what that option does in most commands: make the command avoid outputting anything to the console (std output). This is useful for a command in Startup-Sequence (or User-Startup) because if text were printed, the shell window would open to show it, which you normally don't want during startup.

In some cases the same effect is created by appending ">NIL:" and possibly "*>NIL:" (for the error stream) after a command.

As for the Power command itself, I assume calling it without any (other) arguments simply makes it activate the same power setting which has previously been saved in the Power prefs GUI.

Best regards,

Niels

@jabirulo

Not sure why either, but I remember this being the case for ages - maybe forever.

Possibly someone once thought it would prevent too many people complaining that their programs wouldn't run. Better to have one unnecessary bit set on many files than a necessary one missing on some?

Best regards,

Niels

Not sure whether those are what you're looking for, but try echoing $RC and/or $Result2 after executing the program.

Best regards,

Niels

@jPV

DirOpus 4 does have configurable columns, but version is not among the data you can select for a column.

One way around it could of course be a script or program which puts the version into the file comment for all libraries in the LIBS: drawer (if that's what is needed), and then the comment could be selected as one of the columns to display.

It has some drawbacks, of course. One is that you can't use the comment for anything else, should you wish to, and another is that you have to do it again if you update any libraries.

P.S. Personally, I'd go with someting like:

list LIBS: files pat #?.library lformat "version %s%s file full" | execute IN:

- and then just copy/paste the output from the Shell; for some reason I can't get it to pipe it into a file.

Best regards,

Niels

@Raziel

Quote:Well, as long as it's an option, I'd support your wish.

I can't see myself using it much in the above scenario, though. If I'm editing a sound, I'd want to save it at short intervals to make sure I can revert if I do something stupid, and I'm pretty sure I'd feel that such a requester for every save would interrupt my workflow and concentration.

But there could of course be other scenarios where it might be useful.

Best regards,

Niels

@Raziel

Quote:I'm pretty sure you need to try it yourself, and you'll be convinced you are wrong . (And I just tested it with LibreOffice in Windows, just to make completely sure.)

As Trixie also writes, the standard behaviour when using Save (just Save, not Save As) with a document which has already been saved with a name, whether you are continuing working on it, or you have loaded it after previously saving it, is to silently save the changed version of the document into the existing file.

Now, if you create a new document (or project as we call it in the Amiga paradigm) and then hit Save and specify the existing file, you should get an overwrite prompt before saving.

Best regards,

Niels

@walkero

Quote:Same here - see you there!

Best regards,

Niels

@walkero

Good solution! It works fine in my Odyssey. Of course 800 px is not much when you have a screen with 2560 - but I can easily live with that as the price for avoiding those extremely wide pages.

I also checked that copying a long (wrapped) line and pasting it into NotePad results in one long line again, so no damage to the formatting.

Nice work - thank you!

Best regards,

Niels