MSAgent detailed explanation page 4/5

5. Resolve difficult errors
The key to whether MSAgent can be displayed is whether the core components of MSAgent are installed
( Microsoft Agent core components - /activex/controls/agent2/ ), but how to make this passive behavior active? The following two methods can be used:

Method 1:
Run the code box

Features: Automatically download and install components, which is more convenient, but the waiting time for download will not be prompted. When the Internet speed is slow, you will think that the page will not die, and it is not very convenient to control.
Method 1:

Features: Convenient error control, user controls download, but cannot be displayed at the time, and the page needs to be refreshed after installation.

Which method to use is a matter of opinion, but the most unwise method is to use the two methods together. Practice has proved that CodeBase will take effect before onerror!

In any case, calling a local role is much faster than a network role, but how do you predict whether the client has installed the role? Take a look at the following example:
 
By setting error capture, you can easily find the best way to call MSAgent. Of course, you can also add the corresponding role download link through DHTML and guide users to copy the *.acs file to the corresponding directory (%WINDOWS%\msagent\chars) or directly install the role installation file of *.exe to facilitate the next browsing. I am just providing you with an idea. It is better to do the specific practice yourself!