Mail Archives: opendos/2001/08/05/20:06:56
Thanks for the clarification, Arkady.
Not to prolong this thread much further, we have a saying :
'this one goes in the "too hard" basket' ...
Oh, well! :-/
Joe.
> -----Original Message-----
> From: Arkady V.Belousov [SMTP:ark AT belous DOT munic DOT msk DOT su]
> Sent: Saturday, August 04, 2001 10:35 PM
> To: opendos AT delorie DOT com
> Subject: RE: New DOS stuff - WDOSX 0.96
>
> X-Comment-To: da Silva, Joe
>
> Hi!
>
> 3-αΧΗ-2001 15:03 Joe DOT daSilva AT emailmetering DOT com (da Silva, Joe) wrote to
> "'opendos AT delorie DOT com'" <opendos AT delorie DOT com>:
>
> dJ> It's a shame that the stubbed executable also has trouble with
> dJ> your PC. This means it's a more serious problem, so WDOSX
> dJ> cannot be recommended as an MZ-executable extender (I assume
> dJ> that's the type of extender used with BC 3.1). :-(
>
> You wrongly understand me.
>
> 1. I can't stub any program because STUBIT freezes before even says
> anything
> on the screen (whereas STUBIT itself is an stubbed executable).
>
> 2. I try to restub program which already stubbed by dos4gw, but see topic
> 1.
>
> 3. When I say "I don't use any compiler beside BC++ 3.1 and TASM" I answer
> to your note "then it might be possible to fix STUBIT just by recompiling
> it
> with a different compiler" - I mean, I can't recompile STUBIT.
>
> dJ> As for other executable types supported by WDOSX, these may
> dJ> or may not have the same problem, so caution would be advised ...
> dJ> BTW, I haven't tried the "COPY /B" method myself, and I don't know
> dJ> if it's suitable for an executable that is already stubbed. If it is,
> then
> dJ> you would probably separate the existing stub using, say UNP411,
> dJ> then re-stub it (just guessing ;-).
- Raw text -