Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!stlvm20.vnet.ibm.com!liebtag From: liebtag@stlvm20.vnet.ibm.com ("David Liebtag") Newsgroups: comp.lang.apl Subject: apl2/pc Message-ID: <9105141537.AA05023@ucbvax.Berkeley.EDU> Date: 14 May 91 15:26:32 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 51 From: felscher@MAPLOG.INFORMATIK.UNI-TUEBINGEN.DE Walter, I asked one of the APL2PC developers your questions and got these answers (slightly reworded.) 1. Having installed 386MAX on a PS2/80, invocation of both the 16bit and the 32bit version of APL2/PC caused the machine to stall. Apparently, certain high memory areas should be kept free. Is it known which ones, or which other remedy might be taken ? 386Max will run with the current 16 bit IBM Internal Use Only level (which will be available to customers in the fairly near future) but will not run with the currently available product level. The 32 bit level of APL2PC will never co-exist with 386Max because it uses the VCPI interface the same as QEMM. Supporting co-existence would require a major rewrite of the interpreter control code. The 16 bit level will require a 387 to operate as I {the developer} suspect the emulator won't function. It {the emulator} switches a bit in the CR0 register to make the CPU inform us {the interpreter} every time it sees an FPA instruction. But, you must be running priviledged. In normal DOS mode you are, but when one of the 386 styl programs runs, you aren't in control anymore. We can provide more detail if required. 2. Having installed the cache programm HyperDisk 4.21, the 16bit version worked allright, but the 32bit version came up with immediate WS FULL and no response to commands - though, fortunately, )OFF still did work. Any known remedy ? This sounds like a case of Hyperdisk not using a recognized method of identifying the highmemory area it has allocated. We will work with two methods: Remap of int 15h or Vdisk. The latter is used by such programs as IBMCACHE. If you need further details, please write another article and I will try to get more information. Regards, David Liebtag IBM APL Products