#syncterm — Public Fediverse posts

@synlogic4242

Oooo, I keep meaning to check out @particlesbbs .
I used to cruise Lunduke's* BBS with #syncterm back in 2019.

*Don't hold it against me, I had no idea how bad his politics was back then 😥

Syncterm v1.6 running on OpenIndiana through pkgsrc

#bbs #syncterm #illumos #pkgsrc

Deuce recently added support for the Atari ST flavor of VT52 to his SyncTerm program.

I first requested this feature 14 years ago. I was so excited it finally happened, that I made a new VT52 animation to celebrate.

Plus I dug up six more that I have never seen published anywhere else.

https://breakintochat.com/blog/2025/02/15/some-love-for-vt52-on-the-atari-st/

#atarist #atari #textmode #textanimation #animation #asciiart #vt52 #syncterm #textart

2./ I finally got my hands on these identifiers yesterday, and I was able to connect again to my favorite BBSs. In particular EndOfTheLineBBS.com. What a joy! And to see that my account still existed, after more than a year of inactivity. Thanks Nigel! I spent Saturday on BBSs and it will probably be the same for a good part of this Sunday.

:0)
#linux #syncterm #BBS #messageboards #bulletinboards #retrocomputing

2./ I finally got my hands on these identifiers yesterday, and I was able to connect again to my favorite BBSs. In particular EndOfTheLineBBS.com. What a joy! And to see that my account still existed, after more than a year of inactivity. Thanks Nigel! I spent Saturday on BBSs and it will probably be the same for a good part of this Sunday.

:0)
#linux #syncterm #BBS #messageboards #bulletinboards #retrocomputing

2./ I finally got my hands on these identifiers yesterday, and I was able to connect again to my favorite BBSs. In particular EndOfTheLineBBS.com. What a joy! And to see that my account still existed, after more than a year of inactivity. Thanks Nigel! I spent Saturday on BBSs and it will probably be the same for a good part of this Sunday.

:0)
#linux #syncterm #BBS #messageboards #bulletinboards #retrocomputing

1/. I used to visit BBS from a MSDOS-only machine. In June 2023 (or July), the power supply failed, and since it is a fairly rare model to find and it is very difficult to adapt one, the machine with its MSDOS hard drive remained there, inactive. In the meantime, an old hard drive where all my identifiers for the different BBSs were, also failed. And I no longer knew on which medium I had made a backup of this data.
But..

#linux #syncterm #BBS #messageboards #bulletinboards #retrocomputing

1/. I used to visit BBS from a MSDOS-only machine. In June 2023 (or July), the power supply failed, and since it is a fairly rare model to find and it is very difficult to adapt one, the machine with its MSDOS hard drive remained there, inactive. In the meantime, an old hard drive where all my identifiers for the different BBSs were, also failed. And I no longer knew on which medium I had made a backup of this data.
But..

#linux #syncterm #BBS #messageboards #bulletinboards #retrocomputing

1/. I used to visit BBS from a MSDOS-only machine. In June 2023 (or July), the power supply failed, and since it is a fairly rare model to find and it is very difficult to adapt one, the machine with its MSDOS hard drive remained there, inactive. In the meantime, an old hard drive where all my identifiers for the different BBSs were, also failed. And I no longer knew on which medium I had made a backup of this data.
But..

#linux #syncterm #BBS #messageboards #bulletinboards #retrocomputing

Making progress with the #synchronet system. Got #qwk downloads working along with #syncterm as well. Now just have to get use to how #multimail works as the mail reader.

I have updated my BBSing resource page, for anyone with a hankerin' to "dial in" once again.

https://bytecellar.com/bbsing/

#BBS #BBSing #BulletinBoardSystem #terminal #telnet #client #vintagecomputing #retrocomputing #nostalgia #dialup #modem #AT #retrocomputers #vintagetech #blog #screenshot #video #SyncTerm #MuffinTerm #ByteCellar

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

Video showing connecting to #mysticBBS (configured for #ASCII not #ANSI) #telnetBBS over #meshtastic (using the --tunnel option in the #CLI tool).

#SyncTerm is the BBS/Telnet client

#shortfast #medfast and #longfast
#telnet

Video showing connecting to #mysticBBS (configured for #ASCII not #ANSI) #telnetBBS over #meshtastic (using the --tunnel option in the #CLI tool).

#SyncTerm is the BBS/Telnet client

#shortfast #medfast and #longfast
#telnet

Video showing connecting to #mysticBBS (configured for #ASCII not #ANSI) #telnetBBS over #meshtastic (using the --tunnel option in the #CLI tool).

#SyncTerm is the BBS/Telnet client

#shortfast #medfast and #longfast
#telnet

Video showing connecting to #mysticBBS (configured for #ASCII not #ANSI) #telnetBBS over #meshtastic (using the --tunnel option in the #CLI tool).

#SyncTerm is the BBS/Telnet client

#shortfast #medfast and #longfast
#telnet

Video showing connecting to #mysticBBS (configured for #ASCII not #ANSI) #telnetBBS over #meshtastic (using the --tunnel option in the #CLI tool).

#SyncTerm is the BBS/Telnet client

#shortfast #medfast and #longfast
#telnet

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!

Saludando a viejos conocidos

https://friendicarg.nsupdate.info/display/69172192-5762-4b76-2b17-6ee847075006

@wembly they are still there. Install #SyncTerm and find out!