Closed Bug 220113 Opened 22 years ago Closed 21 years ago

ibm.com - ``Support download manager'' doesn't work properly

Categories

(SeaMonkey :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: relf, Unassigned)

References

()

Details

OS/2 build 1.5rc1 To reproduce: 1. Open provided URL 2. Enter Type-Model: 2647-47U Operating system: OS/2 3. Click continue 4. Click on ``[+] Expand all'' and select all the files ( see related bug 220112 ) 5. Click on ``Download Now'' (allow popup window if blocked) and accept Applet from IBM 6. ``Support download manager'' window reports ``Ready to download!'' but the only working feature is ``close''.
This page is no less broken in W32 20030916. The popup makes no provision for the visitor not having Java enabled, except for the close link.
Hardware: PC → All
OS: OS/2 → All
Blocks: 114157
Tried the IBM support site in IE and Mozilla. The site doesn't even seem to work in Internet Explorer, all I get is a warning to check my proxy settings. Is this the result you are seeing?
Version: Other Branch → Trunk
I've got it working under Win2k IE 5.5 and JRE 1.4_02 Now I know that there should be [Download] button at the bottom of that ``Support download manager'' window.
I just re-tested this site using a selfmade Firebird build from 20040109 on WinXP, and the site now works as expected. I'm using the latest Windows JRE from Sun, 1.4.2_03. Can anyone confirm that the bug has been resolved for them as well?
Unable to test on recent OS/2 builds due to bug 225472
Now with Mozilla OS/2 build 2004102908 it reports ``Download Director applet cannot be loaded. Java support must be enabled to run.'' I have Java support enabled but I have JRE 1.3.1 instead of required JRE 1.4.x. So that seems to be an explanation. Anyway the originally reported problem is gone. Resolving as WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.