This is good news.
Those three files you mention can be precreated and placed on the client.
There is no need for them to be created by starting the browser.
Could you try this?
Thank you
Mike Kaply
IBM
Bj�rn-Willy Arntzen wrote:
> Hello there, the workspace guy (me) has tested the latest release....
>
> The good news is that a WorkspaceOnDemand client now can run Mozilla
> from everywhere I want. This is very good, but I have to create a
> FIT-file to manage this. The file is show below.
>
> j:\os2\Moz094\MOZREGISTRY.DAT
> \\SERVER\D$\HOMEDIR\<USER>\Moz094\MOZREGISTRY.DAT
> j:\os2\Moz094\COMPONENT.REG
> \\SERVER\D$\HOMEDIR\<USER>\Moz094\COMPONENT.REG
> j:\os2\Moz094\COMPONENTS\XPTI.DAT
> \\SERVER\D$\HOMEDIR\<USER>\Moz094\XPTI.DAT
> j:\os2\Moz094\COMPONENTS\XPTITEMP.DAT
> \\SERVER\D$\HOMEDIR\<USER>\Moz094\XPTITEMP.DAT
>
> Even if this is working, the use of FIT files is not wanted, because a
> ordinary Warp Client cannot use FIT files, so if I want to run a
> networkinstalled (shared drive) Mozilla, the client still tries to
> create the following files: component.reg, xpti.dat and xptitemp.dat on
> the programdirectory (j:\os2\Moz094) I have set the env. variable
> MOZILLA_HOME to F:\Moz094 (f: is the users homedrive), and it's working
> fine. The profiles are placed in f:\moz094 directory.
>
> Mike K. my most wanted feature/fix is that the files component.reg,
> xpti.dat and xptitemp.dat is also places in the MOZILLA_HOME directory.
> If this could be done the public part and the private part is separeted
> which make a networing environment very easy....
>
> The bad news is that proxy still is so slow that it's not working. It
> takes 5-10 minutes to load www.vg.no. If I uses direct connection to
> internet, it's so fast that my hair is blowing....
>
> Could this be a bug or maybe a configuration thing ? I have checked the
> firewall log and there is not a error logged. Netscape 4.61 had no
> problem with this.
>
> Bj�rn-Willy Arntzen, KLP Incurance, Norway
> [EMAIL PROTECTED]
