🚀 go-pugleaf

Hi,

I have made the changes from a server service developed on Indy 9 to Indy 
10, and is working ok(without fibers) on both development machine(winxp) and 
production (Win2003 server).

Now i have added the fibers components to the Service form and have linked 
them to each other to test fibers...
TIdSchedulerOfFiber,
TIdFiberWeaverThreaded,
TIdSchedulerOfThreadPool

On run time i create the TCPServer(more than one) and i have the following 
code :
TCPServer = new TIdTCPServer(NULL);
TCPServer->Active = false;
TCPServer->DefaultPort = PortNum;
TCPServer->OnConnect = MyIdTCPServerConnect;
TCPServer->OnDisconnect = MyIdTCPServerDisconnect;
TCPServer->OnExecute = MyIdTCPServerExecute;
TCPServer->Scheduler = indySchedulerOfFiberAlone; =>TIdSchedulerOfFiber

When i run the service under WinXp everything works ok....but under Win2003 
i get an exception and no connect or execute events are triggered.

If i comment the Scheduler assignment..it works with no problem under 
Win2003.

I'm have tried using the 10.x.52 and the latest snapshot.

Could be that i'm not using fibers in the correct way?

Thanks in advance

Omar Zelaya