"constantcomputertrouble" wrote:
> I am running Windows XP Home. When I log on to my computer, I get the
> following error code:
>
> Cannot find import; DLL may be missing, corrupt, or wrong version
> File "rtl70.bpl", error 126
>
> I tried to load my antivirus/spyware program, and I got the same error.
> Even when I signed into this forum, I got the error.
>
> I have tried to use my System Restore several times, now, but to no avail.
>
> I have also tried to use the Recovery Console program, but it isn't
> accepting my Administrator password (of which there is and has always been
> only one).
>
> I have run the installation CD, looking for the "repair missing files"
> section, but I can't find it anywhere.
>
> I can't run any antivirus or antispyware programs, because I keep getting
> this error. I don't know how many other programs this error will appear on,
> as I haven't tried to do anything more than seek help with this.
>
> please give me quastion
How can I replace the file, I have tried restore before with bad results.
It seemed to occur just after I tried to uninstall Spyware Doctor. Now my
sound for streaming videos will not work but the sound works for Media Player
and Quick Time. Neither will my magic jack phone ring anymore.
Does anyone have a good fix for this problem?
A lot of 3rd party programs are written in Borland's Delphi or C builder
environements. These 3rd party programs may also incorporate other 3rd party
design time / run-time components. Those components are compiled into a Run
Time Library, hence the rtl prefix. the 70 comes from the version of Delphi
the developer is using. The .bpl is the Borland Pascal Library. AKA Borland
Project Library.
The short of it is whatever application generated the error is poorly
written. as the end user you should never see that "error 126". They do not
have a complete error trapping code block or take into consideration all the
possible outcomes for error trapping and presenting the user with the
appropriate (or as appropriate as possible) dialog box with more information.
The Application is attempting to access the bpl (almost always during
application startup) and call a procedure that is failing. The procedure
either requires another file that is missing, or the application (and
run-time component that came with it) is failing because it was never
designed or tested to work with a particular operating system or service pack
release level.
Best fix, contact the offending softwares manufacturer for the fix, if it
even exists. If a newer version of the software exists update it. if that
doesn't work rip it out and find a suitable working replacement.
Apps using the older .bpl's may start developing problems on newer versions
of the Windows OS's. OS's now are a LOT different than what they were in the
late 90's.
There several other radical options if you really need to get a unique app
running and vendor no longer exists. But that's another explanation.