Thomas,
That's for the workaround, but I've been having these discussions
because I'm developing some client apps and am forseeing the problems
people are going to have as well as trying to prompt discussion to
enable a better OOo design for the future.
mike
--- Thomas Benisch <[EMAIL PROTECTED]> wrote:
> Hi Mike,
>
> > We decided to go for a) and I don't really see any problems
> > with it. You mentioned the problem with OOo 1.1.x which
> > always writes to HKEY_CURRENT_USER. This is a bug and very
> > unfortunate. I think this bug cannot be fixed in OOo 1.1.x
> > but probably I'm wrong. Therefore I only see two solutions.
> > Either you remove all OOo 1.1.x installations from the system
> > or you delete the registry key in HKEY_CURRENT_USER.
>
> as a workaround for your current problem you can try the
> following. Install your OOo 1.1.4 as network installation,
> that means '.\setup -net -alluser'. After that you
> make your user installation without parameters '.\setup'.
> Note, that the second .\setup must be called from your
> program directory, which was created by the network installation.
> Then the registry key is written to HKLM instead of HKCU.
>
> Thomas
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
