X-Authentication-Warning: delorie.com: mailnull set sender to opendos-bounces using -f
Message-ID: <01FD6EC775C6D4119CDF0090273F74A455A98B@emwatent02.meters.com.au>
From: "da Silva, Joe" <Joe DOT daSilva AT emailmetering DOT com>
To: "'opendos'" <opendos AT delorie DOT com>
Subject: RE: WDOSX update (was: New DOS stuff - WDOSX 0.96)
Date: Mon, 11 Feb 2002 18:30:34 +1100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g1B7Oen22799
Reply-To: opendos AT delorie DOT com

Well, there is now a new "STUBIT" program, incorporating a new
WDOSX loader, that is currently available via :
          http://wdosx.homeip.net/wdosx/xpmess.html

This fixes a compatibility problem with Windoze XP, which causes
WDOSX stubbed programs, and the "STUBIT" program itself, to crash.
This sounds similar to the problem Arkady was having, although I'm
sure he wasn't using Windoze XP ... (might be similar cause?)

Anyone using WDOSX version "0.96 final" probably should get the
above update, and also the "kernel32.wdl" update, via :
          http://wdosx.homeip.net/wdosx/kernel32.wdl

I expect these two updates will soon be incorporated into a revised
release of WDOSX, at which time the above URL's may disappear(?).
If so, just go to http://wdosx.homeip.net/ for the 0.97 release ...

What is WDOSX? Well, for those who aren't familiar with it, it's
an easy-to-use 32 bit "DOS extender", that lets you create DOS
applications using TASM, NASM, MASM, Borland C++, Borland
Delphi, M$ VC++ (NB. not sure about V6 compatibility), Watcom
C++, TMT Pascal and DJGPP V2 (including GNU Pascal :-). BTW,
for DJGPP applications, it just adds DPMI support (and shrinks
the executable to about half size:-).

Joe.

> -----Original Message-----
> From:	da Silva, Joe 
> Sent:	Monday, August 06, 2001 10:07 AM
> To:	'opendos AT delorie DOT com'
> Subject:	RE: New DOS stuff - WDOSX 0.96
> 
> 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 ;-).