Background:
My scientific research involves continuously generating large amounts of data. I use 4 mechanical hard drives in rotation, adding a folder number each time to track the order. Previously, I assigned drive letters, but the order often became inconsistent and difficult to manage. Later, I discovered that I could mount drives to folders. So I mounted the 4 mechanical hard drives under a fixed directory on my SSD, managing them as different subfolders under the same drive letter. This way, I can back up the parameters, format the oldest drive, and change the mount point number for reuse. https://ibb.co/mCQ0ynjp
Steps to reproduce:
Create a new VHD virtual disk in Windows Disk Management.
Initialize the virtual disk as GPT. Create a simple volume, but instead of assigning a drive letter, mount it to a folder — for example, C:\111.
Open and lock the C:\111 tab, keeping it as the current tab.
Are you sure the path still points to a valid location? Can you access it from Explorer? Total Commander should only show <Read error> when it can't read from the location.
__MACOSX
recycler
recycled
treeinfo.wc
$Recycle.Bin
$$DeleteMe*
treeinfo.ncd
system volume information
pagefile.sys
hiberfil.sys
You can access this path without any read errors when going through the parent path; issues only come up if the current tab is locked and you reopen TC.
Thanks for the extra details, I was able to reproduce the problem.
It happens because the mounted drive does not have a parent directory "..", so the list is completely empty and causes an error.
Fortunately it's not difficult to fix.
This should be fixed in Total Commander 11.58 RC4, please test!
14.06.26 Fixed: Starting Total Commander with drive mounted to directory on a locked tab would show <Read error!> if the mounted drive was empty (32/64)
