From:	"Chris A. Triebel" <cat AT sun4 DOT iol DOT unh DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	ALLEGRO||DJGPP: virtual memory error in 'new'
Date:	Fri, 3 Jan 1997 08:45:55 -0500
Organization:	University of New Hampshire - Durham, NH
Lines:	45
Message-ID:	<Pine.SUN.3.91.970103082300.10414A-100000@sun4.iol.unh.edu>
NNTP-Posting-Host:	sun4.iol.unh.edu
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I am having a problem that I can't seem to fix.  Pardon my ignorance if 
this is common sense to other people.

I had a problem with my hard drive and since I don't currently have a 
backup drive I had to salvage as much of my own programming as I could in 
a minimum of disk space.  So at any rate only the source code survived.
Then I blew away the hard drive and went from a clean copy of DOS 6.?

I downloaded a clean copy of djgpp and everything needed to compile C++ 
( plus allegro ).  I had an old copy of a program which compiled and ran 
fine before this change, I recompiled it ( it relies on allegro ) and ran 
it.  It immediately died throwing something to the affect of what is on 
my subject line above ( and spitting out the registers and stack trace ).  

I can't figure out what the problem here is.  I checked the faq and saw a 
few pertinent details, but since I am using DOS6 and EMM386 and HIMEM 
from it I can't see that they are conflicting.  I checked that MEM 
reported the full 20 Megs of XMS memory I required, and even changed some 
of that over to EMS.  I even removed HIMEM, and EMM386 individully.

I checked double-checked the hard drive to make sure that it wasn't full.

I remember that there are some params for cwsdpmi to check on what it 
sees as available for memory, and adjusting those details.  Could someone 
pass along where to find these params and their usage, if available.  I 
searched through the faq and info base but couldn't find any reference to 
them.  I did skim through the cwsdpmi.txt, am I missing something here?

I am not sure where the problem is centralized.  I ran all the allegro 
tests as well as a number of the djgpp tests to see if they work, there 
doesn't seem to be a problem with them.

Oh, another point that may be insignificant.  When I installed print.com 
( so that I could print the error message from the screen ) the program 
reported the same error but quit quietly back to DOS without giving me a 
stack trace.

Another minor point is that allegro doesn't restore text mode when it 
dies, and doesn't report that it caught the error.  In the previous 
system it did.  Not sure if that means anything here, but more info can't 
hurt.  

If anybody has any ideas, please let me know.

cat

- Raw text -