#Syncterm xmodem how to
#Syncterm xmodem serial
#Syncterm xmodem pro
#Syncterm xmodem software

When you say 'At the moment I try to handle the download section. I will try to help as much as I remember. Much of the time I spent just trying to understand things. Modifying the board was my main hobby for several years in the late eighties.

#Syncterm xmodem pro

Note that GBBS Pro 1.2 only had Hayes Smartmodem at 2400 baud, Hugh Hood modified it to support 4800.

#Syncterm xmodem serial

Anyway, I tell it to use an external modem via the Super Serial Card, and specify Hayes Smartmodem. I understand newer versions do not have this file so not sure if my experience would apply. Note that my version of GBBS Pro 1.2 uses a file called extmodems for this. This triggers the 'busy.txt' file for anybody who tries to connect (as described above).ДЄs for which modem I have GBBS configured for. What I do know when I plan to have it off-line (for backups, etc), is open a connection to the Pi after I take the board down. Note that I have never gotten it to display the contents of the second text file 'offline.txt'. I then try to open a second connection, this second connection will get the contents of the busy.txt file (saying the board is busy, even though it is actually off-line). I would then open a telnet connection to the Pi, which would succeed. For example, I would have no program at all running on the Apple. What it does know- is if somebody else is connected to the Pi. It appears the Pi has no idea if anybody else is logged on to the BBS, it doesn't even know if the BBS is actually on-line. Hi 6502enhanced, glad you like the board.ДЄs for 'scripts/busy.txt', do you mean how does the Raspberry Pi know the board is busy, so it will display the contents of busy.txt to the remote caller? That was a mystery to me as well as a few others. It might have something to do with me using a Raspberry Pi as a modem. (telnet port 6502) I tried to run verson 2, but could not get it to work (yet). (Hugh indicated I was free to give to anybody who was interested).Дj's Place BBS (also GBBS Pro) is actually running at 9600 baud, but he is using a prototype version 2 of GBBS Pro. I could probably send you the hacked file if you wanted to try it. I don't know if Hugh is on this forum or not, he responded to my plea for help in the Apple II forum on. 4800 works great though, smooth as glass. He tried for 9600 baud, and it actually connected, but I could not get it to recycle after a caller disconnected, and I had to manually reset it. Hugh Hood hacked the external modem file of v1.2 so it supports 4800 baud. How did you get up to 4800bps? I'm having all sorts of trouble at 1200bps but I think a lot of problems would disappear at higher speeds. I lost interest in the BBS scene for a few months after getting frustrated with my own GBBS setup. I'd even make the first 128 bytes (a whole packet) of file data as a header, which could include anything, like how many bytes will follow, the data file version or comments or some unlocking magic numbers if it is going to be flashed into code memory or something.I'll have to jump on and try this one out, looks good skipper. I would create the data I send with XMODEM so that the first thing to be sent is how many bytes there are in a transmission, so we can stop at the padding. There already is a non-standard modification of XMODEM where the first packet to be sent is not 1 but 0, and it includes file name and stuff.

And then you must create your own upload software.

#Syncterm xmodem software

Why would you want to change a working de-facto standard protocol? Then you cannot use any other XMODEM software to upload your stuff. So the sender constructs the padding in a way that it's harmless for the used interpretation.

#Syncterm xmodem how to

If the receiver has no way how to determine that the file has ended, he's going to continue interpreting the padding. This is necessary because the length of the file is not transmitted. But the padding is actually allowed to contain anything according to the standard. The padding was originally the SUB character (called CPMEOF in the standard) which has value of 26 decimal.