From owner-freebsd-current Tue Apr 2 12:21:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA23256 for current-outgoing; Tue, 2 Apr 1996 12:21:34 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA23250 Tue, 2 Apr 1996 12:21:28 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA16934; Tue, 2 Apr 1996 13:16:02 -0700 From: Terry Lambert Message-Id: <199604022016.NAA16934@phaeton.artisoft.com> Subject: Re: COFF 386 X Windows application. To: DARREND@novell.com (Darren Davis) Date: Tue, 2 Apr 1996 13:16:02 -0700 (MST) Cc: hackers@FreeBSD.org, current@FreeBSD.org In-Reply-To: from "Darren Davis" at Apr 2, 96 08:40:19 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > OK, here's the scoop. I have an X windows application that is a 386 COFF > binary. When run from X, the application hangs. The message printed on > the console is: > > IBCS2: 'sysi86' function 114(0x72) not implemented yet > > Does current have support for this? What is a person without source to > the application to do? (woe is me). I really would like to get this working. > If I remember rightly, Terry was stating something like the sysi86 function > doesn't fully work or something like that if my memory serves me. I believe > I have my IBCS emulation stuff set up correctly (I followed the FAQ). Most of the sysi86 functionality is a hack Sean Eric Fagan put together for the call that does math coprocessor detection; specifically, it was as a result of a bug report that I made when I was running WSU's SVR3 Lotus 1-2-3, Word Perfect, and Sybase packages under IBCS2. Basically, sysi86 is what SCO calls their VM86() interface to allow protected mode programs to make DOS calls. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.