Yes. The network configuration tool included with MCP Express (XE) does
not support Windows 7, so you have to enable MCP networking manually.
I assume you've followed the instructions in Section 3 of the Getting
Started Guide and have the CNS and TCPIP init files in place with an
appropriate IP address and default route for your local network.
Next, open System Editor on the active PCD (with the MCP partition shut
down) and examine the configuration for NP 210, the network processor.
It should show three lines, 0-2. Line 0 is always used for the EVLAN, a
private network between the MCP and Windows environments. If you only
want to run a terminal emulator on the same workstation as XE, that is
all you need, and the default configuration should work. The checkbox
for Line 0 should be ticked.
Line 1 appears to be configured for use with a network adapter that will
be for the exclusive use of the MCP. If you have only one physical
adapter on your workstation, that is probably not what you want. I've
not yet tried to use this one. The checkbox for Line 1 should NOT be ticked.
Line 2 is configured as a "shared adapter", which will be used by both
Windows and the MCP. The checkbox for Line 2 should be ticked. Note that
the LINEID attribute for this line should be 2, which should match the
LINEID for the Connection Group in the CNS init file and the TCPIP ID
configuration in the TCPIP init file.
If you've made any changes, save the PCD. In any case, exit System Editor.
Next, go to the Win7 Network and Sharing Center and click the "Change
adapter settings" link in the upper-left corner.
The "Local Area Connection" is the physical network adapter on my
system, and probably on yours as well. The problem I had when first
setting this up was that "Unisys Network Services Protocol Driver #1"
was not ticked -- I had to select this protocol explicitly. If you look
at the properties of that protocol, you will see it is assigned to CNS
LINEID 2, which in turn matches the System Editor and MCP init file
configuration. On my system, this adapter also has "Internet Protocol
Version 4", "Client for Microsoft Networks," "QOS Packet Scheduler," and
"File and Printer Sharing for Microsoft Networks" selected, as you would
expect of a normal Windows network adapter. I am not running IPv6, so
have un-ticked that protocol.
"Local Area Connection 2" is the EVLAN virtual adapter on the MCP side.
If you look at its properties, it has only the Unisys protocol driver
checked, and its properties indicate it is assigned to CNS LINEID 0, as
it should be.
"Local Area Connection 3" is also an EVLAN virtual adapter, and has
properties similar to Connection 2, but this one appears to be for the
Windows side of the EVLAN. If I do an "ipconfig" command, it has address
192.168.16.6, which is the address for the Windows side of the EVLAN.
Note that the WebEnabler application that is used for the ODTs and MARC
window is a standard T27 terminal emulator, and can be installed on
other systems. It requires Java. You can install it from the MCP
INSTALLS share, or get and install file from
*SYSTEM/INSTALLS/NXWEBSTATION/NXWEBSTATION_INSTALLERS/=.
You can also use the telnet client that is included in Windows. It's not
as nice as a proper T27 emulator (the MCP emulates T27 control sequences
on top of ANSI X3.64), but it works.
If you want the MCP to resolve domain addresses on an external network,
you'll need to set up the Resolver configuration file,
*SYSTEM/RESOLVER/CONFIG, which must have a FILEKIND of SEQDATA. Here's a
basic example:
CACHE = 64
MODE = FORWARDING
SERVER + 192.168.2.20
SERVER + 10.101.1.24
I hope this allows you to fix the problem and get your system on the
network. If not, please post back and describe what's happening and I'll
try to help.
--
Paul