I have encountered a frustrating error that stops me from editing and testing a script in Windows XP SP2. I would like to know whether anyone has encountered the same thing and whether it can be fixed.

I have just re-installed Perl and restored my data as I had to get a new hard disk following the failure of my old one. The software image is provided by my company and is Windows XP service pack 2 with the latest security updates. I have installed the latest vesrion of Activestate Perl (v5.8.8).

When it comes to development, my method of working is to edit the script and then test it in a command prompt (CMD.EXE) before making changes and testing again using the same instance of the command prompt. The problem surfaced when I tried to save the changes to the script and my editor told me that the file was locked (file unavailable or readonly) by another process.

I have done a fair bit of investigation and come up with the following:

1. The problem is limited to a script executed via the extension association. Running myscript.pl at the command line will lock the source file. If I use perl myscript.pl there is no problem.
2. The script itself runs as expected even though the source cannot be edited.
3. I have tested various other situations where the file association is used (E.g. running the script from Explorer) and not had a problem.
4. The source file is locked (reported as readonly) until the CMD.exe instance is closed.
5. The inability to edit has been verified with standard tools such as notepad and edit in order to remove the editor form the problem.

The only concludion that I can draw is that CMD.EXE is somehow holding on to the file after it has been executed in the way described.

Is anyone else able to reporoduce this issue? Although, I can work around the problem but I am finding it particularly frustrating!

cheers