A couple of days before Christmas I bought a new laptop. It came with Windows 8.1 preinstalled. I'm not a big Windows fan and would ditch it all together were it not for Netflix and a couple of other minor "deal-killers" (
such as being able to connect to my cell phone.) So, I normally install some flavor of Linux alongside Windows so I can switch back and forth as needed. I personally prefer Ubuntu and use that as my main OS, which means I do everything in Ubuntu - edit videos, play music, manage personal records, spreadsheets, etc. Anyway my Christmas holidays went something like this: installing Ubuntu next to Windows, deleting Windows and installing only Ubuntu, deleting Ubuntu and installing only Windows, installing Ubuntu and Windows together again. After much trial and error I got a somewhat stable setup going. The only problem was the laptop wouldn't boot unless I pressed F2 and went into the BIOS settings. (BTW, It didn't matter whether I saved any changes to the BIOS, or exited without saving.) Only then would the boot process continue. However if I simply rebooted the computer it would work perfectly. It was only when the computer was shut down (turned off) that I would encounter the boot issue the next time it was started. The last thing I had done during the whole installation/update process, during which the computer seemed to work fine (because it was only "restarting"), was to install a video editing program and then turned the computer off for the night. It wasn't until the next day that I discovered the boot issue. So, my logic went like this: computer seemed to work fine, installed a program, computer didn't work fine. Problem must be the program. I was about to send "hate mail" to the program developer when, for whatever reason, I unplugged my USB Modem during startup and the computer started normally. I turned the computer off, plugged the Modem back in, hit the power button, and no boot. After various repetitions of this I realized it's the Modem. The BIOS sees it as a boot device even though the hard drive is listed first. I'm glad I didn't send that email to the programmer.
I ran out of both coffee and coffee filters at the same time. The next time I was at the store I picked up some coffee (Organic Mexican Dark) but forgot to get any filters. Since I use a percolator, filters aren't necessary but they do make clean up much easier. Anyway, the next morning I loaded up the percolator with freshly ground coffee (sans filter) and let it rip. It sucked. The coffee that came out was horribly weak. I've used this brand quite often and never had it come out looking like tea. After several more attempts I concluded it must be a bad batch - wasn't roasted properly, or too old perhaps. A week later I got a different strain (Ethiopian Dark) of the same brand. It too, sucked. I had used the Ethiopian only a couple of weeks before and it had been deliciously strong and bold. What gives? Must have been a bad shipment, not batch. Finally, while grocery shopping I remembered to get some filters (unbleached of course) and bought a completely different brand of beans. So, this morning I popped a filter into the percolator's basket, but was too lazy to drag out the grinder so I used some of the left over shitty stuff from yesterday. This time it came out looking like tar - the stuff a truck driver would be proud of. The only difference between yesterday and today was the addition of a filter. Why does using a filter make the coffee stronger? I can only guess that it traps more water and slows down the drip-time (I just made up that word) allowing the coffee to steep longer. Although this doesn't seem logical with a percolator (since the water continuously recycles through the grounds) it does seem to be true. Now my faith in my favorite brand has been restored and it didn't involve a USB Modem this time.