-
Bug
-
Resolution: Cannot Reproduce
-
P4
-
None
-
1.4.2
-
x86
-
windows_nt
On Win NT, I created a directory with Japanese characters in its name.
I then copied a JDK installation (1.4.2-b19) to this directory.
When I navigate in Explorer to the <install>/bin/ dir and dbl click javaw.exe, I get an error box saying
Error: Could not open ..../jvm.cfg
where .... is a pathname that has nothing to do with the pathname
of thd JDK installation.
A brief look at java_md.c indicates that
- it could not find the jvm.cfg in the installation I was running,
I presume because of a bug in the handling of the JA chars.
- it then looked for a pathname to jvm.cfg in the windows registry
and found one that was no longer valid because I had deleted the
installation.
Are there user errors here, such as
- rm -rf'ing a jdk installation but not cleaning out the registry?
- 'installing' a jdk by doing a cp -r and not creating any
registry entries for it?
Are the above rm and cp valid ways of dealing with JDKs on windows?
I then copied a JDK installation (1.4.2-b19) to this directory.
When I navigate in Explorer to the <install>/bin/ dir and dbl click javaw.exe, I get an error box saying
Error: Could not open ..../jvm.cfg
where .... is a pathname that has nothing to do with the pathname
of thd JDK installation.
A brief look at java_md.c indicates that
- it could not find the jvm.cfg in the installation I was running,
I presume because of a bug in the handling of the JA chars.
- it then looked for a pathname to jvm.cfg in the windows registry
and found one that was no longer valid because I had deleted the
installation.
Are there user errors here, such as
- rm -rf'ing a jdk installation but not cleaning out the registry?
- 'installing' a jdk by doing a cp -r and not creating any
registry entries for it?
Are the above rm and cp valid ways of dealing with JDKs on windows?
- relates to
-
JDK-4847320 mantis-beta does not work correctly in Multi-Byte locales
-
- Closed
-