Click above to get retro games delivered to your door ever month!

 Microsoft profiler
------------------------------------------------------------------------------
 The Microsoft profiler does not currently support overlaid programs, but
 non-overlaid .EXE files created with Blinker with CodeView information are
 fully compatible with the Microsoft profiler.
 Create the non-overlaid .EXE file for use with CodeView, as described in the
 section above, and then use it with the profiler in the same way as if it
 had been linked with Microsoft LINK.
 For example, to profile the TEST program created above and record the number
 of times each procedure was called, use the FCOUNT batch file provided with
 the Microsoft profiler :

 FCOUNT TEST

 The output from the profiler will be in the file TEST.OUT, which can be
 edited using any ASCII text editor.
 Selective profiling can be performed by using the CVON and CVOFF commands to
 only include CodeView information for the files to be profiled, as in the
 second CodeView example above.

 Turbo profiler

 In the same way as the Turbo Debugger can be used with .EXE files created by
 Blinker with CodeView information and converted with TDCONVRT, so can the
 Turbo Profiler.
 Simply prepare the .EXE file as described for the Turbo Debugger in the
 section above, and then load up the .EXE under the profiler.
 Please refer to the Turbo Profiler documentation for further details of how
 to use it to profile a program.