@kas1e
You won't ever catch every situation by identifier because the identifer is user-selectable. There are many users which run SFS or PFS with 0x43465300 (CFS\0) because this is what HDToolbox suggests if you don't change it.
According to the manual PFS2 and PFS3 shall use 0x50465302 (PFS\2) for the TD64 version and 0x50445302 (PDS\2) for the Direct-SCSI version. I usually use PFS\3 for PFS3.
There are even file systems which have a different identifier for each partition, for example fat95 uses the least siginificant byte to select the partition from an MBR partition table.
Furthermore the identifier only matters if there is an entry in filesystem.resource for it. In a mountlist or dosdriver you can use whatever you like.
Also you completely missed CD file systems yet. They usually use something like CD01 or CDFS depending on the preference of the author.
list of all FS indentificators
Re: list of all FS indentificators
@thomas
At last that how it was done in dopus5 modules (that checking on identificators), to showup info in the "informatin/ device information" menus. Probably that all need major rewrite, but in meantime just want to add more fs to the same checking code which already done by original dopus5 authors.
@All
Is there possibility to get from doslist->dol_misc.dol_volume.dol_DiskType that volume in question are RAM: , or all what possible to know from there is that its DOS9 ? And if nope, how i can know that volume in check are RAM (i.e. i know that is is DOS9, now i need to know that it is RAM).
At last that how it was done in dopus5 modules (that checking on identificators), to showup info in the "informatin/ device information" menus. Probably that all need major rewrite, but in meantime just want to add more fs to the same checking code which already done by original dopus5 authors.
@All
Is there possibility to get from doslist->dol_misc.dol_volume.dol_DiskType that volume in question are RAM: , or all what possible to know from there is that its DOS9 ? And if nope, how i can know that volume in check are RAM (i.e. i know that is is DOS9, now i need to know that it is RAM).
- salass00
- AmigaOS Core Developer
- Posts: 530
- Joined: Sat Jun 18, 2011 3:12 pm
- Location: Finland
- Contact:
Re: list of all FS indentificators
@kas1e
If it's just the filesystem name that you are after you can get it by parsing the version string which can be obtained by using FileSystemAttr()/FSA_VersionStringR. It will be in the format "filesystem_name VER.REV (dd.mm.yyyy)".
If it's just the filesystem name that you are after you can get it by parsing the version string which can be obtained by using FileSystemAttr()/FSA_VersionStringR. It will be in the format "filesystem_name VER.REV (dd.mm.yyyy)".
Re: list of all FS indentificators
@Thomas
Code: https://sourceforge.net/p/dopus5allamig ... /diskinfo/
See disinfo.c for diskinfo_info() and get_dostype_string()
@salas00
Thx
@joerg
Btw, read in another thread , but just to not make offtopic ask here:
Added:According to the manual PFS2 and PFS3 shall use 0x50465302 (PFS\2) for the TD64 version and 0x50445302 (PDS\2) for the Direct-SCSI version. I usually use PFS\3 for PFS3.
#define ID_PFS2_DISK 0x50465302
#define ID_PFS3_DISK 0x50465303
#define ID_PFS2_SCSI_DISK 0x50445302
#define ID_PFS3_SCSI_DISK 0x50445303
#define ID_PFS3_MULTI 0x6d755046
The only one FS with which i have actually problem to detect by dopus5 code is os4's fat32 (identificator 0x46415432). Its just show always OFS (DOS\0) for. NTFS, exFAT and all others from filesysbox are ok, but fat32 use crossdoss, so seems something different there.There are even file systems which have a different identifier for each partition, for example fat95 uses the least siginificant byte to select the partition from an MBR partition table.
Code: https://sourceforge.net/p/dopus5allamig ... /diskinfo/
See disinfo.c for diskinfo_info() and get_dostype_string()
@salas00
Thx
@joerg
Btw, read in another thread , but just to not make offtopic ask here:
As far as i know, os3.x have some SFS\1 already (someone says it was your one too, just for os3.x?). Also is it safe to add SFS\3 as #define ID_SFS3_DISK 0x53465303 ? In other words, is it safe to assume for os3/os4:and add new, AmigaOS 4.x only DOSTypes (SFS\1 and SFS\3) which allow using all UTF-8 strings.
?#define ID_SFS0_DISK 0x53465300
#define ID_SFS1_DISK 0x53465301
#define ID_SFS2_DISK 0x53465302
#define ID_SFS3_DISK 0x53465303
- salass00
- AmigaOS Core Developer
- Posts: 530
- Joined: Sat Jun 18, 2011 3:12 pm
- Location: Finland
- Contact:
Re: list of all FS indentificators
That person is probably confused and is thinking of SFS\2 which is supported in Joerg's m68k version as well as the AmigaOS 4.x version. At least I've never heard of any SFS\1.kas1e wrote: As far as i know, os3.x have some SFS\1 already (someone says it was your one too, just for os3.x?).
Re: list of all FS indentificators
Some early beta versions of SFS supporting partitions > 128 GB used DOSType SFS\1, but such versions should never have been available to anyone, except for OS4 beta testers maybe, and I'm quite sure there were no AmigaOS 3.x/m68k builds of these beta versions. The format was incompatible to the one used for SFS\2 now.salass00 wrote:That person is probably confused and is thinking of SFS\2 which is supported in Joerg's m68k version as well as the AmigaOS 4.x version. At least I've never heard of any SFS\1.kas1e wrote: As far as i know, os3.x have some SFS\1 already (someone says it was your one too, just for os3.x?).
As Thomas wrote you can use any DOSType on AmigaOS 3.x in the RDB for any file system, for example using 'PFS\4' for SFS and 'SFS\1' for FFS was possible.
@kas1e
Don't use any DOSTypes for SFS in your program, it supports FileSystemAttr() FSA_VersionStringR, FSA_DOSTypeR, etc., the AmigaOS 3.x/m68k versions support it as well, not only the AmigaOS 4.x versions.
Using DOSTypes as fall back could be done for old file systems which didn't implement FSA_VersionStringR yet, but even for such file systems it's possible to get the version string (for example C:Version can do it).
Re: list of all FS indentificators
Ram-handler is not a file system you can use on HD partitions, floppy disks, etc., therefore it doesn't need a DOSType and may not have any at all.kas1e wrote:Is there possibility to get from doslist->dol_misc.dol_volume.dol_DiskType that volume in question are RAM: