March 10th 1997 Mirror Sites ![]() Download the Software Network Card Drivers ![]() Features User's Guide Help ![]() Search Distribution Rights Listserv Shareware Links ![]() Order the Software Help Us Promote NetSoft LAN Dealer Enquires Welcome Home Page | http://www.netsoft.ie/ CHAPTER 15 Microsoft Windows Network Installation Procedures
Windows 3.1There are three ways to install Microsoft Windows 3.1 on a network. These are all briefly documented in the Microsoft Windows User's Guide. The following instructions detail these installations step by step.The three installations are as follows: Single User Installation. Network Administrators Installation. Windows 3.1 Single user installationThis is the normal Windows 3.1 installation for a single user. Before setting up this type of installation it is recommended that NetSoft LAN is not loaded. If you have NetSoft LAN loaded, re-boot your machine and hold down the CTRL+ALT keys until your machine has completed its boot sequence (NetSoft LAN will not load).To set-up a single user version of Windows 3.1, type the following at the DOS command line: a:setup Follow the on-screen prompts, but do not select a network.
The Windows Setup icon displays the following options. ![]()
Select Network to change the network setting. ![]()
![]()
![]()
![]()
![]()
When Windows re-starts it will be correctly configured to work with NetSoft LAN Computer Networks. If you wish to load Windows from a server machine rather than your local machine you must install Windows 3.1 using the other two methods. The procedure for installing a shared copy of Windows 3.1 on your server machine is explained next. Windows 3.1 Network administrators installationThe administrators installation sets up a shared copy of Windows 3.1 on a server machine. You will require about 16MB of free disk space on the servers disk. This installation expands all of the Windows 3.1 files and copies them to the servers directory. During this process all files are marked read only.To install a shared copy of Windows 3.1 type the following at the DOS prompt command line: a:setup /a This installation asks you to insert the Windows 3.1 disks one at a time, while it copies and expands all the files to the directory that you specify. When you have exhausted all the disks, press F3 twice to end the installation. If the system does not complete the installation of all the disks, an error will be displayed. To fix this problem, you must delete the *.CRC files from the Windows 3.1 installation disks using the following command for each disk: del a:*.crc The reason you must do this is because Windows makes all files read-only after copying them to the server directory, and the files that end in .CRC have the same filename on each disk, so Windows 3.11 is unable to copy the next disk to the server directory because a file by the same name already exists. If you still have problems installing all disks, you will have to install them manually using the EXPAND command on disk 1. This is explained in the Microsoft Windows User's Guide. Windows 3.1 Network user installationThis installation sets up a directory for each network user. The directory may be on the server or on the user's client machine. A shared copy of Windows 3.11 must have been previously installed on the server, as explained previously. Also NetSoft LAN must be loaded on the server and the client machines.The server machine must have also shared the server's drive that contains the shared copy of Windows using the NET SHARE command. To do this, type the following commands on the server at the DOS prompt command line: cd\dosnet net share c: Each client must then connect to the servers hard disk using the NET USE command. To do this, type the following on each client machine at the DOS prompt command line: cd\dosnet net use f: \\server1\c: The network drive used in this example is F: and the server's name is \\SERVER1 yours may be different. (The lastdrive= parameter in the CONFIG.SYS file of the client must be set to at least F, if you want to use the F: drive). To set up a Windows 3.1 network user, type the following commands on the client at the DOS prompt command line: f: cd\windows setup /n Follow the on-screen prompts, entering your user directory name. Windows 3.1 will then check your systems configuration and display a list, the last of which will be the network option: NETWORK: No network loaded Change this to the last option in the list "Other Network (Requires disk from OEM)". You will then be prompted to enter the path to the OEMSETUP.INF file for NetSoft LAN. You must specify either the server's NetSoft LAN network directory, or your local NetSoft LAN network directory. f:\dosnet or c:\dosnet Windows 3.1 will then proceed as normal, installing the files to your selected user directory. You may be required to boot the client machine so that changes made to your CONFIG.SYS and AUTOEXEC.BAT files by Windows 3.1 may take effect. Once booted, load NetSoft LAN, then connect to the server's drive using NET USE command as explained next (using the same network drive letter that you used to install the network user). Starting Windows 3.1When you have completed the network user set-up of Windows 3.1, type the following to start Windows:net use f: \\server1\c: f: cd\userdir win The userdir is the user directory you specified on the server. Remember, you must use the original network drive used to install the network user directory (F:). If you installed the network user directory on your local client's disk, type the following to start Windows 3.1: net use f: \\server1\c: c: cd\userdir win The userdir is the user directory you installed on the client's hard disk. Remember, you must use the original network drive used to install the network user directory (F:). Windows for Workgroups 3.11There are three ways to install Microsoft Windows for Workgroups 3.11 on a network. These are all documented in the Microsoft Windows for Workgroups User's Guide. The following instructions detail these installations step by step.The three installations are as follows: Single User Installation. Network Administrators Installation. Workgroups 3.11 Single user installationThis is the normal Windows for Workgroups 3.11 installation for a single user. Before setting up this type of installation it is recommended that NetSoft LAN is not loaded. If you have NetSoft LAN loaded, re-boot your machine and hold down the CTRL+ALT keys until your machine has completed its boot sequence (NetSoft LAN will not load).To set-up a single user version of Windows for Workgroups 3.11, type the following at the DOS command line: a:setup Follow the on-screen prompts, but do not select a network.
![]()
![]()
![]()
![]()
![]()
Type the network directory name (this is usually C:\DOSNET). ![]()
![]()
Choose OK to install this network. ![]()
![]()
If you wish to load Windows for Workgroups 3.11 from a server machine rather than your local machine you must install Windows for Workgroups 3.11 using the other two methods. The procedure for installing a shared copy of Windows for Workgroups 3.11 on your server machine is explained next. Workgroups 3.11 Network administrators installationThe administrators installation sets up a shared copy of Windows for Workgroups 3.11 on a server machine. You will require about 20MB of free disk space on the servers disk. This installation expands all of the Windows for Workgroups 3.11 files and copies them to the servers directory. During this process all files are marked read only.To install a shared copy of Windows for Workgroups 3.11 type the following at the DOS prompt command line: a:setup /a This installation asks you to insert the Windows for Workgroups 3.11 disks one at a time, while it copies and expands all the files to the directory that you specify. When you have exhausted all the disks, press F3 twice to end the installation. If you have any problems installing all disks, you will have to install them manually using the EXPAND command on disk 1. This is explained in the Microsoft Windows for Workgroups 3.11 User's Guide. Workgroups 3.11 Network user installationThis installation sets up a directory for each network user. The directory may be on the server or on the user's client machine. A shared copy of Windows for Workgroups 3.11 must have been previously installed on the server, as explained previously. Also NetSoft LAN must be loaded on the server and the client machines.The server machine must have also shared the server's drive that contains the shared copy of Windows using the NET SHARE command. To do this, type the following commands on the server at the DOS prompt command line: cd\dosnet net share c: Each client must then connect to the servers hard disk using the NET USE command. To do this, type the following on each client machine at the DOS prompt command line: cd\dosnet net use f: \\server1\c: The network drive used in this example is F: and the server's name is \\SERVER1 yours may be different. (The lastdrive= parameter in the CONFIG.SYS file of the client must be set to at least F, if you want to use the F: drive). To set up a Windows for Workgroups 3.11 network user, type the following commands on the client at the DOS prompt command line: f: cd\windows setup /n Follow the on-screen prompts, as Windows for Workgroups 3.11 loads you will be prompted to set up your network type. Follow the procedure outlined for "Workgroups 3.11 Single user installation" on page 211. You will be prompted to enter the path to the OEMSETUP.INF file for NetSoft LAN. You may specify the server's NetSoft LAN network directory, your local NetSoft LAN network directory or insert the NetSoft LAN Set Up 1 disk . Windows for Workgroups 3.11 will then proceed as normal, installing the files to your selected user directory. You will be required to boot the client machine so that changes made to your CONFIG.SYS and AUTOEXEC.BAT files by Windows for Workgroups 3.11 may take effect. Once booted, load NetSoft LAN, then connect to the server's drive using NET USE command as explained next (using the same network drive letter that you used to install the network user). Starting Workgroups 3.11When you have completed the network user set-up of Windows for Workgroups 3.11 , type the following to start Windows:net use f: \\server1\c: f: cd\userdir win The userdir is the user directory you specified on the server. Remember, you must use the original network drive used to install the network user directory (F:). If you installed the network user directory on your local client's disk, type the following to start Windows for Workgroups 3.11: net use f: \\server1\c: c: cd\userdir win The userdir is the user directory you installed on the client's hard disk. Remember, you must use the original network drive used to install the network user directory (F:). Windows TipsIt is recommended that Windows for Workgroups 3.11 is used, rather than Windows 3.1.The DOS SHARE.EXE command must be loaded on the Windows server, but does not need to be loaded on the client. Before installing Windows make the necessary changes to your memory manager to exclude the network card's DMA memory segment. Once Windows is running, an extra icon will appear in the Control Panel with additional options. Window's File Manager allows you to connect to network disks using network names. Window's Print Manager allows you to connect to network printers using network names. Any network connections made prior to running Windows will remain, unless you change them with the File Manager, or Print Manager. Make sure that you have enough files specified in the servers CONFIG.SYS file, or Windows may not load and display 'Unsupported: DOS version'. If you require more than 255 files on the windows server machine, you will have to run the NETFILES.COM program. This program allows up to 10,000 files to be opened on a server. It is recommended that you load the NetSoft LAN server disk cache program on the server machine as this improves network throughput. The NetSoft LAN disk cache program is called NETCACHE.COM and can be found in your C:\DOSNET directory. Each Windows user will have their own user directory. This directory contains 25 to 30 files. Each user must start Windows from their own user directory, using the network drive that was originally used when setting up the Windows network user directory. For example: f: cd\userdir win The DOS PATH must include the network user directory and the Windows server directory. Read the following files in the Windows server directory once you have started Windows: NETWORK.WRI Contains general information for network users. SYSINI.WRI Explains the parameters for SYSTEM.INI file. WININI.WRI Explains the parameters for WIN.INI file. The OEMSETUP.INF FileWhen you install NetSoft LAN with Microsoft Windows, you will be prompted to supply the OEMSETUP.INF file. This file is used by Windows to configure specific settings in your SYSTEM.INI file. The contents of this file is as follows:Contents of OEMSETUP.INF file for Microsoft Windows ;NetSoft LAN Version 1.40a ;OEMSETUP.INF file For Windows 3.1 & WFW 3.11 [MultiNet] nslans ="NetSoft LAN as Secondary Network",0x8030,0,0,nslan_140,0x0030 [network] nslan =,"NetSoft LAN as Primary Network", ,,,nslan_140 [nslan.versions] xx000000="Version 1.40a",,,,,,1,nslan_140,0x8030 [nslans.versions] xx000000="Version 1.40a",,,,,,1,nslan_140,0x8030 [nslan_140] warning=2 system.ini=386Enh,TimerCriticalSection,1000 system.ini=386Enh,PSPIncrement,5 system.ini=386Enh,UniqueDOSPSP,TRUE system.ini=386Enh,ReflectDosInt2A,TRUE system.ini=386Enh,INT28Critical,TRUE system.ini=386Enh,InDOSPolling,TRUE system.ini=386Enh,VirtualHDIrq=off system.ini=Standard,Int28Filter,1 system.ini=Standard,NetHeapSize,8 win.ini=network,NoQueryPrinter,1 [nslan_140s] warning=2 driver=1:wfwnet.drv driver=8:msnet.drv system.ini=386Enh,TimerCriticalSection,1000 system.ini=386Enh,PSPIncrement,5 system.ini=386Enh,UniqueDOSPSP,TRUE system.ini=386Enh,ReflectDosInt2A,TRUE system.ini=386Enh,INT28Critical,TRUE system.ini=386Enh,InDOSPolling,TRUE system.ini=386Enh,VirtualHDIrq=off system.ini=Standard,Int28Filter,1 system.ini=Standard,NetHeapSize,8 win.ini=network,NoQueryPrinter,1 All these settings are explained in detail in the NETWORKS.WRI file supplied with Microsoft Windows 3.1 and Microsoft for Workgroups 3.11. If for some reason this file gets lost or damaged, you can recreate it by copying the above sample file to a new text ASCII file. The filename OEMSETUP.INF must not be changed. [Table of Contents] [Home Page] | |
![]() | ![]() | ![]() |