Hi,
I have just downloaded and installed Core FTP on a laptop running Vista. In the local window, I keep getting the message 'Invalid local directory'. I cannot work out why this is happening. It happens on some directories and not others, and happens on directories that I have previosuly been able to get into. I run the propgram by right-clicking on the .exe file and running as administrator.
Many thanks,
Graham
PS This is a brand-new PC and a new download of Core FTP.
Problems with Vista
I am having the same issue when you click on files in the local directory window I get an INVALID LOCAL DIRECTORY message. If I use the Drive/Folders button I can navigate to the files I want.
The top blank folder in the local directory window works fine to go backwards thru the directory. But if you click a folder after going backwards you can not access it thus getting the INVALID LOCAL DIRECTORY message.
The image attached shows the error when I click on Documents and Settings.
Also you can not rename folders or delete files in the local window.
I am running Vista.

The top blank folder in the local directory window works fine to go backwards thru the directory. But if you click a folder after going backwards you can not access it thus getting the INVALID LOCAL DIRECTORY message.
The image attached shows the error when I click on Documents and Settings.
Also you can not rename folders or delete files in the local window.
I am running Vista.

I did what you said and it sort of helps a little, but if you still use the local directory window to back up one level from users to the c: directory you can not re access the the users when you try to go forward.
I can use the drives button to navigate anywhere.
The problems seems to be in the local directory window.
I can use the drives button to navigate anywhere.
The problems seems to be in the local directory window.
Problems With Vista
Was this issue resolved? I just downloaded the software on a laptop running Vista and have the same problem as everyone else.
Any resolution?
I am having same problem here.....
Using 2.0 build 1539
Using 2.0 build 1539