seems to have been asked, but...

[Ian Levy]

> perhaps the architecture might support an additional display driver - to
> which the
> information might be directed.

That's not what's required, though. You need to know what's going on on the 
screen, surely.

> Do we need to
> replace/modify the 
> current drivers, or just add an additional one of our own.

Modifying existing drivers is a non-starter. For a start, getting the source 
code would be tortuous (not everyone is as generous as ORL :->) and then you'd 
have to iron out all the bugs :->

The way to do this is to create a new video driver. All this driver will do is 
retrieve the information that VNC would like (ie the current invalid region etc) 
and then pass the function request on (unaltered) to the 'proper' display 
driver. The EngLoadImage function would be used to load the 'proper' driver in 
the context of out replacement driver, but I haven't figured out how to actually 
*call* anything in the old driver yet.
	
		Cheers
			Ian.
--  
Dr. Ian Levy, Dept Of Computer Science, University of Warwick, Coventry
  CV4 7AL  eMail: ian "at" dcs.warwick.ac.uk   SMS/Phone: +44370 428779
     FAX: +44370 429016    Urgent eMail: ian "at" emobile.co.uk  
         Err, that's DOCTOR short, fat bastard to you!


---------------------------------------------------------------------
The VNC mailing list     -   see http://www.orl.co.uk/vnc/intouch.html
---------------------------------------------------------------------