From owner-freebsd-hackers Tue Apr 2 11:02:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA15887 for hackers-outgoing; Tue, 2 Apr 1996 11:02:10 -0800 (PST) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA15857 Tue, 2 Apr 1996 11:01:58 -0800 (PST) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id MAA27113; Tue, 2 Apr 1996 12:56:39 -0600 Received: from tserv.lodgenet.com(204.124.120.10) by bacall via smap (V1.3) id sma027107; Tue Apr 2 12:56:19 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by tserv.lodgenet.com (8.6.12/8.6.12) with ESMTP id MAA10688; Tue, 2 Apr 1996 12:09:16 -0600 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id MAA13315; Tue, 2 Apr 1996 12:22:24 -0600 (CST) Message-Id: <199604021822.MAA13315@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: DARREND@novell.com (Darren Davis) cc: hackers@freebsd.org, current@freebsd.org Subject: Re: COFF 386 X Windows application. In-reply-to: Your message of "Tue, 02 Apr 1996 08:40:19 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Apr 1996 12:22:23 -0600 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk AFAIK sysi86 isn't working at all, except to tell you that it isn't ;). I think you're confusing sysi86() with vm86(), I did too, 'til I read the SCO man page. sysi86() works kind of like an ioctl in a driver, it provides a bunch of different commands that may or may not return useful stuff. From sco's function 114 is ``get os features vector'', whatever that is. Other common uses are get/set swap info and status, get/set hardware clock, SCO's vm86() interface is accesed through this, the ldt/gdt manipulation stuff is done this way too. Many of the functions provided by sysi86() are available on FBSD in other ways, some aren't. It'd be a good exercise to cast those that are available to the sysi86() emulation. I'd call it an `entry level kernel hack'. For your app, you might want to just have sysi86() return a success value, and see what happens. I'm not sure what the app expects back from a `get os features' call, maybe something as usless as a uname, or maybe the whole app depends on it. good luck, eric. Darren Davis writes: >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). > >Darren R. Davis >Senior Software Engineer >Novell, Inc. > > > -- erich@lodgenet.com erich@rrnet.com