Annoying behavior for network shares mapped to 'B:'
Posted: 29.04.2014, 18:52
Apologies if this has already been posted, I did not find it with a cursory search.
I had a network share mapped to B:, any time I accessed it in Freecommander (build 650) any action would return an 'asterisk' warning and the folder tree would select my DVD drive (h: the last in the tree). FreeCommander would also occasionally dump me out to 'Computer' stating that the device at H: was not ready while browsing B:. Suspecting this was an error with network shares mapped to B: I remapped to Z: and no longer have this issue. I then added a new share to B: and navigating that share selects z: from the folder tree- Still annoying, but more liveable.
The first issue can be reproduced by mapping a network share at B: and browsing it with an empty optical drive as the last in the folder tree. but there appears to be an issue with handling Network shares on B:, and I would suspect A: as well, but I have not tested it.
I had a network share mapped to B:, any time I accessed it in Freecommander (build 650) any action would return an 'asterisk' warning and the folder tree would select my DVD drive (h: the last in the tree). FreeCommander would also occasionally dump me out to 'Computer' stating that the device at H: was not ready while browsing B:. Suspecting this was an error with network shares mapped to B: I remapped to Z: and no longer have this issue. I then added a new share to B: and navigating that share selects z: from the folder tree- Still annoying, but more liveable.
The first issue can be reproduced by mapping a network share at B: and browsing it with an empty optical drive as the last in the folder tree. but there appears to be an issue with handling Network shares on B:, and I would suspect A: as well, but I have not tested it.