I have upgraded a working unit on 1.03 to v2beta. Got everything working. So after playing a while, it was time to go cruising.

The problem is the unit won't do anything in the car. It powers up, empeg pequin screen, my logo, then it runs off the list of booting procedures as it always has. It goes momentarily(half second) to the player screen. The display then goes black. No sound, no activity from anything. Except if you power down from the Rio remote or holding the top button, the blue light starts the flashing(as it should). If anything is pressed the blue LED goes out, but the unit still doesn't come on.

What have I done here? Is anybody else seeing this?

The unit still works in the house.

Proud Owner of MK2 080000558 - 18gb Blue

I had the same problem. I thought my empeg was toast. The problem is that the dimmer is all the way down!!!

Adjust that, and you'll be right as rain.

- Jon

A couple things wrong with that theory. I get no sound. That shouldn't matter on the dimmer setting. You can't change the dimmer setting on the empeg from the car if you can't see whats going on. And just to make sure, I played with the lights and dimmer in the car. I also have two vehicles that I use the empeg in. They both have the same problem.

Proud Owner of MK2 080000558 - 18gb Blue

Try turning your headlights on...

- Jon

If you have made the changes to the config.ini for outputting FID information to the serial port, then you are seeing a known bug that is fixed in the next release. You remove that feature from config.ini to get your player working again.

If that's not the case, downgrade to 1.03 and see if that keeps you going until the next release.

___________
Tony Fabris

I did that, but it still shouldn't affect the fact that there is no sound.

Proud Owner of MK2 080000558 - 18gb Blue

Hm. I had the same exact problem you are having. I fixed it by turning the headlights on and then my display popped up. The default volume was WAY down, and once I turned it up, I could again hear what was playing on the empeg...

Maybe you have a different problem.

- Jon

I don't know if have done that in the past or not. What would I look for in the config.ini file?

Proud Owner of MK2 080000558 - 18gb Blue

Ok, figured it out. You are both right on the problem. First,Tony was right. I had put the quit menu item in the config.sys. Did this so long ago I didn't remember. Got to looking in the file and was reminded of that.

Second, jbauer turned out to be right also about the dimmer and volume being down.

Corrected this issues and all is well.

If it weren't for the people on this board, RIO might have a very busy phone line.
Thanks ya'll - I'm from Texas can ya tell?

Proud Owner of MK2 080000558 - 18gb Blue

Excellent. Congrats!

- Jon

Thanks ya'll - I'm from Texas can ya tell?

Yes, by your stubborn refusals of Jon' advice

BTW, 'Quit' menu option does no harm (and needs to be there for the new DisplayServer). People (including myself) had problem with

[output]

timecodes=1

notify=1

The player would simply die immediately upon start (and be restarted etc). But that was at home, too.

Do browse through Feedback->Bugs forum: many interesting things there . (OK, I realize other people have other things to do apart from this BBS...)

Dragi "Bonzi" Raos
Zagreb, Croatia
Q#5196, MkII#80000376, 18GB green

Well, the quit option is what I took out and now it works. Maybe I'll try putting it back in now that it is booting in the car. Maybe the unit needed to fully boot without that to complete some other task.

Proud Owner of MK2 080000558 - 18gb Blue

2.0-beta3 has only been announced to people on the BBS for good reason. The official tech support answer to _any_ problems with a beta will be to return to the last consumer version!

The BBS and [email protected] are an effective tool for collecting bug reports, and hopefully 2.0 will become a stable consumer release fairly soon. (Then we can start with the 2.1-beta's )

Rob