From: "Campbell, Rolf [SKY:1U32:EXCH]" Newsgroups: comp.os.msdos.djgpp Subject: Re: (KII) - Program works under windows95 but not under dos? Date: Thu, 19 Aug 1999 11:15:44 -0400 Organization: Nortel Networks Lines: 32 Message-ID: <37BC1FA0.1AF894E1@americasm01.nt.com> References: <19990819094511 DOT 24744 DOT 00000851 AT ng-cj1 DOT aol DOT com> NNTP-Posting-Host: bmerhc00.ca.nortel.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.7 [en] (X11; I; HP-UX B.10.20 9000/712) X-Accept-Language: en To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Keith Weatherby II wrote: > Okay i'm working on a game with Allegro, and it works fine under a windows 95 > dos box, however whenever i go into dos mode (and try to run cwsdpmi.exe), when > I run my program it exits giving me a SIGSEGV, I ran symify, and below is the > results. Can anyone tell me what this stuff means? I will post the source > code to my program later if someone needs to look at it to help. I'm not doing > anything out of the ordinary for djgpp or allegro, so i couldn't understand > what could be wrong. > Also I noticed similar problems happening with the last couple of allegro > examples programs too. They will basically work under a win95 dos box but not > under dos mode itself. Note i'm running allegro version 3.11 (and i've just > reinstalled it) So does anyone have any ideas? > Thanks -Keith W. II I can only think of 2 common problems that would exibit this crash: 1) Your program accesses a NULL pointer. This is allowed (stupily) under Win95, but not allowed under cwsdpmi. And it looks like it happens in your load_pcx function. Triple check your code for uninitialized pointers or failed malloc's, especially in that function. 2) Your win95 video drivers run in a more stable way than the real card. This is unlikely, because usually it is the other way around, but the manufacturer of your card may have noticed a bug in the hardware and fixed it with the Win95 drivers. I really doubt this is your problem, but it is possible.. -- -Rolf Campbell (39)3-6318