Re: [ros-svn] [ea] 18219: A do-nothing crt0 for native NT processes.

[Alex Ionescu]

[e-mail] wrote:
> A do-nothing crt0 for native NT processes.
> (see note by A.Ionescu in reactos/subsys/crt/main.c)
>
> Added files:
> trunk/reactos/lib/ntrt0lib/
> trunk/reactos/lib/ntrt0lib/args.c
> trunk/reactos/lib/ntrt0lib/entry_point.c
> trunk/reactos/lib/ntrt0lib/ntrt0.h
> trunk/reactos/lib/ntrt0lib/ntrt0lib.xml
>
> Updated files:
> trunk/reactos/lib/directory.xml
>
> Ros-svn mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-svn

Hi,

Thanks, I didn't have time last night ( I went to bed at 5AM). Do you 
mind if I rename this to "nt" ? It's the official name of the DDK static 
lib, and would mean that we don't have to have 2 .XML files for anyone 
using the library (for the msvc build).

Anyways, I'm going to commit the code now, I have it on my disk.

Best regards,
Alex Ionescu

[Emanuele Aliberti]

Alex Ionescu wrote:
> Thanks, I didn't have time last night ( I went to bed at 5AM). Do you 
> mind if I rename this to "nt" ? It's the official name of the DDK 
> static lib, and would mean that we don't have to have 2 .XML files for 
> anyone using the library (for the msvc build).
>
> Anyways, I'm going to commit the code now, I have it on my disk.

No problem for me. I didn't even know there was one. What puzzles me is 
the ANSI signature for the main function. NT is almost everywhere 
Unicode, but in the entry point of a native process...
-- 
:Emanuele Aliberti

[Alex Ionescu]

Emanuele Aliberti wrote:
> Alex Ionescu wrote:
> > Thanks, I didn't have time last night ( I went to bed at 5AM). Do you 
> > mind if I rename this to "nt" ? It's the official name of the DDK 
> > static lib, and would mean that we don't have to have 2 .XML files 
> > for anyone using the library (for the msvc build).
> >
> > Anyways, I'm going to commit the code now, I have it on my disk.
>
> No problem for me. I didn't even know there was one. What puzzles me 
> is the ANSI signature for the main function. NT is almost everywhere 
> Unicode, but in the entry point of a native process...

That's because _wmain didn't really appear until much later. Vista's 
nt.lib now implements NtStartupProcess (calls _main) and 
NtStartupProcessW (calls _wmain). I didn't implement it yet because I'm 
waiting for Thomas's patch to make mingw support _wmain.

Also, speaking of mu-sessions and smss, you might be interested to know 
that Vista now has a completely re-designed LPC called ALPC (you can 
email me if you want more info), as well as a much more "open" and 
public SMSS, now accessible through functions like RtlConnectToSm and 
RtlSendMsgToSm. I'm going to guess that some of the features regarding 
mu-sessions you've wanted will actually be done right this time:)

Best regards,
Alex Ionescu

[Emanuele Aliberti]

Alex Ionescu wrote:
> > No problem for me. I didn't even know there was one. What puzzles me 
> > is the ANSI signature for the main function. NT is almost everywhere 
> > Unicode, but in the entry point of a native process...
>
> That's because _wmain didn't really appear until much later. Vista's 
> nt.lib now implements NtStartupProcess (calls _main) and 
> NtStartupProcessW (calls _wmain). I didn't implement it yet because 
> I'm waiting for Thomas's patch to make mingw support _wmain.

That explains this oddity.
> Also, speaking of mu-sessions and smss, you might be interested to 
> know that Vista now has a completely re-designed LPC called ALPC (you 
> can email me if you want more info), as well as a much more "open" and 
> public SMSS, now accessible through functions like RtlConnectToSm and 
> RtlSendMsgToSm. I'm going to guess that some of the features regarding 
> mu-sessions you've wanted will actually be done right this time:)

My English must be really bad, because I totally dislike μSessions and 
the way the SM is implemented in 2k/XP/2k3 (which is the design that 
inspired you in writing the new CSR). The main problem is Win32 
polluting everything in MS design: from kernel up. SM and CSR aren't 
exceptions. My goal was drawing a sharp line between the ROS core and 
any personality subsystem: cloning the MS CSR (and modifying the SM to 
work with it) will bind ROS to Win32 and leave other personality 
subsystems no run-time to grow upon. Thightly binding ROS to Win32 means 
problems in Win32 may propagate deep down in the system and vice versa 
(the well known example is win32k.sys, which can not be removed though).

RtlConnectToSm!? Well, it seems that MS eventually cloned our smdll.dll :)
-- 
:Emanuele Aliberti