July 29, 2003

Defining new Script Engines on Windows

Matt Heyse very kindly posted a long comment explaining how to get round the problems about Running JavaScript Batch Files on Windows I posted on before. It turns out that you need to define a new "script engine" and link it to the file extension you are interested in. Other people want to do other variations too, as Matt describes:

Why do all this.... Well we use VBscripting in our new Active Directory Domain.
But to stop the thousands .vbs viruses we had made the HLCR\.vbs(default)="NORUN". This stops all .vbs programs (we didn't have any). But with the new need for .vbs scripts we had to reactivate it, and thus allow in viruses too. Instead we made up an extension as described above, and kept .vbs broken.
All of our vbs scripts have the new extension and work great, and .vbs virus still can't execute.

Thanks for the info Matt.

Entry categories: Microsoft Programming
Posted by Jorgen Thelin at July 29, 2003 03:03 PM - [PermaLink]
Traceback List