Hyperion Entertainment Message Boards

LiveForIt wrote:There are lots of functions marked as obsolete for AmigaOS4.1, and I guess that’s also true for AmigaOS3.1.4.

AFAIK dos.library has not been touched in 3.1.4, so no, it's not true.

You better send this question to the uae4arm support because it surely does not have anything to do with Kick 3.1.4. If uae4arm is similar to WinUAE, then it tries to identify known ROM files by their CRC checksum. Of course the new ROM is not yet known. In WinUAE this manifests so that it does not ...

Where does IExec come from? If you run without startup code, the system provides IExec to you. Alternatively you can read ExecBase from address 4 like in the old days and read IExec from ExecBase. If you run with startup code, you don't need to care. The startup code provides an external symbol IEx...

You should read the docs. There is a lot of information in the FAQs.

There are new tooltypes for HDToolbox which let you override certain limits.

Set LIMIT_4GBYTE to OFF or FALSE to remove the white bar at 4GB.

Also enable the "Direct SCSI Transfer" checkbox in the advanced options.

nbache wrote:Maybe because MakeDir only has to be loaded once?

Maybe you should look at the code before you suggest something?

Old: C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
New: C:MakeDir RAM:T RAM:Clipboards RAM:ENV/Sys ALL

In both cases MakeDir is loaded only once.

It shortens the command line but how does it speed up the processing? It rather slows it down. The directories have to be created one by one anyway. With your command line it first has to recognise that ram:env does not yet exist. So it's at least one DOS call more than with all sub-directories spec...

All versions of FFS have the issue that they need a lot of RAM to build the bitmap. As a rule of thumb you need ca. 1 MB of memory per GB partition size.

What's new with 3.1.4 is that it actually tells you what the reason is instead of just sitting there with an unvalidated volume.

This is not a new issue, it has always been like this with all version of FFS.

IMHO it's more likely lack of RAM. FFS is a bit memory-hungry with large partitions. As a rule of thumb you need ca. 1 MB of RAM per GB of partition size to validate a FFS partition. So in your case it just fails to create the bitmap for the big partitions and they stay in "validating" sta...