MS Zune's commit mass suicide

[Trooper110]

I would too if I was running a Microsoft OS (don't tell my desktops that)

All Together Now!: 30GB Zunes Failing Everywhere, All At Once
http://www.zuneboards.com/forums/gen...ne-frozen.html

[WalkinTarget]

Currently the workaround is to open up the Zune and remove the battery, then pop it back in after a few hours after it has fully discharged. But ... and here's the but .. you cannot SYNC it again to the PC or it will fall back into recovery mode and die.

What a pie in the face disgrace, MS !! Hopefully they can resolve this from an update if the end user can follow the battery removal fix and refrain from a sync, then load the updated firmware to fix the flaw.

[BenKenobi]

HAHHAHAHHAHAHA

I laughed so hard... its like they put a piece of code in there to self destruct at a certain time.... .....lol so funny good job microsoft

[Murder Simulator]

It sounds to me also like a timer ran out or something, since they all started to die out at the same time. Anybody MS suckered into buying one of these is surely regretting it now.

[Mobojo]

My 1st gen 30 gb is running fine.

[WalkinTarget]

It was fixed after the internal date rolled over to today, Mobo. Someone forgot to tell you to try it 2 days ago.

[Mobojo]

I did. :P I used it on my plane ride home the 31st. I watched Anchor man the whole flight home.

[ChrisWW11]

That sucks I still think the ipod touch still is the superior mp3 player.

[killa_zn]

My 80g is still operational

[H0ly-H@nd-Gr3nade]

If anyone is interested into why it died for a day, take a look here (starts at line 249).

Here is a comment from someone who explains what that code means (and why it broke):
"For anyone who is wondering or just doesn't want to figure it out, Dec. 31 qualified as being greater than day 365 (obviously, because it was day 366) but it got caught where the program says to look at (days > 365). The problem is that there was no code for what to do if the day *equals* 366, only if days is *greater* than 366. So, there was no way to break out of the (days > 365) loop until today (day 367) when the program would reset days to 1, thereby breaking the loop."

[Gimmie2]

If anyone is interested into why it died for a day, take a look here (starts at line 249).

Here is a comment from someone who explains what that code means (and why it broke):
"For anyone who is wondering or just doesn't want to figure it out, Dec. 31 qualified as being greater than day 365 (obviously, because it was day 366) but it got caught where the program says to look at (days > 365). The problem is that there was no code for what to do if the day *equals* 366, only if days is *greater* than 366. So, there was no way to break out of the (days > 365) loop until today (day 367) when the program would reset days to 1, thereby breaking the loop."

lol ive had similar problems in programs i've written, in one of them, if the user entered a capital N for "play again?" it would stick the loop saying while (answer != n)... they would play again, and again... until they manually closed the program (it was a slot machine in java)

[Mobojo]

lol ive had similar problems in programs i've written, in one of them, if the user entered a capital N for "play again?" it would stick the loop saying while (answer != n)... they would play again, and again... until they manually closed the program (it was a slot machine in java)

Oh yea, good old loops and if statements in java.

[Savage_Hobo]

lol ive had similar problems in programs i've written, in one of them, if the user entered a capital N for "play again?" it would stick the loop saying while (answer != n)... they would play again, and again... until they manually closed the program (it was a slot machine in java)

lol... been there... I wrote a C++ look that was supposed to decrement an integer from 5 to 0 each loop and I would check and see if the integer <= 0 and get out of the loop.... but instead of decrementing the integer I incremented it... I ended up crashing Windows when it overflowed

The crash was accompanied with system beeps and everybody in the library did the "turn and around and throw eye-daggers at me" until I did a hard reset of my laptop...... it's was actually pretty funny... (unfortunately that wasn't the last time I pulled that one )

[Mobojo]

lol... been there... I wrote a C++ look that was supposed to decrement an integer from 5 to 0 each loop and I would check and see if the integer <= 0 and get out of the loop.... but instead of decrementing the integer I incremented it... I ended up crashing Windows when it overflowed

The crash was accompanied with system beeps and everybody in the library did the "turn and around and throw eye-daggers at me" until I did a hard reset of my laptop...... it's was actually pretty funny... (unfortunately that wasn't the last time I pulled that one )

I miss taking my C++ class in high school. You never left your computer unguarded because if you do cout >> "/a" the internal speaker would beep. It was always fun sneaking over to someone's computer and hiding that in an infinite loop within their code. They would compile and run and then usually hard reboot. It was like a game in my class to get each other.

[Trooper110]

Here's a very detailed description, including the code from the driver that caused it: AeroXperience A lesson on infinite loops