Freecommander Access Violation when running with SmartFTP
Posted: 07.04.2009, 21:46
This is VERY strange.
When I run SmartFTP and FreeCommander at the same time, I get this error 100% of the time.
To reproduce:
Run FreeCommander (2009.02)
Now run SmartFTP (actually, the order you run them doesn't matter).
Go to a remote browser in SmartFTP. In this case, I go to my VSP, and I'm looking at the file tree in my remote system.
Now, on the remote system, change a file name or folder name.
I hear a ding in the background--renaming a file on the remote system causes Freecommander to show a "Access violation at address 005B9F0A in module FreeCommander.exe. Read of address FFFFFFFF.
Why would it do that when I rename a file on a remote system using FTP? What the heck does FreeCommander have to do with that? What possible local system effect could that be having by using SmartFTP to rename a REMOTE file or folder?
It's 100% reproduceable. Every time. Probably on other systems, but I'm running Vista Home 64 bits, with 6 GB of memory on a quad processor.
According to the SmartFTP forum admin, "It's a bug with FreeCommander. SmartFTP uses the shell notify to communicate with the RemoteBrowser and it seems FreeCommander doesn't play by the rules."
When I run SmartFTP and FreeCommander at the same time, I get this error 100% of the time.
To reproduce:
Run FreeCommander (2009.02)
Now run SmartFTP (actually, the order you run them doesn't matter).
Go to a remote browser in SmartFTP. In this case, I go to my VSP, and I'm looking at the file tree in my remote system.
Now, on the remote system, change a file name or folder name.
I hear a ding in the background--renaming a file on the remote system causes Freecommander to show a "Access violation at address 005B9F0A in module FreeCommander.exe. Read of address FFFFFFFF.
Why would it do that when I rename a file on a remote system using FTP? What the heck does FreeCommander have to do with that? What possible local system effect could that be having by using SmartFTP to rename a REMOTE file or folder?
It's 100% reproduceable. Every time. Probably on other systems, but I'm running Vista Home 64 bits, with 6 GB of memory on a quad processor.
According to the SmartFTP forum admin, "It's a bug with FreeCommander. SmartFTP uses the shell notify to communicate with the RemoteBrowser and it seems FreeCommander doesn't play by the rules."