Closed Bug 35916 Opened 25 years ago Closed 23 years ago

Can't install Shockwave Player into Mozilla (Netscape 6.01)

Categories

(Tech Evangelism Graveyard :: English US, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mgeller, Assigned: arun)

References

()

Details

(Keywords: shockwave)

(THIS IS THE SAME AS BUG 35915 but on WinNT) When I tried to download Shockwave 8 Player from the above URL on Windows NT, I got an error message that said: Your are about to download a file of type "application/octet-stream". This file is unrecognized by Netscape .... I chose to save the file anyway, but it would not open and execute properly.
Keywords: beta2, shockwave
With tooday's build, I could save and open the file.But the shockwave installer tried to look for "Netscape.exe" in the selected folder. The netscape executable for 6.0 is named "Netscp6.exe". I am not sure if this is a problem with the shockwave installer or a problem in the client. But the file definitely downloads and installs itself if I select a 4.x version on my machine.
Resolving invalid as problem in beta need to be reported in Netscape's bug report form and this prob needs to be verif on a recent moz build. I do not see it in a recent build.Resolving invalid
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Keywords: nsbeta2
Reopening. The original problem is still there. "Can't install Shockwave Player into Netscape 6". 1.) Visit sdc.shockwave.com/shockwave/download and get the win32 version of shockwave. 2.) Try to install it into Netscape6 What happens: The install fails because it cannot find netscape.exe
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Original problem should read 'Macromedia installer cannot install Shockwave Player into Netscape 6'. It looks specifically for netscape.exe to continue an installation, and there is no way _we_ could fix it. Marking invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → INVALID
I agree. Unless macromedia release a plugin compatible for netscape6, this problem would be seen.VERIFIED
Status: RESOLVED → VERIFIED
Not even a plugin, this is purely installer issue. It is too automatic.
*** Bug 56112 has been marked as a duplicate of this bug. ***
Re-opening. Somebody better talk to Macromedia.
Status: VERIFIED → UNCONFIRMED
Component: Plug-ins → Evangelism
Resolution: INVALID → ---
-> ekrock
Assignee: av → ekrock
Status: UNCONFIRMED → NEW
Ever confirmed: true
This issue has been reolved in the Shockwave install that will be released in conjunction with the Netscape release.
adding keyword rtm, just learned of this problem. Also have contacted Troy Evans at Macromedia.
Keywords: rtm
*** EVERYONE *** -- Please be *very specific* in your comments and bug reports to indicate whether you are talking about the Macromedia Shockwave Plug-in or the Macromedia Flash Plug-in. They are two separate products. It is very confusing because the Macromedia Shockwave Plug-in installs the Flash Player as well, and you can have Flash content within a Shockwave animation. Bug 56112 is tracking the inability to install Flash Player without 4.x on your machine. That is the bug JohnG is working on. This bug is tracking the inability to install Shockwave Player. Per mtomlin's comments that this is fixed in the next release of Shockwave and also in a coming installer update for the current release, marking this fixed (with the new Shockwave installer bits). shrir, please still verify this with the next-release Shockwave bits Meridith is giving us access to. Thanks all!
Assignee: ekrock → av
Like bug 56112, this does not seem to effect anything that is shippe with Netscape 6. Shockwave is not shipped with Netscape 6, but the user may already have an earlier version of Shockwave installed on their computer (from an different browser). Will the pre-installed shockwave plug-in work after you install the new Netscape 6? cc'ing kiwi@macromedia (troy evans), ssu, and marking rtm- since this is a fix for the Shockwave installer that a user would download from Macromedia.
Whiteboard: [rtm-]
There will be a release of the Shockwave install in coordination with the Netscape 6 release. This will not include a new version of the player, but the install will look for the correct exe. I have added myself to the cc list in case there are any further questions regarding the shockwave install.
Adding Paul Chen and myself to CC:list Paul, did you already fix this in bug 35915 and it has regressed?
Nom. nsbeta1. Shockwave backward compatibility bug, and high-quality plug-in support is a priority for embedded applications.
Keywords: nsbeta1
Eric, on 10/11, you wrote "marking this fixed (with the new Shockwave installer bits). shrir, please still verify this with the next-release Shockwave bits Meridith is giving us access to." But never marked this bug fixed. Is it fixed? Could we get Shrirang to test this? I will mark fixed per Eric's earlier comment and then maybe it will get some attention for confirmation.
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → FIXED
no ,this is still not fixed. I tried to install both shockwave 8.0 and 8.5 on windows trunk (0122) and branch (0117). The 8.0 installer on the macromedia website does not recognize and list 6.0 in the 'available browsers' list' that pops up i the first step of installation. I have to manually point to the netscape6 plugins directory and then proceed with the installation. However, only part of the installation completes and then the problem in bug 57012 is seen (6.0 does not launch after completing the initial part of the installation since the installer cannot find Netscape.exe). Also, this does not work with 8.5 installer provided by macromedia. Would it be fine to mark this as a duplicate of 57012 since the problem here is the same as seen in 57012 or keep this seperate ? FOr the time being, I am reopening this bug..
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
There will be a release of the Shockwave install in coordination with the Netscape release that fixes all priority 1 Shockwave bugs. This will not include a new version of the player, but the install will look for the correct exe.
moving to m0.9
Target Milestone: --- → mozilla0.9
Chris, This bug deals with the Shockwave installer not locating the Netscape 6/Mozilla binary EXE. We can not fix this. Meredith Tomlin from Macromedia says they will refresh their software in a comment. What is the status of this?
Keywords: nsbeta1, nsbeta2, rtm
Whiteboard: [rtm-]
As Meredith says, "There will be a release of the Shockwave install in coordination with the Netscape release that fixes all priority 1 Shockwave bugs." We have not yet released that version.
FYI: the way to detect where Mozilla is at has changed. You still do it via the windows registry keys tho. Here's what's changed: old: key: HKEY_LOCAL_MACHINE\Software\mozilla\seamonkey name: CurrentVersion key: HKEY_LOCAL_MACHINE\Software\mozilla\seamonkey\[CurrentVersion]\Main name: Install Directory new: key: HKEY_LOCAL_MACHINE\Software\mozilla.org\mozilla name: CurrentVersion key: HKEY_LOCAL_MACHINE\Software\mozilla.org\mozilla\[CurrentVersion]\Main name: Install Directory
> old: HKEY_LOCAL_MACHINE\Software\mozilla\seamonkey > new: HKEY_LOCAL_MACHINE\Software\mozilla.org\mozilla The key for Netscape 6, however, has not changed. It is still "HKEY_LOCAL_MACHINE\Software\Netscape\Netscape 6" Note, not "Netscape 6.anything", the actual version is contained in the Current Version subkey.
Reassigning to aruner.
Assignee: av → aruner
Status: REOPENED → NEW
Netscape bugs belong in Bugscape. Changing Summary to reflect Mozilla
Summary: Can't install Shockwave Player into Netscape 6 beta 1 → Can't install Shockwave Player into Mozilla (Netscape 6.01)
Blocks: 74980
*** Bug 65389 has been marked as a duplicate of this bug. ***
Meredith or anyone else, Seen Meredith states "There will be a release of the Shockwave install in coordination with the Netscape release that fixes all priority 1 Shockwave bugs.", the field "Bug 35916 depends on:" should be filled with some values, shouldn't it?
Patrick, This is a great point; however, I've been working offline with Shockwave to see if their issues are closer to resolution, and both QA's are working on some test cases. Should it become necessary to further link this, we will! Meridith, feel free to link this if you want to also, as Patrick suggests. -- akr
Arun and Meredith, I am not sure to understand. Meredith talks about problems with Netscape/Mozilla but Arun talks about problems on Macromedia's side. If it is the first case, the other bugs in Bugzilla should be marked as blocking this bug and that's very simple. If it's the other way around, then ... well you do what you want to.
To rule Macromedia out, change the UA string to Nav 4.x and test: Hand-edit Netscape 6\defaults\pref\all-ns.js, add this line, and save; this causes N6 to report itself as Nav4.75 pref("general.useragent.override","Mozilla/4.75 [en] (Macintosh; U)");
One problem may be that Macromedia's Netscape Enterprise server is handing back a HTTP/1.1 302 Moved Temporarily for the welcome page. No wonder if fails but works on reload of orriginal page. Continuing to investigate..... Send 734 bytes. <00000000< GET /bin/shockwave/visitor/welcome.jsp?first=sdfafs&last=safsaf& <00000040< email=asffs%40safas.com&pref=y&lang=en&age=0&url=http%3A%2F%2Fpo <00000080< ppy.macromedia.com%2Fnetlanski%2Ffiles%2FMovie%2Fmudball.dcr <000000BD< HTTP/1.1 <000000C7< Referer: http://poppy.macromedia.com/netlanski/files/Movie/mudba <00000107< lldcrDoc.html <00000116< Cookie: macromedia_member_id=42339042,fad8619ee711623aea15150a53 <00000156< 2dbe77; auto_login=1; vid=80c23ef8.22181.3a557fa3.17841; <0000018F< net6_warning=1; flash5up_total=3 <000001B1< Host: www.shockwave.com <000001CA< User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.8.1+) <00000208< Gecko/20010419 Netscape6/6.5b0 <00000228< Accept: */* <00000235< Accept-Language: en <0000024A< Accept-Encoding: gzip,deflate,compress,identity <0000027B< Accept-Charset: ISO-8859-1, utf-8; q=0.667, *; q=0.667 <000002B3< Keep-Alive: 300 <000002C4< Connection: keep-alive <000002DC< Receive 351 bytes. >00000000> HTTP/1.1 302 Moved Temporarily >00000020> Server: Netscape-Enterprise/4.1 >00000041> Date: Thu, 19 Apr 2001 22:02:04 GMT >00000066> Location: http://www.shockwave.com/bin/shockwave/account/welcome >000000A6> /welcome.jsp?first=sdfafs&last=safsaf&email=asffs%40safas.com&pr >000000E6> ef=y&lang=en&age=0&url=http%3A%2F%2Fpoppy.macromedia.com%2Fnetla >00000126> nski%2Ffiles%2FMovie%2Fmudball.dcr >0000014A> Connection: close >0000015D>
unsetting Target Milestone (forgive the trespass) so this doesn't show up as something that needs fixing for Mozilla 0.9
Resetting target to 0.9. We're working to resolve this as best as possible! :-) -- akr
Creating a dependency with 57012 till it can be determined that it is no longer a blocker. Input from Shockwave?
Depends on: 57012
created a dependency on 76771 till mtomlin tells us that this bug won't block installer issues.
Depends on: 76771
Depends on: 56297
Depends on: 56171
I've created dependencies: most have been marked FIXED | VERIFIED except 76771 (see dependency tree). Despite their FIXED | VERIFIED status, mtomlin's team seems to think that they aren't fixed quite yet. Has the Regression Monster spiked our Kool-Aid (t.m.)? I am in the process of determining whether further dependencies are necessary -- as mtomlin says: "We would like to work with you and your team to resolve all of these issues. It seems that streaming and keyboard commands and javascript submit are all still not functioning." I would like to know how crucial these are for installer issues, and am discussing this with mtomlin currently -- can we go ahead without them? etc.
68756 added as dependency (see dependency tree). Appears to work in peterl's local debug builds but not other builds :-( Regression...
Depends on: 68756
Arun, if this is just a tracking bug, could you move it off of 0.9 radar, and replace it with any dependencies that do need to be fixed for 0.9? thanks
In fact, this is a bit more complicated than a tracking bug, since it is the evangelism bug about skewed installers for Macromedia. We'd like this discussion to be completed in time for 0.9. It can only be closed if they fix their installer, which is dependent on all the bugs which themselves are dependencies of this bug. So this is an evangelism bug, with dependencies -- should I still move it? If so, to 0.9.1?
<a href="show_bug.cgi?id=76769">76769</a>, which is a dupe of <a href="show_bug.cgi?id=5522">5522</a>, has been added as dependency. Shrirang has found the desired test-case (see dependency tree).
Depends on: 76769
yes, lets move this off the 0.9 radar since we don't have any thing to do on our side.. thanks
Target Milestone: mozilla0.9 → mozilla0.9.1
copying my comments from bug 57012 here upon peter's request: On Mac build 0423, with the 8.5 shockwave installer and preset memory sizes for mozilla (20m and 28m for minimum and preferred sizes) Steps: 1 The installer recognised ns6 on my desktop and proceeded with the installlation 3. I was prompted with a message saying 'the browserrequires a larger memory partition to run shockwave. Click OK and the installer will increase the partition.' 4 Clicked OK 3 The browser restarted with my home page 4 I went to the test url above to complete the registration and load the movie 5 As soon as the registration update dialog opened up, another error dialog opened in front of it saying" An error aoccured while contacting www.macromedia.com. Pls try again later" The browser just freezes after that(crashes too sometimes). Works ok on windows (except for the known issue of the installer looking for 'netscape.exe').
is this going to work for 0.9.1 and the betas that come off that branch?
choffman, we're currently negotiating this on a "bug fix" basis -- e.g. peterl is working on a few bugs that are important to making this happen. There are some dependencies. In particular, look at Bug 76771 and Bug 77572.
Depends on: 77572
this shouldn't be on any '0.9.1 stopper' or beta stopper radar. moving to 0.9.2 in the hopes that we're close to resolving the outstanding issues.
note that though i've moved it to 0.9.2, the remaining bugs which are dependencies such as bug 76771 and bug 77572 are TFV 0.9.1 (considered stoppers).
Target Milestone: mozilla0.9.1 → mozilla0.9.2
This should be 0.9.3 or later as per the postings on n.p.m.builds. Also, why is shrir listed as qa contact for this?
Target Milestone: mozilla0.9.2 → mozilla0.9.3
zach, this one ought to be treated as an exception since the two dependency bugs are "hot" (t.m.) and on the 0.9.1 radar. shrir gets listed as QA since this was probably originally a plugins bug and he gives final benediction to the checkins (e.g. VERIFIED).
Ok, I won't disagree with that logic.
Target Milestone: mozilla0.9.3 → mozilla0.9.2
I see that all bugs this one depends on are solved. Doesn't that mean that this bug itself is solved? Or maybe it is the case but we are waiting for the next milestone to declare it as fixed? It would be nice to have a little status update here. Pleeaase!
Status Update: Feedback from Macromedia about bug fixes has been positive. I'm still trying to negotiate this one, and am coordinating my efforts with mtomlin and mgeller from the macromedia side. From our side, bug fixes have taken place, but it's still necessary to keep this open so that Shockwave can verify fixes. Some may need to be reopened for example. I'll close this one finally when the shockwave installer is fixed :-) i believe we're quite close now.
Another bug has become a dependency of this bug :-( Just spoke to mtomlin and she believes that bug 58128 is definitely a blocker.
Depends on: 58128
Adding bug 85334 to the dependency list. I hope I'm right.
Depends on: 85334
To set have Shockwave.com set a cookie and unblock Netscape 6.x, go to this URL: http://www.shockwave.com/bin/shockwave/entry.jsp?skip=net6
pushing out. 0.9.2 is done. (querying for this string will get you the list of the 0.9.2 bugs I moved to 0.9.3)
Target Milestone: mozilla0.9.2 → mozilla0.9.3
The last dependency was fixed a week ago. Why don't we fix this one?
Added dependency to bug 89493, which blocks 3DGroove, a shockwave component, from successful install.
Depends on: 89493
All dependencies are now fixed. I'd like to get confirmation from Shockwave.com that all our outstanding issues are resolved -- so I'm keeping this open for a week from today, before I close.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Target Milestone: mozilla0.9.4 → ---
Version: other → unspecified
I just put my vote back... waiting for the closing... Arun, how is it going?
Patrick, Finally, let's close this bug. Shockwave.com unblocks N6.1/Moz' as of today, 08/21/01.
Status: NEW → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → FIXED
Does it mean that the installer is ready for this and that we can go and download it? If so, that is great news!
yeah, just verified on windows trunk 0821...and the installer does work on 6.1 as expected. Filed a minor issue found while testing this. Will verify on mac trunk soon and mark verif.
verified fixed..works now
Status: RESOLVED → VERIFIED
When going to their download page, we still get a "We are unable to locate a single Web player that best matches your platform and operating system." Is that in the scope of another bug?
I think Shockwave may be blocking us again? See bug 113887.
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.