>>>>>Not that votes mean anything, I think that Ed is right about this one. If the whole EXE was loaded, why would the EXE file be "used by another process" if you try to make changes to it?
>>>>
>>>>This flies in the face of how Windows computers operate. EXEs are loaded into memory and if there isn't enough space in memory then the EXE is put into virutal memory which is usually on the local C: drive.
>>>>
>>>>The EXE is locked because this the file is in use. This is a quirk of file servers. I have never really understood why this locking occurs, it doesn't seem to make sense with EXEs.
>>>
>>>Try this: Load a VFP EXE. Load NOTEPAD.EXE from wherever you have it. Now, with both EXEs loaded, try to rename the VFP EXE. You can't, right? Try to rename the NOTEPAD.EXE. You can, right? What does this tell you?
>>>
>>
>>Put notepad.exe on the server and try the same test.
>
>As expected, I loaded notepad from the server (changed to the server's WINNT directory and ran notepad from there), then renamed the file and it had no problem. If I tried the same thing with a VFP exe, it wouldn't allow me to rename the EXE.
>
>I doubt you had any different results.
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.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement