The error continued.
I went to the website.
Searching for the error code, I found the "solution" was to
call an 800-number.
I called that 800-number. (I must admit, the hold music was
pretty enjoyable: various themes from the Zelda universe.)
I was finally connected with David. He was very pleasant,
but wouldn't be able to fix my issue himself. He needed to open a ticket with
the tech department. They would contact me within the next 1 to 2 business
days.
Later that same day, I received an email. It had a different
number to call.
I called that different number.
I was eventually connected with Casey. He asked for my
reference number, which I provided, and then for the error code, which I also
provided. (Though, I had expected that information to already be available to
him, as he was, presumably, looking at my incident ticket at that point in
time.)
He looked up the code and then proceeded to explain what
this error means and how to "fix" it. He explained that some files
had gotten corrupted and that this can often happen when people illegally
modify their systems.
He asked if I had made such modifications.
I said that I
had not (which, by the way, is the truth, though I suspect that question is
fairly universally answered in the negative).
He then proceeded to explain
"the solution": formatting the memory.
"This may result in the loss of data." (Uhm... not
so much "may" if I'm doing a format.)
Playing dumb, I asked, "What about the files that I
cannot move to the SD card?"
As expected, he indicated that those would be lost.
I wish I had a transcript of the conversation because I
don't recall exactly when, but he did mention that this error is typically a
result of people illegally modifying the system. That's all well and good... if
I had modified my system, but, since I hadn't, the karmic slap in the face seems unwarranted.
Basically, I’m being accused of breaking the rules and then
I’m going to lose all my data. Wow, way to make me feel like a valuable
customer.
Epilogue: We later reattempted the download, and it worked. So, we haven't lost any data yet, but I'm fearful that there is a lingering problem that could rear its head at any moment.
No comments:
Post a Comment