Another new feature is the FastFileSystem which improves on OldFileSystem (OFS). It can boot from HD or RAD, the FS can be stored on the RDB.

Full history of FFS on Wikipedia: https://en.wikipedia.org/wiki/Amiga_Fast_File_System

_________________
Peter J Hutchison
http://www.pjhutchison.org/

@pjhutch

I remember using RAD on Amiga500 kickstart 1.3, I guess FFS came in kickstart 1.3, not 2.0.

My Amiga500 came with kickstart 1.3 and workbench 1.2n

My favorite tool was LastHope, but maybe not a filesystem repair tool but tool to fix bad secotor check sums, by reading the sector until you where lucky and had all correct CRC's for all blocks.

Come to think of it might have been loaded as resident module later, but anyway I'm pretty sure formatted disks as FFS, maybe the bootblock loaded FFS? I'm not sure how that works.

Last edited by NutsAboutAmiga on 21-Jan-2017 at 12:41 PM.
Last edited by NutsAboutAmiga on 21-Jan-2017 at 10:42 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@pjhutch

Are you talking about OS1.3 here? Looks like you are continuing a conversation here. I can't see any context except some new feature that was here around 30 years ago or so.

@NutsAboutAmiga

FFS 1.3 and FSS 2.0 weren't quite compatible--I formatted a number of 1.3 diskettes with 1.3--you had to have a special DEVS: mount-file--and 2.0 wouldn't read the upper half....did it because FFS stored more data than OFS, a big deal when you only had 1 meg of raw storage to play with....

@Hypex

I think he is continuing discussion of the new guy with A500 1.2 who want to start developing for that machine...

_________________
"When the Amiga came out, everyone [at Apple] was scared as hell." (J.L. Gassée, former CEO of Apple France and chief of devs of Mac II-fx, interviewed by Amazing Computing, Nov 1996).

@pgf_666

Was that using the same filesystem? For example DOS3. I recall I had to put together a mountlist so I could format my disks with FFS. But don't recall having trouble on my A1200 or if I tried them on my A1200.

Did you also try the 1.3 mountlist on 2.0? Or convert it a DOS driver?

At first I thought you was saying 2.0 wouldn't read the upper half of the mount file.

@Raffaele

I didn't see any discussion on FFS.

@Hypex

He continued discussion from Kickstart 1.3... Other people pointed Kick 1.3 had only Autoboot in comparison to 1.2.

This guy pointed 1.3 had also FFS support...

"Another new feature" (is related to) "Kickstart 1.3"...

Last edited by Raffaele on 24-Jan-2017 at 09:25 AM.

_________________
"When the Amiga came out, everyone [at Apple] was scared as hell." (J.L. Gassée, former CEO of Apple France and chief of devs of Mac II-fx, interviewed by Amazing Computing, Nov 1996).

@Raffaele

Yes I saw that. I see what you mean. I searched for FFS specifically and didn't find it. So why I was lost. I guess to me Autoboot and FFS are different things.

@Raffaele

Quote:

This guy pointed 1.3 had also FFS support...

Which is not true, at least if you look at Kickstart only. At that time FFS was only available on disk which means you could use it for floppies only with a mountlist entry and for harddrives only if the controller's driver allowed to read file systems from disk and add them to filesystem.resource.

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

@thomas

I'm deeply puzzled by this.

I know RAD worked, there where lots of diskmags that used RAD to unpack games on.
so FFS was needed by RAD, that can't be true can it?

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

RAD is a virtual floppy. By default it uses OFS, just like real floppies do.

You can change the mountlist entry to FFS, like you can make a mountlist entry for FFS floppies. But you cannot boot from either of them.

_________________
Email: thomas-rapp@web.de
Home: thomas-rapp.homepage.t-online.de

@thomas

Quote:

thomas wrote: @NutsAboutAmiga RAD is a virtual floppy. By default it uses OFS, just like real floppies do. You can change the mountlist entry to FFS, like you can make a mountlist entry for FFS floppies. But you cannot boot from either of them.

Is that only on OS4.x?
I am fairly sure I used to set a RAD: up and booted from it with AmigaOS 1.3.. possibly AmigaOS 3.1 too on my Amiga 2000..

Or is my memory failing me?

@Amigo1

I think the point was that you can't boot frm RAD: under 1.3 if you set it up to use *FFS* .

An OFS RAD: could boot ( I think, not used a 1,3 machine for a loooong time)

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@thomas

Quote:

thomas wrote: @NutsAboutAmiga RAD is a virtual floppy. By default it uses OFS, just like real floppies do.

Actually, it's a bit stranger than that

Any file system which you can mount on a disk, or a partition, will initialize the volume using its choice of data structures if you use the "Format" command. Yet RAD: does not need to be formatted in the first place, and it does not invoke the "Format" command either, for that matter.

The ramdrive.device, which RAD: uses, initializes the file system signature block and the root block (smack in the middle of the disk) when it starts up. The root block is a "partial" root block, lacking the bitmap data structures which are needed to keep track of which blocks are still available for use.

When the file system mounts this device, it finds that the root block is missing something and proceeds to set up the bitmap blocks, filling in the bitmap. These steps render RAD: fully usable.

RAD: more or less auto-formats itself, making a few assumptions about how the file system will access it. None of these steps are required or even expect from floppy diks

Last edited by olsen on 26-Jan-2017 at 02:58 PM.

@Amigo1

Quote:

I am fairly sure I used to set a RAD: up and booted from it with AmigaOS 1.3.. possibly AmigaOS 3.1 too on my Amiga 2000..

Yes I recall it was one of the fun things to do on Amiga. And I started having that fun on my first Amiga, a 1.3 A500.

It was also annoying, because it kept allocating disk blocks from chip memory. And no matter what buffer settings I played with it kept using chip ram!