TZUTC: 1000   
   MSGID: 655.fdn_dbridge@3:633/509 23116938   
   REPLY: 1:229/426 722C6086   
   PID: Synchronet 3.17c-Linux  Mar 11 2020 GCC 8.3.0   
   TID: SBBSecho 3.10-Linux r3.151 Mar 11 2020 GCC 8.3.0   
   CHRS: CP437 2   
   NOTE: SlyEdit 1.72 (2020-03-04) (ICE style)   
     Re: Re: Working with QICO   
     By: Nick Andre to Deon George on Fri May 01 2020 02:11 am   
      
   Hey Nick,   
      
    NA> While I respect and encourage experimentation with DB, unfortunately I   
    NA> cannot offer much tech-support for that configuration. DB is an MS-DOS   
    NA> program written in the days of IBM XT's with limited spec... a lot of   
    NA> assembly language timing and trickery done for Zmodem and other things. It   
    NA> was never written to specifically support Dosemu or Tcpser.   
      
   Sure OK. DBridge works fine with dosemu and tcpser - I had it transferring no   
   trouble at all with IFICO. My question really was would you know of reasons   
   why it wasnt working with QICO - since it is an EMSI mailer (fsc-0056.001) and   
   FrontDoor and Portal were working fine.    
      
   So I turned on serial port tracing of tcpser to watch what was going back and   
   forth to see if there was something wrong with the protocal exchange and which   
   side it was. (I did the same for zmodem and fixed it in qico.)   
      
   I noticed Dbridge reporting some strange sequences of chars, followed by "to   
   Ezycom", followed by "Swap Error" in the EMSI_DAT exchange. Given that I didnt   
   think DB knew about my Ezycom, that lead to wonder if DB was pointing a   
   variable to a bad memory location.   
      
   (I was playing with exiting to a BBS, hence my other messages around *L and   
   *H.)   
      
   There seemed to be an EMSI exchange a few times, so maybe the CRC that was   
   qico calculated didnt match what DB had calced for the EMSI_DAT?   
      
   So I rebooted the dosemu environment, and it then worked. I will play with it   
   a bit more and if it resurfaces, perhaps there is a usage of a variable that   
   hasnt been initialised yet - and thus points to invalid data? (I'm just   
   guessing...)   
      
   I have the serial exchange log if you are interested.   
   ...ëîåã   
      
   ... An independent is a guy who wants to take the politics out of politics.   
   --- SBBSecho 3.10-Linux   
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)   
   SEEN-BY: 1/123 90/1 120/340 601 226/30 227/114 229/101 426 664 1014   
   SEEN-BY: 240/5832 249/1 206 317 400 280/464 292/854 317/3 322/757   
   SEEN-BY: 342/200 633/0 267 280 281 412 416 509 640/1384 712/848   
   PATH: 633/509 280 229/426