I fear blogging has fallen by the wayside thanks to a variety of other draws on my time. But I can still post my new Christmas desktop for the holiday season.
Photograph from Pixabay.
I don’t even remember making this decision, but I recently discovered my motherboard’s storage controller was set to RAID for my SSD and spindle hard drive. I was trying to see how much life was left on my SSD after seeing a friendly reminder on Reddit. But SSDLife couldn’t see either drive. They were hidden behind a RAID configuration I didn’t even want.
When I switched from RAID to AHCI in the BIOS, Windows 7 wouldn’t boot. Fortunately, changing it back to RAID fixed that.
If you can believe it, I fixed the not-booting issue with two lines. They were registry edits I found on Microsoft’s answers site.
Here they are:
REG ADD HKLM\System\CurrentControlSet\Services\msahci /v Start /d 0 /f /t REG_DWORD
REG ADD HKLM\System\CurrentControlSet\Services\atapi /v Start /d 0 /f /t REG_DWORD
I’ve heard people claim commands like these are magic. I know better than to make that claim myself, but I have to admit, going from not booting to a fully working system without RAID enabled felt magic. I love it when a plan comes together.
It could be my imagination, but even after a day of having switched over to AHCI, the SSD and the spindle drive both feel much snappier. I didn’t run any benchmarks, but everything on my system feels lighter and faster. I like it.
And the good news is, at least according to SSDLife, my SSD has another 8 years left (taken with a large grain of salt of course).
I was surprised to see it’s only been powered on 58 times in 5 years. That’s probably due to monthly Windows updates reboots. Windows reliability has come a long way.
The falling snow blends so much with the background it’s hard to even tell it’s there.
The price began another ascent when the list reached 5,000 subscribers. It leveled off at $75/month and I was somewhat okay with that.
In the past few months I’ve been going up the third staircase. It’s longer and steeper than the first two and it’s painful. Every 200 subscribers adds $5/month, and I was heading for $150/month. Halfway up the staircase, I was no longer okay with it. I couldn’t justify paying $150/month to send out a monthly newsletter.
So I began my search through nearly a dozen alternatives, and last month my search ended at EmailOctopus, which uses Amazon SES behind the scenes. I will be paying $35/month until I reach 100,000 subscribers. That would have cost me $500/month with Mailchimp.
If anyone from Mailchimp comes across this, my suggestion would be to stop the $5 bump for every 200 subscribers. It’s frustrating and feels unfair when you’ve been adding thousands of subscribers and remained at the same price. I felt like I was being punished every time I bumped up a step. The 10% discount for enabling two-factor authentication was appreciated, but not enough.
Instead, keep it simple:
5,000 subscribers = $50
10,000 subscribers = $75
25,000 subscribers = $150
Now that I have a successful campaign under my belt, I am pleased to report that my first campaign with EmailOctopus had similar click and open rates as Mailchimp (even higher on open rates). The higher open rate could have been due to the new email template I used, but at least I know deliverability isn’t suffering with Amazon SES.
The migration was painless. I exported the list from Mailchimp, imported it into EmailOctopus and requested Amazon increase my sending limit, which they did in a matter of hours. It was also simple to enable DKIM on the domain in Amazon SES.
EmailOctopus doesn’t have as many features as Mailchimp, but they have the essentials that I use, like autoresponders, scheduled campaigns, subscription forms, unsubscribe support and campaign analytics. Plus they’re adding new features. Since I created my account they’ve added email templates and two-factor authentication. Their customer support has also been responsive and helpful.
And I love the price!
Ever since Windows 10 came out, my Windows 7 updates have gotten really slow. It started taking days instead of minutes or hours to run, with no end in sight. And the whole time it was cranking my CPU fan and still stuck at 0%.
My first solution was to disable Windows Updates and use WSUS Offline Update instead. I would follow these steps:
This worked until recently, when Microsoft started using an all-in-one update instead of piecemeal. When I tried WSUS Offline Update, it just failed.
Back to the drawing board, I discovered Woody Leonhard’s InfoWorld article on this very topic, and his solution worked!
I don’t use Bluetooth on my desktop, but you should be aware that’s still a potential pitfall.
Otherwise, here’s the process I used to get Windows Updates working in minutes instead of days:
This issue has plagued me for months now. It’s quite satisfying to have finally found a solution. If you’ve had the same problem, I hope this works for you too.