??? 05/10/04 16:07 Read: times |
#70127 - RE: another microsoft bug: delay (50) Responding to: ???'s previous message |
Hi Van....
Thanks for your reply. I have some suggestions and questions: Suggestion 1: You said: Please mind your language, this is a public forum, and I do not expect such language be used on this professional forum. Mr. Charles Bannister and other senior members of this forum, Please reply your comments on the language. Suggestion 2: Looking at your reply, I feel that I have hurt your feelings a lot. My apologies to you and am sorry if I have done so. Please understand that, I have done some experiments regarding the delay(50) and have faced the errors. For your reference, I am posting the source code and the observations of this test. Please go through it thoroughly, and test it yourself, and compare the results with my results. I had asked for help from VB gurus and came to a blank. Sorry, I was not able to take help from you at that time. Better late than never. Please inform me if I have done anything mistake. Suggestion 3: I know this is 8052 forum, so discussing VB related matters is out of scope of this forum, but the routines which I have used are the most common routines, which anybody using MCS-51 for PC communication (in Windows, through VB) might use. This thread started by pointing out the issue of RTS in Windows through VB. Similarly, as per the experience of the original poster, even I have found a common problem with Windows, and so I have raised this point of delay(50). Suggestion 4: I know in my earlier posts, I had written as delay(50), instead it is Sleep(100). It has been a long time (more than a year) since I had done that test, so I had forgotten the details, including the exact command. Please forgive me for this mistake. And please treat my earlier references to delay(50) as Sleep (100). I am not able to post the whole message, hence I am sending it in parts... continued on next post ...2 |