12 Feb
2007
12 Feb
'07
4:27 a.m.
"Jeff Latimer" <lats(a)yless4u.com.au> wrote:
+ rc = pNtCreateMailslotFile(&hslot,
DesiredAccess,
+ &attr, &IoStatusBlock, CreateOptions, MailslotQuota, MaxMessageSize,
+ &TimeOut);
+ ok( rc == S_OK, "Create MailslotFile failed rc = %x %u\n", rc,
GetLastError());
NT APIs return STATUS_xxx error codes, S_OK is an OLE error value.
+ ok( hslot != INVALID_HANDLE_VALUE, "Handle
is invalid\n");
INVALID_HANDLE_VALUE is a kernel32 thing, NT APIs don't use it. Most likely
you need to test returned value against 0.
+ ok( CloseHandle(hslot), "CloseHandle
failed\n");
To close the handle returned by an NT API you have you use an NT API as well.
--
Dmitry.
17 Feb
17 Feb
9:15 a.m.
New subject: 1/4 NtCreateMailslotFile tests
Dmitry Timoshkov wrote:
"Jeff Latimer" <lats(a)yless4u.com.au>
wrote:
Have reread MSDN http://msdn2.microsoft.com/en-us/library/ms648410.aspx
and it seems that NtClose has been superseded by CloseHandle. So I
suppose that CloseHandle is the one to use. Have fixed the other points.
Jeff
+ ok( CloseHandle(hslot), "CloseHandle
failed\n");
To close the handle returned by an NT API you have you use an NT
API
as well.
9:51 a.m.
New subject: 1/4 NtCreateMailslotFile tests
"Jeff L" <lats(a)yless4u.com.au> wrote:
> To close the handle returned by an NT API you have
you use an NT API
> as well.
What is not apparent in the explanation above?
Have reread MSDN
http://msdn2.microsoft.com/en-us/library/ms648410.aspx
and it seems that NtClose has been superseded by CloseHandle. So I
suppose that CloseHandle is the one to use.
The information in MSDN is misleading in this case, CloseHandle is a kernel32
API, not an NT (native) one.
--
Dmitry.
9:58 a.m.
New subject: 1/4 NtCreateMailslotFile tests
Dmitry Timoshkov wrote:
So the correct move is to use the depreciated function? Microsoft
appears to be pushing people away from NtClose. Is the it that they are
reserving NtClose etc for their ntdll use?
Jeff
"Jeff L" <lats(a)yless4u.com.au> wrote:
I have no problem with what you have
said though I did have a bit of
difficulty marrying to the sentence below.
> To close the handle returned by an NT API you
have you use an NT API
> as well.
What is not apparent in the explanation above? Have reread MSDN
http://msdn2.microsoft.com/en-us/library/ms648410.aspx and it seems
that NtClose has been superseded by CloseHandle. So I suppose that
CloseHandle is the one to use.
The information in MSDN is misleading in this case, CloseHandle is a
kernel32
API, not an NT (native) one.
2:29 p.m.
New subject: 1/4 NtCreateMailslotFile tests
"Jeff L" <lats(a)yless4u.com.au> wrote:
So the correct move is to use the depreciated function?
It's not deprecated, even Microsof tries to create an impression it is.
Have reread MSDN
http://msdn2.microsoft.com/en-us/library/ms648410.aspx and it seems
that NtClose has been superseded by CloseHandle. So I suppose that
CloseHandle is the one to use.
The information in MSDN is misleading in this case, CloseHandle is a
kernel32
API, not an NT (native) one.
Microsoft
appears to be pushing people away from NtClose.
I'd suggest you to find a reason why.
Is the it that they are
reserving NtClose etc for their ntdll use?
Also I'd suggest to learn about a difference between Native and Win32 API
before writing the tests that mix them.
--
Dmitry.
19 Feb
19 Feb
1:37 a.m.
New subject: 1/4 NtCreateMailslotFile tests
Microsoft
appears to be pushing people away from NtClose.
I'd suggest you to find a reason why.
11:40 a.m.
New subject: 1/4 NtCreateMailslotFile tests
richardvoigt(a)gmail.com wrote:
That particular documentation happens to
be part of the API released
under court order. They didn't want to give it out to begin with, and
they don't want people using it now. Ok I am happy with this as an explanation
and will move the tests.
Another case of MSDN telling fibs to the gullible.
Jeff
Microsoft
appears to be pushing people away from NtClose.
I'd suggest you to find a reason why.
6299
days inactive
6306
days old
6 comments
3 participants
participants (3)
-
Dmitry Timoshkov -
Jeff L -
richardvoigt＠gmail.com