Hello, It depends. Here is some data to consider:
For mTCP I distribute 11 executables in two different forms - UPX compressed and standard. The UPX versions sum to 496KB. The original versions sum to 824KB. The UPX versions require 60% of the space of the originals. On a low-end 8088 class machine the UPX versions take significantly longer to start running than the standard versions. You can feel it decompressing. I have timed it before; it is less than a second but it is noticeable. On faster machines this penalty may not be noticed. UPX makes my programs tolerable to use from a floppy drive. It is also great for those ancient 20MB hard drives that I regularly use; 400KB of extra space for other things is handy. Once again, on larger machines this is not an issue. I would not use UPX on something like a TSR where it may cause a functional problem or behavior difference. But for plain executables, UPXing for 8088 class processors is generally reasonable. Or provide the end user with a script or instructions on how to do it themselves. I provide two different versions to take the guesswork out. Mike ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
