Windows printing to HP 4014N from filePro
Reggie Freedman DC1
reggie1 at damncomputer.com
Tue Jul 20 14:14:38 PDT 2010
Since filePro has an HP PCL5 driver to use...
On my Windows Server(s), I always create a generic
printer, i.e., no codes, so what is sent from filePro
is passed through to the printer without added
'flavoring'. For different printers, I add another
generic printer, no codes, in Windows Server.
Reggie
----- Original Message -----
From: "Steve Wiltsie" <swiltsie at micro-mui.com>
To: "filePro Mailing List" <filepro-list at lists.celestial.com>
Sent: Monday, July 19, 2010 5:08 PM
Subject: SCO printing to HP 4014N from filePro
>I have something I don't think I've seen before going on with a new
> LaserJet 4014N at a customer site. They recently replaced an old HP
> 2015N that had failed with this new 4014N. We can print to it just fine
> from Windows with either the PCL5 or PCL6 drivers from HP. The printer
> has the latest firmware installed. The SCO HPLaserJet driver is still
> the one we have used with the 2015N, so that hasn't changed.
>
> My problem is this: if the drop-down tray 1 is open and has paper in
> it, filePro print jobs will print properly with pitch, orientation,
> lines per inch, whatever, from that tray. If that tray is closed, the
> print jobs will come out WITHOUT ANY FORMATTING from the standard tray
> 2.
>
> To fix this I've switched from PCL5 to PCL6 drivers on the Windows
> server to make sure that Windows printing wasn't leaving the printer in
> a state that Unix couldn't overcome but that didn't help. We have
> rebooted Unix and the printer to clear everything but that didn't help.
> I have updated the printer's firmware.
>
> I've been on the phone with HP tech support who couldn't help me and
> sent me to an Active Chat who couldn't help me and sent me to a phone
> number that turned out to be 'contract support' who couldn't help me and
> sent me back to standard support who kept suggesting that we re-download
> the PCL6 drivers for Windows. So they weren't too much help in addition
> to being hard to understand.
>
> That's why I'm turning to this group. Has anyone seen this issue
> before? If so, what did you do to fix it?
>
> Thanks,
> Steve Wiltsie
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.celestial.com/pipermail/filepro-list/attachments/20100719/37b33c5d/attachment.html
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
More information about the Filepro-list
mailing list