JDK-6198632 : singlemsi installer should only be used on windows2003 32-bit without servicepacks
- Type: Bug
- Component: install
- Sub-Component: install
- Affected Version: 6
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2004-11-22
- Updated: 2010-04-04
- Resolved: 2006-10-31
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.
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.
| Other | JDK 6 |
|---|---|
| 5.0u2Fixed | 6 b20Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
Description
We have always had an issue with iftw on windows 2003 and later OS's. Microsoft has fixed the problem with MSI 3.0. Therefore, the latest builds of all 64-bit windows have this problem fixed. Sp1 of Windows2003 32-bit includes msi 3.0, so the only officially released build of windows2003 is 32-bit without any service packs. We should change the jinstall iftw algorithm, to only download the singlemsi when on win2k3d without service packs (and machines behind auth-proxies)
Comments
|