Damn COMM port on damn NT Workstation

[ermingut]

Program that works on 10 diferent Win95/win98 machines and uses serial communication thru COMM port doesn't work on Windows NT Workstation / Server

Please, send me some tips how to programm COMM the right way. I modyfied my code on and on and tested in NT but with no success.

Please help before I buy new disk and install NT Workstation on it and run VB on it.

How my program works:

open comm port ...OK
send data to port ...OK
wait for 1s
on comm event
read data ... no data recieved

Thanks

[Paul282]

Are you using the MSComm Control?

It should be ok but otherwise you're probably hitting the NT HAL (Hardware Abstraction Layer)

[Chris]

If the comm port really receive data from others terminal, then it should fire the comEvReceive events and then only you start retrieving the data by calling a function that sit under the comEvReceive event.

May be after your program wait for 1sec, then check the comm port input buffer count. If it is equal to 0 that mean your comm port does not receive any data. But make sure you have clear the inputbuffer count to zero after each time you sedn data.

As I know, a standard Comm port communication should wait for 3 sec, before it decide whether resend the previous data or skip the current data and send the next data.

Or you can refer to the sample code at the following thread
http://forums.vb-world.net/showthrea...threadid=17607

Hope this can help you.

[ermingut]

Yes I use MScomm.


I really did't try comEvReceive event. I will try it.

Bit it's funny that on Win95/98 works fine.


U asked me if I use MScomm. The answer is yes. That leads me to the other question. Is there a substitute for MScomm.

thanx

[Asterix]

Hi I have used SI_COMM 32Bit ActiveX from "Software InnoVations Inc." because I had the same problem u got and it works great.