I'm trying to use Jemplode to edit my config.ini file and seem to run into an issue with actually saving the changes I've made.

I connected to my empeg (over ethernet), opened up the configi.ini and made my changes and hit ok. I then synchronized, and the config.ini still contains my changes. However, if I reconnect to the empeg, I get a notification box indicating that my changes haven't been made. Hitting OK and going back to the config.ini results in reverting back to whatever was there before I made any changes. Does this sound like an issue with Jemplode or a step I'm forgetting to do, or perhaps something I've done to cause the config.ini to not be editable?

For what it is worth I am seeing the same erratic behavior with jemplode and config.ini. It seems to work for some edits but not others! I haven't been able to correlate the "failure to stick" edits to anything yet.

Lynn

Hrm.. Running emplode now indicates that I have an error while checking media (Error 0xc0041010).

I don't get any bad disk errors, and all of my tracks seem to be there. Jemplode seems to synchronize just fine, though..

Arg.. I'm running into the same thing that bbowman ran into with reguards to telnetd running off of /dev/hda4.. If it's running, the sync is blocked. I guess this is a strong argument against putting anything on /drive0 after all..

Odds are it has nothing to do with Jemplode.

It's probably the same thing I was running into: As soon as you move userland programs onto /drive0/, certain aspects of the synch start failing if you're running those apps in AC power mode.

The drive unmount/remount commands (used in a synch) quit working when an app is running off of that partition.

You need to make sure all your apps on /drive0/ are tagged as @DC only, and then only do synchs in AC mode. After you've done that, you need to do this to fix your drives. After that, you should (in theory) be OK.

So, the bottom line is that /drive0/... may not be where we want to keep ALL user apps. @DC is fine for gpsapp but what about telnetd or empegVNC that you want to use at home, @AC in fact.

"BZZZZZZT, wrong answer!"

I, for one, would still like to have a consistant place to keep programs and data that will survive an update and not have interactions with other tasks (and not be restricted to use on DC power).

Perhaps, in the course of refining the user app instal process this will emerge.

Lynn

Okay, I deserved that.

I just ran into the problem Yang described, using jemplode 47 to add "[startup]
ReserveCache=64"
to config.ini. I'm not running anything other than Hijack and the default player software.

After doing the fsck's manually via the serial port, rebooting, and watching the unit rebuild both databases, now emplode tells me Error 0x00041002.

(I mention this only because it does seem there is something wacky with using jemplode to edit config.ini.)

--Nathan

jEmplode 47 has a bug where it will not update config.ini at all (basically I forgot to add the line of code that syncs config changes back).