Not to point out the obvious... but... how come they don't have a problem with/. using the Apple logo in their image list when they have a problem with the t.o?
Also.... why can't the author of said themes just.. oh... idunno... reverse the logo, or change the color, or alter it some other way so it RESEMBLES the original log? (Might be funnier, anyway...;)
Y2K hit our little computer crew without incident (we service the computers for the Physics Dept. here at the U of A). We watched the clocks roll over and nothing happenned. We knew it would be this way, since we had prepared for it.
Then, two weeks later (now, 1/11/00) we go to reclone one of the Windows labs. On 7 of the 21 machines we get errors in Netscape saying our encryption keys have expired. A quick check of the date revealed the computer thinking it was 2094.
Curious.
Rebooting and fixing the date in BIOS made them recognize the correct date.... untill the system was rebooted again... when the date would promptly switch back to 2094.
We updated the flash BIOS on one test machine... which fried the machine (now it wont even boot). So, we've had to hang our heads low and yank the 7 computers from the lab till we get replacement montherboards. Sigh....
So, we did have one fairly bad Y2K glitch..... it just took a week to happen!;)
AAGGHH! MY ANSWERING MACHINE CRASHED!
on
Apocalypse Not
·
· Score: 1
I actually did have a Y2K problem.... my home Answering Machine's time/date stamp has been stuck at 11:59pm, Fri., Dec. 31st since the new year.
It's not a big problem.... the thing still works... it just gives incorrect time/dates for people calling my home...
Slashdot Mirror
Also.... why can't the author of said themes just.. oh... idunno... reverse the logo, or change the color, or alter it some other way so it RESEMBLES the original log? (Might be funnier, anyway... ;)
Y2K hit our little computer crew without incident (we service the computers for the Physics Dept. here at the U of A). We watched the clocks roll over and nothing happenned. We knew it would be this way, since we had prepared for it.
Then, two weeks later (now, 1/11/00) we go to reclone one of the Windows labs. On 7 of the 21 machines we get errors in Netscape saying our encryption keys have expired. A quick check of the date revealed the computer thinking it was 2094.
Curious.
Rebooting and fixing the date in BIOS made them recognize the correct date.... untill the system was rebooted again... when the date would promptly switch back to 2094.
We updated the flash BIOS on one test machine... which fried the machine (now it wont even boot). So, we've had to hang our heads low and yank the 7 computers from the lab till we get replacement montherboards. Sigh....
So, we did have one fairly bad Y2K glitch..... it just took a week to happen! ;)
It's not a big problem.... the thing still works... it just gives incorrect time/dates for people calling my home...
---
Sam"Criswel"Hart
The Officious Strenua Inertia Web Site