I think this is the missing piece to help my 64Door problem. I will have to give it a try. Amazing how much trouble this little program has given me. I have already sorted out the other problems. 64Door is picky from what I have learned. I am currently only able to run it on an unaccelerated A1000 with KS 1.3 and 8.5MB RAM.
For my test, I would prefer to just change &k rather that change the three other values. I won't be needing hardware flow control with 64door anyway.
Incidentally, I tested WiBridge on the same A1000 with JrComm set at 38.4kbps and I was able to receive a Zmodem transfer from the PC side. As soon as I bumped it up to 56.7kbps, I started getting too many errors.
I should mention that I am using BaudBandit.device and I do have the WiModem232, not Paul Rickards' modem. Also, hardware flow control *is* enabled for WiBridge.
So I then tried my 030 accelerated Amiga. Same term program, same speed and same modem. It too errored out at 56.7k. My NComm is broken at the moment. Some known issue with changing the serial.device. TERM 4.8 was also tested but just hung during the start of the ZModem xfer. I did not test XModem.
Maybe I should be pointing my finger right at ZModem. It isn't very internet friendly. At least not under modem emulation. I've not had any luck with it on my Commodore 8 bit machines either.
And yet, when I use a real telnet program like DCTelnet, ZModem transfers are ultra fast and flawless. I am on a direct internet connection in this case. Not a fair comparison perhaps.
JimDrew wrote: ↑
Wed Jan 10, 2018 1:19 am
Ok, try the latest version. I beat on 64 door with no slow downs or any issues at 300/1200/2400/9600 baud.
Just keep in mind that if you enable flow control (AT&K1) that you MUST invert the polarities (AT*R1*C1) because 64 door uses the same inverted polarities that the C64/128 does. Kind of odd, but it does! You don't need flow control though, but in case you try it and it hangs - you don't have the proper polarities for RTS/CTS.