A user had Core FTP Lite installed, but needed some features from the WS_FTP application, so we installed it and that has become the default FTP program. We recently used the CoreFTP .msi package to upgrade to the latest CoreFTP (ver 1.3c build 1447.4) and it appears that CoreFTP has taken over as the default FTP client for that PC. The user accesses some Office docs (Excel, etc) from the Office app (File -> Open -> FTP Locations) and this has been working fine. With the Core FTP upgrade, the user new gets the small Core FTP popup screen titled 'Transfer file(s) with CoreFTP?' with options Yes, Always, No, Save As, View/Exec, Edit, Cancel. None of these options work except Cancel. Questions:
1 - How does one change the Windows default to a different FTP client? I saw no settings within CoreFTP, nor in Windows. The only registry key I found was a coreFTP one called DefFTP.
2 - Any idea why none of the options on the 'Transfer file(s) with CoreFTP' popup work from a Office app? Opening CoreFTP directly and accessing the ftp sites and files does work ok.
Changing Windows default FTP client; and Transfer file popup
Thanks for the help, I was able to disable Core FTP as the default browser. However now if I go to ftp.microsoft.com, I get a continuous stream of new IE windows popping up. I've tried the two settings in IE for configuring either Standard or Passive FTP mode, but this does not help. I was hoping to make IE the default for FTP is the user did not want to use Core FTP. Any ideas?
The multiple windows popping up when CoreFTP has been turned off as the default FTP client appears to be a setting within CoreFTP because if we uninstall CoreFTP then IE opens up text files from FTP sites just fine. We installed the latest CoreFTP LE 1.3c build 1447.5 and I think it works better, but we need the .msi file. So any idea on what CoreFTP is doing to IE to generate the multiple windows when it is not the default FTP client? And when it is the default, we get the small CoreFTP tan window and if we choose to open using CoreFTP we get a IE window with an error and CoreFTP does not open. So there seems to be some problems between CoreFTP and IE. Any ideas?
Thanks for the updated .msi file!
We originally installed CoreFTP LE on some PCs using the .msi file last fall (or perhaps we used the non-msi version on our original PC image, can't remember). In early June we ran an updated version of the .msi file so it gets installed thru the server. The PCs run WinXP Pro. This may have been a problem since day one, not sure. One of our users had an Excel spreadsheet setup to edit it from our FTP site, so this worked well...it all occurs within Excel and a small login screen to our FTP server (no IE, no CoreFTP, no WS_FTP Pro). After the CoreFTP upgrade he started getting the CoreFTP small tan screen with buttons and none of them worked to open up his Excel file. Since he insists on using WS_FTP Pro, we assumed that this last CoreFTP LE install must have setup CoreFTP as the default FTP client, or somehow interferred with the WS_FTP Pro settings, or some other Pc FTP settings. So we found out how to turn off the browser integration in CoreFTP and when we do this, the Excel file still does not open. But also, if we use IE to go to an FTP site and double click on a text file, we get the multiple IE windows, like it is shelling out to something. The title bar however does not list the full path and file name, so perhaps this is part of the problem. If we uninstall CoreFTP, then IE successfully opens the text file within the browser, and the Excel file also opens ok. We also made sure that WS_FTP Pro has its browser integration disabled. So it seems that the upgrade of CoreFTP LE caused this since we can have the .msi file reinstall CoreFTP and observe the same problem again.
We originally installed CoreFTP LE on some PCs using the .msi file last fall (or perhaps we used the non-msi version on our original PC image, can't remember). In early June we ran an updated version of the .msi file so it gets installed thru the server. The PCs run WinXP Pro. This may have been a problem since day one, not sure. One of our users had an Excel spreadsheet setup to edit it from our FTP site, so this worked well...it all occurs within Excel and a small login screen to our FTP server (no IE, no CoreFTP, no WS_FTP Pro). After the CoreFTP upgrade he started getting the CoreFTP small tan screen with buttons and none of them worked to open up his Excel file. Since he insists on using WS_FTP Pro, we assumed that this last CoreFTP LE install must have setup CoreFTP as the default FTP client, or somehow interferred with the WS_FTP Pro settings, or some other Pc FTP settings. So we found out how to turn off the browser integration in CoreFTP and when we do this, the Excel file still does not open. But also, if we use IE to go to an FTP site and double click on a text file, we get the multiple IE windows, like it is shelling out to something. The title bar however does not list the full path and file name, so perhaps this is part of the problem. If we uninstall CoreFTP, then IE successfully opens the text file within the browser, and the Excel file also opens ok. We also made sure that WS_FTP Pro has its browser integration disabled. So it seems that the upgrade of CoreFTP LE caused this since we can have the .msi file reinstall CoreFTP and observe the same problem again.