remove one drive from over view ?

[flyby]

Is it possible to remove one dridrive from the overview.
Our employees should not have access to c:\, so it wourld be nice if i can remove this drive og denie access to it.

Regards
Thomas

[Stitscher]

2flyby
There is a ini-Setting "Allowed=xyz".
http://www.ghisler.ch/wiki/index.php/Ini-settings#Configuration

Stitscher

[icfu]

...additionally this should be done by adjusting NTFS rights...
Even stupid employees are able to open Windows Explorer and enter C:\ in address bar.

Icfu

[flyby]

2flyby
There is a ini-Setting "Allowed=xyz".
http://www.ghisler.ch/wiki/index.php/Ini-settings#Configuration

Stitscher

Thanks it works om my PC where it installe nromal.
But on my server, wincmd runs from a dir.
It is not install like this, but is just moved there and made a schortcut to wincmd.exe
And then there is not at wincmd.ini in windows dir.

Is there anyway to made this work ?

Regards and RESPEKT

Thomas

[Stitscher]

Check out where the wincmd.ini is stored.

Menue bar--->Help--->About Total Commander

[flyby]

ohh, it is in dokument and settings/administrator/window/wincmd.ini

That is not so god, right?
When a nother profile open wincmd that thay do not have access to this file..
Can i change the location on this wincmd.ini ?

[Stitscher]

http://www.ghisler.ch/wiki/index.php/Ini-settings#Configuration

UseIniInProgramDir=0

This variable will only be read if the wincmd.ini is located in the same dir as the program.

It is the sum of the following values:
1: Use wincmd.ini in program dir if no other location is set via registry or parameters
2: Use wcx_ftp.ini in program dir if no other location is set via registry or parameters
4: Override registry settings (but not command line parameters)

[Sir_SiLvA]

And now u please do the following:

1) press F1 inside TC and read the help
2) read the Wiki
3) read Clo's Tutorial
4) if you still have a question you use the search

5) Welcome on Board

[flyby]

If i change the path to wincmd.ini it works but when i relogin that defautl path is back.

But if i use H:\totalcmd\TOTALCMD.EXE /o /n /i=h:\totalcmd\wincmd.ini in start link it works everytime.

But is this the way to handle this problem ?

[Sheepdog]

If i change the path to wincmd.ini it works but when i relogin that defautl path is back.

How did you change the path to the ini file?

But if i use H:\totalcmd\TOTALCMD.EXE /o /n /i=h:\totalcmd\wincmd.ini in start link it works everytime.

That is no surprise. If you use commandline parameters to define the inifile this always overrides the other settings. So no change of the location of the inifile will make sure that all users will start TC with your settings.

BTW if you want to change the standard ini file for all users on your system please use Inireloc.exe and check the "set this location for all users on this system" option.

But is this the way to handle this problem ?

Since every 'advanced' user can call Totalcmd.exe with commandline parameter probably the way icfu proposed is the only solution. Restrict the access of the drive by defining NTFS- access rules.

sheepdog

[flyby]

Hi

Inireloc.exe works fine, but i need to run it on every user in AD.
(We run windows terminal server)

So if there is nothing wrong in using this line ill do that.H:\totalcmd\TOTALCMD.EXE /o /n /i=h:\totalcmd\wincmd.ini
Im only asking, be cores i can´t see if there comes any problems later by dooing this. And you meby know there would.

[Sir_SiLvA]

Sorry but when u cant read what we write
(Stitcher and me)
http://ghisler.ch/board/viewtopic.php?p=97532&sid=1ac8579f8ea5c770ee778d2596a0e700#97532
you deserve as punishment to set it for every user per Inireloc.Exe

[ghisler(Author)]

There is a (badly documented, only in history) registry key which has the same functionality as the Allowed= line in wincmd.ini:

Under
HKEY_CURRENT_USER\Software\Ghisler\Total Commander\configuration
add a new value named allowed (type string), which contains the allowed drive letters (plus \ for network).

The value will be combined with the value in the ini file (the more restricted wins). For example, if the registry value contains
ACDEF
and the ini file EFGH, then this will be combined to EF.

The registry key has the adavantage that it can be protected by the admin, so the users cannot change it.

[Sheepdog]

Interesting. Now it is at least documented in the Wiki

sheepdog

[icfu]

The registry key has the adavantage that it can be protected by the admin, so the users cannot change it.

Doesn't it make more sense to set limits machine wide before configuring each user separately?
HKLM\Software\Ghisler\Total Commander\configuration has no effect?

Icfu