What is MSS?


MSS is an abbreviation for Martin's Server Suit which currently consist of Yet Another FTP Server and Snug HTTP server. Yet Another FTP Server will be called YAFS from now on. Although YAFS and Snug HTTP server can be used independent of each other, they function very well together to run and maintain a small web site. MSS is a way of distribute them both in a single package. MSS and its components can run on old operating systems such as Microsoft Windows for Workgroups and OS/2 Warp 3 as well as on more recent releases. MSS can bring your old hardware and software back to life again!

MSS on AROS


The default configuration for AROS is a little bit different then for other operating system. For YAFS, User AROS exists in the accounts directory and will have full access rights! Use user AROS for testing the AROS port of YAFS.

Step-by-step setup guide for setting up snug HTTP server


This guide is a simple step-by-step setup guide for setting up Snug HTTP server. This guide assume you are running Microsoft Windows 95 or later. However, it is good reading for other users as well. Few details are given so just follow the guide and the server should be up and running within a few minutes.

1. Make sure you are located in the MSS/Snug/bin/Win32-i386 directory.

2. Open snug.ini, you should be able to just double-click on the file to open it with the default application.

3. You can skip this step if you are running Microsoft Windows, OS/2 or using only one network interface card. Otherwise, locate the parameter Address. The default value should read AUTO. Change AUTO to whatever your real IP address is. The IP address can be found in your network settings. Microsoft Windows should be able to automaticly determine the first valid IP address on your system.

4. Locate parameter ExternIP, which will be your public or WAN IP address. Enter the public IP address instead of AUTO, which should be the default value. If you are uncertain what your public IP address is leave ExternIP as it is and continue to the next step.

5. Now locate the last AddVirtual parameter in snug.ini. There should be only one uncommented AddVirtual in snug.ini as default. The AddVirtual parameter should be located near the end of the file. AddVirtual tells the server where the web root is located. The web root holds all documents and files that you wish to make available on the network or the Internet. The default value of the parameter AddVirtual is /;c:, which tells the server to use c:\ as the default web root. This is not a very good choice as c:\ usually holds the operating system files. Change c: to the directory you wish to use as the default web root directory. The full searchpath must be specified. Also make sure to keep /;. If you are running a GNU/Linux-style operating system you may want to use something like AddVirtual=/;/home. AROS users must use a sub-directory such as sys:www/. You can add more than one web root directory with additional AddVirtual statements. See the instruction manual on how to do this.

6. Now save and close snug.ini.

7. Make sure your firewall settings allow traffic and server action on port 80.

8. You are now ready to run Snug HTTP server by double-clicking on SnugW32.exe.

9. Read more about Snug HTTP server here.

Step-by-step setup guide for setting up YAFS


This guide is a simple step-by-step setup guide for setting up Yet Another FTP Server. This guide assume you are running Microsoft Windows 95 or later. However, it is good reading for other users as well. Few details are given so just follow the guide and the server should be up and running in a few minutes.

1. Make sure you are located in the MSS/YAFS/bin/Win32-i386 directory.

2. Open yafs.ini, you should be able to just double-click on the file to open it with the default application.

3. You can skip this step if you are running Microsoft Windows or OS/2. Otherwise, locate the parameter Address. The default value should read AUTO. Change AUTO to whatever your real IP address is. The IP address can be found in your network settings.

4. Locate parameter ExternIP, which will be your public or WAN IP. Enter the public IP address instead of AUTO, which should be the default value. If you are uncertain what your public IP address is leave ExternIP as it is and continue to the next step.

6. Now save and close yafs.ini.

7. Change current directory to the accounts directory.

8. If you are not using Microsoft Windows for Workgroups 3.11, you can remove WFW311.ini and continue to the next step. If you are using Microsoft Windows for Workgroups 3.11, you can instead remove anonymous.ini and keep WFW311.ini. anonymous.ini and WFW311.ini only differs by their names. Microsoft Windows for Workgroups 3.11 can only handle filenames with the 8.3 format hence the name WFW311.ini. The next step assume that you are running a something else than Microsoft Windows for Workgroups 3.11 and are using anonymous.ini.

9. anonymous.ini is the default account on this FTP server. The user anonymous don't require a password upon login but will only have read permissions on the server. anonymous is the user's name. Change the name of the file to reflect the user's login name and then open the file in a text editor such as Notepad or Wordpad. Note that you can only use a-z, A-Z, 0-9 and _ for the user name.

10. Decide for the user's password and type it as a value to parameter PassWord. The default password setting should be set to no password, which is indicated by no value to parameter PassWord.

11. RootDirectory sets the user's FTP root directory. The default root directory is d:. GNU/Linux users may want to use /home/ instead. The full searchpath must be specified. AROS users must use a sub-directory such as sys:www/.

12. The user configuration is read-only as default. Change this by uncomment AddCommand=DELE, AddCommand=MKD, AddCommand=RMD_RECURSIVE, AddCommand=STOR ,AddCommand=APPE, AddCommand=RNFR and AddCommand=RNTO. This will give the user full access rights in the users FTP root directory. 13. Now save and close the account file. Copy the default user account and use the above procedure to create additional user accounts. Then go to the parent directory.

14. Make sure your firewall settings allow traffic and server action on port 2121 and port 6666 through 6676.

15. You are now ready to run YAFS by double-clicking on the appropriate executable.

16. Read more about YAFS here.