Custom Query (8117 matches)

I recently noticed that a .txt file from a Unix machine was download as binary to a windows machine, even though "txt" is in the ASCII file list. The file is named like filename.20091204.165157742.txt. I am guessing that the reason for this is because it sees the text after the first "." as the extension and not the text after the last "." as the extension. I would contend that only the text after the last "." should be looked at for the extension. This is consistent with how windows works (don't know about other OSes).

I use a media player that uses an .xml file for the playlist. I tried uploading three instances of the player to some webspace last evening. None of the three would work. I have another instance of the player on the space that I had uploaded probably with a 2.xx version of FileZilla. I finally traced the problem down to the playlist which is an .xml file. When I was reasonably certain that the problem was with the .xml file I got FireFTP and uploaded my playlists with that program. The players all work with playlists uploaded with FireFTP. I have two computers and I tried with both computers. To check I uploaded the files using FileZilla 3.0.10. All the players broke again. Reuploading the files with FireFTP fixed the players again.

My Computers both run Windows XP Home OS. They are Core 2 Duo computers with 2GB of ram. I had version 3.0.5 running when I first encountered the problem. I checked for updates and updated to 3.0.10. I have attached one of the .xml files. I did not download one of the broken ones to compare.

Hello,

In version 1.8 the directory is always ending with a "/". That is not allowed on an OpenVMS system. On that system the directory is ending with a "]" (without quotes).