btnh47
New Head-Fier
- Joined
- Nov 15, 2008
- Posts
- 44
- Likes
- 0
just did a quick check on my zune out of curiosity...
and.. yep..its workin :]
and.. yep..its workin :]
**30Gb Zune? Go ahead - Switch it on!**
- Thread starter daglesj
- Start date
rossboy
Head-Fier
- Joined
- May 22, 2008
- Posts
- 54
- Likes
- 10
It's ALIVE. Just in time for bed.
Blue Meanie
100+ Head-Fier
- Joined
- Oct 28, 2003
- Posts
- 281
- Likes
- 12
Quote:
Well, we won't know if it works until 12 NOON GMT (2 hours from now).
| Originally Posted by qusp /img/forum/go_quote.gif anyway I just wanted to see if any had 'self healed' but since over half of the world is in the new year now, and nobody has posted happy post yet. I wonder if it really happens. |
Well, we won't know if it works until 12 NOON GMT (2 hours from now).
Kicksonrt66
Head-Fier
- Joined
- Nov 23, 2008
- Posts
- 99
- Likes
- 0
Quote:
Some of the articles I read said they died at midnight pacific (ie Redmond) time. Does the setup have a timezone setting so internally the time is pacific (like computers keep internal at GMT)?
| Originally Posted by Blue Meanie /img/forum/go_quote.gif Well, we won't know if it works until 12 NOON GMT (2 hours from now).
|
Some of the articles I read said they died at midnight pacific (ie Redmond) time. Does the setup have a timezone setting so internally the time is pacific (like computers keep internal at GMT)?
daglesj
100+ Head-Fier
- Joined
- Dec 7, 2008
- Posts
- 176
- Likes
- 11
As of 12.14pm Mine is up and runnin'!
Yeah!!!!!
Yeah!!!!!
krmathis
Head-Fi's Most Prolific Poster
- Joined
- Jan 13, 2004
- Posts
- 34,759
- Likes
- 82
Great to hear that they are coming to life again.
Earwax
Headphoneus Supremus
- Joined
- Aug 31, 2003
- Posts
- 2,319
- Likes
- 14
I never turned mine on yesterday at all. Turned it on just now and it is working.
Drag0n
Headphoneus Supremus
- Joined
- Jun 11, 2004
- Posts
- 3,706
- Likes
- 16
I have 2 Z30's, and i havent used them in like 2 weeks maybe....turned them on like half an hour ago, and its fine.
When i saw the thread on this site about it, i waited before turning mine on, and now that its after the problematic period, they turned on just fine.
When i saw the thread on this site about it, i waited before turning mine on, and now that its after the problematic period, they turned on just fine.
Bullseye
Headphoneus Supremus
- Joined
- Nov 25, 2008
- Posts
- 2,075
- Likes
- 13
Leap year
nsx_23
Headphoneus Supremus
- Joined
- Aug 24, 2005
- Posts
- 5,000
- Likes
- 11
Hmm, this problem is apparently affecting the Toshiba S-series as well.
I hope to hell that the S60 I'd hope to be getting sometime soon isn't affected......
I hope to hell that the S60 I'd hope to be getting sometime soon isn't affected......
mypasswordis
Member of the Trade: Corsonus
- Joined
- Jan 23, 2006
- Posts
- 1,802
- Likes
- 34
It's a day or two once every 4 years. Not really all that bad.
nismo96
500+ Head-Fier
- Joined
- Jul 12, 2003
- Posts
- 842
- Likes
- 10
MS has already committed to releasing a firmware update that will address the leap year issue. There shouldn't be another occurrence of this issue for Zune users. I am not so sure that Toshiba S-series owners will have the same luck.
krmathis
Head-Fi's Most Prolific Poster
- Joined
- Jan 13, 2004
- Posts
- 34,759
- Likes
- 82
Quote:
Not all that bad.
But a company of Microsoft's caliber should not slip such an bug through.
| Originally Posted by mypasswordis /img/forum/go_quote.gif It's a day or two once every 4 years. Not really all that bad. |
Not all that bad.
But a company of Microsoft's caliber should not slip such an bug through.
nsx_23
Headphoneus Supremus
- Joined
- Aug 24, 2005
- Posts
- 5,000
- Likes
- 11
I just hope Toshiba pulls through.
ericj
Headphoneus Supremus
- Joined
- Aug 2, 2005
- Posts
- 8,270
- Likes
- 170
Actually, it's not Toshiba's bug either. It's Freescale's bug.
Whch means that there's a very good chance that the man responsible for the bug is a former coworker of mine. But I'll never tell if it is.
And it's actually more likely that it's the fault of some long gone and forgotten 22 year old programmer in beijing, from what I hear of freescale's hiring practices over the last 6 years.
It's a rookie mistake - and freescale's kernel team consists of a bunch of suspendered old unix geeks (who i used to work with, before they were part of freescale) in the US working in conjunction with wet-behind-the-ears, just-out-of-college, never-wrote-a-driver-in-their-life chinese programmers who never stick around for long. A lot of whom, I'm told, are very smart guys - just with zero experience and low pay.
One of my old friends over there left in large part because he realized that all he was doing was teaching young chinese guys how to write device drivers, and every 3 months the guy he'd been teaching would quit and get a better job, and he'd have to teach a new one.
Moreover, it's a failure in QA.
Which isn't specifically the fault of programmers. From a QA perspective, it's nice if coders unit test their code, but all coders produce buggy code. The only differences among them are how many they produce and how much they realize that they need another set of eyes on the product. And believe me, my friends at Freescale wish they had a real QA team in house. And they don't. And that's not their fault. I'd work with those guys again in a heartbeat - but their bosses aint hiring.
Microsoft takes some blame for not taking advantage of their own QA team, and so does Toshiba. Obviously the leapyear rollover condition was never tested. The rule in QA is outwardly "trust but verify" - and inwardly it's "verify. Don't trust."
I could go on about the state of quality control in the software industry, but it gets boring and preachy.
Whch means that there's a very good chance that the man responsible for the bug is a former coworker of mine. But I'll never tell if it is.
And it's actually more likely that it's the fault of some long gone and forgotten 22 year old programmer in beijing, from what I hear of freescale's hiring practices over the last 6 years.
It's a rookie mistake - and freescale's kernel team consists of a bunch of suspendered old unix geeks (who i used to work with, before they were part of freescale) in the US working in conjunction with wet-behind-the-ears, just-out-of-college, never-wrote-a-driver-in-their-life chinese programmers who never stick around for long. A lot of whom, I'm told, are very smart guys - just with zero experience and low pay.
One of my old friends over there left in large part because he realized that all he was doing was teaching young chinese guys how to write device drivers, and every 3 months the guy he'd been teaching would quit and get a better job, and he'd have to teach a new one.
Moreover, it's a failure in QA.
Which isn't specifically the fault of programmers. From a QA perspective, it's nice if coders unit test their code, but all coders produce buggy code. The only differences among them are how many they produce and how much they realize that they need another set of eyes on the product. And believe me, my friends at Freescale wish they had a real QA team in house. And they don't. And that's not their fault. I'd work with those guys again in a heartbeat - but their bosses aint hiring.
Microsoft takes some blame for not taking advantage of their own QA team, and so does Toshiba. Obviously the leapyear rollover condition was never tested. The rule in QA is outwardly "trust but verify" - and inwardly it's "verify. Don't trust."
I could go on about the state of quality control in the software industry, but it gets boring and preachy.
Users who are viewing this thread
