Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: nyteschayde on January 16, 2017, 05:09:34 AM
-
I searched Aminet for HFS+ file system entries and it doesn't seem like there is one that would work for the modern incarnation of HFS. I looked for ExFAT and there are some OS4.x implementations.
There is FAT32 but there seems to be some potential issues with directory length and disk size; in this case 128GB. Perhaps I am wrong about the FAT32 stuff.
Should I endeavor to make EXT2 work with my MacOS installation and/or Windows machines? EXT2 and EXT3 are certainly superior to FAT32 and there seems to be a driver for EXT2/3 on Aminet.
Thoughts? Has anybody used this with Trident4.4/Subway?
-
I don't think you get into problems with FAT32 either, if you don't want to change by other reasons. FAT32 is the most compatible one at least if you're going to use it in "obscure" machines.
I have even 2TB external HD formatted to FAT32 for backup use, and couple 1TB drives too, and so far they have worked :) And many bigger than 128GB external drives also come pre-formatted in FAT32.
HFS+ is the most unlikely to get write support in "alien" systems, so I wouldn't use that at least...
-
the only problem with FAT32 is that you cant save files larger than 4GB
Don't know if that is a limiting factor (not in the Amiga Classic World IMHO)
Mike
-
I searched Aminet for HFS+ file system entries and it doesn't seem like there is one that would work for the modern incarnation of HFS. I looked for ExFAT and there are some OS4.x implementations.
There is FAT32 but there seems to be some potential issues with directory length and disk size; in this case 128GB. Perhaps I am wrong about the FAT32 stuff.
Should I endeavor to make EXT2 work with my MacOS installation and/or Windows machines? EXT2 and EXT3 are certainly superior to FAT32 and there seems to be a driver for EXT2/3 on Aminet.
Thoughts? Has anybody used this with Trident4.4/Subway?
What is your intended purpose of the thumb drive?
For most versatility i recommend keeping the FAT32 fs.
If you aim for large files and data transfer between modern systems, NTFS will work in most these systems. with a little hassle it will work in a mac.
Making Windows system reading HFS or EXT partitions will be hard work.
Software like "get data back" will read and let you "salvage" files from a EXT drive. but usage will be severely limited.
-
Thanks to OP and all for replies. I have been wondering about this issue, and have no useful input on the subject, but at least I do have a better idea now of how to go about these matters.
-
What is your intended purpose of the thumb drive?
For most versatility i recommend keeping the FAT32 fs.
If you aim for large files and data transfer between modern systems, NTFS will work in most these systems. with a little hassle it will work in a mac.
Making Windows system reading HFS or EXT partitions will be hard work.
Software like "get data back" will read and let you "salvage" files from a EXT drive. but usage will be severely limited.
I am using this to update a large set of Amiga files that are downloaded and maintained on a USB thumbdrive of 128GB in size, but that I also want the Amiga to be able to write to and read from.
Long name support and maintaining the case of file names when viewed on the Amiga side is critical.
-
Long name support and maintaining the case of file names when viewed on the Amiga side is critical.
FAT95 (http://aminet.net/package/disk/misc/fat95) on the Amiga side supports up to 104 characters long filenames. PFS does up to 107 characters. FFS, as I recall, is limited to 30 characters. If that information is helpful to you, at all?
FWIW Some directory utilities choke when reading long file names, in my experience.
Personally I'd just FAT95 (FAT32) and be done with it, if you have any plans to transfer this flash drive among different computers.
-
I guess if you are trying to emulate a server, you are better off using a server style of file system, probably derived from Nix, that both sides can read and write. FAT32 isn't really designed for that. It does limit how complex the directory structure can be, but if the structure actually used isn't that complex, this is not an issue.
Even if it works now, it will fall over sooner than the other options, as entropy on the structure occurs, it becomes more complex over time. That process might never complete before a system fails elsewhere, or it could happen rapidly, depending on how often the contents are altered. The universe could in theory die before the directories overflow.
Myself, I would want to put a hardware write protect option in there somewhere. You don't want it to change very often, I guess. Not sure about that, but if either side can trash it spontaneously, then obviously you are doubling your risk factor. Might be too late, and let's face it, double "almost infinitely zero" is still "almost infinitely zero" so it's maybe not much of a real factor.
I just like SD cards over USB thumb drives. For this sort of thing, anyway.
-
FAT95 (http://aminet.net/package/disk/misc/fat95) on the Amiga side supports up to 104 characters long filenames. PFS does up to 107 characters. FFS, as I recall, is limited to 30 characters. If that information is helpful to you, at all?
FWIW Some directory utilities choke when reading long file names, in my experience.
Personally I'd just FAT95 (FAT32) and be done with it, if you have any plans to transfer this flash drive among different computers.
PFS and FFS won't work because I cannot mount those, to my knowledge, on Mac and Windows based systems. The FAT95 long filename support should suffice. So thanks!
-
There is this old relic, but I don't think it's going to be compliant with a 64bit device.
It was designed more as an Amiga filesystem that could read alien systems, even format them, so it is worth a shot maybe.
http://de4.aminet.net/disk/misc/xfs.readme
Just an alternative to try, if it hasn't got LFN support and 64 bit device support then it won't do you any good at all.
Then again it might. But don't even bother looking if what you have is working fine. Like I said, it's a relic.