home.social

#imp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #imp, 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 is my piece from the last Fantasy Artist Illustration Intensive Workshop in 2025.

    Brimstone Imp
    11x14 oil on panel
    Glazed for AI scraping protection
    Prints available at www.leonbarrettillustration.com

    #FAIIW2025, #Demon, #imp, #brimstone, #fire, #apocalypse, #gothic, #devil

  7. My warlock Gilderoy along with his (bird) fish friends: Sparrow (adopted kenku) and Gypsy (familiar, imp, parrot, editor, best friend, etc.) having some family time

    Based on... a Tumblr meme, I guess..?

    #art #drawing #oc #dnd #dnd5e #kenku #dndkenku #anthro #anthroart #lineart #ocart #furry #furryart #digital #MastoArt #oc #dndoc #warlock #imp #parrot

  8. My warlock Gilderoy along with his (bird) fish friends: Sparrow (adopted kenku) and Gypsy (familiar, imp, parrot, editor, best friend, etc.) having some family time

    Based on... a Tumblr meme, I guess..?

    #art #drawing #oc #dnd #dnd5e #kenku #dndkenku #anthro #anthroart #lineart #ocart #furry #furryart #digital #MastoArt #oc #dndoc #warlock #imp #parrot

  9. My warlock Gilderoy along with his (bird) fish friends: Sparrow (adopted kenku) and Gypsy (familiar, imp, parrot, editor, best friend, etc.) having some family time

    Based on... a Tumblr meme, I guess..?

    #art #drawing #oc #dnd #dnd5e #kenku #dndkenku #anthro #anthroart #lineart #ocart #furry #furryart #digital #MastoArt #oc #dndoc #warlock #imp #parrot