R API Monitor description
API Monitor is a software that monit

||ESoftpedia PI calls made by applications.

API Monitor is a software that monitors and displays API calls made by applications. Its a powerful tool for seeing how Windows and other applications work or tracking down problems that you have in your own applications.

API Monitor also includes useful Filters to monitor the following API Categories.

Since API Monitor is a User-Mode application, it can only monitor API's called by User-Mode applications. API's called by drivers will not be monitored. NT Services cannot be monitored using this version of API monitor

Here are some key features of "R API Monitor":

· API Filter - API's can be filtered based on their category. Only API's from the selected categories will be monitored. All other API's will be bypassed
· Process Filter - A process filter is used to select processes that are to be monitored. You can either specify an include process filter or an exclude process filter. The process filter can also be disabled, so that API Monitor will include all processes
· Detailed API Information
· Unicode and ANSI Support - Besides displaying the API called, API Monitor also displays information about the encoding used by the API. For Unicode API's the character "W" is appended to the name of the API. For ANSI API's the character "A" is appended to the API. For e.g. if an application calls the Unicode version of CreateFile, API Monitor displays CreateFileW. If the ANSI version is called instead, API Monitor displays CreateFileA.
· Message Log - When a capture is started, API Monitor displays the process name and process ID of each process it finds. It also displays information about whether the process is being monitored or not
· Error Code Lookup - API Monitor includes an Error Code lookup tool that can be used to get a description of an error, given the error code. It provides description for the following types of errors: Standard Win32 Network NTSTATUS - Windows NT Only Windows Sockets - Only English Messages
· IOCTL Decoder - A tool to decode IOCTL codes. It gives full information about the IOCTL, which includes the IOCTL Name, Device Type, Function Code, Access Type and Method. You can also try our online IOCTL Decoder.
· NT Native API: - Support for NT's Native API Calls. More calls have been added in this version. Parameter Information, Return Type and Error Codes have been included for most of the Ntxxx API's and some Rtlxxx API's. For undocumented Native API's, a stack dump of 10 (possible) arguments is displayed
· Process Loader - API Monitor includes a process loader that can be used to monitor API's called by console mode applications or to monitor API's called very early in the program. It can also be used to monitor API's in programs like RUNDLL32
· Monitor Running Process: - This version of API Monitor includes a Monitor Running Process tool that can be used to monitor API's in a background or console process that is already running. A complete list of processes that are currently running in the system is displayed, and you can select the one that you want to monitor. DO NOT try to monitor NT Services using this method as they will hang. It is highly recommended that you use till tool only when all other methods of monitoring the process fail.s
· GetProcAddress Hook - A new option has been added, where in, you can select if API's called using LoadLibrary-GetProcAddress are hooked or not.
· API Details - Double-clicking or pressing the return key on an API opens up the API Details window, which displays the details of the API in a easy to read format. It also provides a description of the error if the API call failed
· Buffer Display - For some API calls like WriteFile, ReadFile, send, RegSetValueExW, etc. buffers can be displayed using the display buffer button in API Details.
· Integrated MSDN Help - This feature allows you to view MSDN context-sensitive help for the currently selected API. You need to have MSDN library installed for this to work.
· Standard Features - API Monitor allows a capture to be saved for later viewing. If a capture is started when a capture while is open, monitored calls are appended to the file. This feature allows you to view MSDN context-sensitive help for the currently selected API. You need to have MSDN library installed for this to work.