<p>A couple of things.</p>
<p>First is I know I'm working with alpha software, so expect problems, I would expect to be asked questions about the exact sequence of operations, and so on.</p>
<p>I know that the folder only ever existed on Raoul's machine, and that's where the problem lies, for some strange reason installations on this particular PC are stuck with THINKING that the folder should be there. Just so you can see what the problem is, here are the first few lines from one of yesterday's trace reports:</p>
<p>OpenLP Bug ReportVersion: 1.9.4--- Exception Traceback ---Traceback (most recent call last): File "C:\Documents and Settings\raoul\My Documents\My Projects\openlp\trunk\build\pyi.win32\OpenLP\outPYZ1.pyz/openlp.plugins.bibles.forms.bibleimportform", line 285, in onCurrentIdChanged File "C:\Documents and Settings\raoul\My Documents\My Projects\openlp\trunk\build\pyi.win32\OpenLP\outPYZ1.pyz/openlp.plugins.bibles.forms.bibleimportform", line 514, in performImport File "C:\Documents and Settings\raoul\My Documents\My Projects\openlp\trunk\build\pyi.win32\OpenLP\outPYZ1.pyz/openlp.plugins.bibles.lib.manager", line 197, in import_bible</p>
<p> </p>
<p>I was attempting to import a bible, one that I'd confirmed would import into V1.2.8 so was fairly certain I was working with a working test data set. I selected the "books" and "verses" files, entered the version and copywrite data and "instantly" on starting the import got the error message.</p>
<p>I reported a similar error some time ago against v1.9.3. I believe there something "hanging" on my PC from that bug, and if so, where should I look to clean it out so testing of 1.9.4 can continue.</p>
<p>I should add, that once this path has appeared the import stops, so it is quite probable that this problem (which is peculiar to one of my PCs) is actually hidding another bug by prevetning the correct error logging taking place.</p>