JDK-5082632 : give warning if users enter double char into jre/jdk path
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2004-08-04
  • Updated: 2016-07-28
  • Resolved: 2015-02-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Related Reports
Duplicate :  
Relates :  
Relates :  
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. 

We should detect this situation using regutils, and tell the user that they need to choose a new path without multi-byte characters.
###@###.### 2004-08-04

The issue is not reproducible with the latest 8u60 and 9 promoted bundlles. Tried the reproduce steps and install was successful with the following bundles: 1. http://jre.us.oracle.com/java/re/jdk/1.8.0_60/promoted/latest/bundles/windows-i586/jre-8u60-ea-bin-b03-windows-i586-17_feb_2015.exe 2.http://jre.us.oracle.com/java/re/jdk/1.9.0/promoted/latest/bundles/windows-i586/jre-9-ea-bin-b51-windows-i586-18_feb_2015.exe

I have tested with 7u40 and 8. Currently they can be installed successfully even though the installation path includes multi-byte characters. I have also confirmed that everything is working fine after installation. So I think this issue can be closed.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang

EVALUATION You have to detect from either the installer or regutils function. Most likely it will be the latter, I am not sure how to do this, we will need to check with Sherman, Naoto or Norbert. But my guess at this time is that,if we need this functionality in Regutils we may need to link with unicows.dll (I think) which is in the coreX.zip file, which we cant unzip. OR we have to bundle this dll into the installer. -Kumar

SUGGESTED FIX Regutils needs a new function, which will do the following: boolean IsValidInstallPath(LPSTR install_path) { 1. Check the default system locale. 2. Check the installpath for mb characters or does it use codepoints not contained in the code-page of the system-locale. 3. if the default_system_locale does not support the codepoints used in the installpath deny the installation, by returning a false. return true; }