Show <JUNCTION><SYMLINKD>instead of <LNK>

Here you can propose new features, make suggestions etc.

Moderators: Hacker, petermad, Stefan2, white

Post Reply
User avatar
dott
Senior Member
Senior Member
Posts: 285
Joined: 2007-03-04, 00:58 UTC
Location: La Plata, Argentina

Show <JUNCTION><SYMLINKD>instead of <LNK>

Post by *dott »

Show <JUNCTION>&<SYMLINKD> instead of <LNK> in size column.
Probablemente no
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50479
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

What would be the advantage? An average user wouldn't know the difference anyway...
Author of Total Commander
https://www.ghisler.com
User avatar
Samuel
Power Member
Power Member
Posts: 1930
Joined: 2003-08-29, 15:44 UTC
Location: Germany, Brandenburg an der Havel
Contact:

Post by *Samuel »

As I (do not know)

:D

Edit: And would like to know :)
User avatar
dott
Senior Member
Senior Member
Posts: 285
Joined: 2007-03-04, 00:58 UTC
Location: La Plata, Argentina

Post by *dott »

ghisler(Author) wrote:What would be the advantage? An average user wouldn't know the difference anyway...
Perhaps you are right, nevertheless the advantage is that Total Commander will be showing the correct information.
Samuel wrote:Edit: And would like to know :)
Mark Russinovich wrote:....A major difference in the way Windows resolves symbolic links and directory junctions is where the processing takes place. Windows processes symbolic links on the local system, even when they reference a location on a remote file server. Windows processes directory junctions that reference a remote file server on the server itself. Symbolic links on a server can therefore refer to locations that are only accessible from a client, like other client volumes, whereas directory junctions cannot. To address this, Windows Vista supports the new symbolic link type for both files and directories...
Probablemente no
Post Reply