"Jamie Dale" <j.dale@turboz.net> wrote in message
news:447f5fba@newsgroups.borland.com...
> Delphi 2005 is not capable of what Borland so proudly boasted.
In what regard exactly? Have you considered upgrading to Delphi 2006?
> I hear C# and VB are the way forward.
Says who?
> After years of happy memorys with Delphi 6, I am sorry to say D2005 has
> become a very harsh disappointment.
Then try Delphi 2006 before you decide to abandone it altogether.
> I have tried installing every download that the Indy website has to offer.
>
> I have offered remote desktop access for anyone that thinks
> that they can help.
Did you try contacting the Indy Experts program yet?
http://www.atozed.com/indy/experts/
Did you try contacting the Indy developers directly in Indy's own
newsgroups? news://news.atozed.com
> I have put up with being told off for not explaining things clearly
(Despite
> describing in detail and even providing screen captures).
You did not provide any details about your IDE setup. You did not provide
step-by-step details of everything you tried. Your screenshots were useless
without adequate context.
> It would appear D2005 has screwed over my other machine as a
> system service I wrote in D6 is no longer working the way it should.
Please elaborate. The VCL's service architecture has not changed at all
since D4, which it was first introduced.
> DELPHI 2005 FOR .NET SUX.
Try Delphi 2006 for .NET. It is much better.
> Why do I need VCL version of Indy for .NET instead of .NET version?
Indy for VCL supports all Borland environments, including Delphi.NET, and
some third-party non-Borland environments (.NET, Mono, Linux, Unix, Mac,
etc).
Indy for .NET is a C# port of Indy and is specifically for native .NET
environments only.
Gambit
