Mail Archives: djgpp/2000/05/17/10:57:18
On Tue, 16 May 2000 20:40:03 GMT, "AndrewJ" <luminous-is AT home DOT com>
wrote:
>> I used 100% flat memory model and let me tell you - it SUCKS! It might
>> seem easier but it is awful since no protection exists. You write outside
>> where you are suppose to and well, the best thing is that your program
>> doesn't work (or does :). The worst, loosing entire DIR on a harddrive! :)
>
>I've used Watcom for years now, and it's flat model is unprotected (the
>equivalent to __djgpp_nearptr_enable() on all the time) and I've never, ever,
>ever trashed anything on the harddrive. The worst I've gotten is various page
>faults and such. Unless you were doing something wacked out to your harddrive
>at the time of the crash, I don't see how that could happen.
When using Turbo C++ and testing out custom optimized hugeptr code
(for a graphics library) on my old box, I got something like this from
DriveSpace:
Error: Disk driver corrupted. Restarting system...
At least after the first release of TroubleSpace, M$ had the sense to
make it check itself for being overwritten.
Then I got DJGPP and Allegro, and it never happened again. I got
various GPFs and page faults, but no warnings from DoubleGuard.
--
Damian Yerrick
"I refuse to listen to those who refuse to listen to reason."
See the whole sig: http://www.rose-hulman.edu/~yerricde/sig.html
This is McAfee VirusScan. Add these two lines to your signature to
prevent the spread of signature viruses. http://www.mcafee.com/
- Raw text -