<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Using an HP Printer shared by Windows in OS X</title>
	<atom:link href="http://www.n8gray.org/blog/2005/10/05/using-an-hp-printer-shared-by-windows-in-os-x/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.n8gray.org/blog/2005/10/05/using-an-hp-printer-shared-by-windows-in-os-x/</link>
	<description>distraction in action</description>
	<pubDate>Tue,  6 Jan 2009 13:39:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: OSX Troubleshooting: PrintJobMgr exited unexpectedly with code 105 &#124; Rick Tech</title>
		<link>http://www.n8gray.org/blog/2005/10/05/using-an-hp-printer-shared-by-windows-in-os-x/#comment-11320</link>
		<dc:creator>OSX Troubleshooting: PrintJobMgr exited unexpectedly with code 105 &#124; Rick Tech</dc:creator>
		<pubDate>Fri, 12 Oct 2007 21:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.n8gray.org/sandbox/wordpress/?p=56#comment-11320</guid>
		<description>[...] For some deep seated financial reason, Epson and HP do not like to make all their printers Network aware. They work great out of the box via USB printing. Unluckily a large number of their printers are not postscript compatible. The driver bypasses the CUPS printing daemon. Locally this is fine because the driver is providing the translation. But when you throw it on a network the driver either can&#8217;t communicate across TCP/IP, or if it does, the &#8220;server&#8221; doesn&#8217;t know how to process the raw data it is receiving. [...]</description>
		<content:encoded><![CDATA[<p>[...] For some deep seated financial reason, Epson and HP do not like to make all their printers Network aware. They work great out of the box via USB printing. Unluckily a large number of their printers are not postscript compatible. The driver bypasses the CUPS printing daemon. Locally this is fine because the driver is providing the translation. But when you throw it on a network the driver either can&#8217;t communicate across TCP/IP, or if it does, the &#8220;server&#8221; doesn&#8217;t know how to process the raw data it is receiving. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
