ASCII file list always is empty

Hello,

although you told smartFTP would come with a great list of ascii files, i always see only one (*.pl) extension listed. Seems this is related to x64 Edition of XP not of your x64 build (it was the same when i used the 32bit build of smartFTP).

Where do you store those settings, in the exe-file? I did save the application data, but those settings were lost after resetting the OS image.

Is there no way to enter them more handy than typing each time every extension again to the list?

By the way this is the only bug i could produce on 64bit OS by now, thanks for a great job you did!!!

kind regards

peet

thanks for your fast reply....seems we should support you too

could you post your ascii file listing to me please?
thnx a million by now

It's not recommended to use any other extension than .pl in the ASCII list. Setting the transfer type to ASCII doesn't allow to resume and it doesn't offer you any benefits over binary transfers.

that's not true, if you upload scripts on webservers it is essential to use ascii mode for most textfile otherwise your formatting is gone and you won't be able to read em in a normal manner anymore

Let's face it: Most webservers run under Un*x-like OSes, i.e. they use Un*x-style line-feeds in text files. Transfering scripts in ASCII mode is only useful if your local machine runs under Windows, which uses DOS-like line-feeds *and* you use an old-fashioned text editor that cannot handle Un*x-style line-feeds, so the text files get converted when transfered. This should very rarely be the case. It is highly recommended that you use a professional text editor under Windows which can handle Un*x files, and always use binary mode to transfer files. There are tons of (very) good freeware / Open Source editors around capable of doing this (Google for Context, PsPad, jEdit ...).

hm that's maybe true, as i deal with this windows - unix problematic for over 20 years now i might have forgotten to think about it really. it's an old routine, to be honest, as i read your answer i thought about it once more and i use Context (too since several years now) for editing my scripts and it handles those files transparent, you're right it#s just the old routine to configure everything right, as those *little* details later prevent an efficient error search, cos nobody remembered the asci converting when debugging the script lateron.

okay I take everything back and claim the opposite.


where is the problem with the pl filess then

where is the problem with the pl filess then  :?:

There is none. There is no reason why .pl files are added by default, and e.g. .php files are not. It's just an example. Just don't care, as you're using binary mode now

thanx a million for wakin me up


by the way boys out there if you read this, - a this fast and friendly support for unregistered users is rarely found!

too there is no ftp program at the moment with native 64bit support exept SmartFTP

and without the need of installation is even more rarely (like LeechFTP which was cult, but got out of time because of ftp protocol standards and Os developments)

it is small - handy - fast, at the moment i don't see why anybody should use other stuff

and the more it is offered completely free !

what else do you search for? better go, get and buy their stuff if you can afford, it's even cheaper than other apps, and these guys know what they're doin!

peet

Hello ..

Regarding the .pl extension. In the past Perl didn't (or still doesn't) like files with CR LF at the end of the line on Un*ix. Files with such line endings failed to run. PHP on the other hand doesn't care about the line endings.

Regards,
-Mat