Xref: news2.mv.net comp.os.msdos.djgpp:568 From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: delorie software Date: Tue, 23 Jan 1996 08:05:47 CST Organization: Rice University, Houston, Texas Lines: 21 Message-ID: <3104eb3b.sandmann@clio.rice.edu> References: Reply-To: sandmann AT clio DOT rice DOT edu NNTP-Posting-Host: clio.rice.edu To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp > the c++ lib for djgpp v2.x seems to have tons of bugs and invalid filenames > such as _g_config.h instead of _g_confi.h? This is only a problem under Win95 with LongFileNames turned on. At the command prompt try "SET LFN=n" and retry. Default for the next beta will be off because of the confusion. > Second, why doesn't anyone build cwsdpmi INTO the DJGPP > compiler? Is it copyrighted or something? It doesn't have anything to do with the copyright issue, since DJ has complete rights to all of it anyway. It's a modularization issue. If you have a DPMI provider (which Windows, OS/2, QEMM, 386MAX all provide) you don't need CWSDPMI at all (except for image distribution). CWSDPMI is also built with different (non-FSF) tools. It can also be easily replaced in the future with a different DPMI provider without modification of the DJGPP distribution or images. It is on my list of things to do to provide a stub which can imbed a copy of cwsdpmi (or some other DPMI provider) so images can be a single EXE if desired, but it's sort of low on the priority list right now.