Is it possible to make One Commander the primary file browser in W10

[Eduard Bitto]

Hello,

I have two unrelated questions. I am a fairly new user of W10 system, I used macOS for the last 25 years; One Commander makes W10 file navigation experience bearable for me... So my questions may have an obvious answer, I am just not aware of them at the moment.

1) Is there a way to set W10 so that Windows Explorer calls are intercepted? An example: I download a file, from the browser I select open/show the file and ... the Windows Explorer does it. Is there a way to make sure One Commander does it instead? If not, would it be possible to add a contextual menu item so that the user can open the current directory opened in the Widows Explorer in One Commander? This would save time navigating there from scratch.

2) An unrelated question/issue. I am referring to a behavior I see in v3 beta 618 build. I use network samba shares for all my important files, these are served from my home Linux server. When I switch to admin mode (CTRL+SHIFT+F12) of One Commander I lose access to these mounts, and at the same time I cannot quit One Commander from the application, there is a process still running in the background when I close the main window. I had to use Task Manager to kill the process and restart One Commander in the regular mode. Is this an intended feature? Shouldn't there be an option to quit the application? I noted in v2 there was an option to regulate this behavior, I do not see in in v3.

Thanks for any insights.

Ed B.

[Milos Paripovic]

Hello Ed, 

At this time there is only manual registry edits to make it possible to register OC as default folder handler. You can find it in this forum but I can only recommend it if you had to restore registry before; I have missed some \ or other character before and made bad registry entries, and restoring it is not fun. It is tricky in this case because if you do that the File Explorer becomes useless and even clicking a folder in File Explorer will try to open OC. I have not tested it much as I have to run OC from development environment all the time, so I'd need to test it more before I know how well it works. After the official release I will make a button in settings to register it in a safe way, so it may be better to wait.

OC runs in background for faster start and to keep the any ongoing copy/move operations alive, and several other reasons. To close it you can right-click on icon in System Tray and click close, or hold Ctrl while clicking the window close button.

Running as admin won't show shares because admin is a different user, so program runs in that user's context; Windows works that way. You'd have to mount those drives from OC so that user also to be able to access these... but I have just realized that Drives>...>Map network drive won't work for that if the network drive is password protected, so I will have to add that soon. I have just tested and accessing network shares directly by typing the path \\comp\share does work and uses already saved Windows credentials (I didn't expect it to work, but Windows is weird). If you can access those that way, you can also add these to favorites for easier access next time