🚀 go-pugleaf

OK, if you would read more accurately...
psapi.dll IS PROVIDED with the Windows XP, plus I don't get that remark of 
yours about Windows 2, lol, I mean Microsoft treats Windows XP as Windows NT 
5.1 (another name for XP), yeah tlhelp is ok, but it misses some 
functionality, and I get the best results when I combine the use of these 
two dlls.

"Ed Mulroy [TeamB]" <dont_email_me@invalid.com> wrote in message 
news:4249bdd8@newsgroups.borland.com...
> No, Windows XP is not NT.  XP is no more NT than Windows 3.1 was Windows 
> 2.
>
> psapi is supplied by the operating system.  If it works differently then 
> that is because what the operating system supplied works differently.
>
> XP provides the toolhelp32 api.  I suggest that you use it.
>
> .  Ed
>
>> Danila Vershinin wrote in message
>> news:4249ba0c@newsgroups.borland.com...
>>
>>I use PsApi.dll functions to retrieve a list of running processes on the 
>>system. Documentation says that exactly PsApi.dll should be used on NT 
>>systems, so I figured out that this is what I should use (Windows XP is 
>>NT, right? lol...).. but NOO... the functions do not work exactly the way 
>>the should, it happens so that some of the processes can not be accessed 
>>and their names accordingly too.. plus the filenames for some processes 
>>are in the form /??/FileName which is not good... but that is common 
>>problem with filenames in psapi.dll, even msdn says smth about that.. 
>>there is even some code there to convert such filenames...
>> But still, what is the problem of that DLL? because when I use another 
>> DLL - tlhelp32 for the same task it shows everything the way it should 
>> be...
>> but the oddest thing is that running VB's samples for the psapi it works 
>> just fine (still the filenames prob but no access problem) , weird, huh?
>
>