I've had four or five instances in the past couple of weeks where my empeg has stopped responding. The player continues to play, but neither the remote nor the face buttons do anything. Only way out is a power bounce.

I am running Hijack - latest version. Any help is greatly appreciated.

Joe

What version of player software are you running? Ive had the same thing happen in beta 7 so I assume thats what you are running.

I installed Hijack over the beta 7 version. Doesn't one replace the other? Did this last week, so it's whatever version of Hijack was available then. Sorry - but my player is out in my truck and its way too freakin cold out there to get it and see what version. ;-)

Happened to me once or twice too. I think it is a known bug.

It just happened to me a few minutes ago. My empeg has been running all day - about 12 hours. Lots of reboots, http list transfers, loads of SITE RW and RO and small FTP transfers.

The first time it happened I wasn't using Hijack, so it isn't the cause of the problem. I've been running Beta7 since it was released, but I can't recall if the first time was with Beta3. It has never happened in the car yet. I use the player at least 2 hours per day in the car - 1 hour in the morning and 1 hour in the evening.

Bruno

For some reason it only seems to crash after its been playing serveral hours unattended. Sometimes it doesnt crash, but in transient mode, you can see where the track name didnt quite make it off the screen. A few pixels are stuck on the bottom of the display, while the visual keeps going. No input is accepted.

Sean

What you have described is a known bug in Beta7. If you install the non-beta 1.03, the bug will go away. Hopefully it will be fixed for the next beta (I haven't had it happen to me in Beta9 yet).

Funny how everyone seems to get this under different conditions. It happens to me EVERYTIME I'm in the car. Sometimes within minutes of each other. Pop it out of the sled far enough to power it down, plug it back in and it reboots, keeps playing the same song and all is well. Hopefully the next release will solve the problem. It's kind of annoying but not enough to downgrade.

I actually had this happen to me with 1.03 this week. The player froze up, and the only way to solve this was to disconnect the power and have it reboot. This was the first time it happened to me at home, but I've also had it happen to me once or twice in the car.
My player is a "standard" Mk2a 60gig. No modifications have been made and it still runs 1.03.
I did find this strange, however if it only happens once in a while I can live with it.

Hm, my old player (MkII, 18GB, 1.03) has not frozen once in more than a year of more or less 24 hr/day playing (car, work, home, and I often fall asleep with it playing), and I think this is the general experience. In other words, something might be wrong with your hardware. Apart from memory test, though, I don't know what to do....

I haven't tried a memory test yet (will do now and get back to you), but I don't think this is the problem since Hugo has said before that they haven't had a single Mk2a with bad memory chips. (of course, with my luck...)
As said before, it's not like it's happening every half hour, so I can live with it. Who knows, maybe it will be solved with a new firmware. (I'm actually awaiting the newest beta. Didn't try one yet because I wanted the biggest bugs ironed out first - I guess that must have happenend by now, so...)