Home » Forums » Support » BPBible support

BPBible Portable 0.4.7 not working on Win7 64bit

Submitted by Kees on Mon, 23/08/2010 - 3:22pm

Hi Guys,

I reported the same error for 0.4.5 but then I had no error to report. The work around is to run the program in win xp terminal elmulator. But now, after installing an running the latest version, I found the following error message in the log file. Hope it helps you to solve the problem.

Error message from logfile...

Traceback (most recent call last):
File "bpbible.py", line 29, in
File "zipextimporter.pyo", line 82, in load_module
File "config.pyo", line 106, in
File "config.pyo", line 56, in create_path_if_not_exists
File "c:\Python25\lib\site-packages\py2exe\boot_common.py", line 67, in write
TypeError: argument 1 must be string or read-only character buffer, not exceptions.WindowsError

‹ Search switches to dictionary without user choosing No right click copy of single words ›
#1Submitted by Kees on Mon, 23/08/2010 - 3:38pm.

Continued...

This time it's not the virus scanner that's causing a problem.
#2Submitted by Chris Morgan on Mon, 23/08/2010 - 10:40pm.

Explanation

config.py, line 106: it's just run create_path_if_not_exists(data_path) successfully, and now it's coming to create_path_if_not_exists(index_path).

def create_path_if_not_exists(path):
	if os.path.exists(path):
		return

	try:
		os.makedirs(path)
	except OSError, e:
		sys.stderr.write(e)

It's getting an OSError, and sys.stderr.write isn't liking a WindowsError; it wants a string.

The data and index paths are specified by the BPBible Portable launcher by command-line arguments as $EXEDIR\Data\settings and $EXEDIR\Data\resources.

The code then appends / to the paths because they don't end in \ or /.

So, the last function call is in create_path_if_not_exists("X:\PortableApps\BPBiblePortable\Data\resources/"). The directory does exist, as it is created by the launcher. Thus I conclude that os.path.exists isn't really liking the trailing forward slash. It's claiming it doesn't exist, which isn't true, so then it goes to os.makedirs which complains probably that the path is invalid or some such thing, and then an exception is printed rather than a string.

I think that's right, but I think I'll leave it to Jon or Ben to work out more about it.
#3Submitted by Jon Morgan on Tue, 24/08/2010 - 1:11pm.

Permissions error

I think it much more likely that it is a permissions error preventing both the PortableApps launcher and the application from creating the directory, and so the directory doesn't exist. Windows handles forward slashes just fine. Could you please check if the BPBiblePortable\Data\resources directory exists?
#4Submitted by Kees on Tue, 24/08/2010 - 1:19pm.

Permission error

I would be suppriesed it was a permission error, since installing the program - and thus creating all necessary directories - went well and other portableApps programs work in the same root directory as well. I've got a :\PoratableApps root directory that contains all of my portable applications. All work like a charm, except BPBible. So, I'm leaning towards an application problem. The more since it works well in a win XP virtual PC.
#5Submitted by Jon Morgan on Tue, 24/08/2010 - 2:51pm.

Permissions error

I agree: I don't like the permissions error answer either. Could you please try the following:
1. Download and unzip the version of bpbible.exe from http://sites.google.com/site/jmmorganswordmodules/Home/bpbible_portable_....
2. Put it in your BPBiblePortable\App\BPBible directory.
3. Run the application again.
4. See what is in the error log, and post it here. Hopefully it will be the actual error, so we won't need to guess.

Thanks!
#6Submitted by Kees on Wed, 25/08/2010 - 11:33am.

Permission error

Hi Jon,

Tried your staps. This time no error file is created. Log file has the same timestamp (23 aug) and content is unchanged.

I've renamed the log file and tried again. Neither your patch nor the original application creates a logfile again. Tried the same with a blank logfile, no entry was made.

I've tried using the original application and your patch. I ran them both seperately as well as through the BPBibleProatble.exe application. No result whatshowever.

As a result of this, a question popped up in my mind. Was the error I reported a result of a runtime error or was it an old compile time error, that never was cleared from the logfile? Is so, the logfile with content was installed with the application and the logfile was not created as a result of starting the application.
#7Submitted by Jon Morgan on Thu, 26/08/2010 - 2:34pm.

Log file missing?

I think it was the result of a runtime error. We certainly do not create the log file in the installer (I just ran it again to make sure). It's also worth noting the timestamp on the log file. 23rd August is presumably when you ran BPBible, but it is certainly not when the installer was built.

I think it most likely that there was some transitory error which came up once rather than a persistent error. That being the case, I'm not sure there's much more we can do about it (other than just waiting to see if it happens again). I hope BPBible still works correctly for you.
#8Submitted by Kees on Fri, 27/08/2010 - 11:54am.

Only when ran in virtualPC on

Only when ran in virtualPC on win xp 32bit and this can't be the intension of the application.

Looking at he error message an I was thinking... Could it be that a variable was passed to a function that expected a string but received an numeric value from the viariable? If so, it should be retracable in the application. In my experience this could happen with weak typed variables. Maybe worth investigating?

Could there be differences in the 32bit and 64bit operating system that interfere with the application.

Well, anyway I hope you will find a permanent solutions. Until then I'll keep running it in virtualPC.
#9Submitted by Jon Morgan on Fri, 27/08/2010 - 2:16pm.

32-bit vs. 64-bit

The particular error reported in the log file was trying to write out an exception to the command line without turning it into a string first. This does not work.

As to the difference between 32 and 64 bit, it would certainly not surprise me if there was a difference because of that. As I do not have 64-bit Windows the binaries have never been built for that platform or particularly tested on that platform.
#10Submitted by bannination on Tue, 14/09/2010 - 12:12pm.

Just wanted to say that I

Just wanted to say that I also experience this error, so it's not just limited to a couple people.
#11Submitted by bannination on Thu, 16/09/2010 - 12:31pm.

I'd be glad to help diagnose

I'd be glad to help diagnose the problem as well if you'd like me to try something. I have already tried all compatibility modes and none help.
(Using the portable version BTW)
#12Submitted by rcbako on Sat, 06/11/2010 - 7:21am.

I think we have all common

I think we have all common concern, the runtime error. I tried to reinstall it but the same problem arises. Maybe there's something missing in the system itself.