Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!helios!tamuts!x041sc From: x041sc@tamuts.tamu.edu (Sean Malloy) Newsgroups: comp.os.msdos.programmer Subject: Re: Memory Models in TC2.0 Message-ID: <17145@helios.TAMU.EDU> Date: 11 Jun 91 20:10:43 GMT References: <1991Jun6.164518.20769@borland.com> <1991Jun6.182748.27627@hubcap.clemson.edu> <1991Jun7.163057.28170@borland.com> Sender: usenet@helios.TAMU.EDU Organization: Petro-Marine Engineering of Texas, Inc. Lines: 41 Well, sorry I didn't post this response eariler, but things have been rather hectic around here recently... I'm the one who posted the original message about the problem with malloc(). I tried (on my own initative, thank you) nearly all of the suggestions that were posted/mailed to me. (most of them regarding a pointer type mismatch and/or the supposed non-declaration of 'malloc()'). In the larger models, farmalloc() seemed to work the same as malloc() [and this is consistant with my references] and the use of far is unnecessary, but what I posted was ~ the 20th thing I'd tried. Basically, I was thinking that the compiler was (for some reason) feeding me near pointers, and I was using brute force to make them all far. Messy, yes. Unnecessary, yes. After some discussion with a tech-rep at Borland [BTW - is there Internet tech-support from Borland? The telephone tag I played that day for more than an hour before I got to talk to a real person was nearly enough to make me go out and buy a copy of Microsoft C, just for the support...] we determined that my machine was running out of memory, even though malloc wasn't returning a NULL pointer. I turned on every warning (besides the ANSI stuff) that I could find, and made a few corrections... It worked... (well, malloc returned NULL at the place where it used to just fail... ;-) *sigh* now can someone recommend a decent extended memory manager... ;-) OR, does Borland have a product that will allow me to write in 32-bit protected mode? [I'd like to be able to easily address *all* my memory, thank you...] We have a copy of Metaware High C collecting dust here that is a 32 bit (protected mode) compiler, but no one around here has picked it up yet, and Borland's integrated debugger is a godsend from time to time... I'm a bit reluctant to use a compiler from another vendor if I can avoid it... Thanks for all the replies... after all that, it came down to a matter of the toy machine that I'm developing on... -Sean #include