Jump to content

Process Explorer v10/v11 on 9x?


osRe

Recommended Posts

Anyone got Process Explorer >9.xx to work on plain 98SE? I tried 10.20, 11.00, 11.11, 11.13, 11.21, 11.33, maybe some others, none work.

The initial post in "Last Versions of Software for Windows 98SE" thread says v11.11 is the latest to work. The changelog mentions for v11.13: "Fixes compatibility with Windows 9x and NT4". The CHM file for various v11.xx says 9x is supported. Yet, no go.

Some newer 11.xx do nothing, some show the EULA dialog and afterwards a tray icon + taskbar button and nothing further happens, or the computer gets stuck(/ish).

Edited by shae
Link to comment
Share on other sites


Anyone got Process Explorer >9.xx to work on plain 98SE? I tried 10.20, 11.00, 11.11, 11.13, 11.21, 11.33, maybe some others, none work.

The initial post in "Last Versions of Software for Windows 98SE" thread says v11.11 is the latest to work. The changelog mentions for v11.13: "Fixes compatibility with Windows 9x and NT4". The CHM file for various v11.xx says 9x is supported. Yet, no go.

Some newer 11.xx do nothing, some show the EULA dialog and afterwards a tray icon + taskbar button and nothing further happens, or the computer gets stuck(/ish).

Did you try "Process Viewer" or "WinTop" (Win95 Kernel PowerToys)? I've no problems on ME. The Process Explorer works with KernelEX up to 11.33 and without KEX up to version 11.11 for me.

Link to comment
Share on other sites

Perhaps you are seeing problems related to this report:

Over on the RegCompact for Win9x I have noted a possible bug in Process Explorer which I don't recall seeing before. Perhaps some others might try to reproduce it?

You will need to also have IrfanView and RegCompact present with the former, or, the former *and* the latter already running to experience the bug.

These were the result of my testing ...

; ProcExp version that never crashed ...

2005-08-22 - 13:29 ... 1,238,544 ... Procexp.exe v09.25

; ProcExp versions that crashed at launch when both IrfanView and RegCompact were already open ...

2006-02-09 - 13:53 ... 1,443,392 ... Procexp.exe v10.04

2006-02-22 - 15:31 ... 1,455,680 ... Procexp.exe v10.06

2006-05-10 - 16:28 ... 3,266,112 ... Procexp.exe v10.10

2006-05-11 - 10:38 ... 3,266,112 ... Procexp.exe v10.11

2006-07-12 - 12:59 ... 3,278,400 ... Procexp.exe v10.20

2006-11-01 - 14:07 ... 3,623,736 ... Procexp.exe v10.21

; ProcExp versions that crashed at launch when IrfanView was already open ...

2007-09-01 - 08:16 ... 3,585,408 ... Procexp.exe v11.00

2007-09-09 - 12:11 ... 3,589,160 ... Procexp.exe v11.01

2007-09-14 - 13:29 ... 3,589,160 ... Procexp.exe v11.02

2007-10-25 - 16:12 ... 3,609,640 ... Procexp.exe v11.03

2007-11-05 - 07:54 ... 3,564,584 ... Procexp.exe v11.04

2008-02-26 - 10:49 ... 3,654,696 ... Procexp.exe v11.10

2008-02-27 - 13:05 ... 3,654,696 ... Procexp.exe v11.11

So in other words, with just IrfanView running and then launching ProcExp v11.0 to 11.11 the bug occurs and ProcExp crashes.

For ProcExp versions 10.04 to 10.21 both IrfanView and RegCompact needed to be open to cause the crash. There may be more complex combinations that cause this crash as well.

9.25 now seems to be the last known stable version of Process Explorer on 98se.

Link to comment
Share on other sites

I too can't run 10 or 11 properly. If I recall correctly 11 won't run at all and first run of v10 will not fully initialize, hanging in the process list without creating a window and not killable by another utility, launching a second instance of it will run normally however. Not trouble at all with v9. Probably some bad interaction with one or another always on background task I run on my system.

There aren't any must have new features in 10 or 11 over 9 anyway if I am not mistaken.

Edited by loblo
Link to comment
Share on other sites

I haven't installed IrfanView and RegCompact.

FYI, that thing mentioning IrfanView and RegCompact was just so that others could try to reproduce the problem. It first popped up when I was testing RegCompact and getting screenshots ( see here ).

Most likely there are other combinations of running software that will cause ProcExp to crash as it starts up. That particular combination mentioned above was routinely reproducible but I am sure there are others.

What happened is that Mark ( the author ) was recompiling the System Internals applications and was in the process of switching over to VS2008 ( see here ) which killed off Win9x for good. Process Explorer was at v11.12 when it became official but it is clear from looking at the increasing filesizes above ( see v10.10 ) that he was already in the process changing over around the summer of 2006 when Microsoft assimilated the company, adding new #includes which showed up in the compiled EXE's as Microsoft EULA's and other stuff. The large bloat is partially from that and also from the fact that he was creating dual 32-64 bit hybrids ( a good thing ). There was also some GUI tweaks occurring most noticeable in FileMon and RegMon between versions 6 and 7 which caused some problems. So there are at least three or four influences in play.

Interestingly, some people apparently have no problems with ProcExp v10.xx in Win9x. So it may be case-by-case dependent on other variables we have yet to isolate.

Link to comment
Share on other sites

Did you try "Process Viewer" or "WinTop" (Win95 Kernel PowerToys)?
I use WinTop for quickly seeing what takes up CPU. But both, including ProcExp v9, don't have certain features that are in ProcExp v10+.
Perhaps you are seeing problems related to this report:
Might be. Although I didn't have these apps running, or anything much else really.
launching a second instance of it will run normally however.
I'll try that.
There aren't any must have new features in 10 or 11 over 9 anyway if I am not mistaken.
For me it's thread details.
Link to comment
Share on other sites

I found in the ProcExp forum a suggestion to remove HKCU\Software\Sysinternals\Process Explorer. Now I can run v11.11 (but not newer v11s I tried). But alas, no thread details! I guess it's NT only. :-/

Edited by shae
Link to comment
Share on other sites

Thanks, ATM does seem to give a few more details. But what would really be nice is being able to see thread start addresses:

uLKb2.png

Any idea if ProcExp may depend for thread info on external libraries like dbghelp? Perhaps it's possible to upgrade that.

Link to comment
Share on other sites

I've just downloaded 11.33 from FileHippo and, surprise, surprise, it seems to be be running fine (KernelEx in default mode mandatory) but unfortunately all those thread features (and others) aren't available, I guess they are only for NT OSes.

It's indeed using dbghelp.dll and I tried it using version 5.1.2600.2180 and 6.2.13.1 of this dll btw.

Edited by loblo
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...