What worries me is that you are supposed to disable the full path when you are done, because it creates a security risk.

What exactly do you think is the risk? I don't think there is any.

Copied from: http://kb.mozillazine.org/About:plugins

Plugin file location:

• Mozilla 20 and below: To show the full path to the plugin instead of just the file name (e.g., in Firefox 20), type about:config in the address bar and press the Enter key. Find the preference plugin.expose_full_path and set it to true (double-clicking the preference name will toggle the setting). Caution: Exposing the plugin location may have security implications on some systems. It's best to reset the preference to the default "false" value when you are done. 1
• Mozilla 21: There is no way to display the full file path in the about:plugins list. An alternate way to find the plugin file location (e.g., in Firefox 21) is to inspect the contents of the "pluginreg.dat" file, located in the profile folder for your Mozilla application.
• Mozilla 22 and above: Starting in version 22 (e.g., Firefox 22) an extra row "Path:" is included in the about:plugins list, which displays the full file path for all plugins. (bug 661961).

It is no longer required to toggle the plugin.expose_full_path to true to be able to see the installation path of plugins on the about:plugins page, so leave that pref set to false or reset a possible present plugin.expose_full_path pref via the right-click context menu. You should always see the full path on the about:plugins page regardless of the value of the pref. Web pages can't see the path via the navigator.plugins array unless you expose this via the pref (?).

Thanks for the info!

Thanks for the answe Cor-el....that explains it. Sorry I could only vote for one solution. Yours was excellent too.