3.7.4. Guidelines

This information provides the following guidelines for using DM3Insight:

• Troubleshooting
• Limiting Memory/CPU Usage

Troubleshooting

If things don't work:

• Make sure that DM3InsightDrv.sys is copied in the \WinNT\system32\drivers directory.
• Enable printing of error messages by running DM3Insight with -t parameters to get more detailed error messages.
• To capture traffic during the download process, select All boards instead of a specific board as the logical board ID may not be assigned.
• If there is no trace output in DebugView, make sure that Capture Kernel and Capture Events are selected in the Capture menu of DebugView.
• When using DM3Insight in remote mode, make sure that you can ping the host system. Make sure that the TCP/UDP port used by DM3Insight is not used by any other application using the netstat application.
• Always run the DM3Insight server on the host system before running the remote DM3Insight client.

Limiting Memory/CPU Usage

DebugView allocates memory to save the output from DM3Insight. If the amount of traffic is large, it is advisable to limit the history depth (number of lines buffered) and select the Log to File option.

If CPU usage is too high, consider limiting the queues or events. Minimizing the DebugView window or capturing traffic on remote system also reduces CPU usage.

Click here to contact Dialogic Customer Engineering