Eric wrote:

> I want to use the RegisterServiceProcess API in both Win 98 and Win
> NT, but Win NT seems to not support RegisterServiceProcess, is there
> an alternative?

Yes. RegisterServiceProcess() API was introduced in Windows 95 just to 
support a minimal part of the services APIs in Windows NT. Windows NT 
contains the complete Service Control Manager API and therefore does not 
need RegisterServiceProcess().

What is it that you want to do?

If you want to application automatically started and make sure it does 
not shutdown just because a user logs out you can install your 
application as a Windows NT service. I have seen guides how to do that 
for a Visual Basic application some years ago but I don't remeber where 
I saw it, maybe you can search for "visual basic" "nt
service" or 
something. The example I saw used an external OCX and a DLL to provide 
the Service Interface needed to communicate with Service Control 
Manager, and then the service control codes where received a messages to 
the OCX object. An alternative is to use srvany in the Windows NT 
resource kit. Srvany can start any application as a service.

If you have used RegisterServiceProcess() in Win 9x just to prevent your 
process from being displayed in the Task List, there is no such thing in 
Windows NT. Windows NT Task Manager always displays all processes 
running on the system (except on Terminal Services, but that's another 
story).

-- 
Olof Lagerkvist
ICQ: 724451
Web page: http://here.is/olof
---
þ RIMEGate(tm)/RGXPost V1.14 at BBSWORLD * Info{at}bbsworld.com

---
 * RIMEGate(tm)V10.2áÿ* RelayNet(tm) NNTP Gateway * MoonDog BBS
 * RgateImp.MoonDog.BBS at 6/15/04 1:02:54 PM