Quote:
|
Originally Posted by mbpark
Mac OS X has CUPS. Grab 1.2rc1 from www.cups.org, install on the Mac, and share out the printer from there.
Set up the shared printer as an Apple Color Laserwriter 12/600 on the XP box. |
I am trying to understand what was happening here AND how using Unix printing solves the problem. CUPL apparently prints using Unix Printing format (that is not defined).
To step back - document to be printed is on an Apple OSx machine. An HP printer driver is loaded onto that Apple. HP Deskjet printers don't use postscript; they use PCL. Apple uses Samba (SMB) network protocol to transmit printer information from Apple's document to a Windows 2000 machine and its HP Deskjet printer. Why would the HP driver on Apple send that information to the XP in Postscript when neither the HP driver nor the HP printer understands postscript?
Normally a Windows program outputs its printer data in EPS. An HP printer driver would convert that EPS to PCL - what HP printers understand. Maybe the Windows 2000 machine expects printer data from SMB (network) to arrive already converted to PCL by that other (in this case Apple) computer. But the Apple does not do that. Apple sends its screen data (in Postscript) directly into SMB network packets?
So CUPL converts that Apple screen (already in Postscript) to what? What is the language used by Unix printer drivers? If the Windows 2000 printer prints data directly from the SMB network, then why would CUPL on the Apple also not print directly to the Windows 2000 printer. Unfortuantely these technical documents like to short us on information - or I am missing something.
And finally, that Windows 2000 system prints from Windows 2000 programs using the HP driver. Therefore the same printer (I suspect) cannot also be driven by a Unix driver. But CUPL apparently needs a Unix printer driver assigned to that HP Deskjet printer. How do I get around that? Or can multiple drivers be assigned to the same printer - I did not think so?
What I think I need is some way for the Apple to talk (using SMB on network) to an HP driver on the Windows 2000 machine, OR for the Apple to output PCL directly to the Windows 2000 Deskjet printer. I thought that second option was what I was doing when I loaded the HP Deskjet printer driver on Apple OSX. I think. Where does all the above go right or wrong?
Unfortuately the computers and network are not readily available to play with AND I have limited time on site to solve this Windows/Apple printer sharing. BTW Windows 2000 programs also must talk to an Epson printer on the Apple - a problem I have avoided because printing in that direction apparently is even more complex. Currently I am only trying to solve Apple printing to an HP Deskjet on a Windows 2000 machine using an existing and apparently working SMB network communication.
Where does all the above go wrong?