If you transfer code back and forth from one machine to another, you
  know how much work it is to keep all of the scripts working on both
  machines. The problem begins when the two machines that have files in
  different locations. For instance, if your compiler and .LIB directory
  is on C: on one machine and on D: on another machine, then any fully
  developed .MAK model would stop working as you transferred the code
  from one machine to the next.

  PBInit has relieved you of this problem by 'refreshing' the .MAK files
  from the environment of whichever machine you are on.

  Simply run PBInit <existingmakfile>, and you will be prompted three
  ways:

  1. Abort, I didn't mean to do this.
  2. Refresh, I just want to update the references in my .MAK file.
  3. Delete this .MAK file and create a new one from scratch.

  Pick #2, Refresh, and PBInit will:

  1. Locate all of the LIB= and INCLUDE= lines in the existing .MAK file
  2. Strip the path off of them
  3. Use the current environment to find the files that were referred to
  4. Find the correct path to each reference
  5. Replace them back into the .MAK file with the corrected path
     information for the current environment.

  If PBInit can't find a referred to file in the current environment, a
  comment will be placed in the .MAK file where the file was originally
  referred to stating that the reference couldn't be found, like:

  // LIB=SOMELIB not found in local directory or LIB= environment

  or

  // INCLUDE=SOME_CH not found in local directory or INCLUDE= environment

  After correcting the environment, you can run the PBInit refresh
  option again and PBInit will look up the full path and correct the
  .MAK file.