It would be way cool for it to have a WMI interface. That's the "correct" way for a service to show some GUI, and its not too terribly hard to code... Plus it makes it so you can show the GUI across the network etc etc.. So if I wanna see how computer "USWEST_PRIME_CRUNCHER" (inside joke, sorry bro), I can connect to it and see it via the WMI interface stuff via the MS Management Console.
-Jeremy -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of George Woltman Sent: Tuesday, June 25, 2002 11:46 PM To: [EMAIL PROTECTED] Subject: Mersenne: Prime95 as an NT/2000/XP service I've spent a few days fighting with Windows and MFC to make Prime95 run as a true Windows NT Service. That is, when you check the "Start at Bootup" menu choice, prime95 is installed as a service. At next bootup it starts before anyone logs in. At first login, the familiar red icon appears in the system tray, and prime95 keeps running even when you log off. This question is for the serious NT sysadmins out there: Given that Microsoft strongly discourages NT services having a GUI interface, are there any problems or security issues I need to worry about? A GUI service must run under the Local System account. You can still use Hide Icon to make the service virtually invisible to all users. Even if there are problems, I think this will work well for naive home users running WinXP with multiple user accounts. My hope is to eliminate the NTsetup and NTPrime programs with this feature. ________________________________________________________________________ _ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
