remote

mine doesnt work anymore. batteries fine, rebooted machine many times. no work. it was working then i sat down and watched a movie and left my empeg playing. i came back and now the remote wont work.

Check and make sure the battery contacts on the remote are tight. There've been quite a few people with this issue... including yours truly.

Do the front-panel buttons work, too? Are you running 2.0beta7?

If the front-panel buttons don't work, and you are running 2.0beta7, there's nothing wrong with the remote. It's a bug in 2.0beta7. Either live with it until Beta9 is released, or go back down to 1.03 which is stable and does not have this bug.

Wait. You said you rebooted the machine several times, so that's not it. The bug would have been cleared by a reboot.

Hmm. Are you absolutely certain the battery is not dead? How do you know the battery is not dead?

cause ive never had a volt meter lie?
how do i open the remote to check connections?
it seems pretty sealed. i suppose i could superglue it back together. face buttons still work.

I'm on my 3rd remote same symptom, works fine 1 minute dead the next. I'm afraid to try my new remote.

I was thinking of using Hijack and an old remote to replace my Rio remote.

I have a smiliar problem with mine. One minute it works and the next it doesn't. If I left it alone for a little bit and came back it would be fine again. The battery was good, and I was considering that maybe it was this contact problem, but I discovered something interesting. It's a well known trick that you can see whether a IR remote is sending signals by looking at it with a video camera, as the IR LED will glow when seen through the viewfinder, and I discovered that in thoses times when it was not working, the LED was always transmitting whether a button was being pressed or not. Very strange, because it is definantely getting power.

In any event, David is graciously sending me a new one. Until then Hijack is coming in mighty handy, though I had to try several remotes before I found one that worked with it (a Kenwood, not surprisingly).

yeah, i cant even use hijack to my advantage cause i cant edit my config.ini.

IF ANYONE KNOWS HOW PLEASE TELL ME!!!
cause mines broken.

I know at radio shack they have these little like i dunno basically its like a color changing piece of paper that detects IR light

>yeah, i cant even use hijack to my advantage cause i cant edit my config.ini.
>IF ANYONE KNOWS HOW PLEASE TELL ME!!!

It's in the FAQ, here.

(Just call me Tony)

I have had a similar problem where at seemingly random times, the Rio remote just stops working. I normally have to power cycle the player and it comes back good.
I have a kenwood remote left over from another project which works with the empeg (probably a similar model to the original Kenwood remote shipped with the earlier models) and noticed then when the Rio remote stopped working the Kenwood continues to work.
Is there a reason for this?

Cheers,

Andy M

It means your battery is about to die. Replace it.

To be honest, I don't think I've actually read about a truly defective remote yet. All the problems I've read about, including the ones I've had myself, have been resolved with a new remote battery.

BTW, I noticed you followed up to another thread. One that hadn't been touched since last September. Don't bother replying to old threads like that. It's best to post to the new thread and just include a link to the old one for reference.

It might be a good idea to ask Paul if there's any support in the BBS software to automatically lock inactive threads after a certain period of time.

Bruno

In reply to:

---

It's in the FAQ, here.

(Just call me Tony)

---

no no its not.

see here

Your config.ini is corrupted. To fix your config.ini, you must delete the file from the hard disk and start over again. This requires using the shell prompt.

When he said "it's in the FAQ" he meant that instructions for editing the config.ini are in the FAQ (which they are).

I have not put instructions for fixing corrupted config.ini's in the FAQ because I'm reasonably sure that's a bug of some kind and it needs to be fixed. I am very interested in getting to the bottom of the bug, but so far no one has given any information about how they caused it to happen.

To delete your config.ini file, connect with hyperterminal (that's in the faq) and do the following:

q
rw
rwm
cd /empeg/var
rm config.ini
rom
ro
exit

Note that there will be a long pause at the "rwm" stage.

I'm unaware of a reason to bother running `rw' and `ro' for this purpose. You should be able to leave those out without any ill effect and save some time, too.

Edit: I had initially said `rwm' and `rom' were unneeded. I was wrong.

I never remember which directories requre one and which directories require the other, so I just always do both.

Actually, I thought VAR was on the same partition as the music and therefore needed RWM?

Oops. You're right. You don't need the `ro' or the `rm'. Didn't realize that /empeg/var was on the music partition. I'll edit my above post so as not to confuse folks. Sorry.

> no no its not.

Hmm sorry, thought you were just asking for instructions, it's hard to keep all the threads straight. The really sad thing is I actually posted in that thread.

I didn't see it; did you ever try to edit it with notepad to fix all that corruption and uploading it back in?

Just to make sure the point doesn't get lost. You CANNOT successfully edit config.ini with NOTEPAD.EXE. Windows notepad is hardcoded to use CRLF. Linux, uses only LF to terminate lines. You'll need a more robust text editor.

TextPad
UltraEdit
PFE
EditPad
etc...

They should all have support for changing your line endings. CRLF (PC), LF (UNIX and Amiga) or CR (Mac).

Bruno

Sorry about that, I'll have to polish my 'netiquette'

> You CANNOT successfully edit config.ini with NOTEPAD.EXE. You CANNOT successfully edit config.ini with NOTEPAD.EXE.

Not entirely true. I covered this point in the original thread. Yes, notepad uses CRLF, but if you transfer the file back using Ascii mode (such as rz -a), it will strip the extra characters and it will work. I mentioned in that thread that I hadn't actually tried it, but since then I have and it works great.

Well, if you're using serial, you can also remove and create a new config.ini right from the command prompt. If you don't have the developer image installed then you also won't be able to use zmodem. So you'd probably be looking at FTP. And since I don't use notepad, I've never tried sending anything over in ASCII to see if it gets properly stripped that way. I keep all these types of files with LF-only because TextPad loads them properly and preserves that attribute. It's more convenient since I ftp a lot to/from webservers...

Bruno

Well if it has developed a fault where it transmits continuously this might explain how the batteries are getting flat. My new mark 2 was manufactured in April so it would be very strange for the battery to be dead already. I've got some new AAA batteries here and the expiry date is in 3 years time.

Remember that the remote ships with the strip of plastic in the battery compartment isolating the battery, so it's effectively brand new when you get it.

And i've had my Mk 1 since 99 and the original battery is fine. When the RIO remote dies, the Mark 2 still responds to the kenwood remote from my mark 1, so it seems to be the remote and not the player.

I'll get a new battery and see if that fixes the RIO remote, but if it is malfunctioning and transmitingt continously, then it will just run the new battery flat after a period of time. Unfortuantly i don't have a camcorder to do the test mentioned