home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 3 Comm
/
03-Comm.zip
/
nos2eval.zip
/
readme.txt
< prev
next >
Wrap
Text File
|
1996-07-02
|
4KB
|
103 lines
NetOp for OS/2, version 5.2
===========================
NetOp for OS/2, version 5.2 consists of an OS/2 Guest, an OS/2 Host and an
OS/2 Gateway.
The Guest program can establish a remote control connection to
the Host program via the following communication methods:
- IPX
- NetBIOS
- Serial (modem / null-modem)
- APPC/APPN (SNA)
- TCP/IP (IBM,FTP)
- ISDN (Capi interface)
The Guest program can also remote control NetOp for Windows Hosts.
Furthermore, the Guest program can establish a remote control
connection to version 4.3x of REMPCNB, REMPCIPX and REMPCOS2,
making it backward compatible with NetOp/NetOpPM version 4.3x.
The Gateway permits the OS/2 Guest program to access the gateway via
modem, ISDN or APPC and then reach OS/2 or Windows Hosts via NetBIOS, IPX
or TCP/IP.
TCP/IP
------
If a DTL2.INI file is created (see manual section 7.4) then the TCP/IP
section should start with [TCP/IP] and NOT with [TCPIP] as documented in
the manual.
NetBIOS
-------
When the NetOp Host program has loaded, please wait at least 10 seconds
before trying to connect to the PC.
Serial/modem
------------
NetOp for OS/2 needs the modem to have local echo enabled (this is
default on most modems). If this is not enabled NetOp will generate
a "No response from modem" message. To explicitely enable local echo
add E1 to the modem setup string.
If you cannot get a remote control session running, please try to define
modem strings that forces your modems not to use compression and error
correction.
Initializing multiple protocols
-------------------------------
If you experience problems during load or exit of the program, please try to
run with only one protocol initialized to test if that solves the problems.
For example, initializing IPX and NetBIOS simultaneously can in some cases
cause malfunction.
Color reduction
---------------
If you reduce the color to 2, you can gain quite a lot of speed when running
across slow speed links. If the screen on the Guest is difficult to read, you
can optain a very good result by changing the color palette on the host.
You can for example do this by selecting System SetUp, then Scheme Palette.
Press the Alt key while you drag e.g. the Monochrome Scheme to your desktop.
Blank Screen
------------
The Blank Screen feature is not supported by all graphic adapters. It has been
verified that the following adapters do not support blank screen: XGA-2
Keyboard Control
----------------
If your Host is running Warp, and you cannot control the keyboard, please try
to add the parameter /D to the NHOST2.SYS device driver in your config.sys
file. Eg: Device=c:\netop\nhost2.sys /D
Mouse Control
-------------
If you are remote controlling an OS/2 2.11 Host you might potentially loose
control of the remote mouse. This is due to OS/2 responding with a message of
in-sufficient resources. If you run into this problem, please use our
"local mouse" setting on the Guest PC. Should this not overcome the problem,
consider upgrading OS/2 to Warp, where no such problem exist. If you cannot
upgrade, you can work around the problem by re-loading the Host program. You
can even do this remotely. If you load the Host program via a cmd file and
then remotely close down the Host, the cmd file will automatically re-load
the Host.
Example of cmd file, NHOST.CMD
:START
NHOST2 /L
GOTO START
Please notice that you should close the NHOST2 program from the NHOST2 program,
not from the task list.
Danware Data A/S
July, 1996