DaveL <dlo...@tricord.com> schrieb am 10.10.96:
Look up:
CreateToolhelp32Snapshot
Process32First
Process32Next
--
Claus André Färber <cl...@faerber.muc.de>, <http://www.muc.de/~cfaerber/>
These work under 95, but not under NT.
jw...@oro.net
..David..
Claus André Färber <cl...@faerber.muc.de> wrote in article
<6IidU...@faerber.muc.de>...
>Hallo DaveL, hallo alle zusammen,
>DaveL <dlo...@tricord.com> schrieb am 10.10.96:
>> Is there a Win32 API call or console command
>> in NT that acts like the Unix "ps" command,
>> which gives status of all processes running
>> on the system? I'd prefer to execute this as
>> a function call from a C program.
>Look up:
> CreateToolhelp32Snapshot
> Process32First
> Process32Next
>--
>Claus André Färber <cl...@faerber.muc.de>, <http://www.muc.de/~cfaerber/>
Those functions will not work under Windows NT !
Grtz, Wido
Sigurd
Wido Riezebos <riez...@twice.nl> wrote in article
<01bbea1e$cf65e2e0$c53e4fc1@client1>...
A 16-bit process may seriously degrade performance of
threads that use user interfacve DLLs, i.e. draw or write something
on screen, manage windows, send messages, etc.
Even if these threads are 32-bit, they will be in a hung state waiting
if a badly behaved 16-bit process doesn't yield control with GetMessage()
like functions.
A 16-bit processes that behaves really well in this, e.g. spends its
life gettings messages in a loop and processing them quickly or
yielding often if it processes them for a long time, will not
seriously affect system performance.
In Win32 API space, you can write the ps command
by using the Performance Data API's.
e-mail me if you want my "home-grown" version of ps.
Ernesto L. Aparcedo
nf...@ccmail.ceco.com