лхарц аRCHIVE цREATOR FOR цс-дос -------------------------------- цOMMAND: лха сYNTAX: лха [-S] ARCHIVE[.LZH] FILE(S) дESCRIPTION: лха IS USED TO CREATE ARCHIVES USING THE лхарц FORMAT. оPTIONS: тHE -S OPTION TELLS лха TO CREATE A SELF DISSOLVING сфь. сEE THE DOCUMENTATION FOR сфь FOR MORE DETAILS ON USING сфь. пROS: тHE лхарц ARCHIVE HAS SEVERAL ADVANTAGES OVER THE арц128 OR мс-дос STYLE арц FORMATS AND IS GROWING IN POPULARITY. аMONG THE ADVANTAGES ARE ... 1) сIMPLICITY. сINCE ONLY ONE DATA COMPRESSION ALGORITHM IS USED, THE CODE IS LESS COMPLEX SINCE WE DON'T HAVE TO WORRY ABOUT OBSOLETE VERSIONS OF THE COMPRESSOR OR CHOOSING BETWEEN ONE OF SEVERAL POSSIBLE COMPRESSORS. 2) пORTABILITY. сINCE THE ц SOURCE CODE FOR THE COMPRESSOR AND DECOMPRESSOR IS READILY AVAILABLE IN THE PUBLIC DOMAIN, THE FORMAT IS BEING USED ON NUMEROUS DIFFERENT OPERATING SYSTEMS INCLUDING мс-дос, аMIGAдос AND OTHERS. тHUS ARCHIVES CREATED ON THE ц128 CAN BE MANIPULATED ON OTHER SYSTEMS AND VISA VERSA. 3) еFFICIENCY. тHE SLIDING DICTIONARY DATA COMPRESSION ALGORITHM EMPLOYED BY лхарц IS A SIGNIFICANT IMPROVEMENT OVER THE лEMPEL зEV TECHNIQUE EMPLOYED BY арц, зоо AND OTHERS. фURTHERMORE, THE TECHNIQUE WORKS WELL WITH BOTH SMALL FILES AND WITH PROGRAM AND OTHER FILES WHICH NORMALLY DO NOT COMPRESS VERY WELL. тYPICALLY, YOU CAN EXPECT TO GAIN ABOUT 20 TO 25% OR SO OVER арц128 OR цсарц. тHAT MEANS THAT A 800к FLOPPY DISK FULL TO THE BRIM WITH ARCHIVES, COULD BE CONVERTED TO лхарцHIVES TO YIELD ABOUT 200к OR SO OF FREE DISK SPACE. 4) лONG FILENAMES. тHE лхарц FORMAT DOES NOT ARBITRARILY RESTRICT YOU TO THE мс-дос 8+3 FILENAME LENGTHS AND SO IS BETTER SUITED FOR цOMMODORE 8 BIT дос OR аMIGAдос AND OTHERS. 5) тHE сELф EьTRACT MODULE CAN BE RUN ON EITHER A ц64 OR A ц128, WHICH CAN AID IN ELIMINATING A BIT OR CONFUSION AND/OR REDUNDANCY. цONS: иT DEPENDS WHO YOU'RE COMPARING TO HERE. цOMPARED TO пкваре'S зип OR дхеси'S зоо лхарц LEAVES A BIT TO BE DESIRED IN TERMS OF SUPPORT FOR FILE COMMENTS, RECOVERING DAMAGED ARCHIVES AND SO ON, BUT COMPARED TO JUST ABOUT ANYTHING ELSE, лхарц HOLDS ITS OWN PRETTY WELL. сPEED IS THE MAIN PROBLEM. лEMPEL зEV COMPRESSION IS FASTER, BUT IN ITS CURRENT STATE лха IS ONLY MARGINALLY SLOWER THAN арц128 SO THE COMPRESSION AND PORTABILITY ADVANTAGES MORE THAN COMPENSATE. и BELIEVE THERE'S ROOM FOR IMPROVEMENT HERE SO лха MIGHT GET A SPEED BOOST LATER ON. лха AND лхь ARE WRITTEN IN HYBRID ц AND ASSEMBLY LANGUAGE, SO THE EXECUTABLES ARE SOMEWHAT LARGER THAN NORMAL. тHIS MAKES THEM A LITTLE MORE AWKWARD TO USE IF YOU DO NOT HAVE A рам EXPANSION CARTRIDGE. иMPLEMENTATION: лха REQUIRES A 1750. иT WON'T WORK WITHOUT ONE. лхь AND лхд DO NOT. иF YOU DO NOT HAVE A рам EXPANSION CARTRIDGE, YOU'LL BE ABLE TO VIEW AND/OR DISSOLVE лхарцHIVES, BUT YOU WON'T BE ABLE TO CREATE THEM. еACH FILE IN THE ARCHIVE IS PRECEDED BY A HEADER WHICH CONTAINS, AMONG OTHER THINGS, THE FILE'S ORIGINAL SIZE, ITS COMPRESSED SIZE, AND THE FILES CALCULATED црц. сINCE THIS INFORMATION IS NOT AVAILABLE UNTIL AFTER THE FILE HAS BEEN COMPRESSED, лха COMPRESSES THE ENTIRE FILE AND STASHES IT AWAY IN THE 1750. иT THEN WRITES THE HEADER INFORMATION, AND THEN FLUSHES THE CONTENTS OF THE 1750 TO THE ARCHIVE. тHERE ARE ALTERNATIVES TO THIS APPROACH, BUT THEY WERE ALL EITHER TOO SLOW OR TOO COMPLICATED, SO IF YOU DON'T OWN A 1750 YOU'RE с.о.л. сINCE YOU MAY BE USING THE 1750'S рам FOR OTHER THINGS, YOU HAVE TO TELL лха WHAT PART OF THE 1750 IS FREE TO BE USED FOR ITS PURPOSES. дO THIS BY PUTTING A LINE SOMETHING LIKE THIS IN YOUR AUTOEXEC FILE ... POKE DEC("1BCF"), X*16+Y WHERE X IS THE LOWEST 1750 BANK THAT CAN BE USED, AND Y IS THE HIGHEST 1750 BANK PLUS ONE. фOR EXAMPLE ... POKE DEC("1BCF"), 4*16+7 TELLS лха ITS OK TO USE 1750 BANKS 4,5 AND 6. аLL OTHER BANKS ARE LEFT ALONE. мORE OFTEN THAN NOT, ONE OR TWO BANKS WILL BE ADEQUATE. аNY FILE WHOSE SIZE WHEN COMPRESSED IS LARGER THAN THE 1750 SPACE AVAILABLE WILL CAUSE лха TO ABORT. лха USES A FAIR BIT OF THE ц128'S MEMORY. иT USES PRACTICALLY ALL OF BANK 1 (FROM $4000 UP TO $е100). иF YOU HAVE SOMETHING UP THERE, лха WON'T RUN. иT ALSO USES BANK 0 FROM $1ц00 UP TO $бффф. $ц000 AND ABOVE IS NOT TOUCHED. жERSIONS 1.0 AND 1.1 OF лха AND лхь DID NOT ALLOW рел OR уср FILES. лха WOULD REFUSE TO ARCHIVE THEM AND лхь WOULD EXTRACT THEM AS прг FILES. сTARTING WITH VERSION 1.2, уср AND рел FILES ARE ALLOWED. сINCE THE сфь CODE CANNOT HANDLE рел OR уср FILES, лха WILL STILL REFUSE TO ADD ANY SUCH FILES WHEN CREATING AN сфь WITH -S. иT SHOULD BE NOTED THAT уср FILES MAY NOT ALWAYS BE HANDLED PROPERLY. (тHIS GOES FOR арц128 AS WELL) фOR THE MOST PART, уср FILES ARE NO DIFFERENT THAN сея OR прг FILES AND CAN BE ARCHIVED WITHOUT PROBLEMS. уср FILES ARE, BY DEFINITION, усEр DEFINED, OR MORE LIKELY PROGRAMMER DEFINED. тHEY MAY NOT BE NORMAL цOMMODORE FILES AT ALL. тHIS PROBABLY ISN'T THE CASE VERY OFTEN, BUT и CAN THINK OF A COUPLE OF CASES OFF HAND WHERE уср FILES WERE A CASE OF "WHAT YOU SEE IS NOT NESSESSARILY WHAT YOU GET". иF YOU'RE NOT SURE WHAT YOU'RE DEALING WITH, IT WOULD BE PRUDENT TO DEARCHIVE THE ARCHIVE TO A DIFFERENT DISKETTE AND MAKE SURE THE FILES BEHAVE AS EXPECTED BEFORE ASSUMING THAT THE CONTENTS OF THE уср FILE REPRESENTS THE WHOLE TRUTH AND NOTHING BUT THE TRUTH. а WORD OF CAUTION IN REGARDS TO рел FILES. фIRST OF ALL, SINCE A рел FILE MAY HAVE BEEN CREATED ON A 1581 AND DISSOLVED ON A 1571, ITS POSSIBLE THE FILE WILL BE TOO LARGE TO FIT ON THE DESTINATION DRIVE. еVEN THOUGH THE FILE MAY PHYSICALLY FIT ON THE DESTINATION DISK, цOMMODORE дос RESTRICTS THE MAXIMUM SIZE A рел FILE MAY BE, AND THE MAXIMUM SIZE VARIES FROM ONE DRIVE TO ANOTHER. иF IT DOES HAPPEN THAT THE FILE IS TOO LARGE, YOU'LL GET AN ERROR 52,фILE тOO лARGE,00,00 AND лхь WILL SKIP THE FILE AND GO ON TO THE NEXT ONE. и HAVE TESTED лхь AND лха WITH рел FILES ON BOTH THE 1571 AND THE 1581 AND HAVN'T ENCOUNTERED ANY DIFFICULTIES. нIETHER PROGRAM DOES ANYTHING OUT OF THE ORDINARY, SO и WOULDN'T ANTICIPATE ANY PROBLEMS WITH OTHER DRIVES. аS STATED ELSEWHERE, THE цOMMODORE FILETYPE INFORMATION, INCLUDING THE релATIVE FILE RECORD LENGTH IS IMBEDDED IN THE лхарцHIVE SUCH THAT THE аMIGAдос AND/OR мс-дос VERSIONS OF лхарц WILL IGNORE IT. цONSEQUENTLY, IF YOU WERE TO DISSOLVE AND THEN RE-ARCHIVE AN лхарцHIVE CONTAINING FILETYPE INFORMATION ON ONE OF THOSE MACHINES, THE FILETYPE INFORMATION AND RECORD LENGTH WOULD BE LOST. лха ALWAYS CHECKS TO SEE IF THE TARGET ARCHIVE EXISTS BEFORE PROCEEDING. иF IT DOES, THEN IT WILL APPEND TO IT. иF IT DOES NOT, THEN IT WILL CREATE A NEW ONE. фOR PORTABILITY, лха CONVERTS THE FILENAME TO STANDARD асции BEFORE PUTTING IT IN THE ARCHIVE HEADER AND CONVERTS BACK TO цOMMODORE асции ON EXTRACTING THE ARCHIVE. оTHERWISE THE FILENAME IS LEFT ALONE. тHUS SPACES AND OTHER CHARACTERS WHICH WOULD BE ILLEGAL IN OTHER OPERATING SYSTEMS ARE ALLOWED. иF YOU ARE PLANNING TO DISSOLVE THE ARCHIVE ON A NON цOMMODORE MACHINE, IT IS YOUR RESPONSIBILITY TO MAKE SURE THAT THE FILENAMES ARE SUCH THAT THEY WON'T CAUSE PROBLEMS WHEN DEARCHIVED ON THE TARGET OPERATING SYSTEM. оN OPERATING SYSTEMS THAT SUPPORT SUBDIRECTORIES, лхарц ALLOWS YOU TO STORE THE FULL PATH AND FILENAME IN THE ARCHIVE. сINCE цOMMODORE'S дос HAS NO SUBDIRECTORY SUPPORT, лхь SIMPLY IGNORES'S ANY PATH AND ONLY USES THE FILENAME. тHIS HAS A COUPLE OF ADVERSE EFFECTS... 1) сINCE THE FORWARD AND BACKWARD SLASH ARE LEGAL IN цOMMODORE FILENAMES, ANY SUCH NAMES WILL BE MISHANDLED. тHE ONLY SOLUTION IS TO RE-NAME THE OFFENDING FILE BEFORE OR AFTER ADDING OR EXTRACTING IT FROM THE ARCHIVE. 2) а FILE WITH THE SAME NAME MAY EXIST IN MORE THAN ONE SUBDIRECTORY. сINCE THE SUBDIRECTORY NAME IS STRIPPED OFF, THE SECOND ONE WILL OVERWRITE THE FIRST ONE. тO AVOID THIS USE THE -R OPTION WITH лхь. тHIS WILL CAUSE лхь TO RENAME ALL FILES WHICH ALREADY EXIST. лхь WILL WRITE A BATCH FILE CALLED "дUPLICATES" WHICH YOU CAN EDIT AND EXECUTE WHEN ALL IS SAID AND DONE. лха SHOULD WRITE A NULL HEADER TO MARK THE END OF THE ARCHIVE, BUT IT DOES NOT SINCE BOTH THE аMIGA AND мс-дос лхарц PROGRAMS CORRECTLY DETECT THE END OF THE ARCHIVE WITHOUT IT. тHIS MEANS THAT YOU CAN CONCATENATE TWO лхарцHIVES TOGETHER TO GET A VALID лхарцHIVE PROVIDED THAT BOTH WERE CREATED WITH лха AND NO ьмодем OR OTHER PADDING HAS CHANGED THE FILE'S LENGTH. тHIS IS ALSO WHY ITS ок TO APPEND TO AN EXISTING лхарцHIVE. хOWEVER, IF THE лхарцHIVE WAS DOWNLOADED VIA ьмодем OR CREATED ON AN аMIGA OR пц, YOU SHOULD NOT TRY TO APPEND TO IT AS THE ADDITIONAL INFORMATION MAY BE LOST WHEN лхь SEE'S THE нулл HEADER AND THINKS IT REACHED THE END OF THE ARCHIVE. тHERE IS A SOLUTION TO THIS, BUT ITS A FAIR BIT OF WORK AND PROBABLY NOT WORTH THE EFFORT. вHEN ITS FINISHED, лха TELLS YOU THE TOTAL NUMBER OF BYTES IT HAS READ FROM, AND THE TOTAL NUMBER OF BYTES IT HAS WRTTEN TO DISK. иF YOU'RE CREATING A NEW ARCHIVE THESE NUMBERS REFLECT THE TOTAL CONTENT OF THE ARCHIVE INCLUDING THE сфь HEADER IF ITS AN сфь. иF YOU'RE APPENDING TO AN EXISTING ARCHIVE THESE NUMBERS REFLECT ONLY THE NEW INFORMATION ADDED. лха SAVES THE FILETYPE IN THE ARCHIVE, SO сея AND прг FILETYPES ARE RETAINED WHEN EXTRACTED. оF COURSE, THIS IS ONLY TRUE IF THE лхарцHIVE WAS MADE WITH лха. иF FILETYPE INFORMATION IS PRESENT IN THE ARCHIVE, IT WILL OVERRIDE THE DEFAULT FILETYPE USED BY лхь. тHE FILETYPE BYTE IS BURIED IN THE FILENAME IN SUCH A WAY THAT IT WILL BE IGNORED BY THE мс-дос OR аMIGA лхарц. аS THE ARCHIVE GETS BUILT, лха TRIES TO IMPRESS YOU BY BUILDING A BAR GRAPH OF THE FILE'S SIZE BEFORE AND AFTER COMPRESSION. еACH VERTICAL BAR IS 1/4 OF A CHARACTER WIDE AND REPRESENTS 256 BYTES. тHUS EACH CHARACTER REPRESENTS 1к. аS THE FILE IS COMPRESSED, THE BAR REPRESENTING THE ORIGINAL SIZE IS BUILT. лATER, WHEN FLUSHING THE 1750 TO DISK, THE BAR REPRESENTING THE COMPRESSED SIZE IS BUILT OVERTOP OF THE ORIGINAL BAR, BUT IN A DIFFERENT COLOR LEAVING YOU WITH A VISUAL IMAGE OF WHAT'S GOING ON. вITH THE DATA COMPRESSION ALGORITHM EMPLOYED, THE BETTER THE COMPRESSION RATIO, THE SLOWER THE COMPRESSOR RUNS. сO, IF лха SEEMS TO BE TAKING A RATHER LONG TIME GOING ABOUT ITS BUSINESS, THE FILE BEING ARCHIVED IS PROBABLY COMPRESSING RATHER WELL. аLSO, THE DECOMPRESSOR WILL RUN FASTER THE HIGHER THE COMPRESSION RATIO. тHUS IF лха TAKES A LONG TIME ON PARTICULAR FILE, лхь WILL TAKE LESS TIME THAN NORMAL FOR THAT FILE. рATHER THAN SPECIFY ALL OF THE FILENAMES TO BE ARCHIVED ON THE COMMAND LINE, лха ALSO ALLOWS YOU TO SPECIFY THEM IN A FILE. фOR EXAMPLE THE COMMAND ... лха TEST @A:NAMES WOULD TELL лха THAT THERE IS A FILE "A:NAMES" WHICH CONTAINS A LIST OF THE FILES TO BE ADDED TO THE ARCHIVE. тHIS WOULD BE USEFUL, FOR INSTANCE, IF YOU'RE WORKING ON SOME PROJECT AND WANT TO PERIODICALLY BACKUP YOUR WORKING FILES. ыOU COULD SAVE A BIT OF TYPING BY PUTTING A LIST OF THE FILES YOU WANT TO ARCHIVE IN A BACKUPLIST FILE. тHE MAIN REASON FOR THIS OPTION, HOWEVER, IS TO ALLOW лха TO INTERACT WITH OTHER PROGRAMS. сUCH PROGRAMS (SOME SORT OF MENU DRIVEN FILE SELECTOR FOR INSTANCE) COULD SAVE THE FILENAMES THEY WANT ARCHIVED IN A FILE AND THEN INVOKE лха FROM A BATCH FILE. тHE FORMAT OF THE @NAMES FILE IS AS FOLLOWS. лха WILL IGNORE ANY LINES WHICH DO NOT CONFORM OR BEGIN WITH A SEMI-COLON. еACH LINE IS OF THE FORM.. D:NAME,T ;ANYTHING AFTER THE T IS IGNORED NAME - MUST BE 16 CHARACTERS OR LESS AND CANNOT CONTAIN ANY WILDCARD CHARACTERS ( * OR ? ) ,T - MUST BE PRESENT, AND 'T' MUST BE 'P' OR 'S' FOR прг AND сея RESPECTIVELY D: - IS OPTIONAL тO GIVE YOU AN IDEA OF HOW FAST (OR SLOW) лха AND лхь ARE, HERE ARE SOME SAMPLE TIMES. аLL TESTS WERE DONE USING THE IDENTICAL ARCHIVE. тHIS ARCHIVE WAS 112 цбм DISK BLOCKS WHEN ARCHIVED WITH арц128, BUT ONLY 82 DISK BLOCKS WHEN ARCHIVED WITH лха. лISTING OF ARCHIVE : 'тест.лзх' нAME оRIGINAL пACKED рATIO дATE тIME аTTR тYPE црц -------------- -------- -------- ------ -------- -------- ---- ----- ---- лха 11580 7468 64.5% 90-01-11 9:22:56 A--W -LH1- 6322 лхарц15.асм 11650 2718 23.3% 90-01-11 9:28:16 A--W -LH1- 82а5 лхь 10982 6977 63.5% 90-01-11 9:23:18 A--W -LH1- 503б лзхуф.ц 10021 3442 34.3% 89-11-26 7:28:10 A--W -LH1- 55д3 -------------- -------- -------- ------ -------- -------- 4 FILES 44233 20605 46.6% 90-01-11 9:28:36 сAMPLE тIMING ------------- цOMPUTER пROGRAM сOURCE дESTINATION тIME IN сECONDS TO -------- ------- ------ ----------- ------------------ цREATE дISSOLVE ------ -------- 20 мхZ 386 лхарц FLOPPY SAME FLOPPY 13.7 21.2 1.13C HARD DISK HARD DISK 6.2 5.0 4.77 мхZ ьт лхарц FLOPPY SAME FLOPPY 90.7 89.0 1.13C HARD DISK HARD DISK 54.1 29.8 аMIGA 500 лхарц 1.0 FLOPPY SAME FLOPPY 110.5 56.8 HARD DISK HARD DISK 96.9 29.0 ц128 лха/лхь 1571 1581 175.4 105.5 1581 SAME 1581 171.5 118.0 ц128 арц128 1571 1581 205.7 121.0 1581 SAME 1581 149.3 103.2 сO, ALTHOUGH THE 128 IS NO SPEED DEMON, THE TIMES ARE IN LINE WITH WHAT YOU MIGHT EXPECT FOR AN 8 BIT MACHINE AT 2 мхZ. фORMAT OF AN лхарц ARCHIVE: --------------------------- аN лхарцHIVE CONSISTS OF ONE OR MORE ENTRIES OF THE FOLLOWING FORM... фIELD дESCRIPTION хEADERсIZE 1 BYTE. тHE LENGTH OF THE HEADER. хEADERцHECKSUM 1 BYTE. сUM, IGNORING CARRY OF ALL THE BYTES IN THE HEADER EXCEPT хEADERсIZE AND хEADERцHECKSUM хEADERид 5 BYTES. "-лх1-" FOR COMPRESSED FILES, OR "-лх0-" FOR STORED пACKEDсIZE 4 BYTES. тHE LENGTH IN BYTES OF DATA WHICH FOLLOW THE HEADER. оRIGINALсIZE 4 BYTES. тHE FILE'S ORIGINAL LENGTH тIME 2 BYTES. тHE FILE'S CREATION TIME дATE 2 BYTES. тHE FILE'S CREATION DATE аTTRIBUTES 2 BYTES. тHE FILE'S ATTRIBUTES. фILENAMEлENGTH 1 BYTE. тHE LENGTH OF THE FILENAME IN BYTES. фILENAME тHE FILE'S FULL PATH\NAME црц 2 BYTES. тHE FILE'S CYCLICAL REDUNDANCY CODE CALCULATED USING THE SAME ALGORITHM AS пкарц 'пACKEDсIZE' BYTES OF DATA FOLLOW, FOLLOWED BY THE NEXT FILE IN THE ARCHIVE. нOTES: 1) лхь IGNORES THE тIME, дATE AND аTTRIBUTES FIELDS. 2) лха SETS THE аTTRIBUTES FIELD TO 0, THE тIME FIELD TO 1:00 AND THE дATE FIELD TO THE DATE YOU SET FOR цс-дос 3) тHE мс-дос AND аMIGA лхарц PROGRAMS STORE JUST THE FILENAME WITHOUT ANY TERMINATING нулл CHARACTER. лха STORES THE FILENAME FOLLOWED BY A TERMINATING нулл FOLLOWED BY A 'S','P','U' OR AN 'R' FOR сея, прг, уср OR рел FILETYPES RESPECTIVELY. иN THE CASE OF A рел FILE, AN ADDITIONAL BYTE CONTAINING THE RELATIVE RECORD LENGTH FOLLOWS THE 'R'. цOMPRESSOR пERFORMANCE ---------------------- аFTER CONVERTING A FEW MEGABYTES OF арц128 ARCHIVE TO лхарцHIVES IT LOOKS LIKE A TYPICAL SAVINGS IS IN THE ORDER OF 25-30% тHERE ARE SEVERAL WAYS OF LOOKING AT THAT. иF YOU HAVE A 1581 FLOPPY FULL TO THE BRIM WITH ARCHIVES, AND YOU CONVERT THEM ALL TO лхарцHIVES, YOU'D LIKELY GAIN ABOUT 200-250к OR ABOUT 800-900 BLOCKS FREE. аT $1.00 A FLOPPY, ITS LIKE PAYING ONLY $0.70-$0.75 A FLOPPY. иF YOU'VE GOT ALOT OF FLOPPIES, IT ADDS UP. иF YOU DON'T ITS NO BIG DEAL. иF YOU RUN A ббс ON A 128 WITH A 20 MEG HARD DRIVE THAT COST YOU $1000.00, IT WOULD BE EASY TO GAIN A HUNDRED OR SO BUCKS WORTH OF HARD DRIVE SPACE BY CONVERTING SOME FILES. иF YOU DOWNLOAD FROM геNIE AT $6.00 PER HOUR, ITS LIKE GETTING $1.50 AN HOUR REBATE IF YOU CHOOSE лзх OVER арц. иF YOU DOWNLOAD FROM цOMPUSERVE AT $12.50 AN HOUR, ITS LIKE A $3.25 AN HOUR DISCOUNT. иF YOU DOWNLOAD FROM A LOCAL ббс AND YOU HAVE A ONE HOUR TIME LIMIT, ITS LIKE HAVING YOUR TIME LIMIT EXTENDED TO AN HOUR AND TWENTY MINUTES. иF YOU'RE A DEVELOPER, AND YOU DISTRIBUTE YOUR PRODUCT IN ARCHIVED FORM, IT COULD MEAN THE DIFFERENCE BETWEEN ONE DISK PER CUSTOMER OR TWO. иN ANY CASE, ITS NOT TOO DIFFICULT TO JUSTIFY A $20.00 SHAREWARE CONTRIBUTION.