<?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>The Perceptus Back Story &#187; support</title>
	<atom:link href="http://blog.perceptus.ca/category/support/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.perceptus.ca</link>
	<description>Issues and adventures in the life of a Canadian micro-sized geek company</description>
	<lastBuildDate>Wed, 08 Sep 2010 05:42:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Whoops.  The Perceptus Forums needed some fixing.</title>
		<link>http://blog.perceptus.ca/2010/08/08/whoops-the-perceptus-forums-needed-some-fixing/</link>
		<comments>http://blog.perceptus.ca/2010/08/08/whoops-the-perceptus-forums-needed-some-fixing/#comments</comments>
		<pubDate>Mon, 09 Aug 2010 00:57:33 +0000</pubDate>
		<dc:creator>leonard</dc:creator>
				<category><![CDATA[downtime]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[forum]]></category>
		<category><![CDATA[perceptus. support]]></category>
		<category><![CDATA[whoops]]></category>

		<guid isPermaLink="false">http://blog.perceptus.ca/?p=284</guid>
		<description><![CDATA[Whoops. The login pages to the Perceptus Forums, has been broken, probably for a while &#8211; it&#8217;s a quiet forum, it was easy to miss. Anyway, it has been fixed. It&#8217;s too bad we don&#8217;t get frequent posts, or else we would have noticed earlier.]]></description>
			<content:encoded><![CDATA[<p>Whoops.  The login pages to the <a href="http://forum.perceptus.ca/">Perceptus Forums</a>, has been broken, probably for a while &#8211; it&#8217;s a quiet forum, it was easy to miss.</p>
<p>Anyway, it has been fixed.  It&#8217;s too bad we don&#8217;t get frequent posts, or else we would have noticed earlier.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.perceptus.ca/2010/08/08/whoops-the-perceptus-forums-needed-some-fixing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Free Computer Burn-In Software</title>
		<link>http://blog.perceptus.ca/2009/06/02/free-computer-burn-in-software/</link>
		<comments>http://blog.perceptus.ca/2009/06/02/free-computer-burn-in-software/#comments</comments>
		<pubDate>Wed, 03 Jun 2009 06:04:28 +0000</pubDate>
		<dc:creator>leonard</dc:creator>
				<category><![CDATA[computers]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[burn-in]]></category>
		<category><![CDATA[burnin]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[cpu]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[free]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[validate]]></category>

		<guid isPermaLink="false">http://blog.perceptus.ca/?p=123</guid>
		<description><![CDATA[I thought that free burn-in software would be easier to find. Every now and then I cobble a computer together from parts, or I have to diagnose a PC that is crashing from time to time.  Unfortunately, even though a PC can boot, it doesn&#8217;t mean that it&#8217;s stable and ready to go. The tool [...]]]></description>
			<content:encoded><![CDATA[<p>I thought that free burn-in software would be easier to find.</p>
<p>Every now and then I cobble a computer together from parts, or I have to diagnose a PC that is crashing from time to time.  Unfortunately, even though a PC can boot, it doesn&#8217;t mean that it&#8217;s stable and ready to go. The tool for this job is burn-in software.</p>
<p>I used to use the free-as-in-beer version of SiSoft Sandra, but over the years it has gotten rather bloated.  Anyway, SiSoft Sandra is more geared towards benchmarking a computer rather than stress testing.</p>
<p>Today, I found a great little tool that seems to do a good-enough job of testing the CPU and RAM &#8211; it also puts a modest amount of load on the hard drive.</p>
<p>The free tool that I am currently recommending: CPU Stability Test by Jouni Vuorio. It seems to run fine in all current versions of Microsoft Windows.</p>
<p>Link: http://www.pcworld.com/downloads/file/fid,7146-order,1/reviews.html</p>
<p>It&#8217;s a bit old, circa 2000, and I can&#8217;t find a current website for it&#8230; but it works.  There are several &#8220;high-quality&#8221;, i.e. non-spammy, websites that host <em>CPU Stability Test. </em>Just Google for it if the link above goes stale.</p>
<p>There is still room to find a better free utility, but for now I&#8217;m satisfied.  But, if you have other suggestions for free burn-in testing software, please leave a comment!</p>
<p>Update: A free utility for testing memory (i.e. looking for bad memory sticks) that runs inside Windows &#8211; http://hcidesign.com/memtest/.  If you&#8217;ve got the ability to reboot the machine, then use Memtest86.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.perceptus.ca/2009/06/02/free-computer-burn-in-software/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>A free schtasks.exe equivalent for XP Home edition</title>
		<link>http://blog.perceptus.ca/2008/12/15/a-schtasks-exe-equivalent-for-xp-home-edition/</link>
		<comments>http://blog.perceptus.ca/2008/12/15/a-schtasks-exe-equivalent-for-xp-home-edition/#comments</comments>
		<pubDate>Mon, 15 Dec 2008 23:38:53 +0000</pubDate>
		<dc:creator>leonard</dc:creator>
				<category><![CDATA[computers]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[limited]]></category>
		<category><![CDATA[permission]]></category>
		<category><![CDATA[scheduled]]></category>
		<category><![CDATA[tasks]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[winxp]]></category>
		<category><![CDATA[xphome]]></category>
		<category><![CDATA[xppro]]></category>

		<guid isPermaLink="false">http://blog.perceptus.ca/?p=74</guid>
		<description><![CDATA[It&#8217;s funny how one stumbles upon the finer differences between XP Home and XP Professional once in a while. Every good geek knows the biggest limits to XP Home such as no ability to join a corporate network, no Remote Desktop, and no encrypted file system (EFS).  But who knew about a tiny utility that [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s funny how one stumbles upon the finer differences between XP Home and XP Professional once in a while. Every good geek knows the biggest limits to XP Home such as no ability to join a corporate network, no Remote Desktop, and no encrypted file system (EFS).  But who knew about a tiny utility that will run a Windows Scheduled Task from the command line? That would be &#8220;schtasks.exe&#8221;, and it&#8217;s not included in XP Home.</p>
<p>The background: I needed a Limited User in Windows to be able to do something requiring Administrative permissions.  There are a few ways to do this, but in this situation, running a scheduled task was the obvious best choice because the task was already there as an overnight maintenance job.</p>
<p>A quick Google search for &#8220;run scheduled task from command line&#8221; will lead you to the aforementioned schtasks tool.  Well, I could copy the file from an XP Pro workstation, but that would violate Microsoft&#8217;s copywrite.</p>
<p>Fortunately, more searching will turn up a reference to an old MS tool &#8220;jt.exe&#8221; from it&#8217;s Windows 2000 Resource Kit.  You can get individual tools from the W2K ResKit here: ftp://ftp.microsoft.com/reskit/win2000/. The license to JT and is much more permissive.  You&#8217;re free to use it, but at your own risk.</p>
<p>The &#8220;JT&#8221; syntax is not straight forward to me.  But these the two examples will probably help:</p>
<p>This lists all tasks: <em>jt.exe /se</em></p>
<p>This will run (&#8220;activate&#8221;?) a task (you do not need to include the .job in the TaskName): <em>jt.exe /sac TaskName /rj</em></p>
<p>On the XP Home Edition computer I was setting this on, the Limited User could run all the scheduled tasks, even when it couldn&#8217;t &#8220;see&#8221; the task in the list. YMMV.</p>
<p>One could  make this end-user friendly by wrapping a batch file around it and put an icon with a link to your script on the Desktop.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.perceptus.ca/2008/12/15/a-schtasks-exe-equivalent-for-xp-home-edition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using an Old Printer with Windows Vista &#8211; and other Vista issues.</title>
		<link>http://blog.perceptus.ca/2008/08/28/using-an-old-printer-with-windows-vista-and-other-vista-issues/</link>
		<comments>http://blog.perceptus.ca/2008/08/28/using-an-old-printer-with-windows-vista-and-other-vista-issues/#comments</comments>
		<pubDate>Fri, 29 Aug 2008 06:37:11 +0000</pubDate>
		<dc:creator>leonard</dc:creator>
				<category><![CDATA[annoying]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[brother]]></category>
		<category><![CDATA[issues]]></category>
		<category><![CDATA[mskb]]></category>
		<category><![CDATA[printer]]></category>
		<category><![CDATA[share]]></category>
		<category><![CDATA[uac]]></category>
		<category><![CDATA[vista]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://blog.perceptus.ca/?p=64</guid>
		<description><![CDATA[So, I bit the bullet and got a new PC with Microsoft Windows Vista. Yes, like every informed geek, I expect a few issues.  However, sooner or later I will need to support Vista at client sites; besides, XP is getting on in years. Today&#8217;s post is mainly about getting my old, but reliable, Brother [...]]]></description>
			<content:encoded><![CDATA[<p>So, I bit the bullet and got a new PC with Microsoft Windows Vista.</p>
<p>Yes, like every informed geek, I expect a few issues.  However, sooner or later I will need to support Vista at client sites; besides, XP is getting on in years.</p>
<p>Today&#8217;s post is mainly about getting my old, but reliable, Brother HL-1030 to work in Vista.  The Brother laser printer is shared over the network by a Windows XP machine.</p>
<p>Some inter-related problems when trying to map this printer in Vista:</p>
<p>Immediately after trying to map the printer, this error comes up: &#8220;The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers&#8221;.  The Microsoft KB describing this, with no real work around other than &#8220;find a compatible driver&#8221;, is KB931719. Honestly, given the error message, wouldn&#8217;t you expect the KB article to provide a way to change the local policy?</p>
<p>Vista has no built in driver for my old HL1030, nor are there compatible drivers on the web.</p>
<p>On the driver front, a quick Google search told me that the built in Vista driver for the Brother HL-2030 would work fine.  But how do I use it? Every time I try the add printer wizard, it tries to install the incompatible point-and-click NT4/2K/XP drivers.</p>
<p>* Update &#8211; 2009-04: I had some intermittent problems with the HL-2030 driver, once in a while a page would not print completely and would cause the printer to require manual intervention to get it going again.  A quick search turned up <a href="http://www.brother.com/E-ftp/windowsvista/europe.html#1230">this page</a> which suggested using the Vista built in driver for the Brother HL-1430.  I&#8217;m trying that now.</p>
<p>So, I used an old trick. I faked a local port for the printer. I don&#8217;t remember the terminology, but I do recall this mapping system being common in the past &#8211; maybe with Novell or DOS?</p>
<p>Anyway, create a new local port using the share name, e.g. \\server\brother. You will be prompted to pick a driver. In my case, using the Brother HL-2030 driver does indeed work fine.</p>
<p>Some other Vista problems that I&#8217;ve had to resolve:</p>
<p>I&#8217;ve disabled User Access Control.  I can&#8217;t officially recommend this to other people, but it just doesn&#8217;t jive with me.</p>
<p>I&#8217;ve removed all but the US keyboard from my keyboard settings. Canadian PC&#8217;s (maybe it&#8217;s dependent on the regional settings?) have English, French and a &#8220;combo&#8221; keyboard mapping installed by default.  That&#8217;s fine until you accidentally hit the hot-key to switch to the French format &#8211; for some reason you do not get a confirmation prompt (!?!).  It happened to me on day two with this computer.  I&#8217;ve previously helped others fix this too.  While you&#8217;re at it, those with Intel Graphics, disable the hot-key that rotates the screen &#8211; everyone stumbles on that one eventually.</p>
<p>I had issues with an Access &#8220;.mdb&#8221; database on a network share that I use for tracking stuff. The resolution for that was to add the &#8220;serving&#8221; machine&#8217;s host name to my Internet trusted zone.  Adding only the IP address did not work, despite a MSKB Knowledge Base article I found.</p>
<p>I&#8217;m sure more Vista issues will pop-up.  But, so far, it&#8217;s been manageable.  I quite like the new 3-D flip task thing and the search tool.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.perceptus.ca/2008/08/28/using-an-old-printer-with-windows-vista-and-other-vista-issues/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
