Early versions of Process Monitor (up to version 2.8) ran on Windows 2000 SP4 with Update Rollup 1.
The two tools were combined to create Process Monitor. RegMon and its sister application Filemon were primarily created by Mark Russinovich and Bryce Cogswell, employed by NuMega Technologies and later SysInternals prior SysInternals being bought out by Microsoft in 2006. In addition it shows how applications use files and DLLs, detects some critical errors in system files and more. It also allows for filtering on specific keys, processes, process IDs, and values. Process Monitor can be used to detect failed attempts to read and write registry keys. If not, I may need to fall back too.Process Monitor monitors and records all actions attempted against the Microsoft Windows Registry. I'm hopefully optimistic that SP1 will address these issues. The last one is the most critical to me right now, but I've worked around it by manually adjusting the monitor.
My main gripes are applications die off with the "application has stopped working" dialogue (but not enough yet to be a fatal flaw for me), the performance is terrible (I upgraded to a machine which is several times as fast as the old one running XP, but with Vista it feels about the same), and a bug with color profiles (when you set a custom profile, eg for photo editing/monitor calibration, Vista resets it, and you can't get it back). I'm not "fully there" yet with Vista either, but I'm not ready to go through the process of rebuilding XP and reinstalling everything again. But for the things I really care about it is working well. The only thing I've run into that hasn't worked as expected is Media Center - it tells me it can't span monitors. I'm using Photoshop, with the image editing on one monitor and the palettes on the other.
Maybe it's a function of the video card (or driver).
0 kommentar(er)
