26
Support and Feedback / Re: LNK shortcut creation bug
« on: May 10, 2018, 14:54:38 »
So you have default on-start shortcut type not LNK, but smth else. Yes? I my shortcut creation windows always starts with LNK
January 2024
MultiCommander v13.5 is released!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Looks like it is packed with a extended zip algorithm, that not many zip tools support
It is only that file or other large files too ?For many. And not only for very large, but for those written by some app to filesystem intensively.
What display settings for the size/unit/dec are you using..
Restart? no Refresh...Yes, exactly restart. I think restart is more hard option than resfresh dirs.
you got lots of tabs opened showing same location ?
is a lot of files added/removed from outside of mc.I wouldn't say so, just routine work. My work is not connected with file-management or processing big data amounts.
something else that cause lots of rescans of the filesystem`?
Fast / slow drive ?, XP ?
A force refresh should fix it since it is a timing issues, it is just a visualization issue.. But I have never been able to recreate it
TS devices are supported, they are shown under NET: since windows expose then as virtual network shares
No that are not mapped drive.. Mapped drives are network path that are connected to drive letters. like Z: X: and so on.
RDP connected devices are something completely different
Drives connected via RDP are located under the virual server path \\TSCLIENT you find them under the network (Net:) or by going to \\TSCLIENT
net use Z: \\tsclient\C
it works wonderfully and become visible in MC. Okay, I can schedule this command at start but maybe it can be done in a more native way?
and from the admin command prompt you can do "dir Z:\" if it now is Z..
You can also open a admin command prompt and run "net use" and see if they are listed