Re: Seamonkey profile

Peter Brown wrote:
> Hi Christer
>
> Christer Jacobsson wrote:
>> Dave Yeo wrote:
>>> Christer Jacobsson wrote:
>>>> Dave Yeo wrote:
>>>>> Christer Jacobsson wrote:
>>>>>> Dave Yeo wrote:
>>>>>>> Christer Jacobsson wrote:
>>>>>>>>
>>>>>>>> Her WinX have screwed up the FAT32 driveletter from r: (the same
>>>>>>>> as in
>>>>>>>> os2) to O:, but in the new box the FAT32 volume will have the same
>>>>>>>> driveletter R: on both sides - will do a clean install of win7
>>>>>>>> 32bit on
>>>>>>>> that box on a C: primary partition and WSeB on another C: partition
>>>>>>>> and
>>>>>>>> a flavour of DOS on a C: partition.
>>>>>>>>
>>>>>>>> She thinks that the simplest way to place the new SMPmW profile
>>>>>>>> would be
>>>>>>>> to put it in a subdirectory to R:\SEAMONKEY and a new FF profile on
>>>>>>>> R:\FIREFOX. But that begs the question, must the SET
>>>>>>>> MOZILLA_HOME=y:\mozilla.org\mozilla be changed or can it be as
>>>>>>>> it is
>>>>>>>> now?
>>>>>>>
>>>>>>> Mozilla will try to use the SET MOZILLA_HOME environmental location
>>>>>>> first, and then fall back to the program directories (latest OS/2
>>>>>>> versions will first fall back to whatever is in SET HOME). I'd
>>>>>>> recommend using SET MOZILLA_HOME as having the profile in the
>>>>>>> program
>>>>>>> directory makes updating hard and will also make migrating to SM v2+
>>>>>>> hard.
>>>>>>>
>>>>
>>>> She looked into the Readme.txt for SMPmW118 and came across an example
>>>> how to divorce the profile data from the current y:\mozilla.org... and
>>>> that was to set the mozilla_home to say
>>>> SET MOZILLA_HOME=R:\data
>>>>
>>>> This would result, according to the readme.txt that the profiles would
>>>> be stored in r:\data\mozilla\profiles and under that the profiles
>>>> themselves. One guy gave Her a tip to get rid of that pesky
>>>> xxxxxxxx.slt
>>>> dir and that was to place a prefs.js containing a couple of lines os
>>>> alphabet soup, then that xxxxxxxx.slt dir wouldn't be created at all,
>>>> making the profile path much cleaner :-)
>>>>
>>>
>>> Yes, that is correct about how SET MOZILLA_HOME works, including SM
>>> 2.x going under SeaMonkey. Don't know about the prefs.js trick.
>>>
>>>
>>>>>>
>>>>>> So how should the new settings for SET_MOZILLA_HOME be set
>>>>>> if She creates an r:\mozilla.org\mozilla catalog on r:, and under
>>>>>> that a
>>>>>> catalog named Profiles and under that the new profile names for
>>>>>> SMpMw118
>>>>>> and Firefox? Remember that the programs itself will live in the
>>>>>> y:\mozilla.org\mozilla\ dir. And btw, She kicks off SMPmW118 and
>>>>>> Firefox-10.0.12 and Firefox-17.0.11esr and one of the .cmd files She
>>>>>> uses to kick off 17.0esr look like this:
>>>>>
>>>>> SET MOZILLA_HOME=r:\mozilla.org\mozilla\Profiles You will end up with
>>>>> a directory Mozilla under that with Firefox, SeaMonkey (and Profiles
>>>>> for SM 1.x) directories for their profiles. Might be simpler to have
>>>>> SET MOZILLA_HOME=r:\mozilla.org.
>>>>
>>>> What would the differences be if She uses your first example or your
>>>> second suggestion?
>>>
>>> Shallower directories with the second example, though it is all
>>> personal preference
>>> Dave
>>>
>>
>> If She uses your example, i.e. setting SET MOZILLA_HOME=R:\mozilla.org,
>
>
> I would shorten that to SET MOZILLA_HOME=R: as the Mozilla app will then
> create a directory structure R:\Mozilla\Profiles on first startup.

No, only Firefox and SeaMonkey use Mozilla.
I have SET MOZILLA_HOME=Z:\Mozprofiles and under that
Downloads (created by SM IIRC)
Moonchild Productions (Where Palemoon put its profile)
Mozilla
Thunderbird

and under Mozilla
Extensions (unused, I believe it for Firefox and universally installed 
extensions)
Firefox
Profiles (SM 1.x)
SeaMonkey (SM 2.x)

Much better to put these under a common subdirectory.


>
> I also seem to recall that mozilla.org was meant to be the root
> directory for the application files to be stored in eg
> mozilla.org\seamonkey

I believe your correct.

>
>> what dir structure will be created when She creates the new profiles for
>> SMPMW118 and FF/2? Ok, the mail and newsgroups would end up on the r:
>> partition, but that can come in handy if She must request a new pw for a
>> site and Copy & Paste to FF/2 doesn't work - have experienced this ot at
>> least one site doing this, but some sites have a button named "Remember
>> me" in the login procedure, so if She manages to login to the site in
>> Win7, then it will carry over to for example FF/2 on the OS/2 side. But
>> on another tack: Can GenMac be installed in the WSeB using the genMac
>> that lives on the eCs 2.0 installation CD's or even on eCs 1.2(?) before
>> it's transferred onto the new box? And btw, have the MMOS2 part been
>> updated in the various eCs version or is the MMOS2 the same as in the
>> classic WSeB?
>>
>>
>>
>> Cul8er alligator!
>> gaea - feminist & chunkawakan
>
>
> I would guess that genmac from an eCS distro can be installed to WSeB. I
> would try installing genmac and any required nic driver pack then use
> Protocols and Adapters to Change nic drivers prior to Power Off and
> moving drive to new box.
>
> eCS integrates the CWMM multimedia classes but MMOS2 is otherwise the
> same I think.

There's a different mminstal program in eCS and currently ArcaOS. The 
ArcaOS is due to be updated

Dave