Networking under DOS

[The#Danger]

With the growing popularity of networks - now in the home - and falling prices for network hardware is increasingly desire on the older computer to integrate into existing networks as well. Since these computers are often no more modern than DOS operating system comes into question, and this operating system for many applications still insufficient, it would be the lack of network capabilities not only due to replace. There are also opportunities for DOS, network functions and even the Internet to use.

Required Software

Since DOS does not provide networking functionality itself, this software must be retrofitted external means. Microsoft has this end, the "MS Workgroup Addon" for MS-DOS to create, which is also known as "MS-Client" is known and version of MS-LanManager represents one.

You get this software under ftp://ftp.microsoft.com/bussys/Clients/MSCLIENT/ as a self-extracting archives.

• DSK3-1.EXE and
• DSK3-2.exe

These two files are in two separate directories (eg C: \ MSCLIENT \ DISK1 and C: unzip to \ MSCLIENT \ DISK2).

Since the TCP / IP support a lot of memory needed (the biggest drivers over 78 kB) it still there, tools to save some to use conventional memory for DOS and all necessary equipment, the driver with the lowest memory usage to work for. Who to connect to the DOS computer is not necessarily required TCP / IP should, instead, the "IPX / SPX compatible protocol" test, which is suggested by the installation program by default. Support for this protocol requires much less memory and configuration. I also began following drivers with minimal memory consumption:

• CTMOUSE.COM
• GERKEYB
• Cdrom.sys

Installation

Optimize memory

First one creates therefore a maximum of free DOS memory by using memory-saving drivers or omission of useless drivers. Drivers for CD-ROM drives are known for their memory hungry, are added then still plenty of time for MSCDEX.EXE 20 kB, so that one should think about drivers not to load the CD, if you want to use the network. A space-saving alternative to the previously mentioned MSCDEX.EXE offers FreeDOS Project at http://www.freedos.org/. The selection of configurations to be set up in the Start menu made CONFIG.SYS werden.Um one of the memory for uploading drivers can use to have to have a comparable or EMM386.EXE memory manager like QEMM from Quarterdeck or 386MAX.

The DOS tool MSD.EXE can display the free space can be (menu item "Memory"), all that is shown in black can be used in general. Furthermore, we obtain the values for the I = parameter, EMM386.EXE in the CONFIG.SYS. However, one must expect something for this. A box in the display of MSD corresponds to 1024 bytes and a number are 16,384 bytes or 16 kB. has to address specifications for a decimal point is omitted, the per box must however be left standing so the number 40hex.

In the example above, so I get a blank area of CD00-EFFF and from B700 to B7FF. From this address memory is displayed by the graphics card, an expansion of the memory-use EMM386 to addresses in the range of B800-BFFF is usually to crash the computer, but to display errors on screen, at least keep. At this point, is displayed under DOS, part of the VGA display memory. My row for the CONFIG.SYS, then, is

DEVICE = C: \ DOS \ EMM386.EXE I = B700-NOEMS NOVCPI B7FF I = CD00-EFFF

It is important to capitalization, as EMM386 otherwise not working properly. It should also be given the option NOEMS, or 64 kB for the so-called "EMS page frame" (page frame) will be lost there. The vast majority of programs work with XMS, so that EMS can be left off. As a further measure I clean free conventional memory a bit by / SHELLMAX parts of the system in the "high memory" can be shifted DOSMAX with:

DEVICE = C: \ UT \ DOSMAX \ DOSMAX.EXE / c + / p-
shell = c: \ ut \ DOSMAX \ shellmax.com c: \ command.com / p
DEVICEHIGH / L: 1 = C: \ WINDOWS \ IFSHLP.SYS

This driver is included with Windows for Workgroups and MS for the client urgently needed. He is also contained in the MS client.

DEVICEHIGH / L: 1 = C: \ DOS \ KEYBGR.SYS

Note the / L: 1 after DEVICEHIGH the DOS induced in the first free area of the "high memory" to load drivers it (in the example of the range of B000-B7FF). In this way I can the area between the CD00 -EFFF for large chunks of free hold.

[The#Danger]

The MS-Client

The next step will be installed the MS client. This one should make sure beforehand that one of the DOS and Windows 3.11 drivers for its network card is ready and a list written down, in which they were the driver disk is stored on. This directory should be a file with extension. DOS (real driver) and a file OEMSETUP.INF. Who uses this driver should not be surprised that only a few settings for the IRQ and I / O address are given. If your values are not selectable, helps specify the default settings (eg, IRQ 5, I / O address 300) and entering the correct values in the protocol.ini :

[MS $ NE2000]
Iobase = 0x320
INTERRUPT = 11

after completion of the installation.

Setup then asks for the "OEM Driver Disk." Now this is not yet time for the network card supplied disk, but the second of MS-client, which can, for example C: \ MSCLIENT \ DISK2 unpacked has to before. This list must be included here. After all the files have been copied, is the setting dialog, the window is divided in two between which one moves with <TAB>. In the upper window, select the cursor keys to what will be edited at the bottom of what is to be made ("Change Configuration"). By then enter the respective configuration dialog starts. We need him, TCP / IP as the protocol to add to set up and a name and the workgroup to give the computer. As Redirector choose "basic out", thus saving memory.

At this point again to note: If the TCP / IP is absolutely no need, should contribute to a tight conventional memory (the specific error messages from DOS applications) to another protocol such as IPX / SPX dodge. Support for these protocols require much less memory than TCP / IP. I have this only TCP / IP and name added to the award, it is easier to PROTOCOL.INI directory of MS-client adjusted in, as by shimmy to the setup. In this case, one must avoid that, according to exit the setup (dialing of "The options are correct") and the following computer reboot, the AUTOEXEC.BAT is processed, unless the network is a DHCP server. If such exist, you need to configure anything further. If not, you take the PROTOCOL.INI in the directory from the MS client, the section [TCPIP] should look like:

[TCPIP]
Nbsession = 6
DefaultGateway0 = 192 168 0 1
SubNetMask0 = 255 255 255 0
IPAddress0 = 192 168 0 2
DisableDHCP = 1
$ DriverName = TCPIP
BINDINGS = MS $ NE2000
LANABASE = 0

Note that the address points but separated by spaces will not be accepted. At this point the IP address can also change quickly without much effort.

Shares or DOS as a server

If one DOS computer drives, directories, or want to share the printer on, one needs the already above mentioned files or NNET.EXE WG1049.EXE These include an updated version of NET.EXE. We unpacked NNET.EXE in the directory in which the MS client has been installed and overwrites the original version of NET.EXE and NET.MSG. If there are problems with printing in the net, you should instead NNET.EXE WG1049. EXE use.

The next step is to edit the SYSTEM.INI:

• FileSharing = Yes
• Print Sharing = Yes

The program NETSHARE from the archive NETSHAR.EXE that easily into the client directory (eg C: \ NET can be extracted), can now set up the shares; <TAB> turn this around between the different input fields. Of course, the shares can be set up within batch files or from the command line, this is the command :
net share available. With net share DOSC = c: \ user is there then for example the C: \ user freely with full access, it will be visible on the web at DOSC. Other computers can be achieved with net use g: \\ dos-computer \ dosc

Network functions use

This is following in the AUTOEXEC.BAT or (like me) the separate NETSTART.BAT:

c: \ net \ net.exe time \\ small // set yes> null

This computer is the time on the DOS client with another synchronized. In order to avoid errors due to different clocks, you should permanently networked computers regularly (once daily) to synchronize with each other, for example. Is also then the daylight saving time automatically. In this way, the release of the drives on the DOS computers indispensable SHARE.EXE loaded.

c: \ net \ net.exe share / yes

Thus the set with NETSHARE shares are enabled. Who this program is not used, must adjust the command accordingly. Setting up network printers:

c: \ net \ net use lpt1: \\ printserver \ hpdeskjet / persistent: no / yes
c: \ net \ net use LPT2: \\ printserver \ hplaser / persistent: no / yes

These two programs MARKNET RELNET and are part of the TSR Utilities. The ZIP archive with the TSR utilities will simply

• md c: \ tsr
• pkunzip tsrcom35.zip c: \ tsr

a separate directory on the hard disk and unzip it in a particular installation is not necessary. So you can MS client leaving any residue from the memory to remove, even Windows can afterwards easily run itself. A performance guarantee can be given, each case should be in the United pack the TSR utilities available file TSR.DOC (no WinWord-file, but normal ASCII text) are read to do so, since it contains many useful references.

[The#Danger]

Program for MS-DOS mode, configure

Alternatively you can on Windows, a shortcut to a DOS program also create, configure it to DOS mode for ("Properties" of the program, right click, then Advanced tab) and its own CONFIG.SYS and AUTOEXEC.BAT give it. At the start of such a connection shuts down Windows, starting with the new CONFIG.SYS and AUTOEXEC.BAT loads the DOS program and will start after the end again.

DOS Startup menu

As with MS-DOS 6.22 and Windows 95/98 can be a Start menu in CONFIG.SYS to create order with different configurations to start the computer. This is the edited file C: \ MSDOS.SYS, which you read previously repealed adds and under [Options] the following:
BootGUI = 0
In the CONFIG.SYS is then for example :

DEVICE = C: \ WINDOWS \ HIMEM.SYS / testmem: off
 DEVICE = C: \ DOS \ EMM386.EXE I = B000-NOEMS NOVCPI B7FF I = C800-F7FF
 INSTALL = c: \ ut \ memstrat \ memstrat.exe 4
 DEVICE = C: \ UT \ DOSMAX \ DOSMAX.EXE / c + / p-
 DEVICE = C: \ WINDOWS \ SMARTDRV.EXE / double_buffer
 DEVICEHIGH / L: 1 = C: \ WINDOWS \ IFSHLP.SYS
 DEVICEHIGH / L: 1 = C: \ DOS \ KEYBGR.SYS
 shell = c: \ ut \ DOSMAX \ shellmax.com c: \ command.com / p
 SET PATH = C: \ WINDOWS c: \ c: \ windows \ system C: \ NET; C: \ DOS C: \ UT 
 C: \ XL c: \ ultraedt c: \ inet \ netscape \ program