Hiya, I found a partial solution to the batch upload to FreeServe thing, although this leads to even more serious problems. To be able to batch upload I have to turn 'Send NOOPS' ON and 'Auto update' OFF. The auto update problem stops the infinite 'waiting for file list problem' and the 'send NOOPs' stops the connection being terminated, as you seem to be terminated even if you are actually uploading something :-( HOWEVER, on to the problems. In HIGH bandwidth consumption, mFTP just grinds to a halt, unlike things like YAM/IBrowse that just get slow mFTP seems to hang. If Miami goes offline any transfers going on just hang, again YAM/IBrowse will resume once your back online, mFTP doesn't. I am getting a lot of 'short write' errors. These appear in requesters. Problem, firstly the requester stops mFTP until you reply to it, hoever the requster appear on the WB screen not the public screen mFTP is running on so you don't even know they are there! Alot of the time the overwrite/resume requester is full of garbage, as though it's reading from the wrong memory address. Transfers seem to internally time out, say I select 25 files to upload. A couple or so of the bottom transfers even though they havn't started eventually get removed off the list without being uploaded. Some times transfers are not uploaded, they get added to to the transfers list and immediately dissapear off it. Does mFTP use the contents with the remote lister to work out whether a file will be over written? Bsically with Auto update off (so the right lster isn't alays upto date' I am not necessarily gettng overwrite requesters even though I should! ----- That's it for know. It took me nearly the entire of yesturday (6am - 1am) to upload 70mb. Come on get your act together, please!!! Kind regards... Alex -- Cremlin Software - http://www.cremlinsoftware.org Founder, lead programmer - [EMAIL PROTECTED] Production, programmer - [EMAIL PROTECTED]
