Clipper 2 ADS

[Maarten Roos]

Is there somebody who can help me what to do to have a Clipper app run with ADS?
I have read about the following lib's:
axipbcom
axipcomm
axipxcom
Something about:
ADSDOSIP?
But... I cannot find a good documentation how to setup? I can't even find that ADSDOSIP?
Maarten

[jfgimenez]

Maarten,
> Is there somebody who can help me what to do to have a
> Clipper app run with ADS?
>
> I have read about the following lib's:
> axipbcom
> axipcomm
> axipxcom
>
> Something about:
> ADSDOSIP?
>
> But... I cannot find a good documentation how to setup? I
> can't even find that ADSDOSIP?
I'm not an ADS expert, but AFAIK, you only need these DLLs (copy them into
the same folder that the executable):
- ace32.dll (always needed)
- adsloc32.dll (only for local access)
- axcws32.dll (only for remote access)
--
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

[nospam]

Marteen:
Greetings from your local ADS advisor.
You see:
Back in the early days of ADS, it was designed to run with Clipper but
only under Novell's IPX protocol.
However, later on, Windows servers came in and were adopted by ADS, and
IP protocol was adopted by Novell also, but clipper programs were still
attached to the DOS NetBios layer to connect to the server.
Under Windows, DOS based programs connect to the server using a NetBios
layer, not a real a TCP/IP comm protocol is used in windows terminals to
access a mapped drive.
This is where the ADSDOSIP.EXE program goes into stage.
ADSDOSIP.EXE is a windows based program that allows a Clipper ADS Client
to comunicate to the server using IP protocol, since MS-DOS doesn't
support real TCP/IP communications, ADSDOSIP will recieve the packages
comming from the Clipper program, "translate" them to IP, and send them
to the server, obviously the packets comming from the server are
recieved via IP and send to the Clipper programm.
You must run the ADSDOSIP.EXE program PRIOR any Clipper ADS Client, in
order to connect to the server and have access to the data.
ADSDOSIP.EXE uses both ADS DLLs: AXWCS32.DLL and ACE32.DLL, and is
configured using an ADS.INI file (for more information regarding ADS.INI
file refer to the ADS manual).
Where is ADSDOSIP ?
IP Support is not installed by default when you run a "Typical" ADS
Clipper client installation, you must select "PERSONALIZED" installation
and select IP Support when installing. A a new folder is created and the
necesary files to use IP protocol with Clipper are copied to that
folder, including ADSDOSIP.EXE.
The folder contains the lib files you mention, axipbcom.lib is the lib
to use when linking with Blinker in both, real and protected mode.
Axipcomm.lib is used when linking with RTLINK, not protected mode is
supported so you will have to overlay some files, finally Axipxcom.lib
is used with Exospace linker for protected mode.
Linking files samples are provided in the same folder for different
linkers, please be aware to follow the linking steps EXACTLY as they are
shown in the samples, if you change anything, for example commands (LIB
for SEARCH or viceversa) or files order, you will not have a right EXE file.
These link files (.LNK) shown which libraries are needed to build the
exe to be used with ADSDOSIP.EXE
Once built your EXE, run the ADSDOSIP.EXE first, you will see a blue two
headed arrow on the taskbar, which means that the ADSDOSIP is running
and now run your Clipper IP program, it should connect to the server.
You may think that adding an extra comm layer when running your clipper
program decreases the speed, you are right, a Clipper app performance
using ADSDOSIP, may be (very) slower than a normal non-ADSaware Clipper
program.
In order to solve this issue, Clipper slow performance using ADSDOSIP,
ADS has a revisted ADSDOSIP.EXE version, which is hidden in the ADS
support web, it's a little hard to find where is it in the ADS website
and what for is it used, so this is the link:
http://devzone.advantagedatabase.com/Co ... roject.asp x?ProjID=138
You will find here a new version of ADSDOSIP.EXE which solves the
slowness issue in previous versions, change the ADSDOSIP that comes with
the Clipper client with the one downloaded from here and your apps will
speed up (really speed up), fasten your seat belt and prepare to enjoy
Clipper apps at the speed of ADS.
Xailer and (x)Harbour programms don't need this. Since they are 32 bits
windows applications, they use the native ADS client, the AXWCS32.DLL
and the ACE32.DLL.
Regards
Rene Flores
http://www.ciber-tec.com
El 04/08/2010 05:29 a.m., Maarten Roos escribió:
> Is there somebody who can help me what to do to have a
> Clipper app run with ADS?
>
> I have read about the following lib's:
> axipbcom
> axipcomm
> axipxcom
>
> Something about:
> ADSDOSIP?
>
> But... I cannot find a good documentation how to setup? I
> can't even find that ADSDOSIP?
>
> Maarten

[Maarten Roos]

Thanks for the info and help guys.
IP Support is not installed by default when you run a "Typical" ADS Clipper client installation, you must select "PERSONALIZED" installation and select IP Support when installing.
I didn't see this option come by? I had a plain install of ADS and that was all folks.

[ignacio]

Rene,
Thank you for your great explanation.
Regards,
"René Flores <"rflores" <nospam> escribió en el mensaje de
noticias:[email=4c5ba217@svctag-j7w3v3j....]4c5ba217@svctag-j7w3v3j....[/email]
> Marteen:
>
> Greetings from your local ADS advisor.
>
> You see:
>
> Back in the early days of ADS, it was designed to run with Clipper but
> only under Novell's IPX protocol.
>
> However, later on, Windows servers came in and were adopted by ADS, and IP
> protocol was adopted by Novell also, but clipper programs were still
> attached to the DOS NetBios layer to connect to the server.
>
> Under Windows, DOS based programs connect to the server using a NetBios
> layer, not a real a TCP/IP comm protocol is used in windows terminals to
> access a mapped drive.
>
> This is where the ADSDOSIP.EXE program goes into stage.
>
> ADSDOSIP.EXE is a windows based program that allows a Clipper ADS Client
> to comunicate to the server using IP protocol, since MS-DOS doesn't
> support real TCP/IP communications, ADSDOSIP will recieve the packages
> comming from the Clipper program, "translate" them to IP, and send them to
> the server, obviously the packets comming from the server are recieved via
> IP and send to the Clipper programm.
>
> You must run the ADSDOSIP.EXE program PRIOR any Clipper ADS Client, in
> order to connect to the server and have access to the data.
>
> ADSDOSIP.EXE uses both ADS DLLs: AXWCS32.DLL and ACE32.DLL, and is
> configured using an ADS.INI file (for more information regarding ADS.INI
> file refer to the ADS manual).
>
> Where is ADSDOSIP ?
>
> IP Support is not installed by default when you run a "Typical" ADS
> Clipper client installation, you must select "PERSONALIZED" installation
> and select IP Support when installing. A a new folder is created and the
> necesary files to use IP protocol with Clipper are copied to that folder,
> including ADSDOSIP.EXE.
>
> The folder contains the lib files you mention, axipbcom.lib is the lib to
> use when linking with Blinker in both, real and protected mode.
> Axipcomm.lib is used when linking with RTLINK, not protected mode is
> supported so you will have to overlay some files, finally Axipxcom.lib is
> used with Exospace linker for protected mode.
>
> Linking files samples are provided in the same folder for different
> linkers, please be aware to follow the linking steps EXACTLY as they are
> shown in the samples, if you change anything, for example commands (LIB
> for SEARCH or viceversa) or files order, you will not have a right EXE
> file.
>
> These link files (.LNK) shown which libraries are needed to build the exe
> to be used with ADSDOSIP.EXE
>
> Once built your EXE, run the ADSDOSIP.EXE first, you will see a blue two
> headed arrow on the taskbar, which means that the ADSDOSIP is running and
> now run your Clipper IP program, it should connect to the server.
>
> You may think that adding an extra comm layer when running your clipper
> program decreases the speed, you are right, a Clipper app performance
> using ADSDOSIP, may be (very) slower than a normal non-ADSaware Clipper
> program.
>
> In order to solve this issue, Clipper slow performance using ADSDOSIP, ADS
> has a revisted ADSDOSIP.EXE version, which is hidden in the ADS support
> web, it's a little hard to find where is it in the ADS website and what
> for is it used, so this is the link:
>
> http://devzone.advantagedatabase.com/Co ... roject.asp x?ProjID=138
>
> You will find here a new version of ADSDOSIP.EXE which solves the slowness
> issue in previous versions, change the ADSDOSIP that comes with the
> Clipper client with the one downloaded from here and your apps will speed
> up (really speed up), fasten your seat belt and prepare to enjoy Clipper
> apps at the speed of ADS.
>
> Xailer and (x)Harbour programms don't need this. Since they are 32 bits
> windows applications, they use the native ADS client, the AXWCS32.DLL and
> the ACE32.DLL.
>
> Regards
>
> Rene Flores
> http://www.ciber-tec.com
>
> El 04/08/2010 05:29 a.m., Maarten Roos escribió:
>> Is there somebody who can help me what to do to have a
>> Clipper app run with ADS?
>>
>> I have read about the following lib's:
>> axipbcom
>> axipcomm
>> axipxcom
>>
>> Something about:
>> ADSDOSIP?
>>
>> But... I cannot find a good documentation how to setup? I
>> can't even find that ADSDOSIP?
>>
>> Maarten
>