Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.

You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.

the answer to first might be to run PT as a service; there was some discussion of looking into this earlier but i haven't yet. if you can find any discussion of these issues and why some apps "resist" i'd love to see.

the answer to second is that i will probably implement this as an option, though there seems to be a debate about whether one would expect to get a benefit from this, since windows 2k/xp is supposed to do this semi-automatically behind the scenes, as i understand it.

I couldn't find anythign on how/why some processes resist the change. I have noticed that some programs set their own priorities and will eventually re-set process tamer's choice. This is a different issue from where programs are simply resistant, but I wanted to mention it as well.

As for 'resistant' programs, maybe this has somethign to do with the level at which PT is running. Maybe running it as a service (as you suggested), would solve this. Other than that, though, I couldn't find any other information on the matter.

if someone could find a program or two for me that pt can't tame that i could run during testing, that would help a lot.

My first post here, so hello everyone.

I've just moved to process tamer from process lasso, I prefer the way you can quickly toggle on/off from tray icon, and I notice that PT can't tame winlogin.exe (XP pro sp2) yet PL can. Not sure if it's related to PL running as a service and PT not, but it's one of the first things I noticed. So at least you have something to play with whilst testing.

Hope that helps.

P.s. the site mentions something about a 'members only version' of the program, but I can't seem to find it, although I am happy with the version I am using so it's no big deal. Just wondering if I missed it or something.

« Last Edit: December 08, 2005, 12:14:35 PM by Zeph »

Logged

A proud member of The Z Project, developers of the HLGuard & AutoBan anticheat systems, Z-Tweaked drivers and more...

if it says somewhere about a members only version of the program then that's just a mistaken holdover from when we allowed members early access to the most recent versions. now we allow everyone access to the most recent releases, so there is only 1 version for everyone. (if you remember where it says that let me know and i'll correct).

yes, we have to add the ability to tame such things - process tamer 3 is in the works and the ability to tame these is definitely planned; as you say it's likely due to the fact that pt does not run as a service. couple ways we can solve it, not sure which route to take at the moment, but we'll get it supported.

There are are a few services/processes that simply ignore Process Tamer.

I am seeing this problem now, and I can give a specific example: mstDfrgS.exe, which is a service installed by mst Defrag Home Edition 1.9. I've configured PT 2.05.02 to force mstDfrgS.exe to low priority, but it never does.

The strange thing is that Sysinternals Process Explorer can set the process priority class of mstDfrgS.exe to 4 (i.e. "low") without a problem. Similarly, the command line utility Process.exe can set it to 4. So why can't PT do the same?

I haven't tried running PT as a service, because honestly, I don't want to run it as a service. And this isn't a "permissions" issue in that regard anyway. In fact, PT's log doesn't show any attempt to set the priority of mstDfrgS.exe at all. So, I guess we can never mind the question of why the other utils can set the priority and PT can't, and start wondering why PT doesn't seem to try in the first place.

Huge apologies (to you and everybody else) for butting in on this thread, but a long time ago in a thread far far away you mentioned a sneaky way of suppressing the Splash Screen in XFilesDialog - Have just purchased it and was annoyed to find that the splash screen is not removed (the author seems adamant about retaining it ).