Another possibility is that your script is trying to write to a file that IIS4 has locked, so that you're sitting there waiting for the lock to be released; guestbooks, for example.
A particularly insidious aspect of this is that the server tracks what page the browser is looking at. If you're looking at a page with a browser, the page is locked and you can't delete it. If you move to another page, the first is unlocked.
If you can afford to, you can reduce this problem by turning off caching in your server. This apparently also stops caching for DLLs, ASP pages, etc. too.
If desperate to change a page, stopping and restarting the web server will clear out the lock, but that's a little extreme.