In the error message, the text "Exception: " comes from cpmcbfs.c, and the rest of the text comes from the Eldos CbFS library it uses.
Searching for that text doesn't find anything.
The exception you see could be happening at any point of the initialisation process, but in my opinion, there are only 3 main calls to CbFS likely to cause it :-
cbfs.CreateStorage(); // installs CP/M callback filesytem as a drive
cbfs.AddMountingPoint(mountPoint); // creates Z:
cbfs.MountMedia(30000); // mounts drive at Z:
Eldos appear to have sold their stuff to Callback Technologies, and the CbFS product has now become CBFS Connect.
These are the relevant documentation pages for the new product, and they seem to be very close to the APIs I am using.
https://www.callbacktechnologies.com/kb ... orage.html
https://www.callbacktechnologies.com/kb ... point.html
https://www.callbacktechnologies.com/kb ... media.html
https://www.callbacktechnologies.com/kb ... tml#extlog
The last link has this text:
Several methods of CBFSConnect class (namely Install(), CreateStorage() and MountMedia() methods and Install function of the installer DLL) write extended information about the reasons of the reported error to Windows event log. The user-mode part of CBFS Connect writes records to "Windows events \ Applications" folder of Windows event log. The kernel-mode part of CBFS Connect writes records to "Windows events \ System" folder of Windows event log.
So can you post what you see in your Windows Event Logs...?
As for your comment about Cloud-drives, I suppose its possible.
Its also possible that cloud drive products themselves also use CbFS in their implementation.
Its also possible that they use a different version of CbFS (ie: the CBFS Connect), and maybe there is some incompatibility as a result.
I don't know really, just random thoughts.