#qterm — Public Fediverse posts

I'm turning to you people as I am at a loss with regards to the following issue:

On #rc2014bbs I use KMD to provide #xmodem transfer over the serial line (and, eventually via #wifimodem over the internet).

This works as long as you either connect with another #rc2014 using #qterm or #imp or if you use a #Commodore64 using #ccgms

But when you try to perform xmodem transfer from a modern machine (PC, Mac - it doesn't matter) using a modern terminal program (Syncterm, Qodem, TeraTerm, lrzsz etc. - it doesn't matter) the transfer begins, sending a few blocks and then gets into a NAK loop and aborts due to the error count reaching max.

So, my question to the wise, collective fedimind is: what can be the cause for such a behaviour? Timing issues?! Old xmodem implementation within KMD?! Some interference from the #Zimodem firmware?!

Any suggestions, comments etc. are welcome!

I'm turning to you people as I am at a loss with regards to the following issue:

On #rc2014bbs I use KMD to provide #xmodem transfer over the serial line (and, eventually via #wifimodem over the internet).

This works as long as you either connect with another #rc2014 using #qterm or #imp or if you use a #Commodore64 using #ccgms

But when you try to perform xmodem transfer from a modern machine (PC, Mac - it doesn't matter) using a modern terminal program (Syncterm, Qodem, TeraTerm, lrzsz etc. - it doesn't matter) the transfer begins, sending a few blocks and then gets into a NAK loop and aborts due to the error count reaching max.

So, my question to the wise, collective fedimind is: what can be the cause for such a behaviour? Timing issues?! Old xmodem implementation within KMD?! Some interference from the #Zimodem firmware?!

Any suggestions, comments etc. are welcome!

I'm turning to you people as I am at a loss with regards to the following issue:

On #rc2014bbs I use KMD to provide #xmodem transfer over the serial line (and, eventually via #wifimodem over the internet).

This works as long as you either connect with another #rc2014 using #qterm or #imp or if you use a #Commodore64 using #ccgms

But when you try to perform xmodem transfer from a modern machine (PC, Mac - it doesn't matter) using a modern terminal program (Syncterm, Qodem, TeraTerm, lrzsz etc. - it doesn't matter) the transfer begins, sending a few blocks and then gets into a NAK loop and aborts due to the error count reaching max.

So, my question to the wise, collective fedimind is: what can be the cause for such a behaviour? Timing issues?! Old xmodem implementation within KMD?! Some interference from the #Zimodem firmware?!

Any suggestions, comments etc. are welcome!

I'm turning to you people as I am at a loss with regards to the following issue:

On #rc2014bbs I use KMD to provide #xmodem transfer over the serial line (and, eventually via #wifimodem over the internet).

This works as long as you either connect with another #rc2014 using #qterm or #imp or if you use a #Commodore64 using #ccgms

But when you try to perform xmodem transfer from a modern machine (PC, Mac - it doesn't matter) using a modern terminal program (Syncterm, Qodem, TeraTerm, lrzsz etc. - it doesn't matter) the transfer begins, sending a few blocks and then gets into a NAK loop and aborts due to the error count reaching max.

So, my question to the wise, collective fedimind is: what can be the cause for such a behaviour? Timing issues?! Old xmodem implementation within KMD?! Some interference from the #Zimodem firmware?!

Any suggestions, comments etc. are welcome!

I'm turning to you people as I am at a loss with regards to the following issue:

On #rc2014bbs I use KMD to provide #xmodem transfer over the serial line (and, eventually via #wifimodem over the internet).

This works as long as you either connect with another #rc2014 using #qterm or #imp or if you use a #Commodore64 using #ccgms

But when you try to perform xmodem transfer from a modern machine (PC, Mac - it doesn't matter) using a modern terminal program (Syncterm, Qodem, TeraTerm, lrzsz etc. - it doesn't matter) the transfer begins, sending a few blocks and then gets into a NAK loop and aborts due to the error count reaching max.

So, my question to the wise, collective fedimind is: what can be the cause for such a behaviour? Timing issues?! Old xmodem implementation within KMD?! Some interference from the #Zimodem firmware?!

Any suggestions, comments etc. are welcome!

I am currently doing some testing with #rc2014bbs and there is something strange here:

#rcbox #BBS runs on a Z80 CP/M system ( #rc2014 ) and I am using the CP/M file transfer tool KMD.COM to #transfer #files to and from the system via #xmodem (CRC and 1K - both possible).

This seems to work as long as the client machine up- or downloading files is an #8bit machine: a RC2014 with #Qterm works, a #Commodore64 with #CCGMS works - but as soon as I try to use #Syncterm or #Qodem or any other modern #Linux #terminal #program the transfers fail with either "error in header" or, more often, with "CRC error".

How is this possible?! 🤔

I am currently doing some testing with #rc2014bbs and there is something strange here:

#rcbox #BBS runs on a Z80 CP/M system ( #rc2014 ) and I am using the CP/M file transfer tool KMD.COM to #transfer #files to and from the system via #xmodem (CRC and 1K - both possible).

This seems to work as long as the client machine up- or downloading files is an #8bit machine: a RC2014 with #Qterm works, a #Commodore64 with #CCGMS works - but as soon as I try to use #Syncterm or #Qodem or any other modern #Linux #terminal #program the transfers fail with either "error in header" or, more often, with "CRC error".

How is this possible?! 🤔

I am currently doing some testing with #rc2014bbs and there is something strange here:

#rcbox #BBS runs on a Z80 CP/M system ( #rc2014 ) and I am using the CP/M file transfer tool KMD.COM to #transfer #files to and from the system via #xmodem (CRC and 1K - both possible).

This seems to work as long as the client machine up- or downloading files is an #8bit machine: a RC2014 with #Qterm works, a #Commodore64 with #CCGMS works - but as soon as I try to use #Syncterm or #Qodem or any other modern #Linux #terminal #program the transfers fail with either "error in header" or, more often, with "CRC error".

How is this possible?! 🤔

I am currently doing some testing with #rc2014bbs and there is something strange here:

#rcbox #BBS runs on a Z80 CP/M system ( #rc2014 ) and I am using the CP/M file transfer tool KMD.COM to #transfer #files to and from the system via #xmodem (CRC and 1K - both possible).

This seems to work as long as the client machine up- or downloading files is an #8bit machine: a RC2014 with #Qterm works, a #Commodore64 with #CCGMS works - but as soon as I try to use #Syncterm or #Qodem or any other modern #Linux #terminal #program the transfers fail with either "error in header" or, more often, with "CRC error".

How is this possible?! 🤔

I am currently doing some testing with #rc2014bbs and there is something strange here:

#rcbox #BBS runs on a Z80 CP/M system ( #rc2014 ) and I am using the CP/M file transfer tool KMD.COM to #transfer #files to and from the system via #xmodem (CRC and 1K - both possible).

This seems to work as long as the client machine up- or downloading files is an #8bit machine: a RC2014 with #Qterm works, a #Commodore64 with #CCGMS works - but as soon as I try to use #Syncterm or #Qodem or any other modern #Linux #terminal #program the transfers fail with either "error in header" or, more often, with "CRC error".

How is this possible?! 🤔

Did you check your mail today?

I'm sure you didn't because there haven't been many calls coming in on RC-BOX BBS #RC2014BBS (the world's first and - currently - only bulletin board system #BBS running on a #RC2014 )

Better fire up your #Telnet terminal client (#Syncterm, #Qodem or even #Qterm if you are using CP/M #CPM) and connect to:

rc2014.ddns.net on TCP port: 2014

so you won't be missing any news!

Did you check your mail today?

I'm sure you didn't because there haven't been many calls coming in on RC-BOX BBS #RC2014BBS (the world's first and - currently - only bulletin board system #BBS running on a #RC2014 )

Better fire up your #Telnet terminal client (#Syncterm, #Qodem or even #Qterm if you are using CP/M #CPM) and connect to:

rc2014.ddns.net on TCP port: 2014

so you won't be missing any news!

Did you check your mail today?

I'm sure you didn't because there haven't been many calls coming in on RC-BOX BBS #RC2014BBS (the world's first and - currently - only bulletin board system #BBS running on a #RC2014 )

Better fire up your #Telnet terminal client (#Syncterm, #Qodem or even #Qterm if you are using CP/M #CPM) and connect to:

rc2014.ddns.net on TCP port: 2014

so you won't be missing any news!

Did you check your mail today?

I'm sure you didn't because there haven't been many calls coming in on RC-BOX BBS #RC2014BBS (the world's first and - currently - only bulletin board system #BBS running on a #RC2014 )

Better fire up your #Telnet terminal client (#Syncterm, #Qodem or even #Qterm if you are using CP/M #CPM) and connect to:

rc2014.ddns.net on TCP port: 2014

so you won't be missing any news!

Did you check your mail today?

I'm sure you didn't because there haven't been many calls coming in on RC-BOX BBS #RC2014BBS (the world's first and - currently - only bulletin board system #BBS running on a #RC2014 )

Better fire up your #Telnet terminal client (#Syncterm, #Qodem or even #Qterm if you are using CP/M #CPM) and connect to:

rc2014.ddns.net on TCP port: 2014

so you won't be missing any news!