Xref: news2.mv.net comp.os.msdos.djgpp:1299 From: alexlehm AT rbg DOT informatik DOT th-darmstadt DOT de (Alexander Lehmann) Newsgroups: comp.os.msdos.djgpp Subject: Re: v2 and dpmi Date: 19 Feb 1996 17:59:40 GMT Organization: Technische Hochschule Darmstadt Lines: 34 Message-ID: <4gadqc$h74@rs18.hrz.th-darmstadt.de> References: <31A6D394110 AT fs2 DOT mt DOT umist DOT ac DOT uk> NNTP-Posting-Host: hp61.rbg.informatik.th-darmstadt.de To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp A.Appleyard (A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk) wrote: : Eli Zaretskii wrote (> Subject: Re: v2 and dpmi):- : > [Compiling a Gnu C/C++ file to an .EXE file which you run on another PC] is : > much like in v1.x, if you substitute CWSDPMI for GO32. The differences are : > that there are other DPMI servers whereas there was no substitute for GO32; : > and that currently there is no way to bind CWSDPMI with the .exe to make the : > .exe stand-alone : > (but probably such a possibility will be added in the future). : When? The sooner the better. Currently a Gnu C/C++ A.OUT can be made (by : prefixing go32.exe) into a completely independent .exe file. It seems that : with v2 the .exe file will be hostage to any faults of whatever DPMI the : recipient's PC has, or to him not running DPMI at all. Actually, if you create an independent program with go32, it will not run on all systems (e.g. the DPMI manager from Borland, I think), so the situation is not much different from the new version, only you need to distribute the cwsdpmi program with the files (which is used if no DPMI driver is present). If you distribute executables as a package, most users will not notice the additional program anyway, as long as they don't decide to move selected programs somewhere else. bye, Alexander -- Alexander Lehmann, | "On the Internet, alex AT hal DOT rhein-main DOT de (plain, MIME, NeXT) | nobody knows alexlehm AT rbg DOT informatik DOT th-darmstadt DOT de (plain) | you're a dog."