Hi,

2006/8/21, Arkady V.Belousov <[EMAIL PROTECTED]>:
> AS> actually supposed I was relying on caller's stack (I am not doing many
> AS> weird things, not using C or the like, that can abuse the stack more
> AS> than I do in assembler.
>
>     There is no such thing as "caller stack" when we discuss transient
> portion (which gets control, when program starts).

True, sorry. I was mislead with the resident portion.

> >> You either have to use another compressor, design your
> >> program as a proper EXE with own stack, or ask some UPX
> >> expert to fix the sub-optimal workings of UPX for your
> >> case. At least you can be sure that this is NOT a FreeDOS
> >> kernel problem.
> AS> Well, I have an option which is better (easier) than the other three
> AS> that you gave me: wait until DISPLAY becomes DISPLAY.SYS. As I said,
>
>     Not need to convert exe/sys to plain sys, especially because combo may
> give additional features (like information about status) without additional
> executables.

I was talking of converting COM to SYS. I may try to make it an EXE
(in the future a COMBO), but it seems that I won't be saved from UPX
greediness.

So either there is a way for a device driver to safely go beyond its
original size, or perhaps I could try:

NASM => APACK => COM2EXE.

Eric, it wasn't clear for me what is the DISPORG.EXE thing that you
mentioned. If it is just the same DISPLAY.EXE where you just modified
the EXE header, I can make just a temporary tool to patch it.

Best could be that I contact the UPX guys for it, but it may in turn
it could be that the decompressing algorythm may well NEED those 12X+
KB to run.

Aitor

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to