ProcessInfo 1.3 is released. The changes in this release are:

• CPU usage is added to TProcessItem.
• Is64Bit is added to TProcessItem.
• IsAccessible is added to TProcessItem.
• Setting thread priority is added to TThreadItem.
• Setting process base priority class is added to TProcessItem.

To download ProcessInfo 1.3, please go to ProcessInfo page.

Q1: How can we find a module which is running a specific thread, giving a thread ID:

A: First of all, Threads are not assigned to modules, they are assigned to processes. You can find a process which is running the thread, by searching in the list of threads owned by each running process. Here is a sample code:

function FindProcessByThreadID(ID: Cardinal): TProcessItem;
var
  ProcessInfo : TProcessInfo;
  AProcess : TProcessItem;
begin
  Result := nil;
  ProcessInfo := TProcessInfo.Create(nil);
  try
    for AProcess in ProcessInfo.RunningProcesses do
    begin
      if Assigned(AProcess.Threads.FindByID(ID)) then
      begin
        Result := AProcess;
        Exit;
      end;
    end;
  finally
    ProcessInfo.Free;
  end;
end;

FindProcessByThreadID iterates over all running processes, and checks which of them has a thread with the given ID. If a process owns a thread with that ID, it will return that process as a TProcessItem object.

Once you have the process object, you can get more information about the process or the specific thread, or you can kill the process, or suspend the thread. For example:

var
  Process : TProcessItem;
begin
  Process := FindProcessByThreadID(StrToInt(3444));
  if Assigned(Process) then
    ShowMessage(Process.FullPath);
end;

The above code looks for a thread with its ID = 3444, and if it is found, it provides full path of the EXE file for that process.

Q2: How can we get memory consumption for a given process?

A: You can read memory info for a given process using TProcessItem.MemoryInfo. It provides different info about the memory the process is consuming. Here is an example for reading memory info of Google Chrome process while it is running :

var
  ProcessInfo : TProcessInfo;
  AProcess : TProcessItem;
begin
  ProcessInfo := TProcessInfo.Create(nil);
  try
    AProcess := ProcessInfo.RunningProcesses.FindByName('Chrome.exe');
    if Assigned(AProcess) then
      ShowMessage(Format('WorkingSet Size = %d, Peak WorkingSet Size = %d',
                         [AProcess.MemoryInfo.WorkingSetSize,
                          AProcess.MemoryInfo.PeakWorkingSetSize]));
  finally
    ProcessInfo.Free;
  end;
end;

First we search for Chrome.exe process among running processes. Once the process is found, we read its current working set size, and pick working set size through MemoryInfo property, and show them in a message box. The values returned are in Bytes.

Q3: How can we get process base priority class or change it?

A: You can access base priority class for a given process or modify it (added in version 1.3), using TProcessItem.

PriorityClassBase. Be careful, adjusting a base priority class of a given process inappropriately might make other processes unresponsive! Here is a example code:

var
  ProcessInfo : TProcessInfo;
  AProcess : TProcessItem;
begin
  ProcessInfo := TProcessInfo.Create(nil);
  try
    AProcess := ProcessInfo.RunningProcesses.FindByName('firefox.exe');
    if Assigned(AProcess) then
      AProcess.PriorityClassBase := BELOW_NORMAL_PRIORITY_CLASS;
  finally
    ProcessInfo.Free;
  end;
end;

You can also change each priority of  each thread within a process by setting BasePriority property of that TThreadItem instace.

Q4: How can I check if a process is 64-bit?

A: You can check this by reading TProcessItem.Is64Bits property.

Q5: How can I get CPU usage for a given process?

A: You can get CPU usage by reading TProcessItem.CPUUsage property.

I hope these few answers and sample source codes can help you use Process Info. For other examples of using Process Info, please refer to this post: How to use TProcessInfo

If there is any question regarding using Process Info, or anything about Delphi that you think worth being mentioned in Tips & Tricks section of this website, please contact me, and let me know about it.

Have Fun!

You might have thought it is your ISP, or maybe Iranian filtering system, or maybe your browser, which are causing the problem, because other visitors are using the website with no such problems, and nobody has reported such problems. Well, if you thought that way, you are wrong!

It was some months (or maybe a year) ago that I noticed I cannot log into Embarcadero forums (web interface for their newsgroups). It was telling me that my username\password was not valid! I retried my username\password several times, and even tried to make it to email me my password, but no success! Eventually I decided to create a new username, and tell them about my problem in the forum, but when I was creating the new account, I noticed that Iran is not in Countries list, and I have to choose another country if I want to create an account in their website. It was there that I found out they deleted my previous forum ID without any notification just because Iran was chosen as my country!

Days passed and April 2010 came, I noticed that some Iranian Delphi developers were reporting problems about accessing EDN (Embarcadero Developers Network). EDN provides some articles, news reports, and white papers about Embarcadero products for software developers. I thought it must have been some ISP problems, but since I wasn’t sure, I created a topic in Embarcadero forums, and asked if EDN is down. Some users mentioned they have no problem accessing it in Europe, and later on, my topic got deleted from their forum, and I received an email from one of Embarcadero employees that this is due to their respected company’s policies in complying with US embargo, and I should keep it as a confidential note!

Now it’s been some days (maybe 1 or 2 weeks) that I found out accessing weblogs belonging to Delphi team members on Embarcadero website, and also documents wiki website (online version of Delphi documentation) is not possible from Iran.

So, if you use any of Embarcadero products (either buying it legally or not) and you travel to Iran for a visit or live in Iran, you are not allowed to check their website, their weblogs, or their online documentations, put aside downloading trial versions or updates from their website! OK, they say it is so to comply with US embargo against Iran, but it is weird, as far as I know, when someone does something nice and according to law, they must be usually proud of it, but Embarcadero is not (!!) because they do not like you to know that they put such restrictions on some people; they do not bother redirecting you to a page saying this content is not available to you due to US embargo. They rather you think it is a server or Internet connection issue, not an organized restriction imposed by the company. That’s why you don’t see any explanation from them, or you do not receive any notifications when your accounts are removed from their website, or your post gets deleted when you ask them about it in their forums.

It is also interesting to know why they are restricting access to such contents as online help or their employees weblogs? Because if they are following US laws, then banning product downloads from Iranian IP ranges should be enough. Why banning access to developers’ weblogs or online help documentations?! Companies like Google, Oracle, or Yahoo impose restrictions on downloading their products to Iranians too; for example you cannot directly download Google Chrome, or Yahoo Messenger from Iran, but they do not restrict their employees weblogs, or announcements for new coming products. Actually it seems Embarcadero likes ambiguity, as they expressed this interest in their published roadmap which was more confusing than clarifying. You can read about it more here.

Maybe the reason Embarcadero decided to ban their website content on Iranians was popularity of Delphi in Iran, and they thought making such restrictions make Iranian people feel the pressure more, and as you might know, US government believes such stupid pressures will eventually lead to people uprising in Iran, and making the country to agree with US demands! I know you might say nowadays Delphi’s popularity is not as before, and Visual Studio and .NET are currently the most popular development tools there, but so far Microsoft hasn’t imposed so called US embargo on Iran that way; that is they do not sell their products in Iran, but they haven’t banned MSDN or their download pages, or their online services for Iranians yet. So if they are supposed to put pressure, why not restricting Microsoft contents in Iran? Maybe Microsoft is kept for later stages of pressure on Iranian people, or maybe they are afraid if they ban very popular websites or tools, the result might get reversed, and people might feel more enmity toward US government.

BTW, If you are a software developer in Iran, you already know how to nullify so-called US sanctions; so I didn’t go for explaining how to do so!

I have a lot to say about US embargo against Iran, that I think I should write about in another post some other time.

Have Fun!

P.S. 1. Today (May 26, 2010) I tried to read Craig Stuntz’s blog post on TeamB website, and this site makes the same restrictions on Iranians as official EDN website. So you can add TeamB to the list too.

P.S.2. Today (June 18, 2010) I found out Embarcadero forums are added to the restricted websites too. If Embarcadero had took developing their products as seriously as they took banning Iranian users, they would have probably had better products by far!

I don’t know if we can call it a roadmap or not. It does not give any time schedule or estimation on when each mentioned feature might be available (except a rough estimation for 64-bit compiler preview availability in the first half of 2011). To me, the published roadmap does not clear any ambiguity regarding Delphi future. It just adds more to it! Really, what was the purpose of publishing this?! Maybe just to  muffle those Delphi users who were complaining about not having any updated roadmap.

Now, let’s take a look at this so-called roadmap…

I skip those unnecessary slides which say the focus of product in future is on this or that, because as far as I know, almost all RAD development tools focus on stuff like better performance, Rich GUI, Cutting-edge data access, and so on. So to me, such pages don’t add anything to reader’s knowledge about the product.

Then in page 8, we see the the projects R&D team are working on:

• Fulcrum
• Wheelhouse
• 64-bit compiler preview
• Commodore
• Chromium

According to other pages in the roadmap, and what we already heard from Delphi team, there are teams working on these projects in parallel. This is good that they are working on these projects in parallel, but that adds some more ambiguity, because you don’t know what features of which project will be available in each release. For example Chromium is the last project in the list, and one of the features it will focus on is documenting OTA. Since the works are done in parallel, then they might finish documenting OTA while the main focus is on the Fulcrum or Wheelhouse or Commodore. So you might see OTA documentation released with one of the earlier projects. It can be taken the other way too, you might see a feature in Fulcrum or Wheelhouse projects not being ready at the time they are supposed to be, and postponed to Commodore or Chromium, or post-chromium release!

So you have no time frame, and no info when each mentioned feature is supposed to be released. Your desired feature might come into product in a few months to a couple of years (maybe even more, who knows?). I don’t know why Embarcadero likes to be so ambiguous!

Project Fulcrum

The main focus right now is on project Fulcrum. It is said that Fulcrum is currently in private Beta phase, and will be available as public Beta some time soon, and will probably go Final in summer. According to the roadmap, the main theme of Fulcrum is building cross-platform applications. The old roadmap was mentioning Windows, Linux, and Mac OS X, but the new roadmap only talks about Windows and Mac OS X. There is no Linux. Linux support is postponed to Wheelhouse project. It is not clear if at least building console applications in Linux is supported in Fulcrum. But it is clear that even Mac OS X support is about client applications in Fulcrum, and you can’t use technologies like DataSnap servers in Mac OS X until project Wheelhouse is released. So again Embarcadero is proving that they are not good at setting  project goals, and estimating projects. As we saw with 64-bit compiler, Linux support will not be available on time, and is going to be postponed. It might be available very soon after Fulcrum release, or it might go the same path 64-bit compiler went, and be postponed for a couple of years. No one knows.

Beside its main theme, Fulcrum is supposed to bring some other features to RAD Studio. First of all, it is mentioned it will provide remote debugging for Mac OS X. I don’t know why is this mentioned here because when they mention they are going to target Mac OS X platform, then they either provide a Mac-based IDE, or a Windows-based IDE cross-compiling for Mac OS X. They took the second approach, and with that, it is obvious that they should provide a remote debugging mechanism. It is a must-have feature for a cross-compiling tool, not a subsidiary feature.

Then we have “Cross-platform VCL-like component library. According to Michael Rozlog in his interview with Jim McKeeth for Delphi Podcast #37, this cross-platform component library is a continuation of CLX library which was a wrapper for Qt GUI framework back in Delphi 6 and Delphi 7. There are no further details about this CLX based component framework except that again according to Michael Rozlog, most of old CLX based Delphi applications should be able to upgrade to this new framework easily, putting aside Unicode migration which is a different story.

The other feature which is supposed to be available in project Fulcrum is better integration with version control software, specially Subversion. It seems OTA is extended to provide a better version control support, and a SVN integration extension will be published with RAD Studio using the new OTA features. According to Nick Hodges in Delphi Podcast #40, this SVN extension is based on open-source DelphiSVN project, and will be published as an open-source tool. The good thing about this new feature is that it will be integrated into History tab of code editor. It seems cool!

Another feature in project Fulcrum is supporting UML Sequence diagrams. That’s good, but well it’s been a while that I use Model Maker for modeling. I do admit that modeling support in RAD Studio 2010 is also very cool.

Next feature is Automatic unit test generation. This is another unclear feature. What is this feature supposed to do?  Automatic unit test generation is already integrated into Delphi using DUnit. What extra stuff is this feature supposed to bring to RAD Studio?

Again another unclear feature is “RESTful Server creation”. This is already provided in RAD Studio 2010, and it is not clear what other stuff regarding to RESTful servers are going to come with project Fulcrum. I think Embarcadero should had gone into more details with these two features in their roadmap.

And the last feature mentioned in project Fulcrum is supporting cloud computing by providing Microsoft Azure integration, which is a nice addition to project Fulcrum.

Project Wheelhouse

Project Wheelhouse is supposed to bring full Linux support to RAD Studio. It will also complete Mac OS X support by providing server side support on both Linux and Mac OS X along with Windows.

64-bit Compiler Preview

64-bit support will not come to RAD Studio sooner than the first half of 2011. Even at that time, you will have a command-line only compiler preview. It is not clear how this compiler preview is going to be shipped; Are Embarcadero going to release a new Delphi version in 1st half of 2011? Or are they supposed to release this compiler preview as an update? As far as I know, they do not ship new features in updates, and usually RAD Studio is released once per year.

Project Commodore

I’m not going to spend that much time on project Commodore and Chromium, because they seem far away, and probably will see many changes in future. Project Commodore is supposed to bring full 64-bit compiler support. If you follow Delphi news, then you probably know project Commodore from previous Delphi roadmaps. It’s been a couple of years that Commodore is there on the roadmap. According to previous roadmaps, we should have had it in 2010, but now according to the current roadmap, it is at least 1.5 to 2 years away from us.

Better multi-core support, and Delphi Parallel Library are other features being worked on in project Commodore. I hope we see DPL sooner; because within 2 years a parallel library wouldn’t be considered as an advantage, but a must-have feature. So it wouldn’t be an advertising point for Embarcadero in 2012 to say, hey we also have this cool parallel library in our product!

Social Networking Integration is another feature for Commodore. Again this is a cool feature if delivered on time, otherwise it wouldn’t make any advantage for Delphi.

And the last feature mentioned for project Commodore is  Better Documentation. I hope they don’t mean people should wait at least 2 years to have better documentation in RAD Studio! It seems this is one of those features that we probably will see sooner, because as we saw in RAD Studio 2010 documentation, the documentation team is working hard to provide better documents in each release, and even with help updates.

Project Chromium

Well, this one looks so far away. This project is supposed to enable Delphi target other hardware platforms rather than Intel X86. Specially mobile platforms. It is also supposed to provide better support for other natural inputs (beside gesture and touch) like voice, video motion, and location (probably supporting GPS in mobile devices). These stuff are cool, but it is not clear or even estimated when such things are supposed to be provided.

Some other features in project Chromium are already being worked on, and we see their progress in each release; like improving look & feel of VCL controls, and IDE, or more integration with database tools. I also expect OTA documentation to be available sooner than other features in this project, and I guess we will see it in the next release or the release after next release (This is just an assumption).

DataSnap (Adaptive) Application Server, and Extended RIA Approach are also mentioned in Project Chromium, but again they lack any detailed specifications.

So it was my take on the newly published document, called roadmap, by Embarcadero. If you want to make any estimated plan for your carrier with Delphi, this document is, to me, quiet useless, and doesn’t really give you any insight.

Entry-level SKU

As you might know, one of the recent hot debates in Delphi community was around Embarcadero providing a free or cheap entry-level SKU for RAD Studio. Michael Rozlog mentioned in his Delphi Podcast #37 that they are working on it, and probably we will see that in next major release which is project Fulcrum.

But according to Nick Hodges in Delphi Podcast #40, they haven’t made their mind yet, and it is not still clear how this entry-level SKU would be. But something is clear; a free version is not on the table anymore. They are just working on a cheap entry-level SKU which its specifications are still unclear. So we won’t see free Delphi anymore!

I hope at least they provide the command-line compiler free, and make it available in all three major platforms they are going to support (Windows, Linux, Mac OS X). This way hobbyists and students could use a free editor like NotePad++ and write Delphi code on their preferred platform for free.

Regards

ProcessInfo 1.2 is released. The changes in this release are:

• SuspendThread, ResumeThread, TerminateThread methods are added to TThreadItem class. Now you can pause/resume/terminate any running thread in a given process.
• TProcessInfo.Active and TAppInfo.Active are published properties, and can be set in design mode.
• TProcessInfo.RunningProcesses and TAppInfo.RunningApplications automatically populate the corresponding list if UpdateList method is not called yet. This means even if you don’t activate any of these two components, or call their UpdateList method, accessing RunningProcesses or RunningApplications does not cause Access Violation.

To download ProcessInfo 1.2, please go to ProcessInfo page.

Regards.

This toolbar provides a nice search box which is able to filter components in the palette based on the search phrase. This toolbar is disabled by default, and is shown when Classic Layout is selected. Here you can see a snapshot of Classic Layout in RAD Studio 2010:

A few weeks ago while I was working with Delphi 2010, I noticed a delay when switching from code view to form designer. The delay was there not only in the complex forms, but also in simple empty forms! It was not a big delay (about 1 second), but since I had to switch between code and form designer view many times, it was really annoying, so I decided to investigate it and find out what is causing this delay.

At first I got suspected to CnPack toolbars in form designer and code view, so I disabled them, but it had no effect on the delay!  Then I went for SysInternals Process Monitor to monitor RAD Studio while switching from code view to form designer. There were many Registry activities regarding to component toolbar. At that time I was thinking about standard Tool Palette in RAD Studio 2010, not the classic component toolbar, because I was not using classic layout.

I tried to hide Tool Palette to see if it fixes the delay, but it didn’t! So I decided to disable its IDE package and see if it fixes the issue. While I was looking into the list of IDE packages in Registry, I found Component Toolbar Package, and I thought this is the package corresponding to Tool Palette. So I removed it from the list of known IDE packages, and restarted RAD Studio 2010; the Tool Palette was still there, BUT the switching delay was gone!

I was wondering if Component Toolbar was not related

to Tool Palette, then what was it related to?! Suddenly I remembered the new classic component toolbar, and switched to Classic Layout. Yes, it was the new classic component toolbar which was using Component Toolbar Package!

Since I don’t use classic view, I simply disabled this IDE package to have a faster switch time from code view to form designer. But still it is weird why this toolbar is being update even when it is not being visible, and why it is making switching from code view to form designer slower. This is definitely a bug in RAD Studio 2010.

How to disable an IDE package:

Here is how you can disable Component Toolbar Package from Registry:

1- Go to HKEY_CURRENT_USER\Software\CodeGear\BDS\7.0\Known IDE Packages.

2- Make a backup by right-clicking on “Known IDE Packages” key, and selecting  Export.

3- Find “$(BDS)\bin\comptoolbar140.bpl” value in “Known IDE Packages” key, and delete it.

4- Run RAD Studio 2010.

Regards

At first I thought it is just a joke, but then I realized it isn’t It seems Chad is in trouble for his son’s custody. He’s been accused of kidnapping his own son and traveling to Bulgaria with him in 2006!

Anybody having some experiences with Delphi programming knows Chad, and his great open-source project; Indy Project.

I hope his problem is solved soon. He asked for help, and I think all Delphi developers who are using Indy have to at least spread the word, or if they can, help him financially to get out of this trouble.

I released a new version of ProcessInfo. In this release I added these features:

• Enumerators are added for Windows, Threads, Modules, and Processes; Now you can use for-in statements in D2007 and above for iterating on running processes list, or modules\threads\windows of a given process.
• TProcessItem.UserName is added; This property returns domain name\user name which is running the process.
• TProocessInfo.AdjustDebugPrivilage is added; This method is called automatically.
  TThreadItem.ToString & TProcessItem.ToString are added; TThreadItem.ToString returns ThreadID. TProcess.ToString returns process EXE name.
• Now supports Delphi 7,2007,2009, 2010; Some conditional compiler directives are added so that it can be used in D7, 2007, 2009, and 2010. I tested it in D7, 2009, and 2010. It should work in D2007 too.

To download ProcessInfo 1.1, please go to ProcessInfo page.

Regards.

I thought maybe it is a good idea to talk about these components and some of their usages by providing some sample source codes. So I will start with TProcessInfo.

Updating running processes list automatically

TProcessInfo has an internal timer which can update processes list automatically. This timer is controlled by Active, and UpdateInterval properties. Active activates the internal timer, and UpdateInterval specifies update interval. The default value for UpdateInterval is 1000 (1 second).

To update the list manually, and not using the internal timer, you can call UpdateList method.

OnBeforeUpdate and OnAfterUpdate

TProcessInfo has two events. They both are invoked when UpdateList is called, either automatically by internal timer or manually by the programmer.

OnBeforeUpdate is invoked just before updating the list. It has a Cancel parameter which lets you to cancel updating. OnAfterUpdate is invoked when the list is updated. So if you have a control (e.g. a list view) that should show processes list, you can write its updating code in the event-handler of OnAfterUpdate.

Finding a running process

You can iterate over all running processes to find a specific process with specific characteristics, or use FindByID, and FindByName methods to find a process by its Process ID or Process Name:

var
  Process : TProcessItem;
begin
  Process := ProcessInfo1.RunningProcesses.FindByID(1234);
  if not Assigned(Process) then
    ShowMessage('No process found');
end;

Finding a process by its Process ID.

var
  Process : TProcessItem;
begin
  Process := ProcessInfo1.RunningProcesses.FindByName('Project3.exe');
  if not Assigned(Process) then
    ShowMessage('No process found');
end;

Finding a process by its Process Name.

var
  I: Integer;
  MemSize,
  MaxMemSize : Cardinal;
  ProcessName : string;
begin
  MaxMemSize := 0;
  for I := 0 to ProcessInfo1.RunningProcesses.Count - 1 do
  begin
    MemSize := ProcessInfo1.RunningProcesses[i].MemoryInfo.WorkingSetSize;
    if MemSize > MaxMemSize then
    begin
      MaxMemSize := MemSize;
      ProcessName := ProcessInfo1.RunningProcesses[i].ExeFile;
    end;
  end;
  ShowMessage(ProcessName + ‘uses more memory than other processes.’);
end; 

Finding the process which consumes more memory than others.

Terminating a running process

To terminate a running process, you should first find it in the list of running processes, and then call its TerminateProcess method:

 var
  Process : TProcessItem;
begin
  Process := ProcessInfo1.RunningProcesses.FindByName('notepad.exe');
  if Assigned(Process) then
    Process.TerminateProcess;
end;

Retrieving full path of a process

 var
  Process : TProcessItem;
begin
  Process := ProcessInfo1.RunningProcesses.FindByName('notepad.exe');
  if Assigned(Process) then
    ShowMessage(Process.FullPath);
end;

Listing modules which a process loaded

 var
  Process : TProcessItem;
  I: Integer;
begin
  Process := ProcessInfo1.RunningProcesses.FindByName('Project1.exe');
  if  Assigned(Process) then
  begin
    for I := 0 to Process.Modules.Count - 1 do
      Memo1.Lines.Add(Format('%d  : %s',[Process.Modules[i].BaseAddress,
                                         Process.Modules[i].ModuleName]));
  end;
end;

You can access other information about a process (e.g. Threads list, threads count, memory consumption, and so on) in the same way.
TAppInfo works very similar to TProcessInfo. I will try to explain it more with some examples in another article.

Process Info is a free Delphi component package containing two components:

• TProcessInfo
• TAppInfo

TProcessInfo provides a list of running processes. TAppInfo provides a list running applications (similar to Application tab in Windows Task Manager). Both components can update their list frequently based on the value of Interval property.

TProcessInfo returns a collection of TProcessItem objects. Each instance of TProcessItem provides these information and actions for the process:

• Creation time
• Kernel time
• User time
• EXE file name
• Full image path
• Process ID
• Parent process ID
• Terminate process
• Threads count
• UserName
• Modules list (TModuleItem)
  • Base address
  • Base size
  • Handle
  • Load count
  • Module ID
  • Module path
  • ProcessID
• Threads list (TThreadItem)
  • Base priority
  • Parent process ID
  • Resume thread
  • Suspend thread
  • Terminate thread
  • Thread ID
• Memory info (TMemoryInfo)
  • Page Fault Count
  • Peak Working Set Size
  • Working Set Size
  • Quota Peak Paged Pool Usage
  • Quota Paged Pool Usage
  • Quota Peak Non-paged Pool Usage
  • Quota Non-paged Pool Usage
  • Page file Usage
  • Peak Page file Usage
• Base priority

TAppInfo returns a collection of TWindowItem. Each instance of TWindowItem provides these information for the window:

• Window caption
• Application path
• Process ID
• Window handle
• Window class

A simple demo is also included which shows basic functionalities of TProcessInfo, and TAppInfo by creating a simple task manager. Demo is tested on Delphi 7, Delphi 2009, and Delphi 2010.

Process Info is published under the Creative Commons Attribution 3.0 Unported License.

Update:

• 2010/07/26: Version 1.3
• 2010/01/13: Version 1.2
• 2009/10/17: Version 1.1

Download:

Download Process Info (Source + Demo)