🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.internet.socket
Article #4973

Re: indy 9.00.15 Winsock.h vs. Winsock2.h TROUBLE

#4973
From: Frank
Date: Tue, 23 Nov 2004 09:33
33 lines
2732 bytes
> > I'm working on an restriced account (win2k system, bcb 6)
> > and tried to install 9.0.17 and 9.0.18 under administrator rights,
> > I was not able to do that in a fast way, because of trouble with
> > pascal units.
>
> Again, I ask you to provide SPECIFIC details.  Being vague is not a very
> helpful way to fix the problem.

sorry my english is not the best, but i will try...
the most trouble i had was converting the delphi project files into builder
ones.
with 9.0.17 and 9.0.18 the components were not visible in the IDE components
toolbar, installation of package works, no components even after extra
installation of them.

> > Indy - team should write that existing project need the indy.bpi
> > before they do the advice to delete all existing indy files, which is
> > written in the online install notes
>
> You should not even have the IDE running at all when you delete the files.
> The BPI is only used when the IDE is running and projects are loaded in
it.
> If you delete the files and install Indy while the IDE is not running at
> all, the BPI is created and installed for the IDE to use.


Maybe I'm wrong but the version i installed did not create an indy.bpi! It
creates an dclIndy60.bpi and Indy60.bpi. The IDE was not running.
On Page: http://bdn.borland.com/article/0,1410,28154,00.html is reportet
that projects needs bpi's that were located on the system when they were
created also if they don't use them.

Ps.: Can't help me to find the units that uses winsock1 ?
Technical Details
Message-ID: <41a303ec@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!feeder.enertel.nl!nntpfeed-01.ops.asmr-01.energis-idc.net!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!npeer.de.kpn-eurorings.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail
References: <41a1d512$1@newsgroups.borland.com> <41a22a04$1@newsgroups.borland.com> <41a2ec25$1@newsgroups.borland.com> <41a2f308$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,f39eb52eec8e73c6
X-Google-Attributes: gid11508e,public
X-Google-Language: ENGLISH,ASCII-7-bit
Reply-To: "Frank" <frank.hofmann@stahlwerk-thueringen.de>
From: "Frank" <frank.hofmann@stahlwerk-thueringen.de>
Newsgroups: borland.public.cppbuilder.internet.socket
References: <41a1d512$1@newsgroups.borland.com> <41a22a04$1@newsgroups.borland.com> <41a2ec25$1@newsgroups.borland.com> <41a2f308$1@newsgroups.borland.com>
Subject: Re: indy 9.00.15 Winsock.h vs. Winsock2.h TROUBLE 
Date: Tue, 23 Nov 2004 10:33:25 +0100
Lines: 35
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: 195.124.129.3
Message-ID: <41a303ec@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1101202412 195.124.129.3 (23 Nov 2004 01:33:32 -0700)
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!feeder.enertel.nl!nntpfeed-01.ops.asmr-01.energis-idc.net!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!npeer.de.kpn-eurorings.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail