To:	djgpp AT delorie DOT com
Subject:	Re: Calling real mode far procedures
Message-ID:	<19961230.165913.4975.1.chambersb@juno.com>
References:	<32c563f9 DOT 7993249 AT ursa DOT smsu DOT edu> <19961229 DOT 134952 DOT 8351 DOT 2 DOT chambersb AT juno DOT com>
	<19961230 DOT 105918 DOT 4983 DOT 11 DOT chambersb AT juno DOT com>
From:	chambersb AT juno DOT com (Benjamin D Chambers)
Date:	Sun, 29 Dec 1996 19:54:32 EST

On Sun, 29 Dec 1996 13:54:29 EST chambersb AT juno DOT com (Benjamin D Chambers)
writes:
>
>On Sun, 29 Dec 1996 14:25:01 GMT aho450s AT nic DOT smsu DOT edu (Tony O'Bryan) 
>writes:
>>On Sat, 28 Dec 1996 21:45:51 GMT, chambersb AT juno DOT com (Benjamin D
>>Chambers) wrote:
>>
>>>If you do, it's card specific.  The only one that's standardized is 
>>the
>>>VGA, and then you can't use svga modes.  For svga, you need specs on 
>
>>each
>>>card :(
>>
>>The interrupt call is a VESA standard.  VESA 1.1 includes a standard
>You mean the VESA VLB, right?  You wouldn't want to call the routine 
Sorry, meant VESA VBE :)
>directly from PM (as it would require a switch to RM, but so would the 
>int), but I believe VBE 2.0 supplies a PM pointer to the routine.

- Raw text -