#ccgms — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ccgms, aggregated by home.social.
-
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!
-
IMSAI C64 WiFi: Levi’s Digital Voyage Links WarGames Hardware to the C64 Ultimate
#IMSAI #Commodore64 #C64Ultimate #LevisDigitalVoyage #CPM #CCGMS #RetroComputing #WarGames
https://theoasisbbs.com/imsai-c64-wifi-levis-digital-voyage-links-wargames-hardware-to-the-c64-ultimate/?fsp_sid=6236 -
IMSAI C64 WiFi: Levi’s Digital Voyage Links WarGames Hardware to the C64 Ultimate
#IMSAI #Commodore64 #C64Ultimate #LevisDigitalVoyage #CPM #CCGMS #RetroComputing #WarGames
https://theoasisbbs.com/imsai-c64-wifi-levis-digital-voyage-links-wargames-hardware-to-the-c64-ultimate/?fsp_sid=6236 -
IMSAI C64 WiFi: Levi’s Digital Voyage Links WarGames Hardware to the C64 Ultimate
#IMSAI #Commodore64 #C64Ultimate #LevisDigitalVoyage #CPM #CCGMS #RetroComputing #WarGames
https://theoasisbbs.com/imsai-c64-wifi-levis-digital-voyage-links-wargames-hardware-to-the-c64-ultimate/?fsp_sid=6236 -
IMSAI C64 WiFi: Levi’s Digital Voyage Links WarGames Hardware to the C64 Ultimate
#IMSAI #Commodore64 #C64Ultimate #LevisDigitalVoyage #CPM #CCGMS #RetroComputing #WarGames
https://theoasisbbs.com/imsai-c64-wifi-levis-digital-voyage-links-wargames-hardware-to-the-c64-ultimate/?fsp_sid=6236 -
IMSAI C64 WiFi: Levi’s Digital Voyage Links WarGames Hardware to the C64 Ultimate
#IMSAI #Commodore64 #C64Ultimate #LevisDigitalVoyage #CPM #CCGMS #RetroComputing #WarGames
https://theoasisbbs.com/imsai-c64-wifi-levis-digital-voyage-links-wargames-hardware-to-the-c64-ultimate/?fsp_sid=6236 -
Now it's time for some BBSing... Right now is behaving correctly: no more spurious resets, and I'm using the #C64 to power it, very conveniently.
I'm using it along with the #KungFuFlash to load #CCGMS , so I'm probably driving the #commodore 's 5v line pretty hard... Until now, I only had a couple of missed boots from the KungFuFlash, probably due to an unstable voltage on turn on. Once it boots, btw, it seems pretty stable. The original power brick may not be having the best time of its life...
#BBS #zimodem #commodore64 #esp8266 -
I just tried the #zimodem #wifi modem for the #commodore I built. It works, but it was a bumpy ride... at first the #esp8266 was resetting continuously. I thought that the #commodore64 wasn't providing enough current, so I cut the 5v cable and connected to usb power, to no avail: it keeped resetting every now and then. Then i checked with the multimeter and there was a low resistance between the reset pin and ground. Cut that as well, but I got only garbled characters. At the end I noticed a comment in the page I used to download #ccgms 2021 saying it wasn't working on certain modems. They suggested trying the 2017 version and... it worked flawlessly!
-
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?! 🤔
