PFS3AIO v3.1 Final

[Radertified]

I've encountered this before. Sounds like your cylinders/etc. aren't set properly so there's no room to save the required data. You need to mess with those values.

Same problem has been posted before. Solution from thomas is to mess with the values

[DamienD]

Originally Posted by Radertified

I've encountered this before. Sounds like your cylinders/etc. aren't set properly so there's no room to save the required data. You need to mess with those values.

Same problem has been posted before. Solution from thomas is to mess with the values

Thanks Radertified

...but it's weird, I've never had to do that before.

Plus remember I'm using emulation so one of the first steps I do are as follows, which automatically detect .HDF geometry (highlighted below in blue text / bold):

... Boot with "Workbench v3.1 rev 40.42 (1994)(Commodore)(M10)(Disk 1 of 6)(Install)[!].adf".
... Double-click "Install" --> "HDTools" --> "HDToolBox".
... Click "Change Drive Type" --> "Delete Old" --> "Continue".
... Click "Define New..." --> "Read Configuration" --> "Continue" --> "Ok" --> "Ok".
... Click "Partition Drive", click on the empty partition and click "Delete Partition".
... Resize the first partition, change the "UDH0" --> "DH0", click "Ok" --> "Save Changes to Drive" --> "Exit".
... Restart.

[Radertified]

WinUAE is also where I encountered it, and recently too. Maybe a bug has been introduced in recent versions? I never used to see the problem before either. It's probably user error from both of us

I think the solution was to also ensure "Full drive/enable RDB mode" was used for the HDF. If you're already using that... *shrug*

[DamienD]

Originally Posted by Radertified

WinUAE is also where I encountered it, and recently too. Maybe a bug has been introduced in recent versions? I never used to see the problem before either. It's probably user error from both of us

I think the solution was to also ensure "Full drive/enable RDB mode" was used for the HDF. If you're already using that... *shrug*

Thanks for the suggestions, but I'm using the same version of WinUAE (v4.4.0) and the same version of PFS3AIO.

...and yes; I've set "Full drive/enable RDB mode" for the .HDF.

[Jope]

What size (in bytes) is the HDF you're encountering this problem with?

[supaduper]

I`m sure PFSaio locks the drive to read only if there is a problem found by PFS so might want to ask Toni

[DamienD]

Originally Posted by Jope

What size (in bytes) is the HDF you're encountering this problem with?

Only a small drive this time; 300MB.

[thomas]

Originally Posted by DamienD

...but it's weird, I've never had to do that before.

All this guessing does not help.

What are the concrete values for Heads, Blocks per Track and Blocks per Cylinder?

How many and which file systems are in the Add/Update list?

[DamienD]

Originally Posted by thomas

All this guessing does not help.

I've deleted now, but let me re-create

[DamienD]

Originally Posted by thomas

What are the concrete values for Heads, Blocks per Track and Blocks per Cylinder?

How many and which file systems are in the Add/Update list?

Just "FFS" and "PFS3AIO":

[thomas]

That's obvious: one cylinder is 32 sectors, the first partition starts at cylinder 2, which means you have 64 sectors a.k.a. 32 KB to save the partition table and the file systems.

PFS alone is 70 KB. Together with FFS which is 24 KB you try to save more than 94 KB in that 32 KB area. It just does not fit. Not enough space, the message is correct.

You can make cylinders bigger or start the first partition later. Mess with the values. There is no other way.

[DamienD]

Thanks thomas; that makes sense.

[Lisko]

Hi, has someone the experimental pfsdoctor? I can't find it anywhere and the original pfsdoctor should not be safe on >4G partitions, right? Thanks

[Toni Wilen]

pfsdoctor link in first post updated.

[Lisko]

Originally Posted by Toni Wilen

pfsdoctor link in first post updated.

Thank you

[spoUP]

Hello!

I run the latest pfs3-aio on a partition on a usb stick on an fpga replay.
Changes i make to files never seem to get written to disk.
I have talked to friends with similiar issues on their non replay setups as well.
The problem might be worse on the replay, but maybe something is off with the cache flush?

[DDNI]

@spoUP I am sure you do this, but are you definitely pressing return after entering values in each field?

[spoUP]

yes.

[AMIGASYSTEM]

Hi Toni, many years ago on my A4000 Reale "if I remember well" with PFS3 I could delete the files contained in the .deldir, on WinUAE these files are protected and cannot be deleted, am I remembering wrong?

[Torti-the-Smurf]

Thank you Toni and everybody involved in making the greatest FileSystem for the Amiga imho.

But i have one little Question, that really want to know ... hmm, how i make it short...? ( i try )

Well, lets say you copy a file to a PFS3AIO Partition;
the file gets written and after maybe 1 second the HD LED Flashes again. (for a very brief moment)(maybe some sort of "verifying") ok

But this happends also when
1) I turn on the Amiga,
2) press both Mouse buttons immediately to get into the Early Startup Screen
3) choosing "Boot with no Startup-Sequence"
4) Amiga Reboots...
5) I am at the Shell Screen
6) but then, the HD LED flashes 1 second or so later, just like a file was written.


Call me confused

What is happening there ?
What is this 1 second after write HD LED flash and why even after "boot with no startup-sequence" ?

Questions over questions, i know

Thanks guys and thanks again Toni& Co for all there work they do for us Amigians

You guys are f...... incredible