United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4895647 Tiger: Inserting double char into jre/jdk path fails the installation
JDK-4895647 : Tiger: Inserting double char into jre/jdk path fails the installation

Details
Type:
Bug
Submit Date:
2003-07-24
Status:
Closed
Updated Date:
2013-06-11
Project Name:
JDK
Resolved Date:
2013-06-11
Component:
install
OS:
generic
Sub-Component:
install
CPU:
generic
Priority:
P4
Resolution:
Duplicate
Affected Versions:
5.0
Fixed Versions:
8

Related Reports
Duplicate:
Relates:
Relates:
Relates:

Sub Tasks

Description
We documented this bug in 1.4.2_01.  I reopening this as a place holder to fix for Tiger/Tiger+.

To reproduce:

1. On any of the windows 2000, XP, or 2003 install language pack for languages such as Chinese, Japanese, and Korean if it does not come with the OS.

2. Install JDK/JRE 1.4.2_01 or 1.5.0.
3. And choose to customize the installation path.

4. Modify the installation path and insert a double bytes char.
5. At the point when installer is creating jar file the installer will fail and pop up the error dialog with error code 1722. 

Note: The tested OS is in English and after installing language pack, the lcoal/regional setting can stays English or to the specific locale used in the path. 

                                    

Comments
Duplicate CR covers use case and fix.
                                     
2013-06-11
WORK AROUND

Do not use any multibyte charaters in the directory into which you
are trying to install the JRE/JDK or set the locale correctly in
the Control Panel->Regional Settings and Set the default locale.

Refer to this URL for further information, it is documented at the
very end.

http://java.sun.com/j2se/1.4.2/install-windows.html
                                     
2004-08-06
EVALUATION

Committing to mustang
###@###.### 2003-09-17

Investigating the bug, ie. to make the java installer and other
sub-components install into a directory which contains multi-byte/wide
characters AND if the default locale is english (for example). 

The fix is very complicated and this configuration cannot be supported.
There are several sub-components (zipper, unpack, unzip) and the vm,
and other utilities which needs to be unicodified. 

This is a very large effort for very little gain, ie. there is no reason why anyone should use multi-byte characters in the path-name when the locale is set to english or something else. 

For the record: To clarify this issue needs to be addressed for a future
release as an RFE when the VM can work when User_Locale != System_Locale,
AND we decide to drop the Win98, WinME systems. Until then its way too
complex to fix the installer subcomponents, especially the zipper and unzip,
and possibly Regutils.

###@###.### 2004-08-03

By popular demand (namely the I18N team) I am re-opening this bug, 
the problem here is that its very cumbersome to deal with Win98 and WinME.
Its entirely possible that these platforms may not be supported for 
mustang, and if the I18N team will fix the vm issues then its worthwhile
to fix this bug.

###@###.### 2004-08-04
                                     
2004-08-04



Hardware and Software, Engineered to Work Together