|We don't bite newbies here... much|
command prompt locks scripts for editingby inman (Curate)
|on Jun 02, 2006 at 14:43 UTC||Need Help??|
inman has asked for the
wisdom of the Perl Monks concerning the following question:
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:
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!