Well, here's an interesting twist to this story. That mysterious and completely enraging "
Zune bug" that cropped up on the final day of 2008 may not have been restricted to Microsoft PMPs. A much smaller cadre of Toshiba
Gigabeat users reportedly experienced similar issues, and some even noted that the whole "discharge and re-date" rigmarole fixed their unit right up as well. Upon further investigation, it seems that the issue may actually reside in the Freescale MC13783 processor, which -- coincidentally enough -- is used in the Zune 30 and a few of Toshiba's alternatives. We suppose it's a little late to ask, but did any non-Zune owners experience similar issues just prior to the dawn of '09? Or were you too busy, um, partying like it was 1999?
[Thanks nywytboy68]
That was a very weak attack, Jay Evans.
My Gigabeat T400 crapped out of me too on the 31st. Booted up again on the 1st. :) All is good.
1st generation Zunes were just Gigabeats with a new cover on it.
You would think someone at Engadget would know that !
Both my Linux box and mine and my missus' WinMob 6's freaked out. The linux box just completely locked up (first time in 8 months) then both phones started acting up, e.g. not connecting to wireless/3G, strange software errors , network cards refusing to start e.t.c. Reboots seemed to clear it, but quite strange.
Can you read the "Breaking News" section once in a while?
Also there were issues with some of the software used on the Samsung Instinct that stopped working on the 31st too. Movies, news, weather all crapped out giving an uncaught exception error instead. Very annoying!
This was my hunch from the beginning. People fail to realize that Microsoft did not create the first Zune. They had Toshiba make it for them. Only the latest Zunes were created by Microsoft. I suspected Toshiba was sorta kinda behind this...
Yikes, that was supposed to be a reply to an earlier post. My first comment mistake here! :( Ignore my lame comment, and my lame blog.
So they just need an else break; after the 267, right? I wonder when they'll release a new version of the firmware.
No, sir. You were mistaken on one interpretation:
"Under most normal circumstances, days is not greater than 365"
Only for the first 365 days since ORIGINYEAR (i.e., 1980). Then in 1981 it becomes 366, 367, 368... and thus:
"The only time such a circumstance can occur is during the last day of a leap year."
Or actually at all times after 365, as I said.
"December 31st, should have been the first time days was ever been equal to 366, thus making this past Wednesday the first time this chunk of code had ever run on a Zune."
On only one day ever (rather than every four years) should days == 366. I believe that day was back in 1980. Thus this while loop has executed perhaps many times a day on every Zune since their creation. However, you are correct that lines 261-268 had never executed before.
well my zune still hasnt un frozen.. its been charged and run flat i dont know how many times over the last few days.. still gets stuck.
@bookbrnr
Nurta knows about the other news posts that were made by Engadget on the day off but he's saying that on that same day in the late afternoon a member of zB had uncovered everything posted in this article here. Including code directly from the driver and what the problem was with the code.
OMG, a relevant informative post with a detailed objective explanation that mentions neither Zune or Apple and their respective accolades and shortcomings.
This, sir, shall not stand, I assure you.
Now Jan 4th, going on 5th.... My 30GB Zune still locking even after draining and recharging. Frustrating. Anyone have alternative solutions?
I did actually, but I don't think it was any way related to why the Zunes and Toshiba's crashed. It was a 2nd Gen 32 Gig Ipod Touch.
The problem you ask?
The button, the only button to quick applications, failed to work, the side keys for volume could not be held down, it'd only be reconized if it was pressed and released. And no matter HOW LONG you held down the power button, it'd go to shutting off the screen, not the ipod. *CORRECTION* the button did work, but only if you wanted to fast track the music. It'd bring up that, thats it. I had to let the battery wear itself to death then charge it again and pray. And remind myself, I hate apple, with a passion. This happened from 6PM New Years eve onto New years Day, where I had to leave music running on repeat and randomly turn on the screen to drain battery as effectively I could, while still being lazy.