Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!munnari.oz.au!uhccux!uhunix1.uhcc.Hawaii.Edu!todd
From: todd@uhunix1.uhcc.Hawaii.Edu (Todd Ogasawara)
Newsgroups: comp.lang.prolog
Subject: Re: Arity/Prolog & DOS 4.X? (RESOLVED)
Message-ID: <11275@uhccux.uhcc.Hawaii.Edu>
Date: 3 Feb 91 00:52:27 GMT
References: <11137@uhccux.uhcc.Hawaii.Edu> <8144@castle.ed.ac.uk> <11204@uhccux.uhcc.Hawaii.Edu>
Sender: news@uhccux.uhcc.Hawaii.Edu
Organization: University of Hawaii
Lines: 32

In article <11204@uhccux.uhcc.Hawaii.Edu> todd@uhunix1.uhcc.Hawaii.Edu (Todd Ogasawara) writes:
>In article <8144@castle.ed.ac.uk> own@castle.ed.ac.uk (O Morgan) writes:
>>In article <11137@uhccux.uhcc.Hawaii.Edu> todd@uhunix1.uhcc.Hawaii.Edu (Todd Ogasawara) writes:
>>>I found much to my dismay that Arity/Prolog 5.1 does *NOT* work under
>>>MSDOS 4.0 (although it works fine under MSDOS 3.3).
>>It works if you specify the /K parameter with your DEVICE=ANSI.SYS
>>statement in the CONFIG.SYS file (ie: DEVIVE=ANSI.SYS/K)

I received my Gateway 2000 33MHz 386 running MS-DOS 4.01 yesterday and
was able to test out the suggestions offered on here (thanks to all!).

My problem was that Arity Prolog 5.1 Interpreter locked up whenever I tried
to run it on a machine using MS or PC-DOS 4.0x. Several people suggested
using the ANSI.SYS /K parameter. This parameter, the DOS documentation
says, turns off extended keyboard functions on an enhanced keyboard. While
this allowed me to get a 'little' further in using API, it still caused
lock ups under certain conditions.

One person suggested placing the line

	kbdriver=no

in an ENV file (API.ENV for the interpter). This suggestion to use this
undocumented Arity environmental variable worked just fine for me.

Thanks to all for the help. Now, I can at least use Arity Prolog 5.1 on my
new machine until 6.0 appears....todd
--
Todd Ogasawara, U. of Hawaii
UUCP:		{uunet,ucbvax,dcdwest}!ucsd!nosc!uhunix!todd
BITNET:		todd@uhunix
INTERNET:	todd@uhunix.UHCC.HAWAII.EDU