Hi Nick,

Another question - I've been using QICO and DBridge cant talk to it (either receiving or initiating a connection) - would you know why? (FD and POP work fine).

An incoming QICO connections shows:
EMSI abort 6
EMSI/A1 sync failure

(It happily works with IFCICO - but IFCICO has other issues, so I was hoping to use QICO.)
...δεσπ



... One of the freedoms of the English is the freedom from culture.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

On 30 Apr 20 22:00:50, Deon George said the following to Nick Andre:

Another question - I've been using QICO and DBridge cant talk to it (either receiving or initiating a connection) - would you know why? (FD and POP wor fine).

As per my other message - Is this running on a dialup modem or a virtualized/telnet session. And have you tried the FTS-0001 and Wazoo overrides in Config-Advanced-Security/Misc. Those questions allow you to force the use of alternative protocols in the initial handshake.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Re: Re: Working with QICO
By: Nick Andre to Deon George on Thu Apr 30 2020 10:30 am

As per my other message - Is this running on a dialup modem or a virtualized/telnet session. And have you tried the FTS-0001 and Wazoo overrides in Config-Advanced-Security/Misc. Those questions allow you to force the use of alternative protocols in the initial handshake.

So this is DB running in dosemu - using tcpser.

I have played with those two settings - with mixed results.

I turned them both off and tried again, and a bit further:

01 May 20 12:53:52 tcpip[28460]: starting inbound EMSI session
01 May 20 12:53:52 tcpip[28460]: address: 10:2/2@private
01 May 20 12:53:52 tcpip[28460]: system: (null)
01 May 20 12:53:52 tcpip[28460]: from: (null)
01 May 20 12:53:52 tcpip[28460]: sysop: (null)
01 May 20 12:53:52 tcpip[28460]: phone: (null)
01 May 20 12:53:52 tcpip[28460]: flags: [0] (null)
01 May 20 12:53:52 tcpip[28460]: mailer: D'Bridge 4/XMIT
01 May 20 12:53:52 tcpip[28460]: time: 00:00:00, unknown
01 May 20 12:54:51 tcpip[28460]: total: 0:00:00 online, 0b sent, 0b received
01 May 20 12:54:51 tcpip[28460]: session with 10:2/2 failed [ok]

DB reported:
05/01/2020 12:53 Calling 10:1/1 at 57600 baud
05/01/2020 12:53 Modem reports "CONNECT 38400"
05/01/2020 12:53 EMSI: 10:1/1, qico 0.59.1
05/01/2020 12:54 Z16-S: Fatal timeout, aborted
05/01/2020 12:54 Successful, 01:14, a "free" call

But let me play a bit more and see what I can figure out.
...δεσπ

... That must be wonderful! I don't understand it at all.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

On 01 May 20 13:00:50, Deon George said the following to Nick Andre:

So this is DB running in dosemu - using tcpser.

While I respect and encourage experimentation with DB, unfortunately I cannot offer much tech-support for that configuration. DB is an MS-DOS program written in the days of IBM XT's with limited spec... a lot of assembly language timing and trickery done for Zmodem and other things. It was never written to specifically support Dosemu or Tcpser.

That said... if DB and QICO can be forced to the bare-minimum FTS-0001 they should be able to talk to eachother. (Xmodem/Telink)

Porting DB to Linux is a big endeavor but not impossible... its something I'm slowly working on.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Re: Re: Working with QICO
By: Nick Andre to Deon George on Fri May 01 2020 02:11 am

Hey Nick,

While I respect and encourage experimentation with DB, unfortunately I cannot offer much tech-support for that configuration. DB is an MS-DOS program written in the days of IBM XT's with limited spec... a lot of assembly language timing and trickery done for Zmodem and other things. It 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)