On 5/31/2011 6:55 AM, Ulrich Hansen wrote:
<snip>
> I think users will like that your server takes good care of the data
> and doesn't loose or damage them. This is an important thing. On the
> other hand, most people will connect to the FTP server from more
> popular operating systems than DOS. So it is likely they use long
> filenames. A server that gives them the option to automatically
> truncate the filenames to 8.3 would spare them the work of renaming
> the files by hand.
A server configuration setting to truncate filenames is possible.
Another possibility would be to use the built-in support for long file
names that Open Watcom has. I believe that Open Watcom added LFN
support in version 1.9, but I have not tried it yet.
<snip>
>
>>> 4. If I try to copy a file that already exists on the server, ftpsrv
>>> responds with "553 File exists already" which causes Filezilla to stop
>>> the transfer and say "Critical error". By default Filezilla should
>>> open its dialogue window which asks if I want to overwrite, rename or
>>> keep the duplicate on the server.
>>
>> Well, the file does exist. The proper action is to delete the file on
>> the server first, and then start again. I could be wrong but if the
>> ftpserver just clobbered files (overwrite) without complaining that
>> would lead to more problems with partial files overlaying good ones.
>
> Normally there is a Filezilla dialog box, that deals with the problem.
> As I understand it, the solution works like this: When a file already
> exists on the server, Filezilla should get a notification about that
> ("File exists already"), open that box and then either abort the
> upload, rename the file or order the ftpserver to replace the file.
>
Ok, we will have to find out why the dialog box is not appearing. It
might not like the return code (553) that I am providing.
>>> BTW I have updated the mtcp files in the virtualbox image at
>>> http://lazybrowndog.net/freedos/virtualbox/
>>>
>> Thanks! I refer people to that fairly often - it is a good FreeDOS and
>> networking sampler.
>
> Yes, I put a lot of effort in it. It should people help to try out DOS
> networking without having too much work with it.
>
> Now that mTCP is Free Software, I think the next version of FreeDOS
> should focus on getting basic networking abilities.
>
> kind regards
> Ulrich Hansen
Well, relatively free. A certain group of people are aghast that I used
GPL v3 - apparently that is not free enough for them. I'm getting a
good laugh out of that conversation though.
My understanding is that the FreeDOS distributions already come with
quite a bit of networking software included. Looking at the list, the
only downside that I can see is that quite a bit of it is getting old
and there are so many authors that there is no consistent look and
feel. (And mTCP just adds to the second problem now.)
Regards,
Mike
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
