Dec 15 2009
When software just doesn’t work, what do you do?
I recently purchased a modestly expensive software package for my Mac. It won’t take much hunting on my blogs recent posts to figure out what that application is.
However, it’s simply still not working. I was promised an impending update (which I patiently waited numerous weeks for) would fix the issue, but it didn’t. I was them promised that another point-release would fix the issue, which it didn’t. If anything, it made it worse - the software crashes hours into it’s task now, instead of days in.
Either way, all cumulative work done up to that point is effectively lost each and every time it fails. We’re talking in excess of 100-150 hours of consistent processing and bandwidth consumption.
So what do I do? If I purchased the software at retail I’d probably shove it all back in the box and return it to the retail location. But alas, I purchased this software online.
So, I requested that the developer rescind my activation key and process a refund. I don’t think that asking for a refund on an application that isn’t working as advertised is out of the realm of fair. Clearly this software doesn’t work for me, and likely isn’t going to anytime soon, so it holds zero value for me at this point - I won’t continue to attempt to use something that is broken, especially when I have something so critical and time-consuming involved with it’s use.
However, now the developer is blaming the failures on my FTP host. Failing that, it’s my computer - not enough memory, or two large of a set of source files.
Requirements for excessively gross amounts of system memory, or limitations on the size of source files I could use were not disclosed. My hardware is maxed out on memory, and the suggestion that my source files are too large (when in reality others are likely to attempt MUCH larger amounts) seems asinine.
And in the end, my polite (at this point) request for a refund is being denied.
What do I do?