Nathanael
12-01-2009, 06:13 AM
The following problem has been reported to the BibleWorks support, but the answer I received did not work.
We installed BW 8 under Windows 7 (64bit) on several machines (standalone installation). The program works fine under the administrator account, but not under a Limited User account. After the splash screen, the following message occurs: "A valid program activation code was not found. Please reinstall BibleWorks."
The support gave the advice "Due to the way BibleWorks writes its information to the initialization file, it is necessary to have some kind of write access to that file, which is stored in the BibleWorks folder itself." We tried this, but even if the user gets full write access to the whole folder, BW quits after the splash screen.
The second advice was: "If write access cannot be given to the Ids that would be using the program, then we would suggest that the desired changes be made by an administrator and saved. Open BibleWorks again and access the BW Options Window. In the FLAGS panel, expand the list of SHUTDOWN OPTIONS. Make sure that all items are deselected, then close BibleWorks again, saving this information. In this way, when one uses the BibleWorks program, the program will not attempt to save changes made during that session." This did not work either. There are no problems in shutting down the program, but in starting it as a Limited User.
Did anyone of you experience the same problem or do you have any suggestions?
Regards,
Nathanael Lüke
We installed BW 8 under Windows 7 (64bit) on several machines (standalone installation). The program works fine under the administrator account, but not under a Limited User account. After the splash screen, the following message occurs: "A valid program activation code was not found. Please reinstall BibleWorks."
The support gave the advice "Due to the way BibleWorks writes its information to the initialization file, it is necessary to have some kind of write access to that file, which is stored in the BibleWorks folder itself." We tried this, but even if the user gets full write access to the whole folder, BW quits after the splash screen.
The second advice was: "If write access cannot be given to the Ids that would be using the program, then we would suggest that the desired changes be made by an administrator and saved. Open BibleWorks again and access the BW Options Window. In the FLAGS panel, expand the list of SHUTDOWN OPTIONS. Make sure that all items are deselected, then close BibleWorks again, saving this information. In this way, when one uses the BibleWorks program, the program will not attempt to save changes made during that session." This did not work either. There are no problems in shutting down the program, but in starting it as a Limited User.
Did anyone of you experience the same problem or do you have any suggestions?
Regards,
Nathanael Lüke