when we use iocp,first,we should create a port like
this --- CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, 0, 0);---
But in the implementation of CreateIoCompletionPort,the beginning of the
fuction is :
if ( ExistingCompletionPort == NULL && FileHandle == INVALID_HANDLE_VALUE
)
{
SetLastError(ERROR_INVALID_PARAMETER);
return FALSE;
}
so ,all the application running well on MS Windows will not run correct in
ReactOS,Because they will always get the ERROR_INVALID_PARAMETER error code
when they
call CreateIoCompletionPort like
--CreateIoCompletionPort(INVALID_HANDLE_VALUE, NULL, 0, 0);--
I think this is a problem,But I'm not sure!
Hello,
it's not really completely supported now.
As for the label, it was a typo, and I fixed it in revision 31882.
WBR,
Aleksey Bragin.
On Jan 19, 2008, at 12:48 PM, Xiaoming Gao wrote:
> Hello everyone
> I'm a new comer,i'm reading the kernel source ,but i found that
> "jz NotBusy " in ctxswitch.S (line 351),the NotBusy label is not
> defined.I have searched the whole source code,but not found it. So,
> would someone tell me some information about this?
Hello everyone
I'm a new comer,i'm reading the kernel source ,but i found that "jz
NotBusy " in ctxswitch.S (line 351),the NotBusy label is not defined.I have
searched the whole source code,but not found it. So, would someone tell me
some information about this?
> trunk/reactos/dll/win32/kernel32/lang/pl-PL.mc (with props)
IMO is not a good idea to use different mc files for every language. MC file
format is specially designed to hold all the languages in the same file,
also our current WMC implementation does not support splitting translation
across multiple mc files. AFAIK Physcious was working on implementing that
feature to our WMC but even in that case there is no easy way to support
them at rbuild level without introducing a hack, also MS's WMC does not
support it so I think we should keep it to the lowest common denominator and
avoid future compiler compatibility problems as there isn't any significant
advantage on it.
/Marc
jimtabor wrote:
>when WindowObject->Wnd is NULL and WindowObject is not NULL
> it crashes in vis.c line 89.
[...]
>Since this crash is started in GetDCEx with a NULL "Window"
>call leaves me with a bad taste. The code was written prior to
>having Desktop support, later hax. So having null window
>associated with DCE is okay then, not now.
>
>Any Ideas?
Isn't this the case where it in Windows originally got the meaning
"use the desktop window", that later became a compatibility hack where
"NULL isn't a cool HWND, but due to the many programs using it, we'll
automatically give the user the DC for the (currently visible) screen"
(or possibly the desktop associated with the thread)?
--
Mike
Hi,
>From this patch
http://svn.reactos.org/svn/reactos?view=rev&revision=30477, I found
when WindowObject->Wnd is NULL and WindowObject is not NULL it crashes
in vis.c line 89. This patch is okay. My best guess, when Wnd is null
that means the window is on the way of removal. Luck of the thread? I
can patch and protect the while loops in vis.c but the crash moves to
another place based on the same null Wnd problem. Since this crash is
started in GetDCEx with a NULL "Window" call leaves me with a bad
taste. The code was written prior to having Desktop support, later
hax. So having null window associated with DCE is okay then, not now.
Any Ideas?
Thanks,
James
Hi list,
attached is a patch to update the crypt-related part of advapi from
wine.
Hope this patch is useful. It's less intrusive than earlier patches from
me.
Please use it,
Christoph (aka egore on IRC)