When I install CBFS Driver 3.0.74 using CallbackFileSystem::Install()
with SupportPnP==TRUE and then create a virtual drive with the following characteristics
SetStorageCharacteristics(0);
SetStorageType(CallbackFileSystem::stDiskPnP);
the disk's type is reported as "fixed" (for testing I used drive list in "Far Manager").

At the same time, when the driver is installed with SupportPnP==FALSE and the disk is created with
SetStorageCharacteristics(0);
SetStorageType(CallbackFileSystem::stDisk);
I can see "subst" in the disk type field.

The problem is that some applications (like QuickBooks) do not allow their files to be saved on a "subst" drive.

My question is: is there any reason why the drive type is reported differently in these two modes and, which is more important, is there a way to control this behavior.

In Plug-n-play mode physical disk device is emulated using plug-n-play driver. Previously this was not supported. Personally I would file it as a bug of QuickBooks and that other applications. It's not their damn business at all, where the user wants to save his or her data.

I brought this topic only because I noticed the difference migrating from 2.5.59 to 3.0.74.
In 2.5.59 (which was definitely a non-PnP driver) virtual drives used to be "fixed".
When I considered switching to 3.0.74 I decided to use non-PnP mode because I expected it to work more like 2.5.59.
However, in 3.0.74 in non-PnP mode the disk became "subst".

I was trying to ask if there is a way to make the disk "fixed" again in non-PnP mode in 3.0.74.

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.