Is the problem restricted to Process Explorer? (I assume that's Process Explorer.)
I'd say it's either a bug in Process Explorer on XP, or some hardware/driver is failing. (Searching Microsoft's KBs for that error message, it's mentioned in an article about the OS being unable to read data from an optical drive or HDD due to various reasons.)
when the icon is not shown it seems limited to the FIRST start of DOpus. Exiting DOpus from the taskbar icon and restarting it will show the icon. Loggin off and on again does not affect the icon showing. It seems to be an issue of the very first start.
Strange, but since processes don't really have icons (only windows have icons; there is no API that a process calls to say "show this icon in the process list"), and it's Process Explorer that would be working out the process's EXE path and loading the icon from the EXE file to show in the list, I think it must be Process Explorer that is going wrong somehow.
Nothing about the icon changed between versions, but if replacing the exe solved it then I bet the issue was to do with how Windows caches icons for files (which has a bunch of bugs/quirks that crop up now & then in various places).
Is the path error message still there? If the icon was to do with icon-caching then I'd expect it to be unrelated to the error message Process Explorer was showing in place of the path (or command line or whatever is meant to be in the tooltip.)
It's back, I mean the icon is gone again . Seems that installing just solves the issue one-time only, i.e. after first reboot.
I was able to circumvent this, by enabling "Launch Directory Opus automatically on system startup". Then the icon just shows fine and I do not have the call-tree "dopusrt.exe -> dopus.exe"
Works fine here, on an XP machine setup like in your original screenshot:
If you want to get to the bottom of it, you'll probably have to ask at the SysInternals forums to see if anyone there has seen something similar, since Process Explorer is where the actual problem is occurring and it's not affecting any other part of the OS or happening on other people's machines.
Opus doesn't tell Windows "here is my icon"; the icon is just part of the dopus.exe file, and it's up to Process Explorer (probably via the Windows shell icon APIs) to obtain the icon out of the exe file.
[quote="leo"]
If you want to get to the bottom of it, you'll probably have to ask at the SysInternals forums to see if anyone there has seen something similar, since Process Explorer is where the actual problem is occurring and it's not affecting any other part of the OS or happening on other people's machines.
Opus doesn't tell Windows "here is my icon"; the icon is just part of the dopus.exe file, and it's up to Process Explorer (probably via the Windows shell icon APIs) to obtain the icon out of the exe file.[/quote]