You are not supposed to tighten it, it is designed to be loose.

So it hangs when you switch to the radio: I am going to go check this on my own player to see if this is a problem with V2 as I have not tried the radio since upgrading.

Hang on - you say it doesn't respond to the remote. Which remote are you using, the Kenwood or the Rio? I have found an issue with the Kenwood relating to the Radio.

OK, I will take a closer look at this post. (my English and technical skills are not that good )

Vince

p.s. I have not changed any disk owse

Since it sounds like a memory issue, I would say you should try and revert to V2 consumer. If that still hangs it, then go back one further to 2B13 consumer, then report your findings.

Sounds like you may still have some form of handshaking enabled. Make sure you have NO handshaking set in your term s/w

What size (capacity) are the hard drive(s) ?

I have a Toshiba 6495MB hdd

When it worked, the remote worked too...

The situation is that I get the boot logo on the display, then a message of loading stuff... and then it goed to standby (light flickers)...
I can still hear the disk spinning... but it does not power on (besides the light)... not from the buttons not from the remote.

Emplode on XP can not find the player (on USB and Serial). But before the crash/freeze that was no problem...

I can upgrade also hyperT (but there i get no prompt)...

I have done the things that you sugested to the pins on the mb.

Vince


I use the Kenwood remote.

with MTTTY I CAN get in...

I will try all the stuff mentioned and update you guys soon!

Vince

hmmmm....

Since the player is not recognized bij emplode... I can't do anything on the config file, right?

Enclosed the bootlog after ctrl+c

Vince

Are you sure you didn't set the handshaking on hyperterminal?

I'm in

[shuff
deduplicate=1


I am not sure that the missing square bracket is good, but I doubt that this would hang up the player. You obviously don't have the "massive CONFIG.INI" problem caused by the bug in 2B11, so it's not that either.

Hmmm....

how can I add the bracjet (I'm not a linux man).

Vince

Hmm. I could see how a missing close-bracket might theoretically screw up the ini-file-reading routine if it wasn't bullet-proofed against that sort of thing. Don't bother with adding the close bracket, just delete the ini file completely and see if that solves the problem.

Just in case, here is the FAQ with the commands you need to type for deleting the config.ini file.

Unfortunately this doesn't help either...

Hello All,

I still have the problem

This morning I have rebuild the disk, put the developer v2 software back and added the tunes.
Back in the car: it worked great... after playing in the car and haning the player on my XP pc... DEAD.
It boots untill the "Loading Visuals" message... and then nothing on the display and just the burning light in the bottom right corner.
I can re-boot what ever I want or press whatever button I want... the player does not respond (the disk is running!!!)
Hyperterminal has access to the player and lets me mount the drive.
The player does not pop up in the select player dialogue screen of emplode (not on USB not on serial)...

The only thing that I can come up with is that the player gets corrupted in my car... 'cause after playing in the car, undocking it from the car and haning it on my pc... the problem first shows herself...
Does anyone have the correct wiring? (it think I have it right, because it plays in the car....)

I have posted the config.ini and the bootlog earlier... I have shortened the pins on the MB. I have checked all connectors... The player does play, but only one session in the car (so this is not a memory problem, right). Basically I have done all I could do (stuff in the FAQ and your tips in these posts).

HELP!

Vince

I have tested it again (re-build the disk and added the developer v2 and some tunes)...

Went to my car, docked it, turned on the egnition, player starten and played pefect. Shut down the juice, started again... PLAYER DEAD!!!!

So undocking is not the problem... the power (or something else) in the car is... Can somebody point out what I did wrong?

Vince

At this point, I really do not know what to add. It might be a good idea to contact support and have them look at the unit. I cannot (personally) think of anything to add at this point.

He's coming round for coffee and a diagnostic on Thursday ....

Excellent!!!

Problem solved. VInce has ben here and it turned out that the audio daughterboard was loose. It's been glued back in, and he's gone away with a handful of stickers and a big smile.

Yet another satisified customer!!!

A loose audio daughterboard? That is a new one. Should that go in the FAQ, or is it too obscure?

No, I think it's a candidate - it's the second Mk 1 I've seen with "weird" behaviour, but had a seriously loose daughterboard. In this case, I did the same as the advice I gave for securing it as before - remove the original silicone bead from the connector header for the board, then make sure it's correctly positioned, and finally coat the connector area and board with lots of semi-rigid hot glue to make sure it doesn't move. I also put big blobs at the opposite side to fix the board to two capacitors sticking up, to make sure it was supported on more than just one side.

It seems to have fixed it: we spend about half an hour turning it on and off, rebooting, all the rest and it came up perfectly every time.

I added a note to the other Mk1-power-loss FAQ entry about the loose daughterboard.