bpl troubble

  • Thread starter Thread starter Kristian Tollefsen
  • Start date Start date
K

Kristian Tollefsen

Guest
I resently tryd to use a work application on my laptop running xp64 but the
program gave me an error trying to install it saying the package wasnt for my
os, so i gave it a thought about installing it on another system runnning x86
artistructue and copy the install over.
Doing this the program started to complain about vcl50.bpl (bde /borland
database engine file) missing and that i need to reinstall the program, so i
copyed the file into c:\windows\system32 and tryd again, again it sayed
missing so i got the registry entrys from the other machine and inported
these but still no use

so is there any workarounds for these ore do i have to install another os
for work use?
 
RE: bpl troubble

Kristian:
1.- What application were you trying to install on your XP x64 laptop (name,
version, supported os's)?
2.- The problem that you have in the x86 system is that "vcl50.bpl" must not
be properly installed already. Just copying it into the system32 folder
doesn't imply it is "installed". You need an installation program for it. I
am not familiar with Borland Delphi so I can't help you further with this
vcl50.bpl file
3.- If you solve the vcl50.bpl issue in your x86 system you might try
installing the free MS application Virtual PC in your x64 laptop (host OS)
and later on installing XP x86 as a guest OS for supporting your x86 work
application.
Carlos

"Kristian Tollefsen" wrote:

> I resently tryd to use a work application on my laptop running xp64 but the
> program gave me an error trying to install it saying the package wasnt for my
> os, so i gave it a thought about installing it on another system runnning x86
> artistructue and copy the install over.
> Doing this the program started to complain about vcl50.bpl (bde /borland
> database engine file) missing and that i need to reinstall the program, so i
> copyed the file into c:\windows\system32 and tryd again, again it sayed
> missing so i got the registry entrys from the other machine and inported
> these but still no use
>
> so is there any workarounds for these ore do i have to install another os
> for work use?
 
Re: bpl troubble

If vcl50.bpl is a 32-bit dll it should be copied to C:\Windows\SysWOW64, not
C:\Windows\system32 which is for 64 bit processes under a 64 bit OS.


"Kristian Tollefsen" <KristianTollefsen@discussions.microsoft.com> wrote in
message news:0533493F-DD97-400E-A16C-B3174DCB4381@microsoft.com...
>I resently tryd to use a work application on my laptop running xp64 but the
> program gave me an error trying to install it saying the package wasnt for
> my
> os, so i gave it a thought about installing it on another system runnning
> x86
> artistructue and copy the install over.
> Doing this the program started to complain about vcl50.bpl (bde /borland
> database engine file) missing and that i need to reinstall the program, so
> i
> copyed the file into c:\windows\system32 and tryd again, again it sayed
> missing so i got the registry entrys from the other machine and inported
> these but still no use
>
> so is there any workarounds for these ore do i have to install another os
> for work use?
 
Re: bpl troubble

ofc i should have remembered
Moving the files into the syswow64 folder let me start the app but it starts
whit an error message: file name is too long or a paradox version 5.0 table.
I can use the program but i domt know if it works as its suppose to.
any idea on the last message?

Regards
Kristian

"Dominic Payer" wrote:

> If vcl50.bpl is a 32-bit dll it should be copied to C:\Windows\SysWOW64, not
> C:\Windows\system32 which is for 64 bit processes under a 64 bit OS.
>
>
> "Kristian Tollefsen" <KristianTollefsen@discussions.microsoft.com> wrote in
> message news:0533493F-DD97-400E-A16C-B3174DCB4381@microsoft.com...
> >I resently tryd to use a work application on my laptop running xp64 but the
> > program gave me an error trying to install it saying the package wasnt for
> > my
> > os, so i gave it a thought about installing it on another system runnning
> > x86
> > artistructue and copy the install over.
> > Doing this the program started to complain about vcl50.bpl (bde /borland
> > database engine file) missing and that i need to reinstall the program, so
> > i
> > copyed the file into c:\windows\system32 and tryd again, again it sayed
> > missing so i got the registry entrys from the other machine and inported
> > these but still no use
> >
> > so is there any workarounds for these ore do i have to install another os
> > for work use?
>
>
 
Re: bpl troubble

update:
The program do not work gives all kinds of errors related whit the
whit an error message: file name is too long or a paradox version 5.0 table

program folder\sysdata\circuitType.db
does this whit the other *.db stuff too

"Kristian Tollefsen" wrote:

> ofc i should have remembered
> Moving the files into the syswow64 folder let me start the app but it starts
> whit an error message: file name is too long or a paradox version 5.0 table.
> I can use the program but i domt know if it works as its suppose to.
> any idea on the last message?
>
> Regards
> Kristian
>
> "Dominic Payer" wrote:
>
> > If vcl50.bpl is a 32-bit dll it should be copied to C:\Windows\SysWOW64, not
> > C:\Windows\system32 which is for 64 bit processes under a 64 bit OS.
> >
> >
> > "Kristian Tollefsen" <KristianTollefsen@discussions.microsoft.com> wrote in
> > message news:0533493F-DD97-400E-A16C-B3174DCB4381@microsoft.com...
> > >I resently tryd to use a work application on my laptop running xp64 but the
> > > program gave me an error trying to install it saying the package wasnt for
> > > my
> > > os, so i gave it a thought about installing it on another system runnning
> > > x86
> > > artistructue and copy the install over.
> > > Doing this the program started to complain about vcl50.bpl (bde /borland
> > > database engine file) missing and that i need to reinstall the program, so
> > > i
> > > copyed the file into c:\windows\system32 and tryd again, again it sayed
> > > missing so i got the registry entrys from the other machine and inported
> > > these but still no use
> > >
> > > so is there any workarounds for these ore do i have to install another os
> > > for work use?
> >
> >
 
Re: bpl troubble

The problem is almost certainly that some of the files used by Paradox are
16 bit. There is NO 16 bit support in x64. Period. Your best solution is to
Virtual PC or Virtual Server and run the application in a virtual machine.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Kristian Tollefsen" <KristianTollefsen@discussions.microsoft.com> wrote in
message news:B0685A89-313A-4113-B7E9-88AFA3362EEC@microsoft.com...
> update:
> The program do not work gives all kinds of errors related whit the
> whit an error message: file name is too long or a paradox version 5.0
> table
>
> program folder\sysdata\circuitType.db
> does this whit the other *.db stuff too
>
> "Kristian Tollefsen" wrote:
>
>> ofc i should have remembered
>> Moving the files into the syswow64 folder let me start the app but it
>> starts
>> whit an error message: file name is too long or a paradox version 5.0
>> table.
>> I can use the program but i domt know if it works as its suppose to.
>> any idea on the last message?
>>
>> Regards
>> Kristian
>>
>> "Dominic Payer" wrote:
>>
>> > If vcl50.bpl is a 32-bit dll it should be copied to
>> > C:\Windows\SysWOW64, not
>> > C:\Windows\system32 which is for 64 bit processes under a 64 bit OS.
>> >
>> >
>> > "Kristian Tollefsen" <KristianTollefsen@discussions.microsoft.com>
>> > wrote in
>> > message news:0533493F-DD97-400E-A16C-B3174DCB4381@microsoft.com...
>> > >I resently tryd to use a work application on my laptop running xp64
>> > >but the
>> > > program gave me an error trying to install it saying the package
>> > > wasnt for
>> > > my
>> > > os, so i gave it a thought about installing it on another system
>> > > runnning
>> > > x86
>> > > artistructue and copy the install over.
>> > > Doing this the program started to complain about vcl50.bpl (bde
>> > > /borland
>> > > database engine file) missing and that i need to reinstall the
>> > > program, so
>> > > i
>> > > copyed the file into c:\windows\system32 and tryd again, again it
>> > > sayed
>> > > missing so i got the registry entrys from the other machine and
>> > > inported
>> > > these but still no use
>> > >
>> > > so is there any workarounds for these ore do i have to install
>> > > another os
>> > > for work use?
>> >
>> >
 
Back
Top