Application: Process Explorer
Category: Utilities
Description:
Ever wondered which program has a particular file or directory open? Now you can find out. Process Explorer shows you information about which handles and DLLs processes have opened or loaded.
The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you'll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you'll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded.
The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.
Download Process Explorer Portable 11.33 Development Test 2 (Online) [0.8MB + 1.6MB download / 3.8MB installed]
(MD5: 5512e469f7a453427ec4d9f1864404eb)
Release Notes:
Development Test 2 (2010-02-11):
- Fixed an issue where you might have to accept the EULA twice (once in the installer, once in Process Explorer itself) under Wine.
- Removed PortableApps.com Launcher source code from package
Development Test 1 (2010-02-11): Initial release
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It really is most fascinating to test this sort of thing in Wine. The online installer worked perfectly (I wasn't certain it would, but it did, so that's good). Then I looked at your launcher.ini. Comments on that later. I then ran Process Explorer Portable... and what a fascinating experience that was. I've never run Process Explorer in Wine before, and it behaves in a most curious way; its CPU meter runs from minus several hundred billion percent to one hundred percent in turn in a most alarming manner (sometimes it's only minus several million; however with the meter-per-CPU option turned on, each core remains at zero (or less, I can't tell)... Wine outputs a lot of "fixme" and "stub" and similar unrelated messages to the console, and all sorts of slightly unusual things happen. However, it does run, even more or less as hoped for - and don't you just wish you could only have one process other than System running in Windows?
I was even astonished to find that Process Explorer can still be useful in my methods of making things portable - you can still view the image path, command line, environment (but not threads due to some Microsoft package needing to be installed first)... I was very much impressed that it worked so well in Wine.
Now to the matter in hand; Process Explorer Portable. What you've got is fine, but I have a few points for you.
[Launch]:DefaultCommandLineArguments=/accepteula. (This is documented in the "Accept the EULA" window.) Since writing that, I see you have DefaultData to do that; I would remove DefaultData and just use the /accepteula flag. The DefaultData just didn't work on Wine (see two points down) so I didn't notice it.I wouldn't bother putting in the PAL source code in Other\Source; we won't be when it (PAL) is an official release.
Thanks.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Yeah, I'm sure something like Process Explorer makes a great stress test for Wine.
Hadn't realized there was an /accepteula switch, that's why I used DefaultData to skip it. If I had known known about the switch before I definitely would have used that instead. Thanks!
I'll keep the thing about the source in mind. Basically what happened is I created a template by installing PAL in my Projects folder, then when I need to make a new app I just clone the PAL folder and go from there. So the PAL installer includes the source, therefore it ended up in there. So I'll just take it out of my template, this way it won't sneak in in the future.
Regarding the drive letter substitution, I seem to remember seeing a value in the Process Explorer registry key that looked like it was meant to hold a path to a user-specified file. I'll look further into it before I release Dev Test 2, though.
Edit: I just thought of something. Is it possible the PortableApps.comInstaller folder created by the installer for EULA management is confusing PAL under Wine and causing it not to copy the DefaultData over? This doesn't explain why the registry isn't being saved properly, however, so it's probably not it...
Edit 2: I just looked it over, and I found two path values in the registry for PE: DbgHelpPath (which by default points to a built-in DLL in system32) and SymbolPath. Presumably the user could set either of these to something on the portable drive, so I'm leaving the drive letter substitution in.
The PortableApps.comInstaller directory will not affect PAL in the slightest. It'll be a deficiency in Wine which I'll have to work around.
Concerning a template, I think I'll be doing one for the PortableApps.com Launcher myself. I may release it along with PAL 1.0 Alpha 3 today.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Process Explorer Portable has been updated to 11.33 Development Test 2. See top of page for details.
When I start the program, the Development splash screen comes up but the program screen never does. The cpu is clocking at about 90% and I've let it run for 4 minutes before cancelling it with Task Manager. I reverted back to Development Test 1 and it works properly. Went back to Test 2 and same problem. Tried this on two different machines running WinXP SP2 and SP3.
After the installer finishes downloading Process Explorer I get an error "The downloaded copy of Process Explorer (11.33) is not valid and can not be installed" and the installation fails.
This may be a temporary failure I guess if the installer is downloading a bad copy from the Process Explorer website, so I will keep trying.
Anyone else having this problem at the moment? I am running 64 bit version of Windows 7 by the way although I doubt that is an issue.
I'm pretty sure the problem is Process Explorer's version - MS updated it to 12.04.
IIRC, both 11.33 and 12.04 have the same download link, but 12.04 has a different md5 than 11.33 so the installer thinks the download failed.
Other than rebuilding the entire Process Explorer Portable installer, there's not much you can do.
"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
You're right, that is the problem - well, actually, it's version 12.03 the one which the installer downloads.
So you can wait for the author to update "ProcessExplorer\App\AppInfo\installer.ini", or even try to modify the 'DownloadMD5=595a29aa50f10f5c4740536eae0e95af' line while downloading, i don't really know if it will work.
But why to do that? I mean, I don't know if you realized that, although installer gives you an error message, all the portable special files have been created. So now all you have to do is download a normal version of Process Explorer (ProcessExplorer.zip) and unpack it in "ProcessExplorer\App\ProcessExplorer\"; and if you're going to do so, I recommend you to search for Process Explorer 11.33 - I have been working with it for more than a year and think it works perfectly, and I have read that 12.xx versions don't allow you to access some Windows 'protected' processes. If you can't find process explorer 11.33 I will be glad to help you but I don't actually know if i'm allowed to put any link or mail adress here.
Hope to help.
Had the same error. I'm also using Windows7 x64.
As a non-programming user, I used to use this just in the form it was downloaded, thinking that the standalone was portable (in the PA.c sense)
Is this just bringing it to PA specs or did it leave something behind before?
“There is a computer disease that anybody who works with computers knows about. It's a very serious disease and it interferes completely with the work. The trouble with computers is that you 'play' with them!”Richard Feynman
It leaves settings and the information if you agreed with the EULA behind in the registry.
"Der Klügere gibt nach, deshalb regieren Dumme die Welt."
Didn't know that, thanks
“There is a computer disease that anybody who works with computers knows about. It's a very serious disease and it interferes completely with the work. The trouble with computers is that you 'play' with them!”Richard Feynman
“There is a computer disease that anybody who works with computers knows about. It's a very serious disease and it interferes completely with the work. The trouble with computers is that you 'play' with them!”Richard Feynman
may I have the launcher source code so I can rebuild it so it will have the correct icon and description when added to the menu? Thanks.
/s/ When life turns your dreams to dust, vacuum
You only need the launcher. Just install the package and put in a new version of PE manually.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
What I wanted to was to make the icon be correct and have the description "PE" versus "Launcher".
EDIT: Ah, my apologies, you mentioned using PAL... I haven't been keeping up with all the threads here. I now understand and have used PAL to redo the launcher with the AppName and AppIcon so it will appear in the menu correctly. Again, sorry to bother you with my thickheadedness.
/s/ When life turns your dreams to dust, vacuum
Very curious what I found. Portable launcher hungs up when running on a virtual machine (well, I only tried on WinXP SP2 & WinXP SP3), I mean, no window appears an you can see PortableProcessExplorer.exe eating 100% from CPU (in my case -obviously- 50%, because having Core2Duo). I suppose I'm getting same error Chris Morgan and other Wine users get. My programming knowledgement is too poor to suggest for a reason, anyway I want to congratulate you for this great result - well, I'm using ProcessExplorerPortable day n nite and think it works truly portable, not as my two past attempts to portablize =(. Keep working as nice as you're donig!
Last of all, I'd like to ask every posting P.E.P. user to take a minute to READ OTHER USERS COMMENTS BEFORE POSTING, haven't you thing that maybe your question is already answered? I'm refering to all that people who still asking what to do when they receive the donload error. I insist: download non-portable Process Explorer an place files on App\Process Explorer\ path under files created by teh portable installer. Hope to help. Respect.
Download link is down.
PortableApps.com Advocate
Use prapper's https://portableapps.com/node/20643
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world