I'll post another exciting follow-up then. On a Mac, if you’re using a one-button mouse, you can perform the equivalent of a right-click by holding down the Control key on your keyboard and clicking your mouse button. I'm going to try a thorough uninstall/reinstall. With the mouse oriented as you’d usually hold it, press the rightmost button (or clickable area) on the surface of the mouse. Right click on the USB-to-Serial Comm Port (COM3). I'm pretty sure it's installed by default (too lazy to check). HCS12C128 Board, USB-to-Serial port driver, and HyperTerminal. I don't use HyperTerminal either, and there must be many systems out there that also have it installed. I know it's a Microsoft component but it's one which may not be used by many people which could explain why the problem hasn't been noticed before. Temporarily disabling the HyperTerminal extension, if you haven't tried that already, may be worth a quick go in case it turns out to be that. (Imaging, annoyed that a program wouldn't crash.) Maybe it had something to do with how those utilities slowed everything down, because DOpus was displaying the context menus very sssslowly at that point. DOpus wouldn't crash at all, and it was annoying. I tried Regmon first, and then Process Monitor. Have you tried running Process Monitor to see which files or registry entries dopus.exe accesses just before the crash happens? That may provide a clue about which handler is involved. But what could it be? I'm running out of ideas, if I haven't already. I've already corresponded with the author, and he doesn't think it's DOpus at fault. (I did have context_menu_debug enabled when I checked this.) But now, in DebugView, nothing at all is showing. And I still have the crashes whenever I right click any given file. I have added each one of the foregoing CLSIDs to ignore_context_menus. Here is what appeared in DebugView when the crash would occur (I've added my own notes on what each CLSID corresponds to): In ShellExView, the only non-Microsoft shell extension entries that show are those from DOpus, and the HyperTerminal entry that is actually part of Windows.Īfter unregistering all of the shell extensions and still having crashes, I ran DebugView as advised, with context_menu_debug enabled. I noticed immediately that right clicking (seemingly) any file would make DOpus crash at least 1/4 of the time, on average.Īt this point, I've unregistered all third-party shell extensions. I did a clean install of Directory Opus 9.0.0.9 on WinXP Pro SP2. I think this dependency is the limiting factor.I've read the FAQ, and taken the steps outlined there. Not sure if it can easily be hacked in or if hterm would need to be replaced. I believe the base issue though actually exists in Google Hterm though, which seems to be responsible for the handling of the actual terminal lines.
0 Comments
Leave a Reply. |