Recently I added

[output]
notify=1
[hijack]
suppress_notify=1
[serial]
car_rate=115200

to my player's config.ini. I did this by using ftp to download the config.ini from empeg/var to a local folder and then I used the windows notepad to edit the config.ini.
The "Restore Visuals" function seems to work, at least in DC/Car mode, but everytime the empeg boots up, i get the "hijack config error". (Btw.: my config.ini is 793 Bytes).
I restored to the original config.ini which i've made a backup of, and used emplode to edit the config.ini (after applying the reg-hack, of course). This time, there was no "Hijack config error". I'm sure i've made no typing mistakes during my first attempt, i still have the modified .ini on my local drive.
One thing i noticed was the format of the config.ini.
It looked like this:

[hush]hushpercent=20[display]visual_names=1
and so on.

I changed that into

[hush]
hushpercent=20
[display]
visual_names=1

maybe it's a problem with the char set? I've got a german windows install.

It's probably because Windows text files and Unix text files specify newlines in different ways. Use a different text editor that allows you to save the config.ini in Unix format. I use Vim. Other folks have suggested ... UltraEdit, I think.

Edit: I've also used EditPad and it's nice, as well, for a fairly simple NotePad-type editor (that includes Unix newline format features).

Quite interesting that the other additions I've made using Notepad (the serial=11520 and the notify=1 thing) seemed to work. Maybe hijack is unicode only? Is notify=1 only used by hijack?

Well, that's odd. The only safe thing for the config file is 7-bit ASCII, though. The newlines thing does explain the lack of newlines that you ``fixed''.

Maybe there's something else....

Edit: What version of Hijack are you using? He fixed a misspelling of ``suppress'' in a version a while back that might be causing your problem.

As you have discovered, do not use Notepad to edit config.ini. Notepad outputs Windows-format text files, which cannot be properly read by Linux.

Instead, edit your config.ini with Emplode, which, as you have discovered, will work correctly.

The FAQ entry covering possible config.ini problems is here and it explains why there is a problem with using Notepad to edit the file.

I think I'll beef up the main "how to I edit config.ini" FAQ entry on this topic, too.

I've got v291 installed.
However, I don't think this was the problem.
Thx anyway!