To: opendos AT delorie DOT com X-Comment-To: "da Silva, Joe" References: <01FD6EC775C6D4119CDF0090273F74A455A668 AT emwatent02 DOT meters DOT com DOT au> Message-Id: <2.07b7.G3JF.GFOWT4@belous.munic.msk.su> From: "Arkady V.Belousov" Date: Fri, 29 Jun 2001 15:48:40 +0400 (MSD) Organization: Locus X-Mailer: dMail [Demos Mail for DOS v2.07b7] Subject: RE: New DOS stuff - WDOSX 0.96 Lines: 36 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r X-MIME-Autoconverted: from 8bit to quoted-printable by postbox.mos.ru id f5TBlUg26044 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id HAA25756 Reply-To: opendos AT delorie DOT com X-Comment-To: da Silva, Joe Hi! 8-éÀÎ-2001 10:34 Joe DOT daSilva AT emailmetering DOT com (da Silva, Joe) wrote to "'opendos AT delorie DOT com'" : dJ> The reason why I ask if the stubbed executable works on dJ> your PC setup is : dJ> If it does work, No, it doesn't work. dJ> then it might be possible to fix STUBIT just by dJ> recompiling it with a different compiler, I don't use any compiler beside BC++ 3.1 and TASM. dJ> else you can manually dJ> stub some types of executables using the "COPY /B" method. You mean "COPY/B STUBIT.EXE+APP.EXE APPNEW.EXE"? Even if app already stubbed by DOS4GW, for example? And don't forget: STUBIT anyway doesn't run. Without arguments. dJ> If it does not work, then the problem is more serious, and I'm dJ> afraid I don't have the expertise to fix DOS extenders. :-( dJ> Also, if the stubbed executable doesn't work on your PC setup, I can't stub app by STUBIT, because STUBIT doesn't work (freezes right after run). And I don't think stubbing by "COPY/B" will work. dJ> it is something we should know. Otherwise we may be creating dJ> DOS app's which won't run on some PC's (ie. yours). In other dJ> words, this something other DOS developers on this list should dJ> know about.