home.social

#xmodem — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #xmodem, aggregated by home.social.

  1. 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!

  2. 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!

  3. 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!

  4. 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!

  5. 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!

  6. This may be of interest to those who are running VICE to emulate a Commodore 64 and using tcpser to bridge serial I/O to the internet:

    There seems to be an isssue with how tcpser encodes the carrier status (see post from lemon64.com below), affecting serial file transfers.

    I have tried a few of the many forks of tcpser (including the fozztexx one and Jim Brain's original code) and none of them worked when trying to transfer files.

    Discussion: lemon64.com/forum/viewtopic.ph

    The solution to the problem was to use a different tool to "bridge" the serial communication: TCPSerial.jar which is a Java based implementation of tcpser. It is an updated version of Jim Brain's Java codebase (tcpser4j) to work with Java 21:

    github.com/MyDeveloperThoughts

    Using this tool instead of the original, C code based tcpser made it possible to finally transfer files using x/ymodem.

    I thought I should let you know ... 🤔

    #Commodore64
    #VICE
    #tcpser
    #xmodem
    #problems
    #solution
    #TCPSerial

  7. Oh, the smell of 8-bit file transfers from a BBS ...

    (on the sending end, at RC-BOX BBS, the CP/M program KMD.COM is being used)

    #xmodem
    #crc
    #CCGMSfuture
    #Commodore64
    #Striketerm

  8. Oh, the smell of 8-bit file transfers from a BBS ...

    (on the sending end, at RC-BOX BBS, the CP/M program KMD.COM is being used)

    #xmodem
    #crc
    #CCGMSfuture
    #Commodore64
    #Striketerm

  9. Oh, the smell of 8-bit file transfers from a BBS ...

    (on the sending end, at RC-BOX BBS, the CP/M program KMD.COM is being used)

    #xmodem
    #crc
    #CCGMSfuture
    #Commodore64
    #Striketerm

  10. Oh, the smell of 8-bit file transfers from a BBS ...

    (on the sending end, at RC-BOX BBS, the CP/M program KMD.COM is being used)

    #xmodem
    #crc
    #CCGMSfuture
    #Commodore64
    #Striketerm

  11. Oh, the smell of 8-bit file transfers from a BBS ...

    (on the sending end, at RC-BOX BBS, the CP/M program KMD.COM is being used)

    #xmodem
    #crc
    #CCGMSfuture
    #Commodore64
    #Striketerm

  12. Звоним через полстраны по dial-up модему в 2025 году

    Приветствую всех! Многие из нас застали лично и всё ещё помнят «модемную» эпоху. И даже мне самому доводилось ими пользоваться, а много позже я писал про то, каково в нынешних реалиях сидеть в интернете через старый аналоговый модем. Но вот мне стало интересно: а как насчёт попробовать позвонить не через мини-АТС, а на модем в другом районе или даже в другом городе? Именно этим мы сейчас и займёмся. Итак, в сегодняшней статье проверим на практике, реально ли заставить два модема связаться друг с другом в наши дни заката эпохи медных линий. Узнаем, насколько стабильным будет соединение и будет ли оно вообще. Традиционно будет много интересного.

    habr.com/ru/companies/timeweb/

    #timeweb_статьи #телефон #модем #gpon #линия #rs232 #uart #xmodem #ymodem #zmodem #crc #ppp #putty #hyperterminal #norton_commander

  13. #WardChristiansen was one of the unkown pioneers. He, along with his friend Randy Seuss, founding the first computer #BBS in Chicago due to a snowstorm. You can read more about Ward here:

    honoraryunsubscribe.com/ward-c

    #Ward also created the #XMODEM protocol in 1977. He was interviewed for the fantastic BBS Documentary by @textfiles , and appears in it at various places, starting here: youtu.be/Dddbe9OuJLU?feature=s

    The raw interview footage is at: archive.org/details/20020216-b

    1/

  14. A typical #RetroComputing sunday with my #Commodore64 - first, testing #xmodem #CRC #file #transfer to #rc2014bbs and then checking out #QLink (the "reloaded" system). Unfortunately, there aren't that much services active there (anymore?!), except the community boards.

  15. 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?! 🤔

  16. 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?! 🤔

  17. 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?! 🤔

  18. 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?! 🤔

  19. 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?! 🤔

  20. Trying - and totally failing - to send files via #xmodem on Linux to a slightly special Z80 machine.

    It's a MinZ, a 36 MHz Z180 in a tiny case. It runs CP/M, but uses a dual serial USB interface. It gives me /dev/ttyUSB0 for terminal but /dev/ttyUSB2 for xmodem transfers. It comes with patched xmodem COM files that use this second serial port. But can I get Linux to do anything but immediately disconnect?

  21. +++ SYSOP NEWS +++ SYSOP NEWS +++ SYSOP NEWS +++

    I took my time today to rework some of the menus of #rc2014bbs (RC-BOX BBS - the world's first and probably only #rc2014 based #BBS system in the world) and do a little maintenance.

    There's a new tool, "FOR", which will list all #files that have recently been #uploaded via #xmodem or #ymodem

    There's now also a help file in the default user area, which you can view by entering TYPE HELP.TXT on the CP/M command line.

    Up-/and downloads work, but not with modern terminal clients. Use your #8bit hardware and an appropriate #terminal program with #xmodem support to successfully upload files. I have successfully tested xmodem transfers using #StrikeTerm on a Commodore 64.

    See my profile for information on how to connect to RC-BOX BBS (the address is listed there)

    EDIT: the C64 terminal program I used for the screenshots is "X-Term!"

  22. Auf Linux nutzt man sowas wie #Minicom.
    Was gibts vergleichbares bedienbar übers #Terminal (bevorzugt Git-#Bash) unter Windows mit dem zB #XModem gesprochen werden kann? 🤔

  23. @bigzaphod When I started #BBSing in the early #1980s on my #Commodore64 the file transfer protocol choices were #XMODEM and #Punter, the latter largely exclusive to #Commodore #BBSes.

    Trivia: XMODEM was invented by Ward Christensen, co-creator of the first #BBS