Re: [GLE-general] Problems with QGLE on windows 10

[Laurence A. <lau...@yo...>]

Thanks for the suggestion. As you say (and I also suspected but had yet to
check!), it seems that QGLE doesn't like the most recent versions of
ghostscript for some reason.

I couldn't locate version 8.22 anywhere but found 9.05 on sourceforge (a
version that is working on an older PC) and that seems to work fine for me
on the new PC.

Cheers,

Laurence

On Mon, 12 Aug 2019 at 12:16, Zbigniew Kisiel <ki...@if...> wrote:

> Laurence,
>
> On a recent vanilla Win10 installation on new laptop I found that the
> latest ghostscript that was compatible with QGLE was v.8.22.
>
> Best,
>
> Zbyszek
>
>
>
> On 12-08-2019 12:29, Laurence Abbott via Glx-general wrote:
> > Hi,
> >
> > I'm in the process of replacing some computers that were running
> > windows 10 for some that are still on windows 10 but a lot more locked
> > down.
> >
> > Having installed gle (either the VC or the other version) and
> > ghostscript 9.27, gle itself works (run from the command line or
> > launched from, e.g., notepadd++) but QGLE gives me issues...
> >
> > It will initially open a gle file (from double-clicking on it)and will
> > draw it fine, and I can edit the file and QGLE updates the figure as
> > expected. However, if I try to zoom in it crashes with something along
> > the lines of:
> >
> >
> > The following is the error code and memory location of the error.
> >
> > We use this to find the line in GLE's source code where the error
> occured.
> >
> > Error code 0xc0000005 in module gsdll32.dll at 0023:1021e4ec.
> >
> > Read from location 00002126 caused an access violation.
> >
> > Stack trace:
> >
> > Call: 0x1021e4ec (module gsdll32.dll)
> >
> > StackWalk end offset: 1021e4ec - error code = 299
> >
> > GLE version: 4.2.5.
> >
> > Time: 08/12/2019 11:18:12.
> >
> >
> >
> > Once this has happened, QGLE immediately gives the error when I try to
> > restart it.
> >
> > The same thing happens when I try to change the display resolution
> > within QGLE, and it happens with whatever (working) gle file I try.
> >
> > Has anyone come across this issue? If so, did they manage to sort it
> > out? Running QGLE from the command line gives no helpful output.
> >
> > It's a bit of a problem for me: gle is the main application we use to
> > generate all publication figures! I use it under linux. My boss on the
> > other hand..!
> >
> > Cheers,
> >
> > Laurence
> > --
> > Dr Laurence Abbott <lau...@yo...
> > <mailto:lau...@yo...>>
> > Department of Chemistry,
> > University of York,
> > YO10 5DD, UK
> >
> >
> > _______________________________________________
> > Glx-general mailing list
> > Glx...@li...
> > https://lists.sourceforge.net/lists/listinfo/glx-general
> >
>
>
> _______________________________________________
> Glx-general mailing list
> Glx...@li...
> https://lists.sourceforge.net/lists/listinfo/glx-general
>


-- 
Dr Laurence Abbott <lau...@yo...>
Department of Chemistry,
University of York,
YO10 5DD, UK