Return to BSD News archive
Xref: sserve comp.unix.sysv386:23469 comp.windows.x:44866 comp.os.linux:9535 comp.os.mach:2089 comp.unix.bsd:4709 Newsgroups: comp.unix.sysv386,comp.windows.x,comp.os.linux,comp.os.mach,comp.unix.bsd Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!kithrup!sef From: sef@kithrup.COM (Sean Eric Fagan) Subject: Re: Free software and the future of support for Diamond products Organization: Kithrup Enterprises, Ltd. Date: Tue, 08 Sep 1992 09:33:00 GMT Message-ID: <1992Sep08.093300.898@kithrup.COM> Keywords: Diamond, free-software References: <1992Sep6.210159.18607@cbnewsj.cb.att.com> <lalqmgINNa96@needmore.cs.utexas.edu> <1992Sep7.133347.4433@cbnewsj.cb.att.com> Lines: 18 In article <1992Sep7.133347.4433@cbnewsj.cb.att.com> dwex@cbnewsj.cb.att.com (david.e.wexelblat) writes: >1) Calling BIOS from a multitasking OS is trick, dangerous, and impossible > for those of us running SVR3/4 An interesting way to get around all of those: set up a v86 process that calls the BIOS routines for you. It can be done, and I've seen it (not for the card in question, however), although I don't recall enough to make any claims about performance. It probably requires some kernel help, however. There's more than one way to skin a cat, remember! -- Sean Eric Fagan | "You can't get lost in one room, no matter how sef@kithrup.COM | little effort you make to learn your way around." -----------------+ -- William E Davidsen (william@crd.GE.COM) Any opinions expressed are my own, and generally unpopular with others.