FOLLOWING FROM USER INPUT ON THE BUG LOADING GM7S32.DLL FOR GOLDBOX-7:


1. ERROR loading GM7S32.DLL

This is about the only unsolved bug left in the entire GoldBox line of
products.  It occurs only for GoldBox-7 (for GoldMine 7).  It does not
occur consistently.  Many users never have a problem with this bug.

GoldBox uses the sync DLL for a single purpose: To generate RECIDs.
Everything else in GoldBox that provides GoldMine compatibility is directly
coded in Visual dBase (the language GoldBox is programmed in, which also
requires the BDE).

In all previous GoldBox releases - GoldBox-4, GoldBox-5, GoldBox-SQL -
there was never a problem loading the sync DLL.  The code in GoldBox is
just a single line, and has remained unchanged.  Therefore, something has
changed in GoldMine 7 to generate this error.  Cause: Unknown.

Some users seem to have solved this bug by installing, within GoldMine,
the license file locally.  I have no further info on how this is done.



2. Installing GoldMine Locally

Paul Laufer provided feedback on solving the GM7S32.DLL load problem in
some GoldBox-7 installs, with the option of installing GoldMine locally.

In GoldMine 7:

File / Configure / License Manager
Click the Tab called "Install Locally".

Provide the folder for the install.

Apparently this installs the EXEs, DLLs, XMLs and so forth, and registers
them so they are visible.  Once that occurs, GoldBox-7 should be able to
load the GM7S32.DLL without error.

Paul also mentions that GM7SETUP.EXE has to be in a folder called
goldmine\setup\goldmine, and that a NetUpdate should handle that as well.



3.

Aha! Things are beginning to come into focus, now. John Stillman has been
recommending local installs of GM for some time now. Hate it, because it
greatly increases the load when updating and doing certain other kinds of
things.

But this may be an example of why he's saying that. Maybe the end of an era
in terms of simple GoldMine installs...all thanks to Microsoft, of course.



4.

FYI: Happens when installing the GISMO with PE as well - am checking a
number of PC's will come back on that.



5.

Did a check..., did a workstation install using the GMPE setup file. This
creates a registry entry in H_KEY_LOCAL_Machine|SOFTWARE|FRONTRANGE. If you
export that and import in any other PC alleviuates that problem. This is
just for GISMO, but might work with GoldBox as well. Doing some more
testing this afternoon.



6.

Further to this, it creates a C:\Program Files\GoldMine folder with a bunch
of files, including the gm7s32.dll. If you have a copy of that, plus the
registry, and copy that it should work, as long as the dll's get
registered. More testing on the way.



7.

Something more is going on, just copying did not work. There must be
something elese being registered. Will find out more.



8.

Call off the dogs.  The problem has "mysteriously" gone away.

Seemingly out of the blue, I am no longer getting the error.

Due to totally unrelated reasons, along the way, we rebooted the server
that I was trying to run GoldBox from (the one that we did the "Install
Locally" for GoldMine on).  This is NOT the server where GoldMine and
GoldBox are installed, but purely the server we are trying to run it FROM.

Nevertheless, the error is no longer happening.  I suspect the reboot may
have done the trick.



9.

For the install locally tab to appear under tools|configure|license
manager, the gmsetup.exe file must be in the \%sysdir%\setup\goldmine\
folder.   Tested and confirmed with GMPE, by the way.



10.

Put the path to GoldMine in the PATH environment variable.  This was a
solution that worked, submitted by Alan Mackenzie:

(The following is for Windows XP)
 
A. Right click on {My Computer} and select {Properties}.
 
B. Select {Advanced} tab.
 
C. Click {Environment Variables} button at screen bottom.
 
D. In {System variables} scroll list, highlight {Path}, then click {Edit} button.

E. In the popup box, add the GoldMine path to the end of the {Variable value} entry.
   Remember to start with the semi-colon, to separate it from the previous entry.

F. Click {OK} to save.


The Path variable is a system environment variable, so you need Administrator rights to change it.


END.