Custom Query (8035 matches)
Results (190 - 192 of 8035)
|#3406||188.8.131.52 error loading xml file filezilla.xml|
ever since I think 184.108.40.206 I get this error dialog box:
error loading xml file Could not load "C:\Documents and Settings\Jim\Application Data\FileZilla\filezilla.xml", make sure the file is valid. For this session, default settings will be used and any changes to the settings are not persistent.
the default settings as referred to are the same as what are in my xml file it looks like.
when I examined the xml file, it now contains 6k worth of spaces instead of 6k worth of xml.
essentially, something in filezilla trashed my xml file. possibly it was the upgrade process to 220.127.116.11?
|#3439||3.0.8 freezes on every ftp upload attempt|
I updated from 3.0.7 to 3.0.8, and now FileZilla freezes uploading just a single small (6kb) text file via ftp.
filezilla.exe and lsass.exe cpu usage each rise to about 8% "System" process cpu usage rises to 14%
It does not get as far as listing the upload in the queue, or logging any ftp commands related to the transfer, though it does say "queued files (1)". It's like it fails doing something with the source file, and is retrying thousands of times a second.
The text file being transferred is on a network drive (DFS) on a Samba file server. A previous version of the file exists on the destination. I'm running XP.
|#3463||18.104.22.168 won't open|
Newest version won't open on MAC G5 running OS X 10.4.11 3.0.6 runs fine