Date: Sat, 3 May 1997 14:57:42 +0800 (GMT) From: Orlando Andico To: Owen LaGarde cc: djgpp AT delorie DOT com Subject: Re: DJGPP 2.01 + OpenDOS = total clusterfuck In-Reply-To: <5kd09q$elr$1@NNTP.MsState.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On 2 May 1997, Owen LaGarde wrote: > I've been coding under a variety of OSs for quite some time, and > just recently decided to try djgpp 2.01 ... unfortunately, I was also > trying out Caldera's OpenDOS as well. I have truly never seen a bigger > mess than this: with a 486DX4/100-16M station, 6M temp and 4M swap, > I dropped in grx20 off the simtel dist site (djgpp/v2tk/grx20.zip). > It built with no evident problems, but upon experimenting, I found that > running ANY executable corrupted seemingly random high-mem blocks, usually > resulting in the top shell crapping out. It's so interesting to follow > installation instruction to the letter only to see the following: [...] I haven't used DJGPP under OpenDOS (I use a Linux cross compiler) but I noticed that the OpenDOS DPMS.EXE and EMM386.EXE really f*ck up many DPMI apps, specially those that use DOS4GW (to be exact, I can't run DOOM2 or Warcraft2 under OpenDOS unless I disable DPMS.EXE and remove the DPMI from the EMM386.EXE command line). Apparently, a) the DPMS "multitasking" bit upsets DOS4GW; b) the DPMI provider in EMM386.EXE is not particularly compatible. In any case, it's OK to use neither EMM386 or DPMS - you lose the "multitasking" (which is pretty inferior anyway) and have less conventional memory, but CWSDPMI should be able to use the rest. ----------------------------------------------------------------------- Orlando Andico IRC Lab/EE Dept/UP Diliman email: orly AT gibson DOT eee DOT upd DOT edu DOT ph http://gibson.eee.upd.edu.ph "There's an obvious attraction to the path of least resistance.."