Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TpaPro install on BCB6

Status
Not open for further replies.

Totte

Programmer
Jun 6, 2001
317
SE
I would like to install the TurboPower Async Professional package on BCB6 but none of the files is applicable when i try to install as a package. Any tips?

Totte
Keep making it perfect and it will end up broken.
 
Dear Totte,

as far as I know, TPApro stopped being developped for BCB with version 5, when You have a version from turbopower.

when You have one from sourceforge, You might be luckier.


try the following newsgroup:
turbocontrol.apro.general
and check for questions like yours (installing the sourceforge package).
find the "latest" available (now free) version of apro at
and feel free to develop it further...

Please let us all know, whether You could find a way to install apro on BCB6!!

Michael
 
Thanks, i will try and i will reach the goal!!!!

I'll keep you posted.

I've using the sourceforge-version by the way and the newsgroup "turbocontrol.apro.general" seems to be non existant......

But hey, i'n not into newsgroups so i might do something wrong.

Totte
Keep making it perfect and it will end up broken.
 
Dear Totte,

I am using since a while iexplorer to view this tektips, as my netscape 4.7 wont display all ok.

when I then try to get into the newsgroups, Outlook express will open :(

So, try to go to the following adress within a non-IE browser and get into the
news://news.turbocontrol.com
there You will find a subgroup
turbocontrol
which is support follower of turbopower.

there You will find the turbocontrol.apro.general

good luck!

michael



 
I'm using Async Pro with BCB 6 that I downloaded from Source Forge. It works great. Much better than most of the other TurboPower components as a matter of fact. What kind of problems are you having?


James P. Cottingham
[sup]
There's no place like 127.0.0.1.
There's no place like 127.0.0.1.
[/sup]
 
finnmike: thanks, i will do that.

2ffat: i need to communicate with various equipments through the serial port. When i used BCB3 (ahhhh, the good old days....) i installed TpaPro but if Async Pro is OK i'll give a go.

Prior to TpaPro i actually did it the hard way and opened the port as a "file" and such, quite tedious!

So, without further ado i'll D/L Async Pro and installs it.

Best regards.

Totte
Keep making it perfect and it will end up broken.
 
Boy, am i tired.....

TpaPro = TurboPower Async Pro..... *blushing*

2ffat: My problem is HOW to install it into BCB6, when i want to install a component package it lacks ALL *.bpl or *.bpc files and i can't remember how to make them... :-(
Could you kick the lower rear part of my anatomy with a few guidelines?

Totte
Keep making it perfect and it will end up broken.
 
The following is from the ReadMe.txt file for Async Pro 4.06.
1. Introduction

Async Professional is a comprehensive communications toolkit for Borland Delphi, C++Builder, & ActiveX environments. It provides direct access to serial ports, TAPI, and the Microsoft Speech API. It supports faxing, terminal emulation, VOIP, & more.

This is a source-only release of TurboPower Async Professional (APRO). It includes designtime and runtime packages for Delphi 3 through 7 and C++Builder 3 through 6.

For help files and a PDF manual, please see the tpapro_docs package on SourceForge (
==============================================

2. Package names


TurboPower APRO package names have the following form:

ANNNMKVV.*
| |||
| ||+------ VV VCL version (30=Delphi 3, 40=Delphi 4, 70=Delphi 7)
| |+------- K Kind of package (R=runtime, D=designtime)
| +-------- M Product-specific modifier (typically underscore, V = VCL, C = CLX)
+----------- NNN Product version number (e.g., 406=version 4.06)


For example, the APRO designtime package files for Delphi 7 have the filename A406_D70.*.

The runtime package contains the core functionality of the product and is not installed into the IDE. The designtime package references the runtime package, registers the components, and contains property editors used in the IDE.

==============================================

3. Installation


To install TurboPower APRO into your IDE, take the following steps:

1. Unzip the release files into a directory (e.g., d:\apro).

2. Start Delphi or C++Builder.

3. Add the source subdirectory (e.g., d:\apro\source) to the IDE's library path.

4. Open & compile the runtime package specific to the IDE being used.

5. Open & install the designtime package specific to the IDE being used. The IDE should notify you the components have been installed.

Make sure you have downloaded version 4.06 from Then following the above step very closely. Post here if you have problems and I'll pull out my notes.

I really didn't have any problems with Async or Flash Filer but I had a lot of problems installing packages like Orpheus, Shell Shock, etc.

James P. Cottingham
[sup]
There's no place like 127.0.0.1.
There's no place like 127.0.0.1.
[/sup]
 
Sigh.....

OK, now it's official: I DID IT WRONG!!!! STUPID ME!!!

But: now i did right!

Here goes:
D/L the .ZIP-file, extract it with path structure.
Start BCB6 (in this case).
Now go: 'Component'->'Install Component...'->'Into New package'.
In 'Package file name' browse to the 'TPAPro\Packages' library and select the correct unit.
In 'Unit File name' select the correct design time package.
Compile it. If you need to give some name do it.

When it's compiled klick the 'Install' button and *poooffff* You got TPAPro installed as a component.

It sure helps with at good nights sleep ;-)

Totte
Keep making it perfect and it will end up broken.
 
BTW, I'm finishing a major application that uses 4 Async Com port componets (for COMs 1 - 4) and a packet component. Very slick :) . Almost too easy.

James P. Cottingham
[sup]
There's no place like 127.0.0.1.
There's no place like 127.0.0.1.
[/sup]
 
Hej 2ffat,
are you also using the tapi component?

I have some liittle problems with the tapiservers on XP, have You heard about that?

regards

michael
 
To James P. Cottingham and Michael
I have a BIG problem with tapi server on Windows 98.

The same version of Async pro (4.06) returns receive different respond from modem.

In Windows 2000 SP2 (3 Packets)
OK
<Packet>
OK
OK
<Packet>
OK
OK
<Packet>
OK

In Windows 98 SE
OK
<Packet>
OK
<Packet>
OK
OK
<Packet>
OK

So as you see it some times loses "OK".
And I can't destinguish this packet from the flow, becouse APRO rely on stable format of the packet.
OK - begin of packet
<Packet> - body
OK - end

Can you advice something to me?
 
Just a question: do you use the same modem in both cases? Not equal but the _very_same_ modem???

Modems can be set to answer differently on same answers....

From your setup i understand that you do some modem-setup-communication and the modem could answer different depending on setup.

Totte
Keep making it perfect and it will end up broken.
 
Another question, are you using TAPI's packet protocol? If so, what are your paramaters to define when the packet begins and ends. I've not used Win98 for some time so I haven't written anything for it using TAPI.

James P. Cottingham
[sup]
There's no place like 127.0.0.1.
There's no place like 127.0.0.1.
[/sup]
 
To Totte:
It was the very same modem. I use standard 14.400 modem driver in both cases.
OF course, as far as TAPI is part of operation system, there were 2 different version of TAPI 4.xxxx and 5.xxxx.

I need perform communications between to stations.
1st station establishes connection and send data packet.
2nd station receives it and sent predefined data packet back
and 1st receive described above sequences from modem

to James P. Cottingham
I use APRO DataPacket and define start and end of a packet as "OK".
 
I use APRO DataPacket and define start and end of a packet as "OK". That may be part of the problem. It seems to me that there was a problem mentioned if the start and stop of a packet is the same but I could be mistaken. Try changing them into different sequences and see what happens. A common one is <STX> for the start and <ETX> for the end. I've seen both the text characters as shown and the ascii characters "\x02" and "\x03".

I ran into a problem with using comma's. I had to use the comma as the end of the packet, include the string in the packet, and the start string is "scString" as a wildcard "?". I have to parse out the comma from the packet but it works.

James P. Cottingham
[sup]
There's no place like 127.0.0.1.
There's no place like 127.0.0.1.
[/sup]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top