home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
wncs11.exe
/
WNCS11.TXT
< prev
Wrap
Text File
|
1995-08-15
|
16KB
|
417 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: WINTOO.EXE, Improved WIN2NCS (Connectivity)
README FOR: WNCS11.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare Connect 1.0
ABSTRACT:
WNCS11.EXE contains version 1.11C (8/1/95) of the NetWare Connect
Windows redirector (Win2NCS, which allows you to use any Windows
communications application which uses the standard Windows API
calls, whether NASI compatible or not.). Includes several
improvements over prior versions and is recommended for all
NetWare Connect 2.0 and NetWare Connect 1.0 sites. The NWC
Windows redirector allows NetWare Connect to use any Windows
communications application which uses the standard Windows API
calls, whether NASI compatible or not.
-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.
HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION
ONLY. NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS
INFORMATION.
-----------------------------------------------------------------
SYMPTOM:
1. "Corrupted Files" message when installing on a network drive.
2. System crash if the "Specific Name" entry was too long when
using the "Map Ports Manually" option.
3. Applications that use "Receive Notify", sometimes left data
in the receive buffer if a "Receive Notify" was not received.
Very few applications use "Receive Notify", so most were not
affected.
NOTE: Symptoms 4 through 13 were corrected in Version of Win2NCS
1.10 (WINTOO) and remain corrected in version 1.11C.
4. System hang, when exiting Windows For WorkGroups.
5. Checksum errors and inability to recover from errors when
using ZMODEM with Procomm+ or PCAnywhere.
6. CRC errors during file transfers.
7. Problems with some large block transfer packages such as
SLIP/PPP and FAX programs.
8. Hesitation in Windows, when doing large data transfers.
9. Lack of reliability when using applications that transfer
large amounts of data if "Double Buffering On Writes" is
disabled.
10. If "Save Window Coordinates" was checked in the mapping
utility, it did not remain checked upon return to the utility.
11. A spurious installation error when installing on a
workstation with DR DOS 7.0.
12. Heavy server utilization when using Windows Terminal (and
perhaps other applications), when using Hardware Flow Control.
13. Unnecessary memory usage because, resources (ICONs, etc.)
that had been allocated for the NASI Mapping utility, were not
released.
New Features
1. During SETUP a fourth option "Configuration Files Always In
Windows Directory" is now available, it guarantees that the
configuration file (NCS.INI) for each user, will always be
created or acquired from the WINDOWS directory.
The prior version (WINTOO) had on only three options during
SETUP:
- "Configuration file is created in installed directory."
Normally used for a local drive install.
- "Configuration files are based on logged in name."
Option which assigns a different configuration file for each
login name. Allows both Win2NCS and the configuration files to
be centralized.
- "Configuration files are always on drive C:."
Creates and uses a configuration file in the root directory of
the users C: drive. Allows Win2NCS to be centralized, but with
local configuration files.
This version adds a fourth.
- "Configuration files are always in windows directory."
See the On-Line Help for more information concerning
configuration files.
2. Improved performance (Group Assist On Writes) for programs
that call COMM.DRV, 1 byte at a time. This will increase
performance up to five fold for such programs. However, the
majority of programs call COMM.DRV with multiple bytes.
A Global Mapping Option was also added to enable or disable
"Group Assist On Writes".
3. Timing enhancements (Timing Assist On Writes) for programs
that are timing sensitive as to how data arrives.
A Global Mapping Option was also added to enable or disable
"Timing Assist On Writes".
4. Support for 115.2KB (for communications boards that support
115.2KB).
5. ATTNASI.EXE can now be executed in Windows Standard mode and
OS/2 V2.1 Windows Standard mode.
6. "Write Callback Assist" is eliminated for LAPLINK. This
should eliminate any possibility of reentrancy problems when
using LAPLINK.
7. The included NASI.DLL is backward compatible with the
NASI.DLL in the NASI SDK. Therefore, if someone has an
application that uses NASI.DLL directly, that application can use
this NASI.DLL and both applications can run simultaneously.
NOTE: do NOT try to use the NASI.DLL that is provided with the
vendor application for Win2NCS since it may be older.
8. The program now checks to make sure that communications
applications are not redirected when exiting WINDOWS.
9. A new program called "NASI Modem Lights".
When this ICON is double clicked, the user can define a COM port
to monitor.
After the port is selected, a NASI Modem Lights window will
appear at the lower right of the screen indicating Receive and
Send Data as well as Carrier Detect, Data Set Ready, and Clear To
Send.
The indicators indicate data at the Redirector or NASI level and
not the NCS level.
The following windows Command Line parameter can be used to
invoke NASI Modem Lights for a particular port.
/PortNumber
For Example: c:\win2ncs\nmodem /1 will invoke Modem Lights for
COM1.
If you wish to invoke NASI Modem Lights each time Windows is
invoked, copy the Modem Lights ICON to the Startup Group and add
the /PortNumber to the command line.
NOTE: If the user changes the position of the NASI Modem Lights
display, the next time it is invoked, it will return to its last
position.
10. The initialization bit map no longer has black lines.
SOLUTION:
Install WNCS11.EXE
Solution Specific
Symptom # 2. The SETUP program will no longer assume that the
SYSTEM directory is a subdirectory of the Windows directory. In
addition to loading into the SYSTEM directory, NASI.DLL will load
into the WINDOWS directory if NASI.DLL already exists there.
Self-Extracting File Name: wncs11.exe
Files Included Size Date Time
..\
WNCS11.TXT (This file)
ATTNASI.EX_ 3280 8-1-95 7:18:06 pm
CTL3D.DL_ 10899 8-28-93 12:00:00 am
DIRNASI.DL_ 30435 8-1-95 7:18:02 pm
INTNASI.DL_ 2878 8-1-95 7:18:04 pm
MAPNASI.EX_ 49902 8-1-95 7:18:08 pm
MAPNASI.HL_ 36771 8-1-95 7:18:08 pm
MSCOMSTF.DL_ 37722 3-23-92 12:00:00 am
MSDETECT.IN_ 3742 3-23-92 12:00:00 am
MSDETSTF.DL_ 13519 3-23-92 12:00:00 am
MSINSSTF.DL_ 36858 3-23-92 12:00:00 am
MSREGDB.IN_ 1169 3-23-92 12:00:00 am
MSSHARED.IN_ 1032 3-23-92 12:00:00 am
MSSHLSTF.DL_ 7888 8-1-95 12:00:00 am
MSUILSTF.DL_ 3611 3-23-92 12:00:00 am
NASI.DL_ 26695 8-1-95 7:18:06 pm
NMODEM.EX_ 6279 8-1-95 7:18:08 pm
NOTNASI.EX_ 5935 8-1-95 7:18:08 pm
NSETUP.DL_ 13357 8-1-95 7:18:12 pm
NSETUP.IN_ 775 8-1-95 12:00:00 am
NSETUP.MS_ 2314 7-19-95 12:00:00 am
NSETUPH.IN_ 330 7-19-95 12:00:00 am
NWCALLS.DL_ 67608 11-2-93 12:00:00 am
NWIPXSPX.DL_ 15803 11-2-93 12:00:00 am
README.WRI 8832 8-1-95 7:18:10 pm
SETUP.EXE 24624 3-23-92 12:00:00 am
SETUP.LST 603 9-12-94 12:00:00 am
SETUPAPI.IN_ 11015 3-23-92 12:00:00 am
_MSSETUP.EX_ 6622 3-23-92 12:00:00 am
_MSTEST.EX_ 49647 3-23-92 12:00:00 am
Installation Instructions:
A. Create a directory (C:\TEMP).
B. Copy WIN--- into C:\TEMP.
C. Unzip WIN---.EXE.
D. Start Windows.
E. Use File Manager to go to C:\TEMP.
F. Run SETUP.EXE from C:\TEMP.
For further details, regarding the Redirector, bring up on-line
Help after installing it.
G. Adding Win2NCS Users On A Networked System
-----------------------------------------------------------------
------------
Win2NCS will manage independent configuration files
(automatically generating and/or acquiring the correct
configuration file on the fly, if any SETUP option for managing
configuration files is used except "Configuration File Is Created
In Installed Directory") for a user on a networked Windows
system. Each users CONFIG file is created as soon as the user
starts WIN2NCS. However, MAPNASI.EXE must be manually copied to
users individual windows desktop. (If you wish, MAPNASI can be
placed in a WIN2NCS program group.)
Also, ATTNASI.EXE (with path) must be placed in the RUN or LOAD
entry in the WIN.INI file if the user wishes the NASI Redirector
to be autoloaded when their Windows starts.
H. When running Win2NCS under Windows on OS/2 V2.1, Windows must
be brought up in STANDARD mode or, protection faults will occur
in NWIPXSPX.DLL.
I. Although all applications that were working with Win2NCS
v1.10 (WINTOO), should work correctly with v1.11C, changes were
made that might result in an unusual application not working
correctly. If an application worked properly with a former
version of WIN2NCS, but no longer does, disable "Timing Assist On
Writes" and "Group Assist On Writes" in the "NASI Mapping Utility
Global Mapping Options".
J. The defaults for the first six "Global Mapping Options"
SHOULD work with all applications. RTS Flow Control, and the
other first 6 Global Mapping Options, are included because of the
very small possibility that some unusual application may need
them.
If Hardware Flow Control (as defined by the application) is
enabled, NCS will automatically use correct Flow Control, by
toggling RTS/CTS when needed.
Choosing the "Enable RTS" option is dangerous. With that option
enabled, if the application drops RTS (to write files to the disk
or any other reason), during a file transfer, the NCS
communications driver will flush the input buffer and the output
buffer, resulting in data loss.
The Disable DTR option is provided in case you have a VERY
unusual application which drops DTR during data transfer.
Do not change the first 6 options, except as a last resort. If
you do change any of them, and the change does not solve your
problem, change them back to the default at once, otherwise
errors could occur. This is especially important with RTS
Control. RTS control should always be disabled otherwise CRC
errors could occur.
---1. The option to enable or disable double buffering on reads.
---2. The option to enable or disable double buffering on
writes.
---3. (DTR Control and RTS Control) options to allow changing
how DTR and RTS will act.
---4. Maximum ECBs Requested
For support of OS/2 and Windows 3.1 Standard Mode. Under
unusual conditions the user may be required to change the default
value.
See The On-Line Help For More Information.
---5. The option to either enable or disable the 3D look of the
NASI Mapping utility.
---6. "Selected Gray Screens" allows the user to enable, or
disable Gray Screens for the; Map Communications Ports Dialogue
Box, Global Mapping Options Dialogue Box, and the Select Colors
Dialogue Box.
NOTE: To create the effect of the first release, disable the 3D
effect and the Selected Gray Screens.
---7. A "Defaults" pushbutton to allow the user to reset the
Global Options to the preferred settings.
OVERVIEW of WNCS11.EXE (WIN2NCS)
- Allows you to use any Windows communications application which
uses the standard Windows API calls, whether NASI compatible or
not.
- Stays active at all times Windows is active (unless you turn
it off). It traps all calls to the COM port, and redirects them
to a NetWare Connect port.
- You can define up to 8 NASI Redirected ports within one Widows
session.
- You do not have load NASI before running Windows.
- Loads and calls NASI.DLL from within Windows and unloads it
again when no longer needed.
- Has been successfully extensively tested with MS Windows 3.1
(both Enhanced & Standard Mode). In addition it appears to work
with Windows 3.1 in the following systems (see On-Line Help for
information concerning known restrictions).
| > Windows 95
| > Windows with OS/2 Warp
| > Windows For WorkGroups 3.11
Version 1.10 (WINTOO) of WIN2NCS contained the following
improvements and they are carried over to v1.11C.
A. Double buffered writes. This eliminates the need for
Blocking Mode and can increase performance on some applications
15% to 35%
B. Can be installed on a network drive. This allows all users
to use the same Win2NCS, but have individual configuration files.
C. If a user is logged on to the LAN, the user name and session
names will be filled in with the Logged In Name, the first time
security is invoked.
D. A "Map Communications Ports" option called "Enable
Mapping/UnMapping Of All Ports". If this box is checked, the
user can Map or UnMap any of the 8 Com Ports, and the UnMap
button will not be grayed for local com ports that do not exist.
E. Both VGA, and SVGA color palettes. The default palette is
VGA, but the user can select the SVGA palette. NOTE: Only use
the SVGA palette if the workstation's display driver supports at
least 32K colors.
F. 3D Effect
The Win2NCS NASI Mapping Utility will now default to the 3D
look. Dialogue Boxes in the NASI Redirector that are invoked by
a communications application, will have the look of the calling
application and not the NASI Mapping Utility. Therefore, if a
invoking communications program has the 3D look, the Dialogue
Boxes of the NASI Redirector will have that 3D look.
G. A bit map will appear on the screen replacing the status
information the first time you invoke Win2NCS. The bit map will
disappear and permanently be replaced by status information after
the Map Communications Ports option is selected or the Win2NCS
mapping utility is exited.
H. The maximum number of services that can be displayed in the
Map Communications Ports option of the NASI Mapping Utility is
512.
I. The "Set Maximum Ports" option in the NASI Mapping Utility
allows single keystroke entry when setting the maximum number of
ports (instead of having to clear the entry).
J. Ability to work with Windows under OS/2Warp Version 3
("Enhancing your existing Widows and DOS", not the "Full
Package".)
K. The install files are flagged read/write to make it easier
for the administrator to erase them.
L. README.WRI can be read prior to installation.
M. The following ability only works NetWare Connect 2 (NOT
NetWare Connect 1.0).
The option to enable the Security Dialogue Box to prompt for 4.X
context by checking the Prompt User For 4X Context in the Global
Mapping Options.
If the Netware Connect is 1.X, or is running on a 3.X server,
this entry is ignored.
History:
WNCS11.EXE supersedes WINTOO.EXE which superseded WINNCS.EXE.
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their
respective owners. Consult your product manuals for complete
trademark
information.
-----------------------------------------------------------------