Help with A1200 with Subway 2021 and Anaiis

[Gilloo]

Originally Posted by Jope

What does your mount file USBKEY0 look like?Why did you choose 50465301 as your DosType? With PFS3 you really ought to use 50465303 (PFS\03)

In pfs3aio/blocks.h
#define ID_PFS_DISK (0x50465301L) /* 'PFS\1' */


so I don't see why we should put another value in DosType

[Jope]

It is just good form. While it's true that PFS3 will work with almost any dostype (PDS\03 is special for PFS3), if you introduce this mount file into a correctly set up system (or emulator) that is already running PFS3, you will now have multiple versions of PFS3 in memory if there are existing PFS\03 partitions in that setup.

You will also confuse other people who are helping when the dostype is strange, they will be off on a short wild goose chase wondering why it was done like this (often strange things are done for a reason and the reason needs to be investigated).

But it is a free world and you are free to not follow any conventions or best practices. When breaking convention, you do need to be aware of having done it and also for the reasons why (for the fun of it is a valid reason) and potentially be ready to communicate what was done in case you are collaborating with someone on a problem.

The header file you are referring to does not actually have anything to do with to the in memory dostypes used when matching an in-memory filesystem handler to a device. Instead it refers to the four bytes found on the first block of the partition you are mounting. PFS3aio has support for several different older versions and alternate flavours of PFS3 (again regardless of the dostype you used) and will use the correct code path depending on what it finds on disk.

[Gilloo]

The mountlist (HigCyl can differ but it is always odd)

USBKEY0:
Device = usbscsi.device
FileSystem = L:PFS3
Unit = 0
SectorSize = 512
LowCyl = 0
HighCyl = 118271
Surfaces = 8
SectorPerTrack = 128
Mask = 0xFFFFFFFF
MaxTransfer= 0x001FE00
StackSize = 8000
Priority = 0
Flags = 0
Reserved = 0
Buffers = 5
BufMemType = 1
BootPri = 0
GlobVec = -1
DosType = 0x50465301
Mount = 1
#


The Error:
Write 2 Error 170 on block 0 + 2
00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00

If I look at how it's built here
https://github.com/tonioni/pfs3aio

mode 2 (direct scsi)
errnum 170
blocknr 0
blocks 2
scsierr (sense error) all void

It seems to be the 2 firsts blocks, but I also got this error on block 64, a bitmap block.
All blocks can be accessed or modified with an hex monitor, without any error, but the format command hangs.
What is the problem ?
Bad MaxTransfer value ?
Wrong disk Geometry ?

To get out of these strange errors, I use HDInstTools on WinUAE, then the key is working under Subway/ANAIIS.

[Jope]

The mask and maxtransfer should not matter here. The geometry looks reasonable for a 64GB pen drive, if I calculated correctly.

You could try extracting a mount file with giggledisk, if you managed to make it work by partitioning with HDInstTools.

https://aminet.net/package/disk/misc/giggledisk

Something like

giggledisk device usbdisk.device unit 0 to ram:

will create mount files for the partitions in ram: