FYI, you can create component.reg, xpi.dat, xptitemp.dat before you deploy.
these files don't need to be created on a user by user basis.
Mike KAply
IBM
Bj�rn-Willy Arntzen wrote:
> Thanks Mike.
>
> Michael Kaply wrote:
>
> > I have no specific WSOD info for later 0.9 builds. It is possible that more
> > files are being changed, and these need to be in the FIT file.
>
> I'm using a tool, fwatch, and get's very detailed I/O trace from it, and it's
> looks like the FIT file is sufficient. The mozregistry.dat file is not created
> yet (in my environment). Is this file in use ?
>
> But I can see that component.reg, xpi.dat and xptitemp.dat is touched under a
> program start, this could cause a rc=32 situation. I don't know how this is
> handled by Mozilla.
>
> > The only file that comes to mind is installed-chrome.txt in bin\chrome.
> >
> > By the way, the issue here is not "easy to deploy in a networked
> > environment" This issue is that WSOD does a very bad job at managing these
> > kinds of situations.
> >
>
> Regarding network deploy, this was a general opinion. And Mozilla would be
> really easy to deploy if also the three files that is changed would be moved to
> MOZILLA_HOME (and all other files that's personal to the user) . Is this
> possible for you to change this behaviour ?
>
> you said : .. WSOD does a very bad job at managing these kinds of
> situations... What do you mean? The FIT files is very manual, but very
> powerful.
>
> Bj�rn-Willy
>
> >
> > Mike Kaply
> > IBM
> >
> > Bj�rn-Willy Arntzen wrote:
> >
> > > I have tried to run Mozilla 0.9+ on the WorkspaceOnDemand (WSOD) client,
> > > but has no success so far. The IBM Web Browser works fine.
> > >
> > > So if I use the IBM Web Browser as a base for the FIT file, it still
> > > crashes. Here is what I have done:
> > >
> > > 1) copied the files into z:\os2\Moz092
> > > 2) created a APPPOST.FIT file with the following contents:
> > >
> > > ?:\os2\Moz092\MOZREGISTRY.DAT
> > > \\ANKUS2\D$\<USER>\Mozilla\MOZREGISTRY.DAT
> > > ?:\os2\Moz092\COMPONENT.REG
> > > \\ANKUS2\D$\<USER>\Mozilla\COMPONENT.REG
> > > ?:\os2\Moz092\COMPONENTS\XPTI.DAT
> > > \\ANKUS2\D$\<USER>\Mozilla\XPTI.DAT
> > > ?:\os2\Moz092\COMPONENTS\XPTITEMP.DAT
> > > \\ANKUS2\D$\<USER>\Mozilla\XPTITEMP.DAT
> > > ?:\OS2\NSCP.INI
> > > \\ANKUS2\w\<MACHINE>\NETSCAPE\NSCP.INI
> > > ?:\OS2\NSREG.DAT
> > > \\ANKUS2\w\<MACHINE>\NETSCAPE\NSREG.DAT
> > > ?:\NETSCAPE\USERS
> > > \\ANKUS2\w\<MACHINE>\NETSCAPE\USERS
> > >
> > > 3) created a public application for this
> > >
> > > And this is what happens:
> > >
> > > Mozilla enters the create new user dialog, but the folder location for
> > > the user is empty, so I'm forced to pick a folder for it, and then
> > > Mozilla chrash
> > >
> > > 07-02-2001 11:47:52 SYS3175 PID 007b TID 0005 Slot 006f
> > > Z:\OS2\MOZ092\MOZILLA.EXE
> > > c0000005
> > > 1e83293b
> > > P1=00000001 P2=0000001c P3=XXXXXXXX P4=XXXXXXXX
> > > EAX=00000000 EBX=1e8527a0 ECX=1e852888 EDX=13e8afa0
> > > ESI=0095c0e0 EDI=0080319c
> > > DS=0053 DSACC=f0f3 DSLIM=ffffffff
> > > ES=0053 ESACC=f0f3 ESLIM=ffffffff
> > > FS=150b FSACC=00f3 FSLIM=00000030
> > > GS=0000 GSACC=**** GSLIM=********
> > > CS:EIP=005b:1e83293b CSACC=f0df CSLIM=ffffffff
> > > SS:ESP=0053:00867f8c SSACC=f0f3 SSLIM=ffffffff
> > > EBP=00867fd4 FLG=00012206
> > >
> > > WDGTOS2.DLL 0001:0000293b
> > >
> > > In this case NETSCAPE was already installed, if I remove it Mozilla
> > > crashes when it fails to load z:\os2\nsreg.dat.
> > >
> > > Mike, can I expect Mozilla to run in WSOD ?
> > >
> > > The only runnable rolution is to move Mozilla to a shared drive i.e
> > > j:\os2\Moz092 and set the Mozilla_Home= f:\Mozilla (f: is homedir). Then
> > > I have 3 files that is 'shared' at j:\os2\Moz092: component.reg,
> > > xpti.dat and xptitemp.dat.
> > >
> > > Can these three files be shared with all users ?. If not, why is they
> > > not located in the MOZILLA_HOME location ?
> > >
> > > A silly thing that I seldom understand is why can't omeone create a
> > > software that's EASY to deploy in a networked environment. The
> > > MOZILLA_HOME variable seems to be a good idea, if all the private files
> > > is placed there.
> > >
> > > Bj�rn-Willy Arntzen
> > > KLP Incurance, Oslo, Norway
> > > [EMAIL PROTECTED]
