Closed Bug 51812 Opened 26 years ago Closed 25 years ago

Error message appears after installation and before launching the browser

Categories

(Core Graveyard :: Plug-ins, defect, P3)

x86
Windows NT

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: shrir, Assigned: serhunt)

References

()

Details

Windows build 2000090704m18 Steps: 1 Go to the url above 2 Go through the steps for installation 3 At the end, when the installation is almost done, notice a dialog titled "Installing Shockwave" stating "Click hte continue button to launch your browser and download the remaining shockwave 8.0 files" appears 4 Click OK and an error messag appears " Cannot find the file 'C:\program files\NETSCA~1\Netscape.exe' ( or one of its components). Make sure the path and the filename are correct and that all required libraries are available." Should the plugin not be looking for netscp6.exe ? Is this problem because macromedia is not yet supporting unreleased browsers? cc'ing kiwi@macromedia.com. The installation however puts the necessary plugin files in the mozilla plugins folder and the plugin works fine.
Whatever it is this is most likely the Shockwave installer problem. Shrirang, could you please doublecheck that the actual plugin ends up in the Mozilla plugins folder, or you concluded this from the fact that the plugin is working?
Andrei, I verified that the plugins ended up in the mozilla plugins folder (since this was the path I specified for the plugin to get installed, which actually did). As you said, I too feel this is a installer problem that is searching for 4.x executable to relaunch the browser after installation. I will recheck today again that the plugin really does get installed in the mozilla folder and comment soon.
Keywords: 4xp
marking invalid..since shockwave folks need to come up with 6.0 api compatible plugin. Not a problem with seamonkey.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
verif.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.