Y2K8 Zune quirk really a Freescale bug?
![](https://s.yimg.com/ny/api/res/1.2/rjJbIqszmPBY_hS1HD9HXw--/YXBwaWQ9aGlnaGxhbmRlcjt3PTcwNTtoPTcxNg--/https://s.yimg.com/uu/api/res/1.2/uJpTgo8VMHLnT0uhoFDuLg--~B/aD00Mzc7dz00MzA7YXBwaWQ9eXRhY2h5b24-/https://www.blogcdn.com/www.engadget.com/media/2009/01/1-3-09-mc13783_bd.jpg)
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]