@wawa

I used the open sourced version on emulation until I started to suspect it might be the cause of some comaptibility issues. I didn't know about the specific mechanics of file-systems between host and client as I now have the emulation partition on ffs2. I also didn't know about pfs back in the day and read a lot about it after coming back because file-systems are the place I feel most comfortable from the location of the uset who isn't a developer. Yes I want to try it and if there is a os4 version then quite possibly it's what I'm looking for.

@Srtest

I recompiled it from the sources, here you go:
https://drive.google.com/file/d/0BzblJSPJy3DCMkJncGtaV0JhWWM/view?usp=sharing

I haven't tested it, but it should still work.

_________________
This is just like television, only you can see much further.

@BSzili

Much appreciated man. What is the correct identification? 0x50465301, 0x50465303 or maybe 0x6d755046?

@Srtest

I think most volumes use 0x50465303, but you can add mount list files for the others too.

_________________
This is just like television, only you can see much further.

@BSzili

It didn't work (nothing appears when adding the fs), switched to the aminet version (18.5) and it worked as 68k. Tried 19 with a mount command and everything using giggledisk and it didn't help and I can't format it - only with 18.5.

Last edited by Srtest on 19-Dec-2016 at 04:06 AM.

@Srtest

To be honest I never tried formatting disks with it under OS4. I was also lazy and just added it to my kicklayout, so I don't have to muck around with mounting and whatnot.

_________________
This is just like television, only you can see much further.

@BSzili

It works. Thanks! puting it in kicklayout as a module did it. It has a couple of issues though: no trashcan and format didn't work. I had to do a full format and then a quickformat on top of that. As you know on ssd that's not recommended and on larger volumes is quite a pain.

@Srtest

BTW, don't EVER do a full format on an SSD - even a small part of one - because it writes to every block and makes the whole partition "used", restricting the area that the controller can use for wear-levelling.

_________________
cheers
tony

Hyperion Support Forum: http://forum.hyperion-entertainment.biz/index.php

Well, got rid of it for now. Did even more harm and made the partition unusable. That's with the version posted in this thread.

@tonyw

I thought we don't have that on AOS.

Last edited by Srtest on 22-Dec-2016 at 11:18 PM.

@Srtest

Quote:

I thought we don't have that on AOS

We don't do wear-levelling in software, because most (all?) SSDs build it into their controllers these days. But the disk controller needs space to move things around, and if you write to every block, there ain't much space left for it to play.

_________________
cheers
tony

Hyperion Support Forum: http://forum.hyperion-entertainment.biz/index.php