Since the original post about launching active content, which appeared nearly a year ago, I've changed the way I do it. So it's time to share the improved approach.
The latest Flash-Fix script works great and has been updated only for readability, but the original Net-Share script had at least three problems:
- the script fails if there is no network
- the script fails if network sharing is disabled (eg- in secure enterprises)
- the script tends to run very slowly if a virus scanner is enabled
I have since come up with a replacement called the IE-Fix script, and it directly updates the user's registry to allow active content to be launched from removable media and the current working directory. This works like a champ in most instances, and directly overrides the default settings of the IE browser, rather than trying to trick the browser into thinking that the content is running from a network device. It does not slow the presentation down in any way, and fails gracefully. So use IE-Fix instead of Net-Share workaround.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgzpHDQ7DM0EPP4Nx1iN_GWKrpLf6gWkR8K2lQT7LYsdNcaf_vBwyot0lfPEHXwS-i8sz3yuJngW7zNaXS4kZLmtnyqOIkBUDK6UotbumrTcV9Oso9e5SRY97lSf0L6K3n4-W351A/s320/active_content_v2_sm.gif)
I also launch the Flash-Fix and IE-Fix scripts from a script named autorun.bat located in the root directory of the removable media. This simplifies testing.
Hope this updated information is helpful.