Hi, I'm no expert on windows programming, but take a generally downbeat view of the amount of ongoing time and effort required to code for the "proprietary API of the week" that seems to characterise this OS.
Consequently, is it possible for someone to code a service "wrapper" that spawns the prime service as an additional process? In other words, separate out the service management and icon code into a separate process, which can be developed by a larger public group, rather than have all this code in prime.exe itself with the corresponding requirement that the coding effort all fall on the shoulders of one person. This would allow outside parties to develop the most fancy and functional frontends, and be able to do all the compilation steps themselves while circumventing the need to have access to the necessarily secret encryption algorithm that protects the authenticity of results. Can this be done? Surely this one's a runner? Yours, Gareth George Woltman wrote: > At 10:46 AM 7/29/2002 -0700, Aaron wrote: > >> I suppose it's probably documented somewhere, but it seems that Prime95 >> ignores any service name settings in the existing NTPrime local.ini >> file... >> >> So I'm still using NTPrime on my dual CPU machines... Any chance of >> getting prime95 to honor the service name settings in the local.ini file >> just like ntprime did? > > > Already coded and tested. Look for the fix next time I upload a new > prime95 -- ======= Gareth Randall ======= _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
