With Filezilla not working on XP, is this XP SP3 fully patched?
I used Filezilla years ago and it worked well, but it was short lived on my XP system. Instead I chose to switch to Linux for better security with my FTP box. I then used PuTTY and WinSCP to interact with it.
I ran into a recent nightmare with a XP system that i got for free that I decided to set up for offline gaming. But it just had its wimpy integrated intel graphivs so I added a better video card. So I needed a driver for my geforce 9800 GT that I added to it and so I selected the download for XP at nvidia's website. Next I found out that the driver needed a bunch of dependencies met before it would install & run such as:
Windows Imaging Component ( WIC_x86_enu ) needed to be downloaded and installed for XP
then .NET 2.0 installed
then Windows Installer 3.1 installed
then Service Pack 3 Redist installed ( in which Microsoft no longer offers SP3 and tells you to get Windows 10 and that XP is no longer supported and I had to get it from MajorGeeks for a file named WindowsXP-kb936929-sp3-x86-enu_c8147...... long chain of alpha numeric characters in file name here of 324MB in size.)
then .NET 3.5 installed
then the driver install for the video card finally started, but then warned that .NET 4.0 is not detected, but by which I was able to get it to install anyways
Got my XP gaming rig running and saved a copy of all the drivers and dependencies for the Geforce 9800 GT video card, especially SP3 since Microsoft no longer offers SP3 for download which is pathetic that I had to get this from a questionable source such as MajorGeeks. Luckily no viruses detected and this box is offline use anyways so.
Additionally to mention, this system when trying to get all updates online, it failed to get security updates from Microsoft so they really have pulled the plug on it I guess. But manually installing the offline installer versions of updates seems to work.
Lastly.... there are a number of programs out there that refuse to install to XP with their current versions that test what OS is running before allowing install and have a message that XP is no longer supported. I found ways around this if this is the case by expanding the contents of the software on a Windows 7 build and then copying the folder contents of the program in its expanded form to my XP system and the software ran fine when launching the EXE for the software on the system because only the installer or expander tested the OS version and the software itself didnt and was happy as a 32-bit application in a 32-bit environment. * Note: This only works if no registry entries are associated with the program. If it has hooks in the registry then I suppose you could manually construct the registry entry dependencies but it would probably be a great pain to have to manually construct the registry entries to support it.