Crash and other problems on subst B:
Posted: 19.02.2014, 22:41
I have B: mapped to a mirror copy of my USB stick with subst:
subst b: D:\Backup\STICK16G-HS
So I can easily access my documents and use the portable apps and other tools, which are on this stick, even if the stick is not connected.
E.g.
- Navigate to B:\todo
- Create folder, e.g. cf_test
- After “Enter” the tab shows “B:todo”, but navigation bar shows T:\todo, and error message “The system can't find the specified path” “T:\todo”.
- Back to B:\todo
- Rename (F2) dir fc_test to fc_test2
- Crash after Enter: EAccessViolation: Access violation at address 006EAC2F in module 'FreeCommander.exe'. Read of address 00000000.
- After “Continue Application” I see the correct renamed dir.
This does not happen with other "subst" drives and not in same dir directly accessed via D:. So there may be some problem with some hard coded special handling of floppy drives!?
FreeCommander XE 2014 Build 650
Win7ult-64 or WinXP
subst b: D:\Backup\STICK16G-HS
So I can easily access my documents and use the portable apps and other tools, which are on this stick, even if the stick is not connected.
E.g.
- Navigate to B:\todo
- Create folder, e.g. cf_test
- After “Enter” the tab shows “B:todo”, but navigation bar shows T:\todo, and error message “The system can't find the specified path” “T:\todo”.
- Back to B:\todo
- Rename (F2) dir fc_test to fc_test2
- Crash after Enter: EAccessViolation: Access violation at address 006EAC2F in module 'FreeCommander.exe'. Read of address 00000000.
- After “Continue Application” I see the correct renamed dir.
This does not happen with other "subst" drives and not in same dir directly accessed via D:. So there may be some problem with some hard coded special handling of floppy drives!?
FreeCommander XE 2014 Build 650
Win7ult-64 or WinXP