| ??? 09/13/06 09:32 Read: times  | 
#124170 - Found the Solution !!! Responding to: ???'s previous message  | 
Hi Forum Members,
 After Burning a lot candles for overnight study, ultimately I got the solution to the problem. And the Solution is: Problem Area: The statement MSComm1.ReplaceParity="" was placed in the code where the serial port is initialized. The reason why it was used: The instrument was sending the Data with "9600,O,8,1" but it is giving parity error for every byte that is recieved. Hence to disable this parity error I used the Above command in the code. Problem: This command works properly with Windows98, but for Windows XP it forcibly replaces the charachter (having Parity Error) with &h27. This is the code for chr(&h27) = "'". Solution: 1.I had to comment out this statement for applications that use WindowsXP, and enable it for Windows9x. 2.There is another way that works and that is for the MSComm object , right click->Properties and delete the charachter for ParityReplace. This also works fine. So like many other problems created by Microsoft (due to upgrade in MSComm32.OCX), we have a solution. Bye, Mr. Kiran V Sutar Mumbai, INDIA  | 
| Topic | Author | Date | 
| Problems with MSComm32 under WindowsXP | 01/01/70 00:00 | |
| I would try... | 01/01/70 00:00 | |
   Found the Solution !!!        | 01/01/70 00:00 | 



