![]()
I tried to make this clear from the beginning. #Newsleecher 5.0 code#I think the coders changed something in the updates to a nonstandard code that VBox rightly rejects and wine and Windows installs over look. I thought I had been clear that I do not think this is a VirtualBox bug. which it would have to do if you are correct and this is a VBox bug. They don't think they have a problem since like I said it is working in Windows (and in wine for that matter). What I need is data or error codes or log info to pass to the BibleWorks programmers. #Newsleecher 5.0 series#So, it seems to me that something in the coding of the 8.0.017 series of updates is causing VirtualBox to cough. #Newsleecher 5.0 install#Then I tried to run the file in VirtualBox and got the same error as I had gotten so many times before in more than one install of virtualbox with more than one install of BibleWorks as explained above. #Newsleecher 5.0 update#However, I went to wine again and got the latest update and copied it into VirtualBox c:\Program Files\BibleWorks 8\ I checked the checksum of the file in wine with md5sum in a Linux terminal and downloaded windows-kb841290-x86-enu from the Microsoft website and installed and checked the checksum of the file that I copied to VirtualBox. So for the problem to be a file with all zeros then the file would have had to have been corrupted the 3 or 4 times I copied it from wine and the 6 or 8 times I have downloaded the update. I copied the file from my wine install and this is not just one update, but every update after 8.0.017 began. I don't have a hex editor installed in Windows in virtual box or really even know what one is, but I had already done on three or four occasions what Sasquatch suggested. Well, unfortunately it does not seem to be that simple. ![]() Mpack wrote:Since my expectation is that the problem is in the install/update program, I wouldn't expect to see anything in a VB or Windows event log: in any case there is no mystery here - your problem is simply that xxx is not a legal Win32 executable, plain and simple. #Newsleecher 5.0 windows 10#Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XP mpack Site Moderator Posts: 35171 Joined: 4. Incidentally, please update your profile to indicate your typical host and guest OS. However since VBox knows nothing and cares less about filesystems I do find it hard to believe VB can be at fault with these symptoms: although there have been bugs in recent VB versions to do with lazy writes to virtual drives, I would expect any such bug to produce widespread corruption of the filesystem, not just an inability to execute one file. In hindsight I was maybe a bit too emphatic in my rejection of the idea that VBox could be at fault. I can't comment on what users on other platforms have or have not reported, I am telling you what (as a programmer myself) is quite plain to me. If you look at the file with a hex editor you'll probably find that it consists of all zeroes or readable text. Since my expectation is that the problem is in the install/update program, I wouldn't expect to see anything in a VB or Windows event log: in any case there is no mystery here - your problem is simply that xxx is not a legal Win32 executable, plain and simple. ![]() Not having been a Windows user since Win98, where would I find the Windows events logs that Perryg mentioned that might show the information to pinpoint the problem? I have reinstalled BW and the original C\Program Files\BibleWorks 8\BW800.exe works fine, but when updated to anything after 8.0.017 then no go. However, any updates after 8.0.017* are rejected. If I click on an earlier update like 8.0.016f-BW800lg VB open and runs it fine. I assume that the BW update rewrites part of the original C\Program Files\BibleWorks 8\BW800.exe If I look in C\Program Files\BibleWorks 8\ I can find BW800.exe as well as previous update. The error in detail: C\Program Files\BibleWorks 8\BW800.exe is not a valid Win32 application. So, something was changed in the BW code with the latest series of updates that VB coughs up on. And, as stated above the updates work in wine. I understand that you probably mean that it is not related to a bug in VB, but it does have something to do with VB in that all these updates must be working with native Windows installs or there would be a major outcry from users. this problem has nothing whatever to do with VirtualBox. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |