Index of /netwaresl/PGM_TOOL/DSWIN1

      Name                    Last modified       Size  Description

[DIR] Parent Directory 23-Apr-2005 03:05 - [TXT] DOC.TXT 15-May-1990 07:31 35k [   ] EMSNET3.EXE 08-May-1990 11:25 57k [   ] EMSNET4.EXE 08-May-1990 11:24 58k [TXT] IPX.OBJ 07-May-1990 11:03 19k [TXT] LICENSE.TXT 22-May-1990 11:59 6k [TXT] NET3.COM 08-May-1990 11:22 47k [TXT] NET4.COM 08-May-1990 11:20 48k [   ] NETBIOS.EXE 20-Apr-1990 10:10 23k [TXT] SHELL.TXT 22-May-1990 11:57 1k [   ] XMSNET3.EXE 08-May-1990 11:27 54k [   ] XMSNET4.EXE 08-May-1990 11:26 55k

NetWare DOS/Windows Workstation README file 
For NetWare DOS client v3.01 
May 1990
--------------------------------------------------
 
1.  The instructions for creating PIF files in the 
NetWare DOS/Windows Workstation Update booklet are 
for the 386 Enhanced Mode.  If you are using other 
modes, check your Windows documentation for instructions 
on how to create a PIF file. 
 
 
2.  BINDFIX--WARNING:  Do not run the BINDFIX utility 
included in this kit on a NetWare 386 server. 
 
 
3.  Full IPX/SPX support was not available in Windows v3.0 
at the time of this release.  Applications using IPX/SPX may 
cause network errors if run under Windows v3.0. 
 

4.  For product information, call 1-800-LANKIND.
    For customer service, call 1-800-LANSWER.  (This service is 
provided for a fee.)

 
5.  The INSTALL Utility for NetWare and Windows 3.0

You may experience problems if you are running Windows 3.0
in 386 Enhanced Mode with Novell NetWare.  The problem
only occurs with some network adapters configured to use
IRQ 2 or IRQ 9.  The INSTALL utility provided with this kit will
prevent these problems by installing a new file in your
Windows directory.

We recommend that you run this installation procedure if
you are using Windows and NetWare on a 80386-based
computer, whether or not your current configuration
displays the problem.  This will ensure that your copy of
Windows will function properly if your configuration is
later changed.

Performing this procedure will have no adverse affects on
your system, whether or not it is required.

The INSTALL utility may be run against your local Windows 
directory or against your shared Windows directory. 
 
If you are running it against your local Windows directory 
(usually C:\Windows), INSTALL will install a new file for use by 
Windows in 386 enhanced mode.  INSTALL will copy the file VPICDA.386 
to your Windows directory and modify your SYSTEM.INI file to tell 
Windows about the new file. 
                                                                                           
If you are running INSTALL against your shared Windows 
directory, INSTALL will install VPICDA.386 in your shared 
Windows directory.  Your SYSTEM.SRC file will be modified so 
that individual copies of Windows set up from this directory will 
receive SYSTEM.INI files that load this new file. 
 
Perform the following steps to run the installation procedure 
 
a.    Change directories to the location of 
      INSTALL.EXE.  (INSTALL.EXE AND 
      VPICDA.386 are located on the UTILITIES-2 
      diskette.) 
 
b.    Type INSTALL if you are running INSTALL 
      against your Windows directory (already installed on 
      your workstation), 
 
      OR 
 
      Type INSTALL /n if you are running INSTALL 
      against your shared Windows directory. 
 
At this point, the installation procedure notifies you that the 
procedure completed successfully. 

 
6.  The following additional shell configuration option 
is available for IPX: 
 
CONFIG OPTION=number
 
Allows you to override the configuration options 
chosen during the SHGEN or DCONFIG program.  
This parameter does not permanently change the 
IPX file.  It only changes the configurations within 
the workstation RAM.  Use it as a temporary method 
for changing the configurations.  If the configuration 
option must be changed permanently, the IPX file 
should be reconfigured through the SHGEN or 
DCONFIG program. 
 
Default: option set during SHGEN or DCONFIG 
 
7.  The following additional shell configuration options 
are available for NetBIOS: 
 
COMMANDS=number
 
Replace number with the number of commands that 
NetBIOS uses.  The minimum is 4 commands; 
the maximum is 128 commands. 
 
Default: COMMANDS=12   

Note:  NetBIOS currently allocates one send buffer for 
every command buffer allocated.  The number of 
commands and send buffers will equal the 
maximum of these two parameters. 
RETRY COUNT=number 
 
Allows you to specify the number of 
times NetBIOS will transmit a request to establish 
a connection before it times out.  No minimum and no 
maximum.    
 
Default: RETRY COUNT=20  
 
INTERNET=[ON | OFF]  
 
Affects how NetBIOS names are resolved 
to NetWare addresses.  If the internet option is 
specified as ON, name resolution broadcasts are 
forwarded through NetWare bridges through the 
internetwork.  If the internet option is specified as 
OFF, the broadcast will only be sent to stations on 
the local network, and NetBIOS will ignore inbound 
NetBIOS packets from outside the local network. 
 
Default: INTERNET=ON 

BROADCAST COUNT=number  
 
NetBIOS broadcasts packets to every station on the 
internetwork while it attempts to register or find a 
NetBIOS name.  It broadcasts the request the 
number of times recommended by the BROADCAST 
COUNT. (Older versions of NetBIOS used RETRY 
COUNT to resolve names.  
 
If the internet option is ON, the default is 4.  If the 
internet option is OFF, the default is 2. 
 
BROADCAST DELAY=number  
 
Allows you to configure the delay 
between each packet that NetBIOS sends out while 
attempting to register or find a NetBIOS name. 
 
NetBIOS waits the amount of time specified by 
BROADCAST DELAY before each retry.   
The delay is specified in milliseconds.   
 
If the internet option is ON, the default broadcast 
delay is 2,000 milliseconds.  If the internet option is 
OFF, the default broadcast delay is 1,000 
milliseconds. The minimum broadcast retry delay is 
100 milliseconds; the maximum broadcast retry delay 
is 65,535 milliseconds. 
  
Note: NetBIOS attempts to find a name whenever a session 
is established or a datagram is sent.  Names used 
by datagrams are cached where possible, but any 
datagram may require name resolution over the 
internetwork.  This can take BROADCAST COUNT 
and BROADCAST DELAY time to complete.