Msg: 6582 *Conference*
06-15-96 15:35:36
From: JAMES KENNEY
To : RICHARD HANSON
Subj: CHECKALL/CHKALL
I have just uploaded these programs, which allow the easy identification of files in terms of size, checksum, and a weighted sum, as the previously uploaded CHECKSUM/CHKSUM do, but the names of the files to be checked may now be drawn from an unformatted list. The data will be appended to a file only after that file is searched for a duplicate. A set of alternative extensions can be used to try to find files listed with a different extension. In only a few minutes you can check every file on the Club 100 computer you have a record of: just run CHECKALL.EXE (or load and run CHECKALL.BAS under either GW-BASIC or QBASIC) and enter three items: the name of the file to receive the data, the name of the file listing the names of the files to be checked (e.g., the Library Catalog or Uploads list), and the path for the files to be checked; then press one key (the alternative extensions option) and the rest is automatic. This must be repeated for each directory holding the files to be checked and for each file listing the filenames, but these can be changed individually for a new run without having to reenter the other items. (Having everything in the same directory simplifies the entries.) Since only non-duplicate data is printed to the data file, rerunning CHECKALL will add data only for new or altered files, making them easy to find. Those downloading from Club 100 could use such a checklist to warn them of corruption during transfers (especially ASCII transfers), and to see if they already have the currently posted version. (Were there any bug fixes?) Uploaders without perfect records or perfect memories could check that the latest versions of their files are posted, and that their files are unchanged (e.g., no Club 100 phone numbers added or other corruption!). Stored files, especially those in static RAM, are subject to corruption which does not generally change the file length; CHKALL.BA provides an easy way to find corrupted text files in RAM in any Tandy or NEC notebook, and also in Booster Pak RAM and on TPDD disks and tape. It works like CHECKALL but much slower, and only checks .DO files. Both versions note the presence of high 8-bit characters, which may indicate corruption in a text file. Suggestions about other alternative extensions are welcomed: while easily added to CHECKALL.BAS, a recompilation is needed for CHECKALL.EXE. I will be happy to upload a recompiled version with requested changes. Does it not not seem a trifle extravagant for a compiler to produce a 42 KB .EXE file from a 3 KB .BAS file? Is this typical? The compiler was PowerBASIC 2.10g. Because of its size, I was reluctant to upload CHECKALL.EXE, but it runs faster and is much easier to use than CHECKALL.BAS and an interpreter. Jim