[rc5] rc5 nicness

Brian Greul (Exch) bbraf08 at exch-imc.b-r.com
Thu Oct 9 09:53:49 EDT 1997

you could also use the task manager to boost the priority of the GC to
something other than idle.
There are 3 other priorities.
Boosting its priority should help.
But in reality.
This is  a GC programming problem.
It sounds like you need to modify the GC to be 'forcible' on demand, or
to execute after so many hours.
It is concevable that a system running NT might not Idle for a long time
(if it was really busy doing rendering or being a web server)
>From the way this discussion is going it sounds like you want to turn
the world on end to satiate a very small program.

>-----Original Message-----
>From:	Harald Meyer [SMTP:haraldme at metronet.de]
>Sent:	Thursday, October 09, 1997 4:38 AM
>To:	rc5 at llamas.net
>Subject:	Re: [rc5] rc5 nicness
>Hey folks,
>look what I've found at
>> (...)
>> There are three types of components involved in making
>> Windows NT services work. The first component is called the
>>  Service Control Manager (SCM, pronounced "scum"). Each
>> Windows NT system ships with a SCM that lives in the
>> Services.exe file. It is automatically invoked when the operating
>> system boots, and terminates when the system is shut down.
>> This process runs with system privileges and provides a unified
>> and secure means of controlling Win32 services. The SCM is
>> responsible for communicating with the various services, telling
>> them to start, stop, pause, continue, and so on.
>> (...)
>> In addition to the Services Control Panel applet, Windows NT
>> also ships with a command-line SCP tool called NET.EXE. This
>> tool is limited to controlling services residing on the local
>> machine. Using NET.EXE, you can start, pause, continue, and
>> stop services using the following syntax:
>> NET START    servicename
>> NET PAUSE    servicename
>> NET CONTINUE servicename
>> NET STOP     servicename
>> You can also use NET.EXE to display a list of services running
>> on the local machine by simply typing
>> without specifying a servicename.
>> (...)
>This scum seems to be able to stop and continue a service, just like a real
>This would solve the problem with having no idle CPU cycles. Simply stop
>the rc5 client, let the GC do it's work and continue.
>To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in
>the body.
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.

More information about the rc5 mailing list