reactos/dll/win32/ubtrfs/ubtrfs.spec

@ stdcall Chkdsk(ptr ptr long long long long ptr ptr ptr ptr ptr) BtrfsChkdsk
@ stdcall Format(ptr ptr long long long ptr long) BtrfsFormat

@ stdcall GetFilesystemInformation(long long ptr)
@ stdcall SetIncompatFlags(int64)
@ stdcall SetSizes(long long)
[FSLIB][FMIFS][AUTOCHK][SETUPLIB] Use more Windows-compatible (but not fully compatible yet) Format() and Chkdsk() ULIB functions. [AUTOCHK] Add also support for scanning FATX volumes. The Format(), FormatEx(), Chkdsk(), ChkdskEx() functions exposed by the U.DLL user-mode FS library dlls are different (and have different prototypes) than the similarly-named functions exported by FMIFS.DLL . In particular, what we used to call "xxxChkdskEx()" and "xxxFormatEx()" in our U.DLL libraries actually correspond more, from their arguments, to the "Chkdsk()" and "Format()" functions in Windows' U.DLL . Their Ex() counterparts instead take most of the parameters through a structure passed by pointer. On FMIFS.DLL side, while FMIFS!Chkdsk() calls U.DLL!Chkdsk() and FMIFS!ChkdskEx() calls U.DLL!ChkdskEx() (and we do not implement these Ex() functions at the moment), both FMIFS!Format() and FMIFS!FormatEx() call U.DLL!Format() instead, while FMIFS!FormatEx2() calls U.DLL!FormatEx() (that we do not implement yet either) !! To improve that, refactor the calls to these U.DLL functions so as to respect the more compatible prototypes: They contain the correct number of parameters in a compatible order. However, some of the parameters do not have the same types yet: the strings are kept here in PUNICODE_STRINGS, while on Windows they are passed via an undocumented DSTRING struct, and the FMIFS callback is instead a MESSAGE struct/class on Windows. Finally, the MEDIA_TYPE parameter in U.DLL!Format() is equivalent, yet not fully 100% in 1-to-1 correspondence, with the FMIFS_MEDIA_FLAG used in the corresponding FMIFS.DLL functions. One thing to notice is that the U.DLL!Format() (and the Ex) functions support a BOOLEAN (a flag resp.) for telling that a backwards-compatible FS version should be used instead of the (default) latest FS version. This is used e.g. by the FAT FS, where by default FAT32 is selected (depending also on other constraints like, the disk and the partition sizes), unless that bit is set in which case, FAT16 (or 12) is used. 2020-11-22 04:35:37 +00:00			`@ stdcall Chkdsk(ptr ptr long long long long ptr ptr ptr ptr ptr) BtrfsChkdsk`
			`@ stdcall Format(ptr ptr long long long ptr long) BtrfsFormat`
[UBTRFS] Addendum to 255ef2c3: Add missing exports expected by mkbtrfs. CORE-16383 CORE-16354 2019-09-21 02:35:01 +00:00
			`@ stdcall GetFilesystemInformation(long long ptr)`
			`@ stdcall SetIncompatFlags(int64)`
			`@ stdcall SetSizes(long long)`