I never managed to get CrossDOS in OS 3.2 to mount anything, so what are the known limitations?

From OS 3.1 source leak, one limitation mentioned in source comments, is support for only MSDOS-3 variant of MBR partition scheme - is this still the case? Or are extended partitions with logical partitions supported? And FAT32 is supposedly supposed to just work, but does that include larger block sizes for larger partitions? If so, are larger blocksize supposed to be automatically detected, or does it require manually configuration in mountfile?

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

So noone else really got it working either?

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

Not tried it and don't have it yet. But I see they have extended CrossDOS. Did you try these hints in the FAQ?

https://aminet.net/package/docs/help/AmigaOS_3.2-FAQ

@Hypex

Yes, of course. It is highly confusing though, with for example this sentence:

Quote:

Note: CrossDOS supports long file names, the mount flags "EnableNSD", "DirectSCSI", Fat32, Fat16, Fat12 and Fat8.

What is a “mount flag”? There is “flags” in a mountfile, but it can only be a number.
“EnableNSD” is accepted as _keyword_, but “DirectSCSI” is not, and neither are any of the FAT variants. Nowhere is there any mention of blocksize (sectorsize), extended partitions etc. I suspect though, that only 512 bytes blocksize is supported, since if I put anything higher, the partition size (as shown by the “format”) also increases.

https://support.microsoft.com/en-us/topic/default-cluster-size-for-ntfs-fat-and-exfat-9772e6f1-e31a-00d7-e18f-73169155af95

So 64MB tops? For a filesystem handler that’s touted to replace fat95?

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

at least fat95 and ntfilesystem are working in os3.2 with floppy and usb

@kolla

Quote:

What is a “mount flag”? There is “flags” in a mountfile, but it can only be a number. “EnableNSD” is accepted as _keyword_, but “DirectSCSI” is not, and neither are any of the FAT variants.

You're right. They are using confusing terms with no example. No examples Cross DOS Drivers to clear it up?

Also, they are slightly obsessed with using examples like Linux. That may not have been around when the Mount system was implemented but why don't they stick to AmigaDOS? Also, mounting is easier in Linux, as you don't need to create a file to do it.

I can only determine they may mean the Startup string as it's the way I know of to pass a string. There is also Control which is for serial.


https://wiki.amigaos.net/wiki/AmigaOS_Manual:_AmigaDOS_Additional_Amiga_Directories#Creating_a_MountFile_or_MountList_Entry

Quote:

Nowhere is there any mention of blocksize (sectorsize), extended partitions etc. I suspect though, that only 512 bytes blocksize is supported, since if I put anything higher, the partition size (as shown by the “format”) also increases.

It was designed with floppy disks in mind. But that's rather too technical for my liking. Does it support block size of 0 for dynamic sizes?

Quote:

So 64MB tops? For a filesystem handler that’s touted to replace fat95?

Doesn't sound right if it supports FAT32. But are other tools provided? OS3.9 had the Mounter and I think it's sorely needed here.

@kolla

This may not be how to fix your dilemma, however, have you tried DOS-2-DOS instead?
I believe the later versions, also supported the high-density IBM format. (You will need the half-spin speed HD AMIGA drive to do that)
From memory, it was Central Coast Software that coded it????
EAB should have an archive in their repository.
At the very least, you will be able to read/write to IBM floppies from a real Amiga. Maybe you are after partition access and not floppies. I am unsure if it can do the conversion on HDD partitions.

Last edited by SHADES on 09-Nov-2022 at 07:57 PM.

_________________
It's not the question that's the problem, it's the problem that's the question.