======================== The ultimate Packer V1.1 ======================== A. The problems =============== This program was designed in order to simplify the process of packing AmigaDos files to a much smaller size. There already exist many programs which claim try to do the same. But most of them have significant disadvantages in some extend. These disadvantages can be one of the following: - their packing efficiency is sometimes very (or relatively) bad. This is often due to a compromise of the programmer between speed and efficiency. - the unpacking header of the resulting files does often not run if started from the boot-block. - the unpacking process often simultaneously holds the packed and the unpacked program in memory. This entails that it will not run on Amigas with low memory sizes. - the use of the packer is sometimes very difficult and requires from the user detailed information of where to unpack the program later to. B. The result ============= These problems are now solved simultaneosly by the ultimate Packer. It is an easy to use program, which does not require the user to have deep knowledge of the system an its free memory areas. This is completed by implementing a relocating packer. Besides, the unpacker does not hold both the crunched and the unpacked DOS file in the memory. This allows to unpack huge files even on small systems. C. The usage ============ The usage is very simple. It entirely uses the intuition interface which allows a very intuitive work possible. However I will detail the menus somewhat, in order to clear any possible doubts. 1. The File Menu ++++++++++++++++ a. Load ------- This menu entry is used to load a file and start its packing process. If the menu entry is picked, a Filerequester will appear, to allow the choice of a program to process. The pack efficiency is chosen in the prefs menu. b. Save as BOOT --------------- This menu entry installs the currently loaded program to disk. The drive to write the BOOT to can be chosen in the prefs menu. The choice of this menu point will create a file called BOOT onto the chosen drive, and write a boot block to the same disk. c. Save as DOS-file ------------------- When this point is picked, a FileRequester will appear and allow you to choose the destination file, which to write the file to. d. Help ------- Online help. (not yet implemented) e. About -------- Gives information about the writing of the program, its author,price and release date. f. Quit ------- Leave the program after a security check. 2. The Prefs Menu +++++++++++++++++ a. Bootify DF?: --------------- This menu entry is used to chose the drive which the BOOT is to be written to. One of DF0:, DF1:, DF2: and DF3: can be picked. b. Efficiency Good ------------------ This choses the packer to make a good packing. This entails however a great memory consumption in the course of the packing. Moreover, large files (>140 KB) may require relatively much time to pack (depending on the file contents). The good efficiency mode is default. c. Efficiency Fast ------------------ This choses the fast crunching mode. This mode may be used if files are very large or if efficiency is less important than crunching speed. The fast mode does not need as much storage space while crunching. This allows to crunch larger files in this mode, even though the efficiency will be much worse. d. Load to ??? RAM ------------------ This menu entry should be used only for special applications. It allows to choose the type of RAM which to unpack the packed file to. This can be one of CHIP, FAST or PUBLIC (=any free RAM). If an unappropriate memory type is chosen, the program displays a WARNING. The default setting is CHIP RAM. D. Restrictions =============== - The resulting (crunched) programs can only be started from CLI. This is due to the use of OVERLAYS. This will be fixed in later versions. - The current version can't pack pure DATA files, but only executable DOS files. This will be fixed too in coming versions. D. Preview ========== If this SHAREWARE program finds general approvement, a new version will be released. It will feature the following new points: - even better efficiency; - faster packing; - recovering of packed files; - packing of data files; - capability to be started from the Workbench (and not only from CLI). E. Credits ========== This program was entirely written by: Georges Thill 32, rue Eugène Welter L-2723 Luxembourg See Info in the program. F. Appendix =========== 1. What programs can be bootified ? +++++++++++++++++++++++++++++++++++ The bootify facility is basically supported for usage with intros or comparable programs. These SHOULD NOT USE ANY LIBRARIES of the system except for the exec library. Using libraries in the bootified programs will very probably lead to an unproper ending of these programs because the libraries have at this time not yet been installed in the system. Moreover, the program which is to be bootified should not expect any parameters from CLI or from the WB ( because none can be given). It is important to respect these constraints if operation of the program is to be certain.