i think i found a bug

[TheWave]

I have a server with two hdd's. The second hdd on the server is mounted at "D" folder at the root drive. When browsing the server's c$ and entering d folder i get the free space wrong. it tells me i have like 1gb of 10gb instead of 1gp of 20gb.

[pdavit]

Does Explorer produce the expected capacity?

If not then probably the OS is passing the wrong information to TC.

[IGL]

What is the size of C: drive?
I do not know how disk information is provided if you have a drive mounted to directory on other drive - I have only one NTFS partition.
You can check what size does the explorer show.
You may run scandisk and check all drives if it's all ok.
Try to see what happens when you save e.g. 12GB of data onto directory D (second HDD) - then what does TC (and what does Explorer) say about free size and total size?

[TheWave]

How do i check the free capacity of a directory in explorer?

[Clo]

2TheWave

How do i check the free capacity of a directory in explorer?

Hi !
• A right-clic on the drive-letter small icon >>> Properties
you get a graphic which shows the used and free spaces for that drive.
 Not sure that'll work in your case…

  Kind regards,
Claude
Clo

[DanyBoss]

TOTALCMD caused an invalid page fault in
module KERNEL32.DLL at 017f:bff87ede.
Registers:
EAX=c00309c4 CS=017f EIP=bff87ede EFLGS=00010216
EBX=0079f9fc SS=0187 ESP=0075ffd4 EBP=00760040
ECX=007601f9 DS=0187 ESI=81774734 FS=4b3f
EDX=bff76855 ES=0187 EDI=00760220 GS=0000
Bytes at CS:EIP:
53 56 57 8b 30 83 7d 10 01 8b 4e 38 89 4d f8 75
Stack dump:


This message comes every day.

Thanks

[ghisler(Author)]

When right clicking?

This probably means that you have installed a context menu shell extension which works only with Explorer. Explanation: Total Commander doesn't create the context menu by itself, but asks Explorer to do it (through OLE2). Some (rare) shell extensions try to access the Explorer window when the shell extenstion is loaded, which fails from Total Commander because there is no Explorer window! The only solution is to remove the shell extension from the context menu, or maybe ask the maker of the shell extension to fix the problem.

You can find these extensions in the registry, usually under
HKEY_CLASSES_ROOT\Folder\shellex\ContextMenuHandlers
or
HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers

To disable them, first export the registry key to a *.reg file (so you can re-add the extensions at a later time), then remove them one after the other and re-try if the context menu works again in Total Commander.