
------------------------------------------------------------
NOVPRIN1.DOC -- 19970604 -- Email thread on NetWare Printing
------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Tue, 8 Aug 1995 03:56:12 -0400
From: "Michael D. Setzer II" <MICHAEL@GCCCC.GUAM.NET>
Subject: Re: Alternatives to pserver

>Does anyone have any good alternatives to running Novell's pserver.nlm on
>NW 3.12?  We need to run more than the 16 printers and we don't want to
>have a whole bunch of dedicated printer servers either.

You can try FPserver (Fast Printer Server), it if from Richard Hartman
rlh@comtch.iea.com, and is $95 for a file server license. You can run
up to 7 printers off of each computer, 4 serial and 3 lpt. You can have
as many computers as you want setup for the license, it is licensed per
server. We have two of them running on our lan providing 3 printers in
each lab. Another server on campus also has purchased it, and has two
print servers running on there lan. Printing is fast, and it uses the
same queues as novell, so nothing special has to be down. The program
is available at netlab2.usu.edu, don't remember the directory. This is
the full program, it is only the key the you need to purchase. Without
the key, it will only run for 20 minutes at a time. So, you can check out
the program before paying anything. We are using old 8088 computers, and
it can run all three of the printers connected as fast as they can go.
It also doesn't use interrupts, so you don't have to worry about that.
I have been very happy with this solution, and since you can run many
printers off a single computer, it is good. It also allows monitoring
what is printing, and you can delete and rush jobs from the printserver.

------------------------------

Date: Mon, 25 Sep 1995 14:00:16 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: garbled net printing

>I have strange network printing problem.
>
>On a couple of my netware workstations, network print jobs are garbled,
>the banner page prints out fine, then it prints the same string of
>garbled characters, these workstations print perfectly on local printers.
>
>The workstations are windows 3.1, vlm, on 3.12 server.
-----------------
	Capture, with /NOTAB so that control code HT (horizontal tab) is
not converted to spaces. Also, if you are sending Postscript material
to a printer which auto-recognizes PS vs regular text then turn off the
banner (save trees) so that the PS header is seen as the first thing.
Finally, tell Capture to use a decent timeout interval, say 30 seconds
or so, such that all the printer output of the application arrives as
one print job rather than dribs and drabs (especially if there are any
graphics involved).
	Joe D.

------------------------------

Date: Tue, 26 Sep 1995 11:36:59 -0400
From: John Carter <carter@CVAX.IPFW.INDIANA.EDU>
Subject: Windows / Rprinter

I have seen a bunch of messages latley about using Rprinter in Windows.
There is a better product to do such a thing, it is called WINSERV
It comes with a 50 user/station license for $150.00 + $15 for shipping.

It is a real windows program that does the same purpose as Rprinter.
You can have the printers hooked up to printer ports or com ports, and
adjust the speed, etc.  It keeps track of the number of pages printed, and
has popups to alert the user of paper jam, paper out, off line, etc..

We have ditched all rprinter and switched to this product for all
departments that do not/can not afford to buy the prefered print server
card for their printers.

For more info, contact Toni Speidel  at  100332.1402@compuserve.com
Phone +46-40-321065  Fax   +46-40-118790  Product Implememtation and
Development AB Forskningsbyn Ideon  S-205 12 Malmo  Sweden

------------------------------

NVQSRV v1.0 (shareware), by Marc Snider, buzz@world.std.com, provides for
redirection of Netware queue jobs to other Netware queues on the same or
other Novell servers, LPR service queues or to a variety of custom queue
destinations.  This utility provides postscript filtering, statistical
tracking by queue, detailed job status screen, and customizable job server
configuration capability.  Currently utilized print server connections can
be freed up by Novqserv's facility for redirecting queues to a centralized
printing file server.

	ftp://ftp.coast.net/SimTel/msdos/novell/nvqsrv10.zip

Floyd Maxwell

------------------------------

ftp://ftp.coast.net/SimTel/msdos/novell/ulist52.zip

ULIST v5.2 is a replacement for the existing userlist of Novell with
several enhanced features promoting management of the server.  It also
has other added programs that can be quite useful for users and admin.

ShareWare.

Contact Marius Eugene van Wyk, marius@jupiter.cs.up.ac.za

Floyd Maxwell

------------------------------

Date: Wed, 1 Nov 1995 17:52:36 -0800
From: John Navarro <jnavarro@MCGRAW-HILL.COM>
Subject: Re: UNLOAD PSERVER = DEATH! :-(

In the 4.1 Admin class it is taught that one should never load/unload
pserver from the console.  Rather, use pconsole or nwadmin to do so.
If you have a 3.x server look in pconsole.

---------

Tom, that's _not_ the way to bring down a printserver since it keeps
files open.
Do it by logging in as supervisor, starting Pconsole, going to
Printserver info, choose the server, go to status & control, then to
status and bring the printserver down only there.

Henno Keers

---------

>Are you using any HP JetDirect adapters on the network? If you are, it
>seems that they are not recognizing that the print server is going down.
>The work around is to use the JetAdmin software, and for each printer
>still showing as connected in the status box go into Configuration/
>Advanced/Restart NetWare Protocol and just do a protocol restart. This
>will drop the connection to the print server. Once you do that for each
>printer, PServer will unload automatically. I have had this problem for
>ages and this was the only work around I could find.
-------------
	Something to keep in mind here. Pserver is definitely fatal to the
server if it is unloaded with print queues open and busy, and if servicing
a printer. Close the queues (Pconsole, say NO to the second entry about
jobs being dequeued), wait for printer jobs to drain (Pconsole again).
	Basically, don't unload pserver.nlm while it's busy.
	Joe D.

------------------------------

Date: Fri, 10 Nov 1995 09:24:53 -0800
From: Charles Martini <cmartini@HALCYON.COM>
Subject: Seek Advice on using HP JetDirect w/ NW4.1

>1.      Can JetDirect handle NDS print queues?
>2.      Can JetDirect act as a NDS PSERVER?
>3.      If not, I know it should handle bindery print queue. How can I
>configure it, what installation problem should I expect?
>4.      What administration problem will arise after installation, I mean,
>in long term?

We have about a hundred JetDirect cards on our 4.1 network, and we're
VERY happy with them.  But, we've been using ours in bindery emulation
thus far.

I just came from an HP Technical Symposium, where we addressed the issue
of Jetdirect & NDS in great depth.  In order to use JetDirect in NDS
mode, you need to:

	a. Ensure your version of JetDirect supports NDS (see www.hp.com
for more info-they have free firmware upgrades for many older JetDirects)

	b. Use the latest JetAdmin software.  You can tell if it supports
NDS by looking at the Printer Config screen: there's an entry for "NDS
Tree" and "Print Server Context" if your JetAdmin supports NDS.  If it
doesn't, you can download the latest from www.hp.com.

	c. Use NWAdmin or PConsole to setup your printing environment.
Name the print server object the name that you'll want the JetDirect to use.

	d. Run JetAdmin, and enter the NDS tree and print server context
in the appropriate field.  Name the JetDirect interface the same name you
used for the print server you created in NWAdmin or PConsole.

	e. According to HP, your JetDirect should now be configured to
operate correctly in Queue Server mode with full NDS support.  You can
even place aliases of the print server object in different contexts, and
thereby easily allow access to the printer by users in many contexts.

If you create your print queues in JetAdmin, you'll be creating
bindery-based queues.  While they'll work fine (as long as your also
create an "Everyone" group to give rights to the queue), if you have to
do a restore, you'll have to recreate the queues.

------------------------------

ftp://ftp.coast.net/SimTel/msdos/novell/pcnt312a.zip

PCOUNTER v3.12a is a page counting print server for Novell NetWare.  It
comes in EXE (Dedicated print server) and NLM flavors.

Features:
 - Counts pages on PCL and PostScript printers.
 - Logs all printer activity and maintains user accounting.
 - Custom banners, remote control.
 - Support for parallel, serial, and networked printers.
 - Novell print queue to UNIX LPR gateway.
 - Automatically converts text to PostScript if necessary.
 - Integrated printer and queue management.
 - Automatically place jobs on hold, delete old print jobs.
 - Reject incorrect print job types and incorrect paper sizes.

Andy Charmatz

------------------------------

Date: Tue, 2 Jan 1996 10:13:40 +0000
From: Marc Bornebusch <marc@NETUTIL.DEMON.CO.UK>
Subject: Re: Netware printing

>We are using Netware 3.12 in a classroom environment.  Is there a way
>to control (read limit) the amount of print a user can spool ?

We have a product called Qmeter that is for controlling tha amount of
printing that users may do on the network. It installs as an NLM on
Netware 3.x servers (version for 4.x under development) and will count
the number of pages of print jobs. You can set limits if you wish to
based on a user, queue or a user on a specific queue. You can also set
limits on the maximum number of pages allowed per job.

We have fully working evaluation copies available at
	ftp.u-net.com/com/netutils/qmeter.zip.

Qmeter provides, at the minimum, a simple method of
monitoring each users output (in pages) to any print queue
on a NetWare network. Qmeter can also enforce administrator
defined page limits and if required provide a complete
accounting system with users required to pay or account for
all print usage.

NetWork Utilities (Systems) Ltd

------------------------------

From: Garry J Scobie Ext 3360 <GSCOBIE@ml0.ucs.ed.ac.uk>
Date: Mon, 8 Jan 1996 08:30:37 +0000
Subject: Another FAQ entry?

Q. Can I turn off the AppleTalk Print messages that are filling up my
   error log?

A. Yes. When loading the ATPS.NLM use the -S switch. This will turn
off AppleTalk Printing messages, keeping the size of your SYS$LOG.ERR
down.

------------------------------

From:	Stephen M. Dunn <bokonon!stephen@GTS.ORG>
Subject: A FAQ suggestion
Date:	Sat Feb 17 20:33:02 1996

Q: VLM is configured for nine printers, but Windows only allows three.

A: You may need to add a few lines to your WIN.INI.  You will find
the lines LPT1:=, LPT2:=, and LPT3:= in your WIN.INI; add LPT4:=
through LPT9:= after them and restart Windows.


Q: VLM is configured for nine printers, but CAPTURE only allows three.

A: CAPTURE.EXE, in 3.12 and below, is hard-coded to only allow
three printer ports to be captured, even though VLM allows up to
nine.

   You can capture additional printer ports in Windows using
the NetWare User Tools program.  If you have access to the
NetWare 4.x utilities, you can try copying them to your 3.x
server; be careful to back up your 3.x utilities first, and
to get all of the required support files, since most .EXEs
in 4.x also require at least one .MSG file to go along with
them.

------------------------------

Date: Sat, 23 Mar 1996 11:11:57 -0800
From: Debbie Crowley <debmc@DELTANET.COM>
Subject: PrintDef Jobs (copying to mulitiple users)

>I'm looking for a way to quickly copy Netware print job configurations to
>our users.  We need to copy the same set of print configurations to about
>100 users, and Netware's way of doing this via PrintCon one by one is
>going to be very time consuming and error prone.  I can't seem to find a
>util that does this and was wondering if anyone knew of one.

This is an annoying limitation of PRINTCON.  Here's a neat solution to
your problem, it lets all users access the same PRINTCON.DAT file:

There's an obscure NetWate command called SMODE (Search Mode), which
modifies the way NetWare searches for data files (yes, data files) whose
path isn't specified. It allows you to use search mappings for data files!

The syntax:	SMODE path mode
 path = pathname of the executable file that will be looking for the data
 mode = search mode being set (there are 7 modes available, we need to
	use mode 5.

Quoting the NetWare 3.12 Utilities manual directly for Mode 5:
  "If a directory path is specified, the executable file searches the
   path first and then the search drives.  If no path is specified, the
   file searches the default directory first and then the search drives."
	(See pages 331-338 for a full explanation on SMODE.)

Now to apply this:
1. Login as Supervisor
2. Create PRINTCON.DAT file that contains the defaults for everyone.
   Remember PRINTCON.DAT file goes into each user's MAIL directory.  Since
   we are logged in as Supervisor, it will go into SYS:MAIL\1.
3. Copy SYS:MAIL\1\PRINTCON.DAT to SYS:PUBLIC
4. Flag SYS:PUBLIC\PRINTCON.DAT as sharable, read-only
5. Now change the search mode of the printing commands as follows:
	SMODE Z:NPRINT.EXE 5
	SMODE Z:CAPTURE.EXE 5
	SMODE Z:PCONSOLE.EXE 5
6. Now when any of these commands are executed (because they are located
   in PUBLIC, their default directory is PUBLIC), the default directory
   will be searched first for PRINTCON.DAT, which means the one in public
   will be found prior to the one in MAIL\usierid.

------------------------------

Date: Thu, 18 Apr 1996 14:03:45 -0800
From: Stephen Herzog <herzogs@SDESIGN.COM>
Subject: How to pay  prints using an inteligent card ?

>We are using Novell Netware 4.1 / 3.12 servers to share printers in our
>computer labs. Students pay for printing pages to shared printers and we
>want to automatize the payment using an inteligent card the students have.

The following list is of places that make printer vending card systems,
and printer accounting systems/software.  Secure Design has not had any
contact with these companies, we are just providing a list for your
reference.  We obtained these addresses from some of our clients who
have used their products.

	Controlled Access Ltd,           (hardware - vending card reader)
	5-6 Station Estate, Oxford Rd,
	Wokingham, Surrey RG11 2QY, United Kingdom
	Phone: (44)734-772255, Fax: (44)734-772296

	PCounter by AND technologies     (Software print server)
	P.O. Box 64811
	Los Angeles, CA 90064
	E-mail: 71011.3570@compuserve.com
	I believe a demo is available for FTP from oak.oakland.edu in the
	/pub/simtel/msdos/novell directory.

	TRACsystems                      (hardware - vending card reader)
	5635 Yale Boulevard
	Dallas, TX 75206 USA
	Phone (214) 369-6576

	Copi Card                        (hardware - vending card reader)
	12900 valley Branch Ln.
	Suite 400
	Dalas, TX 75234

	Harco Industries, Inc.           (hardware - vending card reader)
	2362 West Shangri-La Road,
	Phonenix Arizona 85029  USA
	Phone 1-800-528-0465

To augment any of the above, Secure Design has a print queue manager
called QView Pro. QView can assist in showing what print jobs are being
sent to the individual printer.  This helps quite a bit in determining
who's vending card should be placed in the card reader when several users
are sharing a printer.  A demo copy is available at the world web site
http://www.peak.org/~sdesign or by e-mail at "auto-help@sdesign.com"
(send a message with a subject of "help")

------------------------------

From:	uk2r@rz.uni-karlsruhe.de
Subject: something for the FAQ
Date:	Thu, 9 May 1996 23:31:47 +0200 (CES)

Concerning printing from NetWare to a UNIX system and vice versa,
there is a collection of programmes called "ncpfs". The main
purpose is to mount NetWare servers into the filesystem of a
Linux host. (Another probably interesting topic... you get
access to all volumes on the selected server, including CD-ROM)

Anyway; Also contained are two utilities called "pserver" and "nprint".
With "pserver" you can connect to a NetWare server and let the
Linux machine service a print queue of your choice. 

"nprint", on the other hand, lets you put print jobs to a standard
print queue. Printing banners etc. is possible.

Especially useful is the following:

Create a print queue and a print server account on your NetWare
server. Run "pserver" on your Linux machine and pipe all incoming
jobs into a magic filter, i.e. apsfilter, for PostScript etc.
conversion. Configure the filter to print via "nprint" instead of
"lpr". Thus you get a PostScript printing facility for your NetWare
for no money at all. Additionally, if you have several UNIX machines,
they can all, too, print to the NetWare queue. 

Advantage over server-based products: Besides creating a queue and
a print server account, you need not at all touch your NetWare server.
Seemes very safe for me, and has been running for more than three
months with no problem at all.

Disadvantage: A server connection is taken by the print server. If you
want several print queues serviced, you need to run "pserver" more
than once, which of course uses more connections. As the source code
is distributed with the software, one should be able to change this,
anyway.

"ncpfs" can (besides others) be obtained from:

  ftp://ftp.switch.ch/mirror/linux/sunsite/systems/Filesystems/ncpfs

------------------------------

Date:	Thu, 23 May 1996 14:26:13 GMT-0100
From:	Andre Boogaards <A.Boogaards@hsu1.fnt.hvu.nl>
Subject: Novell FAQ Addition

When a user is logged into a workstation that hasn't been rebooted
since another user has logged off, a submitted printjob has an
identification of the first user, like this:

- USER1 logs on, submits a printjob
- In pconsole the job-owner is USER1
- USER1 logs off
- USER2 logs on (without rebooting the workstation)
- USER2 submits a printjob
- in Pconsole the job-owner is USER1!!

To solve this problem, you could force all users to reboot the pc in
between, but this isn't really efficient. Alternatively you could put
a /NAM=%LOGIN_NAME on the capture statement. However, this causes the
system to produce a bannerpage if the /NB switch is put in front of
the /NAM switch. Move the /NB to the end, and this problem is fixed too.

	[Thx Sidney Skinner and Andre Boogaards]

------------------------------

Date: Wed, 29 May 1996 10:30:26 +0100
From: Bruno Belhassen <Bruno_Belhassen@EUROPE.NOTES.PW.COM>
Subject: Re : Error printing to more than 3 queues with VLM under Dos

>Will any programs running under DOS print to LPT4 or higher or am I
>restricted to LPT1, LPT2 and LPT3?  Windows can print to LPT4 and others
>without too much trouble.  Is there a setting I am missing to allow DOS
>programs to also print to LPT4?

Programs running under DOS can't print to LPT4 or higher because DOS only
manage three parallel ports.

However, you could use a netware program called NPRINT because no LPT? is
required; Just a print queue or a printer (NW 4 only).

If you want to print with a DOS command, try the following :

 - Type FILENAME > LPT4:        (ASCII format)
 - copy /b FILENAME LPT4:       (BINARY format)

------------------------------

Date: Thu, 30 May 1996 16:37:25 -0400
From: PowrTekSys@aol.com (Kevin C. McIntosh)
To: netw4-l@bgu.edu
Subject: Re: Printing with 32-bit clients

>>Management thinks that if the Novell client32 works with an HP4 or 5
>>it should work with all HP printers, so I must be the problem.
>>
>>Does anyone have an idea as to why one client works and the other prints
>>gibberish?  Is there a config. parameter, in the Novell client32 that I
>>can modify?
>
>I don't really know why one client 32 works and another doesn't. But I do
>know that most and perhaps all InkJet printers are designed for standalone
>use and not recommended for network use.  This is becoming true of your
>low end laser printers also. Cannon and HP have taken advantage of Pentium
>technology (my opinion). The processor was basically removed from the
>newer InkJet printers. The printer uses the computers processor and ram
>to process the print job. Perhaps Microsoft's Client 32 can enable a
>remote computer to communicate better than Novell's Client 32.  It was not
>that long ago we could take a $300 Ink Jet or laser printer and make it a
>Network printer very easy. Now you almost have to spent $1,500 + for
>simple print sharing. Perhaps Novell's new Nprinter for Client 32 will
>address this?
>
>I have not asked HP, but Cannon did tell me that they do not recommend
>any of their InkJet printers for shared network use.
>
>Roger W Taylor

Thanks for the reply.  This is the truth that I was fearing to tell
management.  Your missive may help the news go down a little less sour.

------------------------------

Date: Sat, 1 Jun 1996 09:23:38 -0400
From: Bill Ott <grmweo@LAKELAND.LIB.MI.US>
Subject: Re: HP Deskjet Printers (600,660C,850C) on NW 3.11

The bi-directional communication of these HP printers causes more problems
than they're worth.  I haven't used these printers specifically in the
above mentioned manner, but you may try this:

	- in Windows launch hpfcfg02.exe

	- disable the Print Cartridge Query and Bi-Directional
	Communications

That may help.  If not try using the HP 500 or 550C drivers, they will work
with the 600 series, I'm not sure about the 800's.

Of course the best solution is to use an HP 1200 or 1600 with a JetDirect
card...

------------------------------

Date: Fri, 7 Jun 1996 11:12:37 -0600
From: Todd Herring <THERRING@SPEANET.IUPUI.EDU>
Subject: desktop printing vs. network printing -Reply

>I need some help preparing arguments for a move to a centralized
>printing model. Any advice that would make this proposal a success
>would be greatly appreciated.
>
>Almost all of the admin staff here have a laser printer directly attached
>to their PC directly.
>
>[snip]
>
>PROS:
>
>  - driver updates are easier to manage
>  - minimal staff training needed
>  - maintenance costs would decrease due to the decreased number of
>    printers.
>  - MTBF would be highest as the proposed printers would be new, this
>    would also decrease maintenance costs
>  - network management would decrease as these printers all have
>    their own "jet admin" queue management
>  - cost per page would be reduced on each printer
>  - depreciation costs would decrease due to increased usage
>  - reduced capital expenditure
>  - staff would have to get out of their chairs to get their print
>    jobs, thereby increasing their circulation
>  - users would complain that the sensitive documents may be seen by
>    others(how sensitive could it be, it is a high school after all!)
>
>CONS:
>
>  - users complains that sensitive documents may be seen by others
>  - staff would have to get off their (ahem...)chairs to get their
>    print jobs
>  - individuals would perceive this as taking a valued possession away
>    from them.(this possessive mentality is pervasive and widespread)

I'd say you've done your homework.  You have some very good arguments for
implementing a centralized printing model.  Remember, it is a model, not an
absolutely inflexible way of doing things.  If there are one or two users
who _really do_ print sensitive information, then why not give them local
printers?

As for adding more CONS to your list....  Some people might see it as a
security risk, in that you've got bits and bytes of print data on the wire
that could be "seen" by others (using a sniffer, they might say).  Pretty
easy to argue against that, though.  Another is the delay.  It might take
1.020134 seconds longer to print that mail message.

---------

I have 50 users myself and understand exactly what you are going through.
They can be quite lazy when it comes to walking a few steps to pick up their
printing.  Ours was a matter of location...not enough workspace to give
everyone their own printer.

First order of business is to find out what kind of sensitive and
confidential printing they claim they need their own printer for.  Have them
make a list and go through it with them and their higher ups to discuss the
confidentiality of each and every piece. This should narrow down the field
quite a bit.  What I have done is given smaller printers to those few,
directly attached to their PC.  This had the backing of their superiors and
everyone was happy.  Everyone else is in a pool with strategically located
printers.  A printing pool is also very helpful when any printer is down for
repair.  All they need to know is the location of the printers, printer
server names and queues, so that they can spool printing to another printer
if needed.  We also do this with our expensive color printers.  {Put the
name of the queues/servers on the printers themselves, so you don't have
to answer those questions; place manuals near each machine in case they
have problems, mark all toner cartridges on the outside so that they can
change those too and give them instructions on how to clean and change
toner cartridges.)

Micki Laseke

------------------------------

Date: Wed, 12 Jun 1996 12:31:46 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: NW3.12, VLM's and Word for Windows

>Someone probably raised the questions, others probably answered it,
>and I did not think that it concerned me, so I did not pay any
>attention to those messages.  But I have just discovered that Word
>for Windows does not print properly to networked printers (this might
>also apply to Excel and other Microsoft products).  This is true
>whether we use a dotmatrix printer or a laser printer, printers with
>their own network card or using FPServer.  If I reconfigrue the
>station to use packet drivers instead of VLM's, the problem
>disappears.  DOS programs have no problems printing.  Has anyone
>experienced the same problems?  Any solution.

	It's not that. I run all the MS products and many other products
over VLMs, with DOS 6.22, Win 3.1, Win95, and they print fine. I avoid
stupid print spooler software in MS products and print to either LPTn
via DOS level Capture commands or directly to NW queues for WordPerfect.
Also I have never had any reason to get involved with printer filters,
the *.PDF things populating sys:public, in years and years of running
apps from NetWare servers.
	I think you can profitably investigate a weak network. Printing
often is an intensive activity (favorite description while waiting is
one byte per packet, but that's only a small exageration). If your lan
adapters and drivers are weak then things break. VLMs introduce packet
burst transmissions which are very stressful on the net. So look at
your adapters and drivers very carefully before deciding the problem
is elsewhere.
	Joe D.

------------------------------

Date: Wed, 19 Jun 1996 16:39:29 -0400
From: "Bumpurs,Clinton,S" <BUMPURCS@CGLPO1.USACHEM.MSNET.BP.COM>
Subject: Re: How much free memory is required to

>Is it possible to change the queue assigned to a redirected LPT port
>without executing the full capture string again?

Use NWCALLS.DLL to capture and reset your queues instead
of running a DOS prompt.
start with this one:
Declare Function NWStartQueueCapture Lib "NWCALLS.DLL" (ByVal ConnHndl%,
ByVal LptDevice%, ByVal QueueID&, ByVal QueueName$) As Integer

Shane

------------------------------

Date: Wed, 26 Jun 1996 09:22:00 -0700
From: "Clarkson, Mark" <mclarkso@SSBPOST.ENV.GOV.BC.CA>
Subject: FW: Mac Printing on Novell 3.12

>When trying to print I get a "Unknown Printer" error.
>Here's how it's set up:
>[...]
>The atps.cfg file looks like this:
>"Laserjet 4 Plus1:phase2 zone1" -o "HFS_SALES"
>
>The network printer I'm trying to access is an HP LJ4+M with a jet
>direct card in it.  The queue was set up in jetadmin with the name
>"HFS_SALES"

Try adding the following to your line in the ATPS.CFG file:

     -t LaserWriter -f HPLASER

so that the line looks like this:

"Laserjet 4 Plus1:phase2 zone1" -o "HFS_SALES" -t LaserWriter -f HPLASER

Below is what the switches do.  I included a few more that I found useful.

# -o  Name of the printer advertised on the AppleTalk Network
# -t  Type of Printer
# -f HPLASER tells atps to use the font list in hplaser.fnt file
# -e  No Postscript error pages are printed
# -wb Advertises the queue but does not service the queue
# -wf To use the Queue on DOS workstations but not on Macs
# -y  No notify

Also note that you almost always need -t LaserWriter when you advertise
the printer over EtherTalk. Let me know if this fixes your problem or if
you have any other questions.

------------------------------

Date: Thu, 1 Aug 1996 08:33:58 +0200
From: Henno Keers <Mailbox@ICE.NL>
Subject: Re: NPrinter

>I have a question with regards to NPrinter which must be used when
>the Printer is in  remote location (not direct to the print server).
>I'm using Windows 95 and I'm getting an error that "Windows is running
>in enhanced mode so Nprinter must be loaded before loading Windows."

Win95 does not support Nprinter (or rprinter) very well, especially
when using 32 bit clients from M$ or Novell.
I would recommed to do the following:
-   Check what king of NIC you have in the workstation. See
    if you have a NetWare 3.12/4.x compatible server .LAN driver
    NLM for it.
-   Get Novell Client32 for Windows95 with patch c3295d.exe
-   Get Novell Nprinter for Windows95
-   Install Client32 with the 32 bit ODI driver
-   Install Nprinter

------------------------------

Date: Wed, 7 Aug 1996 08:38:39 -0700
From: "Richard K. Acquistapace" <acquista@NETCOM.COM>
Subject: Re: what password?

>(3.11) Can someone tell me what password pserver.nlm is looking for,
>when told to service queues on another server.

When you define a load PSERVER.NLM in the AUTOEXEC.NCF it should look
something like this;

LOAD PSERVER <PSERVER_NAME>

The reason it is asking for a password is because you have not correctly
defined it in PCONSOLE.  Make sure that you have defined ALL portions of
your Print Server in PCONSOLE.  <PSERVER_NAME> being the name of your
Print Server.  Make sure that you create the Printer Queue(s) that will be
servicing that Print Server.  If all is completed correctly you won't have
your console asking for a password.

------------------------------

Date: Thu, 3 Oct 1996 09:20:18 -0800
From: Stephen Herzog <herzogs@SDESIGN.COM>
Subject: Re: how to charge for printing with NW4.1

in bit.listserv.novell, jmirza@uoguelph.ca (Jeff I Mirza) wrote:
>I'm running a small student lab with a NW4.1 server and DOS/Windows
>workstations. I'm still in the planning stages and just wondered if
>there's a way to charge students for printing on a per page basis.

The following list is of places that make printer vending card systems,
and printer accounting systems/software.  Secure Design has not had any
contact with these companies, we are just providing a list for your
reference.  We obtained these addresses from some of our clients who
have used their products.

	Controlled Access Ltd,           (hardware - vending card reader)
	5-6 Station Estate, Oxford Rd,
	Wokingham, Surrey RG11 2QY, United Kingdom
	Phone: (44)734-772255, Fax: (44)734-772296

	PCounter by AND technologies     (Software print server)
	P.O. Box 64811
	Los Angeles, CA 90064
	E-mail: andtech@netcom.com
	http://www.andtechnologies.com/andtech
	ftp://oak.oakland.edu/pub/simtel/msdos/novell/pcnt*...

	TRACsystems                      (hardware - vending card reader)
	5635 Yale Boulevard
	Dallas, TX 75206 USA
	Phone (214) 369-6576

	Harco Industries, Inc.           (hardware - vending card reader)
	2362 West Shangri-La Road,
	Phonenix Arizona 85029  USA
	Phone 1-800-528-0465

	Copi Card                        (hardware - vending card reader)
	12900 valley Branch Ln.
	Suite 400
	Dalas, TX 75234

	COIN-OP JR. Venda Card Reader    (hardware - vending card reader)
	XCP, Inc.
	40 Elm Street
	Dryden, NY 13053-8824
	Phone: 1-607-844-9824 / 1-800-647-7020
	Fax: 1-607-844-8031


To augment any of the above, Secure Design has a print queue manager
called QView Pro. QView can assist in showing what print jobs are being
sent to the individual printer.  This helps quite a bit in determining
who's vending card should be placed in the card reader when several users
are sharing a printer.

A demo copy is available from our world wide web site at

	http://www.peak.org/~sdesign

or by e-mail at autohelp@sdesign.com (send a message for instructions.)

------------------------------

Date: Tue, 8 Oct 1996 10:33:40 -0400
From: Dan Schwartz <dan@SNIP.NET>
Subject: PostScript printing/faxing

>>Just soliciting some opinions.  I want to set up a fax server for a small
>>Novell 3.12 network. The complication? All outbound faxes are created in
>>MS Word for Windows using PostScript fonts, and not every product has PS
>>support built-in. (I can live without inbound, if necessary, since we don't
>>have DID lines). There's where the winnowing of products comes in.
>>
>>-FACSys will handle PostScript - with a $2K co-processor board.
>>
[snip]
>>
>>Any recommendations for a dedicated fax server (NOT file server), that
>>supports PostScript without any additional hw/sw required?  Looking at
>>about a dozen users.
[snip]
>>Michael Leone
>
>We are using 2 different products for fax servers on several different
>networks, and don't have any problem with the creation of jobs in Word
>and then faxing them.  One product is Castelle's Faxpress -- a hardware
>solution that is very reliable and has no problems handling any fax sent
>to it, whether it is text, graphics, or a combination.  Another is
>LanSource's FaxPort software solution -- using a dedicated PC as the
>modem/fax server -- which also works very well, but does have a hiccup
>once in a while.
>
>At any rate, there should be a conversion table to convert unknown or
>unrecognized fonts to a "standard" font that the "printer", which is what
>the fax
>server is see as, can accept and print.
>
>If you are not sure whether a product will work in your environment,
>contact the company about getting an evaluation product for 30 days and
>then really stress test it.

	There seems to be a bit of confusion here about what PostScript
Type 1 typefaces & fonts and Adobe Type Manager really is, and what it
does; so I'll review its history & basics of it's implementation on both
the Macintosh and windows... Maybe this will make the solution to Michael
Leone's challenges a bit clearer. I'm going to start with the Macintosh;
and then pick up windows at the end because there ARE some key differences.
And, I'm going to bypass Apple's QuickDraw GX because it's not in wide use.

	This may at first seem a bit off-topic for this list; but a brief
history and comparison to how DOS & windows handles it's printing will
shed quite a bit of light on the care & feeding of NetWare print spoolers.

	First, we need to define the difference between a typeface and a
font: A typeface is a scaleable set of characters that prints with no loss
of quality at any size; while a font is a fixed size group of characters,
such as a bitmap 12 point Baskerville or a "font" (rack) of 12 point
Bookman hot metal type. [That's how I remember the difference between
typefaces & fonts!] This may seem to really be straying a bit, but it will
become clearer by the end of this article.

	PostScript Type 1 typefaces originated in the early 80's as a tool
used by dedicated digital typesetting machines (such as CompuGraphics). In
it's most basic form, a PostScript Type 1 typeface is a file with up to 255
"slots" corresponding to each ASCII character. Each slot, or character,
contains a series of Bezier curves that are filled according to two
well-defined rules: Odd-Even (number of times a path crosses itself or
another, as in a Star of David with filled-in triangles), and path
direction (clockwise & CCW, as found in the letter "O"). In addition,
Typefaces are fully scalable with no loss in quality, because they consist
of vector graphics -- A mathmatical description of the outline of each
element (character). Furthermore, PostScript Type 1 typefaces (and all
PostScript and EPS files) are platform-independent.

	In 1985, Apple released the LaserWriter laser printer, which could
not only print QuickDraw raster graphics (bitmaps) but also had a
PostScript Level 1 rasterizer to handle Type 1 typefaces downloaded to it.
It also had the Symbol, Times, Helvetica, and Courier typefaces embedded in
the ROM. [These printers cost over $4000; and Apple was paying Adobe $750
per printer royalty!] Simultaneously, Adobe released versions of Type 1
(and the now-obsolete Type 3) typefaces and corresponding bitmap (screen)
fonts and .AFM (Adobe Font Metrics) files for the Macintosh from their
extensive library.

	What would happen is that if a user would type, say, a phrase
"Hello World" in Times 12 point the Mac would look for an installed Times
24 point font, scale it to 12 point to display on the screen, and then
reference it in the given document. Now, if the user typed "Goodnight
Moon" in, say, 12 point Clarendon ultra bold the Mac would again look for
the 24 point version to scale, display, and reference in the document.

	Now, it's print time: First, the PostScript driver (LaserWriter
Chooser Extension) looks at the document and compares what typefaces it
finds to what the printer already has in ROM. It then polls the printer to
see what typefaces are loaded in RAM (and on the hard drive, if the printer
or imagesetter has one attached). The PostScript driver then creates a
PostScript file that contains everything that the rasterizing engine on the
printer needs to render the job: The text, any placed graphics, and very
importantly any Type 1 typefaces that are already not residing on the
printer. The printer CPU then takes this file (typically about 300 to 500
kilobytes for a typical single page document) and then chews it up and
spits it out as a finished page.

	Now at this point you are probably asking "Why is a PostScript
printer so much more expensive than a regular printer?" Let's pause a
moment and go back 10 years: A Mac Plus cost about $3000, yet with it's
68000 CPU was woefully underpowered. What Apple did was to have the
workstation "husband" it's resources by offloading the print rasterizing
to a second 68000 CPU in the LaserWriter itself. And this brings up two
additional salient points:

	1) PostScript printers, are, in general network printers: They do
not sit attached to a single computer; nor are they required to be attached
to a complicated print spooler (such as NetWare) as character-based (and
later windows raster-based) printers;

	2) PostScript is technically a programming language; hence the
PostScript RIP (Raster Image Processing) engine in the printer is able to
work more efficiently.

You'll notice that I'm stressing the independence of the printer from the
workstation: This is a key feature of PostScript printing.

	One of the issues that arises is that how do you display off-sized
characters, such as 17 point Helvetica, where there is no corresponding
bitmap (screen) font? Very poorly, in fact. This is because the printer
typefaces sit on the user's Mac essentially idle, unless downloaded to the
printer. So, as Macs became more powerful in 1989 Adobe created Adobe Type
Manager (ATM). What ATM does is find those instances like "17 point
Helvetica" where there is no bitmap and rasterize the outline to a 72 dpi
(screen resolution) 17 point font, so the System can throw it up on the
screen. (It also caches the font in RAM). In addition, for QuickDraw
(Macintosh raster) printing, such as for the 144 dpi ImageWriter dot-matrix
printer, ATM will also rasterize the characters to the 144 dpi resolution.
Basically, ATM is a "poor man's" PostScript rendering engine that resides
on the workstation... It only RIP's characters, and not PostScript graphics
(such as Illustrator or EPS files).

	One of the differences between the Macintosh and windows is that
on the Mac PostScript typefaces will *not* show up in the "Fonts" menu
unless at least one bitmap screen font is installed. In windows ATM manages
Type 1 type differently: It does not use bitmap (screen) fonts: Instead it
rasterizes and caches everything on the fly; and patches into the
application Font menus any typeface installed through the ATM control
panel.

	In personal correspondence, Michael Leone asked:

>   The biggest problem that I have with PS is that hardly anyone uses it;
>when I send docs to clients, they arrive "broken" - wrong pagination,
>unaligned tables, etc. Will Fontographer help in this situation?
>(I know that you can embed TT fonts in Word docs; if the PS fonts are
>converted to TT, and embedded in the docs, then whoever receives
>the doc should have no problem, correct?)

	This brings up the third part of a PostScript Type 1 typeface: The
metrics. The metrics include the character spacing, the kerning tables,
and the hinting. On the Macintosh, initially the metrics were stored in
the .AFM (Adobe Font Metrics) text file, with the contents added into the
PostScript file downloaded to the printer. Later on, the metrics were
integrated into the bitmap font. For Windows, the .PFB (Printer Font
Binary) file (typically 40-50 kilobytes) contains the outlines; while the
.PFM (Printer Font Metric) file (typically a few kilobytes) contains the
metric data.

	Now, let's take a quick glance at TrueType: This was created by
Apple to complement QuickDraw (and get around the expensive Adobe
licensing); and was subsequently licensed to Microsoft for integration
into Windows. It was initially released in System 6.0.8 as an Extension;
and seamlessly integrated into System 7. It differs (on the Mac) from PS1
because it has, in a single file, the outline info and the metrics. Also,
on the Mac it does not require a bitmap font for it to appear in an
application's Fonts menu like a PS1 typeface. (Although having
corresponding screen fonts will save on CPU time.)

	Now, what has been happening here is not so much a PostScript/
TrueType problem as a metrics problem: He is mainly using Avante Garde,
which is a ROM resident typeface in all Level 2 PostScript printers --
Part of the "Adobe 35."  Since he is NOT running ATM for Windows and
instead relying on the internal ATM emulator in Word for Windows, it
should still be picking up the metrics (for display purposes) from
somewhere; and the printer is using the default metrics stored with the
typeface. When he is giving the WFW documents to clients their machine is
 *substituting*  the metrics present on their machine -- Often causing
reflow. And, 9 times out of 10 the metrics differ between TrueType and
PostScript Type 1 versions of a given typeface. If the client's PC is
hooked to a Level 2 PostScript printer, then the text may reflow on the
screen but still print out correctly.

***********

	Now [as to] outbound faxing...

	Faxing is just a special version of raster imaging. If one is
using TrueType then the TT engine will simply fill in the outlines as
called for by the fax driver's resolution setting. If one is using PS1
type in the document, then ATM will fill in the outlines the same way as
TT. If there are placed EPS (Encapsulated PostScript) graphics in the
document the fax driver will (in most cases) output the 72 dpi bitmap
(low-res) header. [Some newer fax drivers now have PostScript emulators
that will properly handle placed EPS graphics, though.]

	In Michael's case, what he wants to do is transmit faxes of his
Word for Windows documents that contain Avant Garde PostScript text, in
a typeface that happens to be one of the "Adobe 35" that is resident on
his HP PostScript laser printer. (Probably a LaserJet 4M.)

	With the background above, he now has a few different directions
to go; as I quickly outlined yesterday. We'll look at each one in a little
more depth today, though.

	1) Michael can load ATM for Windows (v3.0.2 is the latest version,
fully compatible with win`95); and he can then load the Adobe Avant Garde
.PFB and .PFM files. This will give him an  *exact*  match between what he
sees on the screen and what he prints out to  *any*  Level 2 output
device... Without having to download any typefaces or metrics. In addition,
ATM will "take over" and allow him to fax any document containing PS1 type,
with the resulting document received at the other end an exact replica
(i.e. no reflow) of what he sees on the screen. All he needs in a network
fax software package is something that is compatible with windows; i.e. no
special PostScript handling is necessary because ATM handles everything
before it arrives at the fax driver.

	If the documents do not need to be edited by the client, then using
Adobe Acrobat is a fine auxiliary solution: It will allow them to view and
print out the document  *exactly*  as you created it -- Metrics and all --
and Acrobat will only embed the characters used, for file space savings.
In addition, the Acrobat reader is freeware (available at <www.adobe.com>);
and it will also properly handle placed graphics and print out vector
graphics at the printer resolution;

	2) Michael can purchase the Adobe version of the Avant Garde family
in TrueType; or alternately use Fontographer to read in the Type 1 .PFB
outline file, import the .PFM metrics file, and then generate the
corresponding TrueType typeface. He'll need to do this for each of the 4
versions of Avant Garde: Normal, Bold, Italic, and Bold Italic. He'll then
be able to load these TrueType faces onto each windows workstation; and
then when used in a document the printer will faithfully substitute the
PostScript versions resident in the ROM... Without having to download
anything. And, faxing will simply use the TrueType typeface (with it's
embedded metrics) installed in the "Fonts" control panel applet.


	The first method has merit because no editing of the "font
substitution" section of the WIN.INI file is necessary; and, if he loads
all 35 of the "Adobe 35" family through the ATM applet (and any other PS1
type he has) he can disable the TrueType engine -- Saving RAM and CPU
horsepower. And, Acrobat Distiller is  *really*  nice: I've even used it
to prepare files output to film on a 2540 dpi imagesetter!

	The second method has some merit, however, because  *if*  the
client needs to edit the document then metrics  *can*  become an issue.
If the typefaces used _and_embedded_  in the document are continued to be
used during the client revision, then WFW  *should*  reuse these metrics.
BUT, unlike the Macintosh (which was designed from the ground-up as a
graphics machine), when you mix MSWindows and graphics, EVERYTHING is a
crapshot.

------------------------------

Date: Thu, 17 Oct 1996 10:44:00 -0400
From: "QUIBELL: MARC" <txh8205@TEXCOM-HOOD.ARMY.MIL>
Subject: Re: Client32 printing

>Hi All, I have installed Novell Client 32 on a working MS Win95
>workstation.  The install went fine and everything worked except the
>printing....Win95 said the printer was off line, and the printer icon
>was greyed.  Joe D. suggested I NOT let Win95 control printing, soooo I
>put the capture commands in my login in script and Client 32 could not
>run the script.  The script that runs is the <DEFAULT> script....if I
>select the system login script Client 32 does not login correctly.  I
>tried to put the capture commands in the Winstart.bat file with no luck
>there either.  Is there a soultion to this?....how do I NOT let Win95
>control the printing?  All thoughts and suggestions will be appreciated,
>thanks....JWS.

Capturing in Win95, Client 32 in Netware 4.x is a little tricky indeed. You
did not specify your Netware version, so I guess it is 4.x, since Win95 is
having a hard time finding the print queue (greyed out). In order to capture
a printer in Netware 4.x and Client32/Win95 not in your bindery context, you
must find the print queue using the Network Neighborhood. Double click on
down the tree to your context where the print queue objects reside and right
click on the print queue object and select "Capture printer port". Hope this
helps...

------------------------------

Date:	Sat, 19 Oct 1996 17:02:40 +0200
From:	Bennie Venter <bjv@Gil-galad.paradigm-sa.com>
Subject: Novell Print Queues to Linux/Unix Print Queues

There are a Linux-based printserver that will service NetWare based
print queue's and it is part of ncpfs, the Linux NCP file-system &
utilities.

It will take a NetWare print job & spool it to a printer attached local
on the linux machine using the standard lpd printing system.

These are located at ftp://ftp.gwdg.de/pub/linux/misc/ncpfs

Amongs others there are:

ipxripd - IPX RIP Deamon
mars_nwe - Netware file server emulator for Linux (bindery, etc)
linware - Another NetWare emulator for Linux
docs    - some miscellaneous documentation

------------------------------

Date: Tue, 29 Oct 96 21:11:01 -0800
From: Randy Grein <rgrein@halcyon.com>
To: "NetWare 4 list" <netw4-l@bgu.edu>
Subject: Re: upgrade to Netware 4.10 and use of NPRINTER

>The headache we are facing now is that the printer servers running
>NPRINTER seem to disconnect themselves from the network, randomly.
>However, there are no errors on screen to indicate that.  The users only
>came to know that there is something wrong with the print server when their
>print jobs get lined up on the PCONSOLE screen and not printing.  They are
>now used to rebooting the print server to "release" the print jobs.

Issue: nprinter creates remote printers, not print servers. The auto
reconnect feature is there, but that deals with the network shell, not
independent spx connections. (Yes, remote printers use spx to gain
reliable, sequenced exchanges.) Try setting the SPX retrys to about 60
for starters. I've included a sample net.cfg that should help. There's
more here than you need, but it should answer other questions you might
have later.

BTW, you have a possibility of never getting high reliability out of
these. With the combination of preemtive and nonpreemptive multi tasking
going on under windows adding yet another service to the client seems to
be pretty marginal.

Link Support
	Buffers	8 1500
	MemPool	4096
	Max Stacks 8
Max Boards 4
	Max stacks 4
	Buffers 4 1514
	MemPool 4096
#
#	NET.CFG File for ne2000
#
Link Driver EXP16ODI
	PORT 300
	Frame Ethernet_802.3
	Frame Ethernet_II
	Frame Ethernet_SNAP
	Protocol IPX ETHERNET_802.3

Protocol TCPIP
	PATH SCRIPT	C:\NET\SCRIPT
	PATH PROFILE	C:\NET\PROFILE
	PATH LWP_CFG	C:\NET\HSTACC
	PATH TCP_CFG	C:\NET\TCP
	ip_address	1.0.0.31
	tcp_sockets     4
	udp_sockets     4
	raw_sockets     1
	nb_sessions     4
	nb_commands     4
	nb_adapter      0
	nb_domain

Netware DOS Requester
	FIRST NETWORK DRIVE = F
	NETWARE PROTOCOL = NDS,BIND
	SHOW DOTS=ON
	IPX RETRY=60
	SPX ABORT TIMEOUT=1000
	SPX VERIFY TIMEOUT=200


;	VLM = NMR.VLM
	VLM = AUTO.VLM
;	VLM = RSA.VLM


	FORCE FIRST NETWORK DRIVE=ON
	NETWARE PROTOCOL = NDS,BIND
	CACHE WRITES=ON
	TRUE COMMIT=OFF
	LARGE INTERNET PACKETS=ON
	PB BUFFERS=5
	LOAD LOW CONN=Off
	LOAD LOW IPXNCP=Off
	LOAD LOW REDIR=Off
	SIGNATURE LEVEL=1
	CACHE BUFFERS=6
	PBURST READ WINDOW SIZE=64
	PBURST WRITE WINDOW SIZE=32
	MINIMUM TIME TO NET=5000
	CONNECTIONS=3
	CACHE WRITES=ON
	NETWORK PRINTERS=3
	AUTO RECONNECT=ON
	AUTO RETRY=100
	BIND RECONNECT=ON
	AVERAGE NAME LENGTH=8
	MAX TASKS=31
	MESSAGE LEVEL=2
	SET STATION TIME=ON
	HANDLE NETWORK ERRORS=ON
	SEARCH MODE=1
	PRINT BUFFER SIZE=64
	PRINT HEADER=64
	PRINT TAIL=16

	LOCAL PRINTERS=1

	; READ ONLY COMPATIBILITY=OFF
	MESSAGE TIMEOUT=540

	DOS NAME=MSDOS
	LONG MACHINE NAME=IBM_PC
	SHORT MACHINE NAME=IBM
	CHECKSUM=OFF

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

DESKTOP SNMP
	sysName = ""
	sysLocation = "
	sysContact = "Randy"
	snmpEnableAuthenTraps = ON
	Enable Monitor Community = SPECIFIED
	monitor community =  "public"
	Enable Control Community = SPECIFIED
	control community = "public"
	Enable Trap Community =  SPECIFIED
	trap community =  "public"
	asynchronous timeout =  20

TRANSPORT PROVIDER IPX

------------------------------

Date: 06 Nov 96 15:42:34 PST
From: MCSWEEJ%62SVS.MCCHORD@mhs-gw.mcchord.af.mil (McSweeney, GS-11 Jay A)
To: netw4-l
Subject: Re: cannot start nprinter.exe without logging in

You can copy the following files to the c: drive or sys:login directory
and then set up nprinter.exe to execute after '@call startnet.bat'in
autoexec.bat:

	nprinter.exe
	nprinter.hep
	nprinter.msg
	nwdsbrws.msg

This will allow nprinter.exe to properly execute without anyone
being logged in.

---------

Date: Wed, 6 Nov 96 20:51:55 -0800
From: Randy Grein <rgrein@halcyon.com>
To: "NetWare 4 list" <netw4-l@bgu.edu>
Subject: Re: cannot start nprinter.exe without logging in

>If I follow the procedure  for setting up (nprinter /ver and copying the
>files, wich files exactly? there are more files with the same name on the
>fileserver) and then start NPRINTER
>without logging in I get the following message.
>
>Error Report : TEXTUTIL-NPRINTER-4.10-384
>
>You are not logged in to server MEMO. You must be logged in to use
>this utility.  The program cannot continue.

You need the NLS\english\nprinter.* files copied to your local machine
with the directory structure; you may need some of the unicode files in
the nls directory as well.

------------------------------

Date: Fri, 8 Nov 1996 13:58:34 -0600
From: Steve McHargue <SMCHARGUE@JW.COM>
Subject: Re: Capture and Win95 [added: Mapping]

>I am currently setting up a number of computer labs on a college
>campus with Win95. For the most part the UNC printing works well but
>in a few cases students need to print from DOS, thus my problem. If i
>set the capture in PRINTER|PROPERTIES|DETAILS it works fine until
>someone else logs into the network from that machine. It then asks if
>they want to connect as the original user who set the capture (they
>of course do not know my password, I HOPE) , when they say no it
>effectively flushes my capture down the toilet.
>
>Is there a way to set a DEFAULT QUEUE for specific machines and
>have them capture regardless who logs in ? ( other than adding a BIG
>batch file containing physical addresses  to the server to differetiate
>which lab the machine is in and which queue to use)

Here's what we do, I'd love a more elegant way: Win95, Client32 and NW
3.12

On each machine we set DPQ=xxx
DPQ stands for the Default Print Queue, xxx is the desired print queue
for this machine.

In the login script we just run capture Q=%<DQP>

That seems to workaround the problem.

Of course the problem is Win95 philosophy that a print capture is a user
resource and not a machine resource. Where I would consider drive
mappings something that needed to follow a user around regardless of
where they login a printer is something that is logically if not physically
tied to a machine location, don't you think?

------------------------------

Date: Fri, 29 Nov 1996 20:31:27 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: lpt stuff

>This has probably been answered a million times before, but is there any
>way to extend the lpt 1-3 limit on printing .... ie lpt 4 lpt 5 ect.  We
>need to extend these to attach to network printers.
-----------
	Fortunately VLMs and Client32 support more than four printers,
by intercepting the device names under DOS/Windows via Capture and
referencing them to NetWare queues. NPRINT does a nice job of bypassing
even this part by going from file to queue. Windows prefers to use NW
queue names too, though at times we wish it didn't (control of printing
characteristics).
	Keep in mind that many applications are network aware these days
and can reference NW queues by name irregardless of Capture.
	Joe D.

---------

Date: Sat, 30 Nov 1996 17:58:57 +0000
From: Mark Roscrow <mark_roscrow@RKCARBON.COM>
Subject: Re: lpt stuff

If your system is windows 3.1, then if you add the following lines to
your  WIN.INI [Ports] section, windows will use upto 9 printers .

LPT4:=
LPT5:=
LPT6:=
LPT7:=
LPT8:=
LPT9:=

Now edit your NET.CFG file, inthe Netware DOS Requester section, add

Network printers = 9

Now reboot your PC. If you system is not a windows 3.1, then maybe
this will point you in the correct direction.

------------------------------

Date: Tue, 10 Dec 1996 16:53:16 EDT
From: Scott Smith <scott@FRED.HRIS.MSU.EDU>
Subject: Re: HP JetAdmin 2.3x for Windows 95

>There is a new family of JetAdmin utilities, that we all have known
>and loved as a remote LaserJet configuration and peer-to-peer print
>management utility, which uses a rather noisy mechanism by which it
>tries to identify IP addressable Hewlett Packard printers on the network.
>
>Traces of this behavior reveal JetAdmin 'joyfully' ARPing sequentially
>down the subnet, continuously.  The software contains a disfunctional
>switch designed to disable this aggressive behavior.  In short, the switch
>doesn't reliably squelch it and has begun to become an issue on large
>bridged networks.
>
>The broadcasts are sent out in little bursts, with a fairly
>predictable delta time between bursts -- 6.5 seconds.  The bursts are
>at a rather potent rate though -- upwards of 600 pkts/sec.  However, the
>bursts are very short lived, usually only around 6 packets per burst, but
>I have seen as many as 40 at one time -- lasting a maximum of .062 seconds.
>
>When/if the ARP gets a response, the PC issues a SNMP Get for a
>private.enterprises.HP.2.4.3.10.6.0 variable.
>
>1) Have other network administrators/engineers observed this behavior?
>
>2) Any ideas on how to overcome this problem (independent of HP)?...given
>this software is freely downloadable from HP and users have no idea the
>trouble they cause.

That's affirm.  Our campus network manager kept calling me up and
telling me to shut down whatever it was that was flooding our campus
LAN.  I would be interested in hearing about any
solutions/updates/etc. that bear on this issue.  I can probably get
our net. mgr. involved too, if for nothing else than more
information.

------------------------------

Date: Fri, 13 Dec 1996 11:41:29 +1000
From: Michael Strasser <M.Strasser@MAILBOX.UQ.OZ.AU>
Subject: Client32 Win95 + NPTwin95

> Is there any way to close the box automatically when nptwin95.exe
> loads for the remote printer?

Start it with the /EXIT option in the program shortcut.

To have NPrinter start up on a PC without a user logging in, add to the
PC's registry under

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices

the information

   "NPrinter"="C:\Novell\NPrinter\NPTWin95.exe /EXIT"

assuming that you have nptwin95.exe in c:\Novell\NPrinter.

This is all documented in the NPrinter help files.

------------------------------

Date: Thu, 26 Dec 1996 12:21:25 -0500
From: "David E. Berry" <dberry@LAMINATIONS.COM>
Subject: Re: DOS Apps Printing Under Win 95 with Client 32

>There is SOMETHING wrong with Client 32 and Dos Apps Printing.
>
>We have 4 Dos based CD-ROM applications.  All four DOS applications can
>print with a capture from the login script.
>
>When we run the same apps from Windows 95, w/client 32 only 2 of the
>applications print.
>
>I don't know what's different from the VLMs running capture and the Win 95
>Client 32 capture, but something is, and it just isn't reliable.

Printing under Win 95 is MUCH different than printing in a native
DOS environment.  In Win 95, you print to an object as opposed
to a port.  Try "playing around" with capturing a port and installing
printer's into the local OS from the network neighborhood.  If the
DOS app is trying to print to that port and you aren't capturing the
actual port, then it will not work.  Make sure the port setting for
the printer object within 95 has the correct NDS path also.

------------------------------

Date: Sun, 19 Jan 1997 22:01:33 -0600
From: "Mike Avery" <mavery@mail.otherwhen.com>
To: netw4-l@bgu.edu
Subject: Re: Printing problems still

>1.  I am still using windows 3.1
>2.  I have just recently installed a Netware 4.11 server
>3.  I was running on Netware Lite Peer to Peer network.
>4.  I am trying to print to a HP4 laser printer .
>
>In Netware Lite I have no problems with the TT Fonts, but when I try
>to print to the same printer through my NW411 server I am geting
>extra characters, and uneven tabs.
>
>My capture statement reads as follows:
>Capture l=3 p=.laser.godseys.commworld nt nb nff ti=10
>
>I have tried disabling the TT fonts in windows but that leaves me
>with only four fonts to work with. Trying several Different fonts
>have led me to only Times new roman and a  two others out of about
>50 different fonts.
>
>Is there a place where I can get a new PCL for the printer that
>NW411 accepts.
>
>I have resorted to going back to Netware Lite until this problem is
>resolved and my boss is having great fun with my dillema.  He is
>calling the $3000.00 dollar server a very expensive paper weight.

He sounds like a real peach.  After you solve this, you might
consider circulating your resume.

Of course, it's ALWAYS the networks fault.  Every boss, and every
employee knows that..... but enough carping.

The big question that comes to my mind is, "What has changed?"  The
printing characteristics of the two systems are very similar.

Here's my suggestions.

1.  When you're the only one in the office or on the system, put the
printer off line.   Capture the job again.  Look in the queue and see
how many print jobs are in the queue.  If there is more than one
print job, your autoendcap may be malfunctioning in one way or
another.  Perhaps 10 seconds is not enough for the program you are
using.  Perhaps you have autoendcap set and when your program calls a
sub-program and it ends, it ends the print job.

2.  Since true-type fonts are a windows construct, make sure your
windows environment is impeccable.  Check the Windows printer
settings.  Make sure that you are NOT using print manager, instead go
directly to the printer, or in this case the queue.  Remember, the
Windows printer settings take precedence over the capture statement
commands.

3.  Did someone set up a printer profile?  If so, check it out, it
may have some other disadvantagous setups in it.

4.  If you are using rprinter, check that you have all the
appropriate patches applied.  NPrinter has been a pain for some time.
Also, consider switching to other products, such as Infinite
Technologies IQServer (an evaluation copy is available from Infinite
Technologies, send an email message to library@infinite.ihub.com with
a subject of help, and another with a title of index.  You'll get
instructions on how to request files for evaluation), or to go to
stand alone print drivers such as those from Intel, HP, and Emulex.

------------------------------

Date: Sat, 1 Feb 1997 21:25:20 +3
From: "Fady Jabbour" <fady@ncc.moc.kw>
To: netw4-l@bgu.edu
Subject: Re: Remote Printer

>I have a problem with a HP1600C DeskJet printer that was installed
>on a workstation on the LPT1 port, to be used as a remote printer on
>a Netware 4.1 network.  Now, when NPRINTER is loaded on the client
>and as long as it's in DOS, the PSERVER screen shows it to be
>"waiting for a job".  However, the minute that Windows for
>Workgroups 3.11 is loaded on the client, the PSERVER screen shows
>the remote printer to be offline every 30 seconds.  By the way, the
>printer has no network interface card installed.
>
>Does anyone have a remedy for this problem?

For anyone who's interested, I finally solved the problem by taking
out the Windows for Wokgroups network support and leaving only the
Netware 4.1 support for Windows.  Furthermore, I found out that the
HP1600C DeskJet loads into Windows a program called Status Monitor
which cause the printer to go offline on the network.

------------------------------

Date: Tue, 4 Feb 1997 10:11:39 +0800
From: Brett Looney <BLooney@COMTECH.COM.AU>
Subject: Re: Automatic printer types with Windows clients

>WinNT servers apparently are able to transmit printer
>make/model information to Win95/WinNT clients as they
>try to configure a printer for the first time.  I'm
>wondering if such automation is also possible with NetWare
>print queues.

Yes, is you are running Win95 as the client. There are two possible
permutations. You will need Supervisory rights in either case for this to
work.

1) If you are running the MS Client for NetWare, browse through Network
Neighborhood till you find the queue you want, right click on it and choose
"Point and Print Setup". You can then choose what sort of printer that
queue is and what directory the drivers are in. Once you do this, you must
copy the correct drivers to the directory you specified on the server -
everyone should have RF to it. Finding out what the files are to copy is a
bit of a pain, but can be done.

2) If you are runinng NetWare Client32, browse as above then right click
ahd choose "Properties". There is a new page in there which is (surprise!)
"Point and Print Setup". The difference here is that it copies the driver
files automagically - providing you have the Win95 CD lying around
somewhere.

In both cases, if a user then browses the network, finds a printer and
double clicks on it the drivers will automatically install and bingo!

BTW, if you had to set up this on an NT server - it's actually much harder.
You not only need to figure out what files make up the driver (as per point
1), but you also need to fiddle with the registry some (urgh) and create
some directories... (Sorry - just showing a little bias here...)

------------------------------

Date: Sun, 23 Feb 1997 21:16:59 -0600
From: "Kevin McIntosh" <powertek@hia.net>
To: <netw4-l@ecnet.net>
Subject: Re: 230 users and 109 printers

>Darwin Collins <dcollins@fastlane.net> wrote:
>>I have 250 user licenses. I have two 4.1 servers(file server and printer
>>server). The number of users grew at 230 users and now I have 109
>>printers. It will go on. Can anybody tell me what the real limit is?
>
>Are the printers configured as 'print server' or 'remote printers'? 
>Basically, if you have a Castelle JetPress, HP JetDirect, Lexmark, etc.
>'print server' cards, and configure them as a 'print server' then they
>will take up a license attaching to their print queue.
>
>Alternatively, you can configure them as a 'remote printer', load
>pserver on the server, and then the printers will not take up a license.
>
>Using the Monitor screen, it will display how many 'licensed
>connections' are consumed on that server.   If you have a 250user
>license, then, it will not allow more than 250 licensed connections on
>that server.   Once you are at the 'magic number' (250 in this case),
>the server will not allow anymore licensed connections to the server. 
>It can still allow unlicensed connections.    Not-authenticated
>connections do not use up a license.
>
>For your user, basically, he will not be able to access any resources on
>that server, such a drive mapping or a print queue.    ... if he can't
>get a licensed connection to that server.

You may not like the performance hit with the mode set to
'remote printer'. It's a matter of balance or money vs. performance.

------------------------------

Date: Mon, 24 Feb 1997 15:45:49 -0600
From: Darwin Collins <dcollins@fastlane.net>
To: netw4-l@ecnet.net
Subject: Re: 230 users and 109 printers

>You may not like the performance hit with the mode set to
>'remote printer'. It's a matter of balance or money vs. performance.

How much of hit is there with Netware 4's PSERVER?   I remember hearing
the same thing with the older Netware 3 PSERVER, but was told that its
'not much' of a factor with 4x.  Also, reduces SAP traffic (Remote
printers don't SAP, whereas queue servers do every 30 seconds) so may
have a side-benefit. ?

One item, that made us use some 'remote printers' is that it made it
possible to keep some older Castelle JetPress cards working.  (they
don't like 4x's bindery emulation)

---------

Date: Tue, 25 Feb 1997 14:00:13 -0600
From: "Kevin McIntosh" <powertek@hia.net>
To: <netw4-l@ecnet.net>
Subject: Re: 230 users and 109 printers

With HP JetDirects you can set the SAP intervals on your remote print
servers. Using print server mode greatly reduces the load on your server
for print services.

------------------------------

Date: Mon, 3 Mar 1997 10:05:42 EST
From: Gilbert Armour <garmour@FRAMATECH.COM>
Subject: Re: Alloc Short-Term Memory

Win95 turns on SAP when Print and File Sharing for NetWare is enabled.
You can manually open its properties window and disable SAP
advertising.  I'd recommend this if you MUST use PFSNW on Win 95.

------------------------------

Date: Mon, 3 Mar 1997 21:22:51 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Intel Print Servers (Pro's & XL's)

>Howdy, I have a serious problem at my shop.
>
>We have 8 Neport Pro Print servers (Intel's) and all 8 decided to
>die one day and they wouldn't keep their connection to the file
>server(s), which are currently Netware 3.12.
>
>We also us 20+ Neport XL's (the step down model from the pro's)
>and they have never missed a beat.  We had our comm. guy put a
>sniffer on the Pro Print Server and he found a lot of
>'appletalk' traffic to and from the pro.  I am unable
>to disable the appletalk protocol (it appears to be on full
>time now matter what) and my Pro's will only stay attached
>to my file servers 5-10 min. max before completely dying,
>requiring a power reset on the servers themselves.
---------
	See if you have an attack by Apples greedy for printers. Once
started you may have to shutdown ever Apple network device to ensure
routers forget all past discressions. At my place we have Cisco routers
separating regions of the site and those routers determine which AT
zones will be propagated across the router. This has greatly improved
AT stability. Further, we try (insist, but there are limits) to keep
AT devices from seeding AT routes and let the big Ciscos do that job.
	Another suggestion: put the printers on the other side of NW
servers, and disable AT support on the servers. That's another router
approach.
	Your wire monitor is your friend; stare at it for awhile during
morning startups.
	Good luck,
	Joe D.

---------

Date: Tue, 4 Mar 1997 10:23:58 +0000
From: Phil Randal <philr@HWCCES.DEMON.CO.UK>
Subject: Re: Intel Print Servers (Pro's & XL's)

>Howdy, I have a serious problem at my shop.
<snip>

Intel have recently released an update to the Netport Pro software
(now at Version 4.21).

It can be found in
ftp://ftp.intel.com/pub/support/enduser_reseller/netport_print_servers
/nppro.exe

---------

Date: Tue, 4 Mar 1997 10:15:37 -0500
From: Dan Schwartz <dan@SNIP.NET>
Subject: Re: Intel Print Servers (Pro's & XL's)

	Joe's in the right ballpark, so here are a few pointers on
narrowing down your search further:

	A) Keep an eye out for PostScript printers: By default, they have
AppleTalk turned ON:

	    A1) They can sit right on the ethernet "wire," where they are
well-behaved;
	    A2) They can be attached to a LocalTalk segment, where funky
things MAY happen:

		A2a) The printer(s) are connected through a hardware
"bridge" (technically a non-seeding router because of the change in
physical wiring from ethernet to LocalTalk), such as an Asante or Dayna
MicroPrint -- These are well-behaved in mixed AppleTalk-IPX installations;
		A2b) The printer(s) are connected through a Mac running
software bridging or routing:

		  A2bi) The Mac is running Apple's LaserBridge 2.0.1
software (Control Panel), which allows a non-intrusive (i.e. non-seeding)
routing of AppleTalk packets between the LocalTalk segment and the ethernet
segment;

		  A2bii) The Mac is running Apple's LocalBridge software,
which is a more powerful version of LaserBridge -- LocalBridge allows the
connection of LocalTalk Macs (such as IIci's & Classics) as well as
printers. Again, this is a non-seeding router method, and is relatively
non-intrusive;

		  A2Biii) The Mac is running Apple Internet Router 3.0.1:
This is a VERY intrusive software package that I have seen abused many
times -- Typically someone bought it to connect a LocalTalk printer into
the ethernet (or Token Ring) LAN, when bridging software or hardware would
have done the trick much less intrusively. In general, seeding is where the
AIR software "blows up:" You MUST turn ON seeding in the LocalTalk zone...
And this leads to a new zone being broadcast all over the LAN. In addition,
I've also seen seeding turned ON for even the ethernet (or token ring)
connection -- And this REALLY screws things up.

	B) Detecting the problem:

	   B1) Use a packet sniffer, as Joe suggested;

	   B2) Hook a Mac up to the ethernet and open the Chooser (from the
Apple menu). Select "AppleTalk" or "LaserWriter 8" in the left-hand window,
and see if any (errant?) zones pop up. Try this over the weekend; and
repeat this Monday morning and throughout the day. [You need to close &
reopen the Chooser, then click on the AppleShare or LaserWriter 8 Icon to
reset the zone-detecting function.] If you see new zones pop up, then
you've found the trouble!

	C) Fixing the problem:

	   C1) If someone is indeed running Apple Internet Router, try to
switch them over to the freeware LaserBridge 2.0.1 software (if there is
only a laser printer) or to LocalBridge;

	   C2) Block AppleTalk at your router. But beware: This will REALLY
piss off Mac users who need to access devices in other zones. Finder File
Sharing is VERY popular among Mac users; and you'll block their
collaboration... And possibly even their printing.

	D) Where to get the proper software: Download LaserBridge for free
from <http://www.mirror.apple.com>, or <ftp://ftp.mirror.apple.com>.
Navigate to the Networking directory and download <Network Software
Installer NSI-ZM 1.5.1>. This provides an up-to-date AppleTalk stack for
the MacOS running Classic networking (i.e. not running Open Transport).
Download the floppy image and perform a Custom Install on the desired Mac.
It's also a good idea to update &/or "refresh" AppleTalk to version 58.1.5
and to refresh the ethernet drivers while you're at it.

	If the Mac is running Open Transport (mandatory if it is a PCI Mac;
optional for other Macs), download <extension_updates.hqx> to update the
LaserBridge Control Panel to version 2.1, which is the Open
Transport-compatible version.

------------------------------

Date: Thu, 6 Mar 1997 20:00:48 -0800
From: STEVEN GUSTAVO ANDRES <steven@UCLA.EDU>
Subject: Re: charging for output?

>Does anyone know of utilities (preferably cheap) that would allow me to
>track the number of pages that a user prints?  I am using a 3.12 server
>and presently I use Rprinter on a dedicated machine, but I would be
>willing to set up a print server.

Search no further. We here at UCLA Residential Computing are using a
wonderful program from A.N.D. Technologies called PCOUNTER. It will do
all that you ask and MORE. I really, really like it. You can run it as an
NLM or an EXE. We run it on a spare 486SX/20 machine as an EXE. At the
end of each quarter, a custom written application reads in the
PCOUNTER.LOG file (which keeps a record on several aspects of each print
job) and we print out invoices that get tacked onto the Residence Hall
bills sent home to the parents.

Check them out at (I believe):

	http://www.andtechnologies.com

If you need more help, please don't hesitate to email me directly:

	mailto:steven@ucla.edu

------------------------------

Date: Mon, 10 Mar 1997 10:06:45 CDT
From: "Dan Creagan" <dcreagan@scholars.bellevue.edu>
To: netw4-l@ecnet.net
Subject: Re: HP DJs print junk

>>Does any one know of a reason why an HP DJ 560C or a HP DJ 870Cse prints
>>junk when attached to a NW 4.10 or 4.11 server.  I've tried both on the
>>server's LPT1 using PSERVER.  The clients are using the latest Novell
>>Client32 on Windows 95 rev.b (OSR2).

This happens a lot with later HPs.  We had a thread similar to this
last year and I believe the consensus was to use HP500 or 550 drivers on
your client.  You lose some features but it still gets you going.
The bidirectional printers do not work well on a network (it even
says that in the printer instructions somewhere).

---------

Date: Tue, 11 Mar 1997 07:49:34 -0500 (EST)
From: RBall84213@aol.com
To: netw4-l@ecnet.net
Subject: Re: HP DJs print junk

>>Does any one know of a reason why an HP DJ 560C or a HP DJ 870Cse prints
>>junk when attached to a NW 4.10 or 4.11 server.  I've tried both on the
>>server's LPT1 using PSERVER.  The clients are using the latest Novell
>>Client32 on Windows 95 rev.b (OSR2).
>
>Check around for TIDs and such, mainly at novell, but check HP as well.
>Seems like I've seen a lot of comments that their color printers just
>simply don't like being networked, period. Believe it has something to
>do with much more use of bidirectional information, talking to the PC.

I can't speak for HP, but the only way to network Canon's "bidirectional"
inkjet printers is to use the unidirectional drivers for a previous model
printer. E.g., a BJC-610 (bidirectional) printer will operate on a network
when driven with the BJC-600 (unidirectional) Windows drivers.  Canon
didn't know this -- I got it from this group.

------------------------------

Date: Tue, 11 Mar 1997 22:25:29 +0000
From: John Wells <jwells@PACIFICCOAST.NET>
Subject: Re: How to turn off print banner in Win95.

>go to printers
>printer properties
>details
>capture printer port
>the settings should be in there
>
>If using Client32
>go to the point where you capture the port and go to lpt settings

I agree this *should* work, but with all the Win95 PCs I've been using
(using either the default MS NetWare client or Client32) the capture
settings under a printer's Properties don't actually affect captures made
using the Capture Port button (at least they don't affect the banner and
form feed settings which I'm using concerned with).

The only way I've been able to control the parameters for persistent
captures (via Capture Port) is to use Client32, and go to Control
Panel/Network/Client32/Properties and select the Default Capture tab.
Changes made there do affect subsequent port captures.

------------------------------

Date: Thu, 13 Mar 1997 15:24:17 CDT
From: "Dan Creagan" <dcreagan@scholars.bellevue.edu>
To: netw4-l@ecnet.net
Subject: Re: Capture

>Under Novell 4.1 the user is able to print out via Windows using print
>queues but not from DOS.  If you issue a DOS capture command it tells
>you that you do not have access to the print queues. If you then go into
>the PCONSOLE the user does not display any queues?

My experience with this is that if Win95 has already captured a port,
then you can't capture it from DOS.  However, if it hasn't captured
it, you can issue the capture command and make it all work like you
would think. I've also tried capturing to LPT2 or LPT3 when 95 has
its strangle hold on LPT1 .. that has had mixed success.

------------------------------

Date: Wed, 19 Mar 1997 15:07:52 -0500
From: Debbie Becker <dbecker@CLARK.NET>
Subject: Re: Printing Probs? Client32/W95it2

>Has anyone else had printing problems once they installed the new client
>with/without the w95it2 patch?  We're running multiple brands of computers
>on Win95 all priting to HP LaserJet 4Si and 5Si printers.  Running
>IntraNetWare with the printers set up as Remote Printers.
>
>When my labs went to the latest Client32 client to fix some other
>problems, the win95 machines mysteriously started dropping prints.
>Actually I believe the machines are somehow losing their connections to
>the printer, since they set themsevles to print off-line.  I haven't had
>this happen to me personally, but I've had reports of it from other people
>I work with. This seems to happen with or without the w95it2 patch.
>(Anyone else notice that you can't get to the w95it2.exe patch from the
>support.novell.com site anymore?).

I haven't worked much in the Win95 environment (so take this with a grain
of salt <g>), but had similar problems on my laptop when I had used a
network printer by simply defining a network printer by queue. I was having
the same sort of problem that you are (even when printer was setup, I'd log
in through Win95 and try to print and it would say the printer was
"offline") -- if I'd reboot Win95, that would sometimes fix the problem for
the time being, but this didn't seem to be a very practical thing to have
to do on an on-going basis. I was also experiencing error messages telling
me that the file hadn't printed correctly even when it had (and then the
printer would go offline again!)

Based on several things I'd read on the list, I made the following changes:

1)  I went into the printer properties and told it to capture a printer
port (LPT1 to the queue). Told it to reconnect upon login.

2)  I also changed the spool data format (under spool settings) from RAW to
EMF. I'm not sure if this had a positive effect or not, but everything
seems to print consistently now and even if the printer truly is offline
initially, I'm able to reach it when it goes back online.

These are probably work-arounds at best (reflecting a less-than-perfect
understanding of how Win95 deals with printers <g>), and kind of
inconvenient to have to implement in a large-scale environment (love that
going around workstation to workstation, don't you), but might help you out
if you don't get a more practical response...

------------------------------

Date: Fri, 21 Mar 1997 09:22:22 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: SAP & RIP On?

>I recently upgraded our system (1 server abt 25 ws) to Intranetware.
>This resulted in nonfunct printers; we use 3 x NetPort 200 from DPI.
>The print servers could not find a server to attach to, although one
>HP Jetdirect and an old Lantronix was in fact functioning.
>
>Found no solution, until I called DPI and got help from their staff.
>They told me to open up INETCFG and to turn SAP & RIP = ON  for the
>IPX bound to the nic (3C579) instead of the default AUTO.
>
>My question is (as I recall some disussion here about it): Isn't the
>SAP being on causing unnecessary traffic on the pipe? Is there
>anything to do about it, except throwing out the DPI stuff? Seems
>that there is no upgrade to the DPI firmware available.
-----------
	Observations here on Jetdirect boards operating as remote printers
(not as NDS queue servers which is plain terrible for reliability):
	SAP on, RIP off. SAP is needed for the printer to find the server.
RIP has nothing whatsoever to do with printers, though the authors of
printer smart boxes don't seem to understand this yet.
	Turn off all unnecessary protocol support in the printer boxes.
	Joe D.

------------------------------

Date: Wed, 9 Apr 1997 17:40:14 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: HP JetDirect EX Plus3 cards

	On the subject of printing, here is a PR blurb from Novell that
should be of general interest.
	Joe D.

>>>>>
FOR IMMEDIATE RELEASE   ---   April 9, 1997

Novell and Industry Partners Meet To Develop Open Standard for Internet
Printing

Networking Leader Helps Advance Internet Standards at IETF-Chartered
Meetings

PROVO, Utah * April 9, 1997 * Novell, Inc. continues to play a major role
in advancing open Internet standards by collaborating with industry leaders
to develop the Internet Print Protocol (IPP), a fully defined industry
standard for printing across intranets and the Internet. Novell helped
drive the creation of a formal working group within the Internet
Engineering Task Force (IETF) that is meeting for the first time this week
to discuss the new printing standard. Developed initially by Novell, IBM,
Sun Microsystems, and Xerox, the IPP will make printing in heterogeneous
network environments much easier and standardize remote printing.

*The IPP is a significant piece of Novell's overall strategy to help
customers make the transition to open Internet standards,* said Glenn
Ricart, chief technology officer of Novell. *By working together with
industry leaders including IBM, Sun, and Xerox, we are bringing structure
to the Internet to make it a serious business tool.*

Through this new working group, Novell and leading printer and software
vendors will establish a set of industry-standard protocols for submission
and control of print jobs over the Internet and across enterprise
intranets. Companies participating in these efforts include Adobe, Canon,
Dataproducts, Dazel, Digital, Hewlett-Packard, IBM, Intel, Kyocera,
Lexmark, Microsoft, Netscape, QMS, Ricoh, Sharp, Sun, Tektronix and Xerox.
The working group will submit the IPP to the IETF later this year for
acceptance as an approved IETF standard. Novell will support these
protocols in future versions of its networking products.

*A universal Internet printing standard would reduce our overall cost for
network printing,* said Mike Hicks, network systems engineer for the City
of Tucson, Ariz. *We currently spend a significant amount of time
configuring workstations to allow users to print to remote locations.
In addition, our employees must print, then fax documents to the desired
destination. An open standard would alleviate much of this work and should
lower the overall cost of printers.*

Novell's Leadership

Novell set the standard for high-quality printing with its market-leading
network operating system. Through Novell Directory Services (NDS), network
administrators realize an unparalleled ability to manage printers and
printer set-up. By assisting in the creation of IPP, Novell demonstrates
its commitment to extending this leadership to the Internet.

The IPP standard will alleviate a significant amount of time administrators
now spend configuring user workstations to facilitate printing to remote
sites, lowering overall network administration costs. With IPP, end users
will be able to find any printer on the Internet, install it and print the
desired document very easily. Users will receive a status report verifying
successful completion of the job.

IPP can eliminate the need for faxing documents by providing a cost-
effective and reliable way to print documents such as invoices, schedules
and forms directly to remote printers. Instead of the costly and arduous
process of printing, then faxing documents to branch offices, hotels and
other remote locations, users will be able to print documents directly to
printers anywhere on the Internet reliably and quickly, using common
Internet connections.

The IPP Project

IPP is the result of several companies' efforts. Last fall, Novell and
Xerox submitted a draft of a jointly developed Internet printing protocol,
Lightweight Directory Printing Application (LDPA), to the IETF for review.
In a parallel effort, IBM started working on a proposal for Internet
printing using Web technology, known as HyperText Printing Protocol (HTPP).
During subsequent meetings among leading printer vendors and manufacturers,
it was decided to merge the Novell, IBM and Xerox efforts into the IPP
project. The first IPP discussion group was held at the December 1996 IETF
meeting, with participation from over 20 printer-related companies. This
week's first meeting of the working group is taking place in Memphis,
Tennessee.

About IETF

The IETF is a large international community of network designers,
operators, vendors, and researchers concerned with the evolution of the
Internet architecture and the smooth operation of the Internet. IETF is
open to any interested individual. The actual technical work of the IETF
is done in its working groups, which are organized by topic into several
areas (e.g. routing, network management, security, etc.). Further
information about the IETF can be accessed on the World Wide Web at
http://www.ietf.cnri.reston.va.us/home.html.

<snip>
<<<<<

------------------------------

Date: Tue, 15 Apr 1997 15:27:46 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Remote printing with NT 4.0 and Novell

>We are looking for information regarding what is the best way to configure
>a Windows NT 4.0 client station on a Novell 3.12 network to support remote
>printing (ala rprinter with Windows 3.1x).  Every thing that we have seen
>in searches have referred to Nprinter with Windows 95 and Novell's
>Client32.  Our preference would be to NOT have to login in order for the
>printer to function as a remote printer.
------------
	Printers managed by NetWare are network resouces, and hence one must
login to the network before access can be granted. They are not free-for-alls
thank goodness, nor peer-to-peer thingys.
	To print with no NetWare get an HP JetDirect board for your HP printers
and set it up to listen to NetBEUI frames (not routable) as well as other
frames.
	Joe D.

------------------------------

Date: Tue, 13 May 1997 22:18:27 -0400
From: Greg Small <gsmall@SYMPATICO.CA>
Subject: Re: HP Jet Direct EX

>The manual for the HP Jetdirect EX claims support for Netware 4.x via
>bindery emulation, yuk! Are there other external printservers that
>directly support NDS? Does anybody have experience with Intel
>Netport 2, does it support NDS directly?

Spar Aerospace is using about 75 Lantronix' EPS-1 multi-protocol print
servers.  They recently started supporting NDS and we are slowly flashing
their BIOS' to get the NDS support.

The box supports Netware, LAT and IP as well as a host of other stuff we
don't use.

I recently saw they have come out with a less expensive version that has
only a single parallel port versus the parallel and serial we have.
(However we have used the serial port directly connected to a VAX VT-320
terminal to do diagnostics on particularly troublesome problems.)

We have had a few failures and have had warranty loaners shipped before
the dead ones are returned.  All in all, we have been extremely pleased
with the product and the support from Lantronix.

---------

Date: Wed, 14 May 1997 07:50:12 -0400
From: Dennis Large <wdlarg01@HOMER.LOUISVILLE.EDU>
Subject: Re: HP Jet Direct EX

>The manual for the HP Jetdirect EX claims support for Netware 4.x via
>bindery emulation, yuk! Are there other external printservers that
>directly support NDS? Does anybody have experience with Intel
>Netport 2, does it support NDS directly?

Is that the latest model [Jetdirect EX Plus]? The internal ones at least
support NDS directly. Lantronix MPS and EPS models also support NDS quite
well.

---------

Date: Wed, 14 May 1997 13:37:08 -0400
From: "Mitchell, Luke" <mitchell.raleigh@SQUARED.COM>
Subject: Re: HP Jet Direct EX

HP's JetDirect EX print servers will support NDS if you purchase the $90
flash SIMM for them.  All their new internal cards are NDS ready, and the
3 port external is NDS ready out of the box.  Internal cards for LJ 2-3
are bindery only.  Some of the older MIO cards (LJ 4 and newer) will need
a $90 flash SIMM (different part # from the EX) in order to be NDS
capable.

The flash capability you get with the SIMM and the newer internal cards
means you can update firmware as HP adds features and fixes bugs, if any.
Besides NDS, the newer firmware allows LP TCP/IP printing.

---------

Date: Wed, 14 May 1997 16:22:04 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: HP JetDirect EX

>The manual for the HP Jetdirect EX claims support for Netware 4.x via
>bindery emulation, yuk! Are there other external printservers that
>directly support NDS? Does anybody have experience with Intel Netport
>2, does it support NDS directly?
---------
	Experiments here indicated a couple of things. One was "NDS" mode
operated the printers as NDS "queue servers," not as NW "remote printers."
That's more efficient in terms of background network traffic, but it also
is highly vulnerable to comms outages (connections go away and stay away,
HP type 40 errors on the printer).
	I decided to use the NW "remote printer" mode, bindery and all, to
have the printers poll the server and thus survive server ups and downs etc.
Setup is more awkward, nprinter.nlm is loaded, probe packets are sent every
couple of seconds (configurable) but robustness is greatly enhanced.
	Before someone asks, "remote printer" mode does not mean plugging
the printer into a client. The printer's JetDirect board attaches to the
network and to the server it looks like a remote NW printer. The printer
software runs on the printer rather than in a client PC.
	Another advantage of "remote printer" mode is one retains control
of the printer via pconsole, to rewind/stop/start/etc. Queue server mode
requires using the HP JetDirect software to accomplish similar goals;
pconsole cannot help with queue servers because pconsole deals with the
nprinter queue server (pulls from queues, pushes to printers).
	Joe D.

---------

Date: Sun, 18 May 1997 19:38:05 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: JetDirect card problems, cont'd

	After that long thread on troubles deailing with HP JetDirect
boards across the net I think I may have stumbled on a possible cure
for some of the trouble.
	Here I had two JetDirect boards which "faded" in and out, yielding
MIO 40 errors on the printers about one print job in three. A third board
was stable. These were connected as INW 4.11 "remote printers."
	The cure seems to be nail down IP connectivity. I changed things
here and left IP protocol active, but there was no assigned IP number and
the DHCP server did not have an entry for the boards. So I created proper
entries (were present, got lost in the shuffle a couple weeks ago just when
this MIO 40 stuff started). I also stretched out the SPX parameters on the
server side. The third, stable, board did have a DHCP entry.
	The printers are stable so far today.
	Joe D.

------------------------------

