AFPS UNIX shared printer problem

From: Steve M. Fabac, Jr. (smfabac_at_att.net)
Date: 02/12/04 

Date: Thu, 12 Feb 2004 18:38:19 GMT

I encountered a client with AFSP 4.0.2 on SCO 5.0.6 and attempted to setup Windows to UNIX
printing but had to work around the initial errors: The HP LaserJet 4+ is on a parallel port
and used the interface HPLaserJet. It prints from UNIX as lp -dprinter1 without problems.

When I checked "Windows shared printer" in mkdev lp, I gave it a shared name of HP4.

I setup a Windows 98 system network printer and choose the \\servername\hp4 printer.

Windows "print test page" resulted in one page with "line too long" and 9+ pages of
garbage.

I setup a new printer named bob and chose "passthrough" interface and /dev/null for the
device. I edited /usr/spool/lp/admins/lp/interfaces/bob and changed "raw=no" at the beginning
of the script to "raw=yes" and piped the output to "lp -oraw -dprinter1." printing from
Windows 98 to shbob (windows share name for UNIX printer bob) works.

I searched SCO's TA for product AFPS "line too long" (exact match) and got 9 articles, none of
which addressed the problem.

My kludge with shbob (Windows sharename for UNIX bob) of defaulting to raw=yes and
piping the output to printer1 with -oraw should not be necessary.

I am more familiar with VisionFS where using the profile manager, master printer share,
you specify print jobs for the UNIX printer with the -oraw directive. Nowhere in the
AFPS manual can I find a similar directive. Since the product is Advanced File and Print
Services, you would think that printer setup would be easy.

Does anyone have specific information on how to setup/troubleshoot AFPS when sharing the
UNIX system printers to the windows network? 

--
                                      Steve Fabac
                                       S.M. Fabac & Associates
                                        816/765-1670

Relevant Pages

  • Re: What is the more popular UNIX flavor?
    ... about my experience with Solaris and Cygwin. ... installing packages. ... needing eg tftp you only need to activate on a Unix system. ... probably need installing first on the equivalent Windows system. ...
    (comp.unix.questions)
  • Re: Five Architectural Flaws in Windows Solved In Mac OS X
    ... But it is still an improvement over Unix, wherein *any executable* can be highly privileged and interact with the user. ... The usual security precautions prevent unauthorized people from doing this, but that's true on Windows also. ... I just got thru upgrading the wifes Mac to Tiger and hpfs is the default. ... This is a more advanced design that Unixes have been trying to duplicate by adding thread support. ...
    (comp.sys.mac.advocacy)
  • Re: Linux no threat to Microsoft
    ... originally developed for Unix. ... Windows has't come on any of the machines I've ever purchased. ... Yet over those years Linux Market Share on the desktop has actually ... philosophy of Apple - later adopted by Microsoft. ...
    (comp.os.linux.setup)
  • Re: OS X "Security" myths
    ... >> lot of UNIX systems down to their knees. ... >>> their code, so they concentrate on developing exploits for Windows, ... > It does tell me that there is not much "boast factor" for malware ... Just like the Hackers convention in Las Vegas known as ...
    (comp.sys.mac.advocacy)
  • Re: Wozu Linux privat einsetzen?
    ... > Open Source bzw. GNU sind nicht an eine bestimmte Plattform gebunden. ... Windows ist nun mal nicht OpenSource. ... > Unix ist genauso gewachsen wie DOS, OS/2, Windows. ...
    (de.comp.os.unix.linux.misc)