home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
WINDLR.FAX
< prev
next >
Wrap
Text File
|
1994-11-27
|
8KB
|
223 lines
Standard Windows and DLR Configuration 9/21/94
WINDLR -- STANDARD WINDOWS AND DLR CONFIGURATION
DESCRIPTION OF SYMPTOMS:
There are a number of common configuration problems that occur
with WINDOWS and DOS LAN REQUESTER. Most of these problems are
created during install, although they may not show up for some
time or until the user does something new.
SUMMARY OF RESOLUTION:
It is very easy to have DLR and WINDOWS running and to have a
problem and not be aware of it. So with any WINDOWS problem
we always check the following INI files first.
DETAILS OF RESOLUTION:
DOSLAN.INI
1. The following switches must be in the DOSLAN.INI file, /NMS:2,
/NVS:n, and /API. In the /NVS:n parameter, n is the number of
servers in the domain, whose shared resources Windows may
"browse." This number is generally set to the number of servers
in the domain with a minimum of 2. THE DOSLAN.INI FILE IS LOCATED
IN THE DOSLAN SUBDIRECTORY ON THE WORKSTATION. Without these
switches, full network functionality can not be assured.
2. If the customer wants to receive messages he must have the
/POP switch in DOSLAN.INI The /POP switch starts MSGPOPUP.EXE at
the workstation so DLR can receive popup messages. The customer
must also have LOAD=WINPOPUP in the WIN.INI file. The WIN.INI
file is located in the WINDOWS directory. (See WIN.INI)
3. Make sure that RCV is selected in DOSLAN.INI if the customer
wants to receive messages. The first line of DOSLAN.INI should
read:
RCV MACHINENAME DOMAINNAME
WINSETUP
1. The Windows SYSTEM.INI also needs some modification to run DLR.
This can be done manually or by running WINSETUP.EXE while in
Windows. Running WINSETUP from the Windows program manager is
the preferred method of making these changes. To run WINSETUP
complete the following steps. NOTE: WINSETUP is in the DOSLAN
subdirectory and is part of DLR code.
a. From the Windows program manager menu bar, select FILE. You
can click on file with the mouse or use the ALT key to
activate the menu bar and then use the down arrow key to get
the pull down menu.
b. Down arrow to highlight RUN and press enter or use mouse to
select RUN.
c. A dialog box will appear asking for a command line.
d. Enter the following, "C:\DOSLAN\WINSETUP.EXE" where c: is
the drive where the DOSLAN directory can be found and DOSLAN
is the name of that directory. The above example works
unless the user renamed is DOSLAN directory or installed it
on a drive other than c:, such as d:\dlr7000. The process
would be the same, you would just enter
d:\dlr7000\winsetup.exe.
e: WINSETUP will run, the user won't be asked for any more
input but will receive some messages, and be returned to the
Windows desktop.
2. To verify:
a. EXIT WINDOWS and DOS LAN REQUESTER. RESTART DLR and
WINDOWS.
b. From the main group select CONTROL PANEL. You will see a
number of icons, select NETWORK. If the network icon is
not there and you have restarted Windows, WINSETUP has
failed.
c. After selecting network you should see NETWORK - DOS LAN
REQUESTER WINDOWS. If you do not, WINSETUP has failed.
3. If WINSETUP has failed, go to the main group, select the
WINDOWS SETUP icon. Make sure that is says NO NETWORK
INSTALLED, if it does not, then select it. Now run WINSETUP
from the program manager as before, and watch for any error
messages.
SYSTEM.INI
1. Windows has a SYSTEM.INI file that it uses at start up. This
file is modified by the WINSETUP program. The following shows
you what WINSETUP adds, with one exception. That exception is
in the Enh| section and relates to memory management. The
emmexclude and emmpageframe are not added by WINSETUP. These
are only needed under certain configuration setups or hardware
conditions.
2. The boot| section contains a list of modules or drivers that
Windows uses when starting. Somewhere near the top of the
boot section you should see the following.
boot|
network.drv=lansrv.drv
3. The boot.description| section contains a list of devices that
can be changed when running SETUP. This is the Windows setup
program not DLR's.
boot.description|
network.drv=IBM OS/2 LAN SERVER
4. The Enh| section contains special information that Windows
needs when running in 386-enhanced mode. The mode Windows
runs in is selected when Windows is launched and 386-enhanced
is default. Standard mode is Windows other operating mode and
is used for 286 machines or machines with less than 2 MB of
memory. Information for Windows memory usage is also located
here. The emmexclude is very important in nonmicrochannel
machines and in some cases microchannel machines. The
emmexclude is the adapter ROM address and should be the same
exclude in the emm386.exe statement in the workstation's
CONFIG.SYS. If expanded memory is used and a page frame is
specified in the CONFIG.SYS, then the emmpageframe should also
be included in the SYSTEM.INI file.
Enh|
network=*vnetbios,*dosnet
emmexclude=d800-dfff
emmpageframe=c000
NETWORK FILES
1. To do network tasks like displaying servers, browsing
resources, Windows requires the use of network application
program interfaces, better known as API support. This API
support comes from three dynamic link libraries and one
driver. The DLL's are NETAPI.DLL, PMSPL.DLL, WINDLR.DLL, and
the driver is LANSRV.DRV. Windows has its own version of two
of these files, NETAPI.DLL AND PMSPL.DLL. Sometimes customers
may have these files in the Windows system subdirectory. If
they are there, then they must be renamed. Have the customer
do a directory listing as follows: DIR
C:\WINDOWS\SYSTEM\*.DLL. This will list all of the DLL's. If
NETAPI.DLL OR PMSPL.DLL are in this directory, rename them
with a different file extension.
CONFIG.SYS
1. If the customer is using the DXMT0MOD.SYS driver the CF=Y
switch must be included with the other DXMT0MOD.SYS switches.
The CF=Y switch prevent application programs from intercepting
X'5C' interrupts incorrectly. The DXMT0MOD.SYS issues the X'5C'
interrupts as part of its NETBIOS function. If an application
intercepts this interrupt incorrectly, LSP processing can be
terminated. Basically you lose your transport out of the blue,
as NETBIOS functions fail. Not having this switch can cause
hangs or network disconnects that can only be fixed by rebooting.
This may seem like a lot of things to check but if you just list
the items without the explanations you can see its not really all
that much. Attached you will find a sample CONFIG.SYS,
AUTOEXEC.BAT and DOSLAN.INI for your reference. We hope this
document is of use to you, if you have any questions or
suggestions ask the DLR group, we will be happy to help.
EXAMPLE OF A CONFIG.SYS WITH A,C, & T DRIVERS, WINDOWS
AND DOS 5.0 OR DOS 6.0
(This is a Non-NDIS configuration. If you are using NDIS
then you will have different LSP drivers loading.)
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS X=D800-DFFF
DOS=HIGH,UMB
FILES=20
STACKS=9,256
DEVICEHIGH=C:\LSP\DXMA0MOD.SYS 001
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS
DEVICEHIGH=C:\LSP\DXMT0MOD.SYS O=Y S=12 C=14 ST=12 ES=4 EST=4 CF=Y
SHELL=C:\COMMAND.COM /E:2000 /P
LASTDRIVE=Z
The following is a simple AUTOEXEC.BAT that starts the
network and goes directly to Windows.
@ECHO OFF
PATH=C:\DOSLAN;C:\DOS;C:\;C:\WINDOWS
SET TEMP=C:\DOS
LOADHIGH DOSKEY
NET START
CD C:\WINDOWS
WIN
DOSLAN.INI EXAMPLE ( The values shown below are default values
for these parameters.)
RCV MACHINENAME DOMAINNAME
/SRV:8 /ASG:29 /NBC:4 /NBS:1K /BBC:1 /BBS:4K /PBC:4 /PBS:128
/PFS:32 /PFT:900 /PWT:250 /KUC:600 /KST:600
/WRK:111121101021210
/NMS:2 /NVS:4 /API /POP /UMB
* If your requester is configured as a Redirector
(RDR instead of RCV), you will not have /POP in the
DOSLAN.INI.
** The /UMB switch forces DLR to load as much of the
Redir40.exe into upper memory as possible.
_____________
LAST UPDATED 9/20/94
OWNER: LEN MALAK
(END)
12/31/99