From: jaynews@ntlworld.com   
      
   Hi Wolfgang,   
      
   >> Has anyone come acroos the problem of the BP7.01 compiler crashing when   
   >> compiling large (>100,000 lines) (DPMI) programs ~without~ switching off   
   >> external debug info?  And more to the point, does anyone know a work-   
   >> around for it? This happens with both the IDE and the command-line   
   compiler.   
   >>   
   > It would be helpful if you give more information about the "crash" and   
   > tell us if the crash symptoms are identical in the IDE and with BPC.   
      
   "Internal Error 216 (ie a GPF) at 0002:1BBB"   
      
   Is what BP.EXE reports when it bombs-out. BPC reports something similar.   
   I can avoid it by switching off "Standalone Debugging" in the   
   "Options|Debugger..." dialog box, but then I can't debug or browse my   
   program.   
      
   I've also had compiler error 110 - "Debug information table overflow" on   
   many occasions, but at least I can work around that problem by turning debug   
   info off on some units.   
      
   > What OS and DPMI host do you use?   
      
   Windows 98SE, with all M$ bug-fixes applied. The W98SE DPMI host is used in   
   a DOS box, but the same crash happens with DPMI16BI.OVL and HDPMI16 in pure   
   DOS.   
      
   > It is folklore that DMPI support in Win2000 / WinXP is "suboptimal".   
      
   Maybe, but SVGA support is buggy as hell. Only Windows programs are   
   "allowed" to use hi-res graphics on Windows 2000/XP.   
      
   > I just did a test without any problems compiling the really big file   
   > DOS Nvaigator 6.40 DMPI with more than 160000 lines and resulting EXE   
   > of 1.9 MB / 800KB map file. And I never had these kind of problems   
   > with WIN98.   
      
   Well at least this means there might be hope, though my map files tend to be   
   a little larger than this. I think the problem is almost cerntainly to do   
   will an internal debug/browser buffer overflow, but I need that info! It   
   ~might~ also be related in some way to large units. That is, units that   
   contain a lot of symbols, but I've broken my largest units up as far as they   
   should logically go - any more would be difficult to do, and not the   
   "correct" thing to do. I will try this as a last resort though.   
      
   Jay   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)