<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Steven Eppler's Blog &#187; on the job</title>
	<atom:link href="http://www.steveneppler.com/blog/category/on-the-job/feed" rel="self" type="application/rss+xml" />
	<link>http://www.steveneppler.com/blog</link>
	<description>My life, technology, and everything in between</description>
	<lastBuildDate>Fri, 09 Jul 2010 17:05:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Fixing Mac OS X 10.6&#8217;s ping command (aka, removing Request timeout for icmp_seq #)</title>
		<link>http://www.steveneppler.com/blog/2010/03/31/fixing-mac-os-x-10-6s-ping-command-aka-removing-request-timeout-for-icmp_seq</link>
		<comments>http://www.steveneppler.com/blog/2010/03/31/fixing-mac-os-x-10-6s-ping-command-aka-removing-request-timeout-for-icmp_seq#comments</comments>
		<pubDate>Wed, 31 Mar 2010 21:12:14 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/?p=79</guid>
		<description><![CDATA[If you are like me, and annoyed that OS X 10.6&#8217;s ping command displays the following text when it cannot reach a host:

Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

Then you&#8217;ll be happy for the fix.  You can either download the source code to the ping command from Apple [...]]]></description>
			<content:encoded><![CDATA[<p>If you are like me, and annoyed that OS X 10.6&#8217;s ping command displays the following text when it cannot reach a host:<br />
<code><br />
Request timeout for icmp_seq 0<br />
Request timeout for icmp_seq 1<br />
Request timeout for icmp_seq 2<br />
</code><br />
Then you&#8217;ll be happy for the fix.  You can either download the <a href="http://opensource.apple.com/source/network_cmds/network_cmds-325.1/ping.tproj/ping.c">source code</a> to the ping command from Apple and edit it yourself, or you can <a href="http://epplersoft.com/ping-fixed.tar.gz">download</a> my pre-compiled copy.</p>
<p>If you choose to edit it yourself, you&#8217;ll want to comment out lines 977 and 978 so they look like this:<br />
<code><br />
 // if (!(options &#038; F_QUIET))<br />
                                        // printf("Request timeout for icmp_seq %ld\n", ntransmitted - 2);<br />
</code></p>
<p>Then just type &#8216;gcc ping.c&#8217; and you&#8217;ll end up with a file called a.out, which you can use to replace /sbin/ping, or put in your local ~/bin directory if you&#8217;ve got one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2010/03/31/fixing-mac-os-x-10-6s-ping-command-aka-removing-request-timeout-for-icmp_seq/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HP Print Driver Crash when printing to networked printers</title>
		<link>http://www.steveneppler.com/blog/2009/09/21/hp-print-driver-crash-when-printing-to-networked-printers</link>
		<comments>http://www.steveneppler.com/blog/2009/09/21/hp-print-driver-crash-when-printing-to-networked-printers#comments</comments>
		<pubDate>Mon, 21 Sep 2009 20:50:57 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/?p=77</guid>
		<description><![CDATA[I ran into an issue recently where any application would crash when printing to a network printer.  Our environment is unique in that we are printing to a Windows print server (using Guest privileges), but users on the network are logging in using the Novell client.
The crash would not happen with generic Microsoft drivers [...]]]></description>
			<content:encoded><![CDATA[<p>I ran into an issue recently where any application would crash when printing to a network printer.  Our environment is unique in that we are printing to a Windows print server (using Guest privileges), but users on the network are logging in using the Novell client.</p>
<p>The crash would not happen with generic Microsoft drivers that came with Windows XP, but it would happen with any HP-branded drivers.  Our first workaround was just to use PCL or PostScript drivers that closely matched the printer, and hope for the best.</p>
<p>In the end, we found out that when printing with the HP drivers, it would write to a file in the Windows directory called hpmnwun.ini.  The contents it would write were:</p>
<p><code><br />
[NWUSERNAME]<br />
NOVELL=1<br />
NWUSERNAME=testuser<br />
</code></p>
<p>Fixing the issue was a two step process:</p>
<p>1:  Erase the contents of the file<br />
2:  Change the NTFS Permissions of the file to make it read-only by all users (even Administrators)</p>
<p>I think this forces the HP drivers to print to the printer in the standard Windows printer sharing way.  When the HP drivers detect the Novell client installed, it writes the NWUSERNAME info to the file and must try to print in an &#8216;NDPS friendly&#8217; way, which causes the application to crash when printing to a standard Windows shared printer and not a NDPS printer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2009/09/21/hp-print-driver-crash-when-printing-to-networked-printers/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adding Printers to OS X from the Command Line</title>
		<link>http://www.steveneppler.com/blog/2009/07/09/adding-printers-to-os-x-from-the-command-line</link>
		<comments>http://www.steveneppler.com/blog/2009/07/09/adding-printers-to-os-x-from-the-command-line#comments</comments>
		<pubDate>Thu, 09 Jul 2009 20:04:12 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/?p=72</guid>
		<description><![CDATA[After a little searching, I found out you can add printers to OS X from the command line using this syntax:

lpadmin -p Printer_Name -L "Printer Location" -E -v lpd://x.x.x.x -P /Library/Printers/PPDs/Contents/Resources/en.lproj/Printer_Driver.gz

If you don&#8217;t specify the -P option, it will not show up in your Print or Printer Setup dialogs.  If you want to include [...]]]></description>
			<content:encoded><![CDATA[<p>After a little searching, I found out you can add printers to OS X from the command line using this syntax:<br />
<code><br />
lpadmin -p Printer_Name -L "Printer Location" -E -v lpd://x.x.x.x -P /Library/Printers/PPDs/Contents/Resources/en.lproj/Printer_Driver.gz<br />
</code></p>
<p>If you don&#8217;t specify the -P option, it will not show up in your Print or Printer Setup dialogs.  If you want to include the generic PPD, it is located here:</p>
<p><code>/System/Library/Frameworks/ApplicationServices.framework/Versions \ /A/Frameworks/PrintCore.framework/Versions/A/Resources/Generic.ppd</code></p>
<p>That path is all one line, with no spaces.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2009/07/09/adding-printers-to-os-x-from-the-command-line/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Synchronizing data between different computers and OS&#8217;s with Dropbox</title>
		<link>http://www.steveneppler.com/blog/2009/05/08/synchronizing-data-between-different-computers-and-oss-with-dropbox</link>
		<comments>http://www.steveneppler.com/blog/2009/05/08/synchronizing-data-between-different-computers-and-oss-with-dropbox#comments</comments>
		<pubDate>Fri, 08 May 2009 18:57:02 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[on the job]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/?p=70</guid>
		<description><![CDATA[About a week ago I installed Dropbox, and I have to recommend it to anybody who needs to sync their files between machines.  I have a group of Macs that I use to sync data between, and I used to use iDisk, but Dropbox is so much quicker that I can&#8217;t see myself using [...]]]></description>
			<content:encoded><![CDATA[<p>About a week ago I installed <a href="https://www.getdropbox.com/referrals/NTEwNTU4OTc5">Dropbox</a>, and I have to recommend it to anybody who needs to sync their files between machines.  I have a group of Macs that I use to sync data between, and I used to use iDisk, but Dropbox is so much quicker that I can&#8217;t see myself using iDisk anymore.  Also, the syncing between Linux and Mac OS X works great &#8211; I haven&#8217;t got a chance to test the Windows client yet, but I&#8217;m sure it works just as good.</p>
<p>If you sign up with this <a href="https://www.getdropbox.com/referrals/NTEwNTU4OTc5">link</a>, you&#8217;ll get an extra 256MB, and so will I.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2009/05/08/synchronizing-data-between-different-computers-and-oss-with-dropbox/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Printing 3&#215;5 cards on Epson LQ-590 or LQ-300 impact printers</title>
		<link>http://www.steveneppler.com/blog/2008/03/17/printing-3x5-cards-on-epson-lq-590-or-lq-300-impact-printers</link>
		<comments>http://www.steveneppler.com/blog/2008/03/17/printing-3x5-cards-on-epson-lq-590-or-lq-300-impact-printers#comments</comments>
		<pubDate>Mon, 17 Mar 2008 16:40:52 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[on the job]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2008/03/17/printing-3x5-cards-on-epson-lq-590-or-lq-300-impact-printers</guid>
		<description><![CDATA[With Windows XP, you can define custom paper sizes (such as 3&#215;5 cards) by doing the following:
Start -> Printers and Faxes -> File -> Server Properties
In this dialog, you can define a 3&#215;5 card.  The problem is, with the LQ-590 and LQ-300 drivers, these paper sizes do not show up as options when you [...]]]></description>
			<content:encoded><![CDATA[<p>With Windows XP, you can define custom paper sizes (such as 3&#215;5 cards) by doing the following:</p>
<p>Start -> Printers and Faxes -> File -> Server Properties</p>
<p>In this dialog, you can define a 3&#215;5 card.  The problem is, with the LQ-590 and LQ-300 drivers, these paper sizes do not show up as options when you try and print.  Any paper size below 4 inches in height will disappear from your printing options.</p>
<p>To get around this, install the LQ-570 driver (the one that is built into Windows XP).  This driver will let you use a 3&#215;5 sized form.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2008/03/17/printing-3x5-cards-on-epson-lq-590-or-lq-300-impact-printers/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Leopard Error -5002 when connecting to AFP shares</title>
		<link>http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares</link>
		<comments>http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares#comments</comments>
		<pubDate>Fri, 26 Oct 2007 20:40:02 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares</guid>
		<description><![CDATA[When connecting to AFP shares in the new Mac OS X 10.5 (Leopard), you may get a -5002 error when the server only supports clear text passwords.  To resolve, either disable clear text passwords on the server side, or change the following plist:
~/Library/Preferences/com.apple.AppleShareClient.plist
You need to change the afp_cleartext_allow value to &#8220;Yes&#8221; &#8220;true&#8221; or &#8220;1&#8243; [...]]]></description>
			<content:encoded><![CDATA[<p>When connecting to AFP shares in the new Mac OS X 10.5 (Leopard), you may get a -5002 error when the server only supports clear text passwords.  To resolve, either disable clear text passwords on the server side, or change the following plist:</p>
<p>~/Library/Preferences/com.apple.AppleShareClient.plist</p>
<p>You need to change the afp_cleartext_allow value to <del datetime="2008-10-10T13:40:53+00:00">&#8220;Yes&#8221;</del> &#8220;true&#8221; or &#8220;1&#8243; (depending on the current values you see, either &#8220;false&#8221; or a &#8220;0&#8243;).</p>
<p>Here&#8217;s an excerpt from my file:</p>
<p><code><br />
...<br />
&lt;key&gt;afp_cleartext_allow&lt;/key&gt;<br />
&lt;true /&gt;<br />
&lt;key&gt;afp_cleartext_warn&lt;/key&gt;<br />
&lt;integer&gt;0&lt;/integer&gt;<br />
&lt;key&gt;afp_default_name&lt;/key&gt;<br />
&lt;string&gt;&lt;/string&gt;<br />
...<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>QuickTime Streaming returns 400 Bad Request</title>
		<link>http://www.steveneppler.com/blog/2007/02/20/quicktime-streaming-returns-400-bad-request</link>
		<comments>http://www.steveneppler.com/blog/2007/02/20/quicktime-streaming-returns-400-bad-request#comments</comments>
		<pubDate>Tue, 20 Feb 2007 22:53:49 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2007/02/20/quicktime-streaming-returns-400-bad-request</guid>
		<description><![CDATA[When you are trying to view a QuickTime movies from a streaming server, sometimes you will get back a 400 Bad Request error.  At my network at work, we intercept all port 80 traffic and forward to our squid proxy server, which is why we get this error.  In order to fix this, just open [...]]]></description>
			<content:encoded><![CDATA[<p>When you are trying to view a QuickTime movies from a streaming server, sometimes you will get back a 400 Bad Request error.  At my network at work, we intercept all port 80 traffic and forward to our squid proxy server, which is why we get this error.  In order to fix this, just open up System Preferences, open the QuickTime pane, click the Advanced tab, and choose Custom&#8230; under the Transport Setup dropdown.  Choose HTTP as your protocol, and type in 7070 where is says Other.  Since making this modifications, we can view the QuickTime streams with no problems.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2007/02/20/quicktime-streaming-returns-400-bad-request/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>WebTester 5.0 Released</title>
		<link>http://www.steveneppler.com/blog/2006/06/14/webtester-50-released</link>
		<comments>http://www.steveneppler.com/blog/2006/06/14/webtester-50-released#comments</comments>
		<pubDate>Wed, 14 Jun 2006 16:08:29 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[on the job]]></category>
		<category><![CDATA[web hosting and design]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2006/06/14/webtester-50-released</guid>
		<description><![CDATA[The newest version of WebTester, my online testing and quizzing software, has been released, along with a completely new site re-design.  You can check out the site here:
WebTester Home
Feel free to check out the newly created forums:
WebTester Forums 
Or, you can log into the demo, using the following information:
Username:  admin
Password:  admin
WebTester Admin
WebTester [...]]]></description>
			<content:encoded><![CDATA[<p>The newest version of WebTester, my online testing and quizzing software, has been released, along with a completely new site re-design.  You can check out the site here:</p>
<p><a target="_blank" title="WebTester Online Testing &#038; Quiz Management" href="http://www.webtester.us">WebTester Home</a></p>
<p>Feel free to check out the newly created forums:</p>
<p><a target="_blank" title="WebTester Forums" href="http://talk.webtester.us">WebTester Forums </a></p>
<p>Or, you can log into the demo, using the following information:</p>
<p>Username:  admin<br />
Password:  admin</p>
<p><a target="_blank" title="WebTester Administration" href="http://wt.epplersoft.com/admin">WebTester Admin</a><br />
<a target="_blank" title="WebTester Testing Engine" href="http://wt.epplersoft.com">WebTester Engine</a></p>
<p>Take a look and tell me what you think.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2006/06/14/webtester-50-released/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>InDesign Crashes Whilte Printing on Mac OS X</title>
		<link>http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x</link>
		<comments>http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x#comments</comments>
		<pubDate>Mon, 17 Apr 2006 17:11:43 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x</guid>
		<description><![CDATA[Sometimes, Adobe InDesign will crash when trying to print on a user account with a networked home folder under Mac OS X.  Here is the fix that I use:

ditto -rsrc /System/Library/Printers /Library/Printers

I send that command to all computers with the problem via ARD (Apple Remote Desktop) and it seems to resolve all of the [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes, Adobe InDesign will crash when trying to print on a user account with a networked home folder under Mac OS X.  Here is the fix that I use:</p>
<pre>
ditto -rsrc /System/Library/Printers /Library/Printers
</pre>
<p>I send that command to all computers with the problem via ARD (<a href="http://www.apple.com/remotedesktop/" target="_blank">Apple Remote Desktop</a>) and it seems to resolve all of the issues.</p>
<p>If that doesn&#8217;t work, you need to copy or create a Printers folder in the current users Library folder.  Drop into Terminal and type the following:</p>
<pre>
mkdir ~/Library/Printers
</pre>
<p>Those two methods have resolved most of our InDesign printing issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Locally Cache Mac OS X Network Login Folders</title>
		<link>http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders</link>
		<comments>http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders#comments</comments>
		<pubDate>Tue, 04 Apr 2006 15:21:22 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders</guid>
		<description><![CDATA[Here at the school district I was running into a problem where if several Mac OS X wireless clients logged into the network at once, everything slowed down to a crawl.  After researching the problem, it looked like the user&#8217;s Library and Microsoft User Data folders were causing the problem.  I tried turning [...]]]></description>
			<content:encoded><![CDATA[<p>Here at the school district I was running into a problem where if several Mac OS X wireless clients logged into the network at once, everything slowed down to a crawl.  After researching the problem, it looked like the user&#8217;s Library and Microsoft User Data folders were causing the problem.  I tried turning on OS X&#8217;s home folder syncronization, but that didn&#8217;t work very well, and filled up our older computers fast.  The solution I found was to locally cache the user&#8217;s Library and Microsoft User Data folder.  To do this, create a symbolic link from the user&#8217;s networked &#8216;Library&#8217; folder and point it to a local source.  I chose /tmp/UserCache/username/Library.  Here is the login script I created to automate the process:</p>
<pre>
#! /bin/bash

# Create local user caches of important directories
# Written by Steven Eppler 04/04/2006

export PATH=/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin

# Set user variable
user="$1"

# This grabs the user's home directory server
input=`dscl localhost read Search/Users/$user NFSHomeDirectory`
nethomedir=${input:18}

# Or you can hardcode it...
# nethomedir="/Network/Servers/ServerName/Volume/$user"

# Check for blank nethomedir - otherwise you will delete
# the root /Library folder!
if [ """$nethomedir""" != "" ]; then

echo $user
echo $nethomedir

# Create local caching directories
mkdir /tmp/UserCache
mkdir /tmp/UserCache/$user
mkdir /tmp/UserCache/$user/Microsoft\ User\ Data
mkdir /tmp/UserCache/$user/Library

# Give everyone rights to them...
chmod -R ugo=rwx /tmp/UserCache

# Create Documents and Desktop folder (sometimes they don't exist)
mkdir $nethomedir/Documents
mkdir $nethomedir/Desktop

# Delete old folders or links
rm -rf $nethomedir/Library
rm -rf $nethomedir/Documents/Microsoft\ User\ Data

# Create new links
ln -s /tmp/UserCache/$user/Library $nethomedir/Library
ln -s /tmp/UserCache/$user/Microsoft\ User\ Data $nethomedir/Documents/Microsoft\ User\ Data

fi
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
