webfork wrote:
computerfreaker wrote:
Do you think the entry looks OK now?
I added a bit more to the description drawn from the feature list on the website. I figure its incomplete if we describe it as "feature-packed" without listing any of those features.
Thanks for doing that! I thought about doing a feature list, but couldn't seem to get all the features summarized into a reasonably small block of text.
webfork wrote:
computerfreaker wrote:
I've got to be careful with all these edits or I'm going to end up getting banned
Although on some servers they come up as red flags, you will not get banned for frequent edits here on PFW. I know because I've edited PicPick like 20x and there were no issues.
That's good to hear. I was basing my statement off this quote, which always comes up when I'm editing an entry:
Quote:
Note: All edits are logged. If any member is found to abuse this privilege, inappropriate changes will be reverted and the offending member may be permanently banned.
"abusing this privilege", at least to me, means excessively using the Edit feature, hence the concern.
guinness wrote:
Quote:
I've got to be careful with all these edits or I'm going to end up getting banned.
No at all! You have made great contributions to the TPFC community. It would be petty if you were banned for improving the quality of your suggested application

Well, I don't really believe in giving users more leeway just because they've contributed a bit. "Rules is rules", which means I really should have done a good job the first time.
-.- wrote:
since this doesnt use .net I'll switch back to it from process explorer, i find a lot more features on processhacker and i like the services tab.
Yeah, the Services tab is a nice feature. I've used it a lot over the past few days; let's just say I was surprised by how many services are on this old system.
-.- wrote:
edit, found kprocess in services tab, stopped/removed it from there and seems to work fine. though it wont fix stealth issue, i can leave the .sys in folder and it wont use it now

I'm pretty sure it'll still leave Registry traces from where the driver was installed, though. I think the only way around that is to delete (or rename) the driver before installing it, which means deleting the driver before running Process Hacker.
Incidentally, once the PortableApps.com Launcher supports handling services & drivers, we can have a truly portable version of Process Hacker complete with its driver. I know a lot of users on here don't use (or like) things from PortableApps, but I figure it's worth mentioning for those who do.