LAN Server Installation

** LAN Server Installation GUI ** This is a straightforward installation program for IBM LAN Server for OS/2. This program is provided "as is" in the hope that it may be useful. It has a minimalist user interface and no online help. However, it should be relatively straightforward to use, at least for administrators who are somewhat familiar with IBM LAN Server. Many of the configuration options are esoteric. If unsure, go with the default configuration, setting the server type as appropriate. By default, this program looks for the IBM LAN Server install image on the specified CD-ROM drive, under the directory \CID\SERVER\IBMLS. You can also use this program to install LAN Server from a CID server or local disk. In this case, you must copy SERVINST.EXE to the directory where the LAN Server install image is located (i.e. the same directory as LANINSTR.EXE), and run SERVINST.EXE with the /AUTO parameter. ** Installation ** Copy SERVINST.EXE to wherever you want to run it from. Copy SRVI_xx.MSG either to the same directory, or to a directory on %DPATH%. This program requires two run-time libraries: VROBJ.DLL and VROBJEX.DLL; these should be placed on the LIBPATH or else in the same directory as SERVINST.EXE. ** Parameters ** SERVINST.EXE supports only one optional argument, /AUTO. This tells it to look for the LAN Server product image in the current directory, rather than in the usual CD-ROM directory structure. ** Notices ** LAN Server Installation GUI is copyright (C) 2005-2018 Alexander Taylor. All rights reserved. This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/. The sources of servinst can be found here: http://trac.netlabs.org/vxapps/browser/projects/servinst/trunk Please note, it would be great if you do update this code you try and also submit the code in same SVN repo. This will make it easier to keep track of any updates! ** Disclaimer ** This software is freeware, it does not cost you anything. In other words this software is provided "AS-IS". You use this at your own risk! Neither the author of this tool Alex Taylor, the VOICE foundation or any of its board members can be held accountable for any form of damage. Before you use this tool you should make a verified backup of your system! ** Support ** If you have any questions about this tool or usage of LAN server for OS/2 you can send me an email to rwklein@xs4all.nl. This support is provided on an *best* effort basis. When you have ArcaOS installed with the File and Print Client, by running this installer and using a LAN server, WSeB or ACP 1/2 CD you will downgrade some files in the \IBMLAN directory to older versions. That is why should backup your system first before using this tool. In broad lines a LAN server or a OS/2 File and Print Client contain mostly the same files in the IBMLAN directory. For example the drivers loaded in the config.sys for an OS/2 File and Print Client and an OS/2 File server are the same. This tool will place some new files in the IBMLAN\SERVICES directory, such as server.exe that provides the LAN server functionality. **SMB 1 protocol and security...** One note of caution when you use the File and Print Client built into ArcaOS, OS/2 and eCS. Both File & Print Sharing and LAN use the very old SMB1 protocol. You should inform yourself of the potential security risks this protocol has, such as extremely weak password hashes! But there are also many security holes. Experts say it is better to use the SMB 2 and SMB 3 protocol; this can be achieved with the Samba server (see Netlabs: http://trac.netlabs.org/samba). These two URLs provide more information: http://news.softpedia.com/news/this-microsoft-engineer-has-a-really-good-argument-for-ditching-smbv1-508481.shtml https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/ If you run LAN server for OS/2 workstations the security risks might be lower, but this depends on the attack. If you just run LAN server in a small, local network with a properly configured firewall to the internet there should be no cause for alarm. We just thought you should be aware of these risks.