›1;32mCrMview v1.00 by Zebedee ©Area 51 (18-Mar-98)›0m ›4mDisclaimer›0m This program is supplied as-is. No warranty may be implied. You use this at your own risk. No files contained within the archive may be modified or reverse engineered in any way! ›4mIntroduction›0m On my system I've crunched all my executables with CrunchMania and all my text documents and AmigaGuide files with PowerPacker. For quite some time I've wanted to crunch the text files with CrM but I don't own a CrM text viewer and quite like the way PPMore operates. Only recently I thought about writing an interface utility for CrM and here it is. ›4mRequirements›0m Enough memory and T: assigned somewhere (see Usage Hints, below). ›4mInstallation›0m Just copy the executable to a valid path and this documentation somewhere handy where you can readily access it if needed. ›4mUsage (CLI)›0m Just specify the path and filename of your datafile and press return. Because of the way I've written the code (this bit's bad) don't use filename quotes and don't put any trailing spaces at the end of the filename. So if you've got KingCON installed (like I have) then when pressing tab to complete the filename you must delete the space KingCON puts on the end or CrMview won't find it. Users of Directory Opus who want to access CrMview must select "No filename quotes" from the listview gadget. You can specify a ? as the parameter for some info. ›4mUsage (Workbench)›0m Change the tool type of your data files to "CrMview" and you're away. ›4mHow It Works›0m It reads in the crunched file and chucks it out to T: as a temporary file. If you use CrMview from the CLI then the temporary file will be called "CrMview.tmp". It then checks the extension on the end of thefilename and activates the appropriate viewer. When you quit the viewer, CrMview will then delete the temporary file and quit. A small window is opened informing you of what it's doing. ›4mUsage Hints›0m If you have a hard drive, you might like to create a new directory somewhere and assign T: to it. This would greatly improve the performance of quite a few utilities like LHA and LZX that use T: for temporary storage. On my system I've installed FMS and created DF1: and renamed as T. This has an even greater advantage that should some utility go beserk I won't have to retrieve a load of data on the partition, but simply re-format DF1. ›4mPlans For The Future›0m Although CrMview is fully functional and works fine, I do have plans to add the following at some time in the future... * Better file recognition Instead of using the file extension to check the type of file, use the library "WhatIs.library" on the temporary file. * Better CLI argument routine The KS2 ReadArgs() function would be a very welcome improvement. * Ideas Any helpful suggestions you can come up with. Please remember that I do also plan on keeping CrMview as small as possible. ›4mExtra Notes›0m A few days after I wrote this doc file I wrote a preferences utility for CrMview. Although CrMview doesn't use the preferences file in any way, I thought I'd include it just so you can get a taste of what's to come! This file requires reqtools.library to function. ›4mBonus Utility›0m I've included the VERY FIRST working pre-beta version of CrMview under the name of CrMtype. This reads in the crunched file and chucks it out to the CLI window. Useful maybe for compo disks and you could even redirect the output to a file... ›4mContact Address›0m If you want to write to me, you can write to me at: 6 Bridgefield Ottery St Mary East Devon EX11 1HL ENGLAND EOF