[ 53280,0:53281,0:646,(162):"":" USE LYNX TO DISSOLVE THIS FILE":10 1 *LYNX XV BY WILL CORLEY 2 GEOBEAPDOCS.CVT 113 S 94 GEOBEAP-2.1.CVT 165 S 84 geoBEAPDocspPRG formatted GEOS file V1.0? '$ $$$$4$$$4$$$$$$<Write Image V2.0Red StormgeoWrite V1.1 This file was created with Wrong is Write. Written by Joe Buckley. =  w ^0@0000000 geoBEAP 2.1 000000000(c) 2001-2004 by Bo Zimmerman 000000000This program is shareware. If you find the program useful, please register it. It will encourage me to continue developing this software. Registration instructions can be seen by executing the program. Please send any and all reports of praise or problems to bo@zimmers.net, or to the address shown on the registration screen. Only registered users will receive bug fixes and new feature enhancements.  @INTRODUCTION geoBEAP is a full featured archival program which supports numerous formats popular with GEOS and Commodore users. These formats include .D64, .D71, .D81, .CVT (GEOS Convert), .BEP (geoBEAP disk image format), .LNX (LYNX, all versions, including geoPack files), .ARK, ZipCode, and both the single and multi-file compressed EMUTIL disk image formats (also called .RLE). Some of the archive formats mentioned above are disk image formats. This means that they are archives of every track and sector on a diskette. The disk image formats are: .D64 (1541 disks only), .D71 (1571 disks only), .D81 (1581 disks only), .BEP (any GEOS/Wheels supported drives), ZipCode (1541 disks only), and the two types of EMUTIL formats (any GEOS/Wheels supported drives). The remainder of the archive formats are file archive formats. These formats support archives of selected source files, and include LYNX, ARK, and GEOS Convert.  @SYSTEM REQUIREMENTS geoBEAP requires the following hardware and software to execute: 1. Commodore 64 or 128. 2. GEOS 64 or 128, Wheels 64 or 128, gateWay 64 and 128, and MP3 64 or 128 (sorta... some operations will complete without problems, but then the app terminates abnomally. It's MP3s fault). 3. At least one GEOS compatible drive. Two drives are required for disk image formats. 4. The geoBEAP application.  @USING GEOBEAP geoBEAP is executed by double-clicking on its icon. This will bring up the main selection screen. On the screen you will see two large file windows, one of which is for the source drive, which indicates the disk containing the files to be packed or the disk on which an archive file to be unpacked is found. The other is the destination file window, which will show files on the disk where an archive will be created or where an archive will be unpacked to. 0@00000 Running along the sides of the file windows are four arrow buttons for viewing different pages of file names. The up arrow will go back a page toward the beginning of the disk, while the down arrow will show files further down in the directory. The farthest up arrow will show the first page of files, while the farthest down arrow will show the last page of files. Below each file window is a button for selecting which drive and disk is to be recognized as the source and destination. Clicking the drive button will cycle through your GEOS active drives from A to B to C to D and back to A. The disk button will prompt you to insert a new disk into the active drive for that file window. Users of Wheels 64 or 128 can use the disk button to select a new partition or subdirectory. The disk button can also be used to format standard CBM floppy drives (1571, 1541, and 1581). 0@00000 In the upper-middle part of the screen are selection boxes for  choosing whether you wish to pack or unpack an archive. A darkened square next to your selection will indicate which options are active0@00000 0@00000 In the upper-middle part of the screen are selection boxes for  choosing whether you wish to pack or unpack an archive. A darkened square next to your selection will indicate which options are active. This may be changed by clicking in an unselected box. Below there is a box to select the type of archive format. The text that appears inside this box will designate the selected format. Clicking on the box will change the format to the next available one. Continue to click on this box to cycle through all supported archive formats. The selected archive format, and whether the pack or unpack box has been selected, will determine whether files in the source window can be selected. While in the pack mode of a disk image format, no files may be selected. While in the unpack mode of any archive format, or the pack mode of a file archive format, one or more files may be selected. Up to 256 files may be selected for any purpose. The launch button will begin the packing or unpacking process as designated by your selections. At the top right of the screen is the exit box, which will exit back to the deskTop when clicked.  @LAUNCHING When the launch button is clicked, the system will examine your selections on the main screen to determine if the process can begin. What happens next depends on the selected format, and whether the pack or unpack box has been chosen.  @.D64, .D71, and .D81 images  Pack0@000000 @.D64, .D71, and .D81 images  Packing:  The .D64 format was first invented by the authors of the Commodore 64 emulator for the PC called C64S. The .D71 and .D81 formats followed later. Each is an uncompressed image of an entire disk, assuming the disk does not have any errors. These format can be used to archive 1541 disks, 1571 disks, and 1581 disks only and respectively. To create one of these archives, first make sure that one of the supported disk drives is the source drive, that the source and destination drives are different, and that a disk capable of holding the entire disk image archive file is in the destination drive. A 1541 disk image file (.D64) requires 689 free blocks on the destination disk. A 1571 disk image file (.D71) requires 1378 free blocks on the destination disk. A 1581 disk image file (.D81) requires 3200 free blocks on the destination disk. When clicking the launch button, the user will be asked to give a name (max 12 characters) for the archive file. The extension .D64 or .D71 or .D81 will be automatically added to the name entered. After confirming the process, a progress box located near the bottom of the destination file window will appear and update itself as the packing process completes. Remember that any disk errors on the source disk, such as those used as copy protection in some commercial programs, will abort the archival process.  @  Unpacking:  To unpack one or more of these archives, select their names in the source file window. Make sure that the destination disk is of the correct type (1541 for .D64, 1571 for .D71, and 1581 for .D81), and that the destination disk has been completely formatted. Unarchiving a disk image onto an unformatted disk will abort the process. Also remember that unpacking a disk image will completely erase any contents on the destination disk and replace them with the archive contents.  @  If more than one image archive file has been selected, a confirmation dialog box will appear between each archive file. When this confirmation box appears, the destination disk may be replaced in order to receive the next image archive. @ The destination disk must also be completely formatted before 0@000000 @geoBEAP (.BEP) images  Packing:  The .BEP format was invented by the author of this program as a substitute for ZipCode and .D64 disk image formats. The .BEP format features support for any GEOS supported disk or partition, and a much higher level of compression than that afforded by ZipCode or even the EMUTIL format. Like the .D64 image archive, a .BEP archive file contains an entire disk image. Unlike .D64 image archives, however, the .BEP format may be of a 1541 disk, a 1571 disk, a 1581 disk, a CMD FD2000 disk, a CMD HD partition, or a CMD RamLink partition.  @  To create one of these archives, first make sure that the desired disk and partition are displayed in the source drive window, that the source and destination drives are different, and that a disk capable of holding the entire archive file is in the destination drive. .BEP archive file sizes vary considerably. A relatively blank 1571 disk may compress to only 3k (12 blocks), while a 1571 disk full of programs may not compress much at all (970 blocks). Be sure to leave plenty of destination disk space for any possible archive. Failure to do so will abort the archival process, once the disk becomes full. Clicking the launch button will present the user with a dialog into which a name for the new .BEP archive file can be entered. The extension .BEP will be automatically added to the name entered. During the packing process, a progress box will appear in the destination window. The .BEP archive format uses a very complex algorithm in order to get very good compression of disks. Because this algorithm is so complex, the creation of these archives can take a very long time. A processor upgrade cartridge, such as the CMD SuperCPU, can improve the performance of this format considerably.  Unpacking:  To unpack one or more of these archives, select their names in the source file window. Make sure that the destination disk is of the correct type, which depends on the type of disk the .BEP file was made from. geoBEAP will present an error if, for instance, it is asked to unpack a .BEP image of a 1571 disk onto a 1581 disk in the destination drive. The destination disk must also be completely formatted before unpacking can begin. Unpacking a disk image onto an unformatted disk will abort the process. Also remember that unpacking a disk image will completely erase any contents on the destination disk and replace them with the archive contents.  @  If more than one image archive file has been selected, a confirmation dialog box will appear between each archive file. When this confirmation box appears, the destination disk may be replaced in order to receive the next image archive.  @  As mentioned above, the .BEP archive format uses a very complex algorithm in order to get very good compression of disks. Because this algorithm is so complex, the unpacking of these archives can take a very long time. A processor upgrade cartridge, such as the CMD SuperCPU, can improve performance considerably. erformance considerably. . . YNX archive, and Converted back from .CVT format to the GEOS file type format if necessary. REL (relative) files will also require additional processing to0@000000 @GEOS Convert (.CVT) files  Packing:  The Convert program was first created by Berkely Softworks, the inventors of GEOS, as a means of converting GEOS-type files into standard sequential CBM type files. Only in a sequential format can files be uploaded to the internet or BBSs. GEOS files that have been Converted will usually end with the extension .CVT, though almost as often as not there will be no extension at all. Convert will only affect GEOS type files, such as geoWrite documents, GEOS applications, desk accessories, and so forth. To convert, select the desired files in the source file window and click the launch button. If the source and destination drives are the same, the conversion will be performed in-place. In-place means that the GEOS file being converted will be replaced by the .CVT file. If the source and destination drives are different, geoBEAP will copy the source file onto the destination disk before performing the in-place conversion. This means that the destination disk must have enough space to hold the source files, and must not have files with duplicate names to either the source file, or the .CVT file being created.  @  During the file Convert process, a progress box located near the bottom of the destination file window will appear and update itself as packing completes. The extension .CVT will be automatically added to the names of the source files, and the source files will be given standard Commodore file names.  Unpacking:  The unConverting process will turn a .CVT file back into a usable GEOS file. To do this, select the .CVT files from the source file window and click the launch button. If the source and destination drives are the same, the unpacking will be performed in-place, meaning the .CVT file will be replaced by the GEOS file contained therein. If the source and destination drives are different, geoBEAP will copy the source archive file onto the destination disk before performing the in-place unpacking. This means that the destination disk must have enough space to hold the source files, and must not have files with duplicate names to either the source .CVT file, or the GEOS file being created. @ file being created. @ @ 0@000000 @ZipCode (1!, 2!, etc..) images  Packing:  ZipCode was written by A.L. Peters, and was both the first, and for a very long time the ONLY disk image archiver for Commodore computers. Zipcode will create a multi-file disk image archive of a 1541 disk. Although Zipcode supports a 4-pack format for standard 1541 disks, a 5-pack format for extended 1541 disks, and a 6-pack format for 1541 disks with errors, geoBEAP only supports the more common 4-pack version. Each file in a 4-pack archive begins with a number from one to four, followed by an exclaimation point (1!diskname, 2!diskname, etc). Zipcode will also use fast and effective compression. To create one of these archives, first make sure that the source drive is either a 1541 or 1571 disk drive, that the source drive contains a 1541 format disk, that the source and destination drives are different, and that a disk with at least a few hundred blocks free is available in the destination drive. If the destination drive is filled up during the creation of the Zipcode 4-pack archive, a dialog box will be presented to allow a new destination disk to be inserted so that the process may be completed. When clicking the launch button, the user will be asked to give a name (max 14 characters) for the archive file. The prefixes of a Zipcode archive (1!, 2!, 3!, and 4!) will be automatically added to the name entered. After confirming the process, a progress box located near the bottom of the destination file window will appear and update itself as the packing process completes. Remember that any disk errors on the source disk, such as those used as copy protection in some commercial programs, will abort the archival process. @  Unpacking:  To unpack one or more of these archives, select the first file in each 4-pack (the one beginning with 1!) in the source file window. Make sure that the destination drive is a 1541 or 1571 disk drive, and that the destination disk has been completely formatted. Unarchiving a disk image onto an unformatted disk will abort the process. Also remember that unpacking a disk image will completely erase any contents on the destination disk and replace them with the archive contents.  @  If more than one 4-pack set has been selected, a confirmation dialog box will appear between each archive. When this confirmation box appears, the destination disk may be replaced in order to receive the next image archive. rchive contents.  @  If0@000000 @LYNX (.LNX) file archives  Packing:  LYNX was originally written by Will Corely as a fast archival format for combining numerous Commodore files into a single archive file. In addition to its speed, LYNX is also famous as one of the only file archive formats which supports Commodore REL (relative) type files. Since the introduction of the original LYNX program, numerous other revisions and clones have appeared. This includes the LYNX series, up through LYNX XV, Ultimate LYNX, Ultra-LYNX, and eventually geoPack. geoBEAP supports them all, including (despite much pain and suffering), the Commodore REL (relative) type files. GEOS users may be familiar with the "fact" that GEOS does not support relative files. This may have been true before, but with geoBEAP, it supports them now.   To create a LYNX archive, select the desired files in the source file window and click the launch button. After entering a name for the new archive file (12 characters max), the packing process will begin.  The extension .LNX will be automatically added to the name entered.  If the source and destination drives are different, the first step will be to copy the sources files onto the destination drive. This means that the destination disk must have space sufficient to hold all of the source files, and must not already have copies of the source files. If the source and destination drives are the same, the archive will be created in-place. This means that all of the source files will be removed from the source disk directory and replaced with the single LYNX archive. 0@000000 Before creating the LYNX archive, geoBEAP will attempt to Convert all GEOS type source files into .CVT format files. Only in the .CVT format can GEOS files be placed into LYNX archives. Finally, the source files will be placed into the LYNX archive. If the source and destination drives were different, the archive will appear on the destination disk, and the source files will be unchanged on the source disk. If the drives were the same, the source files will have been replaced by the LYNX archive. During the creation of the LYNX archive, a progress box will appear in the destination file window. geoBEAP will create a LYNX XV compliant LYNX archive.  Unpacking:  To unpack a LYNX archive, select the archive file from the source file window and click the launch button. If the source and destination drives are the same, only one LYNX archive may be processed at a time, and the unpacking will occur in-place, which means that the LYNX archive file will be removed and replaced by the files which are the contents of the archive. If the source and destination drives are different, any number of LYNX archives may be selected, and the archive files will be copied to the destination drive before they are unpacked. This means that the destination disk must have sufficient space to hold the contents of the selected LYNX archives. During the unpacking process, a progress box in the destination file window will notify the user when files are being copied, unpacked from the LYNX archive, and Converted back from .CVT format to the GEOS file type format if necessary. REL (relative) files will also require additional processing to restore side-sector links. If more than one LYNX archive file was selected, a confirmation dialog box will appear between each archive file. ble, and better than Zipcodes will be used on the disk sectors. To 0@000000 @ARK (.ARK) file archives  Packing:  ARK was originally written by Edward Rohr, and supports an archive format for combining numerous Commodore files into a single archive file. ARK formatted archives are fairly rare, but are comparable in speed and functionality to LYNX archives. Some believe that ARK was a more stable and reliable program than LYNX.   To create an ARKive, select the desired files in the source file window and click the launch button. After entering a name for the new ARKive file (12 characters max), the packing process will begin. The extension .ARK will be automatically added to the name entered. If the source and destination drives are different, the first step will be to copy the sources files onto the destination drive. This means that the destination disk must have space sufficient to hold all of the source files, and must not already have copies of the source files. If the source and destination drives are the same, the ARKive will be created in-place. This means that all of the source files will be removed from the source disk directory and replaced with the single ARKive. Before creating the ARKive, geoBEAP will attempt to Convert all GEOS type source files into .CVT format files. Only in the .CVT format can GEOS files be placed into ARKives. Finally, the source files will be placed into the ARKive. If the source and destination drives were different, the ARKive will appear on the destination disk, and the source files will be unchanged on the source disk. If the drives were the same, the source files will have been replaced by the ARKive. During the creation of the ARKive, a progress box will appear in the destination file window. geoBEAP will create a ARK V2 compliant ARKive.  Unpacking:  To unpack an ARKive, select the ARKive file from the source file window and click the launch button. If the source and destination drives are the same, only one ARKive may be processed at a time, and the unpacking will occur in-place, which means that the ARKive file will be removed and replaced by the files which are the contents of the ARKive. If the source and destination drives are different, any number of ARKives may be selected, and the ARKive files will be copied to the destination drive before they are unpacked. This means that the destination disk must have sufficient space to hold the contents of the selected ARKives. During the unpacking process, a progress box in the destination file window will notify the user when files are being copied, unpacked from the ARKive, and Converted back from .CVT format to the GEOS file type format if necessary. REL (relative) files will also require additional processing to restore side-sector links. If more than one ARKive file was selected, a confirmation dialog box will appear between each ARKive file. etween each ARKive file. . . ld the contents of the selected LYNX archives. During the unpacking process, a progress box in0@000000 @EMUTIL single-file disk images  Packing:  The EMUTIL format was invented by the author of this program as a disk image format for multiple computers and disk drives. The original EMUTIL program runs on either a Commodore PET, or the C64, and is able to create a disk image archive file from any Commodore supported drive, including the old IEEE-488 drives, such as the CBM 8050 and CBM 8250. This format features support for any GEOS supported disk or partition, and a level of compression comparable (and slightly better) than Zipcode. Like the .D64 image archive, an EMUTIL archive file contains an entire disk image. Unlike .D64 image archives, however, this format may be of a 1541 disk, a 1571 disk, a 1581 disk, a CMD FD2000 disk, a CMD HD partition, or a CMD RamLink partition. Also worth mentioning is that, unlike the EMUTIL program, geoBEAP will place a special extension (.RLE) at the end of the EMUTIL archive files to better identify them. EMUTIL does not place an extension on its archive files.  @  To create one of these archives, first make sure that the desired disk and partition are displayed in the source drive window, that the source and destination drives are different, and that a disk capable of holding the entire archive file is in the destination drive. EMUTIL archive file sizes vary considerably. A relatively blank 1571 disk may compress to only 20k (80 blocks), while a 1571 disk full of programs may not compress much at all (1300 blocks). Be sure to leave plenty of destination disk space for any possible archive. Failure to do so will abort the archival process, once the disk becomes full. The EMUTIL .RLE format does not store any information about the original disk image format. For this reason, embedding the type of disk from which the archive was made (1541, 1571, etc) into the name of the archive would be wise.  Unpacking:  To unpack one or more of these archives, select their names in the source file window. EMUTIL image files created with geoBEAP will have the .RLE extension. EMUTIL image files created with EMUTIL may not. Make sure that the destination disk is of the correct type, which depends on the type of disk the EMUTIL file was made from. geoBEAP will not present an error if one of these archive files is unpacked onto the wrong type of disk, but will likely terminate prematurely. The destination disk must also be completely formatted before unpacking can begin. Unpacking a disk image onto an unformatted disk will abort the process. Also remember that unpacking a disk image will completely erase any contents on the destination disk and replace them with the archive contents.  @  If more than one image archive file has been selected, a confirmation dialog box will appear between each archive file. When this confirmation box appears, the destination disk may be replaced in order to receive the next image archive. chives. During the unpacking process, a progress box in0@000000 @EMUTIL multi-file disk images  Packing:  The multi-file EMUTIL format is identical to the EMUTIL single-file disk image format, except that the image is conveniently broken into numerous smaller files. Each file in a multi-file EMUTIL disk image archive begins with a number from one on up, followed by a dash (1-diskname, 2-diskname, etc). Multi-file EMUTIL disk image archives created with geoBEAP will also end with the .RLE extension. Like the single-file version of this format, a compression algorithm comparable (read: better) than Zipcodes will be used on the disk sectors. To create one of these archives, first make sure that the desired disk and partition are displayed in the source drive window, that the source and destination drives are different, and that a disk with at least a few hundred blocks free is available in the destination drive. If the destination drive is filled up during the creation of the EMUTIL multi-file archive, a dialog box will be presented to allow a new destination disk to be inserted so that the process may be completed. When clicking the launch button, the user will be asked to give a name (max 8 characters) for the archive file. The prefixes of a EMUTIL multi-file archive (1-, 2-, 3-, .etc) and the .RLE extension will be automatically added to the name entered. After confirming the process, a progress box located near the bottom of the destination file window will appear and update itself as the packing process completes. Remember that any disk errors on the source disk, such as those used as copy protection in some commercial programs, will abort the archival process. @  Unpacking:  EMUTIL multi-file disk image archives will always begin with a number and a dash, and those created with geoBEAP will end with .RLE. To unpack one or more of these archives, select the first file in each multi-file archive pack (the one beginning with 1-) in the source file window. Make sure that the destination drive is of the same type that the archive pack was created from, and that the destination disk has been completely formatted. Unarchiving a disk image onto an unformatted disk will abort the process. Also remember that unpacking a disk image will completely erase any contents on the destination disk and replace them with the archive contents.  @  If more than one multi-file pack set has been selected, a confirmation dialog box will appear between each archive. When this confirmation box appears, the destination disk may be replaced in order to receive the next image archive. l completely erase any contents on the destination disk and replace them with the archive contents.  @  If more than one image archive file has been selgeoBEAP_2.1PRG formatted GEOS file V1.0q I Iq A AA}))}geoBEAP V2.1@Bo Zimmerman geoBEAP creates and dissolves numerous disk image and file archive formats. /  q +FT `TV U 87? W V / Kp q  O * l `L,geoBEAP V2.1pk ?  (k pLqPlease re-insert geoBEAP disk.4 8 7 LP¥ "   k ` `轢 轢 W X W eX e`  x © sru(t  qp!sr!t u H  h`5  v U eV e U e V e ` 9u tU eV e  Xe  &1 $p sr/utU eV e H` r 9 $ r qpr !W !X X i X W !pp8p!p cW W X ܐ`" x" ©"srut "qp#sr#t u H "h`  9 $ "qpr `5 ͅ / U eV e U e V e ` D L" D" kL  ` `   ͸"` kL" ` k  ͸"` LH hH @OPhE P Phl  qap ` `͸"  qGpL  V­8"i9  "  ƅ P  V­L`aYL  L*Lccy<ûfc̓3>c̓3fc̓3fc̓3fcy3>; p" 5 \­"    " "   ZH"  " _ h`N0:DISK,IDU0>M0i/ "  L  V­@"i9  "  ƅ P  V­ LC  ¢` pD DD<  5 A7 II  D " 5 A7 IIFormat disk in drive: AFormat 1571 double-sidedAll data will be erased!Are you sure?Please insert new disk.Cannot remove geoBEAP disk. G JJ<)`   xU eV e HL  L @.D64/71/81 P.BEP image p.CVT GEOS `?!zipcode+4 .LNX LYNX .ARK Arkive .RLE (emutil)0.RLE ?-multi `  r `ʆp `pa ` ͸" a p!W pmW W rp cW !!`!`  D  * O * `  O  * D * `=ELZ QYLZ  U eV e U e V e `i>>H=H #oL h#h#h=h>#H#H =oLutL   Lvw Šww`p8pq 0 0 +ȱ ɠppȑpeppqp8pqqspr 3Pww`  Lpr ɠr`  L K3####3qp3st65i4# Hsȱȱ eȢ#3###rs trp cts`  Lvvvtp  p`prȥqr`  pLxv/qspr9  qsprpxxv ptȥqt`xxvsqrp  Lv####v` ¨i#vv ¨ȥP`v##i# ##`vvpP *`  cLppq`pq`tvv8`uww`Hvh`vHu~tP tub Vh`. O g   !"#$%&'0)D?Xsg p (t@Disk error:Unknown disk error.Not enough blocks.Illegal track or sector.Disk full.Directory full.File not found.Block deallocation error.Illegal VLIR chain number.VLIR: Illegal track or sector.Too many VLIR chains.File is not a VLIR file.End of file. File too long.Device not present.Write protect is on.No header block.Drive not ready.No data block.Bad block on disk.Write protext is on.Bad header block.Cannot open disk.File exists.DOS mismatch on disk.87L6?LV pGG  L̅LV pGG  LLV p@  L LV p@  Lqprn `f%h%g%$ f  K`  !L d$f$He$ )PȌd$h`qspr p r rsL`  LperrqessrrsL  L p pqspr pqP`  Lf%f% `f$ `g$f$$ f `d$e$f$g$e$`q( qpn  ?` #΅ ݭ#p(#o(  åj(i( 6r#n(sm(rn(m( x#rȭo(rȭp(rl(k(errs  j(i(& i ` rr cLj% j%i%`#  mk(k(l(# #j%#i%p(o(% i Щ#p(#o( #LP p PpLqsprr P rsL`  LperrqessrrsL'  Lp Pqspr pqP`  'L p(o(% i +Operation CompleteSelect a file to unpack.File is not a .D64 image!00 ©`qpwsr 0 LY0#0# qspr`qp / ӭ0 Lm*0ȱ.`ȱdD`ȱ14 60`70`80``,q4p0 6G,4H,` 7G,1H,`8G,1H,`Ready to unpack .D64 file?" 0#000 ,p,q ``Dest. Drive must be a 1541/1571.Dest. Drive must be a 1571Dest. Drive must be a 1581,,, 05% ©` ( )0P 2 -`ut-0ȍ0P'ubt-0͍0P ut-0ҍ0" G© u t` -`Drive type not supported.Not enough space on dest..D64.D71.D81 o!.Dd`P`0u0tt`0) a.0ȹa.00q0p0͏.0͎.L@0p000`k.k.v...#$F$5<BGP'Q p .L0 |0;000q p qq0p00 00ӐѢ`  .L0 |0E00q p ,qq0p0qspr`0 00Đ¢`  .L |0h00M00q p Eqq0p00 000000 0`qspr`  N/L |0h00A00q p E0 000000 0`qq0p0qspr`  /L0͉0 ©  0i..00`0͉0 ­00 `0u0tt0ȱt0`.D64.D71.D81 o!.Dd`P`0u0tt`0) a.L7) ͸" P)` Lu)L.Source and Dest. must be different!" 1LY L) 1*LW  *LWI4H4I4H4n LY  L*LWI4qH4pr !LY *LW*qhp C LWL+Operation CompleteSelect a file to unpack.File is not a .BEP image!Ready to unpack .BEP image?" ` -lA" nA p$nA.,+q+pL#+GnA+qNpL#+QnA`+qkpL#+C +qpL#+nA +qpL#+ plA +` `Dest. Drive must be a 1541/1571.Dest. Drive must be a 1571Dest. Drive must be a 1581Incorrect dest drive type.File is not in BEP format.Diff. partition sizes. Continue?`7X4a7~ABL4B_7`-- x, LY ,L4ꭀB#B# -s-r`--`qprrs O3 L4`7(LY L)7M-bL-`7+`7]7\7b77c7]7b\7P7b7]7a\7\7]7 pL4`Abע` -``7` x- -a7 a7X4P&X4a7PX4ʭR4Y4S4Y5V4Y6U4S4T4R4L,_7"L-M-_7M-]7L-\7`7(`T4 K-.T4 K-.U4`---x-`i`~A`~A -(~A(`T4U4PU4X4 S4R4ȍAP -Ȍ~AAV4`Y6ș~AY4Y5Ȍ~A~AV4`Y5L- 1LY uot s`o k. //" © qopr cLYLu/ J4C% ©` ( 2J4P6ut -K4CJ4P-ut$J4PutGJ4P uątQJ4" G© u t` /`Not enough space on dest. o!.Bb`P`/uptt`.BEPBBB#B# `7X4a7Y7^77\1b[1\1q[1pJ4p[1\1J4CK4ȑp[1\1 0LY 1^7 Z1P 1穂p S  *LW`qpwsr 2L4_U1T1q[7pZ7B#B#  ^0 1L4`a7a7R4`U1T1`S4`7`T1U1U1[7T1Z7` S1Y7X4*R4Y4S4Y5T4Y6S4R4Y7P 1X4X4PX4ʭR4Y4S4Y5T4Y6T4S4R4Y7L^0\1s[1rrrs7qbp7\1b[1" '`7 bAb7`7`T4`.^7&m[1[1\1^7\1A[1b`7`R4 Z1S4kAkA Z1`B) 1Bȹ1BBqBpB2B2L3pBBB`11122#$F$5<BGP'Q p 1LB 4;BBBq p qqBpBB B͂BӐѢ`  *2LB 4EBBq p ,qqBpBqspr`B B͂BĐ¢`  {2L 4hB́BMBBq p EqqBpBB B͂BBBB́B '4`qspr`  2L 4hB́BABBq p EB B͂BBBB́B '4`qqBpBqspr`  O3LB͉B ©  Bi22BB`B͉B ­BB `ꭄBuBttBȱtB``7`T4`.^7&m[1[1\1^7\1A[1b`7`R4 Z1S4kAkA Z1`B) 1Bȹ1BBqBpB2B2L3pBBB`11122#$F$5<BGP'Q L7) ͸" P)` Lu)L.Source and Dest. must be different!" 4"  )LWLY L) *LW L) *LWDest. drive not a 1541/1571.^7]7`7_7 + LW*qp C LWꭡ #0 c+ L)`7_7n   +LW  *LW`7q_7pr !LY -L* L)LYOperation CompleteSelect a file to unpack.File isn't 1st Zipcode image!Ready to unZipcode images?Insert next volume disk.`7q_7p sqrprr !q 1 *`0q `7q_7``7_71 c7d7`2 c7d7`3 c7d7`4 c7#d7``e7t77,7;7DUSe7r77,7P7D31e7q77,7c7De7p77f7f7`             `7_717 ,Χ7`7P魲888ɵ08qpDsr888 q8p8 `8Ͳ88ͱ88q8pp88`888888 u,`c7DDD#D#  +b7 -`b7b7e7`qp7s7rD7D7D d67D7D`DDd7L,-d7"`` ,`a7 ,`DDe7`a7)?͵DDf7f7a7)ɀL3.a7)@@L.7`De ,`77` ,`7 ,`77`De ,`ͦ7 77P( ,`7 ,`Χ7Χ777Ψ77Χ7ж``De ,`` 4LY ust s`s S/ 0L." ­`7q_7pr cLY 0LYp S /`p S  *LWLY ­   /` G 77" G©  Ȑ` /`Not enough space on dest.Source is not a 1541/1571. #0" G©  Ȑ`  w0` `q 9q `0q `7 _7q `7p_7p 9p `0p `7 _7p `7o_7o `Destination full. Insert next.0ut ot `7q_7`001!888 c+c7D "4`b7DD#D#  +D7D7D`qp`sre7ess 57D7D`7q7pb7pD 1`b7b7e7ېDDd7L0 4`d7"`` 2>D S4`D S47`De7 S47ߢ`(D @ S4D S4`De S4`D S4ɭD S47 S4й7 S4бL2`De88D8' S4`έ8P7 S488 S488 S4 ж8ЮL28 S4` S4έ8P7 S488 S4ٱ S4Ң`77777`De88i8H 8m778m778m77P$77777777i788777 Б8ЉL38H 8m778m778m77P$77777777i777`8`7`777`7`D S4 S4` S4 S47 S4魙7 S4`H~8D8ɵ 4~h`8q8p88hp~`8qp8s8r888rrs '`D) 4Dȹ4DDqDpD,5D+5L6pDDD`555&5+5#$F$5<BGP'Q p 4LD 7;DDDq p qqDpDD D͸DӐѢ`  ?5LD 7EDDq p ,qqDpDqspr`D D͸DĐ¢`  5L 7hDͷDMDDq p EqqDpDD D͸DDDDͷD <7`qspr`  5L 7hDͷDADDq p ED D͸DDDDͷD <7`qqDpDqspr`  d6LD͉D ©  Di+5-5DD`D͉D ­DD `ꭺDuDttDȱt͵D` 4~h`8q8p88hp~`8qp8s8r888rrs '`D) 4Dȹ4DDqDpD,5D+5L6pDDD`555&5+5#$F L7) LB)L+)qŅp ͸")qp  L9* )LW L9* )LWOperation CompleteSelect one or more files.Ready to unconvert file(s)?Copy and unconvert file(s)?Ready to convert file(s)?Copy and convert file(s)?:: ­ ͸"Q+qp:s:r :q:p:s:r`utwv"x ,LY" ©+qp:s:r :q:p *6 L|)ĭ:q:p"+p+++ +qp LY L|)" is not CVT!" is not GEOS!Copying:Converting:Unconverting:*qp ͸"*qp  L, )LW L, )LW:: ­ ͸"Q+qp:s:r :q:p:s:r`utwv"x ,LY" ©+qp:s:r :q:p 5 L,ĭ:q:p"+p+++ +qp LY L,`:x:u:t:w:v:qpn  ` #::::::::#:#:#)# -Ю# -Т:LP.  , L##::::: : `: : ȱ :P:`##::: ::: :: `::L'.: : : :ȱ :Ȍ:`茫:` k2 /`::::: Q2 0 . q/ڮ:: Q2 0Ȯ:):::: k2в /::::` Q2Е 1`:` 2: : : ȥ: : : ,:: 2: :  ȥ :: 8: : ȱ :P:::::::` 2C: :  :::ȥ :::: 2:ȥ::`::`: '.筢:ͤ::ͣ:`::: : `: : :ȱ ::L/srn ?` G # #` ˥::::::#΅#)#er P :: `: :  &:):::::  2`::: 1:: : : ȭ: :: `::::: : ::P`::ͺ::͹:L0::::ȭ:Ȍ:`::L1:::: : `::: : ԭ: : ) 2: : J k2`:͉  G`: : J`:͉ `  `:`::::::::::::::::::: : `: : $:::: z4 4ٸP$ 3 4` :ȱ : z4 4дܭ: : :: ȭ: :i:: 3 4`::::: : `:::: ::::: : `: : ::ȱ 蝻:莫: Ţ`: : :: `:: : : : 轻: L(5: : :: `:)`:::: `:: ­::: : :::: ` 2::: : `: : : ȭ: ȩ :: `: : :: ȭ: Ȍ:: : `: : :ȱ :: `4`:L(5 `4: : :ȱ :::L4`qpn `;; ; ; ) ` ;ȱ ; :ȱ : 8 R8` -9 8 k9`  5Lqpn `;; ; ; ) ` 6` 6` R7`  *6L; ;  ;ȱ ;: ԅ `:{:`; ; : : ȭ:  `; ;  ;ȭ ; ѭ;; и G­;; J¢`:`;; V;;;; ;;Y;ȹ;;;;ș;; `;;;թ;  ;; `; ; :{:: ȩ::ș::ș:` G`  ` #΅ ; ; # ȭ# J`: ԅ ## `; ;   ɠ7:7:Y: 2:  i ȱ i ;; `:: `;; :: `:`;; ?;;; ;;dȹ `; P۬;;ȭ; ;;ȹ е;; `.CVT_}{~`\|abcdefghijklmnopqrstuvwxyz-[]+'/!ABCDEFGHIJKLMNOPQRSTUVWXYZPRG formatted GEOS file V1.0L4`qpn `;; ; ; ) ` ;ȱ ; :ȱ : 8 R8` -9 8L7) LB)L1 ͸" 1: +*qp ͸"*q6p  LK+ )LW )P ͸" LK+ )LWOperation CompleteSelect a file to unpack.Select only one (1) file.Select one or more files.Ready to de-LYNX file?Copy and de-LYNX file?Ready to LYNX file(s)?Copy and LYNX file(s)?" is not LYNXed!Copying:LYNXing:Closing:De-LYNXing:Converting:Unconverting:Re-Linking:FF`FF ­ ͸"H*qpFsFr FqFpFsFr`utwv"x -9LY" ­FqFpr !߭FF m0L1 b1qFpF 0 5,LY ,-FFFFF &/ L)Mq@p B1_@MX+qpMs@r FF7 b14qp&qFpFFq˅p B18F`L,FF8FɄ b1mqp_qFpFF b1KqFpFqp3FF@M FFFF`` `FFFFȭFȭFȽ@M șȭFȩiFȭFL-F)LE. .,F8FFFFFFF `FFFFFFFп ¬FȭFȭFFiFȭFLE.FF UFFFFFFFF  FF `FFFFFFFFxF8xFFFFP٭FFFFFF FF`FF 8``FF+q/pFsFr FqFp XB_XN N )Gȱ pMȱ qM nMȱ oM}aM`M+q>pFsFr  G > J¸P`FFFFFF+FFFFFFFFLB/`FFFFFFFF FF `FFP p  p` p 09 FPHF 7qFpFGqphP p` `1 LYNXFqFp"*p*** *qp LW p` pp` p` 09FF 7`!` uot sSo N Y6FFGFF*qOp ͸"*qhp  L2 *LW L2L2FF ­ ͸"k*qpFsFr FqFpFsFr`utwv"x -9LYuM tM sMrM 8" ¸PFFn 8FF+q"pFsFr FqFp A L2Љ L2" © qopr cLYFFFF H5GFFL3LWmFFFFFFFL3+q p sor pl(Fk(FFmk(k(Fml(l( S v4LY )LW 6eF F 8+qpFsFr FFFFFFFP&FFFF ` 6F@FFFF ЭFFFFFF 6еFFFF '8ФL?3 p(o( `FF 쩁 FF ӭFqFp *7bF FF ПGqpqFpF`pȱp p ȱp eppqPFF5 P`FF}FqFp *7p PpqP $9ͭp(Fo(F`[ 53280,0:53281,0:646,(162):"":" USE LYNX TO DISSOLVE THIS FILE":10 *LYNX XV BY WILL CORLEY FFFFFF FFPâ` o!.Ll`P`6utt`.LNXFFFFȱ ` ȱ F F ɠ=M=MMF@F )FFFF Fȱ F`0FqpdFiFp8dpqPȥqp FiFp8 pqPȥpyFFȩFFqpF0 pqP`qpȹF`F0pqF8FP߈F0 eppqF8FP𺈹F0deppqF8FP`FqFp o 9j 9eFqFp *7 Q $9LF PB $9=F 93qFp *7  $9 9qp *7  $9` Fȱ FFF )8FR F`DSPURCIFFȥȥ ȥ mFFF` P` P` 9 9`^Mx_MuaMt`MweMvdMqpn  ` #gMfMiMhMaMcM`MbM#kM#jM#)# :Ю# 9ТML~:  -9 L##bMfMcMgMcM bM `cM bM ȱ cMPcM`##bM`MhM cMiMaM cMaM `lMvMLU:iM hM lM jMȱ kMȌlM`lM` > ;`mMaM{M`MzM > M< : ;ڮmMmM > =ȮmM)aMcM`MbM >в ;aM{M`MzM` >Е >`gM` >uM tM nM ȥoM gM fM ,MM >gM fM  ȥ MM 8gM fM ȱ gMPgM{MfMzM{MgMfM` >CuM tM  xMpMMȥ yMqMMiM >MȥMwM`jMiM`lM U:cMeMbMdM`kMjMcM bM `cM bM jMȱ kMcML;srn ?` G # #` ˥sMrMuMtMuMtM#΅#)#er P sMrM `{M zM  &iM)mM{MzMcMbM  >`MMwM =wM{M zM M ȭM MM `MMMM{M zM iMwMP`{McM{MbMzML=iMhMvMMȭMȌvM`vMvML=iMyMxMiM hM `sMrMuM tM ԭuM tM ) >M M J >`_M͉  G`M M J`^M͉ `  `M`aMgM`MfMaMiM`MhMiMiMcMhMbMcMvMmMoMnMgM fM `gM fM $oMyMnMxM @ AٸP$ ? C@` xMȱ yM @ @дܭgM fM vMxM ȭyM vMivMmM ? C@`mMpMoMnMgM fM `lMyMxM|M yM}MxM|MiM hM `iM hM lM|Mȱ |MlM Ţ`iM hM yMxM `lMiM hM mM |M |M LVAiM hM yMxM `_M)`yMxMyMxM `yMxM ­oMnMgM fM oMyMnMxM ` >yMxMgM fM `gM fM xM ȭyM ȩ oMnM `iM hM lMpM ȭqM ȌlMcM bM `cM bM pMȱ qMpM @`lMLVA @iM hM xMȱ yMmMmMLC@`qpn `NN N N ) ` Nȱ N Mȱ M ?D D` [E D E`  ALqpn `NN N N ) ` B` B` C`  XBLN N  Nȱ NM `MݩF`N N M M ȭM  `N N  Nȭ N ѭNN и G­NN J¢`M`NN VNNNN NNYNȹNNNNșNN `NNΜNթN  NN `N N MFM ȩMMșMMșM` G`  ` #΅ N N # ȭ# J`M ## `N N   ɠeFeF뽇F `F  i ȱ i NN `MM `NN MM `M`NN ?NNN NNdȹ `N P۬NNȭN NNȹ еNN `.CVT_}{~`\|abcdefghijklmnopqrstuvwxyz-[]+'/!ABCDEFGHIJKLMNOPQRSTUVWXYZPRG formatted GEOS file V1.0LC@`qpn `NN N?L7) LB)La0 ͸" S0: +*qp ͸"*q5p  LD+ )LW )P ͸" LD+ )LWOperation CompleteSelect a file to unpack.Select only one (1) file.Select one or more files.Ready to de-ARK file?Copy and de-ARK file?Ready to ARK file(s)?Copy and ARK file(s)?" is not ARKed!Copying:ARKing:Closing:De-ARKing:Converting:Unconverting:Re-linking:`C_C`hCgC ­ ͸"H*qp`Cs_Cr `Cq_Cp`Cs_Cr`utwv"x 5LY" ­`Cq_Cpr !߭mClC /L0 ^/ ,LYeCeCfCfCeC u. L) `cCdCbCaC pcC)kCcC pӍ|CicCrCȭsCȩcC pЭcC@IɠIՌcCI!+qpIsr sCrC`cCșȌcCL, p'~CcCcC pUC p`C p}CcCUCcC pԬcCzC pcCcC{ChCgCI hCgCgChCL-`CxCyCkCzC8xCzC{CyC{CsCrC `sCrCzCzC{C{CzCп|C kCUdCirCȭsCsCrC ?sCrCxC֭}C bCaC ``C_C 8``jCiC+q(pjCsiCr jCqiCp >_XK K )Gȱ Iȱ I Iȱ I}II+q7pjCsiCr  G r; J¸P`iCjCjChCiCgC+jCiCiCjCjChCiCgCL.`mCsClCrCoCnCsCrC sCrC `sCrCP p`eCfCeCeoCnCnCoC8Pܢ``Cq_Cp"}*p~**~* *q}p LW!` uot sSo N ?4fCeCChCgC*qMp ͸"*qep  L0 *LW L0L1`C_C ­ ͸"k*qp`Cs_Cr `Cq_Cp`Cs_Cr`utwv"x 5LYI I II 5" ¸P`C_Cn 5eCfC+qp`Cs_Cr `Cq_Cp f> L0Љ L0" © qopr cLYwCvCqCpCTCSCCjCiCeC PLw2LWmiCiCjCjChCiCgCLw2+qp sor pl(oCk(nCSCmk(k(TCml(l( S `3LY )LW 4e rCȱ sC*qp`Cs_Cr {CzCvCsCqCrCpCP&sCrCwCvC ` 3yCxC}C|C|CtCFuCtCsCrC жuCsCtCrCuCtC 3Л}CsCwCrCvC 5ЄL 2 p(o( `qCpC p(o( کCqpqhCpgC`pȱp p ȱp eppqPxCyCzC{CSCTCsCrC sCrCP` o!.Aa`P`4utt`.ARKuCtCjCiCȱ bCaC ` ȱ dC cC ɠIII`C_C )  tCȱ tC`dC cC P`|C PUCUC PUCUCUCUC PUCUCxC Pе}C PЫzC PС{C P`hCgCȥȥ ȥ mgCgChC`IxIuItIwIvIqpn  ` #IIIIIIII#I#I#)# 6Ю# [6ТJL7  5 L##IIIII I `I I ȱ IPI`##III III II `IIL6I I I Iȱ IȌI`I` #; r8`IIIII ; 8 7 )8ڮII ; 9ȮI)IIII #;в r8IIII` ;Е :`I` H;I I I ȥI I I ,JJ H;I I  ȥ JJ 8I I ȱ IPIIIIIII` H;CI I  IIJȥ IIJI H;JȥJI`II`I 6IIII`III I `I I Iȱ IILr8srn ?` G # #` ˥IIIIII#΅#)#er P II `I I  &I)IIIII  H;`JJI e:II I J ȭJ JJ `JJJJI I IIP`IIIIIL9IIIJȭJȌI`IILe:IIII I `III I ԭI I ) r;J J J #;`I͉  G`J J J`I͉ `  `J`IIIIIIIIIIIIIIIIIII I `I I $IIII 2= =ٸP$ h< <` Iȱ I 2= ==дܭI I II ȭI IiII h< <`IIIII I `IIII IIIII I `I I IIȱ II Ţ`I I II `II I I I I L=I I II `I)`IIII `II ­III I IIII ` H;III I `I I I ȭI ȩ II `I I II ȭI ȌII I `I I Iȱ II =`IL= =I I Iȱ IIIL<`qpn `KK K K ) ` Kȱ K Jȱ J @ A` A nA #B`  f>Lqpn `KK K K ) ` ;?` v?` @`  >LK K  Kȱ KJ  `5J3C`K K J J ȭJ  `K K  Kȭ !K ѭKK и G­KK J¢`,J`!K K VKKKK KKYKȹKKKKșKK `KKKթK  !K K `K K J3CJ ȩJJșJJșJ` G`  ` #΅ K K # ȭ# J`J  ## `K K   ɠBBC B  i ȱ i KK `JJ `KK JJ `J`KK ?KKK KKdȹ `K P۬KKȭK KKȹ еKK `.CVT_}{~`\|abcdefghijklmnopqrstuvwxyz-[]+'/!ABCDEFGHIJKLMNOPQRSTUVWXYZPRG formatted GEOS file V1.0