home *** CD-ROM | disk | FTP | other *** search
- Program: LineFix Package
- CHR10.EXE v1.1
- CHR13.EXE v1.1
- Version: This is version 2.1 of the package
- Author: George Spafford
- Date: February 15, 1992
-
- Purpose:
-
- To quickly repair CR/LF line delimitters. Often times, mainframes,
- or what have you, will leave out either the ASCII 10 or ASCII 13 at the
- end of a line. This wreaks havoc with many importation programs.
- This set of programs will insert the necessary character.
-
- Procedure:
-
- There are two files to this package:
-
- CHR10.EXE Repairs missing ASCII 13 characters.
- (This assumes that the ASCII 10 is currently present
- in the source file.)
-
- CHR13.EXE Repairs missing ASCII 10 characters.
- (This assumes that the ASCII 13 is currently present
- in the source file.)
-
- The usage for both programs is:
-
- CHR10 source target
- CHR13 source target
-
- Source This is your master file.
- Target This is the file to be created.
-
- Do NOT give source and target the same name.
-
- NOTE: THERE ARE NO SCREEN WRITES WHILE THE PROGRAMS ARE ACTIVE.
- In other words, be patient. On my 33Mhz 386 with a 2Mb
- cache, a 1 megabyte file takes 35 seconds to repair.
-
- Both programs assume that the given character will be missing throughout the
- file. They will not discern between a correctly delimitted line and an
- incorrectly delimitted line. I.E. half your file is missing ASCII 10 and half
- is not, then half your target file will have duplicated ASCII 10 codes.
-
- If the data file was "streamed" to the file with no delimitter at all
- between records, you should use CUTIT to parse the records into
- specifed lengths. When CUTIT runs, it will automatically create the correct
- line delimitters (ASCII 13 followed by ASCII 10).
-
- Fine you say, but George, what are these two codes you are babbling about?
- ASCII 10 (hex 0x0A) and ASCII 13 (hex 0x0D) form the end of a line in a DOS
- text file. If 10 is missing, the file may appear to be correct when you view
- it with Vern Buerg's LIST or another viewer, but when you look at it in hex,
- using LIST's ALT-H command or a diskeditor, you can see that there is only one
- of the two codes. If you look at this file right now, look for "0D 0A" in hex
- or look for what appears to be a music note followed by a solid square with a
- hole in it.
-
- Some programs will let you slide if you are missing one of two codes, some will
- not. When in doubt, look at your source file using some form of editor or
- viewer that will allow you to see the source file in hex (Hexadecimal).
-
- History:
-
- v2.1 February 15, 1992
-
- Ooooops. The bug that caused incomplete file transfers has been
- corrected. These programs are now compiled with Borland's C++ 3.0
- optimizing compiler it is a really sweet language product to say the
- least.
-
- v2.0 December 2, 1991
-
- The programs are now coded in Borland C++ and are an order of magnitude
- faster than v1.0's QB based code.
- All filenames are now specified at the command line in order to
- facilitate batch processing.
-
- v1.0 May 10, 1991
-
- Initial release. Program coded in QB 4.5.
- What can I say - it met the needs at the time, but toooooo slow.
-
- I hope this program helps you evaluate some of your problems
- or even makes some solutions/benefits clear.
-
- This program is shareware. It is not Freeware or public domain. This
- product costs $5 for each concurrently used copy. Please register this
- software if you find it useful. If you have any suggestions, I'd REALLY like
- to hear those too.
-
- Sincerely,
-
- George Spafford
- 3001 LakeShore Drive, #329
- St. Joseph, MI 49085
-
- Data: (616) 468-5026 Queued Access BBS 19200-8-N-1
- FIDO: 1:2340/0 NEC/NC site: Tim Akright - Sysop.
-
-
- And now for the unpleasantries:
-
- THE LINEFIX PACKAGE IS DISTRIBUTED AS IS. THE AUTHOR (GEORGE
- SPAFFORD) MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR
- IMPLIED, INCLUDING BUT NOT LIMITED TO TO WARRANTIES OF
- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, WITH
- RESPECT TO THIS SOFTWARE AND DOCUMENTATION. IN NO EVENT SHALL
- THE AUTHOR BE LIABLE FOR ANY DAMAGES, INCLUDING LOST PROFITS,
- LOST SAVINGS, OR ANY OTHER INCIDENTAL OR CONSEQUENTIAL
- DAMAGES ARISING OUT OF THE USE OF OR THE INABILITY TO USE
- THIS PACKAGE OF PROGRAMS.
- ---------------------------------------------------------------------------
-