RE: [ros-kernel] Final module movements

[Steven E. <Ste...@ya...>]

Your right. I was looking at rpcrt on mok last night and then looking at
the wine sources and I agree. What about psapi.dll? WINE seems to be
implemneting more ntapi support but the current psapi uses direct
wineserver calls. How muc of this can we make use of?

Thanks
Steven

"Every revolution was once a thought in one man's mind"
- Ralph Waldo Emerson 

> -----Original Message-----
> From: rea...@li... 
> [mailto:rea...@li...] On Behalf 
> Of Eric Kohl
> Sent: Friday, June 07, 2002 4:54 PM
> To: rea...@li...
> Subject: Re: [ros-kernel] Final module movements
> 
> 
> 
> "Steven Edwards" <Ste...@ya...> wrote:
> 
> 
> > The wine rpcrt4 needs a lot of work. I cannot build it at 
> current do 
> > to unixisms when dealing with time.
> 
> I don't know whether porting rpcrt4 is a good idea.
> 
> RPC is used for the communication of the SCM (Service Control 
> Manager aka
> services.exe) and the services (via advapi32.dll). Rpcss 
> itself is a services started by the SCM. Therefore, the RPC 
> core components (rpcss.exe, rpcrt4.dll and advapi32.dll) have 
> to be part of the reactos cvs module.
> 
> I suggest we rip the usable pieces of rpcrt4 from Wine and 
> combine them with the already 'removed' parts of the reactos 
> rpcrt4. Now that services.exe can load drivers, I can easily 
> add code to start services. And since named pipes are already 
> available it should not be too difficult to get the 
> SCM<->service communication going.
> 
> 
> Eric Kohl
> 
> 
> 
> _______________________________________________________________
> 
> Don't miss the 2002 Sprint PCS Application Developer's 
> Conference August 25-28 in Las Vegas - 
> http://devcon.sprintpcs.com/adp/index.cfm?> source=osdntextlink
> 
> 
> _______________________________________________
> reactos-kernel mailing list rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>