Re: command prompt locks scripts for editing (sysinternals)

[tye]

You should go to http://www.sysinternals.com/ and grab a tool (like Handle) that will show you who really has the file open. It might be cmd.exe or it might be something else that cmd.exe launches that goes away when cmd.exe's console goes away. Perhaps it is something that you can 'kill' to make working around the problem easier.

There are also other tools that will let you monitor what is going on such that you might be able to figure out how to prevent the problem.

I'd think that Perl would not even leave the script open unless you had a __END__ / __DATA__ in it. If so, closing DATA in your script may prevent the problem (yes, I'm not assuming that cmd.exe is what is keeping the file open at this point).