A week with Windows

A week with Windows

As a GNU/Linux user and developer I rarely get to see how the other half lives. That is, Windows users. So, during my week off work, I had two goals: complete the recording of a music project I’d been working on, and finish as many outstanding (non-Linux-centric) projects as possible... using only Windows. I managed the first without too many problems (now to find a record deal ;) but had some issues on the second. This entry documents those problems, and the lessons to be learnt from it. I’m writing this part as therapy, and part talking point, in the hope someone will comment and explain why these things are the way they are. There is a companion piece, A Week With Technology, covering the other problems I had that week.

Disclaimer: what follows are the trials and tribulations of two Windows machines. One is an IBM Thinkpad laptop, the other a self-build desktop. So there are twice as many problems as normal.

My first task was getting Windows installed on the desktop. I’d got a disc (legitimate, too!) of Windows 2000 and thought that it’d be up-to-date enough for my needs. Alas no. The on-board network card is not recognized by W2K. No problem, I’ll just logon to the Microsoft site and download... Oh... Wait... Perhaps I’ll use the Windows laptop to grab some_random_driver.zip from their server. I tried and failed. As did the installation CD I’d been given with the motherboard. Various random, seemingly unrelated, error boxes appeared with cryptic messages so I gave up, found a PCI network card, and installed that instead. Perfect! (I later used it to find updated drivers for the on-board network card, but still no joy.) Rhetorical note to self: never install or configure a machine without a second machine with Internet access. Borrow a laptop if necessary.

The next task was to format a partition. That should be easy! Since I wanted to re-use it in my NSLU2, I selected FAT32 and walked away. Only to find an error popping up almost instantly saying Windows couldn’t format it. Thinking I’d got a broken drive, I started worrying. But it didn’t work on another disc I tried. It turns out that Windows is intentionally crippled to stop you formatting “large” discs with FAT32, because Microsoft want to promote NTFS, and would rather you didn’t use FAT32. I half agree with them—I don’t want to use FAT32 on the drive either, I want to use ext3. But there’s no facility for that. So FAT32 it is. But since Windows won’t format the drive for, er, Windows usage, it’s over to Partition Magic to do the dirty. Rhetorical note to self: if you need anything that isn’t an OS-default, find a specialist package to do the job.

While formatting, I thought I’d backup a few files onto DVD-R on the laptop. I have an external Lacie DVD-RW that hadn’t caused me any problems. Until now. For some reason the program refused to work, and the only suggestion was “reinstall the software”. Which I did. This time the DVD burner wasn’t even in the device list. And neither was the internal DVD drive from which I’d just installed the software. So I re-installed the drivers from the laptop’s rescue partition. But to no avail. I searched for, and downloaded, patches from the IBM website, but still nothing. After much time wasted, I copied cdrom.sys and some related files (as listed in the “Device Manager” within the control panel) from the Windows desktop machine and it started working. Alas, the DVD re-writer still doesn’t work, two weeks hence, despite repeated reinstalls.

Oh, and I’d accidentally installed the Nero index server. It doesn’t have anything to do with the burning process, but it does contain NMIndexStoreSvr, which crashes periodically for no good reason. So I removed that.

Another annoying productivity delay occurred when the laptop told me to change my password upon logon. I have no problem with this; every user should change their password regularly, and I don’t mind the OS reminding me. When I did, however, the boot process stopped, and the machine refused to log me on with the new password. I had to hard reset (suffering the patronizing “If you’d shutdown properly you wouldn’t see this” message) and logon again. Rhetorical note to self: only change the password once Windows has fully booted.

I can’t remember the day I had graphics card problems, but I’ll assume it was a Sunday, to space the problems out a bit. Basically, I couldn’t install a second graphics card into my PC despite managing it with the same card about ten years ago. Yes, really! It was used for the second monitor of my old music PC. I fear the “new and improved” drivers don’t work properly under W2K, so I’m working at half capacity. Plus, the existing driver for the working graphics card is so slow/buggy/broken that every time there’s a large screen update, noise is produced on the sound card. Since this is my music PC, and I’m trying to produce a demo of my new album on it, this was causing me a problem. The solution was to minimize all the windows and then start recording, which avoided any screen updates. Rhetorical note to self: latest doesn’t necessarily mean best.

One of the simpler problems to overcome was with the Windows command shell not having a backtick facility, or any sensible way of providing the date in a custom format. It would have been simple enough to install bash and solve my “backup to a newly created directory with today’s date” problem in that manner, but in attempt to mimic what a traditional Windows user would do I searched for suitable software and solutions on the Internet. I found no decent solutions, so I wrote Backtick for Windows and a neat little replacement date utility for Windows to accomplish the task. Typing

backtick md `ndate`

Feels icky, but it rocks! Although I’ve since discovered

md %DATE:~-4,4%%DATE:~-10,2%%DATE:~-7,2%

does the same job, I like the brevity of my solution better. Rhetorical note to self: the simplest solutions are often the hardest to find. If you’re not a developer, some solutions are just impenetrable.

Monday was my “get the NetGear SC101 NAS working”, day. NAS stands for Network Address Storage. Or, if you’re like me, Not work. The NetGear fell over after just 30 seconds of use. In this case I determined “use” as copying one 5 meg file to it. This happened from both Windows clients. Hardly a heavy load, though. Both NetGear and the company from which I bought it refuse to accept the problem existed. Pah!

Tuesday was pain free, I’d written a short piece for string quartet, and a demo for the first part of my avant-garde symphony was complete. I thought I was cooking! Rhetorical note to self: savor these moments, they don’t last.

My Wednesday was mostly occupied with web design for a friend of mine. Both Windows machines handled the task admirably. Alas, my Linksys WRK54G router did not. Instead of requiring a reboot every 3-4 days (which is pretty pants, to be honest, but better than nothing), we were lucky to get 20 minutes of net access before the frustrations began. The only change to the network configuration was the addition of a third Windows machine; my mates Windows XP laptop. Once he’d left, all the problems went away. Sorry, David!

On Thursday my new mobile phone arrived! Hooray. Their next day delivery service had only taken 6 days. Plus a phone call. But this seemed like a minor problem. I duly plugged in the USB cable to download some music (it appears as a standard memory device, so no drivers are necessary) only to find I couldn’t un-mount it! It looks like W2K lets you plug in and access the device as a normal user, but not un plug it without shutting down the computer. It claims admin rights are to blame, but logging in as Administrator didn’t help. And the Windows equivalent of su, Run As, is only available as an explicit invocation on executable files. Run As will additionally work on .cpl (control panel) files, but not (alas) .msi files. MSI files are the installation bundles used with some Windows applications, and if there’s one time you need to run as Administrator, it’s when installing software. Ho hum. I’d better reboot then. Rhetorical note to self: use Bluetooth if available. I did try it in this case, but the Bluetooth driver wouldn’t work. I’m glad I only borrowed the device to experiment.

It was Saturday, and I’d very little holiday time left with which to capture some material from my (fast degrading) video cassettes. My TV card supplies a simple, but useable, video capture tool so I started it up. Fully aware of the 4 gig limit under FAT32 I moved all the temporary, working, and resultant files onto the NTFS partition. I also invoked the DivX codec to ensure the video got nowhere near that size, and started recording. It stopped, unceremoniously, after 20 minutes. Checking the settings, I could find nothing wrong, so I tried again. Again nothing. It appeared that the tool has a hard-wired 4 gig limit, completely ignoring the underlying file-system, and disregarded the compressions settings by saving all the temporary data as a raw stream in its own file, thereby ignoring the configuration until you saved the data from within this file. It took 8 hours to capture 3 hours of material.

Finally, on Sunday evening, I wanted to relax with my working media server, a can of beer, and take-out pizza. I actually ended up fixing PCs, as the Windows MediaMVP server refused to deliver my recently-captured video clips. The problem was a bad FAT table on one of the drives attached to the NSLU2. This introduced timeouts on the Windows machine. Bad timeouts. Freezing the machine for 10 minutes at a time. So I connected the machine locally, and started to fix the disk. While doing so I did something I wouldn’t normally consider a problem—copying a file from one disc to another. Neither was the disc being checked, but one did have an undiagnosed FAT problem. The price I paid for copying from a broken FAT disc was high—it rebooted my Windows machine, corrupted the boot block, and destroyed the data on my boot partition. And all because I copied a file! I can not believe how stupid this is. I have yet to run low-level recovery tools on the disc, but I’m quietly hopeful I’ll get the data from it. The biggest time sink was in the Windows settings, which I’ll have to redo. Or learn Ghost. Rhetorical note to self: fix any and all problems as soon as they arise. Not everything will self-test effectively.

I can not believe I had so many problems in one week. Have my Windows skills been reduced to that of a stillborn newbie? Is the quality of hardware and software now so low as to be useless? Where are the Windows forums that don’t popup advertising windows, and require site registration and login? How do normal people cope?

I’ve never had these problems with my Debian box, so free software is doing something right. Be proud of it!

Rant over.



alex2echo's picture
Submitted by alex2echo (not verified) on

It would have been more fair to try Windows XP, not 2000.
Other than that I totally understand your pain ... FAT32 is such a piece of crap file system that I feel sick just hearing about it.
But unfortunately it is a standard used by lots of devices.

BTW ... you can install in windows a driver to make windows recognize ext3 partitions.
From a quick search I found this: http://www.fs-driver.org

You are right, Debian is a stable and mature system, and it deserves some credits.
Don't give up on it :)

Steven Goodwin's picture

Since this has come up a couple of times I feel I'd better clarify.

I have a legal copy of 2000. I do not own a copy of XP, legal or otherwise. I will not purchase something for the sake of a blog article (sorry, I'm not that rich!), nor will I purchase something that doesn't fit my needs. In the case of XP, this is due to restrictions placed through DRM. If Bill Gates wants a follow-up article putting XP on trial, then I'm willing to accept a copy!

I should also clarify that I'm not comparing W2K with my up-to-date Debian box, per se. (I've had many problems with Debian over the years, but none that seemed as braindead as the ones I noted above.) This is merely to reference the issues I had while using W2K. No truth distortion is present, or should be inferred.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

Why weren't you using Windows XP? You wouldn't have had so many problems if you would just gone with the Windows OS that has the most driver support and larger userbase.

Shame on you for distorting the truth.

 wordspeake's picture
Submitted by wordspeake (not verified) on

My first OS ever--in fact, my first computer ever-- had the pre-installed nightmare called Windows XP. Four years later,the cd player still won't let go of whatever it read before,--reboot--then it screws up Nero--I put that in trying to end the control of the clutching monster-- I constantly have to "re-install" bits of MS Word that mysteriously vanish--always when I need to use it--when else? and having been forced by the DSL IP to install some spyware program--an adware trojan, fortunately picked up by ZA-- that only registers the router and service using IE and active X, I have to boot the piece of MicroSwiss so I can reboot--this time to a sane piece of software, Ubuntu 6.06-- with the connection made. This leaves out all the horrors of backdoor trojans let in by their crappy firewall, two solid days of not being able to work on an important project deadline, trying to recover from the effects of the "Genuine Windows Advantage" that overrode MY Admin rights, disengaged Zone Alarm firewall,(the MS "tech support" dutifully warned me about "third party software" while they put me through the standard MS pablum "fixes") and brought up that ugly blue E browser, which somehow felt it should run no matter how many times I disabled it. Have you ever tried to follow a Microsoft bulletin to anywhere it makes an enlightening,informative,definitive statement? Try doing it as a new computer user. They're so helpful within the system as well--"XML files are of type XML" One enlightening thing XP did for me: It made me look for something else--and in so doing, I realized Microsoft for what they really are.

Ryan Cartwright's picture

My first OS ever--in fact, my first computer ever-- had the pre-installed nightmare called Windows XP.

Boy do I feel old now!

wordspeake's picture
Submitted by wordspeake (not verified) on

Don't sweat it Ryan--would you believe my 20 year old daughter had to first show me the intricate operations of how to use a mouse? What's a mouse?", said I. I resisted learning anything about these diabolical machines until I HAD TO get an email address. Now the hardest thing for me is to admit I was so stubborn. Bet I'm older than you.

Jeffery Hudson's picture

My friend, I would love you to tell you that you just had an unlucky week, but I'd be lying to you if I told you that. :)

How do normal people cope? They don't. If they are lucky, they call a friend/family who is computer literate and let them try to handle the mess. If they are unlucky they do one of three things.

1. They take the machine to a shop to be 'fixed'. It doesn't matter that the machine may or may not be broken, it needs to be 'fixed'. For this privilege they end up spending a few hundred dollars. By the time the machine is returned to them they could have a great down payment on a new machine.

2. Those few smart one's who realize that getting the machine 'fixed' is a waste of time just go out and get a new machine. Then the process starts all over. :)

3. They just give up and do NOTHING with the computer. They live in a world of fear. They know the computer is hopelessly broken but they are too afraid of losing 'valuable' data (like the solitare game that came with that copy of windows) to actually let anyone fix it.

Normal people hate computers. They don't find the same joy in computing that 'geeks' do. It's all to complicated and confusing for them. Every task is a monumental challenge. There is real fear to do anything new. Once past email, word processing, internet, and solitaire the computer world is a truly frightening place. And this is BEFORE trying to get them to run adware/virus protection.

I teach computers for a living. I'm amazed there is a computer industry sometimes. I've been lucky enough to convince a handful of people to try linux and NONE of them have moved back to windows once they have made the full switch. People truly want an alternative to the current computer world but they are to afraid of changing.

Your article points out exaclty why.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

I agree to the extent that I can say nothing else. Except... cheers!

Stephan Gromer's picture

First just for the records, I'd like to point out that while writing this I am actually removing my remaining Windows partition (in fact I removed the complete drive) - I don't like Microsoft and I like their politics even less.

However, comparing a Windows 2000 system with a (presumably) rather recent Debian (or $FAVOURIT*ix) is simply comparing apples and beans.
Even WinXP is now >6 years (oct-2001 in germany) old and 2000 (sep-1997) is even older.
Most of the hardware I used worked fine with Windows XP and in general I had more trouble getting it to work under Linux.
The big advantage is, that - once you HAVE GPL (or other truely FOSS) drivers you are no longer in the vendor trap.
In our laboratory we have e.g. a HPLC-system which runs under Windows NT. It has two proprietary ISA-cards required for comunication with the HPLC. Now, the PC is about to die.
Getting a PC with ISA-slots is already difficult. But unfortunately, the (you guessed it - proprietary) software does not run under Windows XP and only with difficulties under 2000. More recent mainboards do, however, not often work together with Windows NT. Windows NT is not an option as security updates are no longer provided. I was thinking about a virtual machine - but the ISA-cards prevent that. I was thinking about an ISA2USB-converter (which I found), but NT doesn't support USB. So in the end we had to buy a new network box to connect the HPLC via TCP/IP for "only" 2000 Euro. Note that we do not get *any* improvement from a users perspective (if not a deterioration: a network problem is far more difficult to track down) - it is all about updates (software -> security, hardware -> replace brolen parts).
If all the stuff was written as OS we could have adapted the driver to the new machine simply by recompiling ....

Laurie Langham's picture

I recently had a similar reaction after using XP for a few weeks. The wry laughter begins to take on the hard edge of hysteria, as images of M$ executives, hanging from lamp posts, begin to blot out the endless error messages displayed on the screen.

M$ aspires to being a world monopoly, and like every other monopoly it fails all attempts at innovation and treats its customers with complete contempt, by selling them overpriced garbage.

Compare M$ operating systems with the state monopoly Soviet Union's attempts to produce cars.

For years, the non-innovative Soviet Union monopoly simply made poor copies of ancient Italian designs, before inflicting on its long-suffering customers its final overpriced masterpiece; the Trabant.

Non-monopoly Italy, meanwhile, was producing the Ferrari.

For years now, the non-innovative M$ monopoly has been making poor copies of other people's software and selling it as an overpriced, unreliable OS. Now it has inflicted its overpriced masterpiece on its long-suffering customers, that Trabant of operating systems, with the grand title of Vista.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

"A week with an obsolete OS, even more obsolete fs and buggy hardware" would maybe have been a more fair title.
A year 2000 Linux distro with ext2 would be a more or less comparable choice, still good for working on stable and aged hardware, but neither good to deal with big files nor to have good chances with problemathic hardware.
You should have used a 2006/2007 Linux distro on ext3 or ReiserFS as you should have used XP SP2 on NTFS, both OSes with latest patches and drivers.

Mitch Meyran's picture

Using Windows 2000 as a comparison piece is unfair compared with using Windows XP SP2 on a few points:
- XP SP2's kernel makes better use of virtual IRQs; for sound hardware, that's actually much better
- Windows 2000 doesn't deal well with recent ACPI revisions (see above problem).
However, on the whole, the two OSes are pretty much equivalent except there's no DRM crap in Windows 2000. As such, you'd have gotten pretty much as many problems with an XP machine, if not more.
You may have solved your burner troubles by installing the Adaptec SCSI drivers. Yes, you gotta know about that trick.
You may have solved your sound problems with disabling ACPI: setting the kernel as 'Standard PC' disables the use of virtual IRQs, most often source of sound/graphics problems and BSODs with IRQ_NOT_LESS_OR_EQUAL.
The ext3 win32 driver works better with NT5 (Win2k) than NT5.1 (WinXP); it doesn't however work as well as under Linux (no journaling, fragmentation appears faster).
Several softwares use 32-bit addressing to size their output; the file system as such doesn't matter much, as you've seen.
NTFS isn't terra incognita for Linux anymore: a working, final, read/write driver came out a few months ago.
Nero has gotten huge and bloated; get CDburnerXP instead. It looks a lot like k3b.

However, if you can do all your stuff on GNU/Linux, stay there. I did.
A computer is like air conditioning: it becomes useless when you open windows.

leonpmu's picture
Submitted by leonpmu on

You guys are all bleating about XP, the writer has re-iterated that he does not have alegally paid for copy of XP, and will not pay to do so, just for the hell of it.BTW windows 2000 is not circa 97, it is circa '99. As for windows XP being the b all and end all of woes, I am a PC tech, who even has enough hell with my wife's machine running XP adn just for no apparent reason not finding the wireless network after a reboot. Requiring another reboot and more downtime.

I feel your pain, but then, there is no perfect OS. I will say though, that Linux gives awesome log files, so that you generally know what is going wrong. Whereas windows likes to pretend that there is no problem whatsoever.

My only question to our intrepid writer is - did you install service pack 4 for windows 2000?

Steven Goodwin's picture

My only question to our intrepid writer is - did you install service pack 4 for windows 2000?
Yep. SP4 is running on both Windows machines.

As for Windows pretending there is no problem - agreed 100% I wish I'd mentioned that in the article!

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

"You guys are all bleating about XP..."
"BTW windows 2000 is not circa 97, it is circa '99"
"I will say though, that Linux gives awesome log files, so that you generally know what is going wrong."
So, to be fair, please install a 1999 Linux distro, using with EXT2 to be comparable with FAT32, and try to accomplish the same tasks on the same hardware, and if you manage to get it better in that week, spend the rest of the time tracking the marvellous error logs to know exactly what went wrong and why...
Or else, install an up to date Linux or BSD or Solaris or OSX or Windows system, place the data on a decent FS (ReiserFS, EXT3 or even NTFS), spend some bucks to replace buggy hardware, and do the same job in a douple of day, with the remaining day spent to do some other job which will full payback the bucks spent for decent hardware and for a well supported distro (even Suse and RedHat developers eat!)

Terry Hancock's picture

Actually, I was using Debian Linux in late 1999 and early 2000. It was pretty usable.

More to the point, however, seeing as it is 2007, I can legally install the very latest Debian Etch system, whereas the last Windows I have legal title to is Windows 98SE (and that only because it was a gift -- I switched to Linux as soon as I saw Windows 95).

I don't think it's "unfair" to notice this difference, since the organic way in which Linux grows and is supported is one of its many advantages. Part of the problem with Windows is that, unless you are quite wealthy and/or lucky, you are always installing an out-of-date version of it.

Anonymous visitor's picture
Submitted by Anonymous visitor (not verified) on

My Linksys WRK54G router doesnt hold a connection for more than a day when I have a Windoze machine plugged into it, so think yourself lucky! It's probably more Linksys fault than Windoze, but I don't know. PLus the Netgear SC101 *IS* crap - everyone knows it. why did you buy one?

Guy_P's picture
Submitted by Guy_P (not verified) on

I run have windows at work but Ubuntu & PCLinuxOS at home. Give me Linux any day. I have actually just had to use a live Knoppix disc to rescue the XP machine as it is a Dell & doesn't come with the intsall disc that has the 'recovery console' (what a joke that is after a Linux command prompt!).

BTW knoppix worked beautifully on the NTFS file system :0)

Chris Lees's picture
Submitted by Chris Lees (not verified) on

Whenever there is a poll of "What was the best version of Windows", Win 2000 always comes out on top; with people citing its stability, comparative lack of troubles, etc.

Windows 2000 is still supported by the vast majority of software and hardware, and XP is really just some extensions to 2000; so this is really a fair test.

James Brickley's picture
Submitted by James Brickley (not verified) on

I support tens of thousands of Windows systems for a living. I run a mix of Solaris/BSD/Linux and Mac OS X at home because I simply don't want to have to deal with Windows problems at home! I've got one PC running Vista Ultimate merely because I have to learn it and become familiar with it. Personal opinion? Vista is horrid... You're gonna need top of the line hardware just to run it efficiently. Seriously, 1GB of RAM is no longer enough, better to have 3GB's of RAM. There are a few things I like, for example changing "\Documents and Settings" to "\Users" which only makes it more Unix like. The file search is a rip off of Mac OS X Spotlight but is a welcome addition. There are enough serious compatibility problems that Circuit City & FireDog in conjunction with Microsoft are now giving out VirtualPC with a WinXP MSIE6 or WinXP MISE7 virtual image to allow users to run the virtual machine for those applications and websites that do not work with Vista yet.

Your experience is far from unusual even with using the very old Win2k "legal" installation. i.e. I've seen it all. I have to jump through virtual flaming hoops of fire every single day just to accomplish basic tasks. Murphy's Law is enhanced by adding ""Whatever can go wrong will go wrong, and at the worst possible time"! I eat, live, and breath Murphy's Law! It rules Windows like a dark shadowy overlord of evil.

If I could obtain a job paying similar rates to work on Unix/Linux/MacOSX instead of Windows I would jump in a heartbeat! Trouble is, Windows is so very horrible people are willing to pay me enormous amounts of money to fix their broken systems. So I swallow my pride and fix the systems, get paid and laugh all the way to the bank and subsequently the Mercedes dealership.

I have found a variety of open source tools to actually make life much easier.

1. GPartEd - Gnome Partition Editor - Bootable ISO CD image. Supports NTFS, FAT32, EXT3, HFS+, etc., etc., etc. - Does 90% of what Partition Magic can do for free. Create and Resize partitions. Latest build even has Intel Mac support.

2. BartPE - Bootable CD mini-WinXP on a RAM disk. Fantastic for booting a dead system or to get access to the hard disk and have a network connection for backup, etc. . BartPE is a clone of WinPE on steroids. It's much better then WinPE and is free. It comes with a utility to customize your boot cd with the tools of choice. Ton's of plugin tools available, some free some not. It does require having a legal copy of WinXP.

3. DBAN - Derrick's Boot & Nuke - Fantastic secure disk wipe tool. Available as a bootable CD ISO or even a floppy image. Supports DoD 7 Pass wipe and greater.

I wish there were more tools of this caliber that were either free or completely open source. I've got my little bag of tricks which contains a whole lot more but much of it is neither free nor cheap.

mykeyspace's picture
Submitted by mykeyspace on

One week with Windows and you didn't have to reinstall the operating system, or MS Office for that matter? Nice one!

Please don't talk to me about Windows. My nightmares (BSOD's and Fisher Price looks all over the place) were just about over...

BTW: Microsoft still issues patches for Win2000, it's still officially supported and has all the latest software. So how is that not fair comparing it to a Debian system?

Cap'n Kernel's picture
Submitted by Cap'n Kernel (not verified) on

Clearly Win2K gave you a lot of problems with your hardware. But what I'd be more interested to know is whether you consider it to be an unstable system. I used Win98 and WinME before I tried out Win2K, and I found Win2K to be incredibly stable, at any rate when compared to those other two disasters. I never once experienced the BSOD in Win2K (though some people claim that it exists) whereas this was a twice or thrice-daily occurrence in Win98 and WinME. I have no desire or reason to go back to Windows, but in the interests of fairness, I think it should be admitted that Win2K and WinXP are actually quite stable systems (or else, the 3 billion that Microsoft claims it puts in R&D every year would have to be some kind of tax dodge).

Author information

Steven Goodwin's picture


When builders go down to the pub they talk about football. Presumably therefore, when footballers go down to the pub they talk about builders! When Steven Goodwin goes down the pub he doesn’t talk about football. Or builders. He talks about computers. Constantly...

He is also known as the angry man of open source.

Steven Goodwin a blog that no one reads that, and a beer podcast that no one listens to :)