NETWORK - DOSUP8.ZIP - HISTORY.DOC

 
Output of file : HISTORY.DOC contained in archive : DOSUP8.ZIP

Shell v3.01 Rev A
The initial release of the v3.01 shell files forms the beginning of the
DOS shell history file. The files included were:

NETx.COM 3.01 Rev. A 5-8-90
EMSNETx.COM 3.01 Rev. A 5-8-90
XMSNETx.COM 3.01 Rev. A 5-8-90

Shell v3.01 Rev B
The second release of the v3.01 shell corrected a problem with the Rev A
shell in which loading SiteLock by Brightworks would fail, thus causing
the DOS workstation to hang.

NETx.COM 3.01 Rev. B 6-6-90
EMSNETx.COM 3.01 Rev. B 6-6-90
XMSNETx.COM 3.01 Rev. B 6-6-90

Shell v3.01 Rev C
The NetWare DOS Shell v3.01 Rev C was made available only to NetWare
developers. It corrected a number of problems with the Rev B shell, as
detailed below. (These changes were all incorporated into the Rev D
release dated 9-7-90.)

NETx.COM 3.01 Rev. C Not released
EMSNETx.COM 3.01 Rev. C Not released
XMSNETx.COM 3.01 Rev. C Not released

o Using the "Preferred Server" option with the Rev B shell caused the
network response time to be functionally slower than if the user did
not use this option.
o When using DOS 4.0 with the EMSNETx and XMSNETx shells, the DOS
directories would not display correctly under Windows.
o The enhanced memory shells were not sending header information when
using print job configurations that included escape codes. For
example, a print job that should print landscape would print using
the default mode (portrait).
o When printing to a captured LPT device, a "Device not ready" error
message would appear. A retry would allow the job to continue.
o Fake roots were being deleted on paths with volume names before the
path was determined valid; for example, CD PRN: would delete the
fake root.
o On NetWare v2.x-based servers, memory in Dynamic Memory Pool 1
(DMP 1) was not being released properly with the XMSNETx and EMSNETx
shells, eventually causing the server to hang. With the v3.01 Rev
C shell, the memory is released when the user exits the Windows DOS
prompt.

Shell v3.01 Rev D
The NetWare DOS shell v3.01 Rev D, dated 9-7-90, was released to users
and contains all of the changes listed above for the Rev C shell.

Another release of the Rev D shell occurred on 9-18-90.

NETx.COM 3.01 Rev. D 9-18-90
EMSNETx.COM 3.01 Rev. D 9-18-90
XMSNETx.COM 3.01 Rev. D 9-18-90

This release contained the following changes:

o When running the v3.01 Rev D shell with a NetWare v2.15 or previous
OS, external program execution from the login script (using the #
command) does not work unless the user has Open privileges at the
volume root. This was corrected in the shells dated 9-18-90 and
later.
o The NVER command returns Rev C instead of Rev D. This was corrected
in the shells dated 9-18-90 and later.

Shell v3.01 Rev E
This revision of the shell included the files listed below.

NETx.COM 3.01 Rev. E 11-27-90
EMSNETx.COM 3.01 Rev. E 11-27-90
XMSNETx.COM 3.01 Rev. E 11-27-90

This revision corrected the following problems and also incorporated
several enhancements:

o When using the DOS 4.0 "TrueName" command (an undocumented DOS
command), invalid data was returned to the shell. This invalid data
causes Emerald's System's backup to not function properly.
o Microsoft Link was reporting a scratched file error when linking a
large number of files.
o The rename function returned the wrong error code to applications
such as Platinum Accounting by Advanced Business Microsystems. This
error was also exhibited with the NETGEN message "Cannot find
DRVRDATA.DAT."
o The shell was not correctly maintaining the default server after
logout when an X.25 bridge is used.
o On ELS NetWare servers, you would get one less connection than the
maximum when using remote boot. The v3.01 Rev E shell allows the
maximum number of server connections.
o Rev E enabled file caching in EMSNETx and XMSNETx shells, which was
not enabled in earlier releases of the enhanced memory shells.
o Rev E added support for the VERSION.EXE utility, which was not
present in earlier releases of the shell.
o Rev E added the "/?" option to the command line, to display version
and usage information.
o Rev E added a feature that informs the user if a terminate-and-stay-
resident (TSR) program is loaded above the shell when the user is
trying to unload the shell.

Shell v3.02
Version 3.02 of the NetWare DOS shell included the files listed below.

NETx.COM 3.02 2-06-91
EMSNETx.COM 3.02 2-06-91
XMSNETx.COM 3.02 2-06-91

This release contained the following fixes and enhancements:

o Corrected a problem that caused some applications that use EMS or
XMS (such as DESQview, NetRemote, and such) to occasionally hang
when using the enhanced memory shells.
o Corrected a problem where capturing to a file would result in
truncated print files. These files are now created and printed
correctly.
o Unloading the shell now relinquishes all connections (previously it
retained one connection.)
o Corrected a problem with the file caching introduced with the
NetWare shell v3.01 Rev E. Users were experiencing problems when
running Paradox, Quattro, and Lotus 1-2-3 with the extended memory
shells.
o Enhanced the speed of file caching, which improves the speed of file
read and writes.
o Setting the parameter "CACHE BUFFERS = 0" in the NET.CFG file now
turns off the shell's file caching.
o Added two new NET.CFG parametersþDOS NAME and ENVIRONMENT PAD:

DOS NAME=name
This option specifies the name of the DOS version used by the
workstation. This name could be something like "MSDOS," "PCDOS,"
"DRDOS," and should correspond to the %OS name in the login script
and the name of the DOS directory. The maximum length of the DOS
NAME is five characters.

ENVIRONMENT PAD=number
This option specifies the number of bytes that can be added to the
DOS environment space for storing search drive path names. If you
are specifying many long path names for search drives with the MAP
command, you may need to add extra environment space to hold those
names. The number of bytes can be any number from 17 to 512 (17 is
the default). Novell recommends that you leave this option at the
default value unless you are encountering environment space
problems.

Shell v3.10
Version 3.10 of the NetWare DOS shell included the new NET5.COM,
XMSNET5.EXE, and EMSNET5.EXE files that work with DOS 5.0.

NETx.COM 3.10 3-07-91
EMSNETx.COM 3.10 3-07-91
XMSNETx.COM 3.10 3-07-91

Shell v3.21
Starting with this release of the NetWare DOS shell, the same three
filesþNETX.COM, XMSNETX.EXE, and EMSNETX.EXEþ work with DOS 3.x, 4.x, and
5.x. This is the so-called "generic" shell.

NETX.COM 3.21 7-18-91
EMSNETX.COM 3.21 7-18-91
XMSNETX.COM 3.21 7-18-91

In addition, the v3.21 shell contained the following corrections and
enhancements:

o Fixed a problem with the "Preferred Server" function that caused
some machines to hang randomly.
o Fixed a problem with being denied simultaneous access to a shared
file.
o Corrected "call 5" functions for programs ported from CP/M to DOS.
o Resolved a problem where Btrieve files were being corrupted when the
server was downed improperly.
o Fixed a cache problem that was causing a WordPerfect disk full
error.
o Fixed the DOS NAME parameter problem that was causing the EMS and
XMS shells to hang when loading.
o Fixed the problem with the "P_STATION" variable returning bad
information in the login script. (This problem occurred only with
the v3.2 shell.)
o Fixed a problem that was causing DOS 5.0 "Load High" not to work
properly with NET5.COM. (DOS "Load High" works with NETX.COM v3.21
and later).
o Fixed a problem that caused the DOS 5.0 MEM program to display
program names improperly after the shell was loaded.
o Fixed a problem that made the DOS ATTRIB command unable to find
hidden directories on network drives.
o Fixed a problem with remote boot on workstations with hard drives.
o Added the "/C = filename" option to allow flexible naming of the
shell configuration file (for instance, /C=NET.CFG).
o Added the "/F" option to allow the shell to be unloaded after it has
been loaded high.
o Added a date code to the shell. The command "NETX i" will now
display the shell's date of creation along with the version and
copyright information.
o Added a feature to display the version of DOS that is currently
running when the shell is loaded.
o Enhanced the shell to be able to locate the master environment
regardless of its location.
o Added support for EMS memory handle names.
o Added support for international date and time formats.

Shell v3.22
This release of the NetWare DOS shell corrected a problem with remote
boot and DOS 5.0. Previously, the shell would look to the F drive rather
than the A (virtual) drive.

NETX.COM 3.22 7-31-91
EMSNETX.EXE 3.22 7-31-91
XMSNETX.EXE 3.22 7-31-91

Shell v3.26
This release of the NetWare DOS shell included the new Burst Mode (Packet
Burst) shell, BNETX.COM.

NETX.COM 3.26 2-11-92
BNETX.COM 3.26 2-11-92
EMSNETX.EXE 3.26 2-11-92
XMSNETX.EXE 3.26 2-11-92

It incorporated the following corrections and enhancements:

o Corrected a problem where CAPTURE would return "garbage" characters
to the screen when capturing without a specified queue name.
o Corrected a problem in which COMSPEC was not being reset to the
local drive when the shell was unloaded with COMSPEC set to a
network drive.
o Corrected a problem with the MS-DOS DOSNAME function not working
properly with EMSNETX.EXE and XMSNETX.EXE.
o Corrected a problem with certain database applications which issue
the commit file command. (The file is now properly updated on the
file server disk.)
o Corrected network errors due to a packet size negotiation problem.
This problem occurred when using the "Preferred Server" option on
a workstation with a packet size greater than that of the preferred
server, and the initial server also had a packet size greater than
the preferred server.
o Enhanced the shell so that memory display applications such as the
MS-DOS MEM program display the name of the shell as well as its size
and location.
o Added a procedure to check if the total of "FILE HANDLES=" in
NET.CFG and "FILES=" in CONFIG.SYS exceeds 254. If so, an error is
returned and the shell is not loaded.
o Added two new NET.CFG parametersþSEARCH DIR FIRST and NCP TIMEOUT
FLAG:

SEARCH DIR FIRST=ON/OFF
This option determines the order in which the shell searches files
and directories on a NetWare file server. If SEARCH DIR FIRST=ON,
the shell searches for directories first. If SEARCH DIR FIRST=OFF,
the shell searches for files first. The default is OFF.

SEARCH DIR FIRST applies only to handle-oriented directory searches,
as from within Windows' File Manager, not to FCB directory searches,
as in DOS's DIR command.

NCP TIMEOUT Options
These options add the ability to change the default timeout value
of the shell. Three options need to be set:

NCP TIMEOUT FLAG=ON (default is OFF)
NCP TIMEOUT BASE=n (default is 10; range 1þ255)
NCP TIMEOUT MULTIPLIER=n (default is 4; range 1þ255)

If only "NCP TIMEOUT FLAG=ON" is set, the shell uses the default
values for the NCP timeout base and multiplier. Setting the base and
multiplier lower than these default values reduces the shell's
timeout. Setting the values too low will cause an excessive number
of network errors.

Increasing the base by increments of 1 increases the NCP timeout by
1 tick. The shell multiplies the NCP TIMEOUT BASE number by the
value set for NCP TIMEOUT MULTIPLIER. The result should not exceed
255.

Note: This option was added for unusual circumstances and may cause
unpredictable results when used incorrectly! Novell recommends
that these values not be changed from the defaults except in
special circumstances.

Shell v3.30
This revision of the NetWare DOS client software was not released. The
changes and enhancements detailed below were all incorporated into the
v3.31 release dated 11-12-92.)

NETX.EXE 3.30 Not released
BNETX.EXE 3.30 Not released
EMSNETX.EXE 3.30 Not released
XMSNETX.EXE 3.30 Not released

This revision of the shell incorporates some significant enhancements
that enable it to work with upcoming products such as SFT Level III and
NetWare v4.0. (A v3.30 client can attach to a NetWare v4.0 server, but
the shell does not support any Directory Services functionality.)

o The v3.30 shell has been language enabled so that all initialization
and run-time messages are accessed from the NETX.MSG file. This file
must be located in the same directory as NETX.EXE.
o NETX and BNETX are now .EXE files. This makes it easier to load them
high, since the message file is appended and doesn't affect the load
image size. It now takes a 60KB contiguous upper memory block (UMB)
to load NETX.EXE high.

Note: If *NETX.COM files reside in the same directory as *NETX.EXE
files, users must rename or remove the *.COM files to be able
to run the *.EXE files.

o Fixed the shell to allow it to be unloaded when it has been loaded
into a UMB.
o Modified the shell so it can correctly handle double-byte and
foreign characters in path and file names. Removed support for the
SPECIAL UPPERCASE keyword in NET.CFG.
o Enhanced the shell to handle broadcast messages that, when
translated, are longer than the current maximum 22-character clear
text message. When the user presses +, the remainder
of the message will be displayed.
o Enhanced the shell so that broadcast messages are always displayed
at the bottom of the screen. The shell now reads the number of
active display rows before displaying the broadcast message.
o Enhanced the shell's ability to adapt to network changes by re-
negotiating packet size when a router or an SFT III mirrored server
goes down.
o Added Large Internet Packet (LIP) capability for routers that are
enabled for large packets. Refer to the documentation that
accompanies the LIP software.
o In light of Novell's change of the default Ethernet frame type from
802.3 to 802.2, support was added for IPX checksumming on 802.2
frames.
o Changed how the shell looks for its configuration file:

1. It first looks for a NET.CFG file in the current working
directory.
2. If not found, it looks for a NET.CFG file in the directory the
LSL was loaded from, or in the current working directory at
the time the LSL was loaded, in that order.
3. If still not found, it looks for a SHELL.CFG file in the
current working directory.

o Fixed a memory allocation error caused when the ENVIRONMENT PAD
variable in NET.CFG was set below the minimum of 11 decimal.
o Fixed a problem where the shell was printing out the "Pipe not found
in transient portion of COMMAND.COM" warning when the shell had
already patched the pipe string. It now only prints the warning if
the shell couldn't find a pipe string, either modified or not.
o Fixed a bug that was causing the shell, when used with IPXODI, to
hang after receiving a broadcast.
o Fixed a problem where the shell was changing the value of the stack
pointer without disabling interrupts first, which caused occasional
lock-ups.

Shell v3.31
The 3.31 release of the NetWare DOS client software supports the "NCP
Packet Signature" security enhancement for NetWare v3.11.

NETX.EXE 3.31 11-12-92
BNETX.EXE 3.31 11-12-92
EMSNETX.EXE 3.31 11-12-92
XMSNETX.EXE 3.31 11-12-92

It incorporates the following corrections and enhancements:

o Enhanced all shell files to perform NCP packet signing. This feature
is enabled through the following NET.CFG setting:

SIGNATURE LEVEL = n
The default value for n is 1, which means the client signs packets
only if the server requests it. Other valid values are:

0 Client does not sign packet
2 Client signs packets if the server is capable of signing
3 Client signs packets and requires the server to sign packets
(or logging in will fail)

Refer to the documentation file that comes with the security
enhancement for more information.

o Added two new NET.CFG parameters to limit packet sizes:

LI FRAME MAX=n
Sets the maximum frame size when using Large Internet Packet (LIP).
The default is 8192 bytes (8KB). Valid range for n is 512 to 16,384
bytes.

PB FRAME MAX=n
Sets the maximum frame size when using Burst Mode (Packet Burst).
The default is 2112 bytes. Valid range for n is 576 to 8256 bytes.

In almost all cases, the default values are the best ones to use.
These parameters should be changed only by a qualified NetWare
technician.

o Fixed a problem where the shell would not unload properly under DR
DOS v6.0.

o Fixed several problems with the Burst Mode shell: a memory
allocation bug, an incomplete write problem, and a timing problem
that was manifest in various ways, including hanging under Windows.

Shell v3.32
The v3.32 release of the NetWare DOS client software has been changed to
include support for DOS versions 3.0 through 6.0.

NETX.EXE 3.32 02-17-93
BNETX.EXE 3.32 02-17-93
EMSNETX.EXE 3.32 02-17-93
XMSNETX.EXE 3.32 02-17-93



Shell v3.32 ptf
The pft Version dated 06-24-93 incorporates the following corrections
and enhancements:

NETX.EXE 3.32 ptf 06-24-93
EMSNETX.EXE 3.32 ptf 06-24-93
XMSNETX.EXE 3.32 ptf 06-24-93


o Interrupt 21h function 40h errors were not being passed on to
application. The shell was clearing the carry flag on write
errors, causing an application to believe that no write
error occurred.

o Interrupt 21h function 4B01h (Load but do not execute) was
causing workstation to hang. This has been fixed in this release.

o The stack size was increased in order to accomodate the
"PRINT TAIL" parameter in NET.CFG

o Interrupt 21h function 4409h was returning incorrect values
when run on a network drive. This version of the shell
corrects the problem.

o The shell was returning an incorrect print job number. The
problem was fixed in this version of the shell.

o If a section of a file is locked with int 21h - 5Ch, and
then another workstation accesses the same file and tries
to read the locked area with int 21h - 3Fh, it will return
successful. This version of the shell fixes the problem.


April 20, 1993

BNETX.EXE and PBURST.NLM were removed from DOSUP7.ZIP due to a rare problem
resulting in data corruption when burst mode was being used.