Hi,
Some of this may be candidates for bug reports, and others may be just
misunderstandings on my part, but I want to present it all here in
context first.
The other day I installed OOo2.0.3 on Windows XP. Firstly, I installed
JRE 1.5.0_7 and then OOo2.0.3 after removing all previous versions of
both. I then configured OOo to use JRE and registered a data source for
the database application that I've just delivered to my client. The
client side of the application is built on OOo forms and the RDMS is
PostgreSQL.
During this process I came up against the following issues:
- There was no quickstarter icon in the Windows Quickstart toolbar even
though Task Manager showed a running soffice.exe and/or soffice.bin from
the previous version. I had to kill these in Task Manager whenever I
changed options that require an OOo restart. There appear to be
radically different versions of Windows XP - one with the older Win 2000
style desktop and one with a newer style desktop. The quickstarter icon
problem was only on the newer looking desktop.
- OOo Tools->Options->OpenOffice.org General->Java doesn't wait for user
confirmation before starting to look for installed JRE versions and
there appears to be no way to interrupt it. I don't know where or how
OOo looks for installed JRE but if this gets into trouble then users
will not know what is going on or how they might work around the
problem. E.g. When I entered this dialog on a Win 2000 machine with an
old JRE 1.4 and JRE1.5 installed, it sat there for a very long time and
I eventually had to abort and leave.
- there was no entry for the currently installed JREs in the "Add/Remove
Applications" window, and I couldn't delete their folders on first
attempt because there was a running process "ju*.exe", which appears to
hang around permanently once JRE has been loaded during a login session.
I had to kill this process in the Task Manager before I could remove the
older versions of JRE.
- once OOo and JRE is installed and configured I'm able to run my
database application, but there's a problem. The .odb connection uses
the postgresql sdbc from OOo and is configured without a pre-specified
username and password because I want users to provide both when they
connect, and the usernames that the database requires are not the same
as the Windows user names. During the first connect this all works fine
- the username/password dialog comes up and the connection completes ok
after authenticating. I also check the "remember password until the end
of the session" box so exiting and restarting should not ask for
authentication again (because the quickstarter will still be running).
However, when I do restart I get an error complaining that the Windows
username is not known to the postgres backend. I'm assuming that this is
due to an interaction with the Windows' single-signon feature,
otherwise, why is OOo trying to use the Windows username instead of the
Postgres username that I supplied earlier?
Whenever I come up against this last issue the only way I can continue
is to kill the OOo quickstarter via the Task Manager and then restart OOo.
I'm not a Windows user/admin, so I'm probably not doing things entirely
correctly, but then perhaps some of these issues are likely to hit other
people attempting to install/upgrade OOo on Windows.
Advice or comments?
Thanks.
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
