Issues with installing software on PFS

[paul1981]

I have got my hands on a boxed copy of Easy AMOS but I am having issues installing it onto my PFS formatted CF HDD. On my FFS CF HDD, which I use for games, it installs fine but the PFS formatted card Easy AMOS keeps saying the destination drive is full. Even though I have 800mb free.
 
This is not the only bit of software I have issues with. X-COM also does this along with Frontier Elite II (I used these for testing).
 
It's annoying because I use one card for productivity, and also for teaching myself about programming, and another for simply playing whdload and installed games.
 
I have the max transfer set correctly and have had no other issues with the drive other than trying to install things.

This is a common problem with old installers. The old installers don't understand partitions which exceed approx 3.9GB, and so it reports back bogus free space. Quite possibly the partition would need to be within the first 4GB of your drive as well (but don't quote me on that one). There's nothing that you can really do except install it to a partition that is approx 3.9GB or less so that the installer doesn't get confused. Or alternatively you could install such software manually.

[paul1981]

Or install to RAM and copy it to the destination manually, remembering to correct the paths in any changes it made to the startup files.

If installing to RAM:, make sure that you're Ram Disk isn't recognised as 100% full even when not. If it is, add this to your startup-sequence:

http://aminet.net/package/util/sys/PatchRAM

...so that it lists correct free space on the Ram Disk.

Alternatively, you could mount a virtual HDF device large enough for your software install and install to there... then move things back across to your main partition afterwards. I prefer to install things manually though.
Not sure about Amos, but if you make a copy of your Amos disk, maybe you could modify that copy to mount a CF drive (with compactflash.device and its mountlist, and with fat95) and then you could direct the install to CF0: assuming it does indeed request for you to type in a device or Volume Name to install to.