Open d1letant opened 5 years ago
I don't believe in that. Most probable your comparison is not fair. Third-party application problems
Check user credentials under which you run Far.
The problem exist not just in Far, but also in any shell I run from ConEmu! I've tried cmd/admin, powershell/admin...see attached image. Credentials, returned by cmdkey /list are the same in ConEmu an in Standalone prompt. When I run net use inside ConEmu, I get: C:>net useNew connections will not be remembered. There are no entries in the list. If I run net use outside ConEmu, it shows proper info. Any suggestions?
Mapped logical network drives / subst drives visibility depends on elevated/non-elevated creation in Windows 10 (as I experienced).
For example: I create my S: drive at elevated FAR start and using S: only in FAR. File explorer (and hopefully ransomware) can't see S:
So, try to start ConEmu with/without elevated!
My network drives have a permanent mappings, created by company sysadmin.2. ConEmu and Far inside ConEmu started in "elevated" (admin) mode, see below3. I only see this problem in Win 10, not in Win 7 Any other ideas?
On Wednesday, December 19, 2018, 3:18:48 AM PST, m0n notifications@github.com wrote:
Mapped logical network drives / subst drives visibility depends on elevated/non-elevated creation in Windows 10 (as I experienced).
For example: I create my S: drive at elevated FAR start and using S: only in FAR. File explorer (and hopefully ransomware) can't see S:
So, try to start ConEmu with/without elevated!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
@d1letant "Any other ideas?" - seems You didn't understood me... Your admin created mapping without elevated, so You will NOT see that drive in elevated ConEmu (and anything You start from ConEmu)
As I already wrote, start ConEmu non-elevated and You will see Your admin-mapped drives!
Or ask Your admin to create net mapping from an elevated Task too, which started at every login (then drives will be visible for both elevated and non-elevated apps)
Also I already wrote that this is a Windows10+ "feature". I used ConEmu/FAR for years and when I switched to Windows10 I played quite time to make things work...
Once more: subst/mapings created from an elevated prompt seen only for elevated programs (so those are invisible for plain File Explorer or other apps). Subst/mapings created from an non-elevated prompt seen only in non-elevated programs (like plain File Explorer or regular apps but unseen for Your elevated ConEmu/FAR)
You also can put a line in Settings/Startup/Environment in ConEmu: net use S: \\server\shared
You also can put a line in Settings/Startup/Environment in ConEmu: net use S: \server\shared
Nope. Environment page supports only limited set of commands, which ConEmu executes internally (set, chcp, alias).
But net use ... & ...
can be put in the task contents.
"Environment page supports only limited set of commands,..." - the way to enhance ;)
Got it to see the Network,Thank you for a detailed explanation. On Wednesday, December 19, 2018, 12:59:55 PM PST, m0n notifications@github.com wrote:
"Environment page supports only limited set of commands,..." - the way to enhance ;)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Versions
ConEmu build: 180626 x64 OS version: Windows 10 x64 Far Manager 3, 5525, x64
Problem description
Got a new Windows 10 PC at work, far manager doesn't see network drives under ConEmu/Windows 10
Steps to reproduce
Actual results
observe that only local Drives are presented If Far is open outside ConEmu, it does see all the network drives
Expected results
local Drives and Network Drives are presented
Additional files
Settings, screenshots, logs, etc.