Not much point in creating a config file you don't use.

If I were you, I'd talk to the Espul folks.  Their configuration files
obviously make the connection twixt logical printers on the e3k and physical
printers 'somewhere on your network', which might or might not be via IP
address.

As for reading NMMGR, any program can read it.  Deciphering it (sorry!) will
be a real can of worms though, and I don't think you'll find what you want
there anyway.

[as an example, we use Minisoft's NetPrint package, which has its own config
file; that package works by recognizing deviceclasses in the output spooler
and transferring those to the specified Novell print queue.  NMMGR?
NPCONFIG? useless!]

Good Luck!

K Tracy Pierce, Systems Programmer
Golden Gate Bridge, Hwy & Trnsp Dist
PO Box 9000, Presidio Station
San Francisco, CA  94129-0601
mailto:[log in to unmask]
415-923-2266


> -----Original Message-----
> From: John Pollard [mailto:[log in to unmask]]
> Sent: Wednesday, November 08, 2000 7:46 AM
> To: [log in to unmask]
> Subject: Re: Printer devices and IP addresses
>
>
> A couple more questions:
> 1.) What are the pros and cons of creating a NPCONFIG file
> now. We have
> been running without one.  Will it actually be used by
> anything if ESPUL is
> doing the printing?  WIll it interfere with anything?
>
> 2.) NMMGR appears to be a block mode program requiring a
> human to press
> keys. I am looking for a means of of entering a single
> command from the
> colon prompt (call it LISTDEVS or some such) which will
> display a list of
> device numbers, devices classes and internet addresses. How
> can I get the
> data from NMMGR programatically?
>