Phoenix CD 2.0/Phoenix_CD.cdr/15a/ft_130.zip/UPDATE.DOC

Text File | 1987-12-12 | 13KB | 269 lines

Last Minute Notes:
     12/12/87
     FILETYPE Version 1.30A

Dear Users:(Boys and Girls)

        Read and Follow the installation procedure!

           A>mode bw80  (or any other equivalent program)
           A>ft or followed with valid switches listed in section 7 of guide

      Applied the above to run FileType in the correct way, of course
      you may just type in FileType and the program will run properly.
          Users are suggested to use DOS 3.x for the current FileType.

    User may rename FILETYPE to an easy accessing name such as FT130.EXE
    or FT.EXE is more desirable or even access thru a batch process.

    User may also copy the file to be test to a ram disk to ensure maximum
        speed.  I agree with all huge files.


Update for the rest of 1987, Release 1.30A

 1. This release has a charge of number by 9 to signify important updates

 2. Update for Lahey Fortran77 Compilers with LP77(Lahey Personal Fortran77)

 3. Marshal System Pascal Compiler added to the compiler list no longer
    display "Compiled by an unknown Pascal Compiler"

 4. Experimental PASCAL-2 manipulation installed

 5. Experimental RM-COBOL manipulation implemented

 6. All data type manipulation updated

 7. Mark William's Let's C will be added soon when I have more time and
    figure out what the hell is going on.

 8. a. This release requires 206K of memory and runs under real IBMs and real
       IBM compatibles

    b. Serious PC users have at least 640K of RAM on their system

 9. Completes the Turbo Pascal 4.0's manipulation

10. This release is specially designed if a fatal error occurs please
    call our boards and leave a message, thanks.  Also the Function list
    section maybe a little slower than before this is because a new method
    is used to make FT use as less memory as possible if this method is
    not applied users may be required to have 256K to run FILETYPE.

11. Turbo C manipulation updated

12. There are 3 versions of FILETYPE have been released seperately

    a. FILETYPE
    b. Advanced FILETYPE
    c. FILETYPE Plus

13. Watch out for fake FileTypes they maybe hazardous for your computer's
    health.  To check if you have a valid version use FileType on FileType
    a prevention message will happen then you have the right one. To make
    sure please use other releases of FT that you have to test the current
    version to see if you truly have the real copy.

14. At last I've decided to fix the typo errors, such as 80827 should be
    80287 all have been corrected.


Updates from 11/26/87 to 12/2/87. Release 1.21

1. Updated new Clipper, DBase produced data files

2. Correction for Borland International's Turbo Pascal 4.0 detections

3. Requires 205K of memory

Updated from 10/27/87 to 11/25/87. Release 1.20

The changes are as follows:

A. A beep & warning will alert user at entry or re-entry of FILETYPE
   if a non-IBM PC/PCXT/PCAT Compatible BIOS has been detected, this
   may not be valid for PS/2.

B. A non-IBMPC Compatible BIOS may cause NULL errors for FILETYPE
   subroutines.     Best effort have been used to correct computer
   incompatibilities but if problems still persist please notify me
   with your specific system name, etc.
   (NEC V20 Chip is a potential problem causer)

C. Determine if you have a very packed, or rather packed file.

D. Update for Lattice C and Microsoft C detections

E. PLINK86 tests updated.

F. Update Clipper with version seperations since many updates are released
   1. The new Clipper Compiler(Autumn 86, Summer 87)  now produces a 99%
      exact code to a Lattice C 3.0 or higher produced code, the older
      Clippers would produce similar executable codes to Lattice 2.x.

   2. If you are using FileType version 1.19B and earlier a result
      of "Origin C, Compiled by Lattice C Compiler 3.00", "Compiled by
      a Large/Big module" will occur when running with CLIPPER Compiler.
      Release 1.20 now adjusted to the new Clipper trickry, how fun!!!!

   3. Clipper is a way to emulate Lattice C Compiler and use as one's own,
      maybe I should try it one of these days.

G. New detections for just released softwares(RapidFile, FoxBase+ 2.0, etc.)

H. First Publisher and ClickART are the same program just making a note here.

I. During the last few earth quakes caused the modules stored in FILETYPE.LIB
   to be impaired, some informations are lost therefore releases since 1.18B,
   1.19 and 1.19A may be compiled with empty variables and may not supply all
   the necessary informations are needed for analysis(With or without FT can
   handle any file perfectly well).  The new FileType 1.19B and 1.20 possess
   the corrected informations and with many revised tracing methods.

J. Please don't hack FILETYPE, even if you change a little bit of the data
   all structure will be altered.  A hacked version will result FILETYPE as
   void where prohibited.

K. FILETYPE Release 1.2.0 requires IBM/PC/XT/AT or Compatible with 204K of RAM

Special Thanks to the recent contributors

    1. Thanks to the sysop at Wellspring for discovering what was
       causing the null error.
     2. Thanks to Jorge my good friend who supplies me files for
       testing.
    3. Thanks to Scott Lawson's new files on his board that made the
       new FT120.LST available with new entries.
    4. And all the authors who made great programs for me to
       test on.

           For additional informations consult me or the User Manual.

Several minor things you should know about this version:

        1) There are still some parameters and features deviate from the
           FILETYPE standard.  These will be fixed shortly.
    2) Users who holds FILETYPE Plus may recompile the new source yourself.
        3) Recently there are alot of AMIGA, MAC programs flowing around IBM
       BBS probably for people who has a conversion board and other users
       may download them and don't know what the hell is going on.  I've
       especially made FILETYPE to pick up some of the MAC and AMIGA type
          files.
        4) As many of you would like to see FILETYPE run faster.  Therefore
           I've installed the /Express switch, which is 4 times and faster
       than the regular speed.  But with the constant changes in FT there
       are features like a tripwire keep getting in the way and cause null
       errors, and another major error is data collision which is un-
       mentionable this would cause FT less reputative.  /E is used just
       to see the quick results and I should never have told you about
       this option.  I don't recommand users to use /E switch and take the
           answer for absolute accuracy.
        5) If FILETYPE does tell you a wrong answer for you're program's
       Origin please write me what it should be and with a copy of the
       program you've tested by FT.  Thanks in advance.
    6) FILETYPE just went over the 64K data limit it is getting very
           unpredictable.  Many features just disappeared without a trace,
           although this has been corrected some bugs may still exist without
       knowing.
        7) As many of you have wondered what FILETYPE was written in and maybe
           tried FILETYPE on FILETYPE as your first common sense.  What a
           suprise you can't do that!!!  Leave me a mail if interested.
    8) There maybe results given by FT that user may not understand or
           comprehend please ignore them(Designed for me only).
        9) Some informations concerning a program may be stored in another
           program's format.  Such as PageMaker its data files are saved in
           Microsoft Window System Paint format and it will just be consider
           as MSW Paint by FILETYPE.  Also take FoxBASE as another example, it
           is a DBASE type clone program it will produce a DBASE III or
           DBASE III Plus formatted data file, this will not be consider as
           a FoxBASE produced data file but instead as DBASE III. After these
           two sensiable examples you should know what to expect.
       10) FILETYPE has become a utility not only trace a compiler but it
           also determine data type of most popular programs
       11) Do not try to modify FILETYPE in anyway, this include COMPRESSING
       from EXE to COM process or any size reducing utility or else FT
       will suffer data collision and return incorrect solution.
       12) You should understand that I am not responsible for any damage
           caused by your incompetence.
       13) If in some case you find a feature that's not listed don't publish
           it, lets just keep it between you and me.
       14) The General informations are relative, the XMODEM transfer rates
       are with 99% accuracy.
       15) Please tell me what's not appealing and I'll make improvements.
       16) Please note that everything that you input at DOS command line
       will be converted to UPPER case letters.  When use FT /f file =msg
           at DOS is same as FT /f file =MSG at the input prompt.  If you use
       /F and obtain an "File not found" error please do it in this format,
       Enter Source[filename.ext]:  /f filename
           Search what string?MSG
       .....
       17) If you find the FILETYPE you are using constantly display an error
           encountered message then you've downloaded a bad copy, etc.
       Use PKXARC /t FT118.ARC to test the integrity of FILETYPE Package
       if an 'ok' message displays then FILETYPE is in an usable condition.
       18) Don't use any SPEED SCREEN Utilities it might cause FILETYPE
           have Screen Collision.
       19) Few internal bugs have been detected in the Microsoft Compilers I
       used to compile FILETYPE which have lead to a few features go weird,
       and many fine detections doesn't work.  If you happen to bump into
        one please write to me.  Thanks in advance.
       20) The old Microsoft C Compiled programs looked almost exactly like
       the currently Lattice C Compiled programs maybe one of them once
       were a child of the other one????
       21) This version of FT is compiled under IBM PCDOS 3.3 may cause
       problems for DOS version other than 3.x

    I am looking for comments on improving the manual and my FILETYPE.
For instance, you may have specific FILETYPE features that you wish I'd
implemented today.

        If you have ideas on FILETYPE.  Please contribute to the OCIPUG RBBS
        @[phone], 300/1200/2400 bauds.  7 days a week, 24 hours or
    Call [phone] with n,8,1 at 20 Hours a day, 7 days a week.
       12:00am to 5am will be offline for maintenance. Pacific Standard Time.
    If these 2 boards are busy or long distance for you, you may write to
    me at PaoHsin Pi
          2039 CHARLE
          COSTA MESA, CA 92627

    VOICE:[phone]. DATA:Will be posted in FILETYPE.EXE

If you want reading material on FILETYPE there are the followings available:

                FileType 1.18 Complete User Reference Documentation
        FileType 1.14N Advanced Info Guide
        FileType 1.13A User Manual Guide
                FileType 1.08A User Guide
                FileType 1.06B User Manual
                FileType 1.00 Basic Operation Guide & Introduction
                FileType Plus User Document

The FILETYPE documents listed above each contains unique and major updated
informations and they would be very interesting to read through and see the
changes. Also you may find info not included in the current issue of FILETYPE.

    Thanks to important friends:

        1) Jorge Schulz who allowed me to perform tests on all of his
               softwares also been such a goober and a good friend.
        2) And many other friends who called me and gave me their opinions.


    Future feature Plans:

        In the near future I plan on moving the 8088 version of FILETYPE
    to a fully implemented Utility.  I am also planning a large set of new
        features such as FileType COMPARE, EXEVIEW or a COMMAND script file
    that allows user to input a series of FT commands and FT will execute
    them at once; In a way this will reduce the keyboard I/O and automate
    inputs known as keep your computer busy while you're away.  Speed will
    be stressed in the later releases.  And I'll try my best to make
    FILETYPE a user friendly utility.  Suggestions are always welcome.

    I would like to hear from all of you, so write me your suggestions.

                        Sincerely yours,

                        PaoHsin Pi, 1987