Article View: borland.public.cppbuilder.internet.socket
Article #4784Re: Indy60.bpl error
From: Tumurbaatar S.
Date: Tue, 14 Dec 2004 03:42
Date: Tue, 14 Dec 2004 03:42
44 lines
2611 bytes
2611 bytes
I did search on *indy* and found a few files from old Indy8 and deleted them. The most important from found files was indy.bpi. I removed from project file any reference to indy.bpi and now all work! Thank you! "Tumurbaatar S." <nospam_tumur@magicnet.mn> wrote in message news:41be5831@newsgroups.borland.com... >I did so. Searched BCB6 main dir for below files and deleted them: > > dclindy*.bpl, dclindy.*, dclindy*.bpl, indy*.lib, id*.pas, id*.hpp, > id*.obj, and id*.dcu > > Of course, except of idpas32.obj. I placed extracted files in > BCB/Indy/Source and make batch compiled files to BCB/Indy/C6. > So now all files matching above wildcards are located in BCB/Indy/C6 > and BCB/Indy/Source. Searching does not find any more files except > within these 2 dir-s. > > > > "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message > news:41bd8484@newsgroups.borland.com... >> >> "Tumurbaatar S." <nospam_tumur@magicnet.mn> wrote in message >> news:41bd7091@newsgroups.borland.com... >> >>> The procedure entry point @Idwinsock@initialization$qqrv >>> could not be located in the dll indy60.bpl >> >> BCB6 ships with Indy 8, which is not compatible with Indy 9. That error >> is >> a result of you still having the old Indy 8 files present on your >> machine. >> You must remove the old Indy 8 files before Indy 9 will work properly. >> Please go to Indy's website and read the Knowledge Base, there are >> detailed >> instructions provided. >> >> >> Gambit >> >> > >
Technical Details
Message-ID:
<41be6122@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!newsfeed.icl.net!newsfeed.freenet.de!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!pe2.news.blueyonder.co.uk!blueyonder!news-peer-test!btnet!newsfeed.bt.es!caladan.landsraad.net!newsgroups.borland.com!not-for-mailReferences:
<41bd7091@newsgroups.borland.com> <41bd8484@newsgroups.borland.com> <41be5831@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,e43d64d615afbb58 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Tumurbaatar S." <nospam_tumur@magicnet.mn> Newsgroups: borland.public.cppbuilder.internet.socket References: <41bd7091@newsgroups.borland.com> <41bd8484@newsgroups.borland.com> <41be5831@newsgroups.borland.com> Subject: Re: Indy60.bpl error Date: Tue, 14 Dec 2004 11:42:19 +0800 Lines: 46 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-RFC2646: Format=Flowed; Response NNTP-Posting-Host: 202.131.2.5 Message-ID: <41be6122@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1102995746 202.131.2.5 (13 Dec 2004 19:42:26 -0800) Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!proxad.net!newsfeed.icl.net!newsfeed.freenet.de!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!pe2.news.blueyonder.co.uk!blueyonder!news-peer-test!btnet!newsfeed.bt.es!caladan.landsraad.net!newsgroups.borland.com!not-for-mail