-
Bug
-
Resolution: Fixed
-
P2
-
5.0
-
b51
-
x86
-
windows_xp
Here is the steps to reproduce the issue:
1. Install JDK, unselect Public JRE.
2. After install, go to jdk/bin directory, launch "javaws.exe".
3. The program crashes.
However, if I go to private JRE directory, there is another javaws.exe which works fine. The question is if the user does not install public JRE, why do we put javaws.exe in the sdk/bin directory? If that requires public JRE installed, we don't need to bundle it into SDK since public JRE has it anyway.
Another way is we can give better message if that requires public JRE installed.
###@###.### 2004-04-30
###@###.### 2004-04-30
1. Install JDK, unselect Public JRE.
2. After install, go to jdk/bin directory, launch "javaws.exe".
3. The program crashes.
However, if I go to private JRE directory, there is another javaws.exe which works fine. The question is if the user does not install public JRE, why do we put javaws.exe in the sdk/bin directory? If that requires public JRE installed, we don't need to bundle it into SDK since public JRE has it anyway.
Another way is we can give better message if that requires public JRE installed.
###@###.### 2004-04-30
###@###.### 2004-04-30
- duplicates
-
JDK-5041025 The javaws.exe does not work when public JRE does not install
-
- Closed
-
-
JDK-5041026 The javaws.exe does not work when public JRE does not install
-
- Closed
-
-
JDK-5041027 The javaws.exe does not work when public JRE does not install
-
- Closed
-