From:	Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com>
Subject:	Re: Another array-writing interrupt not catered for by G032
To:	A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk (A.Appleyard)
Date:	Fri, 13 Jan 1995 10:23:07 -0600 (CST)
Cc:	DJGPP AT sun DOT soe DOT clarkson DOT edu

> C:\DJGPP\CONTRIB\LIBGRX\NDRIVERS\DOCS\VESA.DOC . Its section 6.3 describes an
> interrupt `AX=0x4f01, CX=n, int10' which writes to addresses ES:DI etseq much
> necessary information about the Super VGA screen mode n. But when I tried to
> use it, it did not write any info. In the end I found the two info items that
> I was wanting (window granularity and window size for my PC's screen's mode
> 0x64) by trial and error; but this is awkward. In my C:\DJGPP\GO32\EXPHDLR.C,
> the function i_10() which handles int10 interrupts, checks for ax==0x1100 and
> ax==0x1110 (user-define a font character), but not for any other array-using
> interrupt. i_10() should also cater for ax==0x4f01, int10, e.g. as follows
> (which may need correcting by someone more skilled in programming for G032):-

Use _go32_dpmi_simulate_interrupt, don't edit GO32.  GO32 goes away
in V2, custom GO32's are a nightmare, so there are lots of good reasons
to avoid this.

- Raw text -