<?xml version="1.0" encoding="utf-8"?>
<!-- generator="Kukkaisvoima version 9" -->
<rss version="2.0"
xmlns:atom="http://www.w3.org/2005/Atom"
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/"
>
<channel>
<atom:link href="http://www.nickcoleman.org/blog/index.cgi/feed" rel="self" />
<title>Nick Coleman: microsoft</title>
<link>http://www.nickcoleman.org/blog/index.cgi</link>
<description>Nick Coleman blog</description>
<pubDate>Sat, 05 Nov 2011 10:12:00 -0700</pubDate>
<lastBuildDate>Sat, 05 Nov 2011 10:12:00 -0700</lastBuildDate>
<generator>http://23.fi/kukkaisvoima/</generator>
<language>en</language>
<item>
<title>Effing Windows
</title>
<link>http://www.nickcoleman.org/blog/index.cgi?post=effingwindows%21201111051012%21microsoft</link>
<comments>http://www.nickcoleman.org/blog/index.cgi?post=effingwindows%21201111051012%21microsoft#comments</comments>
<pubDate>Sat, 05 Nov 2011 10:12:00 -0700</pubDate>
<dc:creator>Nick</dc:creator>
<category>microsoft</category>
<guid isPermaLink="true">http://www.nickcoleman.org/blog/index.cgi?post=effingwindows%21201111051012%21microsoft/</guid>
<description><![CDATA[ 
 [...]]]></description>
<content:encoded><![CDATA[
<p>
God-damn it, effing bloody Windows has done it again.  I was running the normal weekly
Update and it asked me whether it should update my video card driver, and I foolishly
said yes.  <i>Two hours</i> later, I am back to having a working desktop after a very
frustrating time of VGA madness.
<p>
You would think I would know better than to let Windows update a perfectly working video
card driver, especially when the card is old and the drivers haven't changed for
several years, and especially when it is Windows XP.  Yet, stupidly, I did.  My excuse
is that I had been fiddling around with disabling and then re-enabling some hardware
drivers for my two audio cards in an attempt to get them to play nicely together (which
they eventually did, I am happy to say).  This update was the first one since, so I
suppose I assumed that I had inadvertently triggered some update mechanism in the video
card driver too.
<p>
Windows said the current driver was old and would I like to update to a Microsoft
current one?  Yes.  Update goes ahead, reboot, and...nothing but VGA.  Yikes! Little did
I know I would now be in for a two hour saga of trying to fix it.
<p>
First, try to update the driver using the Hardware Manager.  No dice, the driver is
current.  Rubbish, I know it is isn't.  Then, go to ATI's website to pull the latest and
install that.  No, Windows won't have it, the existing driver is current.  And so it
goes, on and on.
<p>
Of course, it is not helped by having to reboot between each and every change.  Each
test cycle takes about five minutes, most of which is shutting down and starting back
up.
<p>
Eventually in frustration, I uninstall all video drivers, including the VGA one, and
reboot.  This time, for some unknown reason and why it is different from the 10 or so
reboots before I don't know, Windows detects new hardware and installs current drivers.
And they work!  Hoo-bloody-ray. 
<p>
I still don't know why Windows thought the driver needed updating.  But it shits me that
it cost two hours of my time to fix.  And having to reboot?  Ridiculous.  I can insert
and remove driver modules in a Linux kernel any time I want without rebooting.
<p>
Lesson learnt for the hundredth time: don't let Windows update legacy drivers that work.
<p>
]]></content:encoded>
<wfw:commentRss>http://www.nickcoleman.org/blog/index.cgi?post=effingwindows%21201111051012%21microsoft/feed/</wfw:commentRss>
</item>
<item>
<title>Top Two Must-Have Utilities for Windows
</title>
<link>http://www.nickcoleman.org/blog/index.cgi?post=top2musthavewindows%21201109050900%21general%2Cmicrosoft</link>
<comments>http://www.nickcoleman.org/blog/index.cgi?post=top2musthavewindows%21201109050900%21general%2Cmicrosoft#comments</comments>
<pubDate>Mon, 05 Sep 2011 09:00:00 -0700</pubDate>
<dc:creator>Nick</dc:creator>
<category>general</category>
<category>microsoft</category>
<guid isPermaLink="true">http://www.nickcoleman.org/blog/index.cgi?post=top2musthavewindows%21201109050900%21general%2Cmicrosoft/</guid>
<description><![CDATA[ 
 [...]]]></description>
<content:encoded><![CDATA[
<p>
There are only two must-have tools for Windows that are on my machines.  If you are
running an OS later than XP (Vista or 7), then there is only one.
<p>
Windows is let down by a poor file management tool.  It tries to push file management
into a quasi browser, Explorer, and the result is a bad compromise.  
<p>
The first thing I do on any Windows machine is install xplorer² from <a
href="http://www.nickcoleman.org/axs/ax.pl?http://zabkat.com/">Zabkat</a>, a small
software company run by a chap called Nikos.  There is a free lite version and a
subscription-based fully featured version.  If you are a command line guru from the unix
world, spring for the full featured version: the list of features is huge, you can read
them <a href="http://www.nickcoleman.org/axs/ax.pl?http://zabkat.com/x2facts.htm">here</a>.  If
you don't need all those features, the free lite version will still provide much better
file management and exploring abilities than the default Windows Explorer; two-pane
browsing alone is worth it.
<p>
I've been using xplorer² for about a decade and bought a licence several years ago.  It
is the best file management utility I've found.  It is even better than the various unix
ones and I wish there was a port of it for Linux.
<p>
The other thing that lets older Windows down is poor file searching.  This doesn't apply
to Windows 7 which has a good fast file searcher, or, to a lesser degree, Vista which
has a reasonable file searcher.  However, if you are using Windows XP, the file searcher
is a dog and needs to be replaced.
<p>
There are a couple of utilities that bring the full power of regular expressions, date
and time, file size and so on to the searching mechanism.  One of them is <a
href="http://www.nickcoleman.org/axs/ax.pl?http://www.voidtools.com/">Everything</a> and
the other is <a
href="http://www.nickcoleman.org/axs/ax.pl?http://locate32.net/">Locate32</a>.  They are
both free of charge and Locate32 is also open source with a BSD licence.  Both provide
similar functions, albeit with different approaches.
<p>
Everything sets up a service that monitors the NTFS filesystem and updates its database
every time a file changes. It won't monitor networked drives and it is persistent in
memory.  It uses up too much RAM for my liking, about 45MB for 1,000,000 files, but
because its database is in RAM it is very quick.  Personally, I would rather not have a
service continually using RAM when I may use the program only once a week or so.
<p>
<p>
Locate32 doesn't sit in memory. It updates its database to whenever you set it, say once
a day.  The main benefit for me over Everything is that it can also locate files by
their contents (like <i>grep</i> in the unix world), so you can do things like search
for all .txt or .doc files that contain "foo" and are more recent than 7 days old. (Note
that xplorer² can do this too in the professional version.) That makes it a deal-beater
for me, so I choose Locate32. 
<p>
You can try any of these utilities for free (xplorer² has a 30-day free trial for the
professional version).  Give them a go and make your Windows desktop experience much
less of a hassle.
<p>
]]></content:encoded>
<wfw:commentRss>http://www.nickcoleman.org/blog/index.cgi?post=top2musthavewindows%21201109050900%21general%2Cmicrosoft/feed/</wfw:commentRss>
</item>
<item>
<title>Windows 7 Upgrade Removes Backup Option
</title>
<link>http://www.nickcoleman.org/blog/index.cgi?post=microsoftvistaupgradebackup%21201001260952%21microsoft</link>
<comments>http://www.nickcoleman.org/blog/index.cgi?post=microsoftvistaupgradebackup%21201001260952%21microsoft#comments</comments>
<pubDate>Tue, 26 Jan 2010 09:52:00 -0700</pubDate>
<dc:creator>Nick</dc:creator>
<category>microsoft</category>
<guid isPermaLink="true">http://www.nickcoleman.org/blog/index.cgi?post=microsoftvistaupgradebackup%21201001260952%21microsoft/</guid>
<description><![CDATA[ 
 [...]]]></description>
<content:encoded><![CDATA[
<p>
I usually hesitate to write about Microsoft, because it's too easy a target,
you're invariably preaching to the converted, and there's a million
other people saying the same thing.
<p>
This one, however, just makes me shake my head<sup><small><a href="#fn1"
id="back1">1</a></small></sup>.
<p>
Microsoft is offering a Family version of an upgrade to Windows 7.  It
allows you to upgrade three computers with one upgrade purchase.
<p>
Get this.  The upgrade removes any previous capability you had to back
up to a remote machine.  Yep, you can't backup to another machine on your
LAN, nor can you backup to a dedicated backup storage unit.  You can
only backup to the local machine.
<p>
For almost all casual users, backup to the local machine  means backup
to the same disk as the originals.
<p>
Backups serve two purposes: you can recover from your error when you
accidentally delete a file; you can recover from a hardware failure when
you can't access your data.
<p>
What is the single most common hardware failure of data?  The disk
drive.  Which is where your backups are.
<p>
What on earth are they thinking?  More relevant, what sort of mind
process goes on in their marketing area?  "Yes, let's remove the ability
for a user to safely store their data."  Unless you pay an extra $200
for the next higher upgrade, which does allow you to backup remotely.
<p>
We have become used to Microsoft's marketing tactics which do things
like arbitrarily limit the operating system's capabilities.  XP vs XP
Pro's networking ability, for example.
<p>
But when Microsoft endangers your data purely as a marketing tactic,
that is a new low, even for them.
<p>
See <a
href="http://www.nickcoleman.org/axs/ax.pl?http://www.theaustralian.com.au/australian-it/windows-70-upgrade-closes-off-an-upgrade-option/story-e6frgakx-1225823429974">
<i>The Australian</i></a> for the full article.  Note Microsoft's weasel
words to explain their rational.
<p>
<div id="footnote">
<a href="#back1" id="fn1">[1]</a>This post is full of "what the..." and
"huh?" and "mind-boggling" moments.  Despite enormous temptation, I've used
extreme will-power and restrained my exclamation
marks.  "Must not use exclamation mark... aaargh... just
one... no, no. Alright, just one.&nbsp;&nbsp; ! There."  <a href="#back1">&#8593;</a>
</div>
]]></content:encoded>
<wfw:commentRss>http://www.nickcoleman.org/blog/index.cgi?post=microsoftvistaupgradebackup%21201001260952%21microsoft/feed/</wfw:commentRss>
</item>
</channel>
</rss>

