kko>> In K-Meleon 1.5 the file profiles.ini is the profile pointer. In previous versions the file registry.dat is the profile pointer. The purpose of the profile pointer is to tell the browser what profiles exist and where they are located. In order to move or rename profile directories, just edit profiles.ini (registry.dat is synchronized automatically).
(kko and desga2)
Ah-ha! That is what I suspected. In the old system, I used a hex editor to modify the ????????.slt file to change the random number/letter convention to something specific that I could then use on other installations of KM by simply copying over the entire SLT sub-folder with all my tweaked settings. The hex editor (of course) worked with DAT files natively, so that part was easy.
When you edit profiles.ini, you lose your modified settings, no?
And the change in Gecko made it impossible for KM to stick with the old methodology. Too bad.
Do I understand correctly that I could (if I wished) rename the sub-folder to the old .SLT extension instead of DEFAULT?
I'm not quite sure I understand why the single system install will work regardless of the drive letter of a usb stick? But that solution for the browser would not also work for your various plugins, so would it not be better to go for the portable apps solution. We have our own, the better known Gecko browsers (like FireFox and Seamonkey) are modified by the Portable Apps people:
kkl>> [Just to make confusion perfect: The profile.ini file that can be placed in the K-Meleon installation directory, is just a pointer to the profile pointer - it tells K-Meleon where to look for the actual profile pointer (profiles.ini or registry.dat).]
Now that is a distinct advantage. FWIW, I have always used a profile.ini file in previous incarnations of KM in order to keep program information where it belongs: in the program's sub-folder, like all well-behaved apps do.
Edited 1 time(s). Last edit at 08/05/2008 05:28AM by ndebord.