Wouldn't it be possible to use functions in FMIFS like described here : http://doc.sch130.ns...rce/fmifs.shtml
It could be possible, of course. Problem is that this is not officially documented anywhere. Not that I am entirely principally against using undocumented API, but they tend to introduce some more trouble to the development.
Generally speaking, undocumented functions can be changed between Windows versions, even between Service Pack versions and similar, without any official notice. It could also happen that they suddenly work in a quite different way than expected on another Windows version which could lead to unexpected behaviour. For example tools that use FormatEx in FMIFS tend to work mostly correct but slow and unreliable on Vista and 7. In this particular case the most useful way would be to for example use FormatEx in Windows NT 4.0, 2000 and XP, the Format WMI method
in Windows Server 2003, IFormatEngine / CFormatEngine in Vista and Windows 7 and whatever appropriate in upcoming versions. This requires some code maintenance that we pretty much don't have to think about today. Both to read about on partially or completely undocumented functions and then to implement them and maintain this. I don't think that is a generally good idea for a project like ImDisk.
If someone would develop an entirely new user interface they would find this a lot easier. They could create a .NET application that could easily use ImDisk API for various tasks and for example DiscUtils API for formatting and for recognizing image file formats and filesystem formats. That would be a user interface project with the main goal of being user-friendly, complete and robust. The current Control Panel applet could live a parallel life and could keep the target of primarily being compatible with old and new Windows versions without .NET or WMI requirements rather than implementing as many features as possible.