Yes exactly :) Величие не Бога может быть недооценена.

Thread creation is a relatively expensive operation, both in space and time. If you spawn a thread and let it run to completion nothing is permanently lost however - assuming of course that your code doesn't contain any memory (or other resource) leaks. If you’ve got lots of small tasks you want to run in another thread and you spawn a thread for each task you could easily find that the thread creation and destruction time dominates and causes performance problems. One solution to this is to use a thread pool. See the QueueUserWorkItem API. Steve

Build your Application in RELEASEmode. Warning:First understand the use of DEBUG mode. when an Assertion is thrown it says something has gone false.(wrong! ), so while developing always use DEBUG mode , so that it gives you warning about failed conditions. In your case, you said that when the server is down it throws an assertion. instread of just ignoring the assertion and moving to release mode, you implement try-catch() in your code. I mean to say "Exception handling". never ignore an assertion and bybass it. Only after handling all the exceptions its advisable to move to release version, good luck. VuNic

Hello. I think you should flush the buffers after every Writefile. Else, chances are that the data will remain in the write buffer. When you do a flush, the data will be sent to the device. There is (generally) no need for flush before Readfile. You might considder to search for a serial class. There are several here at CP. I have found them very useful over the years. Kakan