Microsoft KB Archive/61858

= Installing NIU-Attached Printers to Work with OS/2 LAN Manager =

Article ID: 61858

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft LAN Manager 1.0
 * Microsoft LAN Manager 1.1
 * Microsoft LAN Manager 2.0 Standard Edition
 * Microsoft LAN Manager 2.1 Standard Edition
 * Microsoft LAN Manager 2.1a
 * Microsoft LAN Manager 2.2 Standard Edition

-



This article was previously published under Q61858



SUMMARY
Network printers can be made accessible by the Ungermann-Bass (UB) NIU180 device. The NIU180 device exists as a node on the network that accepts traffic and routes requests to asynchronous devices (printers, dumb terminals, and so forth). By installing the appropriate UB drivers and device monitor programs on an OS/2 LAN Manager server, a printer can be shared without being directly attached to the server itself. The technique listed below describes how to set up an OS/2 LAN Manager server to manage an NIU-attached printer.

First, two programs from Ungermann-Bass are required:   Program        Description ---       ---   TONIUPDR.SYS   OS/2 Device Driver TONIUP.EXE    OS/2 Device Monitor NOTE: You must have the versions of these programs that work correctly with the version of OS/2 LAN Manager you are running.

In the CONFIG.SYS file, after all of the DEVICE= statements for OS/2 LAN Manager, insert one DEVICE= statement referencing the TONIUPDR.SYS device driver for each NIU-attached printer. TONIUPDR.SYS takes a device name (the device name you want to associate with the printer) as an argument. For example, assuming TONIUPDR.SYS is located on the root directory of drive C, the following DEVICE= line will load the driver for a printer that will be named NIUPRT1:   device=c:\toniupdr.sys niuprt1 After booting OS/2, one instance of the TONIUP.EXE device monitor must be started (as a background task) for each TONIUPDR.SYS driver loaded. TONIUP.EXE takes the device name (what you supplied to TONIUPDR.SYS) and the node address of the NIU180 port attached to the printer as arguments. Each port on an NIU180 has an address that consists of the serial number of the NIU180, followed by the letter &quot;A&quot;, and the port number (each port is numbered 1 through 8). For example, the following line will start TONIUP.EXE in the background for a device named NIUPRT1 that is physically attached to port number 1 of an NIU180 with a serial number of 11581:   detach c:\toniup.exe niuprt1 11581a1 Please note that several devices (for example, instances of TONIUPDR.SYS) may be directed to a single NIU-attached device by using the same node address with each instance of the TONIUP.EXE monitor program.

Once the monitor program has been started, the device can be printed to directly by using the device name (for example, copy CONFIG.SYS NIUPRT1), or by sharing the device via an OS/2 LAN Manager Spool queue. The following NET commands will create and share an OS/2 LAN Manager Spool queue for an NIU-attached printer with the device name of NIUPRT1:   net share niuq /print net print niuq /route:niuprt1 TONIUP.EXE uses OS/2 LAN Manager to interface with the network and thus requires that, at least, the OS/2 LAN Manager workstation service be started.

Additional query words: 1.00 1.10 2.00 2.10 2.10a 2.20

Keywords: KB61858

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.