How does OSFMount mounts an image "synchronously" as compared to AIM

[mArkGoldBridgE]

Hi,

Does anyone know exactly how OSFMount mounts "synchronously"?

For example, in a single PowerShell script block, after I mount an image using OSFMount.com commands, I was able to execute subsequent PowerShell commands. In contrast, with Arsenal Image Mounter (AIM), I cannot execute further commands until the mount process is terminated (using CTRL-C).

[David (PassMark)]

Neither option would seem to be difficult to implement from a coding point of view (the hard part of image mounting is writing the device driver required to emulate a physical disk or disk volume).

So I assume it was just a design decision.

[mArkGoldBridgE]

Hi David,

Thank you for your response.

Would you mind sharing more on how this is achieved in OSFMount? I'm relatively new to image mounters and programming, so would like to find out on how its being done.

[David (PassMark)]

It is beyond the scope of this support forum to teach programming.
But as a starting point research Threads and process and services.