I would appreciate it if someone could point me in the right direction.
regsvr32 bordbk51.dll
if that doesn't work first run
regsvr32 -u bordbk51.dll
and then register it.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
A spider wanders aimlessly within the warmth of a shadow, not the regal creature
of border caves, but the poor, misguided, directionless familiar of some obscure
Scottish poet. The mist crawls from the canal like some primordial phantom of
romance To curl, under the cascade of neon pollen. While I sit tied to the
phone like some expectant father, your carnation will rot in a vase. (Fish)
> same solution works fro both OSes. Get a command prompt switch to the directory
> with bordbk51.dll in it and run
>
> regsvr32 bordbk51.dll
>
> if that doesn't work first run
>
> regsvr32 -u bordbk51.dll
>
> and then register it.
Jeff,
When I try REGSVR32 from a command prompt, I get "Bad command or file name".
Larry
> same solution works fro both OSes. Get a command prompt switch to the directory
> with bordbk51.dll in it and run
>
> regsvr32 bordbk51.dll
>
I have found, however, a file called REGSVR32.EXE in the "C:\WINDOWS\SYSTEM"
directory. It appears to have corrected the problem. Thanks.
This directory is *NOT* in the PATH string; would you expect it to be? No wonder I
hate win95!
Larry Bristol wrote:
>
> I have found, however, a file called REGSVR32.EXE in the "C:\WINDOWS\SYSTEM"
> directory. It appears to have corrected the problem. Thanks.
>
> This directory is *NOT* in the PATH string; would you expect it to be? No wonder I
> hate win95!
--
>Win9x should automatically have <windows> and <windows\system> in its path. It
>not being there could cause a lot of unexpected problem of dll not found
>messages.
"<windows>" and "<windows>\command" are there, but not
"<windows>\system". I will add it manually and continue to be amazed
that any of this works at all.
I have not received any (other) messages about .DLL's not being found,
or encountered other anomalous behavior that I cannot explain. (OTOH,
I cannot explain it when things behave correctly, either!) Since I
have not had this OS installed very long, it just could be one of
those "situations" waiting for the right opportunity to come along in
order to inflict the most damage. In time, unless I am very lucky, I
am sure I will get used to windows. <smile>
Thanks for your help, Jeff!
>same solution works fro both OSes. Get a command prompt switch to the directory
>with bordbk51.dll in it and run
>
>regsvr32 bordbk51.dll
>
>if that doesn't work first run
>
>regsvr32 -u bordbk51.dll
>
>and then register it.
Whoops! I spoke too soon earlier. This has *NOT* fixed the problem.
I ran the above command with the -u switch and got:
DllUnregisterServer in Bordbk51.dll succeeded.
then ran it again (without the switch) and got:
DllRegisterServer in Bordbk51.dll succeeded.
However, I still get the message about the missing .DLL. I only get
the message if the project has been modified in some way. If nothing
is modified, even a "Build All" does not cause the error message to be
generated.
>same solution works fro both OSes. Get a command prompt switch to the directory
>with bordbk51.dll in it and run
>
>regsvr32 bordbk51.dll
>
>if that doesn't work first run
>
>regsvr32 -u bordbk51.dll
>
>and then register it.
As I indicated earlier, this procedure does not correct the problem.
As far as I can tell, the DLL is, infact, registered correctly. I
have narrowed the problem down a bit from last week.
This only seems to occur when I select Run (F9) in the IDE after
having made changes to the application. It first performs the
required Make (a la Cntl-F9), displays the message box about the
"missing DLL", and does not execute the application.
If I first select Make (Cntl-F9), the application changes are compiled
and linked as one would expect, and the message does not appear.
After the Make activity is completed (using either of the two ways
above), I can now select Run, and the apllication executes as
expected. (Well, not always *exactly* as expected, but that is
another story. <grin>)
I have no trouble getting BCB to run the application, and in spite of
the "missing DLL", the debugger also works perfectly well. This
message box is more of an aggravation than anything, but I surely
would like to get it resolved.
TIA
This should make it work.
Chris Kuhn
KBSI
>
>1) Put bordbk51.dll in the system directory.
>2) regsvr32 bordbk51.dll
>
>This should make it work.
OK - I put the DLL in C:\WINDOWS\SYSTEM and registered it
(successfully) as you suggested. Since doing so, I have not been able
to reproduce the error message. We will have to wait and see if this
solution "sticks", but it looks good for now.
Thanks, Chris!