Hi,
On Wed, Sep 21, 2005 at 10:35:13AM +0200, Boaz Harrosh wrote:
> Funny how Microsoft uses a totally different set of Headers for CE.
> Even the Wine-headers are closer to the original SDK than CE. The order
> of function is different, the macros, the styling. There is no
> resemblance, not
On 9/20/05, Filip Navara <[EMAIL PROTECTED]> wrote:
It was proved that to run simple WinCE/x86 programs all that is
needed is to get the loader to accept the WinCE PE signature (which Wine
used to ignore and probably still does) and have implementation of the
DLLs...
Was that on React-OS o
Hi,
On 9/20/05, Filip Navara <[EMAIL PROTECTED]> wrote:
> We have already made this experiment once ... you can find info about it
> in the ros-dev (or ros-kernel) mailing list archives and skeletons of
> the two WinCE DLLs in the ReactOS SVN history
> (trunk/reactos/lib/commctrl and trunk/reactos
Boaz Harrosh wrote:
[snip]
What if I want to do the same but for WindowsCE x86?
We have already made this experiment once ... you can find info about it
in the ros-dev (or ros-kernel) mailing list archives and skeletons of
the two WinCE DLLs in the ReactOS SVN history
(trunk/reactos/lib/com
OK What you guys think.
I have an Arm based machine Running Windows CE. Same machine also runs
Linux...
Do you think it can be the same Wine codebase, implementing Both Win32
API as well as WindowsCE API?
What areas must be rewritten (or not) ?
1.Loader
2.HAL (is there an HAL in Wine)
3.
