[Bug 1490] Bible Companion loading stops on LOCAL_GetBlock not enough space in local heap

http://bugs.winehq.org/show_bug.cgi?id=1490

--- Comment #30 from David Moore   2009-07-13 22:48:45 ---
(In reply to comment #29)
> Is this still an issue in current (1.1.25 or newer) wine?

David Moore here who began this thread:

I finally resolved this on my Linux system and have Bible Companion
Series and its Gramcord functions running under Wine.

Since this was mainly a process of trial and error I may not remember
exactly every step, but I will post the most important matters and hope that
others may get their BCS and Gramcord up and running with Wine as well.

First of all, it is necessary to come up with an environment (speaking of
the computer operating system environment of course) under which BCS has room
to run.  Through trial and error, I found that the minimum environment
variables which are needed are PATH, DISPLAY, and HOME.  I was able to create
this reduced environment for BCS by prefixing the command that opens the BCS
program with the following code:  env -i PATH=$PATH DISPLAY=$DISPLAY HOME=$HOME

If you want to understand some basics about the env command try this:

$ env --help

The help message explains that the env command with the -i variable following
creates an empty environment for the program being initiated.  The addition of
PATH=$PATH DISPLAY=$DISPLAY HOME=$HOME reestablishes only these three values to
the environment under which BCS will run.  This got me past the problem of "not
enough space in local heap."

I had copied my BCS directory from my Windows partition to
/home/my_username/.wine/drive_c, so my complete command line for starting BCS
under Wine was as follows:

$ env -i PATH=$PATH DISPLAY=$DISPLAY HOME=$HOME /usr/bin/wine "C:\bcs\Bcs.exe"

I did this from the command line and did not set up an icon on the desktop
until later, since working from the command line is a better way to read the
feedback.

Using this command did get me past the "not enough space in local heap,"
but the program soon hung again.  Reading in the command window the steps that
the program had taken, I saw that a certain dll file was being requested by the
program.  I located this file and copied it into the
/home/my_username/.wine/drive_c/bcs directory, and registered it with Wine
using the Wine utility that helps with dll files (sorry I don't recall the
utility program's name right now).  This helped, but there were still minor
bugs.

I added a number of other dll files from different places.  One which was
specifically called for in the feedback from the command window I was not able
to find on my Windows partition, so I located it on the Internet, copied it to
my Wine BCS directory and registered it with Wine using the utility mentioned
above.  So now it works.

At one point in this process, after I had figured out the necessary
environment for BCS, I did an install under Wine from a Gramcord for Windows CD
(Series 1E).  I don't know whether or not this affected the outcome.

When I put an icon on my desktop to start BCS, the command I used was as
follows:

env -i PATH=$PATH DISPLAY=$DISPLAY HOME=$HOME /usr/bin/wine "C:\bcs\Bcs.exe"

In the "Work path" space I put the following:

/home/my_username/.wine/drive_c/bcs

If you use these command lines, be sure that the capitalization of letters and
the filenames in all repects correspond to what you have in your
/home/your_username/.wine directory.

I can give no guarantees that what has worked for me will definitely work
on your system.  But I recommend it as a way that I got my BCS-Gramcord program
up and running.

All the best,
David Moore