I’ve finished another minor upgrade to Script Sentry. This version fixes some bugs that would corrupt the Safe Files list. (If your Safe Files list is already corrupted — if you get errors after adding, removing, or updating Safe File entries — you’ll have to delete your old ScriptSentry.dat.) The other squashed bug was a 32K limit on Safe Files. (Turns out I was using an ‘Integer’ typed variable with a 32,000 limit. Now I’m using a ‘Long’ typed variable with a 2.1GB limit…. So no files over 2.1GB please. ) The new version is 2.1.5 and you can download it from http://www.jasons-toolbox.com/scriptsentry.asp. As always, simply install the new version over your old version. No need to uninstall before updating.

I’ve been working to squash some bugs that I (and others) found within Script Sentry and Cookie Jar. Nothing show-stopping, but some annoying little bugs. I was wondering if I should hold off releasing the new versions until all the bugs were squashed or do a series of minor releases as I get each bug. In the end, I decided not to hold off on bug fixes that might solve problems that people might be having. So expect to hear of some minor-version upgrades to Script Sentry and Cookie Jar over the next few days. If the upgrade doesn’t address a bug you encountered, there’s no real need to upgrade (unless you really want to).



The first minor-release is Script Sentry v2.1.2. This fixes an error that would pop up if you checked a script on a network path. (Along the lines of \\computer_name\folder\file.) It also updates the Check For Updates URL and the contact e-mail address.