That's disk caching and... any resource that the program use are also
cached.
But.... the process will not still be listed in task manager, that's what
this thread started as

hence my reply
Some program can be written in such away that they 'in simple terms' just
hide, then hang around, just incase the user didn't mean to quit, they
normally lock onto a mutex, when the program gets loaded again, it checks
for the mutex, if its locked, it will know that it has a copy hanging around
and it will tell the 'hanging' around program to un hide itself.
Outlook did this (or at least it did something like this with the old mapi
spooler), not sure if it still does, I am running beta OS and BETA office,
so it would not be a good test on my PC.
Thanks
Steve
"Frank Saunders, MS-MVP OE" <> wrote in message
news:...
> "Steve Drake" <steve@_NOSPAMDrakey.co.uk> wrote in message
> news:735AE31D-7D7E-4247-94B3-
>> mmmm, isn't this up to the developer of that program?
>>
>> or when you say, windows does this, do you mean programs written by
>> MS.
>> If windows kept exe your program running after it received a WM_QUIT
>> message and then when you restart your EXE, does window, send a
>> WM_DONTQUIT? this message does not exist.
> > The programmer is responsible for releasing memory the program's data.
> Windows keeps the program code "just in case". Have you never noticed
> that programs load much faster right after they've been closed? As soon
> as another program needs the memory it is available.
>
> --
> Frank Saunders, MS-MVP OE
> Please respond in Newsgroup. Do not send email
> http://www.fjsmjs.com
> Protect your PC
> http://www.microsoft.com/security/protect/
>
>
>