When I try to run the Database Desktop I get the following Error Dialog,
"
Could not initialize BDE.:
Insufficient shared memory available."
Thanks,
G. Saich
>Has anyone had success running the Borland Database Engine under wine?
>The 16-bit engine seems to run fine but when I try to execute
>bdeadmin.exe (32-bit) I get the following error dialog, "
>Exception EDBEngineError in module bdeadmin.exe at 00054FA2.
>An error occurred while attempting to initialize the Borland Database
>Engine (error $251E)."
I have no time now but it can be made to run. You probably
miss the registry entries. Try to export them with regedit
under Windows and import them using regapi.
>When I try to run the Database Desktop I get the following Error Dialog,
>"
>Could not initialize BDE.:
>Insufficient shared memory available."
>
I never was able to start the database desktop
anyway (another bug not related)
Gerard
do you have
[HKEY_LOCAL_MACHINE\Software\Borland\Database Engine\Settings\SYSTEM\INIT]
"SHAREDMEMLOCATION"="9000"
in your registry (~/.wine/system.reg)? It will be created when the winedefault.reg file
is imported via regapi.
Ciao Stefan
Thanks, I think this is progress of sorts. Now I'm getting, "
Exception EDBEngineError in module bdeadmin.exe at 00054FA2.
An error occurred while attempting to initialize the Borland Database
Engine (error $2B32).
"
When running bdeadmin.exe;
and
"
Unhandled exception 0xc0000005 at address 0x0046c97d. . . "
I admit the Win registry is a bit of a dark art to me. I haven't
located a cenbtral repository of information on wine with the BDE, does
anyone know if it exists. (I hate to keep posting, if there is a place I
can read it myself.
Thanks,
GS
>Exception EDBEngineError in module bdeadmin.exe at 00054FA2.
>An error occurred while attempting to initialize the Borland Database
>Engine (error $2B32).
BDE error : Sharing violation
Try to add :
"LOCAL SHARE"="FALSE"
just after the sharedmemlocation line.
Gerard
> BDE error : Sharing violation
> Try to add :
> "LOCAL SHARE"="FALSE"
Please tell whether this works (we need to add it to winedefault.reg
in this case)
Andreas Mohr
Yes, this worked. Thank you. I am able to use bdeadmin.exe and I have
run apps using the bde. I have even compiled delphi 4 apps using the
bde that are now running fine.
I am not able to run the debugger in delphi 4, though. I get an error
that says, "Debugger Kernel BORDBK40.DLL is missing or not registered."
Should I start a new thread on this?
GS
>> BDE error : Sharing violation
>
>> Try to add :
>
>> "LOCAL SHARE"="FALSE"
>
>> just after the sharedmemlocation line.
>Please tell whether this works (we need to add it to winedefault.reg
>in this case)
>
You are aware that here you will hide a Wine bug, are you ?
Gerard
And I to wonder why those registry entries needed by BDE aren't created
during programm installation...
Bye
--
Uwe Bonnes b...@elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
> :>> BDE error : Sharing violation
> :>
> :>> Try to add :
> :>
> :>> "LOCAL SHARE"="FALSE"
> :>
> :>> just after the sharedmemlocation line.
> :>Please tell whether this works (we need to add it to winedefault.reg
> :>in this case)
> :>
> : You are aware that here you will hide a Wine bug, are you ?
Well, I was afraid that it is one, yes.
So what to do about it ? Add it or not ?
And what bug is it ?
> And I to wonder why those registry entries needed by BDE aren't created
> during programm installation...
Well, of course you do not need the base address key !! (in Windows, that is)
This is an *option* of BDE, and we can be damn glad that we can set it !
Andreas Mohr
>
>> : You are aware that here you will hide a Wine bug, are you ?
>Well, I was afraid that it is one, yes.
>So what to do about it ? Add it or not ?
IMHO, no
>And what bug is it ?
One of the thousands I don't have the time to investigate:-)
Disk access ? Synchro Apis ?
Gerard
>I am not able to run the debugger in delphi 4, though. I get an error
>that says, "Debugger Kernel BORDBK40.DLL is missing or not registered."
>Should I start a new thread on this?
It comes from you not having installed Delphi under Wine, or imported
missing registry keys. But if you do it, I don't expect it to work.
Windows 32 bits debugger have to rely on interprocess communication -
there is none currently under Wine.
Gerard
I did install Delphi under wine; "C:\" is actually "~/wine" and Delphi 4
is the first application I have installed. There were some pretty good
reviews of Delphi at Winehq, I wonder how those guys are doing it (The
whole RAD tool is pretty pointless without being able to use the "run"
function). I sent e-mails out asking, so we'll see what comes back.
Here is a grep of what I found related to bordbk.dll in the ~/.wine
directory.
"
[gsaich@xmachina .wine]$ grep bord *
system.reg:"BorlandReboot5"="C:\\Program
Files\\Borland\\Delphi4\\Bin\\TREGSVR.EXE -q C:\\Program Files\\Common
Files\\Borland Shared\\Debugger\\bordbk40.DLL"
system.reg:"C:\\Program Files\\Common Files\\Borland
Shared\\Debugger\\bordbk40.dll"=dword:00000001
"
Any thought on where I can go from here, or should I just punt?
I pulled some registry entries from another machine (Win98) and was able
to get the debugger working (Its a little flakey, but seems to be
working). Additionally, I had to copy a RPCRT4.DLL to the
C:\windows\system folder. With Kylix on the way I'm not sure if anyone
besides me is interested in this, but if anyone is interested let me
know and I'll post what I did. Anyone know what RPCRT4.DLL does?
GS
>
>I did install Delphi under wine; "C:\" is actually "~/wine" and Delphi 4
>is the first application I have installed. There were some pretty good
>reviews of Delphi at Winehq, I wonder how those guys are doing it (The
>whole RAD tool is pretty pointless without being able to use the "run"
>function). I sent e-mails out asking, so we'll see what comes back.
>Here is a grep of what I found related to bordbk.dll in the ~/.wine
>directory.
Well, running and debugging are different things; Wine allows
for spawning a different process, but it can't allow currently for
a process to 'see' a process it spawned. Maybe they disabled
the integrated debugging ?
Gerard
Gerard