Welcome, Guest. Please login or register.

Author Topic: Installing PFS3AIO on Amiga OS3.2  (Read 27143 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Boing-ball

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #14 from previous page: August 09, 2025, 08:41:01 PM »
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

Have had similar issues with other SCSI adapters on the Amiga. Unfortunately you are still tied to the firmware of the Adapter.
 

Offline sean_sk

  • Newbie
  • *
  • Join Date: Aug 2017
  • Posts: 27
    • Show only replies by sean_sk
Re: Installing PFS3AIO on Amiga OS3.2
« Reply #15 on: August 10, 2025, 07:48:15 AM »
Been using the Beta release over a year without incident 🤞🏻 Sorts out a lot of issues I had with 19.2 (3.1) current release.

What issues were you having with 19.2? Asking as I'm contemplating updating to the beta.
 

Offline Boing-ball

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #16 on: August 10, 2025, 01:22:22 PM »
What issues were you having with 19.2? Asking as I'm contemplating updating to the beta.

Strange behaviour with booting up using removable media such as Zip and Jaz. Had to use FFS instead.
On HDD side with SD and CF couldn’t utilise 4096K block size. Issues with max transfer and if using higher Buffer sizes would cause media not to boot up, unless I dropped this down to a max transfer of 0x0FFE.

Remember that v 20.0 (3.2) needs the latter version of PFS Doctor. Older versions will corrupt the drive if repairing.
 
 
 

Offline jaesonkTopic starter

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #17 on: August 11, 2025, 05:11:08 AM »
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
 

Offline Boing-ball

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #18 on: August 11, 2025, 10:51:55 AM »
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

The Amiga will always favour the IDE over SCSI. (caveat, Not sure how the A4000T works).
The best way would set the IDE device as Bootable and make sure there is no Bootable on the SCSI drives.
Remember that the boot priority can also play a part. I.e “0” lowest, “4” highest. “5” is reserved for the Floppy drive, therefore why it will always boot a floppy disk first regardless of HDD installed.
 

Offline Thomas

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #19 on: August 11, 2025, 01:03:15 PM »
@Boing-ball  I am not happy with what you write. That AmigaOS prefers IDE is only by coincidence. The OS will initialize drivers in the order they appear in the resident modules list. In order to build the resident modules list it will first scan the Kickstart ROM for resident tags and then add expansions from the Zorro bus. Hence mainboard periphals will be initialized before third-party expansions.

Each driver on initialization will scan its hardware for partitioned harddrives and read the partition tables. It will add all partitions into a list to be mounted by dos.library and all bootable partitions into a list of boot nodes, ordered by boot priority. It will also read required file systems from the RDB and add them to filesystem.resource if not already present or present with a lower version.

Therefore if a later driver will encounter a third-party file system on one of its partitions it might benefit from an earlier driver which has already loaded this file system.

Only when all drivers have been initialized, dos.library is started, will mount all partitions from the mount list and start booting from the first node in the boot list. This means that the boot priority does not have any influence on whether a partition is mounted or not, it only determines which partition is used for booting.

Also 5 is in no way reserved for the floppy drive, it is only hardcoded. But nothing hinders you to set your partition to 5, too. It just won't boot because the floppy drive is checked first.

Valid boot priorities range from -127 to 127 while -128 means not bootable. You can indeed set your partition to a higher value than 5 to prohibit floppy booting (you can still select the floppy drive in the early startup menu).

I would always recommend to put the boot drive on the fastest hardware which most likely is SCSI. And I also recommend to use the fastest file system for the boot drive. Actually there is no reason to use different file systems. If you chose PFS as your preferred file system, you should use it for all partitions.

In the special case of the T-Rex using a third-party file system is a bit difficult because the T-Rex does not read file systems from its RDB. Therefore you need a harddrive with a PFS partition on another controller which is initialized before the T-Rex. Which is quite easy if you already have a drive on the internal IDE bus.

You only need to keep in mind that the PFS partitons on the T-Rex will stop working if you remove the IDE drive.



« Last Edit: August 11, 2025, 01:06:59 PM by Thomas »
 

Offline Boing-ball

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #20 on: August 11, 2025, 05:29:44 PM »
@Boing-ball  I am not happy with what you write. That AmigaOS prefers IDE is only by coincidence. The OS will initialize drivers in the order they appear in the resident modules list. In order to build the resident modules list it will first scan the Kickstart ROM for resident tags and then add expansions from the Zorro bus. Hence mainboard periphals will be initialized before third-party expansions.

Each driver on initialization will scan its hardware for partitioned harddrives and read the partition tables. It will add all partitions into a list to be mounted by dos.library and all bootable partitions into a list of boot nodes, ordered by boot priority. It will also read required file systems from the RDB and add them to filesystem.resource if not already present or present with a lower version.

Therefore if a later driver will encounter a third-party file system on one of its partitions it might benefit from an earlier driver which has already loaded this file system.

Only when all drivers have been initialized, dos.library is started, will mount all partitions from the mount list and start booting from the first node in the boot list. This means that the boot priority does not have any influence on whether a partition is mounted or not, it only determines which partition is used for booting.

Also 5 is in no way reserved for the floppy drive, it is only hardcoded. But nothing hinders you to set your partition to 5, too. It just won't boot because the floppy drive is checked first.

Valid boot priorities range from -127 to 127 while -128 means not bootable. You can indeed set your partition to a higher value than 5 to prohibit floppy booting (you can still select the floppy drive in the early startup menu).

I would always recommend to put the boot drive on the fastest hardware which most likely is SCSI. And I also recommend to use the fastest file system for the boot drive. Actually there is no reason to use different file systems. If you chose PFS as your preferred file system, you should use it for all partitions.

In the special case of the T-Rex using a third-party file system is a bit difficult because the T-Rex does not read file systems from its RDB. Therefore you need a harddrive with a PFS partition on another controller which is initialized before the T-Rex. Which is quite easy if you already have a drive on the internal IDE bus.

You only need to keep in mind that the PFS partitons on the T-Rex will stop working if you remove the IDE drive.

I stand corrected.

But from my initial experience using a A1200 and A4000D and having both an IDE and SCSI setups (WarpEngine and Cyberstorm). If I plug into a IDE device and a SCSI device, then always I find the IDE device will always startup first. Unless a Floppy Disk is inserted first.

This is true for when I use a Zip750 as an IDE device with Boot priority = “0” and a SCSI SD card again boot priority = “0”.
Or a IDE SD and a SCSI SD card in both drives. Again IDE SD boots first.
 

Offline Thomas

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #21 on: August 11, 2025, 06:18:29 PM »

What I said: mainboard first, expansions next.
 
The following users thanked this post: Boing-ball

Offline jaesonkTopic starter

Re: Installing PFS3AIO on Amiga OS3.2
« Reply #22 on: August 12, 2025, 07:10:28 AM »
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