This can't be changed anymore. Regardless which key is used we would break compatibility by using a new one in the next version (changes for OOo2.0 are too late now) just to avoid possible problems with outdated versions that will get out of use in the near future. So a bug report would be a waste of time.
But maybe the problem is not the key, I just heard that OOo1.1.4 *does* support the new bootstrapping and the key *is* a new one. Maybe Thomas can make this clear. So we need to know: which version of OOo1.x exactly did you use?
The new bootstrap mechanism was introduced in SO7 PP3 (I think this is OOo 1.1.2) for Java only and in OOo 2.0 for Java and C++. Also the NEW registry key was introduced with those versions.
As Mathias already wrote, it's too late to change the default behaviour of the bootstrap mechanism, as this would break compatibility.
Looking at your stack trace it seems, that your OOo 1.x installation was found and the bootstrap method was called. In the past there were several bug fixes in the bootstrap method, and I assume that your OOo 1.x installation didn't have all of the bug fixes. E.g. the bootstrap method was not working, if your installation path contained spaces (e.g. "C:\Program Files\OpenOffice1.1.2).
Thomas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
