I have a configuration backup created on October 26. I'm reasonably confident, but not 100% certain, that this configuration backup was created with 10.2.0.0 just before I installed 10.2.0.1. In what follows, I will refer to this as the 10-26 configuration.
I have an Epson scanner, the software of which has an option Open image folder after scanning. For as long as I can remember, this has resulted in the folder into which the image was placed being opened in Opus. Yesterday I noticed that the folder containing the scanned image was opening in Explorer. After much experimentation, I have arrived at the following repeatable scenario:
[ul]Scan document
Folder opens in Explorer
Restore 10-26 configuration
Scan document
Folder opens in Opus
Backup configuration
Scan Document
Folder opens in Explorer![/ul]
Just the act of creating a configuration backup causes the folder opened by the scanner software to opened in Explorer rather than Opus.
I completely uninstalled Opus, then installed 10.2.0.1. With the installed default configuration in place, scanning a document resulted in a folder being opened in Explorer. Restoring the 10-26 configuration into this installation fixed the problem.
In all cases in which the folder is opened in Opus, the new New Tab button is displayed. Unchecking the preference to display that button causes the undesired behavior of the folder opening in Explorer. Rechecking that preference does not restore desired behavior. I have to restore the 10-26 configuration to get desired behavior back.
I use an image backup program Image for Dos from TeraByte Unlimited which also provides a program TBIView which allows an image to be mounted as a drive letter. Always before, the image has been mounted and the created drive letter has been displayed in an Opus tab. Now whenever Opus is in the state such that the scanned image folder is displayed in Explorer, the drive letter created by TBIView is also displayed in Explorer. When this happens, there is the additional symptom that my empty DVD drive becomes visible in both Computer and my Drive Buttons where empty drives are normally hidden.
Certainly the question could be asked whether this behavior is the fault of TBIView and the scanner software, but it never happened before 10.2.0.1.
May or may not be related: before 10.2.0.1, my standard Backup Location for Backup Configuration was
E:\some_custom_path_of_mine.
After 10.2.0.1, I did a couple backups. When I couldn't find them, I realized that they had gone into
C:\some_custom_path_of_mine.
So it looks to me as though something happened in 10.2.0.1 so that the drive letter of the Backup Location path decided to revert to the system drive letter.
I also put backups in a location not on C:, but they are still going there. Regardless, it doesn't seem like just creating a backup should change behavior wherever the backup goes.
I suspect all these things are just coincidences as doing a backup does not modify Explorer Replacement settings.
Have the actual Explorer Replacement settings in Preferences changed?
Make sure you have rebooted after installing a new Opus version, too, since old DLLs still being loaded into other processes can cause Explorer Replacement to fail and open Explorer instead of Opus sometimes.
I'm sure rebooting had occurred, but it certainly has now because the PC was powered off overnight, but the behavior remains.
I wouldn't believe it either if I didn't see it, but I've just demonstrated the behavior again. After the PC was powered off overnight, the first attempt at performing the previously described actions resulted in Opus being opened.
Create a configuration backup and perform the actions again, Explorer is opened.
As far as I can tell, Explorer Replacement settings have not changed.
But here's something else. With things working correctly, changing the preference to Replace Explorer for all folders caused the opening Explorer behavior to return.
This gave me an idea. With things working correctly, I disabled the display of icons in details mode (just arbitrarily picking some seemingly unrelated preference). Explorer started to open again. It looks like making any configuration change causes the opening Explorer behavior.
As strange as all this seems, don't forget that a default installation of 10.2.0.1 experiences the Explorer opening behavior. This may be a simpler route of investigation than all the other strange things described.
It has occurred to me to wonder if this behavior is actually due specifically to the two actions I've described or if it would happen in the case of any unrelated application opening a folder. At the moment, I can't think of any other application I have that would do that.
This is not completely a 10.2.0.1 issue though it's more of a problem on that release.
I uninstalled, then installed 10.2.0.0 from scratch. With it in its default configuration, I ran the scanner and Explorer opened. Then (I'm not really sure why) I created a configuration backup. After that running the scanner opened Opus. Once again just creating a backup resulted in changed behavior albeit better behavior this time. Unfortunately the same scenario didn't "fix" 10.2.0.1.
The only way I can find to "fix" 10.2.0.1 is to restore a configuration created in 10.2.0.0 when it was working correctly, but that leaves 10.2.0.1 in a state such that I can't make any changes to it's preferences without making it misbehave again.
I could believe that this issue is my scanner software's fault, but why would it only happen some of the time if that's the case.
For now, I reinstalled 10.2.0.0 over 10.2.0.1 and everything seems to be OK. Of course I don't have new features, but, for the moment, I'd rather have consistent expected behavior than new features though, of course, I'd like to get to the bottom of this so I'm not stuck on 10.2.0.0 long term.
I thought it was something I did when I installed the latest version of DO. Currently, if I scan or rip a DVD, the folder now opens up in Explorer in stead of DO. Prior to installing the latest release, all folders were opened in DO. My current setting is to replace Explorer for all folders. I'm new with using DO so I assumed I did something wrong or I messed around with settings and inadvertently changed DO's behavior.
OK, let's not call it a 10.2.0.1 issue. Let's just say that explorer replacement doesn't work reliably here.
I have an application ActiveWords which can, among other things, open a folder in response to designated keystrokes. I've discovered that it also may cause Opus to open or Explorer to open.
It looks more and more like whatever problem I have is related to Explorer Replacement and external programs in general rather than any particular external programs.
I'm willing to accept that nothing relevant changed in 10.2.0.1 so this is not a 10.2.0.1 issue per se.
The most productive approach at this point would probably be to try to determine why Explorer Replacement doesn't work in conjunction with external programs on a fresh install of Opus.
I just installed Opus 10.2.0.1 and my scanner software on a copy of Windows 7 which has very little else installed (same hardware, different instance of Windows).
Scanning initially opened Explorer.
Restored old configuration.
Scanning opened Opus.
Backed up Opus configuration.
Scanning opened Explorer.
I understand how difficult it is to believe that backing up the configuration alters subsequent behavior, but it's definitely happening and it's repeatable.
Bob, what do you have in Windows Folder Options\Open folders in a separate process - see attachment
I recall a similar problem with another file manager that could replace Explorer on Vista - similar to what Opus does.
And the problem was with OCR scanning
From memory we solved it by checking that option off, but that created problems elsewhere.
Then we excluded the OCR program from being 'serviced' by the file manager, that worked most of the time. But we eventually unchecked the Replace Explorer option.
That option is not checked. I'll see what happens with it checked, but note that 1) it's never been required before and 2) the problem though occurring in relation to scanning also is present in other circumstances.
That option is not checked. I'll see what happens with it checked, but note that 1) it's never been required before and 2) the problem though occurring in relation to scanning also is present in other circumstances.[/quote]
Just to answer the question, since it was asked, checking that option doesn't make any difference.
Agreed. Nothing happened after the change which makes sense for the noted reasons above but appreciate the input. The only pattern I see is that if I'm in a lister that includes the folder for which the file will be placed after performing DVD ripping or scanning documents, the folder will not open up in Explorer. It is only if my lister(s) do not already have that folder open when Explorer opens the folder. These are the only two instances that I have come across when this problem occurs.
I uninstalled 10.2.0.0 then installed 10.2.0.2 with default configuration.
At least three external programs open folders in Explorer rather than Opus.
Could this be the fault of the external programs. I suppose so, but they work as expected in my currently configured 10.2.0.0.
I understand that it is believed that nothing relevant changed in 10.2.0.1, but, as stated, I don't have this behavior in my currently configured 10.2.0.0.
Despite the fact that 10.2.0.0 as I'm normally using it, does not exhibit the undesirable behavior described, a fresh default install of 10.2.0.0 does.
I'm reasonably sure I installed 10.0.0.0 fresh without this problem. I may have arrived at 10.2.0.0 by continually upgrading.
Is it possible to obtain 10.0.0.0 so that I can install it clean and see how it now behaves?
