On 20-Feb-00, Tim Jackson wrote:

> Hi Ken, on Sun, 20 Feb 00 at 17:01:33 you wrote...
> 
>> I'm finding mFTP that came with NC3 not as good as AmFTP that came with
>> NC2 it gets to the logging on stage then stalls at 'Retrieving directory
>> contents (so many) bytes transferred'
> 
> mFTP, whilst nicely architectured and well written in most respects (nice
> GUI, multi transfers etc.), is unfortunately bugged to hell, resource
> hungry and I'm not at all impressed. I've sent loads of bug reports to
> [EMAIL PROTECTED], have yet to see if anyone will do anything about
> them.
> 
> I'm almost tempted to ask that AmFTP be compiled to work with NC3, as I
> didn't have NC2 so I have to use the demo version of AmFTP all the time. 
> I'm not very impressed that I paid for mFTP as part of NC3 yet it is
> almost as good as unusable it's so buggy.  I tried to upload a moderate
> size website yesterday - nothing fancy, just uploading a big bunch of
> files!  It guru'd twice before I even got half way at which point I gave
> up and used AmFTP instead.
> 
> One of the very basics of an internet connection is a solid FTP client. 
> mFTP is about unstable, unreliable and has compatibility problems with
> some servers - I've had problems even with some Aminet FTP servers!


I've got to say your 100% right what with V3 and the others all needing
updates straight away to work as they should its bad. I've gone back to NC2
for some stuff like AmFTP to work as they should. I don't think I should have
got the update till it was sorted, but it could have been chicken and egg no
updates till folk buy.

But I'm going to have a play with the new stuff on NC3 like metalweb and we
shall see.
 
                 Cheers all the best

                       Ken 




  

_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>

Reply via email to