#rc2014 — Public Fediverse posts

+++ SYSOP NOTICE +++ SYSOP NOTICE +++

* File transfer issues with RC-BOX BBS have been resolved !!

I have eventually been able to fix the issues regarding file transfers from/to modern hardware (e.g. PC or Mac). So now file transfers work with programs like SyncTerm, TeraTerm, lrzsz etc.

Please report any errors or problems in the SUPPORT message file on the BBS.

Thank you.

#bbs
#rc2014
#rc2014bbs

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!

Prior to today, the last time I got any new #RC2014 PCB designs ordered was in 2025. Well, now there has been not just one, but two designs ordered. They should be here in time to build up a couple of prototypes ready to show off at #RetroFest2026 in a couple of weeks time. Fingers crossed.

Prior to today, the last time I got any new #RC2014 PCB designs ordered was in 2025. Well, now there has been not just one, but two designs ordered. They should be here in time to build up a couple of prototypes ready to show off at #RetroFest2026 in a couple of weeks time. Fingers crossed.

Prior to today, the last time I got any new #RC2014 PCB designs ordered was in 2025. Well, now there has been not just one, but two designs ordered. They should be here in time to build up a couple of prototypes ready to show off at #RetroFest2026 in a couple of weeks time. Fingers crossed.

Prior to today, the last time I got any new #RC2014 PCB designs ordered was in 2025. Well, now there has been not just one, but two designs ordered. They should be here in time to build up a couple of prototypes ready to show off at #RetroFest2026 in a couple of weeks time. Fingers crossed.

Prior to today, the last time I got any new #RC2014 PCB designs ordered was in 2025. Well, now there has been not just one, but two designs ordered. They should be here in time to build up a couple of prototypes ready to show off at #RetroFest2026 in a couple of weeks time. Fingers crossed.

RC2014 Bus Reverser

I’m not sure quite how universal this is, but this started because I wanted to add a single RC2014 card to my Easy Z80, which supports an RC2014 bus interface.

Easy, I thought, just add a 40-way socket and the card will plug in. And in principle it would. I would end up with something like this.

But then I realised that the orientation of the RC2014 bus was probably meant to be used for pin headers to make the EasyZ80 be more of a CPU card in a bus system, as shown below.

But what I’m heading towards is being able to plug in a compact flash card, which means connecting the following:

And in either of the above configurations, the cards will be sticking out at odd angles, and feeling somewhat precarious. It would be great if I could just connect them horizontally as shown above.

So that is what I’ve built.

This is an RC2014 bus pin reverser. In the photo above pin 1 is at the bottom on the left hand side and at the top of the right hand side.

There is an option to not pass through VCC, just in case at some point I wanted to connect two independently powered systems.

Originally I envisaged the silkscreen as shown above being the top, but it turns out I got things the wrong way round for that to happen. And it does need to be the right way around as the VCC connection is a wider track and GND connects to the GND fill. Also the jumper and capacitor would be between the wrong two connections if I tried to connect it up the other way round. I guess what I’m saying is that it is not a fully symmetrical reversal of all 40 pins.

It actually works quite well for any “all in one” CPU card being connected to a single IO card. Below I have my RC2014 Micro connected to the digital IO module.

There isn’t a lot else to say really. The BOM is pretty minimal: just two 40-way right angle headers in addition to the PCB, capacitor and jumper. The capacitor and jumper are optional and the jumper can be replaced with a wire link if required.

The schematic and PCB files can be found on GitHub here.

I originally thought the converter would have pin headers on one side and a pin socket on the other. But once I realised I really wanted to connect a card to a card, the use of two sets of pin sockets seemed right. But really, any combination can obviously be used if it works.

Note: I have no idea what this does to any signal integrity. There is certainly no attempt to keep trace lengths equal or anything like that. But I figure if the RC22014 can get away with pin headers in the first place, I suspect that kind of thing is not going to be a big issue.

Kevin

RC2014 Bus Reverser

I’m not sure quite how universal this is, but this started because I wanted to add a single RC2014 card to my Easy Z80, which supports an RC2014 bus interface.

Easy, I thought, just add a 40-way socket and the card will plug in. And in principle it would. I would end up with something like this.

But then I realised that the orientation of the RC2014 bus was probably meant to be used for pin headers to make the EasyZ80 be more of a CPU card in a bus system, as shown below.

But what I’m heading towards is being able to plug in a compact flash card, which means connecting the following:

And in either of the above configurations, the cards will be sticking out at odd angles, and feeling somewhat precarious. It would be great if I could just connect them horizontally as shown above.

So that is what I’ve built.

This is an RC2014 bus pin reverser. In the photo above pin 1 is at the bottom on the left hand side and at the top of the right hand side.

There is an option to not pass through VCC, just in case at some point I wanted to connect two independently powered systems.

Originally I envisaged the silkscreen as shown above being the top, but it turns out I got things the wrong way round for that to happen. And it does need to be the right way around as the VCC connection is a wider track and GND connects to the GND fill. Also the jumper and capacitor would be between the wrong two connections if I tried to connect it up the other way round. I guess what I’m saying is that it is not a fully symmetrical reversal of all 40 pins.

It actually works quite well for any “all in one” CPU card being connected to a single IO card. Below I have my RC2014 Micro connected to the digital IO module.

There isn’t a lot else to say really. The BOM is pretty minimal: just two 40-way right angle headers in addition to the PCB, capacitor and jumper. The capacitor and jumper are optional and the jumper can be replaced with a wire link if required.

The schematic and PCB files can be found on GitHub here.

I originally thought the converter would have pin headers on one side and a pin socket on the other. But once I realised I really wanted to connect a card to a card, the use of two sets of pin sockets seemed right. But really, any combination can obviously be used if it works.

Note: I have no idea what this does to any signal integrity. There is certainly no attempt to keep trace lengths equal or anything like that. But I figure if the RC22014 can get away with pin headers in the first place, I suspect that kind of thing is not going to be a big issue.

Kevin

RC2014 Bus Reverser

I’m not sure quite how universal this is, but this started because I wanted to add a single RC2014 card to my Easy Z80, which supports an RC2014 bus interface.

Easy, I thought, just add a 40-way socket and the card will plug in. And in principle it would. I would end up with something like this.

But then I realised that the orientation of the RC2014 bus was probably meant to be used for pin headers to make the EasyZ80 be more of a CPU card in a bus system, as shown below.

But what I’m heading towards is being able to plug in a compact flash card, which means connecting the following:

And in either of the above configurations, the cards will be sticking out at odd angles, and feeling somewhat precarious. It would be great if I could just connect them horizontally as shown above.

So that is what I’ve built.

This is an RC2014 bus pin reverser. In the photo above pin 1 is at the bottom on the left hand side and at the top of the right hand side.

There is an option to not pass through VCC, just in case at some point I wanted to connect two independently powered systems.

Originally I envisaged the silkscreen as shown above being the top, but it turns out I got things the wrong way round for that to happen. And it does need to be the right way around as the VCC connection is a wider track and GND connects to the GND fill. Also the jumper and capacitor would be between the wrong two connections if I tried to connect it up the other way round. I guess what I’m saying is that it is not a fully symmetrical reversal of all 40 pins.

It actually works quite well for any “all in one” CPU card being connected to a single IO card. Below I have my RC2014 Micro connected to the digital IO module.

There isn’t a lot else to say really. The BOM is pretty minimal: just two 40-way right angle headers in addition to the PCB, capacitor and jumper. The capacitor and jumper are optional and the jumper can be replaced with a wire link if required.

The schematic and PCB files can be found on GitHub here.

I originally thought the converter would have pin headers on one side and a pin socket on the other. But once I realised I really wanted to connect a card to a card, the use of two sets of pin sockets seemed right. But really, any combination can obviously be used if it works.

Note: I have no idea what this does to any signal integrity. There is certainly no attempt to keep trace lengths equal or anything like that. But I figure if the RC22014 can get away with pin headers in the first place, I suspect that kind of thing is not going to be a big issue.

Kevin

RC2014 Bus Reverser

I’m not sure quite how universal this is, but this started because I wanted to add a single RC2014 card to my Easy Z80, which supports an RC2014 bus interface.

Easy, I thought, just add a 40-way socket and the card will plug in. And in principle it would. I would end up with something like this.

But then I realised that the orientation of the RC2014 bus was probably meant to be used for pin headers to make the EasyZ80 be more of a CPU card in a bus system, as shown below.

But what I’m heading towards is being able to plug in a compact flash card, which means connecting the following:

And in either of the above configurations, the cards will be sticking out at odd angles, and feeling somewhat precarious. It would be great if I could just connect them horizontally as shown above.

So that is what I’ve built.

This is an RC2014 bus pin reverser. In the photo above pin 1 is at the bottom on the left hand side and at the top of the right hand side.

There is an option to not pass through VCC, just in case at some point I wanted to connect two independently powered systems.

Originally I envisaged the silkscreen as shown above being the top, but it turns out I got things the wrong way round for that to happen. And it does need to be the right way around as the VCC connection is a wider track and GND connects to the GND fill. Also the jumper and capacitor would be between the wrong two connections if I tried to connect it up the other way round. I guess what I’m saying is that it is not a fully symmetrical reversal of all 40 pins.

It actually works quite well for any “all in one” CPU card being connected to a single IO card. Below I have my RC2014 Micro connected to the digital IO module.

There isn’t a lot else to say really. The BOM is pretty minimal: just two 40-way right angle headers in addition to the PCB, capacitor and jumper. The capacitor and jumper are optional and the jumper can be replaced with a wire link if required.

The schematic and PCB files can be found on GitHub here.

I originally thought the converter would have pin headers on one side and a pin socket on the other. But once I realised I really wanted to connect a card to a card, the use of two sets of pin sockets seemed right. But really, any combination can obviously be used if it works.

Note: I have no idea what this does to any signal integrity. There is certainly no attempt to keep trace lengths equal or anything like that. But I figure if the RC22014 can get away with pin headers in the first place, I suspect that kind of thing is not going to be a big issue.

Kevin

RC2014 Bus Reverser

I’m not sure quite how universal this is, but this started because I wanted to add a single RC2014 card to my Easy Z80, which supports an RC2014 bus interface.

Easy, I thought, just add a 40-way socket and the card will plug in. And in principle it would. I would end up with something like this.

But then I realised that the orientation of the RC2014 bus was probably meant to be used for pin headers to make the EasyZ80 be more of a CPU card in a bus system, as shown below.

But what I’m heading towards is being able to plug in a compact flash card, which means connecting the following:

And in either of the above configurations, the cards will be sticking out at odd angles, and feeling somewhat precarious. It would be great if I could just connect them horizontally as shown above.

So that is what I’ve built.

This is an RC2014 bus pin reverser. In the photo above pin 1 is at the bottom on the left hand side and at the top of the right hand side.

There is an option to not pass through VCC, just in case at some point I wanted to connect two independently powered systems.

Originally I envisaged the silkscreen as shown above being the top, but it turns out I got things the wrong way round for that to happen. And it does need to be the right way around as the VCC connection is a wider track and GND connects to the GND fill. Also the jumper and capacitor would be between the wrong two connections if I tried to connect it up the other way round. I guess what I’m saying is that it is not a fully symmetrical reversal of all 40 pins.

It actually works quite well for any “all in one” CPU card being connected to a single IO card. Below I have my RC2014 Micro connected to the digital IO module.

There isn’t a lot else to say really. The BOM is pretty minimal: just two 40-way right angle headers in addition to the PCB, capacitor and jumper. The capacitor and jumper are optional and the jumper can be replaced with a wire link if required.

The schematic and PCB files can be found on GitHub here.

I originally thought the converter would have pin headers on one side and a pin socket on the other. But once I realised I really wanted to connect a card to a card, the use of two sets of pin sockets seemed right. But really, any combination can obviously be used if it works.

Note: I have no idea what this does to any signal integrity. There is certainly no attempt to keep trace lengths equal or anything like that. But I figure if the RC22014 can get away with pin headers in the first place, I suspect that kind of thing is not going to be a big issue.

Kevin

If you think that the AI companies buying all the RAM production is only hitting DDR5 prices, think again.

The 32k DIP chips I use in most of my kits (AS6C62256) were just £2.25 a couple of years ago. (And less than a quid a short while before then).

Mouser are one of the cheaper places at the moment and they're £7.69+VAT singly, or still well over six quid in bulk. https://www.mouser.co.uk/ProductDetail/Alliance-Memory/AS6C62256-55PCN?qs=LD2UibpCYJqgbIupMJnGTQ%3D%3D

I am going to have to take a serious look at the #RC2014 prices I'm currently charging!

If you think that the AI companies buying all the RAM production is only hitting DDR5 prices, think again.

The 32k DIP chips I use in most of my kits (AS6C62256) were just £2.25 a couple of years ago. (And less than a quid a short while before then).

Mouser are one of the cheaper places at the moment and they're £7.69+VAT singly, or still well over six quid in bulk. https://www.mouser.co.uk/ProductDetail/Alliance-Memory/AS6C62256-55PCN?qs=LD2UibpCYJqgbIupMJnGTQ%3D%3D

I am going to have to take a serious look at the #RC2014 prices I'm currently charging!

If you think that the AI companies buying all the RAM production is only hitting DDR5 prices, think again.

The 32k DIP chips I use in most of my kits (AS6C62256) were just £2.25 a couple of years ago. (And less than a quid a short while before then).

Mouser are one of the cheaper places at the moment and they're £7.69+VAT singly, or still well over six quid in bulk. https://www.mouser.co.uk/ProductDetail/Alliance-Memory/AS6C62256-55PCN?qs=LD2UibpCYJqgbIupMJnGTQ%3D%3D

I am going to have to take a serious look at the #RC2014 prices I'm currently charging!

If you think that the AI companies buying all the RAM production is only hitting DDR5 prices, think again.

The 32k DIP chips I use in most of my kits (AS6C62256) were just £2.25 a couple of years ago. (And less than a quid a short while before then).

Mouser are one of the cheaper places at the moment and they're £7.69+VAT singly, or still well over six quid in bulk. https://www.mouser.co.uk/ProductDetail/Alliance-Memory/AS6C62256-55PCN?qs=LD2UibpCYJqgbIupMJnGTQ%3D%3D

I am going to have to take a serious look at the #RC2014 prices I'm currently charging!

If you think that the AI companies buying all the RAM production is only hitting DDR5 prices, think again.

The 32k DIP chips I use in most of my kits (AS6C62256) were just £2.25 a couple of years ago. (And less than a quid a short while before then).

Mouser are one of the cheaper places at the moment and they're £7.69+VAT singly, or still well over six quid in bulk. https://www.mouser.co.uk/ProductDetail/Alliance-Memory/AS6C62256-55PCN?qs=LD2UibpCYJqgbIupMJnGTQ%3D%3D

I am going to have to take a serious look at the #RC2014 prices I'm currently charging!

Super cool Mazogs #RC2014 port by @shieladixon ...

https://shieladixon.itch.io/mazogs2014

Super cool Mazogs #RC2014 port by @shieladixon ...

https://shieladixon.itch.io/mazogs2014

Super cool Mazogs #RC2014 port by @shieladixon ...

https://shieladixon.itch.io/mazogs2014

Super cool Mazogs #RC2014 port by @shieladixon ...

https://shieladixon.itch.io/mazogs2014

Super cool Mazogs #RC2014 port by @shieladixon ...

https://shieladixon.itch.io/mazogs2014

Just found this old photo from 2016. So, if you ever wondered how the early #RC2014 kits were assembled... well, now you know!

Just found this old photo from 2016. So, if you ever wondered how the early #RC2014 kits were assembled... well, now you know!

Just found this old photo from 2016. So, if you ever wondered how the early #RC2014 kits were assembled... well, now you know!

Just found this old photo from 2016. So, if you ever wondered how the early #RC2014 kits were assembled... well, now you know!

Just found this old photo from 2016. So, if you ever wondered how the early #RC2014 kits were assembled... well, now you know!

Super busy day here at #RC2014 Towers. Mostly playing Grid Trap (https://loudscotsbloke.itch.io/grid-trap-altair-680-8800) and Altairis (https://loudscotsbloke.itch.io/altairis-for-the-altair-680) by @loudscotsbloke

Super busy day here at #RC2014 Towers. Mostly playing Grid Trap (https://loudscotsbloke.itch.io/grid-trap-altair-680-8800) and Altairis (https://loudscotsbloke.itch.io/altairis-for-the-altair-680) by @loudscotsbloke

Super busy day here at #RC2014 Towers. Mostly playing Grid Trap (https://loudscotsbloke.itch.io/grid-trap-altair-680-8800) and Altairis (https://loudscotsbloke.itch.io/altairis-for-the-altair-680) by @loudscotsbloke

Super busy day here at #RC2014 Towers. Mostly playing Grid Trap (https://loudscotsbloke.itch.io/grid-trap-altair-680-8800) and Altairis (https://loudscotsbloke.itch.io/altairis-for-the-altair-680) by @loudscotsbloke

Super busy day here at #RC2014 Towers. Mostly playing Grid Trap (https://loudscotsbloke.itch.io/grid-trap-altair-680-8800) and Altairis (https://loudscotsbloke.itch.io/altairis-for-the-altair-680) by @loudscotsbloke

@thelastpsion Preparing already for #RetroFest? But that's month away... oh wait...
Damn! I need to start making up some #RC2014 stock already!

@thelastpsion Preparing already for #RetroFest? But that's month away... oh wait...
Damn! I need to start making up some #RC2014 stock already!

@thelastpsion Preparing already for #RetroFest? But that's month away... oh wait...
Damn! I need to start making up some #RC2014 stock already!

@thelastpsion Preparing already for #RetroFest? But that's month away... oh wait...
Damn! I need to start making up some #RC2014 stock already!

@thelastpsion Preparing already for #RetroFest? But that's month away... oh wait...
Damn! I need to start making up some #RC2014 stock already!

I want to extend my RC2014Pro with a keyboard. I already have a TMS9918-based video card and want to get rid off the serial connection. What kind of keyboard are you using? PS2? USB? MSX? ZX81?

I want a "real" keyboard, not a hardware terminal with Arduino, Pic or Raspberry Pi. I'm using RomWBW and mostly CP/M but sometimes Basic as well. Would be great if the keybord is supported by both.

Dino Boards seems to have a break for a year, their MSX-keyboard and card was my first choice but it's no longer available at Tindie.

#rc2014 #keyboard #retrocomputing

I want to extend my RC2014Pro with a keyboard. I already have a TMS9918-based video card and want to get rid off the serial connection. What kind of keyboard are you using? PS2? USB? MSX? ZX81?

I want a "real" keyboard, not a hardware terminal with Arduino, Pic or Raspberry Pi. I'm using RomWBW and mostly CP/M but sometimes Basic as well. Would be great if the keybord is supported by both.

Dino Boards seems to have a break for a year, their MSX-keyboard and card was my first choice but it's no longer available at Tindie.

#rc2014 #keyboard #retrocomputing

I want to extend my RC2014Pro with a keyboard. I already have a TMS9918-based video card and want to get rid off the serial connection. What kind of keyboard are you using? PS2? USB? MSX? ZX81?

I want a "real" keyboard, not a hardware terminal with Arduino, Pic or Raspberry Pi. I'm using RomWBW and mostly CP/M but sometimes Basic as well. Would be great if the keybord is supported by both.

Dino Boards seems to have a break for a year, their MSX-keyboard and card was my first choice but it's no longer available at Tindie.

#rc2014 #keyboard #retrocomputing

I want to extend my RC2014Pro with a keyboard. I already have a TMS9918-based video card and want to get rid off the serial connection. What kind of keyboard are you using? PS2? USB? MSX? ZX81?

I want a "real" keyboard, not a hardware terminal with Arduino, Pic or Raspberry Pi. I'm using RomWBW and mostly CP/M but sometimes Basic as well. Would be great if the keybord is supported by both.

Dino Boards seems to have a break for a year, their MSX-keyboard and card was my first choice but it's no longer available at Tindie.

#rc2014 #keyboard #retrocomputing

I want to extend my RC2014Pro with a keyboard. I already have a TMS9918-based video card and want to get rid off the serial connection. What kind of keyboard are you using? PS2? USB? MSX? ZX81?

I want a "real" keyboard, not a hardware terminal with Arduino, Pic or Raspberry Pi. I'm using RomWBW and mostly CP/M but sometimes Basic as well. Would be great if the keybord is supported by both.

Dino Boards seems to have a break for a year, their MSX-keyboard and card was my first choice but it's no longer available at Tindie.

#rc2014 #keyboard #retrocomputing

Had some fun yesterday driving this crazy little #RC2014 Mini II around the garden.

Had some fun yesterday driving this crazy little #RC2014 Mini II around the garden.

Had some fun yesterday driving this crazy little #RC2014 Mini II around the garden.

Had some fun yesterday driving this crazy little #RC2014 Mini II around the garden.