user documentation E_WISE Veit Kannegieser ðððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððð usage: ÍÍÍÍÍÍ E_WISE example: E_WISE M:\SETUP.EXE E:\TEST The idea for E_WISE comes from EXWISE / Andrew de Quincey (adq@tardis.ed.ac.uk, http://www.tardis.ed.ac.uk/~adq). my version - reimplemented in Pascal - can handle more WISE-versions - can retrive filenames and date/time after program usage you will find in target directory: - ????????.EWI: unpacked data - 00000000.TXT: reference of ????????.EWI and quessed filename - 00000000.BAT, (DOS) \ to rename ????????.EWI 00000000.CMD: (OS/2) / and move to subdirectories problems: ÍÍÍÍÍÍÍÍÍ * HPFS filesystem recommended (long file/directory names) * thhere exist packages where one filename is used multiple times (example: multilingual README.TXT) * if you want unpack an executable sliced onto muliple diskettes you must rebuild one singe file for E_WISE: copy A:\setup.exe s.exe copy /b s.exe + A:\setup.w01 copy /b s.exe + A:\setup.w02 and then unpack e_wise s.exe x\ Frequently asked question: Can you help me making an setup.exe from unpacked files ? The problem is not the compression procedure (zip/inflate), but the data format of the directory file. It differs each version. And i do not want my time spend for an user unfriendly archive format/target platform. changes: ÍÍÍÍÍÍÍÍ ð 2000.02.11..2000.02.29 þ processing of version NE/$3e10 added þ processing of version NE/$3bd0 and NE/$3c10 added þ Support for selfextracing selfextractors .. þ improved filename recognition ð 2000.03.01 þ corrected PE/$6e00with relocations ð 2000.08.21 þ processing of version NE/$3770 added þ accept readonly files ð 2000.10.12 þ corrected missing zeroes in last packed file ð 2002.02.11 þ added NE/$84b0, use /DEBUG to bypass bad blocks ð 2002.03.26 þ added NE/$3c20 ð 2002.03.29 þ added PE/6e00;$3d04 þ reads known formats from e_wise.ini ð 2002.07.01 þ protect "&" char in filenames þ NE/37B0 þ added partial support for patch format þ append numbers to equal filenames