Thread View: borland.public.install.vdbase
7 messages
7 total messages
Started by Paul Johnson
Sun, 24 Jan 1999 00:00
Debugger failure (BLW32.DLL)
Author: Paul Johnson
Date: Sun, 24 Jan 1999 00:00
Date: Sun, 24 Jan 1999 00:00
14 lines
852 bytes
852 bytes
I am getting the following message when I choose the "Debug" button from the "Fix | Ignore | Debug..." dialog box: Error initializing BLW32.DLL Cannot start Visual dBASE Debugger. Blw32.dll is there, and by this point, I have gone as far as doing a complete uninstall/reinstall of VdB7 and the 7.01 upgrade. The error message still pops up. What should I try next? Thanks. Paul Johnson
Re: Debugger failure (BLW32.DLL)
Author: Romain Strieff [TeamB]
Date: Mon, 25 Jan 1999 00:00
Date: Mon, 25 Jan 1999 00:00
24 lines
1198 bytes
1198 bytes
In article <78gr0o$p3r21@forums.borland.com>, Paul Johnson politely paraphrased ... > I am getting the following message when I choose the "Debug" button from the > "Fix | Ignore | Debug..." dialog box: > > Error initializing BLW32.DLL > Cannot start Visual dBASE Debugger. > > Blw32.dll is there, and by this point, I have gone as far as doing a > complete > uninstall/reinstall of VdB7 and the 7.01 upgrade. The error message still > pops up. > What should I try next? > > Check your registry if it points to the right directory. HKEY_LOCAL_MACHINE\SOFTWARE\Borland\BLW32 -- Romain Strieff [TeamB] Please read this newsgroup guide below before posting on the private Inprise newsgroups. http://www.inprise.com/newsgroups/guide.html --
Re: Debugger failure (BLW32.DLL)
Author: Paul Johnson
Date: Tue, 26 Jan 1999 00:00
Date: Tue, 26 Jan 1999 00:00
9 lines
819 bytes
819 bytes
>Check your registry if it points to the right directory. > >HKEY_LOCAL_MACHINE\SOFTWARE\Borland\BLW32 >-- >Romain Strieff [TeamB] Yes, it does. I am wondering if I would get that error if the database I'm using isn't correctly registered with the BDE administrator?
Re: Debugger failure (BLW32.DLL)
Author: Romain Strieff [TeamB]
Date: Tue, 26 Jan 1999 00:00
Date: Tue, 26 Jan 1999 00:00
19 lines
1123 bytes
1123 bytes
In article <78kd5e$smv5@forums.borland.com>, Paul Johnson politely paraphrased ... > >Check your registry if it points to the right directory. > > > >HKEY_LOCAL_MACHINE\SOFTWARE\Borland\BLW32 > >-- > >Romain Strieff [TeamB] > > > Yes, it does. I am wondering if I would get that error if the database I'm > using isn't correctly registered with the BDE administrator? > Mmm, could be worth a try. Perhaps also a corrupt .cfg -- Romain Strieff [TeamB] Please read this newsgroup guide below before posting on the private Inprise newsgroups. http://www.inprise.com/newsgroups/guide.html --
Re: Debugger failure (BLW32.DLL)
Author: Paul Johnson
Date: Tue, 26 Jan 1999 00:00
Date: Tue, 26 Jan 1999 00:00
36 lines
1991 bytes
1991 bytes
Romain Strieff [TeamB] wrote in message ... >In article <78kd5e$smv5@forums.borland.com>, Paul Johnson politely >paraphrased ... >> >Check your registry if it points to the right directory. >> > >> >HKEY_LOCAL_MACHINE\SOFTWARE\Borland\BLW32 >> >-- >> >Romain Strieff [TeamB] >> >> >> Yes, it does. I am wondering if I would get that error if the database I'm >> using isn't correctly registered with the BDE administrator? >> >Mmm, could be worth a try. Perhaps also a corrupt .cfg >-- >Romain Strieff [TeamB] I looked through the BDE for any apparent problems, and thought I had something when the driver for some of my databases was listed as PARADOX. I changed them to dBase, saved changes and closed the BDE Admin, but this still didn't work, even when trying to open the debugger on the VdB7 sample files. The corrupt .cfg you refer to is IDAPI.CFG? That's what gets written by the BDE Admin, right? I'm guessing that if I run the BDE Admin and save changes, the IDAPI.CFG file ought to be intact. I would be willing to end the headache by uninstalling/reinstalling again, but even that didn't work the first time. I suppose there was something left over that I needed to remove manually (files or registry keys?) to get a fresh start. I'll wait and see what advice comes in..... Thanks. Paul Johnson, novice. Team B rocks!
Re: Debugger failure (BLW32.DLL)
Author: Romain Strieff [TeamB]
Date: Wed, 27 Jan 1999 00:00
Date: Wed, 27 Jan 1999 00:00
27 lines
1640 bytes
1640 bytes
In article <78lfpj$ia3@forums.borland.com>, Paul Johnson politely paraphrased ... > > I looked through the BDE for any apparent problems, and thought I had > something when the driver for some of my databases was listed as PARADOX. I > changed them to dBase, saved changes and closed the BDE Admin, but this > still didn't work, even when trying to open the debugger on the VdB7 sample > files. The corrupt .cfg you refer to is IDAPI.CFG? --- Yes, if you don't use several specific ones. (1 for level 7 tables, 1 for level 5 tables etc) > That's what gets written > by the BDE Admin, right? I'm guessing that if I run the BDE Admin and save > changes, the IDAPI.CFG file ought to be intact. --- Not necessarily. Tr to rename it, then a new, fresh one will be created which you can try out if it works. Naturally you have to do all your settings anew. -- Romain Strieff [TeamB] Please read this newsgroup guide below before posting on the private Inprise newsgroups. http://www.inprise.com/newsgroups/guide.html --
Re: Debugger failure (BLW32.DLL)
Author: Paul Johnson
Date: Thu, 28 Jan 1999 00:00
Date: Thu, 28 Jan 1999 00:00
10 lines
971 bytes
971 bytes
I couldn't figure it out, so I removed all traces of VdB and Borland from disk and registry, and re-installed. It was a pain, but the debugger is working now, along with the rest of VdB7. Thanks for your suggestions. I hope this posts correctly. I'm trying out Free Agent, vice Outlook Express. Paul Johnson
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads