Valkyrie 2.0 README File
========================

      Welcome to Valkyrie 2.0! Please read this file for new
      information on v2.0 which hasn't made it into the manuals yet.


Disk Contents
=============
      Your Valkyrie diskette should contain the following files:

      README.TXT     - The file you are now reading
      VPP.EXE        - The Valkyrie Preprocessor
      V.EXE          - The Valkyrie Recovery Engine
      VAU.EXE        - The Valkyrie Analysis Utility
      UNPAK.EXE      - EXEPACK Unpacker (for Microsoft-linked files)


Quick Start
===========
      If you're anxious to get going, here are the quick instructions
      for running Valkyrie.  Assuming your application is named
      MENU.EXE:

   0) Copy the Valkyrie diskette to your hard disk.

   1) Run the Valkyrie Preprocessor:

         C>VPP MENU

   2) Run the Valkyrie Recovery Engine:

         C>V MENU

      V will ask for your serial number. Type it in from the inside
      cover of your manual, and then sit back and watch it work.

   3) Your source code will be in MENU.SRC. There may be other .SRC      
      files as well.  They are named "SRC" in order to avoid
      accidentally overwriting any existing program files you may have
      on your disk.


Enhanced Linker Support
=======================
      VPP 2.0 now supports Blinker 2.01 (and all earlier versions),
      Warplink 2.0, and .RTLink/Plus.

      New versions of the various overlay linkers are appearing all
      the time. If VPP cannot process your Clipper EXE, contact us
      right away. We can usually provide an updated version of VPP
      within 48 hours.


Turning Off Visual Decompilation
================================
      The Valkyrie Recovery Engine (V.EXE) now has a visual display as
      it runs. You can turn off the display with the Console Mode
      switch (-c), which causes V to print simpler messages to your
      screen as it runs. You can disable all screen output with the
      Quiet Mode switch (-q). Run V with no command line arguments to
      see a complete list of available switches.


Splitting Out Your Source Code
==============================
      The Valkyrie Preprocessor (VPP) produces an ASCII .MOD file when
      run on your Clipper EXE file. The .MOD file is used by the
      Recovery Engine (V.EXE) to determine how to break out the source
      code in your application.  You can edit this file with a text
      editor to customize how your source code is written to disk.

      The basic format of the .MOD file is:

         # COMMENT(S)

         SOURCE MODULE1
            PROC PROC1
            PROC PROC2

         SOURCE MODULE2
            PROC PROC3
            PROC PROC4

         etc.

      There are two types of statements in the .MOD file, SOURCE and
      PROC. Lines starting with a pound sign ('#') are comments, and
      blank lines are ignored.

      The recovery engine (V.EXE) creates a source file for each
      SOURCE statement, using the name given. The PROC statements
      following the SOURCE statement name the procedures to be placed
      into that source file. You can add, change, or delete any SOURCE
      statements in order to place procedures exactly where you want
      them.

      For example, assume you have a Clipper S87 file named
      MAILLIST.EXE. You run VPP on it, and it produces the files
      MAILLIST.RIP and MAILLIST.MOD. The .MOD file might look
      something like this:

         SOURCE MAILLIST
            PROC MAILLIST
            PROC STARTUP
            PROC MAINMENU
            PROC SHUTDOWN
            PROC REPORTS
            PROC REPT1
            PROC REPT2
            PROC REPT3
         SOURCE VIDEO
            PROC VIDEO
            PROC VINIT
            PROC VMODE

      This .MOD file will cause V.EXE to create two source files,
      MAILLIST.SRC and VIDEO.SRC. MAILLIST.SRC will contain the
      procedures MAILLIST through REPT3. VIDEO.SRC will contain the
      VIDEO, VINIT, and VMODE functions.  Notice that the MAILLIST
      procedure is still listed under the SOURCE MAILLIST statement. 
      All procedures to be decompiled must be named in the .MOD file
      with PROC statements. You could also delete PROC statements if
      you didn't want particular functions to be decompiled. You
      cannot, however, change the PROC names.

      Now suppose that you want the report functions to be placed into
      their own source file. You simply add a SOURCE REPORTS statement
      to the .MOD file before running V.EXE. Also, suppose you want
      the video functions placed into a file named VLIB.SRC.  The
      edited MAILLIST.MOD file should look like this:

         SOURCE MAILLIST
            PROC MAILLIST
            PROC STARTUP
            PROC MAINMENU
            PROC SHUTDOWN
         SOURCE REPORTS             <== added
            PROC REPORTS
            PROC REPT1
            PROC REPT2
            PROC REPT3
         SOURCE VLIB                <== changed
            PROC VIDEO
            PROC VINIT
            PROC VMODE

      Again, notice that the PROC REPORTS statement is still listed,
      we've only changed the source file into which it is placed by
      adding a new SOURCE statement. The SOURCE VIDEO statement has
      been changed to SOURCE VLIB, which causes VLIB.SRC to be
      created, and it will contain the source code for VIDEO, VINIT,
      and VMODE.

      Following the SOURCE and PROC statements is a comment section
      which names all of the non-Clipper (external) functions found in
      your EXE file. These cannot be decompiled by Valkyrie, although
      you can use this list to help determine what libraries may have
      been used in creating the application.


Valkyrie Analysis Utility
=========================
      Your disk also contains the Valkyrie Analysis Utility, VAU.EXE.
      This program may be used to determine what version of Clipper
      was used to create an .EXE file. It will also attempt to
      identify the linker which was used to create the file. Complete
      instructions are in the user manual.


Renamed Executable Files and Missing Overlay Files
==================================================
      If your executable uses overlays and has been renamed from the
      original name it had when linked, VPP may report that it cannot
      find an overlay file. The message will list an .EXE file name as
      the missing "overlay". This is the name the program had when it
      was originally linked. Some overlay linkers record the original
      name of the application in the EXE file, and this is what VPP is
      reporting.  VPP may also give many warnings about missing
      symbols.

      Simply copy (or rename) the EXE file to the original name and
      then run VPP again. It will now process the file correctly, with
      no warnings.

      For example, the original program was named FPMENU0.EXE, but
      when installed, the programmer renamed it MENU.EXE.  VPP will
      report that FPMENU0.EXE is a missing overlay file.  Copy or
      rename MENU.EXE to FPMENU0.EXE and then run VPP again.


Blinker temporary files
=======================
      In order to process some applications linked with Blinker 1.x,
      VPP may have to copy the executable code to a temporary file.
      This file will have an .OVV extension. After your source code is
      recovered with V.EXE, you may delete this temporary file from
      your hard disk.

      For instance, if your Blinker-linked application is named
      MENU.EXE, the command

         C>VPP MENU

      will produce both MENU.RIP and MENU.OVV. Recover the code with
      the command:

         C>V MENU

      You may now delete both MENU.RIP and MENU.OVV.  Your source code   
      will be in MENU.SRC (and any other .SRC files created by V).
