home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Bila Vrana
/
BILA_VRANA.iso
/
007A
/
GFXCK121.ZIP
/
GFXCHK.DOC
< prev
next >
Wrap
Text File
|
1996-01-30
|
25KB
|
540 lines
┌──────────────────────────────────────────┐
│ G F X C h e c k │
│ GIF/JPEG/BMP Graphics Checking Utility │
└──────────────────────────────────────────┘
Version 1.21
(c) Copyright 1995-1996 - Stacy Smith
Courtesy of:
The Bloom Beacon-Picayune BBS
Node 1: *** DOWN *** (USRobotics Courier Dual Standard V.34)
FidoNet
ILink
Intelec
Stacy Smith
┌────────────────────┐
│ 1. Introduction: │
└────────────────────┘
GFXCheck was developed to provide the cyberspace community with a means of
validating GIF, JPEG and BMP graphics files without the need for actually
firing up a graphics file viewer. While there are similar utilities available
for GIF files, they are generally dated, run only under DOS and do nothing to
validate JPEG (currently the leading graphics file format technology) or BMP
files.
GFXCheck was designed to address these specific issues. While GFXCheck
obviously cannot determine the subjective quality of an image, it can detect
many common defects and corruption that can occur in graphic files being
transferred by a variety of media.
┌────────────────────────────┐
│ 2. Features of GFXCheck: │
└────────────────────────────┘
∙ Native versions for both 16-bit DOS and 32-bit OS/2!
∙ Automatically identifies (by signature) GIF87a and GIF89a GIF files, JFIF
1.x format JPEG files, and Windows, OS/2 1.x and OS/2 2.x format BMP
files.
∙ Validates graphics files for proper format and construction (e.g. invalid
structure, unexpected end of file, etc.).
∙ Trims any extraneous bytes from the end of the graphic file.
∙ Rejection of graphics files based upon image parameters (e.g. width,
height and/or number of colors). These can be set individually for GIF,
JPEG and BMP graphic formats.
∙ Logging of existing GIF and JPEG comments.
∙ User-defined stripping and/or insertion of GIF and JPEG comments.
∙ User-defined disposition of defective or rejected graphic files.
∙ Updates BBS file descriptions (PCBoard-format or similar) with a user-
configurable information string.
∙ User-selectable process logging to a disk file.
∙ Written completely in C for optimal speed, using Watcom C/C++ 10.0.
┌──────────────────────────────────────────────────────────┐
│ 3. Files Included in the GFXCheck Distribution Archive │
└──────────────────────────────────────────────────────────┘
GFXCHK.EXE GFXCheck file checker program (16-bit DOS).
GFXCHK2.EXE GFXCheck file checker program (32-bit OS/2).
GFXCHK.DOC This file.
SAMPLE.CFG Sample configuration file.
GIF.TPL Sample GIF comment template.
JPEG.TPL Sample JPEG comment template.
SUPPORT.DOC List of authorized support sites for my shareware.
HISTORY.DOC GFXCheck revision history in reverse order.
REGISTER.FRM Registration form for GFXCheck and other software.
FILE_ID.DIZ Internal description file.
When you unzip the distribution archive, you should see my PKZIP authenticity
verification stamp, and a '-AV' after every file in the archive:
# SSU301 The Bloom Beacon-Picayune BBS
If there are any files missing or added, or the -AV stamp is missing, the
archive has been tampered with. It would be advisable to call my BBS (listed
at the top of this document) or one of the support sites listed in the
SUPPORT.DOC file for the latest version of GFXCheck.
┌───────────────────────────┐
│ 4. Program Requirements │
└───────────────────────────┘
To the best of my knowledge, this program will run on most any machine, as it
uses no specific hardware or operating system features. I have personally
tested GFXCheck under OS/2 Warp 3.0, DOS 6.20, DESQview and Windows for
Workgroups 3.11, although I don't expect problems under other configurations
given they conform to the general requirements of GFXCheck.
GFXCheck requires DOS 3.x and higher (or OS/2 2.0 and higher for GFXCheck/2),
as it uses DOS SHARE-compatible file reads and writes. GFXCheck's memory
requirements are very small (less than 100K) and should run merrily under most
any upload or file processing software, in many cases without any need for
swapping.
┌───────────────────┐
│ 5. Registration │
└───────────────────┘
GFXCheck is not free; nor is GFXCheck crippled to force registration. GFXCheck
is fully functional, and will always remain so. The only variation with the
registered copies is no time delay and beg message.
Why register? Besides a clean conscience, you will get a registration key
that will work for all future versions of GFXCheck, and will remove the delay
and beg message at the end of execution.
The registration fee for your unique key is $20 for hobbyist use. The
registration fee for commercial use, defined if you use GFXCheck in the course
of a commercial business or for profit (e.g. CD-ROM production, more than 10
BBS nodes, etc.), is $30. Refer to the file REGISTER.FRM for more registration
information. Please print the file REGISTER.FRM and fill it out. You can
print out the form by issuing the following command from the DOS prompt:
TYPE REGISTER.FRM > PRN
┌───────────────────────────────────────┐
│ 6. License, Warranty and Disclaimer │
└───────────────────────────────────────┘
I'll keep this part short and sweet, and dispense with the legal-ese:
License: You are allowed to use GFXCheck for 30 days, after which you must
either register GFXCheck or stop using it completely. Decompiling,
disassembly or any other form of reverse-engineering GFXCheck for any
purpose is prohibited. GFXCheck registration is a license for your use
of GFXCheck; I retain ownership of the software. A single registration
applies to a single enterprise (e.g. BBS, CD-ROM mastering company)
regardless of the number of computers used. If you run two or more
distinct BBS systems on the same computer (with different names), you
require two or more GFXCheck registrations. GFXCheck registrations are
not transferrable; you cannot sell your registration to another person.
Warranty: There isn't one. The only thing I'll guarantee is that GFXCheck
will take up disk space, and will disappear when deleted.
Disclaimer: I'm not responsible for anything bad that happens. GFXCheck
works for me, but I cannot be held responsible for it not working on
your computer or doing any damage to hardware or software.
If these conditions aren't agreeable with you, then the best thing to do is
delete GFXCheck right now. I'll do my best to help any user (registered or
not) that wants to use GFXCheck, and I'll act on bug reports quickly, but I
simply cannot and will not be responsible for anything bad, like lost data,
disk crashes, or whatever else you can think of.
┌───────────────────┐
│ 7. Installation │
└───────────────────┘
GENERAL INSTALLATION:
─────────────────────
Make a subdirectory on your hard drive. For the purposes of this document,
we'll call it "D:\GFXCHK". Unarchive the GFXCheck distribution archive into
this subdirectory. You've more than likely already made it this far, if you're
reading this file. <grin>
The GFXCheck program opens a few files at once for various reasons. I would
recommend that you have a minimum of FILES=30 per node in your system
CONFIG.SYS file for a DOS single-node system, since GFXCheck is often run in
conjunction with your BBS and upload or file processing software.
If you are running under a DOS network or a multitasking operating system, you
should already have DOS's SHARE.EXE loaded