Those of you having the problem can you send the following info to me at mbushell@bibleworks.com:
1. Your Operating System version and default language
2. the type of account (administrator or limited user)
3. are you running as a remote user?
Thanks,
Mike
One more suggestion. If you are running remotely or in a limited account, try going to the BibleWorks main folder. Look int the INIT subfolder. If you are running from a limited account your should see a file named like this:
username.ini
wherer username would be your logon name.
If that file is there delete it and then try running BW.
Mike
Mike,
I had the same problem Markus explained running BW8 under Win XP Pro SP3 (Spanish) even though I had Administrator rights (and no remote user). I spent a whole afternoon trying to solve the problem on my own. Here's what I did:
Start - Control Panel - Folder Options - View tab - uncheck Use Simple File Sharing (last checkbox).
After doing that I could right-click on folders and files and use the Security tab and the Advanced Options for permissions.
I made sure I had total control of all the files in BW's directory and then I was able to update. It was a very unpleasant experience, but I am now running 8.0.015j.1 without any noticeable problem.
For the record, my other BW8 installation on a virtual machine with an English copy of Win XP Pro SP3 did not have any of the problems described in this thread.
Hope this helps.
Last edited by Ruben Gomez; 01-14-2010 at 04:10 PM. Reason: Add more info
Ruben,
When you changed the permissions, do you recall if Full Control was given (or not given) for the groups Everyone, Users, & Administrators?
To all others affected:
We made some changes to make it easier for Limited User accounts to run BibleWorks, but it appears that some non-English systems are having folder Security permissions messed up by this new patch. If you look at the folder Security tab properties for the BibleWorks 8 folder, you need to have Full Control (read, write, delete) permissions for Administrators and all Users.
To see the Security tab permissions, you have to turn off "Simple file sharing", as Ruben points out:
Start - Control Panel - Folder Options - View tab - uncheck Use Simple File Sharing (last checkbox).
Once that is enabled, you need to right-click on the Program Files\BibleWorks 8 folder, select Properties, and click the Security tab.
After that, you need to grant Full Control to Everyone, Users, Administrators, and Current user.
Then, you need to restore an old EXE. In your BibleWorks 8 folder, there should be a file with a name like "8.0.015c-BW800lg.exe". Rename the existing "bw800.exe" to "do_not_use-bw800.exe", and make a new copy of the file named "8.0.015c-BW800lg.exe" and name it "bw800.exe". This should enable things to be running from a previous version of the EXE.
We are very sorry for this problem and are working hard on a fix.
Thanks for bearing with us.
Michael
Last edited by MTan; 01-14-2010 at 05:23 PM.
To be quite honest, I don't remember what the settings were. I think everyone had full control, but I'm not 100% sure. Sorry.
I did uncheck the inherit permissions options (or something to that effect), and left just me with full control.
I hope this makes sense.
Thank you for your help.
I just posted a new exe that should be sase (8.0.015k.2). The security fixes that we were trying to add have been removed until we figure out what is going on. But ig you had a problem you will still have to set the read-write permissions of the BW folder as Michael Tan outlined above.
In case you are curious about the problem we were trying to address it has to do with users trying to run BW from a limited account under XP. It didn't work for non-English OS installations. Back to the drawing board on that.
Mike
FWIW...
The latest update, k, crashed after I first updated it, but when I tried to open BW again afterwords, it worked fine. IOW, the update crashed, but it did update, and all I had to do was reopen.
This just shows you how convoluted all of the security measures have become.
I think from now on we should all just join the NSA Cryptography/Analysis Section and go from there.