Mail Archives: djgpp/2000/10/30/01:30:20
> How can I use the stub version with UPX, because I need to compress my exe
> file?
If you append the stub before UPX'ing the file, it should work fine. You
can also use the upx --coff qualifier to create a COFF output then do the
COPY /B CWSDSTUB.EXE+coff_output new.exe ...
> BTW: Does somebody know the difference between the memory which will be used
> from CWSDPMI and PMODE/DJ if they are started as TSR?
The TSR versions behave about the same as the built in versions. To get
exact numbers I'd suggest just building an image which does a
system("command.com") and running mem/c and/or mem/d from it.
If you use the built in stub, the memory required for each stub depends on
the amount of physical memory present on the system, and if it has EMM386
enabled, etc. For a VCPI system with relatively small amount of memory
PMODE/DJ will use 20-30Kb less DOS memory. For a raw environment system
with 128Mb of memory PMODE will use around 140Kb less DOS memory (since it
does not enable paging or use page tables to support virtual memory).
I do know of a couple of problems with PMODE/DJ however - since PMODE can't
nest any programs running nested can mess things up. It also don't seem
to handle "novcpi" on an EMM386 line well. The lack of virtual memory is
can be a problem - so I recommend you determine the worse case stack size
and stubedit that in - the default of 256Kb can be a problem on small
memory machines. And you need to be aware the default stack size is
smaller (256Kb) than on the standard stub (512Kb) which could cause problems
if you aren't careful.
If you plan to mess with PMODE/DJ, please get the 1.3 beta.
- Raw text -