Not much of one, but it is xmas...
-
I wouldn't have thought sites such as Orange.co.uk would have the man power to remove out-of-date items from there website by now, or at least have a default message if they have been accidentally left on.
As another WTF, I've just heard on the radio of a certain shopping center saying "We are open until Midnight on Christmas eve, so there still plenty of time to get your christmas presents"... Delayed advert perhaps?
-
I've seen the following on a couple of occasions -- once in Firefox's download window, and once on a server-side script output:
Just took me ages to find that screenshot; I don't know where the latter one is.
-
-
I never get such things. :(
Software always works when I'm around.
-
I've got a couple still showing a transfer speed for a file that's finished downloading, Future Shop saying my city is located in NULL, a 72-day 15090068x15090068 video in 646KB, pretty standard stuff. http://img526.imageshack.us/img526/3220/hwbug.jpg is one of my best "ridiculously wrong statistic" errors. The actual percentage should be around 81%, if the count were accurate - but I know for a fact that file has far less than 81% empty space.
http://img23.imageshack.us/img23/8359/implode.gif is a good one as well, I'm not sure where I got it. Could've been here; can't remember.
http://img109.imageshack.us/img109/2053/japanese.png is one of my favourites. Google looked at all the Hangul and instances of the word "Korea" and concluded that the page must be written in Japanese. Nevermind the total lack of any Japanese characters. (The English and Korean, not being Japanese, has been passed through untouched.)
(Incidentally, I didn't even notice the "picture of female breasts" link until just now, nor do I remember what in the heck I was looking for to come across this... PSP stuff I think?)
http://img695.imageshack.us/img695/6678/kluploadextra.pngAhh, that takes me back. Pretty good song too.
http://img695.imageshack.us/img695/9497/lastlogin.jpg I have no idea what that's supposed to be. Expecting a 2-digit year in the formatting string? Y2.005K? Obscure Japanese date format?
Anyway, I should do something...
-
until Until enableJavaScript=
What?! Until enableJavaScript=what?!
-
@dhromed said:
Software always works when I'm around.
Are you willing to relocate to Canada? I will pay you to just sit around the office and make software work.
--- Mr. DOS
-
@Mr. DOS said:
@dhromed said:
Software always works when I'm around.
Are you willing to relocate to Canada? I will pay you to just sit around the office and make software work.
--- Mr. DOS
I am the anti-gabe, I think.
-
Seeing all these negative numbers reminds me of the bad old days (this is going back 10 years) working in a music studio of what was then state of the art G3 macs. I wish I'd taken screenshots - back then they didn't cope too well with estimating time transfers from CD drives. Yes it took forever to import a CD full of aiffs but one of mine threw up an estimate of a few million years before finally settling on a calculation. Macs were kinda prone to either doing that or giving you the epoch as the current date, or the makers birthday or something.
Once we got a tape backup we abused it to transfer data between studios, because 6xCDs was taking us an average of an hour or more. Maybe it wasn't wrong in estimating a million years.
-
@Nyquist said:
Macs were kinda prone to either doing that or giving you the epoch as the current date, or the makers birthday or something.
The Classic Mac epoch was Jan 1, 1904. IIRC, it's not 1900, because that one saves an operation when calculating leap-years. (At least for the next 200 years.)
Also IIRC, it's also notable for storing the year as a separate (16-bit) int, so that Mac Classic could store a file creation date of 32000 B.C or 32000 A.D.I always joked that Apple did that so they could use it to power the time machine they're working on. (Although I suppose it would be interesting to make a "Historical Events" database using the native DateTime type.
More pointless trivia, the Mac epoch also explains this Microsoft KB article: http://support.microsoft.com/kb/180162
