Network Links User Guide

7 PCNE2 moduleoptions

You need to make sure PCNE2 is set up correctly for the PC networksoftware which you intend to use. You can configure the PCNE2 module bychanging the following line in !PC's !Run file:

   RMEnsure PCNE2 1.87  RMLoad <Obey$Dir>.PCNE2 {options}

{options} may be one or more of:

-ppacket type

Selects the type of network packets which PCNE2 is to receive andtransmit to the network. This needs to be chosen according to the PCnetwork software in use. The currently available types are:

ISO	Packets using theISO/IEEE802.3-style Frame Length packets. This is what Netware, NetwareLite, and Windows for Workgroups normally use, and is the default forthe PCNE2 module.
IPX	Novell systems using the IPX protocol and oldEthernet (Ethernet_II) ('Frame Type') style packets. See section 5.2, Alternative Novell Netwareconfigurations for an explanation of this.
TCPIP	Systems using the TCP/IP protocol e.g. PC-TCP orPC-NFS.
XNS	Xerox's XNS protocol (e.g. 3Com's 3+Open system).
DECNET	Digital's DECNET-DOS operating system.
DECLAT	Digital's LAT protocol.
IBMSNA	IBM's SNA architecture

More than one -p option can be given, although there is amaximum limit imposed by the network driver.

Some choices may use up more than one frame type.

-nnumber

If you need to support a protocol which is notlisted above, you can specify the Frame Typevalues which PCNE2 should receive by number using this option. Thenumber given is in hexadecimal using up to 4 digits:

Frame type	Number
TCPIP	-n800 -n806-n8035
DECLAT	-n6004
DECNET	-n6003 -n6005 -n6006-n6007
XNS	-n600 -n807
IBMSNA	-n80D5
ISO	-n0000
IPX	-n8137

Several -n options can be given, and mixed with-p options.

-ddriver name

Selects the RISC OS network driver and unit number to be used. PCNE2will choose a driver and unit number from:

the -d command line option if given
system variable Inet$EtherType, if it is set
driver and unit ea0

If you have just one Ethernet card in the machine and are not usingmultiple units (see Chapter 6,Using multiple Ethernet driver units, above)PCNE2 should automatically use the right driver, and you will not needto set a -d option. You can check this by typing

*show Inet$EtherType

at the command line. The internal driver name will be two lettersfollowed by a unit number, for example:

eh0 for an i-Cubed Ethernet card (eh),unit 0
eb0 or eb1 for ANT/older Acorn cards
ea0 for podule Atomwide/ANT/Acorn Ether III cards

The internal driver name for your Ethernet driver is shown in the listin the section Ethernet drivermodule in ROM . The unit number is always zero, unlessyou have more than one Ethernet card in the machine, or a driver thatsupports multiple driver units.

-b

This is the 'bodge' option that is necessary to get around a problemwith older SEEQ 8005 Ethernet controllers(these are found on ANT podule network cards). Do*showstat at the command line to find out which you have.

SEEQ 8005 controllers supply an extra three or four bytes on the end ofsome types of packet. This prevents Netware(when using IPX)from working on cards with an8005 controller. The -b option removes four bytes from theends of packets and cures this problem.

The problem only appears if Netware is set to use Ethernet IIpackets; if you are using ISO packets, whichhave their own length field, or TCP/IP packetsthis option is not needed.

-p packet type
-n number
-d driver name
-b