Siemens washer with F-18 error

So, I have this washingmachine from Siemens. It’s been going steadily for a few years, working as if should, washing all my clothes. Then suddenly I hear it make a totally new sound I’ve never heard before. I rush out to the machine, and the display says F-18. I’m stading there, staring at my big, clumpy, washing-companion, trying to make sense of the situation.

The first thing that springs to mind is of course to check the manual. But where do you place manuals for these monstermachines? I for one have a habit of placing them someplace clever, then forget about them and never find them again. After a while I give up, and being who I am, the next step in any quest if to google it. Appearently, Siemens washing machine error messages isn’t the most commonly commented piece of information on the internet. Finally I find an old forum post from 2008, saying this message means a blockage of the pumping mechanism. I loosen the panel and twist out the plug, the washer appearently still full of water… The water floods out on the floor, but I manage to plug the drain again. I prepare myself to try again with towels all over the floor. Once more I pull the plug out and the water is flowing like a waterfall. After 5 towels the water finally stops.

I check the fan-thingy inside where the water was comming, only to find nothing. NOTHING! There’s nothing blocking the pumping mechanism… What to do? Well, I think, lets try it again! I run the program once more, everything running fine, untill there’s one minute left on the counter. The same odd sound I heard the last time I ran it. “Beep Beep Beep”, and F-18.

Once more I drain the pump, spending another 5 towels, witch are now starting to pile up in the shower. The water stops flowing, and now the closet is empty and I have no more dry towels. Once again I try to run it. It works! Everything went fine and the program ended with the regular “Beep Beep”.

A few days later, thinking nothing more of it for the past days, I hear the dreaded “Beep Beep Beep” again! Now I’m getting angry, running into the bathroom, ripping out the drain plug and draining the machine! And then it works again…

It’s now been running fine for a few days, but this time, I can’t forget it. Everytime the machine starts to run, I sit in front of it, just waiting for the beeps, having to fill the bathroom floor with towels, dreading the next time I have to get all wet and angry cause I can’t figure out what generates the error. Bottom line is, I’m starting to hate washingmachines…

Live Messenger 2011 error

So, I use MSN Live Messenger a lot at work, and everything works ok there. I also use MSN Live Messenger 2011 on my laptop at home. A few months ago I got a new laptop and and installed Live Messenger on it. Everything worked just the way it was supposed to. Then suddenly, I started getting the error like the one in the picture below. Error code: 80040154

The weird thing is, it doesn’t seem to try to connect at all. It just shows the errormessage the second I press the login button. So, I pressed the “More information” link, witch led me to this site:

This site tells me that I need to register msxml3.dll again. So, I follow the steps, and it says the file is registered and everything should be fine.

Well, same error again. So, I try uninstalling/installing the whole Live Essentials package, same error. I’ve searched around the internett trying to find other people with the same problem, but I can’t seem to find anyone who has it.

Now, after a bit of research, trying to remeber what I myself did around the time this time, and the only think I can think about must be that I changed the time-zone on the laptop. I had changed the clock, but not the timezone. So the clock on my iPhone changed like 6 hours back and Google Calendar entries in Outlook popped ut at wrong times. After I figured out this was related to wrong timezone, I changed the timezone. This must have been around the same time as my Messenger problems started.

The problem is, I can’t remember witch timezone used to be set before, so I can’t confirm that this is the source of the problem. As a workaround I’ve just started using Pidgin instead… But, would be nice if someone had a solution/could at least confirm that this was the problem.