|written by Alex on Dec 08, 2010 08:01|
|This was fun...|
it's so broken that it could send me a warning message.
Reminds me of "keyboard error - press F1 to continue".
However, it's just because it had been broken a few hours ago, it simply kept complaining until I voided the log.
|written by Megagun on Dec 08, 2010 20:48|
|Well, it does say "might".. |
|written by Alex on Dec 08, 2010 21:17|
But it had me chuckle anyway. :p
don't say it too loud, but I begin to get fond of Linux
|written by Speeder on Dec 08, 2010 21:19|
|I just remembered of the most stupid problem in a Mac... People say that Macs never break, but this is proof that sometimes Mac is more crap than windows.|
I worked making iPhone games in a company, my station had a new mac (I even had to wait week for it to arrive), but one month later the Mac stopped working, having several defects.
I went to research on internet, and found that ALL errors in apple software are logged in the same log, including errors that your code generate in the iPhone emulator and some other things, and that the log probably was full, and thus making software fail to write on the log, thus making errors generate more errors.
I opened the log, and it was like:
"bunch of errors"
and nearly half of the log messages was a error about the log being full... the log file actually had already 3 times the size it was supposed to have...
Solution from Apple: Clean the log... and t hat is it, if it happens again, you have to clean it again, there are no solution :/
|written by Alex on Dec 08, 2010 21:27|
|So the Mac did also lie to you: the log was not full, as it kept accumulating "log full" notices.|
Windows API, on its side, has an immense number of different ways to tell you when a function was successful or failed, and I think it might be what gets sometimes misunderstood by developers, resulting in the emblematic "error: the operation completed successfully".
|written by Speeder on Dec 08, 2010 21:31|
|Or, error: error.|
Or error: internal error (fireworks do this a lot).
Or the most bizarre of all:
"Catastrophic Error" (from MS Word). I wonder how in bad mood the programmer that made that message was
I visit TheDailyWtf just to see all the screenshot of silly error messages (the most funny one EVER was that the Windows Vista installer when finding a eror actually blamed the software that caused the error, but the error was caused by windows itself, so the installer wrote: "Error caused by Microsoft, please contact them." or something like that. The author said it was the first time windows has been honest