Paolone,

Cheers for the name change, it will end the confusion of people thinking you need VMW. Put me on the beta tester list!

Steven

Cheers to that name change. I guess it wasn't an easy decision, but the right one. :cheers:

VmwAROS 1.1 will be called Icaros Desktop 1.1 and will be released soon. I'm sorry if this anticipated and waited update has been delayed of a little, but there are many things happening in the AROS development which suggest to wait some days more. I can only confirm that works on Icaros Desktop 1.1 never stopped and I'm close to release a internal beta testing version. Once approved, it will be released.

Suppah has given Michal permission to add MarranoFTP to AROS's contrib tree, so hopefully sometime soon it will be on the nightlies.

Quote:

Done.
http://archives.aros-exec.org/index.php?function=uploads

In the meanwhile I have updated FileZilla for Windows at least a couple of times. Maybe my issues arise due to the client, not the server (just haven't thought that).

That's strange... I haven't changed anything in the server's networking code for a very long time. All that's been done is changing the address detection routine (the DHCP issue) which is only called upon initialization and is not part of the server's networking core/engine. I suspect two things. The first thing is the default timeout time for the clients (a couple of seconds may be enough if the file system is slow, emulation maybe). The default timeout time for the version in the archives is 300 seconds, which should be plenty. The other thing is if something in AROS has changed.

The server will disconnect if timeout time elapses.
The server will disconnect upon network error (TCP/IP stack error etc) on that client connection or on the server side.
I don't think that the server will disconnect if for example a protected file is requested (outside the users root drawer for example). The server will in that case reset the path variable to a safe value. However, this may confuse the client on the next call (the client assume one path which doesn't aggree with the server's path), the client may disconnect for that reason. This is a common behaviour for FTP clients/servers (it's not easy to cope with the broad range of different client behaviours).

How frequent is it? How frequent was it before?
I have not had any problems myself with the YAFS available in the archives and 1.0.2.

Quote:

I don't think so, however I noticed that latest YAFS tends to disconnect the clients more often than in the past.

Are there any compatibility issues with Yet Another FTP Server (YAFS) or Snug HTTP server and AROS? If we loose MarranoFTP the FTP server becomes even more important when transferring large amount of files. I do have time to recompile them but not much more atm. As far as I know, YAFS is working (excpet that buffering needs to be implemented to minimize disk activity). Snug HTTP server is working but there are some other minor issues (no security issues afaik). I will fix this sometime in the future but not right now :)

By the looks of it, might be that VmwAROS will continue to supply most of these apps (except that they will be updated - hurrah!)