Loading ...
Sorry, an error occurred while loading the content.

22178Re: [aprsisce] Explicit message when port can't be opened

Expand Messages
  • Rob Giuliano
    Jan 27, 2013
    • 0 Attachment
      If the issue is with the PC, maybe the solution is also with the PC?
      This seems to come up a lot.
      I know there are ways of configuring thumb drives to always be a particular drive letter, maybe there is a mechanism to force the interface to always be a certain comm port -> there is in Linux, based on parameters that are supplied by the USB device.
      I haven't looked, but I might suggest a web search on the subject.
      Maybe a request into Microsoft.
      Robert Giuliano

      From: Tony VE6MVP <tony@...>
      To: aprsisce@yahoogroups.com
      Sent: Saturday, January 26, 2013 6:01 PM
      Subject: [aprsisce] Explicit message when port can't be opened

      For unknown reasons my PC will sometimes change the COM port on me on a reboot.   However APRSIS32 doesn't give an explicit message stating it couldn't open the port.   Of course I do see some differences on the screen when this happens but they can be subtle at times.  For example nearby RF stations don't have the *2 behind the call sign.  In my opinion I feel it would be better to give the user an explicit message when a com port can't be opened.

      Below is a sample log file entry

      Port(KwdD710):2013-01-26T22:51:28.851 Opening COM22:9600,N,8,1
      Port(KwdD710):2013-01-26T22:51:28.851 Opening COM22 with 4 Args
      Port(KwdD710):2013-01-26T22:51:28.851 Opening COM22 Got -1 Error 2
      Port(KwdD710):2013-01-26T22:51:28.851 Status 0 Error 0 At 228 in c:\compass\code\aprs\aprsisce\cprtns.c
      Port(KwdD710):2013-01-26T22:51:28.851 Error Opening COM22:9600,N,8,1 LastError 0

    • Show all 34 messages in this topic