Thread View: borland.public.cppbuilder.deployment
5 messages
5 total messages
Started by Danila Vershinin
Tue, 29 Mar 2005 08:57
Windows XP and PsApi.dll
Author: Danila Vershinin
Date: Tue, 29 Mar 2005 08:57
Date: Tue, 29 Mar 2005 08:57
13 lines
1798 bytes
1798 bytes
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?
Re: Windows XP and PsApi.dll
Author: Ed Mulroy [TeamB]
Date: Tue, 29 Mar 2005 20:42
Date: Tue, 29 Mar 2005 20:42
30 lines
2293 bytes
2293 bytes
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?
Re: Windows XP and PsApi.dll
Author: Danila Vershinin
Date: Wed, 30 Mar 2005 00:02
Date: Wed, 30 Mar 2005 00:02
38 lines
2745 bytes
2745 bytes
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? > >
Re: Windows XP and PsApi.dll
Author: Ed Mulroy [TeamB]
Date: Wed, 30 Mar 2005 01:30
Date: Wed, 30 Mar 2005 01:30
19 lines
1826 bytes
1826 bytes
> ... I mean Microsoft treats Windows XP as Windows NT 5.1 ... Microsoft in some ways treats Windows XP as Windows 2000. However that is NOT as Windows NT. As examples, Windows XP and Windows 2000 both are stable and both provide Toolhelp32 support. The reference to Windows 3.1 versus Windows 2 alluded to how Windows 3.1 worked and Windows 2 did not. . Ed "Danila Vershinin" <danprep@yahoo.com> wrote in message news:4249eca8@newsgroups.borland.com... > 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.
Re: Windows XP and PsApi.dll
Author: Danila Vershinin
Date: Mon, 11 Apr 2005 07:08
Date: Mon, 11 Apr 2005 07:08
11 lines
1561 bytes
1561 bytes
"Ed Mulroy [TeamB]" <dont_email_me@invalid.com> wrote i <XP provides the toolhelp32 api. I suggest that you use it. Hi Ed, thanks for the suggestion BUT... when I use Dependency Walker for taskmgr.exe (Windows Task Manager) guess what I see? psapi.dll module and no tlhelp32.... So that's how it is on XP... at least for the matter of getting processes' info NT-kind DLLs are used. Cheers, Danila
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads