Category Archives: Systems Admin

First Step: Source Control

So I decided that I may as well make this project open source and take advantage of CodePlex gives you a simplified and free “Visual Studio Team System” to connect to.

I created a new project @

Interesting Tidbit: Batch Files in Windows 2003

I am not sure if this is just a new thing in Windows 2003, or it’s been this way for all time, but if you edit a batch file while it is executing, then you will change the behaviour of the script in real time. It seems that dos keeps a pointer to the last character it executed, and then when the current command it is executing returns, it resumes from (approximately) that character. Meaning if add a line or two this pointer will no longer be valid, causing unknown behaviour.

I was always under the impression that dos read in the whole batch file into memory, then ran it allowing you to edit the file in the meantime. The things you learn when you break a system, err, umm, are playing with dos batch files.

If you are bored, and have a lot of hard drive space, try this example (save as a.bat):

@echo off
type a.bat >> a.bat

(Make sure you have a trailing return character). For more fun, remove the pause and watch your free space shrink.

Symantec virus definitions slow websites with javascript significantly

The Skinny:

Anyone who has ever had to develop on a machine with a virus scanner than has “real time protection” knows the pain that it can cause. Have you ever had issues in Visual Studio where files are locked and don’t become unlocked till you restart your environment / iis / your machine? Well, in the majority of cases, it’s thanks to Symantec getting it’s grubby hands all over it.

Now Symantec are making things awkward from the other side – as a valentines day gift, Symantec have decided that they will now try to scan the content of javascript in an html document, with a badly implemented heuristic. This means that if anyone vists your website with Symantec installed, if you have a large chunk of javsacript it will pause for up to a minute while it tries to work out what the javascript is doing! This means a large portion of your client base could be seeing minute long delays as they are using your site.

Slightly more details:

It seems the key is the new statement. If your code has a lot (thousands) of new statements in a single block (e.g. pre loading rollover images / using your own custom objects to preload an array / drop down – typically done when you query a database in programming to populate some items for use by javascript) then Symantec will get it’s knickers in a twist.


imgArr[0] = new Image(“Aniceimage.jpg”);
imgArr[1] = new Image(“anotherimage.jpg”);

imgArr[2000] = new Image(“TheLastImage.gif”);

To show how ignorant they are, if you break it up into script blocks it works fine.


<script>imgArr[0] = new Image(“Aniceimage.jpg”);</script>
<script>imgArr[1] = new Image(“anotherimage.jpg”);</script>

<script>imgArr[2000] = new Image(“TheLastImage.gif”);</script>

 I’ve filed a complaint with Symantec – lets hope they take it seriously!