Closed Bug 18656 Opened 25 years ago Closed 24 years ago

pdf files don't launch unless dll is manually added to plugins folder

Categories

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

x86
Windows NT

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: kirsten_fundanish, Assigned: serhunt)

References

Details

Attachments

(1 file)

Although netscape 4.6 finds and launches the inso quick view plus and adobe
acrobat reader plugins, i cannot get the new m10 build id:1999100618 browser to
recognize the file types that either one should be launched for.  It comes up
with unknown file type box (for example saying that application/msword is
unrecognized)when viewed thru a html page that sets the mime type, or just views
it as junk if i view it right off the hard drive.  Although i am only interested
in running the quick view plus plugin, the adobe reader plugin is a standard for
comparison...
To find the quick view plus plugin you can go to www.jasc.com and download quick
view plus version 5.
Assignee: leger → av
Component: Browser-General → Plug-ins
QA Contact: leger → elig
setting component and QA contact.
Shrirang is now QA owner for Plug-ins; QA assigning all of my Plug-ins bugs over
to him.
Status: NEW → ASSIGNED
Target Milestone: M13
Target Milestone: M13 → M14
I think association between file extension and mime type is not in yet. 
I have trouble finding a right component for that, so hope Browser-General 
person would know better. As far as I remember there used to be something like 
MIME component before?
Assignee: av → leger
Status: ASSIGNED → NEW
Component: Plug-ins → Browser-General
QA Contact: shrir → leger
av@netscape.com - you mean the plug-in component perhaps?
Moving to plug-ins, and assigning to the owner of the selected component.
Possible Beta1?
Assignee: leger → av
Component: Browser-General → Plug-ins
QA Contact: leger → shrir
Target Milestone: M14 → M15
The adobe acrobat plugin works fine with today's commercial beta1 build on 
windows(2000032206). I can launch and read a '.pdf' file perfectly fine and with 
no crash or "Unknown File Type" Dialog. 
 Firstly, manual addition of the adobe plugin dll file needs to be done for 
adobe plugin to work in mozilla on windows. As the 'MIME settings' are not 
enabled in mozilla as of now, acrobat files will not launch in the ACROBAT 
READER as a seperate application(since Helper Applications are not working) and 
that's why you are seeing the 'Unknown File Type" dialog. But if the 
"nppdf32.dll" file is copied in the Plugins folder under either mozilla 
installation or any existing 4.x installation, then the browser will launch 
Acrobat Reader as a plugin and show the .pdf file since plugin detection logic 
on windows is fixed. 
 Also, it would be worthwhile to mention that the beta1 document from marketing 
requires only Shockwave Flash and Realaudio plugins to work on windows.
Also see bug 18679 regarding crash on Acrobat plugin.

Am marking this one WORKSFORME.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
marking Verified.
Status: RESOLVED → VERIFIED
Reopening for release note, changing summary. 
Severity: critical → minor
Status: VERIFIED → REOPENED
Keywords: beta2, relnote
Resolution: WORKSFORME → ---
Summary: plugins not being launched, files are coming up as unrecgnozied. → [ACROBAT] pdf files don't launch unless dll is manually added to plugins folder
Blocks: 33833
Shrirang, what is the story?
Target Milestone: M15 → M17
Installed Acrobat Reader 4.0.5 and don't see this problem anymore as the plugin 
dll gets added automatically to the netscape plugins folder. Marking this one 
worksforme.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
Keywords: nsbeta2
verified (2000072811m17)
Status: RESOLVED → VERIFIED
Keywords: relnoteacrobat
Summary: [ACROBAT] pdf files don't launch unless dll is manually added to plugins folder → pdf files don't launch unless dll is manually added to plugins folder
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: