Somehow my config.ini file got corrupted. Now, whenever I try to change its settings in emplode, I get the error "sequence mismatch, someone was here before us". I'm using 2.00b7 with hijackv92. When I sz the file to my computer to view it, I see a bunch of weird ascii characters, and then the actual config file below them. Any ideas on how to revert back to a plain, original config.ini file, or how to edit the one I have now?

Anyways, I just tried re-downloading the 2.00b7 upgrade and installing it to no avail. I truely hope the solution doesn't involve me losing everything on the drive as I just finished uploading it all today

I can think of two easy ways:
- sz it to your computer, edit it there, rz it back to empeg. Use editor that can keep Unix EOL characters (LF (ctrl-J), as opposed to DOS/Win CR LF (ctrl-M ctrl-J)).
- Load developer image. Connect via serial, drop to shell. cd to appropriate directory, type

cat > config.ini

(type carefully yout config.ini)

(finish with ctrl-D)

Hey again, I'm getting the read-only file system. I did rw in the /empeg/var directory but that didn't help. Is there something I'm missing?

Nevermind, I just tried rwm and that worked... I'll let you know if this solves it...

I have a suspicion that it might be related to one of the Hijack versions. Were you running Hijack?

(Mark, jump in here and slap me if I'm wrong about it).

Re-installing an Upgrade will not fix the config.ini file, as the upgrade deliberately does not touch config.ini.

To fix config.ini, use this procedure from the FAQ to edit it and see if all is well afterwards. Let us know how it goes.

Ah, /empeg/var is a symlink to /drive0/var. Do both rw and rwm. Don't forget ro and rom later!

Okay great I got it, now I can edit it in emplode again, thanks. By the way, if the seq_number gets screwed up, does that prevent you from doing anymore syncs???

I was using hijack, I don't think that screwed it up, it might have gotten screwed up during a sync. Anyways, I just did the rw and rwm and just put a blank line in the config, then I was able to edit it from within emplode.

By the way, anyone know of any resources that explain the commonly used developer commands on the bash prompt, like sed and such? Also, is there a cross-compiler from arm-linux that will run on a win32 box?

sed is a separate command altogether. It's not part of bash (ugh) or any other shell. However, there are a number of good places to look for Unix command basics. Try Unix Guru Universe. Other beginners seem to have had good success there.

>I have a suspicion that it might be related to one of
>the Hijack versions. Were you running Hijack?
>(Mark, jump in here and slap me if I'm wrong about it).

Consider yourself slapped silly!

Hijack does not have write access to the disk, never even thinks about calling a write() routine, and definitely does not attempt to write or modify config.ini or any other file or buffered item, so it cannot corrupt anything on it.

-ml

Is it maybe some extra hijack-related options, hand-added to config.ini, that are confusing emplode's ability to read and write the file?

I am not aware of any such impairment. Are you?

I once also saw a corrupted config.ini file, with 2.00beta3, long before hijack even had code to read the darned thing. I think emplode / emptool / player just get seriously confused at times, and have a small chance of randomly corrupting things.

I suppose someday we may bump into a possibly hardcoded buffer size limit in Emplode, like if one crams zillions of ir_translate codes into config.ini, but it hasn't happened yet.

Cheers

-ml

My config.ini somehow got corrupted a week or two ago. I have no idea how it happened. I was running hijack but I am also skeptical about that having anything to do with the corruption.

I wonder if this rash of config.ini corruptions has anything to do with the 2.0 betas? Have any 1.03 users had their config.ini corrupted?

I also had a config.ini corruption a while back. I am pretty sure it was after upgrading to 2.0b3 and before I started running hijack. Hasn't happened since so I have not worried about it.

-Mike

I am not aware of any such impairment. Are you?

Here's what I recall. This could be wrong, my memory is... ... what was I going to say? I don't remember...

I seem to recall that config.ini didn't like nonstandard formatting. It was something like either semicolons didn't count as comments, or it didn't handle them right or something, or if the file wasn't in a perfect [section](cr) key=value(cr) format, then it would get corrupted on the next emplode edit.

The only reason I thought of hijack was because I thought that early in hijack's history it used some settings that either had the semicolon doing something emplode didn't like, or the lines didn't have equals signs, or something like that. It's all a blur to me now, but I could have sworn we discussed it here on the board.

a perfect [section](cr) key=value(cr) format

[nitpick]
(lf), not (cr)
[/nitpick]

Speaking of that, are CRs tolerated at all?

You are correct. Since the program resides on a Linux system, it's not CR's, it's LF's.

I meant that on the screen when you edit the file, there is a new line at those points.

I wonder if the presence of CRs is what corrupted the file in the first place?