I ran in to a small issue when checking ftp under Windows/64 :
220- *** Mystic Alpha6 test ftp ***
220
502 Command not implemented.
User (livingroom:(none)): bcw142
331 User name okay, need password.
Password:
230 User logged in, proceed.

ls

200 Command okay.
150 File status okay; opening data connection.
226 Closing data connection.

cd

Remote directory fsx_info
250 Working directory is now "/fsx_info"

ls

200 Command okay.
150 File status okay; opening data connection.
DNET1016.ZIP
fsxinfo.zip
fsxnet-usenet.zip
RETRONET.ZIP
VKRADIO.ZIP
226 Closing data connection.
ftp: 76 bytes received in 0.00Seconds 76000.00Kbytes/sec.

It doesn't show directories in c:\mystic\files, only files under directories. At least that's what I've found. I have all the normal fsx directories as
lower case, so perhaps there is a case issue for directories? As you see
there is no case issue for files.

--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: BetaTest bcw142.zapto.org:2323 (21:1/145.4)

It doesn't show directories in c:\mystic\files, only files under directories. At least that's what I've found. I have all the normal fsx

LS is not a function of FTP.

You are describing the difference between NLST and LIST and Mystic is doing what its supposed to be doing.

--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/26/17, g00r00 said the following...

It doesn't show directories in c:\mystic\files, only files under directories. At least that's what I've found. I have all the normal f

LS is not a function of FTP.

You are describing the difference between NLST and LIST and Mystic is doing what its supposed to be doing.

It was only responding to LS at the time, not ls. I see you did fix that as it's working now, just an odd case problem. Now cured in the newer alpha.

--- Mystic BBS v1.12 A36 2017/11/27 (Linux/64)
* Origin: Workpoint (21:1/145.3)

LS is not a function of FTP.

You are describing the difference between NLST and LIST and Mystic is doing what its supposed to be doing.

It was only responding to LS at the time, not ls. I see you did fix that as it's working now, just an odd case problem. Now cured in the newer alpha.

Once again, LS is not a part of FTP. That is in your FTP client not the FTP protocol that is doing whatever it does with that command. There have been no changes to the FTP server since it was added into MIS2. :)

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/28/17, g00r00 said the following...

LS is not a function of FTP.

You are describing the difference between NLST and LIST and Myst doing what its supposed to be doing.

It was only responding to LS at the time, not ls. I see you did fix t as it's working now, just an odd case problem. Now cured in the newer alpha.

Once again, LS is not a part of FTP. That is in your FTP client not the FTP protocol that is doing whatever it does with that command. There
have been no changes to the FTP server since it was added into MIS2. :)

OK, so the client on my end did something odd, likely with keymaps for
unknown reasons that have been cleared as it all works fine now. Right now everything is working including telnet, rlogin, ssh, binkp, ftp, and nntp on this system all under mis2. I compiled the cryptlib a number of times, but found I had done it right, something else had gone wrong a few times with
that as well. Anyway it's all running with nodespy doing ssh and rlogin fine
as well. I only have the telnet open to the world at present, everything else is internal only for testing, but all working.

--- Mystic BBS v1.12 A36 2017/11/28 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)