Re: Seamonkey profile

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.
>>
>
> 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.
>
> <$quote>
>
> setlocal
> set BEGINLIBPATH=n:\mozilla.org\mozilla\firefox-17.0.11esr
> set LIBPATHSTRICT=T
> set MOZILLA_PLUGIN_PATH=n:\mozilla.org\mozilla\plugins
> cdd n:\mozilla.org\mozilla\firefox-17.0.11esr
> firefox.exe -P "default" -no_remote
> endlocal
>
> </quote>
>
>
>>>
>>>> Eventually you should consider upgrading SeaMonkey and Firefox. Not
>>>> easy getting all the dependencies unless you use YUM/RPM or better,
>>>> the Arca Noae Package Manager (ANPM), free download.
>>>>
>
> Must She log into his site or does this utility exist elsewhere, for
> example on hobbes, THAT site She can access via the NFTP/2 program.

Currently you have to use HTTPS to download the utility. If needed, you 
can always get wget from Hobbes and use that to download ANPM.

>
>>>>>
>> [...]
>>>>> This may be a bit offtopic, but have somebody in this ng have any
>>>>> experience using File and print service in eCs? She plans to
>>>>> install the
>>>>> ecs22_en_cd1_smp_betaII.zip on the new box which comes with both the
>>>>> Air-boot and the PEER server that's is running here in eCs 1.2. So
>>>>> what
>>>>> steps must be taken so that She can transfer all partitions to the
>>>>> new box?
>>>>>
>>>>
>>>> I've always just moved my hard drives to new boxes and used xcopy to
>>>> move partitions to new hard drives (after partitioning).
>
> Not possible in Her case as the drives on the old system is SCSI and in
> the new box 2x500GB SATA drivers.
>
>>>> ArcaOS has been released as well if you want something more up to date
>>>> Dave
>>>>
>>>
>>> In Her case it's about moving all data from the old box to the new box
>>> and having the same driveletters on the new box for the corresponding
>>> 'old' partitions on the old box, for example the old F: partition with
>>> it''s contents should be copied to the new F: on the new box - rinse and
>>> repeat for all the other partitions that sits on the old box but NOT the
>>> C: that contains W*nXP, there She will do a fresh install. Would be nice
>>> though to somehow backup some applications, i.e. browsers stuff and
>>> restoring them to Win7 when it's created and up and running. She
>>> supposes that this xcopying could be done over the network or using File
>>> and Print services to to the copying. Will also use rsync to backup the
>>> whole system to a 70Gib USB stick formatted with JFS. If File and Print
>>> services don't work, install rsync and restore the whole shebang from
>>> the USB stick. As She understands it an XOPY over a network would be
>>> something like this: XCOPY \\SORILESERV\C:\*.* \\SORILEACLI\C:\ /S /E /V
>>> /H /T /R or is She out in the blue here?
>>>
>>
>> I've always used /H /O /T /S /E /R /V and don't use *.* but rather *
>> so the wildcard gets files without a dot or extension
>> Dave
>
> Ok, so when the new box is up and running with the and connected to the
> network with the name 'SORILEACLI' and the old box with the name
> 'SORILEASRV' because She have Warp Server installed and had used this
> flavour of os/2, She must somehow give the new box access rights to all
> the partitions on the old minus the XP partition and using XCOPY
> \\SORILEASRV\C:* \\SORILEACLI\C: /H /O /T /S /E /R /V - then rinse &
> repeat for all the other partitions that sits on the new box.
>

Looks right. I've never copied across the network to test
Dave