Example A-2 shows a sample installation of the LANprint software for MS-DOS, installing from drive A: to drive C:

Example A-2 Sample DOS Installation

C:\>a:install * LANprint MS-DOS Installation v1.2. * Copyright (c) 1993-1996 Vector Networks Limited. All Rights Reserved. * Copying files... * Installation complete. * * If the network software is running you can use the C:\LANPRINT\STARTPRT.BAT * batch file to start LANprint/PC, sharing a printer assigned to LPT1 as * \\pcname\LASER. You should edit STARTPRT.BAT if you wish to force another * node name (rather than the current network node name), if you want to use a * different resource name (instead of 'LASER'), or if you want to share more * than just LPT1. * * You will have to edit STARTPRT.BAT if you are running on a Novell NetWare * system, for instance, as NetWare does not set the DOS 'Machine Name', and * that is where LANprint/PC collects 'pcname' from. * * Once any/all changes have been made to STARTPRT.BAT, you can start * LANprint/PC as follows: * * C:\LANPRINT\STARTPRT * * or, perhaps from the AUTOEXEC.BAT file immediately after the command to * start DECnet (CALL C:\DECNET\STARTNET), or any other network transport, * you can add CALL C:\LANPRINT\STARTPRT * * C:\LANPRINT\LANPRINT -H will give a help screen showing all command options. * Please see the documentation for further details. C:\LANPRINT>lanprint -h LANprint - Version 1.1 - 10-Sep-1993. Copyright (c) 1993 BTVC & Vector Networks Limited. All Rights Reserved. LANprint/PC Print Gateway Program LANPRINT. Usage: LANPRINT [-option] <LPTx[=name]>[ -p:<password>] ... -option -option ... Options: -A:<Adapter_num> Default : <0> -B:<Buffer_size> Default : <4136> . . . C:\LANPRINT>startprt ------------------------------------------------------------------------------- * Setting up print redirections and starting the LANPRINT Gateway * LANprint v1.2 * Copyright (c) 1993-1996 Vector Networks Limited. All Rights Reserved * * Setup completed ok. Starting LANprint/PC. * LANprint - Version 1.1 - 10-Sep-1993. Copyright (c) 1993 BTVC & Vector Networks Limited. All Rights Reserved. LANprint/PC Print Gateway Program LANPRINT. LANprint/PC: Server Resource Table : No Local Device Resource Alias Network Path Password -- ---------------- ---------------- ------------------------------------ ----- 1 LPT1 LASER \\DELL\LASER <No> -- ---------------- ---------------- ------------------------------------ ----- Server initialisation complete. Starting to Serve the Network. To shut the Server down safely, type <Control-C> once. To force the Server to exit, type <Control-C> twice.

A.4 Package Removal

The VIAREMOVE.COM command procedure can be used to remove selected VIA package(s) from a system after a trial. To do this, login as user SYSTEM, ensure that no-one is using LANprint, and execute the following command:-

$ @viaroot:[via]vialppshutdown

This will start the shutdown process, as described in Section 3.11.

Once the shutdown has completed, you can delete the package files by issuing DCL DELETE/QUEUE commands for each LANprint queue and then executing the following command to delete the files:-

$ @viaroot:[via]viaremove

VIAREMOVE.COM will prompt you to select which of the installed VIA package(s) are to be removed.

VIAREMOVE.COM can also be used to delete all VIA products from your system. To do this, a slightly different procedure is required (after deleting all LANprint queues):-

$ set default sys$manager $ copy viaroot:[via]viaremove.com [] $ @viaremove

In this case, it is necessary to copy VIAREMOVE.COM to a location outside the VIA directory tree. Once copied, it can be executed directly, and the option to delete the entire tree selected. VIAREMOVE.COM itself will also be deleted in this case.

The installed files can be removed using the following commands:-

C:\>c: C:\>cd \ C:\>del lanprint Are you sure? y C:\>rd lanprint

(Assuming that the DOS software was installed on drive C:).

It is important that any reference to LANprint/PC in AUTOEXEC.BAT is also removed.

If the Operator message feature is not disabled, the LANprint Symbiont will report error conditions by using the $SNDOPR System Service. This will produce messages with the following format:

%%%%%%%%%%% OPCOM 15-NOV-1995 21:23:04.27 %%%%%%%%%%% Message from user SYSTEM SYMBIONT_1 - Error Accessing Remote Server <EPSON> %SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node

These messages will be added to the operator log file, and may also be output on suitably configured operator terminals.

All Symbiont-generated messages come from user 'SYSTEM'. The following line identifies SYMBIONT_1 as being responsible for the message. This line also includes the error message. In this case, the remote server was not accessible. The VMS error message corresponding to this error is listed on the last line of the report. VMS error messages, and the actions needed to recover from them, are described in Appendix C.

When the Symbiont starts it will output its sign-on message in the following way:

%%%%%%%%%%% OPCOM 31-JUL-1996 21:12:11.93 %%%%%%%%%%% Message from user SYSTEM on VLC LANprint - Version 1.2 - 31-Jul-1996 - Kit #07D4 LANprint Print Symbiont - Evaluation Package. Expires on 30-AUG-1996

The following console messages are generated:

SYMBIONT_1 - Error Accessing Printer Database File.
Explanation: The Symbiont was unable to open the database file for read.

SYMBIONT_1 - Error Accessing Remote Resource <resource>
Explanation: The Symbiont was unable to access the specified resource.

SYMBIONT_1 - Error Accessing Remote Server name
Explanation: The Symbiont was unable to contact the server.

SYMBIONT_1 - Error Creating Spool File on \\name\resource
Explanation: The Symbiont was unable to create a spool file.

SYMBIONT_1 - Error Writing Spool File on \\name\resource
Explanation: An error occurred while writing to a remote spool file.

SYMBIONT_1 - Insufficient memory for session data structures.
Explanation: The Symbiont was unable to allocate sufficient dynamic memory.

SYMBIONT_1 - NetBIOS initialisation failed - Network not accessible.
Explanation: The Symbiont was unable to access the NetBIOS network. This is likely to be caused by an attempt to access a system over the TCP/IP transport when the underlying TCP/IP stack itself is not running, or when LANprint fails to identify it.

SYMBIONT_1 - Unexpected error 9999 occurred during initialisation.
Explanation: An unexpected error occurred...

Message from user JOB_CONTROL -SYSTEM-W-ENDOFFILE, end of file
Explanation: When all of the queues that a particular Symbiont was processing have been stopped, the Symbiont may exit abnormally, causing this message which can safely be be ignored.

The following error messages can be output by the LANprint Symbiont or by the Utility Programs. LPPPRINT errors are indicated by a message following "ERROR". These messages are quite detailed, as they are intended to assist in debugging faulty installation or network conditions. LPPQUERY errors are listed next. The Print Symbiont uses VMS RMS and SYSTEM error message codes, as these are always available on VMS systems. In some cases, the meaning is not quite the same as that originally intended by Digital.

When accessing the Printer Database, RMS errors will generate RMS error messages. This appendix describes the most common RMS error messages. For further detail on RMS error messages, please refer to the VMS RMS documentation.

ERROR 9999 occurred accessing resource resource_name
Explanation: LPPPRINT was unable to access the named resource on the remote print server.
User Action: Check to ensure that the server has shared the correct print resources, and also make sure that the resource name is correct in the Printer Database. If the name is incorrect, the template file must be corrected and the database rebuilt before the operation can be retried.

ERROR 9999 occurred calling server_name
Explanation: LPPPRINT was unable to contact the named server.
User Action: Check to ensure that the named server is running. If the name is incorrect, the Printer Database must be corrected and rebuilt before the operation can be retried.

ERROR 9999 occurred closing the remote spool file.
Explanation: LPPPRINT failed to close the remote spool file.
User Action: The error number should correspond to the VMS error message that is printed after LPPPRINT exits. This message is an indication of the nature of the problem. Correct the problem, and retry the print operation.

ERROR 9999 occurred creating a remote spool file.
Explanation: LPPPRINT was unable to create a spool file on the remote print server system.
User Action: The error number should correspond to the VMS error message that is printed after LPPPRINT exits. This message is an indication of the nature of the problem. Correct the problem, and retry the print operation.

ERROR 9999 occurred de-registering name network_name
Explanation: LPPPRINT was unable to de-register its network name before it exited.
User Action: This should not occur. Please report.

ERROR 9999 occurred during data spooling sequence.
Explanation: LPPPRINT failed to send all of the data to the print server.
User Action: The error number should correspond to the VMS error message that is printed after LPPPRINT exits. This message is an indication of the nature of the problem. Correct the problem, and retry the print operation.

ERROR 9999 occurred during End Connection sequence.
Explanation: LPPPRINT encountered an error as it was disconnecting from the print resource at the remote server.
User Action: This is not a fatal error. The print file should be printed correctly (so long as this was the first error).

ERROR 9999 occurred during Verify Dialect sequence.
Explanation: LPPPRINT was unable to negotiate an acceptable dialect of the SMB protocol.
User Action: This is a fatal error. LANprint supports the "PC NETWORK PROGRAM 1.0" dialect of the SMB protocol.

ERROR 9999 occurred hanging up session to server_name
Explanation: LPPPRINT encountered an error as it was disconnecting from the remote server.
User Action: This is not a fatal error. The print file should be printed correctly (so long as this was the first error).

ERROR 9999 occurred registering name network_name
Explanation: LPPPRINT was unable to register its network name on the NetBIOS network.
User Action: This could be the result of a name clash if another LPPPRINT program is running on the network. Wait for a while and try the operation again, when the clashing program may have stopped.

ERROR: Database file filename open failed.
Explanation: LPPPRINT was unable to access the named database file.
User Action: Check the filename and retry the print operation.

ERROR: Database file read for device device failed.
Explanation: LPPPRINT was unable to access the data for the named device in the Printer Database.
User Action: Check the device name and retry the print operation.

ERROR: Error allocating session data from pool.
Explanation: LPPPRINT has encountered an internal error.
User Action: This should not occur. Please report.

ERROR: Insufficient memory for network data structures.
Explanation: LPPPRINT was unable to allocate sufficient dynamic memory.
User Action: This should not occur. Please report.

ERROR: NetBIOS initialisation failed - Network not accessible.
Explanation: LPPPRINT was unable to access the NetBIOS network.
User Action: Make sure that the NetBIOS is running and retry the operation. If you are using the embedded DECnet or TCP/IP support, ensure that the DECnet or TCP/IP software is itself running. If you are using TCP/IP with the LPPQUERY program, then ensure that you have VMS SYSPRV privilege. If you are using an external LANlink NetBIOS, check that it is running and not trying to shutdown.

ERROR: Open failed for file filename.
Explanation: LPPPRINT was unable to open the named input file(s).
User Action: Check the filename and retry the print operation. LPPPRINT doesn't support any wildcard filenames. LPPPRINT is intended to verify the connection to a remote server; if you wish to print multiple files, you should use the Symbiont with normal VMS PRINT commands, which do support wildcards.

ERROR: Too many arguments - argument
Explanation: LPPPRINT has detected a command line error.
User Action: Remove the excess argument(s) and retry the print operation.

ERROR: Unexpected error 9999 occurred during initialisation.
Explanation: LPPPRINT was unable to allocate sufficient dynamic memory.
User Action: This should not occur. Please report. The listed error number can be converted into a VMS error message using the DCL EXIT command. Type EXIT followed by the error number and press the <Return> key to see the corresponding VMS error message.

ERROR: Unrecognised option option
Explanation: LPPPRINT has detected a command line error.
User Action: Remove the unrecognised option and retry the print operation.

%LPPQUERY-E-OPNERR - Database file filename open failed.
Explanation: LPPQUERY was unable to access the Printer Database file.
User Action: Check the filename specified. Correct the problem and retry the query operation.

%LPPQUERY-E-READERR - Database file read for device device_name failed.
Explanation: LPPQUERY was unable to access the data for the specified device in the Printer Database file.
User Action: Check the device_name specified. Correct the problem and retry the query operation.

%RMS-E-FNF, file not found
Explanation: The LPPDIR:LPPDATABASE.BIN file could not be found.
User Action: Ensure that the LPPDIR logical name is defined system-wide to reference the directory containing LPPDATABASE.BIN, and that the file is accessible to the SYSTEM account.

%RMS-E-RNF, record not found
Explanation: An attempt was made to start a queue which was initialised with /ON=device_name qualifier for which the device_name entry was not found in LPPDIR:LPPDATABASE.BIN. Or LPPQUERY was unable to find the requested device entry in LPPDIR:LPPDATABASE.BIN.
User Action: Check the /ON= qualifier on the INITIALIZE/QUEUE command. If the device_name field has been mis-spelt, delete the queue and initialise it again with the correct name. Check the device_name entry in LPPDATABASE.BIN with LPPQUERY. If LPPQUERY also reports this error, you should ensure that the device is defined in LPPDATABASE.DAT and then rebuild the database with the LPPDATABASE utility.

%SYSTEM-F-BADLOGIC, internal logic error detected
Explanation: An internal software check has detected an error. This should not occur.
User Action: Please report the conditions under which the error appeared.

%SYSTEM-F-FORMAT, invalid media format
Explanation: The server responded with an invalid SMB protocol message.
User Action: This message may be produced when a print job is being aborted. Try again. If the error is repeated, there is a problem. Please report the situation under which the error occurred.

%SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
Explanation: The server node did not respond to the network connect request.
User Action: Check the network connection to the remote node. Check the database entry for the remote server, using the Query Program, to ensure that it contains the correct values, and make sure that the requested print resource is available on the server. If you are using TCP/IP, you may need to create the [VIA.TCP]NBHOSTS.DAT file and add an entry for the target node name, or you may have to specify a NetBIOS name scope to be used to qualify names that are used on the network. Please refer to Section 3.3.6 for more details of TCP/IP configuration.

%SYSTEM-F-NOTPRINTED, failed to queue spool file for print
Explanation: The server returned an error code to our SMB SPOOL_BYTE_BLOCK command, or, LPPPRINT was unable to print the requested file(s). The data has not been placed in the remote spool file.
User Action: Check the remote printer is running, and the server has sufficient free disk space. Then, retry the print operation. In the case of this error being reported by LPPPRINT, refer to the description associated with the "ERROR:" message that accompanies this error.

%SYSTEM-F-OPINCOMPL, operation is incomplete
Explanation: The server returned an error code to our SMB CLOSE_SPOOL_FILE command. The remote spool file has not been queued correctly.
User Action: Check the remote printer is running, and the server has sufficient free disk space. Then, retry the print operation.

%SYSTEM-F-PROTOCOL, network protocol error
Explanation: The server does not support the "PC NETWORK PROGRAM 1.0" dialect of the SMB protocol. This is a fatal error.
User Action: Buy a new server.

%SYSTEM-F-REJECT, connect to network object rejected
Explanation: The server did not allow access to the print resource.
User Action: Make sure that the print resource is available on the remote system. Check the password matches the remote resource password. Ensure that network access control, or routers or bridges in between the host and target systems, do not disallow the desired network connection.

%SYSTEM-F-REMRSRC, insufficient system resources at remote node
Explanation: The server node did not have sufficient resources available at that time to accept the SMB CREATE_SPOOL_FILE command. Try again later.
User Action: Make sure that the remote printer is running.

%SYSTEM-F-TOOMUCHDATA, too much optional/interrupt data specified
Explanation: An individual print file data record was too large to fit in the maximum message size allowed by the remote server.
User Action: This message may occur when the LPPPRINT program is used. Create the file with smaller records. All servers are guaranteed to be capable of handling print records 470 bytes long.

%SYSTEM-W-NOSUCHDEV, no such device available
Explanation: An attempt was made to start a queue over a network transport which was not available. The queue has been initialised, but not started. Or, an attempt was made to use LPPPRINT to print a file over a network transport which was not available.
User Action: Ensure that the network transport (e.g. DECnet, or a LANlink stack) is running and that the 'device' entry in LPPDATABASE.BIN is correct - check it with LPPQUERY. If it is wrong ensure it is set correctly in LPPDATABASE.DAT and rebuild the database with the LPPDATABASE utility. The queue will be in a "stopped" state. Once the transport has been made ready, the queue can be started, or the LPPPRINT command repeated.