A few years ago I got sucked into GoDaddy’s low prices and (seemingly) cohesive capabilities across a wide technology spectrum. For the better part of a year, however, I’ve been reminded of the maxim, “You get what you pay for.”
I finally gave GoDaddy the boot, and I’m already pleased with the results. I wish I had enough time to recount all the GoDaddy-induced pain, but I just don’t. A few quick points:
- Customer Service was terrible. Yes, I received the “we promise to respond within 24 hours” email, but I frequently had to reply back (days later) asking, “what’s the status of this issue?” Of course I’m not privy to GoDaddy’s inner workings, but I am left with the impression that SOP is to do nothing until the customer makes a reminder contact (calls by phone, send an email, etc.)
- Charged more for less. It’s still hard for me to believe, but it’s true. I hosted 2 WordPress blogs with GoDaddy. One was measurably faster even though it contained less content and used fewer plug-ins, etc. Unfortunately, it is also the less important blog. After demonstrating (with measured results) that one was slower than the other, GoDaddy said there was nothing they could do about it. If I were to upgrade to the next package level (Economy to Deluxe if memory serves), performance would improve substantially. “Sucker” is now emblazoned on my forehead. I continued to measure the performance of my more important (and now more powerfully hosted) blog. There was absolutely no change (other than the amount GoDaddy charged me). I disabled WordPress plug-ins and did everything I could to give GoDaddy’s host server the opportunity to deliver the promised performance. Nada.
- WordPress Upgradability – During the tenure of my blogs at GoDaddy, there have been at least a half-dozen upgrades to the WordPress platform. I can only remember one of the dozen working correctly (2 blogs x half-dozen upgrades = ~dozen total). GoDaddy’s Customer Support personnel blame WordPress. But when I talk to other bloggers, their upgrade from 3.0 to 3.1 (or whatever) is flawless. We take the same steps; their blogs (not on GoDaddy) upgrade; mine don’t.
Have I already written that much? I really didn’t want to spend much time on this topic, but my fingers just couldn’t hold back. Frustrating!
Ok. Take a breath; think positive thoughts. I’m moving on now. Good riddance!
Since “upgrading” to the 4.0.6 release VirtualBox for 64-bit Windows, it has begun resetting guest VMs randomly. The VM I’ve been using most frequently is Windows Server 2008 R2 x64 with SQL Server 2008 R2 x64 and Visual Studio 2010.
Sometimes VBox doesn’t reset the VM. But when I shutdown the VM (from inside or outside the guest), the shutdown process seems to hang and something just spins CPU at about 50%
I’m experiencing this multiple times per day, so I’ll probably have to revert to 4.0.4. Here’s the Windows Error Fault Details from the most recent reset:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Files that help describe the problem:
Read our privacy statement online:
If the online privacy statement is not available, please read our privacy statement offline:
I have also attached the Windows Error Report xml file (https://altamodatech.com/blogs/wp-content/uploads/2011/05/WER-77593-0.sysdata.txt)
Everyone’s pretty excited about Amazon’s MP3 Cloud Player with 5 GB of Cloud Drive space. I downloaded the Android version to my HTC Incredible as soon as I could. The concept is great – buy music from any device (just about) and play it from any device (just about). Do you really need an iTunes app anymore?
Amazon’s announcement came along with some disappointing and exciting caveats. Disappointing: If you previously bought MP3 music from Amazon, it doesn’t show up in your Cloud Drive, and there’s no handy option on the Cloud Player site to move it there. Exciting: You can use the Amazon MP3 Uploader tool to (wait for it…) upload MP3s to your Cloud Drive! So, you can manually copy previously purchased (from Amazon or elsewhere) to your Cloud Drive and use it from your various Cloud Players.
Well, in theory anyway. I’ve tried to upload MP3 files using version 1.0.1 of the Amazon MP3 Uploader, but it doesn’t actually upload any files. So, exciting becomes Disappointing! The application (which is based on Adobe AIR) either hangs or crashes. In the past 24 hours I’ve experienced 3 hangs and 2 crashes. The more recent crash dump was:
1 Problem signature:
2 Problem Event Name: APPCRASH
3 Application Name: Amazon MP3 Uploader.exe
4 Application Version: 0.0.0.0
5 Application Timestamp: 4ca30b7b
6 Fault Module Name: Adobe AIR.dll
7 Fault Module Version: 220.127.116.1120
8 Fault Module Timestamp: 4d7a8071
9 Exception Code: c0000005
10 Exception Offset: 001fe2db
11 OS Version: 6.1.7601.2.1.0.256.4
12 Locale ID: 1033
13 Additional Information 1: 0a9e
14 Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
15 Additional Information 3: 0a9e
16 Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
18 Read our privacy statement online:
21 If the online privacy statement is not available, please read our privacy statement offline:
BTW, I started out trying to upload a bunch of files, but after the first hang I’ve just tried to upload 1 or 2 files. I’m using Windows 7 32-bit with SP1. I’ve launched the uploader app from both IE9 and Firefox 3.6.16. AIR seems to be up-to-date (see Fault Module Version).