Name, life-cycle, directory structure, autoconf, temporary kludges for wine rpcss subtitute?
gmturner007 at ameritech.net
Fri Nov 1 16:29:44 CST 2002
On Friday 01 November 2002 02:55 pm, Alexandre Julliard wrote:
> Ove Kaaven <ovehk at ping.uio.no> writes:
> > I think I'd say dunno/maybe/yes. There's no terribly good reason to
> > make it compatible, but I know of no terribly good reason not to
> > either (except for the fact that we don't know exactly how much
> > stuff it does - I think it does RPC/DCOM registrations, DCOM object
> > activation, and probably hosts the Running Object Table). It's
> > probably wisest to make it as compatible as we know how anyway,
> > just in case.
> Well, a good reason for being compatible is that we can then plug in
> the native rpcss.exe, that would be a great help for testing. So if
> it's possible I think it's worth it.
I'm afraid it probably isn't, rpcss probably uses NT "Ports" and many
other very scary internal/undocumented wingarbages... I presume all
those "*ss.exe" executables that hang around are this way... then
again, it would be fun to try, wouldn't it? I'll have to snag one from
W2K, run it under wine, and see what happens some time...
It's a service exe, I think, so, presumably, if we want to be like it,
we just follow those conventions (or are there different ones for wine
"The purpose of government is to rein in the rights of the people"
--President Bill Clinton, MTV interview, 1993
More information about the wine-devel