Well Windows is weird. I just shut down and re-booted the system, and the 
problems disappeared. Sorry to have bothered people.

 

Peter

 

From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Ben 
Coman
Sent: 15 July 2017 15:39
To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Subject: Re: [Pharo-users] Mysterious problem in loading Pharo

 

Maybe revew recent Windows 10 updates...

http://www.sysprobs.com/how-to-view-installed-updates-on-windows-10-8-1-server-2012

 

cheers -ben

 

On Sat, Jul 15, 2017 at 6:26 PM, PBKResearch <pe...@pbkresearch.co.uk 
<mailto:pe...@pbkresearch.co.uk> > wrote:

Hello

 

I have a problem in loading Pharo images which, until yesterday, loaded without 
difficulty. All the images showing the problem are Pharo 6 with the Cog VM; 
older images do not seem to be affected.

 

The first sign of a problem is that, as soon as I start the image, the debug 
console appears, with several repeats of the message: 

LoadLibrary(FT2Plugin.dll) (998: Invalid access to memory location.)

The other strange thing is that the appearance of some opened windows has 
changed. Most obviously, the three icons at the top left (close, minimise, 
expand) are very close together. Also, I think the print size has got a bit 
smaller, though this is not obvious.

 

I have recently reinstalled some components of Pharo and Moose, trying to solve 
my problems with PunQLite, so I wondered if I had fouled something up. To 
check, I made a completely new install of Pharo 6 (#60508) from the Pharo 
download page in a separate folder. When I start the image, both the strange 
things above are present, plus a debug window with the message; ‘FT2 Error: 
Freetype2 primitive failed’.

 

So it looks as though something has happened to my system which means that any 
Pharo 6 image will show these oddities. The images I have tried seem able to 
run some of my functions correctly, so it’s all to do with appearance.

 

I am running on Windows 10 with all recent updates. There was a major update of 
Windows late yesterday, so it may be that the problems appeared then. Does 
anyone have any suggestions?

 

Many thanks

 

Peter Kenny

 

Reply via email to