I have been complaining that open source software suffers from dumb names for a while. In fact, when I presented the httperf talk at WWW2007, the track officiator specifically mentioned that very blog post when he introduced me.

So I can’t help but feel squirmy whenever I hear or read the name LibreOffice.

I think this is a dumb name; like really (OpenOffice.org is really dumb too)

• Uses lingo which is never a good idea if you want to get beyond your grassroots (yay! marketing to myself, but not new people woooo!)
  
• Potentially hard to pronounce (needs a page devoted to how pronounce it’s name)
  
• Doesn’t roll off the tongue (see comments on recent Oracle OpenOffice.org ArsTechnica article)
• There is a fair amount of dissent about the quality of the name.
• Many people don’t find the name LibreOffice catchy, rather they find it difficult.

That said, there is evidence that some people like the name, so either they are crazy and should be first up against the wall when the revolution comes or genuinely don’t mind it.

Anyway, I’m hung up on this. Seriously, I really am. I don’t like it, and I want someone to make the effort to change it.

In my downtime, I have been spending a lot of time at the Rocky Mountain Computer Repair Shop here in Calgary, Alberta helping out with system tune-ups and general computer maintenance.

I’ve encountered a huge variety of issues while working with the machines that come in, including virus removal, slow computers, broken installations of Norton, AVG, Internet Explorer, etc. Many of the problems are major nuisances to the owners and are caused by malfunctioning software or some sort of malware running on the system, other times the problems are caused by run of the mill user ineptitude.

I am really good at getting systems working once they have been wacked by problems and can almost always actually fix the problem at hand rather than opt for the traditional orbital nuke of format/re-installation.

That said there are some scenarios in which I recommend reinstalling Windows:

• Want to migrate from 32-bit to a 64-bit installation (note that you would need a 64-bit installation media for this, the default recover partition/disks included on many OEM machines is not sufficient for this)
• Want to start fresh with no OEM software installed
• Have encountered a fundamental problem with your installation of Windows (rarer than many people actually think, but it can happen).
• No service packs have been installed on Windows Vista.
  

Many manufacturers introduce an artificial upgrade ceiling on their customers by deploying 32-bit installations of Windows on 64-bit capable machines. By doing this, it prevents customers from ever expanding the amount of installed, usable memory beyond the 4 GB (actually 3, or 3.5 GB) threshold. This is why many machines come from the factory with only 3 GB installed.

Anyways, this article is not really about formatting and re-installing Windows which is a tiresome task without much challenge these days (except for tracking down drivers which can be very challenging sometimes).

Rather this article is about how to actually go about tuning up a sick or slow computer.

The very first thing to do before beginning a tune up is to ensure that the system is actually working properly. It is very annoying to put hours of work into a computer and then discover that the problem was simply a dying hard drive.

There are some things that die relatively regularly on a typical computer.

1. Power Supply (Incredibly Common)
2. Hard Drive (Incredibly Common)
3. Fans (Incredibly Common)
   
4. Memory (Occasional, but at least it’s easy to address)
5. Motherboard (Usually a surface mounted chip, rather than the board itself)
   

So if a computer is turning itself is turning off all on it’s own the first places to check those noted above. Assuming that the computer turns on, it probably isn’t the Power Supply, so the next thing to do is run a hard drive diagnostic.

Seatools is a perfectly good Windows Application for diagnosing hard drive failures. Generally if the Short Self Test returns no problems then the drive is usually good to go. There may be filesystem issues though which may need to be examined. Filesystem issues can be worked at by loaded a Windows Recovery Console and running the chkdsk utility.

If a computer is failing to boot or having trouble reading data from the drive, even though the drive reports all is well in SeaTools, then consider running chksk /B {driveletter}: against the offending drive (if on Windows Vista or later) in the recovery console. Or chkdsk /F if running on windows XP or earlier.

Typically for filesystem issues, I will boot from a Windows 7 install/recovery disk and run the chkdsk utility from there seeing as Windows 7 has the latest NTFS code in it. Checking Windows 7 NTFS partitions from XP will typically not work as the filesystem has been extended since XP was released.

If the there are no filesystem errors, then checking the memory may be appropriate. Windows 7 has a built in memory checker which works well, however the tried and true memtest86+ works wonders as well.

If everything is checking fine on the diagnostics it may be appropriate to examine the system physically. This can involve popping off a side panel on a desktop or disassembling a laptop (Which can be intimidating at first but isn’t nearly as hard as you might imagine). Issues with fans running at full tilt are often caused by dust covering heat sinks (even in laptops, where this is really hard to check, and it’s best to just blast compressed air inside and see what comes out.

Heat sinks may need to be reseated, which is done by completely removing all of the existing thermal compound from the contact surface of the heatsink and processor with a soft brush and rubbing alcohol, and then applying a thin layer of thermal paste to the surface of the chip and the heat sink and rubbing it in so that it fills all the micro-grooves and grains of the surface and t then remounting the cooler.

If there is stability issues, the last piece of hardware to examine is the motherboard (and occasionally the video card). It may be necessary to apply an update to the boards firmware using the manufacturers firmware update procedure. Intel motherboards are a pleasure to update since that manufacturer provides update ISOs which can be burned and applied without an operating system install. Other manufacturers require the use of a dos boot disk which can be a challenge to acquire.

So now that all the hardware issues are out of the way, the operating system itself needs to be examined.

One of the first things to check is how up to date the installation is. Windows XP should be at Service Pack 3, Vista at Service Pack 2 and 7 and Service Pack 1. If the system is more than one Service Pack behind the state of the art, then I suggest formatting and re-installing with up to date media because waiting for updates to download and install will take FAR more time than cleanly installing an updated OS.

If you don’t have up to date installation media, then you may be out of luck as far this goes, but these things can always be created using slipstreaming techniques.

If the machine just needs to be updated a bit, then by all means go about this. However if the computer is unbearably slow, the first thing to do may be to clean it up a bit.

Download the CCleaner application (and donate to the organization that makes it while you are at it. Use this application remove temporary cruft from the system, and then uninstall everything that doesn’t belong. Personally, if the machine is really slow and a memory upgrade isn’t in its future, consider removing the antivirus suite, as these applications have a tendancy to introduce a considerable amount of extra IO activity. When you are finished uninstalling all the toolbars and nonsense which doesn’t need to be there, work through the startup applications and remove as many as you would like. Windows doesn’t actually need anything listed in the startup locations to boot and work properly so you can feel free to remove anything there. That said, some applications are a good idea to keep running like the Java Update, Google Update and the adobe reader things get reinstalled left-right and center anyways so you may as well leave them.

Now restart the computer.

It should already perform faster, and allow you to run the rest of your activities without fuss.

Next examine the computer for software which should be updated and patched. One of the best tools for this is the Secunia Personal Software Inspector, which is free for personal use. This application will scan the software installed on your computer and indicate to you that it should be updated.

Follow it’s indications. No kidding.

Anything that you cannot update, seriously consider uninstalling.

Lastly consider which applications you are using to browse and interact with the Internet. For Windows XP, there is very little reason to be running Internet Explorer, rather any of the alternatives (Firefox, Chrome, Opera) are superior.

Lastly examine the amount of system memory installed in the machine. Today, 4 GB of RAM is not inappropriate as the size of system applications and software requirements increases. Also, older desktops with onboard graphics can benefit greatly from discrete graphics solutions.

Hopefully this article has been of use, let me know any of your suggestions in the comments.

Take Care,

Ted

Can someone port uriparser to Openbsd?

I was over at Rocky Mountain Computer Repair last night looking over some of the dead machines that had been abandoned by their customers. Most machines were old and rather junky looking, but a few are in decent condition, except for the fact that they simply do not turn on at all.

A friend and associate, Tristan Marler runs Lanified LAN Parties here in Calgary, Alberta and during the last event we got into the deliciously fun game of Minecraft.