Xref: news2.mv.net comp.os.msdos.djgpp:6811 From: "Maan M. Hamze" Newsgroups: comp.os.msdos.djgpp Subject: Re: Help with DJGPP MSDOS Settings Date: 1 Aug 1996 18:28:31 GMT Organization: University of Texas at Austin Lines: 44 Message-ID: <01bb7fd6$24a76660$31fb5380@maan-m.-hamze> References: NNTP-Posting-Host: slip-54-1.ots.utexas.edu To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Eli Zaretskii wrote in article ... > > On 1 Aug 1996, Maan M. Hamze wrote: > > > When DJGPP is installed in E:\DJGPP, was simply not working on my system. > > So instead, I put, in autoexec.bat, the line > > e:\djgpp\bin\setdjgpp.bat e:\djgpp e:/djgpp > > which configures the setting each time at startup. Having done that > > everything is working fine and smoothly with the original djgpp.env. I do > > not know if that is the way I was supposed to do it from the start. > > Both calling `setdjgpp' and setting DJGPP=E:\DJGPP\DJGPP.ENV should have > worked. You can use the solution you've found, if you're reluctant to > investigate while the other didn't work. Believe me I know that it should have worked, but it looks like the setdjgpp e:\djgpp e:/djgpp is sort of 'forcing' the setting on the system at each startup. With only: SET DJGPP=E:\DJGPP\DJGPP.ENV or SET DJGPP=E:/DJGPP/DJGPP.ENV in autoexec.bat, RHIDE is crashing the system and gcc and gxx do not work after reporting that they can not find: dpmiload.exe, although I have cwsdpmi in the path. However, at only one occasion RHIDE started to compile a source code before it crashed. So, apparently it was able to 'read' the info in the env file. From my guess, the culprit is not the env file, but something to do with the inability to properly use cwsdpmi unless the setting is forced by using setdjgpp. Because it looks like there is a correlation between 'forcing' this environment setting and for the apps to 'properly' use cwsdpmi. Anyway, as I mentioned before, everything is working smoothly since I started using setdjgpp. I'll investigate this matter further and try to isolate the culprit that is leading to these crashes and report back in case anyone is running into this same kind of problem. Meanwhile, setdjgpp is working fine. So be it! i am quite glad with it :) -- Maan M. Hamze mmhamze AT mail DOT utexas DOT edu http://leb.net/~mmhamze