Message-ID: <01FD6EC775C6D4119CDF0090273F74A455A693@emwatent02.meters.com.au>
From: "da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
To: "'opendos AT delorie DOT com'" <opendos AT delorie DOT com>
Subject: RE: New DOS stuff - WDOSX 0.96
Date: Fri, 3 Aug 2001 15:03:11 +1000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id BAA21616
Reply-To: opendos AT delorie DOT com

Thanks for the info., Arkady.

It's a shame that the stubbed executable also has trouble with
your PC. This means it's a more serious problem, so WDOSX
cannot be recommended as an MZ-executable extender (I assume
that's the type of extender used with BC 3.1).  :-(

As for other executable types supported by WDOSX, these may
or may not have the same problem, so caution would be advised ...

BTW, I haven't tried the "COPY /B" method myself, and I don't know
if it's suitable for an executable that is already stubbed. If it is, then
you would probably separate the existing stub using, say UNP411,
then re-stub it (just guessing ;-).

Oh, well !   :-/

Joe.
> -----Original Message-----
To: 	opendos AT delorie DOT com <mailto:opendos AT delorie DOT com> 	
From: 	"Arkady V.Belousov" <ark AT belous DOT munic DOT msk DOT su
<mailto:ark AT belous DOT munic DOT msk DOT su>> 	
Date: 	Fri, 29 Jun 2001 15:48:40 +0400 (MSD) 	
Subject: 	RE: New DOS stuff - WDOSX 0.96 	
Thread:	Frames <thread.cgi?msg=opendos/2001/06/29/09:53:32&mode=frames>,
NoFrames <thread.cgi?msg=opendos/2001/06/29/09:53:32>, TwoWindows
<thread.cgi?msg=opendos/2001/06/29/09:53:32&mode=windows>	
X-Comment-To: da Silva, Joe

Hi!

8-éÀÎ-2001 10:34 Joe DOT daSilva AT emailmetering DOT com
<mailto:Joe DOT daSilva AT emailmetering DOT com> (da Silva, Joe) wrote to
"'opendos AT delorie DOT com <mailto:opendos AT delorie DOT com>'" <opendos AT delorie DOT com
<mailto: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.
>