We have an application that uses 4 rackmount modems ( 32 modems ) and works
just fine 99 percent of the time. Very occasionally we will get into a state
where we cannot initialize the modem from our apps ( we use the normal API’s
to open the device, flush the modem and write out an initialization
string ).
When we get into this state we can use Qtalk to open the device and it will
initialize just fine. Is anyone aware of something special that Qtalk is
doing when it opens a modem? Or any thoughts on what this might be?
Thanks
Sheldon Parkes
sheldon@onlinedata.com
Sheldon Parkes <sheldon@onlinedata.com> wrote:
We have an application that uses 4 rackmount modems ( 32 modems ) and works
just fine 99 percent of the time. Very occasionally we will get into a state
where we cannot initialize the modem from our apps ( we use the normal API’s
to open the device, flush the modem and write out an initialization
string ).
When we get into this state we can use Qtalk to open the device and it will
initialize just fine. Is anyone aware of something special that Qtalk is
doing when it opens a modem? Or any thoughts on what this might be?
Hm…replied elsewhere with link to qtalk source:
ftp.qnx.com:/usr/free/qnx4/os/utils/communication/misc/qtalk.tgz
Thanks
Sheldon Parkes
sheldon@onlinedata.com
–
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.