I wonder if anyone has experienced a conflict with Wine Pre-Loader and Devonthink. I regularly use a program called NotaBene, which is actually a suite of programs built around a word processor. It has the capability to search my bibliographic database as well as all of my documents (produced by NB but also Word, pdf, ppt, saved web-pages, basically anything) in a manner (from a user-perspective) very similar to DT3. Since NotaBene is a Windows program in order to run it on a Mac one uses Wine Pre-Loader (which is bundled with NB for Mac). What I have been experiencing is that Wine PreLoader does not quit when I exit NB if (and I think only if) I happen to have DT open.
Does it make sense that there is a possible conflict? Has anyone had this or similar experience? Any suggestions?
It is not clear how you are using NotaBene / Wine in relation to DEVONthink. Are you opening documents stored in DEVONthink into NotaBene, thus causing Wine to launch? Or something else?
No, the situation is as follows. During the course of a workday I might want to look at items I have in DT, and so I have it open, but may or may not search or use DT in any way. There is one group of indexed files in DT which is also indexed and searched by the NB bibliographic program, called Ibidem, and another NB program called Orbis. I don’t think either Orbis or Ibidem can access the files I keep in the DT database – only the files I have indexed in DT.
In order to open and use NB on a Mac it has to use the Wine pre-loader. It is a version of Wine that is bundled with NB so that opening NB simultaneously and automatically opens the Wine pre-loader.
The situation I experiencing is when I am using NB and also happen to have DT open on my computer, when I at the end of the day shut down NB, Wine does not shut down (as it would normally when I use NB) but remains open and requires me to Force Quit it.
I think this is mostly in the category of a slightly annoying inconvenience because as far as I can tell the functionality of neither DT nor NB is impaired. Nonetheless, I am wondering if this behavior is due to some sort of conflict and if so if there is anything that can be done to correct the situation.
Well, this is a pretty non-standard setup so I wouldn’t be too surprised if issues arise.
I would recommend purposely stalling it then doing this…
When the application is stalled, do a Spotlight search for Activity Monitor . Select our application in the list of processes - it should show “(Not Responding)” and the name in red - and press Command-Option-S to run a sample on it. Provide that to the NotaBene support team and maybe they can make some sense of the cause.