OpenEuphoria

Re: DOS Translator Issues

• Posted by Vincent <darkvincentdude at yahoo.com> Apr 15, 2005
• 455 views

Matt Lewis wrote:
> 
> 
> Rob,
> 
> I translated a file named sequencef.e.  In emake.bat, the file name was
> sequencef.c, but the actual file created was SEQUENCE.C, causing an error
> with emake.bat.  I renamed the file, and it worked fine.  The windows
> translator works correctly.  (I'm doing this on a WinXP Home box.)
> 
> Also, I wanted to note that UPX will now compress DOS executables.  I got
> a smaller file when using UPX than when using the Causeway compression:
> 
> 253,269 bytes UPX
> 388,529 bytes CW
> 
> Same file, compiled using OpenWatcom v1.3.
> 
> Matt Lewis
> 

What good is EXE\DLL compression? The physical space you save with
a compressed app is almost all the more computer memory used and extra
memory overhead created when running it. It only causes loading time
to increase (UPX does a very efficent method to minimize loading time,
and minimize overhead too).

Compressed EXE/DLLs offer some sort of encyription which is cool,
but if you think about it.. someone needs only uncompress it and
it goes right back to unencyripted form.

If you want to save HDD space, just use a popualar compression
archiving utility.. Like WinZip, WinRAR, 7z, etc. The results
are almost as good too, and you wont get better results if you
compress your apps and put it into a compressed archieve.

If you ask me, the idea behind EXE/DLL file compression makes sense
if computer memory was much more cheaper and greater in capacity than
hard drives avialable.

You guys should consider all that carefully before compressing your executables.
It really is just pointless to compress EXE/DLLs and
that is at the very best.

Regards,
Vincent


Without walls and fences, there is no need for Windows and Gates.