
MSDOS5.0

NO NAME    FAT12   3

|8N$}$

at2Nt

BOOTMGR    

Remove disks or other media.

Disk error

Press any key to restart

$CB$Eb$G

'sB'ub'w

33C35c37

4CC4Ec4G

5SC5Uc5W

6cC6ec6g

7sC7uc7w

C1$C3DC5dC7

DA$DCDDEdDG

ESDEUdEW

Fa$FcDFedFg

Gq$GsDGudGw

$CB$Eb$G

'sB'ub'w

33C35c37

4CC4Ec4G

5SC5Uc5W

6cC6ec6g

7sC7uc7w

C1$C3DC5dC7

DA$DCDDEdDG

ESDEUdEW

Fa$FcDFedFg

Gq$GsDGudGw

FILE    HLP 

INSFILES    

INSFILESLAN 

INSHELP     

INSTALL EXE 

MSCDEX  EXE 

NET     BAT 

NETBIOS EXE 

NS      EXE 

PRTSC   EXE 

README  DOC 

REDIR   300 

REDIR   400 

REDIR   500 

RQAGENT EXE 

RQNAMES H   

RQNAMES LIB 

RS422   EXE 

RS485   EXE 

RS485EM EXE 

RS485NEWEXE 

S121100 DOC 

SESSION EXE 

SETNAME EXE 

TBACKUP EXE 

TRESTOREEXE 

AUTOEXECPC  

AUTOEXECPCE 

CDDRIVEREXE 

CDR     EXE 

CONFIG  SMP 

CTOSAPI DL_ 

CTOSRQ  DL_ 

CTRQRS4 EX_ 

CTRQRS4 IN_ 

                        SignOn 

 Login

  Starts a session with your user name that replaces the 

No Name

  entry in the cluster list on the CTOS server.                  

                             

     Login Name     One to 16 characters for your user name.

          

        

        

                                                                

                     

                        SignOn 

 Logout

  Disconnects all local drives and devices connected to network

  drives and devices.  A processing window appears to confirm

  the Logout.  Press OK to continue or CANCEL to cancel the 

  Logout.

                                   

                                                                  

                    

                        SignOn 

 ClusterUsers

  Displays the Login names of all workstations clustered to the  

  CTOS server.  No input is required.

                                

  These same names appear in CTOS if you use the Cluster Status 

  command, under the User Name column.

                                                                 

                      

                        SignOn 

                                                          

                                                                 

                                 

                                                               

                       

                        SignOn 

 Exit         

                

    Exits from LANce

pc Network Shell and returns to the DOS 

    system prompt. Any logical connections remain intact. To 

    disconnect the logical connections before exiting, select

    Logout then Exit.        

                                                                   

                     

                                          

                     General Help Information

  Select from one of the words at the top of the screen by 

  pressing the ALT key and the highlighted letter in the word. 

  SignOn   Specifies a user name to the CTOS server, disconnects all

           local connections, displays workstations, or exits.

  File     Connects or disconnects network drives, lists all 

           connections, or lists all directories in server's <Sys>.

  Printer  Connects or disconnects network printers, lists all

           available printers, or lists status for specified printers.

  Admin    Creates and deletes CTOS directories, displays the last 

           error from SMB Service, or modifies CTOS directory

           passwords.

                        File 

 Connect

  Connects a local drive to a CTOS or LAN network drive.

                 

  Local Drive    E: through the last drive specified in CONFIG.SYS.

  Network Drive  \\SERVER\LOCAL\Volume\Directory            

         or      \\SERVER\BNetNodeName\Volume\Directory

         or      \\Server\CTOSResourceName

         or      \\NetBIOSName\ResourceName

         or      \\NetBIOSName\LOCAL\Volume\Directory 

         or      \\NetBIOSName\BNetNodeName\Volume\Directory

  Password       Optional. 1 to 8 characters for directory password.

                        File 

 Disconnect        

  Disconnects a local drive from the network drive.  You must 

  disconnect a drive before reconnecting to another network drive.

       

  Local Drive     E: through the last drive specified in CONFIG.SYS.

              

                        File 

 List

    Lists all the local drive and device connections, with the  

    corresponding network drive and device names.  No input        

    required.                                 

                                                              

                       

                        File 

 VolumeDir  

  Lists all the directories from the <Sys> volume of your     

  CTOS server.  No input required.

     

     

                              

     

                                                               

                   

                        Printer 

 Connect

  Connects a local printer device to a network printer device.       

                                                                   

  Local Device    LPT1, LPT2, or LPT3.

                                                                   

  Network Device  Up to 27 characters for a network device.

                  \\SERVER\DeviceName

             or   \\NetBIOSName\DeviceName

                                                               

                      Printer 

 Disconnect

  Disconnects a specified local device from a remote device on the

  server. 

            

  Local Device    LPT1, LPT2, or LPT3.     

            

                                                              

                   

                        Printer 

 (DOS Printers)

     

             

       

       

                        Printer 

 List        

  Lists all printers and queues currently available on CTOS.

  (For printers currently connected, see File 

 List.)     

  CTOS Name   CTOS printer device name.

  DOS Alias   DOS alias name from SMBFileMap.cfg file.

  BNet Node   BNet name of the server where printer installed.

  Expects     Printer mode (CTOS ASCII, PC ASCII, or binary).

  Physical    Physical location of the printer, stipulated by 

    Location  the system administrator.  Without GPS, this

              column is blank.

                        Printer 

 Status

  Displays the current status of a selected CTOS server printer. 

                            

  CTOS Printer   One to eight characters for the CTOS

                 printer name.  

      

       Idle        Ready to print.

       Printing    Currently printing a document.

       Down        Printer not switched on.

       Paused      Printer waiting for an operator.

       Off

line    Off

line option selected on printer.

                        

                        Tape 

            

                                                                         

                                                       

                          

                                     

                        Tape 

 (Restore)  

     

                

                        Tape 

 (Rewind)   

                           

                                                       

        

              

                        Admin 

 Create

  Creates a CTOS directory in a CTOS volume.              

  Directory    Up to 30 characters for the directory.  

  Name         \BNetNodeName\Volume\Directory

  Dir Password One to eight characters for the CTOS 

               directory password.

              

                        Admin 

 Delete

  Deletes a CTOS directory. A directory can only be deleted 

  if it is empty.                                

  Directory Name    Up to 30 characters for the directory name.

                    \BNetNodeName\Volume\Directory

                                                               

  Dir

Vol           One to eight characters for the CTOS

  Password          directory password or volume password.

       

                        Admin 

 Error

  Displays the last CTOS error message (if one exists) from the SMB

  Service running on the CTOS server.  No input required.

         

                        Admin 

 Modify

  Adds, changes, or removes the password from a CTOS directory.   

  Directory Name      Up to 30 characters for the CTOS directory.

                      \BNetNodeName\Volume\Directory

  New Dir Password    Optional. 1

8 characters for directory password.

  Old Dir

Vol         1

8 characters for the old directory

  Password            password or volume password.

                        

                        Diag 

 Netname

       

       

       

       

       

              

       

                        Diag 

 Reset

       

       

                        Diag 

 Addname

      

       

      

       

       

              

                        Diag 

 Deletename

       

       

       

                        Diag 

 Findname

       

       

       

       

                                     

       

       

       

                        Diag 

 Call

       

                                                        

       

       

       

               

             

       

                        Diag 

 Listen

       

        

       

       

               

       

       

                        Diag 

 Send

              

           

                        Diag 

 Receive

       

       

       

       

       

       

                        Diag 

 Hangup

                     

\LANCE\RQNAMES.LIB

\LANCE\NET.BAT

\LANCE\FILE.HLP

\LANCE\NS.EXE

* CDROM SOFTWARE

\CDROM\CDDRIVER.EXE

\CDROM\CDR.EXE

\CDROM\MSCDEX.EXE

\CDROM\CONFIG.SMP

* LANCE SOFTWARE

\LANCE\README.DOC

\LANCE\NETBIOS.EXE

\LANCE\SESSION.EXE

\LANCE\PRTSC.EXE

\LANCE\SETNAME.EXE

\LANCE\TBACKUP.EXE

\LANCE\TRESTORE.EXE

\LANCE\RQNAMES.H

\LANCE\FILE.HLP

\LANCE\NS.EXE

\LANCE\RQNAMES.LIB

\LANCE\RQAGENT.EXE

* CDROM (THIS LINE JUST PROMPTS INSTALL.EXE TO ASK FOR SECOND DISK)

* LANCE SOFTWARE

\LANCE\README.DOC

\LANCE\TBACKUP.EXE

\LANCE\TRESTORE.EXE

\LANCE\RQNAMES.H

The INSTALL program creates a \LANCE directory and a 

\CDROM directory, and copies files into the directories.  

If you have Windows installed, INSTALL also copies files 

to your Windows directory.

As each file is copied, the file name appears below.

The INSTALL program creates a \LANCE directory and a 

\CDROM directory, and copies files into the directories.  

If you have Windows installed, INSTALL also copies files 

to your Windows directory.

As each file is copied, the file name appears below.

t$<\t

t'<\t

Z[X_+

,at[,

,+t$,7t>

, <Xw

<st'<ntQ<pt

s6BSQ

7t3)G

_^]XP$

$0<0u

'SQPRJ

7,7>7U7

+*'_'

7,7>7U7

+*'_'

tDPRS

N([ZXr9

,6,B,M,V,a,j,z,

,6,B,M,V,a,j,z,

,6,B,M,V,a,

,6,B,M,V,a,

,6,B,M,V,a,j,z,

,6,B,M,V,a,

,6,B,M,V,a,

+*'_'

,6,B,M,V,a,j,z,

=,B,M,V,a,

   $$$(((

222888???

=VEu0

S$N$X$

L'A'S'U'X'

tp;>0

89:;<=>?

7,7>7U7

+*'_'

7,7>7U7

+*'_'

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

LOGIN

LOGOUT

CLUSTERUSERS

CONNECT

DISCONNECT

VOLUMEDIR

CONNECTPRINTER

DISCONNECTPRINTER

PRINTERLIST

PRINTERSTATUS

CREATE

DELETE

ERROR

MODIFY

UNISYSMONOMENU

MONOMENU

COLORMENU

C:\VPC\PEMM.EXE

                                                

                                                         

\LANCE

\LANCE

s\WIN.INI

\CLUSTER

\CLUSTER\RS485.EXE

\CLUSTER\RS485EM.EXE

\CLUSTER\RS422.EXE

\CLUSTER\RS422EM.EXE

\CLUSTER\CSKNAMES.OBJ

\CLUSTER\ABRESET.EXE

\CLUSTER\PRTSC.EXE

\CLUSTER\README.DOC

\CLUSTER\REDIR.EXE

\CLUSTER\CLUSTER.BAT

\CLUSTER\CLUSTERE.BAT

\CLUSTER\NETBIOS.EXE

\CLUSTER\CS.EXE

\LANCE

s\INSHELP > NUL:

s\INSFILES.LAN INSFILES > NUL:

s\INSFILES > NUL:

s\LANCE\REDIR.

c00 REDIR.EXE > NUL:

s\LANCE\RS422.EXE 

s\LANCE\RS422.EXE > NUL:

s\LANCE\RS485.EXE 

s\LANCE\RS485.EXE > NUL:

s\LANCE\RS485EM.EXE 

s\LANCE\RS485EM.EXE > NUL:

s\WINSTALL.EXE \LANCE             

s\INSTALL.EXE \LANCE\WINSTALL.EXE > NUL:

CDROM

s\CDROM

s\CDROM\AUTOEXEC.PCE \CDROM > NUL:

s\CDROM\AUTOEXEC.PC \CDROM > NUL:

s\LANCE\CTRQRS4.EX_ \LANCE             

s\LANCE\CTRQRS4.EX_ \LANCE > NUL:

s\LANCE\CTRQRS4.IN_ \LANCE             

s\LANCE\CTRQRS4.IN_ \LANCE > NUL:

s\LANCE\CTOSRQ.DL_ \LANCE             

s\LANCE\CTOSRQ.DL_ \LANCE > NUL:

s\LANCE\CTOSAPI.DL_ \LANCE            

s\LANCE\CTOSAPI.DL_ \LANCE > NUL:

\LANCE\INSFILES

\LANCE\INSHELP

s \LANCE\CTRQRS4.EX_ 

s\CTRQRS4.EXE > NUL

s \LANCE\CTRQRS4.IN_ 

s\CTRQRS4.INI > NUL

s \LANCE\CTOSRQ.DL_ 

s\CTOSRQ.DLL > NUL

s \LANCE\CTOSAPI.DL_ 

s\CTOSAPI.DLL > NUL

inshelp

insfiles

s > NUL:

s\oldaexec.bat

s\autoexec.bat

\lance

\LANCE

s\LANCE;

s\LANCE

s\oldwin.ini

s\win.ini

[windows]

ctrqrs4.exe

CTRQRS4.EXE

s=CTRQRS4.EXE

ConvergentClusterCard

UNISYS

Insert the second diskette and press ENTER.

        All Rights Reserved 

\LANCE

\CDROM

Press any key to copy files     

All installation diskettes copied.

Copying 

..done

Press any key to exit.

This installs the CTOS LANce

pc optional Windows components.

This installs the CTOS LANce

pc release diskette onto your hard disk.

Specify where to install the LANCE and CDROM directories.

Type a drive letter and press ENTER: 

(Press ESC to cancel installation)

Invalid choice

  Please try again...

NOTE: ClusterShare software (CS 1.3 or CS 2.0) will be

deleted from the disk where CTOS LANce

pc is installed.

Press any key to continue...

Clustered PC (8

bit ClusterCard)                  =  1

Clustered PC (16

bit ClusterCard or ClientCard)   =  2

PC on an Ethernet or Token

Ring LAN               =  3

Type the number for your configuration and press ENTER: 

Press any key to install the software.

CTOS LANce

pc successfully installed

Press any key to exit the installation program.

Installation of CTOS LANce

pc is complete.

Adding CTRQRS4 entries to WIN.INI ...            

*** NOTE: You may need to adjust the following parameters (manually) ***

LASTDRIVE, FILES and BUFFERS    in \CONFIG.SYS

:XBlocks: and :MaxXBlocksOut:   in [sys]<sys>Config.sys

:ServerLargeRequests:           in [sys]<sys>BNetConfig.sys

:Max OSI Message Size:          in [sys]<sys>BNetConfig.sys

:Buffer Size:                   in [sys]<sys>BNetSessionConfig.sys

(See \LANCE\README.DOC for more information.)

SB and 

Z switches for REDIR   in \LANCE\NET.BAT

See LANce.doc for configuration suggestions on floppy disk.

(NOTE: A ClusterCard is installed in this machine.)

(NOTE: A ClientCard is installed in this machine.)

DOS platform:

CTOS platform:

NOTE: Microsoft Windows is not installed on this machine

 If you install

 it later, you must copy LANce

pc DLLs to \WINDOWS and modify WIN.INI

Press any key to continue ...

CTOS LANce

pc contains optional Windows components.

Please supply the full path specification for the directory

where you have installed Windows (for example, C:\WINDOWS).

If Windows is not already installed, press ENTER.

If you wish to abort the installation, press ESC.

Windows is in the directory: 

EXPAND

Not enough memory to open window

Not enough memory to open window

Not enough memory to allocate scroll buffer

_C_FILE_INFO=

  0PX

000WP

ppxxxx

(null)

         (((((                  H

COMSPEC

COMSPEC

command.com

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

CDROM

CD001

\NEWELL.DAN

EMMXXXX0

SMSqS

TATZTtT

U2UBUWUnU

UCDR100: Unknown error

CDR101: Not ready

CDR102: EMS memory no longer valid

CDR103: CDROM not High Sierra or ISO

9660 format

CDR104: Door open

DN0:\DN

DNMSCDEX

<\t6*

<dr*<hw

Y0Y0Y0Y0v

Y0Y0Y0Y0Y0

Y0Y0Y0Y0

Y0Y0Y0Y0Y0Y0Y0Y0Y0Y0Y0

080Y0

=\\uY

r1< u

r(< u

caBuffer

      Drive 

c: = Driver 

s unit 

Device driver not found: '

No valid CDROM device drivers selected

Not enough drive letters available

Insufficient memory

Insufficient far memory

Not enough expanded memory, reducing number of buffers

Expanded memory allocation error

uld  bytes free memory

uld  bytes expanded memory

ud   bytes CODE

uld  bytes static DATA

uld  bytes dynamic DATA

uld  bytes used

usage: MSCDEX [

F:<pathname>] [

D:<driver> ... ]

L:<drive letter>] [

M:<value>]

Expanded memory not present or not

usable

Illegal option '

Illegal option

Cannot share drives

Incorrect DOS version

MSCDEX Version 

d already started

MSCDEX Version 2.20

Copyright (C) Microsoft Corp. 1986, 1987, 1988, 1989, 1990. All rights reserved.

Unable to load translated messages

Packed file is corrupt

;    Translation:  USA

; File MSCDEX.MSG 

 Message file for MSCDEX.EXE CD

ROM FILE SYSTEM

;**************************************************************************

;  NOTE TO TRANSLATOR: TRANSLATE THE INFORMATION BETWEEN QUOTES 

 ONLY.

;  If more than one line is needed, begin the next line with db followed

;  by the text between 

 and end each line with 0dh,0ah. Thanks.

;  Do not remove or translate 

d as these mark

;  replaceable parameters for MSCDEX.EXE.

;  Use the ';' (semi

colon) character to mark non

message lines.

;**************************************************************************

; msg0 db 

CDR100: Unknown error

,0dh,0ah

  msg0 db 

CDR100: Unknown error

,0dh,0ah

       db '$'

; msg1 db 

CDR101: Not ready

,0dh,0ah

  msg1 db 

CDR101: Not ready

,0dh,0ah

       db '$'

; msg2 db 

CDR102: EMS memory no longer valid

,0dh,0ah

  msg2 db 

CDR102: EMS memory no longer valid

,0dh,0ah

       db '$'

; msg3 db 

CDR103: CDROM not High Sierra or ISO

9660 format

,0dh,0ah

  msg3 db 

CDR103: CDROM not High Sierra or ISO

9660 format

,0dh,0ah

       db '$'

; msg4 db 

CDR104: Door open

,0dh,0ah

  msg4 db 

CDR104: Door open

,0dh,0ah

       db '$'

; msg5 db 

Drive 

c: = Driver 

s unit 

,0dh,0ah

  msg5 db 

Drive 

c: = Driver 

s unit 

,0dh,0ah

       db '$'

; msg6 db 

Device driver not found: '

,0dh,0ah

  msg6 db 

Device driver not found: '

,0dh,0ah

       db '$'

; msg7 db 

No valid CDROM device drivers selected

,0dh,0ah

  msg7 db 

No valid CDROM device drivers selected

,0dh,0ah

       db '$'

; msg8 db 

Not enough drive letters available

,0dh,0ah

  msg8 db 

Not enough drive letters available

,0dh,0ah

       db '$'

; msg9 db 

Insufficient memory

,0dh,0ah

  msg9 db 

Insufficient memory

,0dh,0ah

       db '$'

; msg10 db 

Insufficient far memory

,0dh,0ah

  msg10 db 

Insufficient far memory

,0dh,0ah

        db '$'

; msg11 db 

Not enough expanded memory, reducing number of buffers

,0dh,0ah

  msg11 db 

Not enough expanded memory, reducing number of buffers

,0dh,0ah

        db '$'

; msg12 db 

Expanded memory allocation error

,0dh,0ah

  msg12 db 

Expanded memory allocation error

,0dh,0ah

        db '$'

; msg13 db 

bytes free memory

,0dh,0ah

  msg13 db 

bytes free memory

,0dh,0ah

        db '$'

; msg14 db 

bytes expanded memory

,0dh,0ah

  msg14 db 

bytes expanded memory

,0dh,0ah

        db '$'

; msg15 db 

bytes CODE

,0dh,0ah

  msg15 db 

bytes CODE

,0dh,0ah

        db '$'

; msg16 db 

bytes static DATA

,0dh,0ah

  msg16 db 

bytes static DATA

,0dh,0ah

        db '$'

; msg17 db 

bytes dynamic DATA

,0dh,0ah

  msg17 db 

bytes dynamic DATA

,0dh,0ah

        db '$'

; msg18 db 

bytes used

,0dh,0ah

  msg18 db 

bytes used

,0dh,0ah

        db '$'

; msg19 db 

usage: MSCDEX [

D:<driver> ... ] [

L:<letter>] [

M:<buffers>]

,0dh,0ah

  msg19 db 

usage: MSCDEX [

D:<driver> ... ] [

L:<letter>] [

M:<buffers>]

,0dh,0ah

        db '$'

; msg20 db 

Expanded memory not present or not

usable

,0dh,0ah

  msg20 db 

Expanded memory not present or not

usable

,0dh,0ah

        db '$'

; msg21 db 

Illegal option '

,0dh,0ah

  msg21 db 

Illegal option '

,0dh,0ah

        db '$'

; msg22 db 

Illegal option

,0dh,0ah

  msg22 db 

Illegal option

,0dh,0ah

        db '$'

; msg23 db 

Cannot share drives

,0dh,0ah

  msg23 db 

Cannot share drives

,0dh,0ah

        db '$'

; msg24 db 

Incorrect DOS version

,0dh,0ah

  msg24 db 

Incorrect DOS version

,0dh,0ah

        db '$'

; msg25 db 

MSCDEX Version 

d already started

,0dh,0ah

  msg25 db 

MSCDEX Version 

d already started

,0dh,0ah

        db '$'

; msg26 db 

MSCDEX Version 2.20

,0dh,0ah

  msg26 db 

MSCDEX Version 2.20

,0dh,0ah

        db '$'

; msg27 db 

Copyright (C) Microsoft Corp. 1986, 1987, 1988, 1989, 1990. All rights reserved.

,0dh,0ah

  msg27 db 

Copyright (C) Microsoft Corp. 1986, 1987, 1988, 1989, 1990. All rights reserved.

,0dh,0ah

        db '$'

; msg28 db 

Unable to load translated messages

,0dh,0ah

  msg28 db 

Unable to load translated messages

,0dh,0ah

        db '$'

echo off

CLOCAL

    goto CLOCAL

clocal

    goto CLOCAL

ELOCAL

    goto ELOCAL

elocal

    goto ELOCAL

CPEER

     goto CPEER

cpeer

     goto CPEER

EPEER

     goto EPEER

epeer

     goto EPEER

      goto CLAN

      goto CLAN

      goto ELAN

      goto ELAN

goto  ERROR_PARA

:CLOCAL

c:\Lance\rs485 

c:\Lance\Session 

c:\Lance\redir 

p1:3584 

SB:3584 

Z:3584

goto EXIT

:ELOCAL

c:\Lance\rs485em 

c:\Lance\Session 

c:\Lance\redir 

p1:3584 

SB:3584 

Z:3584

goto EXIT

:CLAN

c:\Lance\rs485 

c:\Lance\Session 

c:\Lance\NetBIOS

c:\Lance\SetName PC1

c:\Lance\redir 

p1:4356 

SB:4356 

Z:4356

goto EXIT

:ELAN

c:\Lance\rs485em 

c:\Lance\Session 

c:\Lance\NetBIOS

c:\Lance\SetName PC1

c:\Lance\redir 

p1:4356 

SB:4356 

Z:4356

goto EXIT

:CPEER

c:\Lance\rs485 

c:\Lance\NetBios

goto EXIT

:EPEER

c:\Lance\rs485em 

c:\Lance\NetBios

goto EXIT

:ERROR_PARA

echo This .Bat file requires one of the following parameters:

echo CLOCAL or clocal = install on clustered PC for accessing local server.

echo ELOCAL or elocal = install on PC Em

Vpc for accessing local server.

echo CPEER  or cpeer  = install on clustered PC for peer

peer comm.

echo EPEER  or epeer  = install on PC Em

Vpc for peer

peer comm.

echo CLAN   or clan   = install on clustered PC for accessing LM server.

echo ELAN   or elan   = install on PC Em

Vpc for accessing LM server.

:EXIT

PQRSTUVW

_^][[ZYX

':'O'd'

PQRSTUVW

_^][[ZYX

t$<\t

t'<\t

s6BSQ

_^][[Z

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

SMB0123456789ABCDEF

NETBIOS

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

Invalid BNet node name.

NetBios Interface already installed.

LANce

pc RS4XX

EM Driver is not installed.

Cannot use LANce

pc NetBIOS on a LAN PC.

Could not set size of memory block.

Could not allocate exchange.

(This TSR serves INT 5Ch, hooks INT 1Ch)

_C_FILE_INFO=

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

t$<\t

t'<\t

,at[,

,+t$,7t>

$\, <Xw

<st'<ntQ<pt

s6BSQ

7t3)G

7t.)G

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

[sys]<sys>mfd.sys

c:\dos\command.com

[sys]<sys>mfd.sys

Login

Logout

ClusterUsers

Connect

Disconnect

VolumeDir

Connect

Disconnect

Status

Create

Delete

Error

Modify

AddName

DelName

Listen

Receive

Hangup

 SignOn   

 File   

 Printer   

 Admin   

 Diag   

Retry

Cancel

OoLlRrLOGIN

LOGOUT

CLUSTERUSERS

CONNECT

DISCONNECT

VOLUMEDIR

CONNECTPRINTER

DISCONNECTPRINTER

PRINTERLIST

PRINTERSTATUS

CREATE

DELETE

ERROR

MODIFY

UNISYSMONOMENU

MONOMENU

COLORMENU

Directory Access Denied

  Adapter Number 

Invalid BNet name. Name size is 1 

 12 characters                              

Invalid local device

Invalid Directory name. Name size is 1 

 12 characters                         

Invalid local drive

Invalid local device. Valid local device: LPT1, LPT2, LPT3                     

Invalid local drive. Valid local drives D: 

 Z:                                

Invalid NetBIOS name. Name size is 1 

 16 characters                           

Invalid network device

Invalid network drive

Invalid Resource name. Name size is 1 

 8 characters                           

Invalid name syntax

Invalid Volume name. Name size is 1 

 12 characters                            

Binary Mode Off

Binary Mode On

Terminating connection of 

Press ESC to Cancel

CD ROM Drives

CloseFile error

Cluster error 

    Users on CTOS Server

Command Successful

All connections will be terminated. (Y

N) ?:

All connections will be terminated

connected to

Copyright (C) UNISYS Corp 1992, 1993, 1994

Create directory error 

CTOS Printer

  Data  

Delete directory error 

Device

Create failed

Create successful

Modify failed

Modify successful

Delete failed

Delete successful

  ...Done. Enter new directory to continue or press ENTER to stop

Directory Name

Dir Password  

Vol Password

disconnected

Dos file open error

Error Code = 

File Names 

File not found

File Protection Violation

file size 

Directory error 

Printer error 

F1=HELP

  Cannot fetch the help screen

File.hlp file missing from \LANce

Missing input

CTOS LANce

pc Network Shell

Press any key to proceed

LAN error 

Local Device  

Local Drive  

  LocalName            

Please log in first

Login error 

Login failed

Login Name

Login successful

Logout successful

CTOS LANce

pc driver (RS422

RS485

RS485EM

RqAgent) not loaded                       

LocalDevice parameter missing                                                  

LocalDevice and

or NetworkDevice parameters missing                            

\BnetNodename\Volume\Directory parameter missing                               

LocalDrive parameter missing                                                   

LocalDrive and

or NetworkDrive parameters missing                              

\BnetNodeName\Volume\Dir, NewDirPassword and

or OldDir

VolPassword missing     

Printer name required

User name missing                                                              

  NetBios not installed

DOS machine name

       NETWORK CONTROL BLOCK

Network Drive

Network Device

New Dir Password    

No connections

No CTOS error logged

Drive

Device not connected

   Not Set   

Old Dir

Vol Password

OpenFile error 

Password     

PC ASCII Mode

Printer

 CTOS Name  DOS Name  Defeat

Image

Mode   Translate Characters

 PrinterName    BNetName   Spool  @Server  Banner    Location

Offline

Paused

Printing

CTOS LANce

pc Network Shell

ReadFile error 

Connect successful

Connect failed

Redirector not loaded

 Connection failed 

  RemoteName           

  Cannot Build This Request 

  Session Number

SetDirStatus error

SetFileStatus error

Too many parameters                                                            

Try again

Updating file protection for 

WriteFile error

Invalid name

Dos_Printer_Name

CTOS_Printer_Name

Defeat_Image_Mode

Translate_Characters

PC ASCII   

CTOS ASCII 

binary     

{none}     

LANce

pc GPS Remote Printer Directory:

CTOS Name     DOS Alias  BNet Node     Expects    Physical Location

LANce

pc Remote Printer Directory:

CTOS Name     DOS Alias  BNet Node     Expects

WARNING: Too many printers configured to permit display

         maximum size of GetGpsNetList response exceeded

         additional printers not shown.

Use the name from the 

DOS Alias

 column with the 

NS ConnectPrinter

command.  Edit the 

SMBPTRMAP.CFG

 file on the DOS Network Drive

\\server\local\sys\lance

 to define additional DOS Names

for a CTOS Name, e.g. to support different output modes.

Where {none} appears, you must define a DOS Name (by editing the file)

if you wish to use that printer, because its CTOS Name is not a valid

DOS Name.

|                        Valid NS Commands (Abbreviation)                      |

|                                                                              |

|        Signon                  File                    Printer               |

|   LogIn        (LI)      Connect        (C)      ConnectPrinter    (CP)      |

|   LogOut       (LO)      Disconnect     (D)      DisconnectPrinter (DP)      |

|   ClusterUsers (CU)      List           (L)      PrinterList       (PL)      |

|                          VolumeDir      (VD)     PrinterStatus     (PS)      |

|                                                                              |

|        Admin                  Menu                     Help                  |

|   CReate       (CR)      ColorMenu      (CM)     Help         (H)            |

|   DElete       (DE)      MonoMenu       (MM)                                 |

|   Error        (E)       UnisysMonomenu (UM)                                 |

|   MOdify       (MO)                                                          |

|                                                                              |

|   Type NS Help           for usage information on all commands.              |

|   Type NS Help Command   for usage information on a specific command.        |

                             Help for NS Commands                               

                                                                                

  Help about NS commands is grouped by function, with each function on a        

  separate help pannel. The functions are :                                     

                 SignOn   File   Printer   Admin   Menu                         

                                                                                

                                                                                

  For each command, the following information appears:                          

     The full command name (example:  NS LogIn), a short description of         

     the command, and usage instructions (example:  NS LI UserName).            

                                                                                

                                                                                

  The notation conventions are:                                                 

     Command abbreviations are shown in the usage instructions (example: LI),   

     but the full command is also valid (example: LogIn).                       

                                                                                

     Capitalized words indicate actual keystrokes (example: SERVER).            

                                                                                

     Initial capitalized words indicate the type of information required        

     (example: UserName).                                                       

                                                                                

     Brackets ([ ]) indicate optional inputs (example: [Password]).             

                                                                                

                         

 Press any key to continue 

                        

                            Help for SignOn Commands                            

                                                                                

                                                                                

   NS LogIn                                                                     

     Identifies the clustered PC or Vpc to the CTOS server.                     

     Usage:   NS LI UserName                                                    

                                                                                

                                                                                

   NS LogOut                                                                    

     Disconnects all local drives and devices connected to network drives       

     and devices.                                                               

     Usage:  NS LO                                                              

                                                                                

                                                                                

   NS ClusterUsers                                                              

     Lists users currently logged on to the CTOS server.                        

     Usage:  NS CU                                                              

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                                                                                

                         

 Press any key to continue 

                        

                             Help for File Commands                             

  NS Connect                                                                    

    Connects a local DOS drive (E: 

 Z:) to a CTOS or LAN network drive.        

    Usage for a clustered PC or Vpc connecting to a CTOS directory:             

      NS C LocalDrive \\SERVER\LOCAL\Volume\Directory [Password]                

      NS C LocalDrive \\SERVER\BNetNodeName\Volume\Directory [Password]         

    Usage for a clustered PC or Vpc using the DOS BACKUP command:               

      NS C LocalDrive \\SERVER\CTOSResourceName [Password]                      

    Usage for a clustered PC or Vpc connecting to a LAN resource:               

      NS C LocalDrive \\NetBIOSName\ResourceName [Password]                     

    Usage for a PC on a LAN connecting to a CTOS directory:                     

      NS C LocalDrive \\NetBIOSName\LOCAL\Volume\Directory [Password]           

    Usage for a PC on a LAN connecting to a CTOS directory across BNet:         

     NS C LocalDrive \\NetBIOSName\BNetNodeName\Volume\Directory [Password]     

  NS Disconnect                                                                 

    Disconnects a local DOS drive (E: 

 Z:) from its connection.                

    Usage:  NS D LocalDrive                                                     

  NS List                                                                       

    Lists all network drives and devices currently connected.                   

    Usage:  NS L                                                                

  NS VolumeDir                                                                  

    Lists all directories in <Sys> on your server.                              

    Usage:  NS VD                                                               

                         

 Press any key to continue 

                        

                            Help for Printer Commands                           

                                                                                

  NS ConnectPrinter                                                             

    Connects a local printer device (LPT1, LPT2, or LPT3) to a network          

    printer device.                                                             

    Usage for connecting to CTOS printer:                                       

      NS CP LocalDevice \\SERVER\DeviceName                                     

    Usage for connecting to LAN printer:                                        

      NS CP LocalDevice \\NetBIOSName\DeviceName                                

                                                                                

  NS DisconnectPrinter                                                          

    Disconnects a local printer device (LPT1, LPT2, or LPT3) from a network     

    device.                                                                     

    Usage:  NS DP LocalDevice                                                   

                                                                                

  NS PrinterList                                                                

    Lists all available printers on the CTOS server. (For connected printers,   

    see NS LIST.)                                                               

    Usage:  NS PL                                                               

                                                                                

  NS PrinterStatus                                                              

    Displays the current status of a selected CTOS server printer.              

    Usage:  NS PS CTOSPrinterName                                               

                         

 Press any key to continue 

                        

                             Help for Admin Commands                            

                                                                                

                                                                                

  NS CReate                                                                     

    Creates a CTOS directory.                                                   

    Usage:  NS CR \BNetNodeName\Volume\Directory [DirectoryPassword]            

                                                                                

  NS DElete                                                                     

    Deletes an empty CTOS directory.                                            

    Usage:  NS DE \BNetNodeName\Volume\Directory [Dir

VolPassword]              

                                                                                

  NS Error                                                                      

    Displays the last CTOS error logged by the SMB Service.                     

    Usage:  NS E                                                                

                                                                                

  NS MOdify                                                                     

    Usage to add or change a password on a CTOS directory.                      

    NS MO \BNetNodeName\Volume\Directory NewDirPassword OldDir

VolPassword      

                                                                                

    Usage to delete a password from a CTOS directory.                           

    NS MO \BNetNodeName\Volume\Directory OldDir

VolPassword                     

                                                                                

                                                                                

                         

 Press any key to continue 

                        

                                                                                

                             Help for Menu Commands                             

                                                                                

   NS ColorMenu                                                                 

     Starts the Network Shell menu on a color monitor.                          

     Usage:  NS CM                                                              

                                                                                

                                                                                

   NS MonoMenu                                                                  

     Starts the Network Shell menu on a monochrome monitor.                     

     Usage:  NS MM                                                              

                                                                                

                                                                                

   NS UnisysMonomenu                                                            

     Starts the Network Shell menu on a Unisys monochrome monitor.              

     Usage:  NS UM                                                              

                                                                                

                                                                                

   NS Help                                                                      

     Displays help information for all NS commands or a specific NS             

     command.                                                                   

     Usage:  NS H [Command]                                                     

                                                                                

                                                                                

Normal return

Illegal buffer length

Invalid command

Command timed out

Message incomplete

Illegal local session number

No resource available

Session closed

Command cancelled

Duplicate name in local name table

Name table full

Name has active session 

 is now deregistered

Local session table full

Session open rejected

Illegal name number

Cannot find name called

Name not found or cannot specify 

 or null

Name in use on remote NETBIOS interface

Name deleted

Session ended abnormally

Name conflict detected

Interface busy

Too many commands outstanding

Invalid number in adapter number field

Command completed while cancel occurring

Command not valid to cancel

Ring status; bits 12,14,15 on for > 60 seconds

Ring status; one or more of bits 8

11 on

Error on implicit DIR.INITIALIZE

Error on implicit DIR.OPEN.ADAPTER

Adapter support interface internal error

Adapter check

NETBIOS program not loaded in PC

DIR.OPEN.ADAPTER or DLC.OPEN.SAP failed

Unexpected adapter close

characters sent 

Node Number 

d returned

Session Number 

d returned

characters received 

Data :

Press ESC to continue

 <unknown> 

       

Server

SPOOLERSTATUS

SPOOLERSTATUS

file.hlp

[Sys]<LANce>SMBPtrMap.cfg

[Sys]<LANce>SMBPtrMap.cfg

Sys]<LANce>SMBPtrMap.cfg

Sys]<LANce>SMBPtrMap.cfg

Server not running or cluster line has been broken.

Service not available.

Directory is full.

No such file.

No such directory on that volume.

Invalid file specification.

File is read

only.

Invalid file handle (master may have been rebooted).

No such volume or device.

Volume not mounted.

Invalid password.

Access denied (password required).

File in use.

File already exists.

No free file headers.

Disk full or too fragmented.

Invalid request for device.

Invalid device specification.

Directory already exists.

Directory not empty, cannot remove it.

MFD is full (no more directories allowed on volume).

Write protected.

Invalid CT

Net node name.

Not enough memory to open window

Not enough memory to open window

Not enough memory to allocate scroll buffer

Out of Memory

Out of Memory

Out of Memory

Out of Memory

Out of Memory

QWERTYUIOPASDFGHJKLZXCVBNM

_C_FILE_INFO=

  0PX

000WP

ppxxxx

(null)

         (((((                  H

COMSPEC

B^G^L^PATH

COMSPEC

command.com

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

VWPSU

][X_^

       =========================  

       CTOS LANce

pc Release 1.2

      March 1994

       =========================

CONTENTS

 1.0 Scope of README.DOC

 2.0 Product Overview

 3.0 System Requirements

 4.0 Getting Started

 5.0 Using CTOS LANce

 6.0 Accessing the CTOS CD

ROM Drive

 7.0 Using the TBACKUP and TRESTORE Commands

 8.0 Using the RQNAMES Library

 9.0 Corrections

10.0 Restrictions and Known Limitations

11.0 Migration and Coexistence

12.0 Support

1.0  SCOPE

This specification briefly describes the general installation, software 

and hardware requirements, and the functionality of the CTOS LANce

software.  For more details refer to the 

CTOS LANce

pc and LANce

Administration and Programming Guide

 packaged with the CTOS LANce

product.  This specification discusses using the LANce

pc product alone, 

without the LANce

LM product.

Note:  The documentation about installing LANce

pc contained in the

       

CTOS LANce

pc and LANce

LM Administration and Programming

       Guide

 is superseded by this document.

2.0  PRODUCT OVERVIEW

CTOS LANce

pc Without CTOS LANce

CTOS LANce

pc enables DOS clients to access the services of a CTOS server.

Clustered PCs and CTOS

Vpc workstations connect directly to the CTOS server 

and become part of the CTOS cluster configuration.

CTOS services that may be available for clustered PCs or CTOS

workstations include:

  CTOS CD

ROM utilities, for access to the CTOS CD

ROM drive

  CTOS QIC tape utilities or the CTOS Sequential Access Service

  CTOS SNA Transport

  CTOS OFIS Mail

  MCS II

LANce

pc also provides a library of CTOS calls that can be linked 

with DOS applications to enable those applications to use services 

provided on the CTOS server.

LANce

pc provides support for applications linked with the 

ClusterShare Sockets library packaged with CTOS TCP

IP and other 

ClusterShare applications that can run over the connection established by 

LANce

pc to the CTOS server.

LANce

pc provides support for making CTOS requests from Windows

applications. 

CTOS LANce

pc With CTOS LANce

When used in conjunction with LANce

LM, LANce

pc enables PCs on an 

Ethernet or Token

Ring LAN to access the following CTOS server services:

  CTOS QIC tape utilities or the CTOS Sequential Access Service, for 

   creating backups of DOS environments

  CTOS SNA Transport

  CTOS OFIS Mail

When LANce

LM is installed on the CTOS server, DOS clients running 

LANce

pc have the following additional functionality:

  Access to CTOS files and printer services

  Access to file and printer services on a LAN server (clustered PCs and 

   CTOS

Vpc workstations)

  Peer

peer NetBIOS communication across the LAN (clustered PCs and 

   CTOS

Vpc workstations)

  Ability to boot off the CTOS server (clustered PCs only)

  Ability to perform certain network and administration services

Components of LANce

The LANce

pc software components listed below can work in 

configurations that include LANce

LM as well as configurations that do not.  

ROM utilities

   These utilities enable clustered PCs and CTOS

Vpc workstations to access 

   the CD

ROM drive on the CTOS server.

  RS485

   This TSR application connects a clustered PC to a CTOS server through the 

   AT

bus ClusterCard or ClientCard.

  RS422

   This TSR application connects a clustered PC to a CTOS server through the 

   XT

bus ClusterCard.

  RS485EM

   This TSR application connects the CTOS

Vpc environment to the underlying 

   CTOS environment.

  CTOSRQ, CTRQRS4, and CTOSAPI DLLs

   These DLLs support making CTOS requests from Windows applications

   running on a clustered PC. 

  RQNAMES.LIB

   This library provides a set of CTOS calls that can be linked with DOS 

   applications.

  Tape utilities

   These utilities enable you to use a CTOS tape module to backup and restore 

   files on your DOS hard disk.  Similar to the DOS BACKUP command, TBACKUP 

   backs up DOS files to a tape in the first CTOS tape module installed on

   the CTOS server.

   Similar to the DOS RESTORE command, TRESTORE restores DOS files backed up 

   using the TBACKUP command.

Components of LANce

pc for Use with LANce

LANce

pc contains the following software components that can be used in 

conjunction with LANce

LM.  All of the components are DOS components, 

except for AutoBoot, which is a CTOS component.

  AutoBoot utilities

   These utilities enable a clustered PC to boot from the CTOS server.  Note 

   that PCs with partitioned hard disks cannot boot from the CTOS server.  

   AutoBoot may be most useful for diskless PCs.

  Network Shell (NS)

   This utility provides an interface for accessing CTOS server and LAN

   server resources, and for performing some network administrative tasks.

  SESSION

   This TSR application provides backward compatibility to the ClusterShare 

   2.0 NetBIOS.  Together with SMB Service, SESSION allows access to files 

   and printers on CTOS or LAN servers.  SESSION runs on a DOS client.  SMB 

   Service runs on a CTOS workstation and is packaged with LANce

  REDIR (redirector)

   This Microsoft TSR application enables you to create logical connections

   from DOS clients to network drives and printers on the server.

  SETNAME

   This utility accepts a user

specified 16

character name used by REDIR as 

   its NetBIOS name.  This name is necessary when the DOS client is 

   a PC on a LAN.

  NETBIOS

   This TSR application is comparable to the NetBIOS library on CTOS.  

   Together with NetBIOS Service, this TSR provides an interface to the IBM

   NetBIOS Extended User Interface (NetBEUI) standard that can be used 

   locally to obtain peer

peer communications within the cluster or LAN

   environment.  NetBIOS Service runs on a CTOS workstation and is packaged

   with LANce

  RQ AGENT

   When used with RQ Service, this TSR application creates an interface that 

   routes requests for CTOS services, such as mail, communications gateway 

   and tape utilities, from a PC on a LAN.  RQ Agent runs on a PC on a LAN. 

   RQ Service runs on a CTOS workstation and is packaged with LANce

3.0  SYSTEM REQUIREMENTS

HARDWARE:

CTOS LANce

pc requires one of the following hardware systems:

  An IBM or compatible PC

   Clustered PCs must have one of the following cards to connect 

   to the CTOS server:

bit XT

bus ClusterCard

bit AT

bus ClusterCard

  ClientCard (included with an EISA

ISA client workstation)

  ClusterPort (for SuperGen Series 1000)

   PCs on a LAN must have Ethernet or Token

Ring cards to connect to the

   LAN.

  A CTOS

Vpc workstation.  For information about the types of CTOS 

   workstations supported, see the documentation associated with the 

   CTOS

Vpc or PC Emulator product.

   Note: Except where explicitly stated, for the remainder of this 

 document, 

 will refer collectively to both CTOS

 and PC Emulator.

SOFTWARE:

CTOS LANce

pc requires the following software for the PC workstation:

DOS, release 3.3 or higher

     or

   DR DOS, release 6.0 or higher

   Notes:

      

      1.  The capability to make CTOS requests from a Windows application

    is only supported on MS

DOS 5.0 or 6.0.

     

      2.  LANce

pc is not supported on OS

The LANce

pc software requires one of the following emulator products for 

the CTOS workstation:

  CTOS

Vpc, release 1.2 or higher

   Note:  The capability to make CTOS requests from a Windows application

  is only supported on CTOS

Vpc 2.0 or higher.

  CTOS PC Emulator, release 4.2 or higher

   Note:  CTOS PC Emulator is required for systems running 

  BTOS II 3.2.

The LANce

pc supports the following software:

  Microsoft Windows, release 3.0 or higher

   Notes:  

      1. A clustered PC running Windows 3.0 does not support enhanced 

   mode.  If you try to use it, you will bring down the network.

   Windows 3.1 enhanced mode is supported.

      2. The RS422 driver (which supports the XT

bus ClusterCard) 

 does not support Windows 3.0 or 3.1 enhanced mode.

      3. You cannot switch out of LANce

pc applications when

 running under Windows in enhanced mode.  You must finish the

 application before moving to another application.

      4. The capability to make CTOS requests from a Windows application

 is supported only on Windows 3.1 or higher.  The capability is

 not supported for Windows for Workgroups.

  ClusterShare Mail release 1.0 or higher (for information about the 

   release levels of OFIS Mail supported for the CTOS environment, see the 

   ClusterShare Mail documentation)

  ClusterShare SNA 3270 Emulator release 1.0 or higher (for information 

   about the release levels of the SNA Transport supported for the CTOS 

   environment, see the ClusterShare SNA 3270 Emulator documentation)

  Applications linked with the ClusterShare Sockets library packaged with 

   CTOS TCP

IP release 2.0 or higher

LANce

pc supports the following software with the stated requirements:

  For CTOS CD

ROM drive access, LANce

pc requires that the CTOS server run 

   the CTOS CD

ROM Service release 1.0 or higher (or, as packaged with the 

   CTOS Standard Software Utilities release 12.1 or higher).

  For tape backups, LANce

pc requires that the CTOS server run the CTOS QIC 

   tape services (as packaged with the CTOS Standard Software Utilities 

   release 12.0) or the CTOS Sequential Access Service (as packaged with the 

   CTOS Standard Software Utilities release 12.1 or higher).

  For printing, LANce

pc requires that the CTOS server run either the 

   Generic Print System (GPS) or the Spooler.  LANce

pc supports GPS release 

   2.4 or higher.  LANce

pc supports the Spooler packaged with the CTOS 

   Standard Software Utilities release 12.0 or higher.  LANce

pc also 

   requires LANce

LM software for printing.

   For additional information about using CD

ROM, see 

6.0 Accessing the

   CTOS CD

ROM Drive

 in this document.

   For additional information about backing up DOS files using a CTOS tape

   module, see 

Using the TBACKUP and TRESTORE Commands

 in this document.

A PC on a LAN running LANce

pc in conjunction with LANce

LM must have 

one of the following products installed:

  DOS LAN Requester, release 1.3, 2.0, or 3.0

  The client software from LAN Manager, release 2.0, 2.1, or 2.2

RAM and Disk Usage

Depending upon your hardware configuration, some of the following files will

be copied into the specified directories during installation.

\LANCE Directory:

File            TSR RAM (K bytes)   Disk Size (K Bytes)

CTOSAPI.DL_ *           

                15

CTOSRQ.DL_  *           

                12

CTRQRS4.EX_ *           

                 7

CTRQR4.IN_  *           

                 1

FILE.HLP                

                 9

NET.BAT                 

                 2

NETBIOS.EXE            87                17

NS.EXE                  

                96

PRTSC.EXE               1                 1

README.DOC              

                57

REDIR.EXE              38                30

RQAGENT.EXE            40                18

RQNAMES.H               

                 5

RQNAMES.LIB             

                 3

RS422.EXE              29                28

RS485.EXE              33                34

RS485EM.EXE             3                 3

SESSION.EXE            47                 7

SETNAME.EXE             

                 5

TBACKUP.EXE             

                56

TRESTORE.EXE            

                58

WINSTALL.EXE *          

                54

* If you have the DLLs installed in the Windows directory, you can delete

  these files from your \LANCE directory.

\CDROM Directory:

File            TSR RAM (K bytes)   Disk Size (K Bytes)

AUTOEXEC.PC             

                 1

AUTOEXEC.PCE            

                 1

CDDRIVER.EXE            3                 5

CDR.EXE                 

                 9

CONFIG.SMP              

                 1

MSCDEX.EXE             32                26    

\WINDOWS Directory:

File            TSR RAM (K bytes)   Disk Size (K Bytes)

CTOSAPI.DLL           130                29

CTOSRQ.DLL             60                27

CTRQRS4.EXE            10 **              7

CTRQRS4.INI                               1

** CTRQRS4.EXE also consumes memory in the first megabyte of RAM, which is

   accessible from real mode.  The amount of RAM is calculated by multiplying

   the MaxPendingRequests specified in WIN.INI (default = 12) by 12, and

   multiplying again by the X

block size specified when installing RS485 

   (default 2.5KB).

4.0  GETTING STARTED

CTOS LANce

pc files can be installed onto a hard disk in one of 

two DOS environments:

  A hard disk on a PC.

  A hard disk on a CTOS workstation running CTOS

Vpc software.  The CTOS

   workstation can be the CTOS server or a client workstation.

   Notes: 

      1. When installing LANce

pc on DR

DOS, the screen scrolls up, causing

 an unusual appearance.  The scrolling does not interfere with proper

 installation.

      2. If installing onto a DR

DOS system or a DOS 3.3 system, manually

 copy REDIR.300 to REDIR.EXE to avoid getting error 

Wrong OS

 version.

  Overwrite the file AFTER you have completed the

 normal installation. 

      3. The documentation about installing LANce

pc contained in the 

CTOS LANce

pc and LANce

LM Administration and Programming

 Guide

 is superseded by this document.

To install LANce

pc software into a DOS environment, follow this

procedure:

1. Insert the first disk labeled 

CTOS LANce

pc R1.2 DOS disk set

 into

   any floppy drive.  

   Note:  Although you can use any floppy drive, this procedure

  refers to floppy drive A.

2. In the command line, type the following command; then press ENTER.

       A:\Install 

       

3. Follow the instructions on the screen.  The installation program does

   the following:

  Removes ClusterShare software from your PC

  Prompts for the destination hard drive to install LANce

pc software

  Prompts for your hardware configuration (except for CTOS

      

  Clustered PC(XT

bus ClusterCard)            = 1

      

  Clustered PC(AT

bus ClusterCard

ClientCard) = 2

      

  PC on a LAN                                 = 3

  Prompts for the name of your Windows directory        

  Copies the appropriate software into the 

LANCE, 

CDROM, and

      

WINDOWS directories

4. After the software is copied, you need to check the values assigned

   to the following DOS parameters and switches:

  In CONFIG.SYS, check the LASTDRIVE, FILES, and BUFFERS parameters.

      See your DOS documentation for information about these settings.                                                   

      Also refer to the description of your network map to determine 

      proper settings for your configuration.

      Note:  PC Emulator adds LASTDRIVE=G to CONFIG.SYS.  

5. Since LANce

pc communicates with the CTOS server, it is vital to 

   review the configuration of the following parameters.  The CTOS and

   DOS configurations must be coordinated for proper communication.  See

11.0 Migration and Coexistence

 for more information.

   File                                Parameters

     

   [Sys]<Sys>BNetSessionConfig.sys     :Buffer Size:

   [Sys]<Sys>BNetConfig.sys            :ServerLargeRequests:

   [Sys]<Sys>BNetConfig.sys            :Max OSI Message Size:

   [Sys]<Sys>Config.sys                :XBlocks:  and  :MaxXBlocksOut:

6. If you are running DOS 6.0, you need to put the following entry in your

   CONFIG.SYS file: 

DEVICE=SETVER.EXE                                

5.0 USING CTOS LANce

Depending upon your hardware configuration and desired functionality, you

use different TSRs (Terminate and Stay Resident) from CTOS LANce

pc.  You 

can run the required TSRs individually or create your own batch file to

automate the procedure.

Note:  This document describes using LANce

pc without LANce

LM.  

       For information about using LANce

pc with LANce

LM, see the 

       

CTOS LANce

pc and LANce

LM Administration and Programming Guide.

       For information supplementing the guide, see 

11.0 Migration and 

       Coexistence

 in this file.

All clustered DOS clients need to use RS485, RS422, or RS485EM.  Clustered

PCs use RS485 or RS422, depending upon the hardware.  CTOS

Vpc workstations

use RS485EM.  RS485 and RS485EM allow you to specify the size of the X

blocks 

that are sent to the CTOS server.  If your CTOS server is configured for 4KB 

blocks, use the switch 

8 is the only valid value other than blank.  

The following is a sample command:

     

    \lance\rs485 

Note:  CTOS

Vpc release 2.0 is required to support 4KB X

blocks.

Using the TSRs

The following lists identify what TSRs are needed for different functions.

Note that the TSR identified as RS4xx is RS485 or RS422 for a clustered

PC and RS485EM for a CTOS workstation running CTOS

  To access communications, mail services, or applications linked with 

   RQNAMES:

   \LANCE\RS4xx switch          

   CS MAIL or CS 3270 or other RQNAMES applications  

      

   For more information, see 

8.0 Using the RQNAMES Library

 in this file.

  To access CD

ROM service:                               

   See the 

6.0 Accessing the CTOS CD

ROM Drive

 section in this file.

  To access tape utilities:

   \LANCE\RS4xx switch

   \LANCE\TRESTORE switches  or  \LANCE\TBACKUP switches

   For more information, see the 

7.0 Using the TBACKUP and TRESTORE 

   Commands

 section in this file.

Setting Up a Batch File

You can create your own batch file to run the components your

installation requires.  After you create the batch file, modify 

AUTOEXEC.BAT to 

 your batch file.  

6.0 ACCESSING THE CTOS CD

ROM DRIVE

Users of any system in the CTOS cluster running the LANce

pc software

can access a CD

ROM drive attached to the CTOS server.  CD

ROM software

includes two basic sets of software:  the CD

ROM System Service and the 

ROM PC software.

The CD

ROM System Service is installed on CTOS workstations only.

Like any other CTOS system service (for example, the Generic Print System or

the Mouse services), the CD

ROM System Service runs in the background, 

handling all the procedures necessary for the CD

ROM hardware and software 

to function with the CTOS operating system.

The CD

ROM System Service is packaged with the CTOS Standard Software

release 12.0 or higher.  Information about installing and troubleshooting 

this software is provided in various standard CTOS guides, including the 

CTOS System Administration and Programming Guide.

Note:  If you are using DOS 6.2, you must use the DOS version of MSCDEX.

       In this case, a sample entry would be:

       \DOS\MSCDEX.EXE 

CDROM 

The CD

ROM PC software runs on DOS and allows clustered PC or CTOS

users to read files from DOS CD

ROM discs through the CTOS CD

ROM driver.  

The CD

ROM PC software is packaged with the CTOS LANce

pc product.

Installing CD

ROM Software

When you install the LANce

pc software onto a PC workstation, you

automatically install the CD

ROM PC software packaged with LANce

Therefore, you don't need to do anything special to install the CD

ROM PC

software onto your PC workstation's hard disk.

After installing the software onto hard disk, however, you must

load the CD

ROM PC software into memory to use it.  You must also make sure

the CD

ROM System Service is installed and running on the CTOS server.

Installing CD

ROM software into memory consists of two steps:

1. Configuring and installing the CD

ROM System Service into memory on the

   CTOS server.

2. Configuring and loading the CD

ROM PC software into memory in DOS.

For information about configuring and installing the CD

ROM System Service

into memory, see the 

CTOS System Administration and Programming Guide

and the 

CTOS Executive Reference Manual.

Configuring the CD

ROM PC Software

To configure the CD

ROM PC software, you must update the DOS

CONFIG.SYS and AUTOEXEC.BAT files to ensure that the CD

ROM software and

device drivers are automatically installed when you start your PC

workstation.

The product disk includes three sample files, displaying the necessary

CONFIG.SYS and AUTOEXEC.BAT entries.

Example 1 shows the sample CONFIG.SYS file found on the product disk

in the file CONFIG.SMP.  Your DOS CONFIG.SYS file should look similar to

this file.

  Example 1.  Sample CONFIG.SYS File

  LASTDRIVE=Z   

  FILES=20   

  BUFFERS=30

  DEVICE=C:\CDROM\CdDriver.Exe 

CDROM 

  DEVICE=C:\DOS\SETVER.EXE

In the sample file, two lines are required to use the CD

ROM software:

  LASTDRIVE=Z

   This allows you to expand the number of CD

ROM drives you can access.  This

   line may be included in the file already.

  DEVICE=C:\CDROM\CdDriver.Exe 

CDROM 

This line includes two options:

  The entry after 

      This is the name of the DOS CD

ROM device driver.  This entry must

      be no more than eight characters long and must conform to DOS file

      name specifications.  You can enter any name, but it's probably easiest

      to use the name CT

CDROM.  Remember, however, that you can't have any

      other file by that name on your disk.

  The switch 

      This indicates how many CD

ROM modules your workstation can access.  For

      example, if your workstation can access one module, enter 

N:1;  if your

      workstation can access five modules, enter 

Editing the AUTOEXEC.BAT File

Example 2 shows a sample AUTOEXEC file, called AUTOEXEC.PCE.  This file 

shows the necessary entries for a CTOS

Vpc workstation.

   Example 2.  Sample AUTOEXEC.PCE File

   PATH C:\;C:\LANCE;C:\CDROM

   RS485EM

   \CDROM\MSCDEX.EXE 

CDROM 

   \CDROM\CDR Assign L: {LOCAL}[CDROM]0 

Example 3 shows a sample AUTOEXEC file, called AUTOEXEC.PC.  This file 

shows the necessary entries for a clustered PC.

   Example 3.  Sample AUTOEXEC.PC File

   PATH C:\;C:\LANCE;C:\CDROM

   RS485

   \CDROM\MSCDEX.EXE 

CDROM 

   \CDROM\CDR Assign L: {LOCAL}[CDROM]0

As shown in the sample files, you must edit or add the following

information to the AUTOEXEC.BAT file to use the CD

ROM software:

  The path must include:

   PATH C:\DOS;C:\CDROM;C:\LANCE;

   This ensures that DOS searches the directories \CDROM and \LANCE when

   looking for files.

  You must include the following command line that loads the CD

ROM software:

   \CDROM\MSCDEX.EXE 

CDROM 

   Note:  If you are using DOS 6.2, you must use the DOS version of MSCDEX.

  In this case, a sample entry would be:

  \DOS\MSCDEX.EXE 

CDROM 

   This line includes the following options:

  The entry after 

      This entry must be the same as you used in the CONFIG.SYS file.  This

      specifies the name of the DOS CD

ROM device driver.

  The entry after 

      This indicates that DOS drive letter assignments for CD

ROM modules

      will start at L (L is the standard drive assignment for CD

      modules).  If you leave this blank, the module will be assigned the 

      next available drive letter (probably E).  This example uses the

      L drive.

  The entry after 

      This specifies the number of buffers allocated to the CD

ROM software.

      Specify four buffers for each CD

ROM module you want to access.  For

      example, if you want to access three CD

ROM modules, enter 

M:12.

  The entry 

      This entry specifies verbose mode, which displays information about

      memory usage when DOS is booted.  This is sometimes useful for

      debugging purposes.

  The entry 

      This entry enables you to use expanded memory, if available.

  Each available CD

ROM module must have its own CDR Assign command line in

   the AUTOEXEC.BAT file, as shown:

   CDR Assign L: {LOCAL}[CDROM]0

   CDR Assign M: {LOCAL}[CDROM]1

   The CDR Assign command line(s) must appear in the AUTOEXEC.BAT file after

   the command line that installs the CD

ROM software.  The syntax of the CDR

   Assign command is described for you later in this section.

   It is recommended that you enter command lines in the AUTOEXEC.BAT file 

   for all available CD

ROM modules to ensure that drive letters are assigned

   automatically each time you start your workstation.  Otherwise, you must

   assign the drive letters manually each time you start your workstation.

   The actual entries in your CDR Assign command line(s) will vary depending

   on how many CD

ROM modules you have and where they are located.  The

   following are samples of possible command lines.

   COMMAND LINE AND DESCRIPTION

   CDR Assign L: {LOCAL}[CDROM]0

     Used to assign a drive letter to a CD

ROM module on your local

     workstation.  

Local

 can be used only by CTOS

Vpc, and specifies the

     CD

ROM module attached to the same CTOS workstation running CTOS

   CDR Assign M: {LOCAL}[CDROM]1

     Used to assign a drive letter to the second of two CD

ROM modules on your

     local workstation (the drive letter increments to M, and the 0 increments

     to 1).

   CDR Assign L: {MASTER}[CDROM]0

     Used to assign a drive letter to a CD

ROM module on the server (or

     master) workstation.  

Master

 can be used by both DOS and CTOS

     clients, and specifies the CD

ROM module attached to the CTOS server.

   CDR Assign L: {NodeName}[CDROM]0

     Used to assign a drive letter to a CD

ROM module on another node, where

     NodeName is the BNet name of the node.

   You can assign drive letters to modules in any order.  Remember to

   increment the drive letters when appropriate (L, M, N and so forth), and to

   indicate the correct location of the modules on the workstation (0, 1, 2

   and so forth).

7.0 USING THE TBACKUP AND TRESTORE COMMANDS

The LANce

pc tape backup and restore commands enable you to backup 

and restore your DOS hard disk using a tape module on the CTOS server.  Using 

the LANce

pc tape commands, you can back up and restore the entire DOS disk 

or selected files.

LANce

pc does not include a command for retensioning CTOS QIC tapes.

You should make sure that the tapes you are using are periodically retensioned

as recommended in the 

CTOS Operating System Concepts

 manual.  To retension a

QIC tape, execute the QIC Retension command from the CTOS Executive.  Ask your

CTOS system administrator for help if necessary.  Also, for general

information about CTOS tape functionality see the 

CTOS Operating System

Concepts

 manual.  The tape commands automatically rewind the tape before 

starting either backup or restoration.

The LANce

pc TBACKUP and TRESTORE commands are based on the DOS

Backup and Restore commands.  Therefore, they look similar.  However, you 

should read the information in this section to find out how the functionality 

of the LANce

pc commands differ from the DOS commands.

Note:  Before starting a tape backup or restoration from a PC on a LAN, 

       check to be sure RQ Agent is installed with at least 4KB for maximum 

       request size.

TBACKUP

This command backs up one or more DOS files to a QIC tape installed on a CTOS 

server.  You can use TBACKUP to back up hidden, read

only, and system files

as well as normal DOS files.

Syntax

   TBACKUP source [

d:date] [

t:time] [

l[:[drive:] [path] 

   [logfile]]

Parameter

   source    Specify a drive letter and colon, a directory name, a file name,

     or a combination.  If you do not specify a drive, TBACKUP uses

     the current drive.  If you do not specify a directory, TBACKUP

     uses the current directory.  If you do not specify a file, 

     TBACKUP uses * and *.*.  You must provide some file 

     specification.

     You can include wild cards (* or ?) in the source.

Switches

s        Backs up the contents of all subdirectories.

m        Backs up only those files that have been changed or are new 

     since the last backup, and turns off the archive attribute 

     of the original files.  The last backup includes both backups

     made using TBACKUP and the DOS Backup command.

a        Adds a backup to the tape without deleting existing backups

     already stored on the tape.  Using 

a, backups are written 

     after the logical end of tape; each backup is assigned a 

     sequence number, the first backup being 0.  You must specify

     this sequence number as the tape parameter for TRESTORE.

d:date   Backs up only those files last modified on or after the given

     date.  Specify date in the format MM

YYYY.

     Note that the date must be specified with the two

digit month

     first, the two

digit day second, and the four

digit year third.

     The month and day must always be two

digit, so must include

     leading zeros when appropriate.

t:time   Backs up only those files last modified at or after the given

     time.  Specify time in the format HH:MM:SS, with the hour 

     specified in 24

hour format.  If you use the 

t without the 

     switch, TBACKUP uses the current date.

l[:      Records the tape backup operation in a log file.  If the file

   [drive:]  given does not exist, TBACKUP creates the file.  If the file

   [path]    given does exist, TBACKUP appends new data to the file.

   [logfile]]

     Note:  If you specify a log file matching the source 

    specification, TBACKUP continues the backup normally but

    does not back up the log file.

     If you do not specify a location ([drive:][path]) for the file,

     TBACKUP uses the root directory of the source drive.  If you do

     not specify a log file, TBACKUP uses the file name TBACKUP.LOG.

     For each tape backup operation, TBACKUP records the following

     data in the log file:

     

 The command and file specification.

     

 The date and time of the backup.

     

 The sequence number of the backup on the tape.

     

 The name of each file backed up.

     

 The total number of files backed up.

     

 Any errors that occur during the back up.

TRESTORE

This command restores one or more DOS files from a QIC tape installed on a 

CTOS server.  Use TRESTORE to retrieve files backed up using the TBACKUP 

command.

Syntax

   TRESTORE tape drive:[path[file]] [

b:date] [

a:date] [

e:time]

l:time] [

Parameters

   tape      Specify the sequence number of the backup on the QIC tape you

     want to restore.  This number corresponds to the number assigned

     by TBACKUP when the 

a switch is used.  The first backup on a 

     tape is numbered 0.

   drive:    Specify the file or group of files you want to restore.  You

   [path     must specify the same path, and file name(s) as were used when

   [file]]   the file(s) were backed up.  You do not need to match the drive.

     If you do not specify a path and

or file, TRESTORE uses * and

     *.*.  You can include wild cards (* or ?) in the name of the 

     file.

Switches

s        Restores all subdirectories in the drive and path specified. 

     Within each subdirectory, TRESTORE restores only those files 

     with names matching that provided in the file.

p        Prompts you for permission to restore files that are read

     (that have the read

only attribute set), that are system files

     (that have the system attribute set), or that have changed since

     the backup.

     TRESTORE ignores the 

p switch if you use it with the 

d switch.

b:date   Restores only those files last modified on or before the given

     date.  Specify date in the format MM

YYYY.

     Note that the date must be specified with the two

digit month

     first, the two

digit day second, and the four

digit year third.

     The month and day must always be two

digit, so must include

     leading zeros when appropriate.

a:date   Restores only those files last modified on or after the given

     date.  Specify date in the format MM

YYYY.

     Note that the date must be specified with the two

digit month

     first, the two

digit day second, and the four

digit year third.

     The month and day must always be two

digit, so must include

     leading zeros when appropriate.

e:time   Backs up only those files last modified at or before the given

     time.  Specify time in the format HH:MM:SS, with the hour 

     specified in 24

hour format.  If you use the 

t without the 

     switch, TRESTORE uses the current date.

l:time   Backs up only those files last modified at or after the given

     time.  Specify time in the format HH:MM:SS, with the hour 

     specified in 24

hour format.  If you use the 

t without the 

     switch, TRESTORE uses the current date.

m        Restores only those files modified since the last backup.

n        Restores only those files that no longer exist on the DOS hard

     disk.

d        Displays a list of the files on the tape that match the names

     specified in file without restoring any files.  Even though 

     files are not restored, you must specify a drive when using 

     this switch.

v        Restores system files along with the hidden, read

only, 

     and normal DOS files that TRESTORE restores without 

f[:      Records the tape restore operation in a log file.  If the file

   [drive:]  given does not exist, TRESTORE creates a new file.  If the file

   [path]    given does exist, TRESTORE appends new data to the file.  

   [logfile]]

     If you do not specify a location ([drive:][path]) for the file,

     TRESTORE uses the root directory of the source drive.  If you

     do not specify a log file, TRESTORE uses the file name 

     TRESTORE.LOG.

     For each tape backup operation, TRESTORE records the following

     data in a log file:

     

 The command and file specification.

     

 The date and time of the restore.

     

 The sequence number of the backup on the tape that is

       being restored.

     

 The name of each file restored.

     

 The total number of files restored.

     

 Any errors that occur during the restore.

8.0 USING THE RQNAMES LIBRARY

RQNames.Lib is a library of CTOS calls that can be linked with DOS

applications.  This enables DOS applications to make CTOS requests.

The DOS applications must be executing on a PC or CTOS

Vpc connected to a CTOS

server.  The RQNames library supports any programming language normally used 

in the DOS environments.

Note:  The RQNames library also supports applications executed on a PC

       connected to a CTOS server through a LAN when LANce

pc is used with

       LANce

For your convenience, LANce

pc includes a header file for the RQNames.Lib on 

its product disk.  You can link this header file, called RQNames.H, with your 

applications.

The RQNames library includes the following categories of calls:  CTOS Kernel

Primitives, CTOS System Common Procedures, and ClusterCard

Specific Commands.

  CTOS Kernel Primitives

   Using these primitives, a DOS application can send requests and receive 

   responses from a system service running on the CTOS server.  For 

   information about the procedural interface for each call, see the 

   Procedural Interface Reference Manual.

  The CTOS Kernel Primitives return

   CTOS status codes.

   The calls are:

   Check

   Request

   RequestDirect

   Wait

   The RQNames library also includes the following new calls, that are

   modified versions of the Wait primitive:

   GetResponse

   Waitp

   GetResponse functions exactly like the Wait call, except that it does

   not have the 

Exchange

 parameter.  Instead of waiting at a specified

   exchange, GetResponse always waits at exchange one.  Requests must specify

   exchange one to be received by GetResponse.

   Note:  Do not use GetResponse if SESSION is installed.  Your program may 

  get a message directed to SESSION.

   Waitp functions exactly like the Wait call, but it has a different name.

   Waitp is provided in case Wait is a reserved keyword in the programming

   language you using.

  CTOS System Common Procedures

   These calls mimic on DOS the behavior expected in a CTOS environment.  For

   information about the procedural interface for each call, see the 

   Procedural Interface Reference Manual.

  The CTOS System Common Procedures

   return DOS error codes.

   The calls are:

   AllocExch

   AllocMemoryLL

   AllocMemorySL

   DeAllocExch

   DeallocMemoryLL

   DeallocMemorySL

   ErrorExit

   GetUserNumber

   QueryDefaultRespExch

  ClusterCard

Specific Commands

   These calls are specific to ClusterCard.  If no ClusterCard is present on

   the system, the SetCSLoginName and GetCSLoginName can still be used.  The

   software keeps the names in memory.

   ClusterCard

Specific commands return CTOS status code 8 when an error

   occurs.

   The procedural interface for the calls are outlined in this subsection.

   The calls are:

   SetCSLoginName

     Use this call to set a name in the ClusterCard.

     ES:BX = Pointer to a name.  The name can be from one to 16 characters

     in length, and must end with null.

     Inputs:  Ax = 00FEh, Cx = 

   GetCSLoginName

     Use this call to get a cluster user name from the ClusterCard.

     ES:BX = Pointer to an address in which GetCSLoginName will return a name.

     The name will be from one to 16 characters in length, and will

     end with null.

     Inputs:  Ax = 00FDh, Cx = 

     Outputs:  Pointer returned in ES:BX.

   CheckClusterCard

     Use this call to check for the presence of a ClusterCard.

     Inputs:   Ax = 00FFh  CS = 0000h

     Outputs:  Ax = 0000h, Cx = 

 for the CTOS

Vpc (plus DX = 

   BX = X

block size)

       Ax = 0001h, Cx = 

 for the clustered PC (plus DX = 

   and BX = X

block size) 

       Ax = 007Fh, Cx = 

 for the PC on a LAN

     Note:  X

blocks size is measured in 512 byte sectors.  For example, 

    an X

block size of 4K is returned as 0008h in BX.  BX values

    are ONLY valid for X

block size indicators when register DX

    contains the proper 

 signature.  If DX contains anything

    else, the application MUST assume an X

block size of 2.5KB.

9.0  CORRECTIONS

Corrections introduced in LANce

pc 1.2:

  For TRESTORE, when the target drive is full, a message prints (UCF

   26514827).

Corrections introduced in LANce

pc 1.1:

  RS485 was modified to permit a clustered PC to work with Windows in

   enhanced mode.  However, you MUST upgrade to Windows 3.1 (see 8.0 

   Restrictions and Known Limitations).  (UCFs:  16333701, 26246067,

   26274176, 42977454, 16969958, 42992780, 31151970).

  When installing AutoBoot from the installation disk, the JCL sequence

   renames the IO.SYS and MSDOS.SYS files to IBMBIO.SYS and IBMDOS.SYS,

   thus enabling your PC to AutoBoot DOS 3.3 (UCFs:  31096171, 42874655).

  A new configuration file was added to enable the DOS Backup command to

   work correctly (UCFs:  16729736, 26208343, 42940429).

  This release allows DOS applications under Windows to support context

   switching (UCFs:  16922048, 31143080).

  The RQNames library call DeAllocExch now deallocates an exchange 

   correctly (UCF:  26301491).

  Calls to the NetBIOS Interrupt return correct error values and enable 

   more than 20 NetBIOS calls.

  DELETE.NAME was using NCB_Num instead of NCB_Name.  This has been 

   corrected.

  FIND.NAME and STATUS used NCB_Name to specify what name to used.  This

   has been changed to NCB_CallName to be compliant with standard NetBIOS 

   protocol.

  SEND, CHAIN.SEND, and RECEIVE no longer fail for more than 2.5KB.

  PC no longer hangs when using NO

WAIT commands.

  Copying files from a network drive (using Redirector and NetBIOS) works 

   correctly.

  CANCEL now works properly.

  NETBIOS now accepts some session commands using the LSN of an

   existing session when the user issuing the command did not own the

   specified session.

  RECEIVE.BROADCAST.DATAGRAM now works correctly.

  The name that SETNAME.EXE supplies to Redirector and NetBIOS is now 

   formatted according to LAN Manager conventions. The product now pads

   to 15 characters and provides Null in the last byte if the name is less 

   than 16 characters.

  AutoBoot now correctly installs when trying to access 

   Install>English.cmds.

  RS485 now works with a SuperGen Series 1000.

  Session no longer goes into an infinite loop if it receives an unsupported

   NetBIOS command.

  Printing from Windows installed on a PC on a LAN to a CTOS printer

   now works properly (PLE 15845767).

  TBACKUP handles attributes correctly (PLE 15954698).

  A PC on a LAN no longer hangs when using TBACKUP (PLE 15845724).

  Lotus Notes now works under CTOS

  The keyboard no longer hangs with an incorrect Alias name 

   (PLE 15920068).

10.0  RESTRICTIONS AND KNOWN LIMITATIONS

This release of the CTOS LANce

pc software contains the following 

restriction and known limitations:

  From a clustered PC or CTOS

Vpc workstation connected to a SuperGen

   Series 5000, the NS ClusterUsers command does not display the users in

   the cluster.

  In the Network Shell menu interface, the Retry button functions the

   same as the Loop button.

  When using the Network Shell to establish a connection to a CTOS

   printer, if you use an invalid printer queue name and Spooler is

   running on CTOS (or no print service is installed), you do not

   receive an error.  You only receive an error when this condition

   occurs and the Generic Print Service (GPS) is installed.

  To use the LANce

pc TBACKUP and TRESTORE commands on a CTOS client 

   workstation running CTOS

Vpc or PC Emulator, both client and server

   must be running the same operating system.  The choices are:

   Both client and server running BTOS II 3.2

   Both client and server running CTOS II 3.3 or higher 

  You cannot switch out of LANce

pc applications when running under 

   Windows in enhanced mode.  You must finish one application before 

   moving to another application.

  The RS422 driver (which supports the XT

bus card) does not support 

   Windows 3.0 or 3.1 enhanced mode.

  The capability to make CTOS requests from a Windows application is 

   supported only on Windows 3.1 or higher. The capability is not 

   supported on Windows for Workgroups.

  CAUTION: A clustered PC running Windows 3.0 does not support enhanced 

      mode.  If you try to use it, you will bring down the network.

      Windows 3.1 enhanced mode is supported.

  If your PC hangs, check one of the following, make changes, and

   reboot your PC.

  The values of X

block parameters on your server are not coordinated

      with the NET and RS485 switch settings

  The service being accessed was deinstalled on the server

  The RS485 cable was disconnected

  The server being accessed was powered down or rebooted

  BNet is not properly configured for connecting to a networked drive

      at a remote BNet node

  The description of software installation for LANce

pc described in 

   the 

CTOS LANce

pc and LANce

LM Administration and Programming Guide

   is superseded by 

4.0 Getting Started

 in this file.

11.0 MIGRATION AND COEXISTENCE

block Settings   

blocks are used for data transmission to and from clustered PCs and

   CTOS

Vpc workstations.  On the CTOS server, the default setting for the 

   maximum number of outstanding requests is five.  To increase this number,

   create or modify an entry for :MaxXBlocksOut:.  

   If you are using LANce

pc with LANce

LM, refer to the 

CTOS LANce

   and LANce

LM Administration and Programming Guide.

  Without LANce

   the following guidelines may help you determine what the maximum 

   number of requests outstanding should be.  You must also be familiar 

   with the type of application being used.

  When using an X

block size of 2.5KB, each PC uses eight outstanding 

      requests.

  When using an X

block size of 4KB, each PC uses five outstanding 

      requests.

  Use the Cluster Status command on the server to monitor the X

blocks.  

   If you have more than four workstations clustered to the server, 

   you need to increase your :MaxXBlocksOut: parameter.  Try 

   increasing the value of :MaxXBlocksOut: to 15 or 20.  See your 

CTOS System Administration and Programming Guide

 for more information.

Setting Switches for REDIR

REDIR enables you to specify buffer sizes for sending information to the

CTOS server.  Microsoft documents all the switches in their documentation,

however, there are three switches that you should set for use with 

LANce

sb, and 

z.  The following values are recommended for 

most installations.  The values for your configuration may be affected by 

other configuration requriements.  Specify values in multiples of 512.

px:n sets the buffer size in bytes for LPTx (where x is 1, 2, or 3).  

   If your CTOS server supports 4KB X

blocks, specify 3584 for n.  

   If your CTOS server supports 2.5KB X

blocks, specify 2048 for n.

sb:n sets the size of a single receive buffer to n.

   If your CTOS server supports 4KB X

blocks, specify 3584 for n.

   If your CTOS server supports 2.5KB X

blocks, specify 10240 for n.

z:n sets the size of workstation work buffers.

   If your CTOS server supports 4KB X

blocks, specify 3584 for n.

   If your CTOS server supports 2.5KB X

blocks, specify 10240 for n.

As an example, suppose you have: a clustered DOS client; a CTOS server 

configured for 4KB X

blocks; a network printer connected as LPT1;

and an application which issues reads to the server's networked

drive. For this example, use the following command:

   \lance\redir  

p1:3584  

sb:3584  

z:3584

If your configuration includes connections to a LAN, the values for 

z should match the values found in the SIZREQBUF parameter.  For

LAN Manager, this parameter is in the LANMAN.INI file.  For LAN Server, 

this parameter is in the IBMLAN.INI file.

If you receive an error message of 

incorrect parameter

 when using 

REDIR, you have not specified enough memory.  Reduce the values 

for one or more of the parameters until you no longer receive the

message. 

Using NET.BAT

Use NET.BAT to help you run the LANce

pc components needed for

your installation when used with LANce

LM.  NET.BAT has the following 

parameters:

Description of Function                           NET Parameters

To access file and printer services on the local 

CTOS server: 

   Clustered PC                                   net clocal

   CTOS

Vpc workstation                           net elocal

For peer

peer communication using NetBIOS:

   Clustered PC                                   net cpeer

   CTOS

Vpc workstation                           net epeer

For access to a LAN through the CTOS server:

   Clustered PC                                   net clan

   CTOS

Vpc workstation                           net elan

NET.BAT has a switch setting that may increase the processing speed of 

your configuration. The switch allows you to specify the size of the X

blocks 

that are sent to the CTOS server.  If your CTOS server can accept 4KB

blocks, use the switch 

8.  For example, the NET command is:

     

     \lance\net clocal 

Note:  CTOS

Vpc release 2.0 is required to support 4KB X

blocks.

Other Coexistence with CTOS LANce

  The NetBIOS API provided in LANce

LM 1.0 and the NETBIOS.EXE TSR provided 

   in LANce

pc 1.0 did not handle DELETE.NAME properly.  This has been 

   corrected to be compliant with the standard NetBIOS protocol.  Therefore: 

  There may be problems with mixing old and new versions of LANce

LM and 

      LANce

pc when running NetBIOS applications. With LANce

pc 1.2, use

      LANce

LM 1.1 or higher.

  If you upgrade to LANce

LM 1.1, you will have to modify any NetBIOS 

      applications that use DELETE.NAME to supply this command with a name 

      rather than a number, and relink the applications.  

  Likewise, DOS applications that ran properly with the NETBIOS TSR 

      supplied in release 1.0 will have to be changed to supply a name rather 

      than a number, and the NETBIOS.EXE s1.0.06 or higher must be used.

  If you are upgrading from LANce

pc 1.0 and are also using LANce

   you must also upgrade LANce

LM to release 1.1 or higher. In addition,

   you need to install LANce

LM on every BNet node that you want to access.

  When LANce

pc is used with LANce

LM, additional components are required. 

   The following information supplements the information provided in the 

CTOS LANce

pc and LANce

LM Administration and Programming Guide,

   Appendix F.

  For a clustered PC, you may encounter an error 

Invalid Base I

O address

   error when installing RS485 after loading an expanded memory manager, such

   as EMM386.  To resolve this error, you must 

exclude

 the ROM address used 

   by the ClusterCard.  You must also set the correct parameters as required 

   by the memory management utility you are using.

   For example, if you are using the EMM386 driver, and the ROM switches on 

   your ClusterCard are set to DC00

DFFF (the default), use the following 

   NOEMS parameter to exclude the address from expanded memory.  

   DEVICE=\DOS\HIMEM.SYS

   DEVICE=\DOS\EMM386.EXE NOEMS X=DC00

   DOS=HIGH,UMB

   Note: The order of the commands is very important.  Consult your memory

 management documentation.

  When possible, execute commands and access network files while pathed

   on the local drive.  For example, if you have a local drive C: and a

   network drive E: with the program XYZ.EXE, you will get better performance

   if you are on the C: drive and run E:XYZ.

  When possible, move or copy batch files to your local drive.  Since a 

   batch file is opened and closed for each line executed, the performance

   is better if the batch file is on the local drive.

12.0 SUPPORT

Warranty

CTOS LANce

pc 1.2 is a warranted Unisys software product.    

Unisys warrants that CTOS LANce

pc 1.2, in its unaltered form, 

will substantially conform to Unisys current published functional 

specifications when used in Unisys supported configurations.  The 

customer is responsible for reporting suspected deviations using the 

User Communication Form (UCF) process within ninety (90) days 

following delivery.  The product is neither field repairable nor 

field modifiable.  Corrections to reported deviations are provided 

to the user via updated code files.

This standard warranty is not a substitute for Unisys Service 

Agreement offerings.

Support Category        

CTOS LANce

pc 1.2 is fully supported by Unisys.

Support services for CTOS LANce

pc 1.2 are offered under the 

SURETY (United States) or A la Carte (International) support 

programs and are consistent with the support services offered for 

the entire CTOS Hardware and Software family of products.

Unisys SureNet is an electronic bulletin board service, providing 

customers in the United States access to technical information seven 

days a week, 24 hours a day.  SureNet Technical Information Services 

are available at no additional cost to customers with a current 

Unisys service agreement or software license and include access to 

system alerts, customer technical bulletins and online UCF entry.  

Registration is required.  SureNet Support Services are available on 

an annual subscription basis.  For more information, contact Unisys 

Direct at 1

1424, prompt 5.  You may register for Technical 

Information Services and

or Support Services either online by 

dialing 1

8796 (8 data bits, 1 stop bit, no parity, 

asynchronous, VT100 emulation) or by calling Unisys Direct.

If you need further assistance or information regarding support 

services, please contact your Unisys representative or your local 

Unisys office.

Support Discontinuance

Unisys supports the current release level and one level back.  Prior 

levels are not supported.

98BADCFE,APPID,LANMAN_BASIC,2.00,MICROSOFT,11

92,MICROSOFT:3.30

 0123456789ABCDEFabcdef

URQSPWV

^_X[YZ].

t?<+tG<Lt><lt:<0r=<9w9<0u

<Ct'<St

PC NETWORK PROGRAM 1.0

MICROSOFT NETWORKS 1.03

MICROSOFT NETWORKS 3.0

MICROSOFT NETWORKS DEC

                

?????

LPT1:

 (C) Copyright Microsoft Corp. 1984, 1985, 1987

1MSP2

<\\tX

(Mu)^V

PSQRVW

_^ZY[X

OD^X=7

_)PSQRW

9_ZY[X

ZYRrAV

@tVXP=

YZ^_r.X

@u0.;

t+ZRP

PSQRV

^ZY[X_

O)QRVP

7cLP.

9cT1.

[Z_Ys

PSVWU

]_^[X

V;|Rr

_XZY^

qTXY_

sVPWV

VSPQR

Y]^[X

                                

SQRVWU

]_^ZY[

$?<?Xu

SQRVW

_^ZY[]

LPT1    

YwWjY

<2r*<Jv

_ZYX6

DTRT.

PSQRVW

_^ZYrJuH

NET809: Network request not supported

NET801: Remote computer not listening

NET802: Duplicate name on network

NET803: Network path not found

NET804: Network busy 

 remote node not responding

NET805: Network device no longer exists

NET806: NetBIOS

Network command limit exceeded

NET807: Network adapter hardware error

NET808: Incorrect response from network

NET810: Unexpected network error

NET811: Incompatible remote adapter

NET812: Print queue full

NET813: Not enough print space for file

NET814: Print file was cancelled

NET815: Network name was deleted

Access denied

NET817: Network device type incorrect

NET818: Network name not found

NET819: Network name limit exceeded

NET820: NetBIOS

Network session limit exceeded

NET821: Sharing temporarily paused

NET823: Network request not accepted

NET822: Print or disk redirection is paused

NET476: Network software not installed

NET477: Unexpected adapter close

NET825: Network data fault

BUGBITS:

C:\LANMAN.BAS

?*@E@

>QdX[YZ_^

OPTIONAL

HIMEM:

VWRQSP

7ct^.

<1rK<3wG,12

WVRQSP

X[YZ^_

Incorrect DOS version

$This is part of Lanman Basic. Use net.exe to start redir.

$Insufficient memory

lIncorrect parameter

lRedirector already installed

4lNetwork has not been started

UlNET3545: Services cannot be started or stopped in a DOS session or Windows VM.

98BADCFE,APPID,LANMAN_BASIC,2.00,MICROSOFT,11

92,MICROSOFT:4.00

 0123456789ABCDEFabcdef

URQSPWV

^_X[YZ].

t?<+tG<Lt><lt:<0r=<9w9<0u

<Ct'<St

REDIR   

PC NETWORK PROGRAM 1.0

MICROSOFT NETWORKS 1.03

MICROSOFT NETWORKS 3.0

MICROSOFT NETWORKS DEC

                

?????

LPT1:

 (C) Copyright Microsoft Corp. 1984, 1985, 1987

<\\tX

Mu)^V

PSQRVW

_^ZY[X

OD^X=7

_)PSQRW

:_ZY[X

ZYRrBV

@tVXP=

YZ^_r.X

@u0.;

t+ZRP

PSQRV

^ZY[X_

O)QRVP

F;RQ.

[Z_Ys

PSVWU

]_^[X

V;|Rr

_XZY^

sVPWV

VSPQR

Y]^[X

                                

SQRVWU

]_^ZY[

$?<?Xu

SQRVW

_^ZY[]

LPT1    

_uYOYOY

YOYOY

YuYuYuYuYuY

<2r*<Jv

_ZYX6

PSQRVW

_^ZYrJuH

NET809: Network request not supported

NET801: Remote computer not listening

NET802: Duplicate name on network

NET803: Network path not found

NET804: Network busy 

 remote node not responding

NET805: Network device no longer exists

NET806: NetBIOS

Network command limit exceeded

NET807: Network adapter hardware error

NET808: Incorrect response from network

NET810: Unexpected network error

NET811: Incompatible remote adapter

NET812: Print queue full

NET813: Not enough print space for file

NET814: Print file was cancelled

NET815: Network name was deleted

Access denied

NET817: Network device type incorrect

NET818: Network name not found

NET819: Network name limit exceeded

NET820: NetBIOS

Network session limit exceeded

NET821: Sharing temporarily paused

NET823: Network request not accepted

NET822: Print or disk redirection is paused

NET476: Network software not installed

NET477: Unexpected adapter close

NET825: Network data fault

BUGBITS:

C:\LANMAN.BAS

V9,Dc 

S5SVSxS

,AQW3

>5eX[YZ_^

OPTIONAL

HIMEM:

VWRQSP

<1rK<3wG,12

WVRQSP

X[YZ^_

Incorrect DOS version

$This is part of Lanman Basic. Use net.exe to start redir.

$Insufficient memory

lIncorrect parameter

lRedirector already installed

mNetwork has not been started

5mNET3545: Services cannot be started or stopped in a DOS session or Windows VM.

98BADCFE,APPID,LANMAN_BASIC,2.00,MICROSOFT,11

92,MICROSOFT:5.00

 0123456789ABCDEFabcdef

URQSPWV

^_X[YZ].

t?<+tG<Lt><lt:<0r=<9w9<0u

<Ct'<St

REDIR   

PC NETWORK PROGRAM 1.0

MICROSOFT NETWORKS 1.03

MICROSOFT NETWORKS 3.0

MICROSOFT NETWORKS DEC

                

?????

LPT1:

 (C) Copyright Microsoft Corp. 1984, 1985, 1987

<\\tX

Mu)^V

PSQRVW

_^ZY[X

OD^X=7

_)PSQRW

:_ZY[X

ZYRrBV

@tVXP=

YZ^_r.X

@u0.;

t+ZRP

PSQRV

^ZY[X_

O)QRVP

F;RQ.

[Z_Ys

PSVWU

]_^[X

V;|Rr

_XZY^

sVPWV

VSPQR

Y]^[X

                                

SQRVWU

]_^ZY[

$?<?Xu

SQRVW

_^ZY[]

LPT1    

_uYOYOY

YOYOY

YuYuYuYuYuY

<2r*<Jv

_ZYX6

PSQRVW

_^ZYrJuH

NET809: Network request not supported

NET801: Remote computer not listening

NET802: Duplicate name on network

NET803: Network path not found

NET804: Network busy 

 remote node not responding

NET805: Network device no longer exists

NET806: NetBIOS

Network command limit exceeded

NET807: Network adapter hardware error

NET808: Incorrect response from network

NET810: Unexpected network error

NET811: Incompatible remote adapter

NET812: Print queue full

NET813: Not enough print space for file

NET814: Print file was cancelled

NET815: Network name was deleted

Access denied

NET817: Network device type incorrect

NET818: Network name not found

NET819: Network name limit exceeded

NET820: NetBIOS

Network session limit exceeded

NET821: Sharing temporarily paused

NET823: Network request not accepted

NET822: Print or disk redirection is paused

NET476: Network software not installed

NET477: Unexpected adapter close

NET825: Network data fault

BUGBITS:

C:\LANMAN.BAS

V9,Dc 

S5SVSxS

,AQW3

>5eX[YZ_^

OPTIONAL

HIMEM:

VWRQSP

<1rK<3wG,12

WVRQSP

X[YZ^_

Incorrect DOS version

$This is part of Lanman Basic. Use net.exe to start redir.

$Insufficient memory

lIncorrect parameter

lRedirector already installed

mNetwork has not been started

5mNET3545: Services cannot be started or stopped in a DOS session or Windows VM.

PQRSTUVW

_^][[ZYX

t$<\t

t'<\t

s6BSQ

7t.)G

_^][[Z

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

RQAGENT

RqAgent

Illegal buffer length

Invalid command

Command timed out

Message incomplete

Data was not received

Illegal local session number

No resource available

Session closed

Command cancelled

Duplicate name in local name table

Name table full

Local session table full

Session open rejected

Cannot find name called

Name not found or cannot specify 

 or null

Name in use on remote NETBIOS interface

Session ended abnormally

Name conflict detected

Interface busy

Too many commands outstanding

Invalid adapter number. Not currently configured

Name defined by another environment

Environment not defined

Required OS resources exhausted

Client ID (uniquely identifies this RQAGENT)   = 

NetBIOS name of CTOS RQ Service                = 

[Adapter Number (default = 0)]                 = 

[Max request size (default = 3072)]            = 

[Max 

 of outstanding requests (default = 1)]  = 

[Connect to RQ Service now ? (default = N)]    = 

One of these RS4XX

RS4XXEM

RqAgent was already installed

An INT 7F Handler was installed. Chain this one                                 

NetBIOS is not installed (no ISR is serving INT 5Ch).

 RqAgent installed as ISR successfully 

Invalid value. Valid values: 1 

Remote NetBIOS name has not been defined

Invalid value. Valid values: 0 or 1

Invalid value. Valid values: 128 

 4096

Could not allocate memory

Invalid value. Valid values: 1 

Please specify 'Y' or 'N'

Unexpected error

Either not enough or too many parameters

Installation of RQAGENT failed

RqAgent already installed elsewhere on LAN with this Client ID.

Installation of RQAGENT failed

Cannot find CTOS RQ Service with specified NetBIOS name.

Installation of RQAGENT failed

Specified CTOS RQ Service is unavailable.

_C_FILE_INFO=

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

****************************** MODULE HEADER *******************************

*                                                                          *

* TITLE: CTOS LANce R1.0                                                   *

*                                                                          *

* FILE NAME: RqNames.h                                                     *

*                                                                          *

* DESCRIPTION: Header file for RqNames.Lib.                                *

*                                                                          *

* HARDWARE SUPPORTED: PC                   OS REQUIRED: DOS 3.0 or Greater *

*                                                                          *

* CHANGE HISTORY:                                                          *

*                                                                          *

YY VVVV

MM PROGRAMMER   

 DESCRIPTION OF CHANGE (Most recent first *

92 1.0                  

 Created.                                 *

*                                                                          *

*                                                                          *

*                                                                          *

*                      PROPRIETARY PROGRAM MATERIAL                        *

*                                                                          *

*         THIS  MATERIAL IS PROPRIETARY TO UNISYS CORPORATION AND          *

*         IS NOT TO  BE  REPRODUCED,  USED OR DISCLOSED EXCEPT IN          *

*         ACCORDANCE   WITH   PROGRAM   LICENSE  OR  UPON WRITTEN          *

*         AUTHORIZATION OF THE GENERAL COUNSEL, OFFICE OF GENERAL          *

*         COUNSEL, UNISYS CORPORATION,  BLUE BELL, PA. 19424, USA          *

*                                                                          *

*         COPYRIGHT (C) 1992 UNISYS CORPORATION                            *

*                                                                          *

*                                                                          *

*         THE WITHIN INFORMATION IS NOT INTENDED TO BE NOR SHOULD          *

*         SUCH BE CONSTRUED AS AN AFFIRMATION OF FACT, REPRESENT

          *

*         ATION OR  WARRANTY BY  UNISYS  CORPORATION OF ANY TYPE,          *

*         KIND, OR CHARACTER.  THE WITHIN PRODUCT AND THE RELATED          *

*         MATERIALS ARE  ONLY  FURNISHED  PURSUANT AND SUBJECT TO          *

*         THE  TERMS AND  CONDITIONS  OF A DULY  EXECUTED LICENSE          *

*         AGREEMENT.  THE  ONLY  WARRANTIES  MADE BY  UNISYS WITH          *

*         RESPECT TO THE PRODUCTS  DESCRIBED IN THIS MATERIAL ARE          *

*         SET FORTH  IN THE ABOVE FURNISHED  MENTIONED AGREEMENT.          *

*                                                                          *

*                                                                          *

*         THE  CUSTOMER SHOULD EXERCISE CARE TO ASSURE THAT USE OF         *

*         THE SOFTWARE WILL BE IN FULL COMPLIANCE WITH LAWS, RULES         *

*         AND  REGULATIONS OF  THE JURISDICTIONS  WITH RESPECT  TO         *

*         WHICH IT IS USED.                                                *

*                                                                          *

************************** END MODULE HEADER *******************************

* CTOS equivalent kernels

procedures *

extern unsigned short pascal far AllocExch(unsigned far *pExchRet);

extern unsigned short pascal far AllocMemoryLL(unsigned cBytes,char far * far *ppSegmentRet);

extern unsigned short pascal far AllocMemorySL(unsigned cBytes,char far *far *ppSegmentRet);

extern unsigned short pascal far Check(unsigned exch,char far * far *ppMsgRet);

extern unsigned short pascal far DeallocExch(unsigned exch);

extern unsigned short pascal far DeallocMemoryLL(char far *pSegment,unsigned cBytes);

extern unsigned short pascal far DeallocMemorySL(char far *pSegment,unsigned cBytes);

extern unsigned short pascal far ErrorExit(unsigned Erc);

extern unsigned short pascal far GetUserNumber(unsigned far *pUserNumberRet);

extern unsigned short pascal far QueryDefaultRespExch(unsigned far *exch);

extern unsigned short pascal far Request(char far *pRb);

extern unsigned short pascal far RequestDirect(unsigned exch,char far *pRb);

extern unsigned short pascal far Wait(unsigned exch,char far * far *ppMsgRet);

extern unsigned short pascal far WaitP(unsigned exch,char far * far *ppMsgRet);

* Procedures specific to LANce

pc driver *

extern unsigned short pascal far CheckClusterCard(void);

extern unsigned short pascal far GetCsLoginName(char far *pLoginName);

extern unsigned short pascal far GetResponse(char far * far *ppMsgRet);

extern unsigned short pascal far SetCsLoginName(char far *pLoginName);

RqNames.asmB

RqNames

DGROUP

KNAMES_CODE

STACKr

ALLOCMEMORYLL

ALLOCMEMORYSL

REQUESTDIRECT

GETUSERNUMBER}

REQUEST

CRASHERCa

GETCSLOGINNAME

SETCSLOGINNAME

QUERYDEFAULTRESPEXCHw

ALLOCEXCHe

DEALLOCMEMORYLLI

DEALLOCMEMORYSLC

NLSULCMPB

ERROREXITd

CHECKCLUSTERCARD

WAIT9

DEALLOCEXCHx

CHECK

WAITPO

GETRESPONSE

ALLOCMEMORYLL

CHECKCLUSTERCARD

DEALLOCMEMORYSL

GETCSLOGINNAME

REQUEST

SETCSLOGINNAME

WAITP

ALLOCEXCH

ALLOCMEMORYSL

CHECK

CRASHERC

DEALLOCEXCH

DEALLOCMEMORYLL

ERROREXIT

GETRESPONSE

GETUSERNUMBER

NLSULCMPB

QUERYDEFAULTRESPEXCH

REQUESTDIRECT

RqNames

ConvergentClusterCard 

IIJKIIJKEEFGEEFG

Network PC

RS422 not installed

$NETBIOS already installed

$*************Crash is invoked

$No boot ROM detected on ClusterCard 

 Default switches assumed

O address switches are incorrect

Master is not running

ClusterCard hardware failure

Interrupt 7FH already installed

LANce

pc RS422 R1.1.0300.

Copyright (C) UNISYS Corp. 1992, 1993.

All rights reserved.

..... done

 RS422 Driver is running ... 

SQRWV

^_ZY[

DSQRWV

^_ZY[

HSQRWV

^_ZY[

GGFFF6

ConvergentClusterCard 

IIJKIIJKEEFGEEFG

qrstuvw

DEFGDEFGHIJKHIJK

Network PC

\\server\

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

(This TSR serves INT 7Fh, hooks INT 1Ch, 21h)

RS485

(Installed using standard 2.5K X

block.)

(Installed using 4K X

block.)

(WARNING: Installed using a non

qualified X

block size.)

MicroChannel Machine Detected

AT Machine Detected

No ClusterCard Detected 

Invalid Base I

O Switch Settings 

RS485 not installed

$NETBIOS already installed

$*************Crash is invoked

$No boot ROM detected on AT ClusterCard 

 Default switches assumed

No boot ROM detected on MCA ClusterCard 

Server is not running

ClusterCard hardware failure

Int 7FH already inst, Is it RS485?

Connecting To Server 

 Please Wait 

  Done.

 RS485 Driver is running ... 

POS read failure on MCA ClusterCard

ClusterCard Found in MCA Machine.  Slot:  

Using IRQ:  

Using DMA:  

BASE I

O :  

ERROR 

 POS DMA select failed 

ERROR 

 POS IRQ select failed 

ERROR 

 POS I

O select failed 

TCt$<

F)^_Z[

VSQRWV

^_ZY[

ZSQRWV

^_ZY[

j,H;F

+=4,u

GGFFF6

UNISYSAscentia

t\<Ar

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

(This TSR serves INT 7Fh)

RS485EM

(Installed using standard 2.5K X

Block.)

(Installed using 4K X

Block.)

(WARNING: Installed using a non

qualified X

Block size.)

Interrupt 7FH is already installed.

ConvergentClusterCard 

IIJKIIJKEEFGEEFG

qrstuvw

DEFGDEFGHIJKHIJK

Network PC

\\server\

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

(This TSR serves INT 7Fh, hooks INT 1Ch, 21h)

RS485

(Installed using standard 2.5K X

block.)

(Installed using 4K X

block.)

(WARNING: Installed using a non

qualified X

block size.)

MicroChannel Machine Detected

AT Machine Detected

No ClusterCard Detected 

Invalid Base I

O Switch Settings 

RS485 not installed

$NETBIOS already installed

$*************Crash is invoked

$No boot ROM detected on AT ClusterCard 

 Default switches assumed

No boot ROM detected on MCA ClusterCard 

Server is not running

ClusterCard hardware failure

Int 7FH already inst, Is it RS485?

Connecting To Server 

 Please Wait 

  Done.

 RS485 Driver is running ... 

POS read failure on MCA ClusterCard

ClusterCard Found in MCA Machine.  Slot:  

Using IRQ:  

Using DMA:  

BASE I

O :  

ERROR 

 POS DMA select failed 

ERROR 

 POS IRQ select failed 

ERROR 

 POS I

O select failed 

TCt$<

F)^_Z[

VSQRWV

^_ZY[

ZSQRWV

^_ZY[

j,H;F

+=4,u

GGFFF6

UNISYSAscentia

t\<Ar

Microsoft Word 6.0

         

UNISYS

Emergency 

Maintenance 

Update

LANce

AB               s1.2.1100

April 30, 1996

Released Version: 

Microsoft Word 6.0 Document

MSWordDoc

Word.Document.6

C:\MSOFFICE\WINWORD\TEMPLATE\NORMAL.DOT

         

Nitin

Nitin

         

UNISYS

Emergency 

Maintenance 

Update

LANce

AB               s1.2.1100

April 30, 1996

Released Version: 

Style ID:

Library Reference:

DESCRIPTION

This Emergency Maintenance Update (EMU) is provided on an as

needed basis only.  It is not an official release nor is it available through Corporate Software and Publications Operations (CSPO).  The information in this document is supplemental to the product's Software Release Announcement (SRA).

Contact your Unisys support center for more information concerning this EMU.

PROBLEMS CORRECTED

s1.2.1100

PLE 16705241           (Lance

RS485EM would not forward more than 9 requests to the server. After the 9 requests it gives an error (error code 15).

s1.2.1005

PLE none           (Lance

RS485 would not work at clustline line speeds other than 1.8 on the PC5 Card.

PLE 16611654, 16631396           (Lance

RS485.exe would not recover if clusterline disconnected (reboot or disconnect

reconnect cable).  Problem would only occur if the redir tsr is not loaded.

s1.2.0901

PLE none           (Lance

RS485 would not work with some higher Mhz machines >33.  The actual machines that we tested

are UNISYS MDP5605 Pentium 60 Mhz 16Mb Memory 

 Unisys SVI5907 Pentium 90Mhz 16 Mb

memory.  We are taking this on a machine case basis.  If the problem is resolved by the rs485, please send us the machine that was tested and the actual problem resolved.  If problem still persists, please send same information.  A related issue my be encountered on the SVI machines when using the ClientCard (the RS485 indicated 

Server not running

 in this case the problem was related to a conflict with the I

O address of the card.  Had to change the card switch for I

O address from 140 to 100). 

PLE 16207217           (Lance

RS485.exe would corrupt memory in MSDOS, NS command would hang system.  The rs485 driver

was installed around location 1F12:0.

PLE 16269239           (Lance

VPC crashed when attempting to perform a NS Connect if no cluster connection.

PLE 16404349           (Lance

Erc 215 when using TBackup

TRestore to an XE.

PLE 16492931           (Lance

INT 7F already installed

 error on machines with certain BIOS's (no other TSR's are installed).

s1.2.0200:

PLE 16251810             (Lance

CTOS request used from PW doesn't work with LANce

PC.  

PLE 16207217            (Lance

RS484.exe corrupts memory on MSDOS

PLE 16129011            (Lance

When target disk is full TRestore does not warn.

PLE 16257788            (Lance

The DLL files are not being copied onto a native PC.

SOFTWARE FILES

This EMU is a complete replacement package for the released product.

INSTALLATION INSTRUCTIONS

Execute Install command from the A: drive.

Page 

 of 2

Page 

 of 2

would  The driver has been changed to handle upto 49 requests.

Normal

Default Paragraph Font

Default

Default Par

Footer

Jeff Tsao

A:\ABC.DOC

Jeff Tsao

A:\LPC

S121.DEF

Jeff Tsao

A:\LPC

S121.DOC

Jeff Tsao

A:\LPC

S121.DOC

Jeff Tsao

C:\JEFF\JOB\S121006.DOC

Nitin

C:\MSOFFICE\WINWORD\S121005.DOC

Nitin

C:\MSOFFICE\WINWORD\S121100.DOC

Nitin

C:\MSOFFICE\WINWORD\S121100.DOC

Nitin

C:\MSOFFICE\WINWORD\S121100.DOC

Nitin

A:\S121100.DOC

@\\SJ

ENG1\ENG_PSLSR_1

Ne01:

winspool

ENG1\ENG_PSLSR_1

Letter

ENG1\ENG_PSLSR_1

Letter

Times New Roman

Symbol

Arial

Times

Courier

Helvetica

         

Nitin

Nitin

SESSION$SERVER

(This TSR serves INT 2Ah)

$(Installed using standard 2.5K X

Block.)

$(Installed using 4K X

Block.)

$(WARNING: Installed using a non

qualified X

Block size.)

$Exception error in SESSION.EXE. Attempting recovery...

$WARNING: Non

recoverable exception error in SESSION.EXE.

$WARNING: SMB Service request codes have not been merged with Request.sys.

$ERROR: Cluster Not Running.  Installation aborted

$MicroChannel Machine Detected

AT Machine Detected

No ClusterCard Detected 

Invalid Base I

O Switch Settings 

RS485 not installed

$Session already installed

$*************Crash is invoked

$No boot ROM detected on AT ClusterCard 

 Default switches assumed

No boot ROM detected on MCA ClusterCard 

Server is not running

ClusterCard hardware failure

Interrupt 7FH already installed

Connecting To Server 

 Please Wait 

  Done.

485 Driver is running ... 

POS read failure on MCA ClusterCard

ClusterCard Found in MCA Machine.  Slot:  

Using IRQ:  

Using DMA:  

BASE I

O :  

ERROR 

 POS DMA select failed 

ERROR 

 POS IRQ select failed 

ERROR 

 POS I

O select failed 

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

SRWQU

]Y_Z[

t$<\t

t'<\t

s6BSQ

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

SETNAME

NetBIOS is not installed..

SetName was done earlier..

SetName error..

Name not specified..

UNISYS LANce

pc.                                                                

Copyright (C) UNISYS Corp 1993. All rights reserved.                            

_C_FILE_INFO=

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

t$<\t

t'<\t

,at[,

,+t$,7t>

, <Xw

<st'<ntQ<pt

s6BSQ

UWVQS3

X[Y^_]

QSRUVP

AkU'9

?S;uD

z?aUY

<0r?<9w;

<0r$<9w ,0

MSEM87

gfw...GW\

NO87=

VSQRW

_ZY[^

_ZY[^

 [ H a h 3 H a H H H H T T H o [ 3 H T 

;$m[ 

WVRQS

WVRQS

WVRQS

[YZ^_

[YZ^_

I|at+

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

\TBACKUP.LOG

[QIC0]

[QIC]

TBACKUP

TRESTORE

s specified

source

target drive

tape file

Switch specified twice 

Too many parameters 

Invalid switch 

Invalid parameter 

WARNING

 Any existing tape file(s) will be lost

Please insert tape into [qic0] on CTOS server

Press any key to continue (or CTRL

C to abort) . . .

Usage :

 where,

   date = MM

YYYY  (  1980 < YYYY < 2099  )

   time = HH:MM:SS    ( HH in 24 hour format )

   tape = index of backup on this tape (0 for first)

TBackup source [

d:date] [

t:time] [

l[:[drive:][path]logfile]]

TRestore tape drive:[path[file]] [

b:date] [

a:date] [

e:time] [

l:time]

f[:[drive:][path]logfile]] [

Cannot issue CTOS requests

Please execute either RS422, RS485, RS485EM, or RQAGENT

****************************************

TBackup of 

 to [qic]

d on 

s at 

  (and all subdirectories)

TRestore of 

all backed

up files

 from [qic]

d to 

s on 

s at 

Request mechanism failed

Wait mechanism failed

GetResponse mechanism failed

OsVersion

OpenTape

CloseTape

TapeStatus

ReadTapeRecords

WriteTapeRecords

TapeOperation

SeqAccessOpen

SeqAccessClose

SeqAccessStatus

SeqAccessRead

SeqAccessWrite

SeqAccessControl

SeqAccessCheckpoint

Please wait while tape is rewinding . . .

Please wait while scanning to end of existing tape file(s) . . .

Invalid time in switch 

Invalid date in switch 

Invalid or non

existent source 

CTOS request failed : 

AllocExch

DOS system call failed : 

getcwd

Microsoft C call failed : 

_fullpath

fseek

_dos_open

_dos_read

_dos_write

_dos_close

_dos_getfileattr

_dos_setfileattr

_dos_getftime

_dos_setftime

_dos_creat

_dos_findfirst

_mkdir

Error while reading DOS file from CTOS tape

CTOS request failed : SeqAccRead

Error while restoring file to DOS disk

DOS system call failed : _dos_write

Internal inconsistency 

CTOS error code 

DOS error code 

u   : 

Directory contains no files to be backed up :

WARNING

 No files were found to back up

WARNING

 No files were found to restore

Source too long

Invalid logfile in switch 

Cannot seek to end of log file

Cannot open log file 

This tape contains data not written by TBackup

TBackup will overwrite all existing data

Do you want to use this tape with TBackup (y

SeqAccessOpen (tape in use)

Date specified in switch 

b is earlier than date specified in switch 

Time specified in switch 

e is earlier than time specified in switch 

Tape is write protected

Tape format is corrupt

Finished 

d file(s) were backed up

   (using 

.1f KB of tape)

Finished 

d file(s) were restored

   (read 

.2f KB of data from tape)

Finished 

d file(s) match the target specification

   (read 

.2f KB of data from tape)

Switches:

This tape is blank

Tape file 

d not found

 This tape contains only 

d tape file(s)

Please wait while scanning to tape file 

d . . .

Cannot read tape archive header

This tape file does not include the specified target path

Invalid tape archive header format

DOS file(s) in 

 were backed up to CTOS tape on 

s at 

Cannot read next file from tape

is a read

only file

was changed after it was backed up

is a system file

is a volume ID file

WARNING

 File 

Replace the file (y

malloc failed 

 couldn't allocate 3072 bytes

User hit CTRL

_C_FILE_INFO=

  0PX

000WP

ppxxxx

(null)

         (((((                  H

Sunday

Monday

Tuesday

Wednesday

Thursday

Friday

Saturday

January

February

March

April

August

September

October

November

December

e+000

010203040506070809101112

M61xx

Error 0

No such file or directory

Arg list too long

Exec format error

Bad file number

Not enough memory

Permission denied

File exists

Cross

device link

Invalid argument

Too many open files

No space left on device

Math argument

Result too large

Resource deadlock would occur

Unknown error

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

: MATH

 floating

point error: 

invalid

denormal

divide by 0

overflow

underflow

inexact

unemulated

square root

stack overflow

stack underflow

explicitly generated

t$<\t

t'<\t

,at[,

,+t$,7t>

, <Xw

<st'<ntQ<pt

s6BSQ

UWVQS3

X[Y^_]

QSRUVP

AkU'9

?S;uD

z?aUY

<0r?<9w;

<0r$<9w ,0

MSEM87

gfw...GW\

NO87=

VSQRW

_ZY[^

_ZY[^

 [ H a h 3 H a H H H H T T H o [ 3 H T 

;$m[ 

WVRQS

WVRQS

WVRQS

[YZ^_

[YZ^_

I|at+

CTOS LANce

 s1.2.1100

Copyright (C) UNISYS Corp. 1992, 1993, 1994.

All rights reserved.

MS Run

Time Library 

 Copyright (c) 1992, Microsoft Corp

\TRESTORE.LOG

[QIC0]

[QIC]

TBACKUP

TRESTORE

s specified

source

target drive

tape file

Switch specified twice 

Too many parameters 

Invalid switch 

Invalid parameter 

WARNING

 Any existing tape file(s) will be lost

Please insert tape into [qic0] on CTOS server

Press any key to continue (or CTRL

C to abort) . . .

Usage :

 where,

   date = MM

YYYY  (  1980 < YYYY < 2099  )

   time = HH:MM:SS    ( HH in 24 hour format )

   tape = index of backup on this tape (0 for first)

TBackup source [

d:date] [

t:time] [

l[:[drive:][path]logfile]]

TRestore tape drive:[path[file]] [

b:date] [

a:date] [

e:time] [

l:time]

f[:[drive:][path]logfile]] [

Cannot issue CTOS requests

Please execute either RS422, RS485, RS485EM, or RQAGENT

****************************************

TBackup of 

 to [qic]

d on 

s at 

  (and all subdirectories)

TRestore of 

all backed

up files

 from [qic]

d to 

s on 

s at 

Request mechanism failed

Wait mechanism failed

GetResponse mechanism failed

OsVersion

OpenTape

CloseTape

TapeStatus

ReadTapeRecords

WriteTapeRecords

TapeOperation

SeqAccessOpen

SeqAccessClose

SeqAccessStatus

SeqAccessRead

SeqAccessWrite

SeqAccessControl

SeqAccessCheckpoint

Please wait while tape is rewinding . . .

Please wait while scanning to end of existing tape file(s) . . .

Invalid time in switch 

Invalid date in switch 

Invalid or non

existent source 

CTOS request failed : 

AllocExch

DOS system call failed : 

getcwd

Microsoft C call failed : 

_fullpath

fseek

_dos_open

_dos_read

_dos_write

_dos_close

_dos_getfileattr

_dos_setfileattr

_dos_getftime

_dos_setftime

_dos_creat

_dos_findfirst

_mkdir

Error while reading DOS file from CTOS tape

CTOS request failed : SeqAccRead

Error while restoring file to DOS disk

DOS system call failed : _dos_write

Internal inconsistency 

CTOS error code 

DOS error code 

u   : 

Directory contains no files to be backed up :

WARNING

 No files were found to back up

WARNING

 No files were found to restore

Source too long

Invalid logfile in switch 

Cannot seek to end of log file

Cannot open log file 

This tape contains data not written by TBackup

TBackup will overwrite all existing data

Do you want to use this tape with TBackup (y

SeqAccessOpen (tape in use)

Date specified in switch 

b is earlier than date specified in switch 

Time specified in switch 

e is earlier than time specified in switch 

Tape is write protected

Tape format is corrupt

Finished 

d file(s) were backed up

   (using 

.1f KB of tape)

Finished 

d file(s) were restored

   (read 

.2f KB of data from tape)

Finished 

d file(s) match the target specification

   (read 

.2f KB of data from tape)

Switches:

This tape is blank

Tape file 

d not found

 This tape contains only 

d tape file(s)

Please wait while scanning to tape file 

d . . .

Cannot read tape archive header

This tape file does not include the specified target path

Invalid tape archive header format

DOS file(s) in 

 were backed up to CTOS tape on 

s at 

Cannot read next file from tape

is a read

only file

was changed after it was backed up

is a system file

is a volume ID file

WARNING

 File 

Replace the file (y

malloc failed 

 couldn't allocate 3072 bytes

User hit CTRL

_C_FILE_INFO=

  0PX

000WP

ppxxxx

(null)

         (((((                  H

Sunday

Monday

Tuesday

Wednesday

Thursday

Friday

Saturday

January

February

March

April

August

September

October

November

December

e+000

010203040506070809101112

M61xx

Error 0

No such file or directory

Arg list too long

Exec format error

Bad file number

Not enough memory

Permission denied

File exists

Cross

device link

Invalid argument

Too many open files

No space left on device

Math argument

Result too large

Resource deadlock would occur

Unknown error

<<NMSG>>

R6000

 stack overflow

R6003

 integer divide by 0

R6009

 not enough space for environment

time error 

R6002

 floating

point support not loaded

R6001

 null pointer assignment

: MATH

 floating

point error: 

invalid

denormal

divide by 0

overflow

underflow

inexact

unemulated

square root

stack overflow

stack underflow

explicitly generated

PATH C:\;C:\LANCE;C:\CDROM

RS485

\CDROM\MSCDEX.EXE 

CDROM 

CDR Assign L: {LOCAL}[CDROM]0

PATH C:\;C:\LANCE;C:\CDROM

RS485EM

\CDROM\MSCDEX.EXE 

CDROM 

CDR Assign L: {LOCAL}[CDROM]0

xxxxxxxx

PSQRVW

_^ZY[X

t*=U=t

X=WFu

        $

t*< v

<ArI<ZwE

<0|I<9

<?|A<Z

<^|9<|t5<a|

,0r'<

XXXX$

CD Driver installation OK.

$** ERROR 

 Invalid or unknown switch character.

$** ERROR 

 Numeric parameter invalid or too large.

$** ERROR 

 Missing : after switch character.

$** ERROR 

 Invalid or too long driver name.

$** ERROR 

 Invalid command line form.

 Driver name is $Unisys LANce

PC CDROM Driver Copyright 1992 Unisys Corporation

 Driver loaded at paragraph $

CDutilityx1.0required software has not been installed.$the local network Server is down.$CD

ROM Service not installed or Server is down.$there are no available CD

ROM handles.$the CD

ROM handle last used is invalid.$the assigned CD

ROM spec is invalid.$there is no such CD

ROM device number at the server.$internal error in the CD

ROM service.$the CD

ROM drive is in use.$the drive letter has not been assigned to a CD

ROM)$the CD

ROM drive has not been opened successfully.$Invalid password.$Access denied.$Rs422.exe or Rs422em.exe is not installed.$

{LOCAL}

[CDROM]*

Assign

Error

Errors

For more error

status information type 

cdr error

CDROM Utility Commands:

Assign            List              Help                   Error

Type  CDR Help <enter>  

 to receive help

Invalid CDROM Utility command

CDROM System Internal Error

ROM Device     Assigned Path or Driver Name              Status$OK$NA$

Error from the Master (refer to the BTOS

CTOS Status Codes Manual)  

Error from DOS (refer to DOS Error Codes)  

$      $

Strike a key to continue . . . $

For $, error is $

System error $, 

.$, There are no errors to report.$

No CD

ROM device driver is installed.  You must have a

DEVICE=

 command in your Config.Sys file that installs

the CD

ROM device driver.

The Microsoft CDROM Extensions program (MSCDEX.EXE) is

not installed.  Check your AutoExec.bat file.

The {drive} parameter must be a valid DOS drive letter

between A and Z that is reserved as a CD

ROM drive letter

by Microsoft CDROM Extensions.

Local device $ assigned to the CD

ROM drive at $Not Assigned$WARNING 

 assignment could not be verified due to an error 

Please check that CDDRIVER.EXE and MSCDEX.EXE are

installed and that the 

D: switches for each contain the

same 8

character driver name (usually CT

CDROM).

$Refer to the BTOS

CTOS Status Codes Manual$

    To assign a local module, enter:

       CDR Assign L: {Local}[CDROM]0

    To assign a module on the server enter:

       CDR Assign L: {Master}[CDROM]0

    To assign a module on a server at another network node enter:

       CDR Assign L: {NodeName}[CDROM]0

    When assigning multiple modules, if you assign the first on L:

       assign the second module M: the third N: etc.

    [CDROM] is the usual name for the CD

ROM service.

    The number at the end of the command (0, 1, 2...) indicates the

       placement of the CD

ROM module on the workstation.  The first

       module (closest to the processor) is named 0, the next 1, etc.

$  Enter: CDR Help

$  Enter: CDR List

$  Enter CDR Error

CDR  ASSIGN

    Assigns MS

DOS drive letters (L: M: N: etc.,) to CD

ROM modules.

CDR HELP

    Provides information on CD

ROM commands.$

CDR LIST

    List CD

ROM drive assignments and status.$

CDR ERROR

    Displays CD

ROM system errors.$_

< t(<

t\<Ar

LASTDRIVE=Z

FILES=20

BUFFERS=30

DEVICE=\CDROM\CDDRIVER.EXE 

CDROM 

DEVICE=C:\DOS\SETVER.EXE

This pr

ogram mu

st be ru

n under 

Microsof

t Window

CTOSAPI

IBMAIN

KERNE

OOLHELP

DLL for

 Reque

 Inter

RQINTERF

=)=9=I=Y=i=y=

 uL)vUL3s

:{JIr$Oq

Ctctp?t

@aOp1

14MDMTMdMtM

]$]4]D]T]d]t]

{hVxfV

x| }0}

3@PRh

_^]YZ

=2]B]

R]b]r]

rland C+

 Copy

right 19

eIntl

bo0LmTd

acCdb

rhfoo

.barc

uest.

Unable 

to open 

h.  erc 

lGetFile

}?}O}

eckErc:

pRqSys kfa*pd

rj6j0

BerdJj0

rjrj0B

?0@0A

4T$'Q7Qs4X7Q

\KYKY

m$m0h

bmriBm

kxSbC\E

A0d7U3i+u

4E<Q<A

uh@to}

$<DpH@

2n@Va1P$

71PLa

g2$s$@

ev43*

Ar182

_P'Q]C

=*=:00

=,=<=L=\=

M,M<MLM\M

],]<]L]\]

m,m<mLm\m

},}<}L}\}

VERSION_

pVarFile

ranslati

String?

04090

CompanyN

YS Corp.

scripS

OS Reque

st API D

LL for W

indows(T

Ve{rsT

Vpc 2.0

 and 

Nce 1.2

alCopyri

) 1993,M

  All

s rese

rved.

demar

is a 

Microso

Productx

This pr

ogram mu

st be ru

n under 

Microsof

t Window

TERMINA

KERNE

LUSER

OLENTRYC

T1{46

T1572

T168F

T18:n

T2{2>

=T28D

6=T29EJ=T3

0F^=T31G

LIBMAIN

HELP 

B?B]?B

LL for 

 RequeO

ernel In

terface

ALLOCEXC

EQUEST

VPCVERS

PRYDEFAU

LTRESPdQ

RPSTRUCT

LOGINNAM

LaSif

NOTIFYRE

TR?ACE

QHOOK

EMOVE

:}J}Z}j}z}

u 61=A=Q=

AMQMaM

0m@mPm

H=X=h=

+8]H]X]

300m@mPm

y=(}8}|H}

0aEby

Rn?tQ

p@v@S

PV* 7

tV*D8

:PP>P

^Tm^T

O^T1^T

$6NP>

ftUlNteNp

Pb^tUXft.Nt'Np

F gc[

Borland 

pyright 

1991 

tl.PP

TOSRQ.TR

UserNu

, Cal

ling Add

ress=

Reque

cExchx

Respo

ERRORx

= 0xm

ppRqB

sC?ntInfo 

RtCode

PbCbU

WinAp

TOOLHE?LP.DLL

='=7=G=W=g=w=

M'M7MGMWMgMwM

]']7]G]W]g]w]

m'm7mGmWmgmwm

}'}7}G}W}g}w}

VS_VERSI

ON_INFO

VarFi

leInfo

Trans

lation

40904E4

anyName

UNISYS C

Descri

CTOS R

equest I

nterface

 DLL for

 Windows

VersT

2.0 and 

lCopyrig

0:5 (c)

 1993,Q14

)  All 

=2s reser

33L demark

is a t

5 of\<

Microsof}t

I from

ZMjMzM

]*]:]

J]Z]j]z]

m*m:m

JmZmjmzm

}*}:}

J}Z}j}z}

This 

program 

requires

 Microso

ft Windo?ws.

=+=;=K=[=

XPORTEDS

KERNEL

1.2.1100

].]>]N]^]n]

m.m>mNm^mnm

}.}>}N}^}n}

STUVW

Ht[HH7

_^][[

12345678

9ABCDEF

LANCE\

UsersE

ndingReq

uests

*<<NMS

R6000

 stac

k overfl

nteger d

ivide by

ot enoug

h space 

0viro_nment

unexp

ected he

ap error

timeY3 d

 atV 

  sup

M(M8MHMXMhMxM

](]8]H]X]h]x]

DLL must

rQ1fr

om WIN*

 85.EXE 

et PM IN

T 7Fh vO0

te rZ

al excha

eRfLDT

tem uJ  n

umber

}+};}K}[}k}

[CTRQRS4

MaxUs

ers=32

endingRe

quests=1

[FileVersion 002] [Description LANce

] [SectorsPerTrack 18]
