Michael Kaply wrote:

> This sounds like eactly the problem we are talking about.
>
> Could you check your system to see if you have another JPEG.DLL which is
> being loaded by Mozilla instead of the one it needs?

Oops, sorry that my fault...

I just used SET BEGINLIBPATH=c:\warpzilla\bin

and it did work.

Subsequently I ran unset this variable and ran

which -l jpeg.dll

and got:-

c:\xfree86\lib\jpeg.dll

It would be great if you could use the same set of DLLs as XF/2, assuming they
are
functionally equivalent.


>
> Thanks
>
> Mike Kaply
>
> John Poltorak wrote:
>
> > Michael Kaply wrote:
> >
> > > I believe the solution to these problems is not to rename the DLLs but
> > > to figure out why Warpzilla cannot use the "standard" versions of these
> > > DLLs.
> > >
> > > I'm asking for help here in figuring this out.
> >
> > I get a SYS3175 in JPEG.DLL whenever a JPG file is encountered.
> >
> > Will you make a seperately downloadable JPEG.DLL if/when there is a fix?
> >
> > > hanks
> > >
> > > Mike Kaply
> > > IBM
> >
> > --
> > John

--
John


Reply via email to