Footprints: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{{Software |Picture=NA.png |Version=v2.0 Demo |Vendor=Hardy Software Systems |Author=[[]] |License= |Download=[https://archive.org/download/monster94no1/monster.zip/monster%2F...") |
No edit summary |
||
Line 3: | Line 3: | ||
|Version=v2.0 Demo | |Version=v2.0 Demo | ||
|Vendor=Hardy Software Systems | |Vendor=Hardy Software Systems | ||
|Author= | |Author= | ||
|License= | |License=Shareware | ||
|Download=[https://archive.org/download/monster94no1/monster.zip/monster%2FOS2%2FFP2DEMO.ZIP] | |Download=[https://archive.org/download/monster94no1/monster.zip/monster%2FOS2%2FFP2DEMO.ZIP] | ||
|Website= | |Website= | ||
}} | }} | ||
Tracks I/O usage of OS/2 applications. | Tracks I/O usage of OS/2 applications. | ||
Footprints lets a developer capture real-time data and monitor a live process. Footprints consists of a DLL and a Presentation Manager executable. Developers use Footprints by including a header and linking to a DLL. The Dynamic Link Library contains four API calls used to implement tracing: initialize, terminate, trace, and check-trace. Using these C function calls, developers trace by assigning various data to any of the 64 trace IDs. Developers can also use the Check Trace feature to implement their own run-time debugging code. | |||
==Articles== | ==Articles== | ||
*[[HSS Releases Footprints v2.0]] | *[[HSS Releases Footprints v2.0]] | ||
[[Category:Shareware]] |
Revision as of 15:19, 23 May 2020
Footprints | |
---|---|
Version | v2.0 Demo |
Vendor | Hardy Software Systems |
Author | |
License | Shareware |
Download | [1] |
Website |
Tracks I/O usage of OS/2 applications.
Footprints lets a developer capture real-time data and monitor a live process. Footprints consists of a DLL and a Presentation Manager executable. Developers use Footprints by including a header and linking to a DLL. The Dynamic Link Library contains four API calls used to implement tracing: initialize, terminate, trace, and check-trace. Using these C function calls, developers trace by assigning various data to any of the 64 trace IDs. Developers can also use the Check Trace feature to implement their own run-time debugging code.