Re: Why does explorer assign a job object to some processes and not ot
- From: Len Holgate <len.holgate@xxxxxxxxxxx>
- Date: Thu, 31 Jul 2008 08:50:04 -0700 (PDT)
On Jul 31, 2:22 am, robe070 <robe...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We are trying to control child processes of our main process by assigning
these children to a Job Object. But, if we start the main process from
Explorer it is assigned one already hence we cannot assign another Job
Object. On the other hand if we execute our main process from the command
line, it does not have a Job Object. This can be viewed using Process
Explorer and looking at tyhe Process' properties - it eithe rhas a Job tab or
it does not.
Thats the background to the question, why is it assigning a job object when
I execute the app from a folder, but when executed from the command line it
does not get a job object?
According to Richter's Window's Via C++ book...
In Vista, Explorer will add processes which don't have a manifest to a
"PCA" prefixed job so that the Program Compatability Assistant can
jump in and 'help' if it crashes. To avoid having explorer add your
process to one of these jobs you need to define a manifest for the
application.
Len
http://www.lenholgate.com
.
- Prev by Date: Re: How to access Graphic Card Memory from a driver
- Next by Date: Re:ReadFile/WriteFile on PhysicalDriveXX
- Previous by thread: Re: How to access Graphic Card Memory from a driver
- Next by thread: Re:ReadFile/WriteFile on PhysicalDriveXX
- Index(es):
Relevant Pages
|
