I think I found the ultimate lockup, and would appreciate any ideas/options. :/

Just got my player, upgraded it to the 2.00b11 and Hijack, haven't been able to play with any settings, as I had to "load 'n go" - but listening to it in Home mode all day at work went fine, until I accidently switched it from Player to AuxIn.

When I did that, everything stopped. The visulization dissapeared, the only think on the screen was the timer countdown, left over from the MP3 playback. It wasn't moving, and NO BUTTONS responded. Not on the remote, or front.
So, I unplugged it, and plugged it back in. Everything came up fin, until the status line said "Starting audio...". And it stuck there. Locking up like previous. So, I have no way to even get it back to playing Mp3s, and it's kinda a downer, having hoped to use the Aux during my next road-trip..

Ideas? Gratzi!

Did you by any chance apply the wrong version of either the player software or the Hijack kernel? For example, applying a Mk1 file onto your Mk2 unit?

.. My bad. I'm on 237 of Hijack. Didn't notice 239 was out today. Going to see if I can do anything to my player (i.e. install newest hijack, telnet in..)

Strange!
After leaving it unplugged for abour 15 mins, and plugging in a network cable (to go ahead and see if I could telnet in), once I plugged it back in, it booted back up! Now I have visuals and and "Input: Waiting.." on the screen.

So, whatever it is, it's gone now.
Thanks ya'll.

..Another interesting note.
My remote started working. It had died about 4 hours before the system locked up. I figured the battery was old and dead.
After the system came back up, the remote started working! Also, my 'bios' settings were reset! (i.e. My date\time was reset.)

Ah. I love beta testing. And I love this thing.

Something sounds screwy with your player. These are not normal things to be happening. Perhaps you should contact support?

I'm gonna give it a week or so.. Just to make sure that it's still being 'burnt in'. My remote locked up once more at work - the display keys worked fine, just no remote. Going into Hijack's IR menu, where you can see the buttons pressed, the remote was completely dead. Nothign was showing up. Unplugging and plugging the player back in cleared up the problem. Didn't ene flip the remote over.

Also, I'll admit, I may be looking at several issues and thinking they're all related (hey, I work in Tech Support. I know how that can happen when you're new with something.) So I'll give it some time..

Thanks!

I had exactly the same problem, whenever Aux-In was selected the player would lock up and not reboot. I had to downgrade to 1.03 and then back to 2.0 Beta. It turned out to be a fault with my player. David fixed it in four days under the warranty. Does it lockup every time you select Aux?

Don't know - haven't done so since. I will try tonight once work slows down.

Yup. Locked up again.
Just hit the 'Source' button on the remove, and complete lockup. Before I rebooted, the Hijac menu still responded, but once I rebooted and got to the "Starting Audio..." part, can't even get into Hijack then.
I'm gonna hook it up to serial connection at home tonight, and see what's on the 'console'. (Mainly because I'm curious.) If I have to return it to get it fixed, I might just wait until AFTER my cross-country trip to do so - I paid more than I had to for the unit to make sure I could have it for the trip. (Assuming I can get it unstuck again..)

Replying to myself again.. I could go blind..
Anyways, figuring out that if I hold the knob down right after I turn on the player, I CAN access the Hijack menu.. Going into 'Vital Signs', I see:
LoadAvg:8.99 8.43 5.33
with the values slowly increasing.. Pretty scary for somethin' that's not doing anything.

In either case, apologies to all for wasting space, since this is something that must be known and not an issue.

In reply to:

---

Did you by any chance apply the wrong version of either the player software or the Hijack kernel? For example, applying a Mk1 file onto your Mk2 unit?

---

Nope. Wish it was that easy. I reinstalled 1.03 and then 2.00b11 again (like the other post indicates), and it still happens. Also, it's not saving the time/date when I set it..