"John Carlyle-Clarke" <jpcc@removethis.bigfoot.com> wrote in message
news:Xns97C13D9EA16Adiscombobulation@207.105.83.66...
> The source options available on www.indyproject.org seem to
> be Version 10.0.52 or the bleeding edge straight from CVS files.
10.1.5 is the CVS version, which you can download from StarTeam directly, or
through one of the mirrors that are updates nightly.
> I am getting an access violation now, at the same spot. It is in
> TIDThread.Execute, and it is the last line of this section:
TIdThread.Run() is an abstract method. TIdThreadWithTask overrides
TIdThread.Run() to call TIdTask.DoRun(), which calls TIdTask.Run().
TIdContext derives from TIdTask and overrides Run() to trigger the
TIdContext.OnRun event handler. TIdCustomTCPServer assigns a handler to the
TIdContext.OnRun event to trigger the TIdCustomTCPServer.OnExecute event
handler. If you are getting an AV in Run(), there are only three places it
could be occuring:
1) TIdThreadWithTask.Run() when calling TIdTask.DoRun() on an invalid
TIdTask pointer. Highly unlikely.
2) TIdContext.Run() when it checks the connection state after the OnRun
event handler has exited. Also highly unlikely
3) in your own OnExecute event handler code. Very probable.
> > Indy 10 doesn't use the FileCtrl unit anymore. You probably
> > still have older Indy files on your machine that you did not remove.
>
> I don't think so...
There is no way you can be getting a FileCtrl error with the latest files.
As I said earlier, Indy 10 does not have any references to the FileCtrl unit
at all anymore.
> When I've uninstalled Indy and deleted the folder, then
> installed 10.1.5, the file IdSysVCL contains this code:
That is not the latest version of IdSysVCL.pas. The current version of
IdSysVCL.pas starts out as follows instead:
unit IdSysVCL;
interface
{$I IdCompilerDefines.inc}
uses
{$IFDEF DOTNET}
System.IO,
{$ENDIF}
{$IFDEF MSWindows}
Windows,
{$ENDIF}
IdSysBase,
SysUtils;
As you can see, there is no reference to the FileCtrl unit anymore.
Gambit
