Pismo Mount Installer Error

Pismo File Mount Audit Package is a great way to mount ISOs on Windows. Once installed, converting an ISO into a folder is as simple as a right-click on the ISO file.

The only problem – it got an error at installation. “ERROR: 193 Unable to execute command “…pfmap-050.exe\pfmap-setup.exe”. (The dots contained the path to the installer)

Alternate versions produced the same error. I searched Google and didn’t find much to help out. In case anyone else has the same problem, the solution was to move the file to the root of the filesystem (C:\). My guess is it wasn’t handling spaces in the path properly, so any path without spaces would work.

» Permalink | Comments (6) | Computers

Comments (Post a comment) | Comments RSS feed

Pismo Technic offers free e-mail support for PFM Audit Package. Whatever the issue is you have experienced with install, I would like to see it diagnosed and resolved. Spaces in the path should not be a problem.
» Comment by Joe on March 18, 2009 @ 1:00 am
@Joe Thanks for the reply. I tried the installer on another machine and it ran with spaces in the path. However, whenever the installer runs Microsoft IntelliType Pro (used for my keyboard) crashes. Strange. I’d be happy to provide you with any information you’d like.
» Comment by Dan on March 18, 2009 @ 1:31 am
Worked perfectly – Tried to run from the desktop and errored. Moved directly into the c: drive and worked perfect. Thanks alot!
» Comment by Liam on August 22, 2010 @ 3:11 pm
I just want to offer my thanks to the OP. I had the exact same problem and your solution worked perfectly. I too was perplexed about the issue, as I already had this build running on another machine. I have no clue whatsoever as to why the installer would not work on this machine without me having to use your fix. In any case, thank you very much.

-IF
February 04, 2011
» Comment by Ian on February 4, 2011 @ 8:15 pm
@Ian You’re welcome, I’m glad it worked for you.
» Comment by Dan on February 4, 2011 @ 11:44 pm
Hi folks,

thanks for the comments. Moving the installer to c:\ just fixed the problem.

Regards,

Alexis
» Comment by Alexis on March 27, 2011 @ 4:48 pm