Xref: news-dnh.mv.net comp.os.msdos.djgpp:2559
Path: news-dnh.mv.net!mv!news.sprintlink.net!mhv.net!news.westnet.com!news-out.internetmci.com!newsfeed.internetmci.com!news.mathworks.com!zombie.ncsc.mil!simtel!chi-news.cic.net!news.uoregon.edu!cs.uoregon.edu!usenet.ee.pdx.edu!not-for-mail
From: idr AT cs DOT pdx DOT edu (Dancing Fool)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Wierd problems with VESA interface under DPMI
Date: 10 Oct 1995 17:11:24 -0700
Lines: 16
References: <DG8n7A DOT 9rD AT jade DOT mv DOT net>
Nntp-Posting-Host: sirius.cs.pdx.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

"Iota (Tom Wenisch)" <FRITZW AT URIACC DOT URI DOT EDU> writes:

>I'm having a truly strange problem getting some VESA-based graphics code to
>work.  The strange thing is, when stepped through in GDB, the code runs
>flawlessly, but when run from the command line, the code crashes DOS, WIN95,
>and every configuration and memory manager I have on my system.

One problem, and this is one that I've had, is you need to set SS and SI
to 0 in the DPMI registers structure.  If you don't, the real mode code
will use whatever happens to be contained in them as a stack pointer. 
Probably not what you want. :)
-- 
- See the Epsilon coder page at:           ____  ____
  http://www.cs.pdx.edu/~idr/             /     /   / /\    / "Good...bad...
- Ian Romanick sez:                      /---- /___/ /  \  /   I'm the guy
  "For the last time, GIVE ME THE BOX!" /____ /     /    \/    with the gun."