From jan@swi.psy.uva.nl  Mon May 15 10:48:55 2000
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.152.30])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id KAA27137;
	Mon, 15 May 2000 10:48:55 +0200 (MET DST)
Received: from localhost (localhost [[UNIX: localhost]])
	by gollem.swi.psy.uva.nl (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id KAA07022;
	Mon, 15 May 2000 10:49:11 +0200
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Organization: SWI, University of Amsterdam
To: "Alan Maxwell" <alan@a-maxwell.freeserve.co.uk>
Subject: Re: Problems with Prolog v3.3.6
Date: Mon, 15 May 2000 10:46:40 +0200
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
References: <000001bfbdc4$7980ff40$934d883e@guardian>
In-Reply-To: <000001bfbdc4$7980ff40$934d883e@guardian>
Cc: prolog@gollem.swi.psy.uva.nl
MIME-Version: 1.0
Message-Id: <00051510491103.06671@gollem>
Content-Transfer-Encoding: 8bit

Someone else with this problem?  What is hookdll.dll?  Certainly
nothing of SWI-Prolog.

	Regards --- Jan

On Sun, 14 May 2000, Alan Maxwell wrote:

>I've been using SWI-Prolog v3.2.7 for a while and recently checked your page to find the new version v3.3.6 (for Win9x). I downloaded and installed this to replace my existing version but every time I close the Prolog application (v3.3.6) I now get the following error message from Windows:
>
>PLWIN caused an invalid page fault in
>module HOOKDLL.DLL at 0177:00b74e9c.
>Registers:
>EAX=000000cc CS=0177 EIP=00b74e9c EFLGS=00010212
>EBX=00000008 SS=017f ESP=011af718 EBP=00b7b1b8
>ECX=00b791a0 DS=017f ESI=00ca0000 FS=433f
>EDX=00000008 ES=017f EDI=00ca0000 GS=0000
>Bytes at CS:EIP:
>8b 47 04 8b 0f 3b c2 89 4c 24 14 8b f1 8d 9f f8 
>Stack dump:
>00b791b8 00ca0000 00b7b1b8 00000008 00b74c9e 00ca0000 000000cc 00000008 00000000 00000000 bff76ec4 00000080 00b791a0 00b7488d 00000008 00000000
>
>I am using Windows98 Second Edition and wondered if you could offer any advice as to the reason for this error, the previous version had no such problems? I am going to try the v3.2.8 version (which is slightly newer than my v3.2.7) to see if that has the same problem.

