www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/08/13/08:36:04

Date: Tue, 13 Aug 1996 13:45:01 +0200 (MET DST)
From: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Reply-To: grendel AT ananke DOT amu DOT edu DOT pl
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
cc: orly AT gibson DOT eee DOT upd DOT edu DOT ph, alaric AT abwillms DOT demon DOT co DOT uk, djgpp AT delorie DOT com
Subject: Re: TVision + UNIX question
In-Reply-To: <9608121702.aa08028@ailin.inti.edu.ar>
Message-ID: <Pine.NEB.3.95.960813133759.18471A-100000@ananke.amu.edu.pl>
MIME-Version: 1.0

 On Mon, 12 Aug 1996, Salvador Eduardo Tropea (SET) wrote:

Howdy to all you guys,

>>  http://brooks.wvn.wvnet.edu/tvhome/tvfiles.htm
>>>library? I'd like to try my hand at building Curses wrappers for it so
>>>that we can all have RHIDE for UNIX (drool..)
>>I think, that with Robert's port of TV you don't need to change almost
>>anything in TV 1.03 sources to compile it under UNIX (except, of course, for
>>the MS-DOG stuff)
>
>  Well the M$-DOG stuff is a hard problem here is a list of things that must be 
>modified to compile TV under UNIX:
>
>1) The screen routines in view.cc, this routines uses the PrimaryScreen, etc 
>and the dosmem... routines and buffers.
>2) The rest of Screen class to switch between video modes, etc.
>3) The mouse system, actually uses Int 0x33.
>4) The keyboard system, actually uses BIOS, in this point you can adapt some of 
>the libkbd-09 (or some thing like this), this routines supports Linux and have 
>an amaizing control over the keyboard (at least under DOS).
Still all these things are PC-related. As long as the only wish is to enable
TV to run on PC UNICES all these can be achieved applying minor changes (at
most cases just specific function calls). You may use BIOS for keyboard unless
you care for national keyboard layouts and in this case, yes, libkbd-100 (!)
will perfectly do. Mouse system is the one thing that'd be written almost from
scratch - actually the THWMouse class. All the PC Unices impliment calls
allowing user to gain access to physical memory (i.e. map a physical device)
so gaining access to e.g. screen would just be a matter of changing the code
that gets the pointer to the area - the rest remains untouched.

>
>  The 90% of the codes remains untouched, but you must get access to Screen, 
>Mouse and Keyboard, these thing can be achived with the SVGALib.
>

>Notes: 
>a) I'm interesed on a port of RHIDE to Linux.
>b) I made a program in Linux that uses screen, mouse and keyboard using the 
>SVGALib, is a GIF viewer with scroll using the keys and or the mouse.
So it seems that main elements are mastered ;-)) All that remains is to
compile the stuff and test it.

Greetings, Mark

/************************************************************/
/** Maybe it was infatuation or the thrill of a chase?   **/          
/** Maybe you were always beyond my reach and my heart **/
/**   was playing safe?                     ***********/ 
/** But was that love in your eyes I saw, **/
/**   or the reflection of mine?        **/
/** I'll never really know for sure,  **/
/** You never really gave me time!  **/
/** Won't you give me that time?  **/ 
/**          "Cindirella Search" **/
/********************************/
Visit my homepage: http://ananke.amu.edu.pl/~grendel

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019