Hi Evan,

As I tried to say earlier, this *could* be because WIN, recognizing an EXE and knowing that such are read-only when executing, "knows" it can refresh code from the EXE rather than placing it on the SWAP.

IBM used to do that in earlier OS/2, but learned that that was the obtuse way to do it. It 'locked' the EXE and took lots of specialized and slow-executing code to achieve the desired result. It (more or less) had to 'virtually' re-run the load process so that code would be sequenced correctly and so that addresses could be resolved correctly.

It was far better to simply load the whole EXE and let the regualr SWAP mechanism work on it too. SWAP was (is) highly debugged, highly optimized, high(est?) priority, etc.

Personally, I had thought that WIN did the 'load it all' thing too, and I am not convinced that being unable to overwrite an executing EXE "proves" the case that it does not. On the other hand, the earlier OS/2 which operated as earlier described may well have been written by MS, since that was from the days when it was still a joint project. Possibly IBM moved on while MS stayed with what it had already designed.

If MS is doing this, you can bet on a change some day, as trhis is simply the worst way to accomplish the desired result.

Cheers,

Jim N

>>>
>>>Actually I had the opposite. (I was not allowed to rename or delete either file). One interesting thing though, we are running different servers. I am using Netware 4.10.
>>>
>>>Let me research how Windows loads and EXE file into memory and I will get back to you.
>>
>>Awwww....Netware....no wonder. I think you should switch to Windows NT.
>
>I know. :-)
>
>FYI. I just tried the same experiment on my Windows NT workstation c drive. I load both the Notepad and an VFP EXE... I can't delete either while they are running.
>
>The search continues...