Safari 3: “cannot decode raw data” (NSURLErrorDomain:-1015)
To fix, I went to Safari -> Reset Safari and all is happy now
Labels: Annoyances, Mac OS X, MacBook, Software
It just is
Labels: Annoyances, Mac OS X, MacBook, Software
Labels: Annoyances, Computers, Internet, Philosophy, Software, WTF
Labels: Annoyances, Computers, Humor, Internet, Philosophy, Software, WTF
Labels: Annoyances, Computers, Internet, Software, WTF
Labels: Annoyances, Internet, Mac OS X, MacBook, Software
Labels: Computers, Hardware, Philosophy, Physics, Software, WTF
Labels: Annoyances, Software
One of the publication's writers replicated the chat Monday. After declining the writer's repeated invitations to eat pizza, a frustrated Santa burst out with, "You want me to eat what?!? It's fun to talk about oral sex, but I want to chat about something else."
Sohn said Santa's lewd comment was sparked by someone "pushing this thing to make it do things it wasn't supposed to do."
Now, if that isn't the response of a developer, I don't know what is.
Hello Kevin,I replaced the person's name with "xxx xxx" to respect the employees privacy. But yes, there is a real explanation to why the software crashed! I have now reconfigured the program to point to a local directory on my laptop and thanks to the outstanding humanized support I got, I am one happy customer. Oh, by-the-way, did I mention that Enso is free? Or at least the beta product is free. I didn't realize that there was a commercial product available, but now that I just found that out, I'm marching over right now to purchase their non-beta product Enso Launcher.
Sorry Enso crashed for you. Thanks for reporting the bug. Enso needs to have access to your "My Documents" directory, because it stores its "learn as open" targets in a directory inside that one. It looks like your "My Documents" directory is on a network share (also known as a file server). Is that the case? If so, then if the network share is unavailable at the time that Enso tries to start up, this kind of crash will be the result. Some users have reported that restarting the server which hosts the network share fixes the problem. You might ask your network administrator to try doing this. In the long run, we need to fix Enso so that it won't crash in this situation, but will just quietly keep trying to read the directory until the network share becomes available. In the meantime, I'm afraid there's not much that you can do about the problem. Changing "My Documents" to point at a local directory on your hard drive would fix it, but I understand that this might not be an option for you.
Once again, I'm sorry for the inconvenience.
xxx xxx, Humanized, Inc.