Debugger Kernel BORDBK50.DLL is missing...
Carl and Kathryn Hurley
it up now I get the following information message after the initial
splash screen.
"Your Just-in-Time Debugger is currently set to 'C:\PROGRAM FILES\NORTON
SYSTEMWORKS\NORTON CRASHGUARD\CG32EH.EXE /p%ud /e%ud'. In order for
Just-in-Time Debugging and Distributed Debugging features to work
correctly, it needs to be chanted to: "D:\PROGRAM
FILES\BORLAND\DELPHI5\bordbg50.exe" -aeargs %/Id %Id. Do you want to
change this setting?"
I clicked No because I thought it would break crash guard.
When I run the Tutorial Project 1 I'm getting a message from Error:
"Debugger Kernel BORDBK50.DLL is missing or not registered."
I've tried answering the msg at startup yes to change the setting and
rebooting the computer. The message reappears. If I don't reboot, the
message will not reappear but the Project will not run either.
Suggestions???
Thanks
Carl Hurley
Jeff Overcash (TeamB)
installing as instructed. To manually register this get a command prompt.
Switch to the program files\common files\borland shared\debugger. type
regsvr32 bordbk50.dll
This should register it by hand.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
The fool escaped from paradise will look over his shoulder and cry
Sit and chew on daffodils and struggle to answer why?
As you grow up and leave the playground
Where you kissed your Prince and found your frog
Remember the jester that showed you tears, the script for tears. (Fish)
Carl and Kathryn Hurley
dialog and the Project 'Runs' without a hitch.
Carl
Just wanted to touch base with you on this solution. It seemed to work
just fine the first time I used it, but...
The fix is not permanent. It does work for a given Windows session. As
soon as I reboot the computer, Symantec's debugger makes its way to the
top of the list and when I start Delphi, in that new instance of
Windows, the previous error about the debugger not being registered
returns.
I've done a very brief look at the registry and found a couple of
entries that I need to revisit but it seems that the two debuggers don't
want to co exist.
The work around I've used successfully is that either before I start
Delphi or after it is up and running, I go to a DOS window and execute
the command you gave me previously. As long as I get the Windows
message that the new debugger is registered, Delphi will 'run' my code
fine.
If you want me to let you know what my continued pursuit of this problem
gets me, please e-mail me.
Thanks again.
Carl
ckhu...@gte.net
Jeff Overcash (TeamB)
only one JIT debugger can be installed. The JIT debugger is not Bordbk50
though, that is the integrated IDE debugger. Are you getting that message again
or just that the JIT debugger is not the primary one do you want to use the
delphi one at startup. They are different.
--
Carl Hurley
"Jeff Overcash (TeamB)" wrote:
> The Symantec debugger and the Borland JIT (just in time) debugger will fight,
> only one JIT debugger can be installed. The JIT debugger is not Bordbk50
> though, that is the integrated IDE debugger. Are you getting that message again
> or just that the JIT debugger is not the primary one do you want to use the
> delphi one at startup. They are different.
>
I understand this, I think.
I did a check on my registry and found the following:
CG32EH.EXE (the Norton debugger) is called from a single RegKey
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Window NT\CurrentVersion\aeDebug\
BORDBG50.EXE
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AeDebug
and
HKEY_USER\Default\Software\Microsoft\Window NT\CurrentVersion\AeDebug
I got the large grey dialog box when I started Delphi this morning but I did not
read it carefully so I'm not sure if the message is exactly the same as in my first
post.
Thanks for following along with me on this one
Carl