what makes a program close?

  • Thread starter Thread starter bill
  • Start date Start date
B

bill

when I open a program then close it with the X, the window closes but
the process continues to run. If I do the same program on another
computer the process also closes with the window close.

If I open and close it multiple times it leave that many processes
running.

Why does it close the process on one computer but not another?

thx
 
I have swapped files between computers.
They are both running the same OS (XP) with the latest updates.
 
when I open a program then close it with the X, the window closes
but
the process continues to run. If I do the same program on another
computer the process also closes with the window close.

If I open and close it multiple times it leave that many processes
running.

Why does it close the process on one computer but not another?

"A program". Oh yeah, that's descriptive. Did you want an answer as
vague as your post? Okay then. Maybe its a config issue in the
unnamed program, like whether it closes or minimizes (to a tray icon)
when you click the "X" titlebar button.

Read:

http://users.tpg.com.au/bzyhjr/liszt.html
http://support.microsoft.com/default.aspx/kb/555375
 
Bill,

Are you sure the applications aren't being minized to the system tray? Is there an option
to minimise to tray or close immediately?

What programs are these?

If you really want to know what closes the dialogs then Windows uses either two API
functions (SendMessage or PostMessage) passing WM_Close to the dialog once it has the
handle of the dialog. The handle is an IntPtr which if successful holds the address of the
dialog. So, posting WM_Close to it will close it

If you then want to know what closes the dialog when windows closes then it checks WndProc
for the QUERYENDSESSION flag & whatever is in that then shoud be done when Windows closes

Hope this helps,
 
your getting close to the answer I am looking for with such vague
details.

when I asked the question with details no one had a reply.

Now if u can tell me where I might look for this config.
I have searched the reg but found nothing I could relate to the issue.

it is an MS program so it is not a programming issue and it is fine on
another computer.

it is not minimizing to the tray. the process appears in task manager
or process explorer only. if I close the process everything is good
until I open and close the program again.

thx.
 
thx for the reply.

it is not minimizing to the tray or task bar
there doesn't appear to be any options in the program

I tried a fix install and uninstall/reinstall, no help.

since I swapped the program files from the working computer to the not
working one and had no success, I assume the programs are fine.

Are those API functions external to the program?
If so, why would they close all other programs but not this one.
If they are not, since I swapped the files, the exe file and dll files
must be good.

I assume it has to be a registry entry, I just have no clue where to
look.

BTW, the program is MSO Picture Manager and the file it OIS.EXE and
the files I swapped were 4 with OIS... in the name.
 
wrote in message news:[email protected]...
your getting close to the answer I am looking for with such vague
details.
when I asked the question with details no one had a reply.

So you really thought that going vague would be better? Maybe no one
was around at the time you posted that was interested in responding or
didn't know the answer.
Now if u can tell me where I might look for this config.
I have searched the reg but found nothing I could relate to the
issue.

For this as-yet-UNNAMED Microsoft program, start looking in the
options that are available within the program itself (Options,
Preferences, Settings, or whatever it is called in whatever program
you are asking about but don't mention).
it is an MS program so it is not a programming issue and it is fine
on
another computer.

Well, same program but different configuration settings means
different behavior. It is also possible that you have some tray icon
management program installed that you forgot about or don't
understand. What happens when you reboot into Windows's Safe Mode and
rerun the unnamed program?
 
Maybe you told the program to do something BEFORE you told it to close,
and it is still trying to do what you told it to do.
 
hey, thanks for sticking with me and humoring me.

Had not tried safe mode. thx for suggestion.
it works fine in safe mode.
I tried in regular mode with everything removed from startup via
msconfig = same problem.

I tried matching all services running between laptop and desktop =
same problem.

what is different about safe mode that I can't see????????????

BTW - this issue is about MS Picture Manager and the OIS.EXE file.
OIS is PM.
In safe mode and on the laptop it closes when I close the open picture
window. On the DT the process stays running but the window closes.
 
No, I have tried it all ways including first thing from boot.

it works in safe mode, but I can't see why.
I removed everything from startup.
I matched services running with laptop - where it is fine.
nothing seems to fix it.
I stopped about everything I can see or dare to in process explorer,
same issue.
 
BTW
everytime I open a picture file it creates another OIS process.
and none of them close when the window is closed.
It doesn't go back and use the previous one - if that is any clue.
 
OIS? Have you tried Help, Detect and Repair?

BTW
everytime I open a picture file it creates another OIS process.
and none of them close when the window is closed.
It doesn't go back and use the previous one - if that is any clue.
 
more info

if i look at the properties of OIS.EXE in process explorer it shows me
4 threads on both LT and DT (task manager won't show the threads)

when I close the window on the LT all threads close.

when I do it on the LT 3 threads close and this one remains open

"kernel32.dll!CreateThread+0x2e"

if I kill that thread OIS.EXE closes.

the stack for the above thread has 5 occurances of
"ntkrnlpa.exe!........" on the DT
and 3 occurances of "ntoskrnl.exe!...." on the LT
the rest of the stack is the same on both.

when it closed the DT has 8 occurances of "wl_hook.dll+...." that were
not there when open.
a kernel entry that was "RegistrWaitForInput" is now "Sleep"

might this have anything to do with the fact that the DT is an Intel
Q6600 quad processor. I tried restricting it to one cpu.

any of this make sense?????????

thx
 
There wouldn't be any permissions related software running? Anti-malware
or other type folder watch software?
 
Outpost and NOD32, but they are also running on LT

when I kill the thread I get no arguement about it.
 
same things are running on the laptop. Outpost and NOD32

how would that cause the thread to remain open and cause hooks and a
sleep mode to appear????????????

when I kill the thread I get no argument about it.
 
I don't know how you managed to get it to do that. You could try setting
up a different profile with admin. privileges and see if somehow it is
permissions related.
 
get it to do what? are u talking about the hooks?
I didn't get it to do that, it's an ol' windoz trick to get u to do a
clean reinstall.

tried a new user with admin priv
same issue

OK, I'll do a clean install on another drive to see if it is hardware
related. I can't imagine how, but I've run out of options.
 
OK, I did a clean install then loaded only MSO Picture Manager.

worked fine.
Loaded the rest of office
Worked fine.

So I have a program someplace that is messing with PM and it isn't
hardware related.

Weellll, I didn't load all the hardware drivers yet so I see later.
 
Back
Top