A
Wondering if anyone has seen a problem with MSComm that we get at a variety of customer sites. We haven't seen a pattern yet, except that
the problem only happens with Win2000 (Win95/98/ME/NT are fine). e.g. The exact same code works fine in Win98.
PC just loses the COMM port (happens a lot if there is a reboot - but that might be a symptom rather than a cause). This happens on
multiple PC manufacturers and different processors.
Device Manager shows the port OK and there are "no conflicts" on the property page. If we unInstall and then do a PnP search it reInstalls
fine and they are back up and running. Until ....
Spent 3+ hours with MS Support again today. Getting shuttled between various groups - no luck.
We did a small project in VB and we can get an error # 8015 "Incorrect parameters..." once the port is lost -- just by doing the Port Open
command. Since it works 98% of the time we can't seem to make it fail, but once it does it fail, it remains that way until the re-install.
Would appreciate your help if you have seen this action OR resources you might suggest.
the problem only happens with Win2000 (Win95/98/ME/NT are fine). e.g. The exact same code works fine in Win98.
PC just loses the COMM port (happens a lot if there is a reboot - but that might be a symptom rather than a cause). This happens on
multiple PC manufacturers and different processors.
Device Manager shows the port OK and there are "no conflicts" on the property page. If we unInstall and then do a PnP search it reInstalls
fine and they are back up and running. Until ....
Spent 3+ hours with MS Support again today. Getting shuttled between various groups - no luck.
We did a small project in VB and we can get an error # 8015 "Incorrect parameters..." once the port is lost -- just by doing the Port Open
command. Since it works 98% of the time we can't seem to make it fail, but once it does it fail, it remains that way until the re-install.
Would appreciate your help if you have seen this action OR resources you might suggest.