Installing PFS3AIO on Amiga OS3.2

[jaesonk]

I used PFS3 in the past on other systems.  I only have FFS partitions under OS3.2 on the current Amiga.  I downloaded PFS3AIO from Aminet but it doesn't include an installer or documentation for install/setup.

Do I just copy the files to L: then add the filesystem in HDToolBox?  What ID should be used?  Any other particulars to be aware of?

Can PSF3AIO be used for boot partitions?

Thanks.

[jaesonk]

Thank you for the link.  I will take a look at this.

[jaesonk]

I have a GVP T-REX-II accelerator with SCSI controller.  The system I'm using this card with gvpscsi2.device in an A4000 with OS 3.2.2.1 ROMs.

HDToolBox recognizes the larger drive (18GB Seagate Cheetah). I can set up partitions across the full drive (just using FFS). But it won't format above the 4GB barrier. I get a "seek failure". Partitions below the 4GB barrier will format.

Problems with the T-REX-II and 4GB are mentioned on this page:
https://www.gregdonner.org/gvp4060/solutions.html

I'm not able to burn a replacement ROM for my T-REX-II.

Some suggested that PFS3AIO might be a work-around solution.  I've use it before on other systems.  I set it up with the Cheetah drive.  Partitions below the 4GB barrier are still FFS.  Two partitions above the 4GB barrier are switch PFS3AIO.  After saving and rebooting, the PFS3 partitions do no appear on Workbench at all.  I do have them set to automount in HDToolBox.  I tried with and without SCSI Direct selected.  Is there something else that I need to check?  Do these partitions need to be manually mounted?  If so, how do I create proper mountlists?  Or will PFS3 not solve my problem with the T-REX-II and large drives?

Thanks in advance.

Jaeson

[jaesonk]

Is there a way to prioritize which drive controller gets accessed first?  My boot drive is on the IDE bus, a secondary drive is on the GVP T-REX-II SCSI bus.  T-REX-II will apparently ignore new file systems added to the RDB of drives on it's SCSI bus (unless you can update the ROM).  But if the AmigaOS reads the boot drive IDE bus first, then file systems (like PFS3AIO) added to it can be accessible to the GVP SCSI.  I think my A4000 is looking the the GVP SCSI first, so any partitions defined with PFS3AIO are not being recognized.

I can get FFS partitions to work above the 4GB barrier on the GVP SCSI as long as direct SCSI is used.  For some reason I had trouble this first times I was trying this (with direct scsi), but I started over with defaults and this time it worked (with direct SCSI).

Jaeson

[jaesonk]

UPDATE!

The GVP T-REX-II SCSI ignores any custom file systems added to the RDB of the SCSI drive.  It also has issues with the 4GB barrier. 

Replacing the ROM solves problems, but I can't do that myself, I don't have access to any burning gear.  Two work-arounds are available though:

1) Put PFS3AIO (or other custom file system) on my CF boot drive, on the A4000 IDE bus, and set up at least one partition to use PFS3AIO. 

2) Make sure to use the Direct-SCSI option in the Advanced settings of HDToolBox (I'm using AmigaOS 3.2.2.1).  With this setting, the GVP T-REX-II SCSI can use FFS partitions above the 4GB barrier.  With step 1, this will make PFS3AIO usable on the GVP SCSI drive. 

For my A4000 set-up, this solved my problem.  I was able to create partitions above the 4GB barrier and use PFS3AIO (or FFS) on my T-REX-II SCSI drive.  The T-REX-II SCSI also needs proper termination.

Thanks for your help and suggestions.

Jaeson