Newsgroups: comp.os.msdos.djgpp
From: "Vladislav Tvarùek" <l-twada AT usa DOT net>
Subject: Re: int86x problems
Content-Type: text/plain; charset=us-ascii
Message-ID: <345D6FA4.64070915@usa.net>
Sender: news AT dior DOT ics DOT muni DOT cz (News Admin)
Content-Transfer-Encoding: 7bit
Organization: Masaryk University,Brno
References: <199710232245 DOT IAA27500 AT rabble DOT uow DOT edu DOT au>
Mime-Version: 1.0
Date: Mon, 3 Nov 1997 06:31:01 GMT
Lines: 42
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

I solve problem. You must use a __dpmi_int. I have a few examples but I don't have source
code with me. If you want this examples, send a mail to me.

Brett Porter wrote:

> > Later on, I try to get the vesa information like this:
> >
> >
> > union REGS regs;
> > struct SREGS sregs;
> >
> > regs.w.ax = 0x4F02;
> > regs.w.di = (unsigned short)&vesainfo;
> >
> > int386x(0x10, &regs, &regs, &sregs);
> > ^^^^^^^
>
> > According to what I read out of the faq this should work, except that I keep getting
> > SIGSEV errors.  Please help me and please hurry.
> >
> As far as I remember, the FAQ suggests using __dpmi_int for all real mode
> interrupt calls. And I think you will also have to set EDI not DI to
> (unsigned int)&vesainfo and the ES to _my_ds()... but I am not totally sure
> on this, because I can't remember if the DPMI server converts these back to
> their real mode equivalents. Sorry I am a little unclear but you said to
> hurry, so I couldn't go research it :) IT is probably worth a try, though.
> And Eli is bound to correct me if I'm wrong :)
>
> HTH
> Brett
>
> --
> "Who here believes in telekenesis? Raise MY hand!"
> --
> Brett Porter
> bporter AT rabble DOT uow DOT edu DOT au
>
> http://www.geocities.com/CollegePark/Union/3596
>         Humour, Programming, and more.