Intermec 6100 Reference Guide

R

For NRInet, SERVICES must contain a protocol entry for nrinet" with a

protocol type of tcp."  For example:

nrinet 44965/tcp #Norand Inet File Transfer

The fields domain" and domainĆnameĆserver" are not required if the host is

specified by IP address rather than domain name.  Also, the fields that specify IP

addresses (nnn.nnn.nnn.nnn) and the domain" field can be omitted if

BOOTP.EXE or DHCP.EXE loads the information from a BOOTP server or a

DHCP server.
Set the environment variable PCTCP to the path of PCTCP.INI.  For example, in

AUTOEXEC.BAT:

SET PCTCP=C:\PCTCP.INI

Some computers support two network interfaces for NRInet: Ethernet and

RSĆ485.  The network interface is selected in a menu in Norand Utilities during

the IPL sequence.  This setting is stored on the RAM drive so it disappears any

time the RAM drive is removed or formatted.  For example, applications that

boot from a PC Card often format the RAM drive before installing the

application.  In these cases, you must return to the Norand Utilities menu to

reselect the setting in order for NRInet sessions to work correctly.
When the RSĆ485 network interface is used on a computer with an Ethernet

network interface, PSROM0C.EXE powers off the the Ethernet adapter.  If the

application uses the Ethernet adapter outside of PSROM0C.EXE, it is

recommended to unload the Ethernet drivers before calling PSROM0C.EXE,

then reload them afterwards.

Under the NORAND standard file transfer session, the HHC always uploads

first.  Once all upload files are sent, the line is turned around and the host then

sends any download files.  Each file is preceded by a header record that gives the

receiving computer information about the format used by the file.
The HHC must first send a session control file, which identifies the HHC to the

host computer.  The HHC may then send a download request file.  This optional

file prepares the host computer to download one or more files to the HHC.

Upload files can then be sent to the host.

To identify itself to the host, the HHC sends the session control file at the

beginning of a TCOM session.  The applicationĆdependent HHC ID is used by the

host to determine which files to downloading to the HHC.  The format of the

session control file is as follows:

<DSCNTRL00001Xnnn>PPPPPPPPPPPPPPTTTTTTTTTTTTTTTTYYMMDDHHMMSS . . .

where:

               < = beginning of file header
               D = file type (fixed)
          SCNTRL = file name (fixed)
           00001 = decimal number of records in file (fixed)
               X = data type (ignored by host)
             nnn = decimal number of bytes in file record
               > = end of file header
  PPPPPPPPPPPPPP = program identification
TTTTTTTTTTTTTTTT = hand-held computer ID (determined by application)
          YYMMDD = date
          HHMMSS = time
           . . . = additional HHC information