From: "Charles Sandmann" Newsgroups: comp.os.msdos.djgpp Subject: Re: One for the Gurus Date: Sun, 1 Jun 1997 19:08:04 Organization: Aspen Technology, Inc. Lines: 19 Message-ID: <3391c894.sandmann@clio.rice.edu> References: Reply-To: sandmann AT clio DOT rice DOT edu NNTP-Posting-Host: spica.dmccorp.com To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk > > I found the same problems, when tried to use the 2.7.2p intel pentium > > patches.... Under plain MS_DOS using CWSDPMI they chrased, under Win95 they > > worked perfectly..., so try to change your dpmi host, or forget the pentium > > Sorry, that's a hack, not a solution. How can a compiler port be released > when it doesn't work with CWSDPMI? Oh, gee - I forgot to tell you all - someday I'll release cwsdpmi r95 which will consume 1/2 the memory on the box, disable the extra memory protection features, zero all memory, check all selectors before touching them, etc. While this will make it slower, it doesn't matter since everyone has a PPro. It won't check for paging in interrupts/RMCBs, so will occasionally trash your hard drive like W95 does, but that's what people expect from PCs anyway. In general, the fix for programmers who are too lazy to write correct bug free code. Oh, it will be $95. I'm taking orders now :-) P.S. We really left the first 4096 bytes in DJGPP space unused so you can read/write random data there without overwriting your code. Just build your program with the crt0 flag to tell cwsdpmi to quit bitching about bad pointers!