Home »  MonTel »  appnotes »  FAQ » How to  » Server  » Old topics from MonTel Server "How to"  » How to configure Win9x computers for maximum conventional memory for running MonTel Server in pure DOS.

Next Topic

Previous Topic

Home

Book Contents

Book Index
How to configure Win9x computers for maximum conventional memory for running MonTel Server in pure DOS.

It is better to run the MonTel server on a DOS machine. Basically, windows just isn't stable enough to run for months on end, and can some times suffer problems with the Serial port and RTC which MonTel accesses directly, but more importantly is subject to the activities of other programs and drivers (and of course users). This doesn't mean that MonTel Server won't work on Windows, it is still very reliable. But you can eliminate the risks of Windows problems by using DOS!

In this example we are using an old machine that currently has Windows 98 installed, connected to an NT Domain, which we want to run as a pure DOS computer (Ver 7.1) for the MonTel Server. You could use the example almost unchanged for MS DOS 6.22. Remember that DOS 5 and earlier are not Y2K compliant.

Note: This article assumes you are converting an existing Win9x system, in which MSDOS.SYS can be edited. In real DOS the MSDOS.SYS file (or equivalent in IBM DOS or FREEDOS) is a hidden executable. Therefore only some of the points below will be applicable.

First of all you will need to acquire the DOS networking files. It is easiest to copy these while still in Window to a set up folder. Make sure you name it with only 8 characters or less, as it gets to be a bit of a pain changing directories in DOS.

The MS-DOS client is available on the older Windows NT Server CD's (Though I can't find it on Windows 2000 Server CDs) or you can still download it from:

ftp://ftp.microsoft.com/bussys/Clients/WFW

There are two significant folders at this address: the msclient folder holds the MS-Client and the lanman folder holds the LAN Manger client. I have used the MS-Client. Which is better? See ID: Q122297 Comparison of MS-DOS Clients for Windows NT Version 3.5 for the Microsoft View. http://support.microsoft.com/support/kb/articles/q122/2/97.asp?id=Q122297

See also the other references below.

Make a note of the type of network card, the interrupt and I/O address of the card, and the use of any ROM or memory.

Make sure that you can view hidden files in explorer. In the root of C:\ drive open the hidden file MSDOS.SYS

Find the [Options] Section and either edit or add the following entries:

[Options]
BootGUI=0
Logo=0

This will ensure that you boot into DOS in the first place, and that the start up screen won't be visible, meaning that you stay in text mode while re-starting. Make sure you save the MSDOS.SYS file. (You may have to changes some of the rights to do so).

Now make a copy of the CONFIG.SYS file and the AUTOEXEC.BAT file, call the backups something like CONFIG.ORG and AUTOEXEC.ORG.

Often these files are blank, or the AUTOEXEC.BAT just has a PATH statement. If so then the job has just been made a whole lot simpler.

In the example below I have used C:\NET to set up the DOS Network client, and I am using the MS-Client Microsoft Network Client for MS-DOS version 3.0. See below for details of where to find the clients, and which ones to use.

You could use almost the same settings (except for the networking parts) to set up a Netware (Novel) ODI network client. (Using Netware ODI will be a lot easier to do than the MS client.)

Now edit AUTOEXEC.BAT to look something like this:

@PATH C:\PROGRA~1\WIN98RK;%PATH%
rem {the above is just the existing path statement}
rem {Make sure that C:\windows (or what ever) is in the path}
rem {if it isn't all ready}
PROMPT $P$G
rem {Any other settings - CD-ROM, Sound card et al here as well}
rem { some times they need to go at the bottom, like MSCDEX if}
rem { installing a LANMAN client}
LH doskey
goto %config%
:dos
goto END
:netdos
@PATH c:\net;%PATH%
goto END
:netstart
@PATH C:\PROGRA~1\WIN98RK;c:\net;%PATH%
C:\NET\net initialize
C:\NET\netbind.com
C:\NET\umb.com
C:\NET\tcptsr.exe
C:\NET\tinyrfc.exe
C:\NET\nmtsr.exe
C:\NET\emsbfr.exe
C:\NET\net logon TEST1{Domain info} password /YES
C:\NET\net view
goto END
:win
win
goto END
:END
rem {Any other settings - CD-ROM, Sound card et al here as well}
rem { just to finish off correctly }

The password above and the network setting will need to be worked out later as you install/set up the network client.

Now edit the CONFIG.SYS file, most of which is new! (Cut and pasting this might be easiest).

[menu]
menuitem=win, Windows 98
menuitem=dos, MS-DOS no networking capacity
menuitem=netdos, MS-DOS with networking capacity
menuitem=netstart, MS-DOS start Network now
menudefault=4,120
[common]
DEVICE=C:\WINDOWS\HIMEM.SYS
[win]
DEVICE=C:\WINDOWS\EMM386.EXE
FILES=20
[dos]
DEVICE=C:\OLDDOS\EMM386.EXE HIGHSCAN I=D000-EFFF WIN=B500-B7FF WIN=B200-B4FF NOEMS
BUFFERShigh=16,0
FILEShigh=30
DOS=UMB
LASTDRIVEhigh=Z
FCBShigh=4,0
DOS=HIGH
LASTDRIVE=Z
[netdos]
DEVICE=C:\OLDDOS\EMM386.EXE HIGHSCAN I=A000-B7FF I=E000-EFFF NOEMS
BUFFERShigh=16,0
FILEShigh=30
DOS=UMB
DOS=HIGH
LASTDRIVEhigh=Z
FCBShigh=4,0
DEVICEHIGH =C:\NET\IFSHLP.SYS
LASTDRIVE=Z
[netstart]
DEVICE=C:\OLDDOS\EMM386.EXE HIGHSCAN I=A000-B7FF I=E000-EFFF NOEMS
BUFFERShigh=16,0
FILEShigh=30
DOS=UMB
DOS=HIGH
LASTDRIVEhigh=Z
FCBShigh=4,0
DEVICEHIGH =C:\NET\IFSHLP.SYS
LASTDRIVE=Z
[common]
rem {Any existing CONFIG.SYS entries should be here}

What we have done is set up a configuration menu where we will be prompted with

1. Windows 98
2. MS-DOS no networking capacity
3. MS-DOS with networking capacity
4. MS-DOS start Network now

when we boot up the computer, and before we run the CONFIG.SYS file. Note that the line DEVICEHIGH =C:\NET\IFSHLP.SYS will probably break windows, which is why it is not included in the Win98 boot. Note also that DEVICE=C:\OLDDOS\EMM386.EXE HIGHSCAN I=A000-B7FF I=E000-EFFF NOEMS includes all of the VGA graphics space adding another 64k of conventional RAM. You cannot run graphics programs in this configuration (including Windows or even show the logo), but the MonTel Server is a text mode only program so it will be just fine. The default menu item has been set to the last, with a two minute time out.

Now save both the files, and restart your computer. When the menu pops up select 2 MS-DOS no networking capacity. Once you get the DOS prompt do an MEM /C /P to be truly amazed!

Now the hard part: You will need set up the network client. You might want to start by setting Network=0 in the [options] section of MSDOS.SYS. Other than that, it is better left to the documentation and other's who know more about networking. DOS is pretty old now and information is hard to find, but there are still some good sources on the net

One good source might be: http://www.wown.info/j_helmig/doscltcp.htm. See also http://freedos.org/freedos/news/technote/157.html.

For a good overall discussion about this (albeit in a Samba context) see: http://huizen.dds.nl/~jacco2/samba/dos.html

You might also want to see the following knowledge base articles.

ID: Q142703 Setting MS-DOS Client 3.0 to Automatically Log On to Domain

http://support.microsoft.com/support/kb/articles/q142/7/03.asp?id=Q142703

ID: Q135465 Microsoft Network Client for MS-DOS version 3.0

http://support.microsoft.com/support/kb/articles/q135/4/65.asp?id=Q135465

ID: Q111302 Microsoft Networking Client Pack Availability

http://support.microsoft.com/support/kb/articles/q111/3/02.asp?id=Q111302

And this as well: ftp://ftp.microsoft.com/bussys/winnt/kb/Q128/7/51.TXT

Download from:

ftp://ftp.microsoft.com/bussys/Clients/WFW

---------------------------------------------------------------------------------------------------

Thanks especially to Dave Moyle at Monitor in Melbourne who got me started on this.

------------------------------