Thread: Accessing huge 2d array causes "general protection exception"

Far pointers fail in Windows XP, immediately. And they didn't get memory from the stack - they got it from the heap, but not on the same "page" of memory.

Memory constraints are a big problem in Turbo C, running under Windows XP. I like turbo C, and have used it since we were stealing T-Rex eggs for breakfast, but never found a way to use far pointers in Windows XP.

It does run fine, for small programs, but Tater is quite right - it's tipping over more and more, into final obsolescence, no matter how much I like it.

R.I.P. Turbo C!

Originally Posted by CommonTater

But, as everyone is telling you... that is some SERIOUSLY outdated hardware and software you're working with...

The compiler is 16 bits i.e 2 byte integers... and before long it will not be supported by new operating systems... 64 bit systems already refuse to run 16 bit code... 32 bit systems won't be far behind that. In fact, I'm guessing that in as little as 5 years new systems will not be supporting 32 bit code anymore...

Hardware wise you're stuck in the late 1980s... 20 year old machines for which you can't even get drivers or upgrades anymore.

If the only place your software is ever going to run is on your own computers that's all fine and dandy... but you have got to know that a LOT has changed since that was the "ultimate" setup and most of what you have there won't even run on newer machines.

Actually, my Borland C++ Compiler supports both 16 bit (short integers) and 32 bit (long integers), and as I already stated in an earlier post I plan on buying a new PC and leaning MS Visual C++. My current laptop is old, but I purchased it in the Fall of 1998 or 1999 (hence Windows98 Second Edition) and the 20 inch widescreen lcd monitor in the Fall 2009, so no my hardware is not from the late 1980s.

node101