101010.pl

Wintermute_BBS+++ Sysop News +++ Sysop News +++So I'm still investigating the connectivity issues I witnessed with <a href="https://oldbytes.space/tags/rc2014bbs" class="mention hashtag" rel="nofollow noopener" target="_blank">#rc2014bbs</a> and here are my current findings:1.) while the telnet listener of the <a href="https://oldbytes.space/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a> firmware is no longer open on port 2014, the <a href="https://oldbytes.space/tags/wifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#wifi</a> of the <a href="https://oldbytes.space/tags/esp8266" class="mention hashtag" rel="nofollow noopener" target="_blank">#esp8266</a> itself is still active and the reserved ip is responding to ping requests.2.) once the firmware gets reset via ATZ it sometimes restarts /re-opens the listener on port 20143.) the listener dies a few hours after initial powerup of the system4.) my memory may be failing me but those issues began somewhere around autumn last year when I updated the firmware to version 3.7.1As a result of these findings, I have reverted the firmware on the esp8266 to Zimodem version 3.6.5. It's not an official release - I checked it out using the corresponding commit hash.The BBS was powered up with that version yesterday at 09:00 am and it is still running about 24 hours later, which was never the case with the 3.7.1 version of the firmware. I've also noticed a few other glitches not being present with the 3.6.5 version.It is still a little too soon to call the problem solved, but there's movement here. Also keep in mind that RC-BOX BBS (the world's first and - currently - only <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#rc2014</a> based <a href="https://oldbytes.space/tags/bbs" class="mention hashtag" rel="nofollow noopener" target="_blank">#bbs</a>) is using a wifi connection so other sources of influence may also have an effect on connectivity (although they never were *that* worse before 3.7.1).

Daniele Verducci 🧉Hang on... this is bonkers! Booting an IBM PC compatible pc mounting a drive via the <a class="hashtag" href="https://social.ichibi.eu/tag/serialport" rel="nofollow noopener" target="_blank">#serialport</a> ! Something like the modern computers <a class="hashtag" href="https://social.ichibi.eu/tag/netboot" rel="nofollow noopener" target="_blank">#netboot</a> ! <a href="https://youtu.be/g7ScyiO19Pg?si=OcAB5Qsfl4xOykZ0" rel="nofollow noopener" target="_blank">https://youtu.be/g7ScyiO19Pg?si=OcAB5Qsfl4xOykZ0</a> He uses the <a class="hashtag" href="https://social.ichibi.eu/tag/xtide" rel="nofollow noopener" target="_blank">#xtide</a> <a class="hashtag" href="https://social.ichibi.eu/tag/opensource" rel="nofollow noopener" target="_blank">#opensource</a> <a class="hashtag" href="https://social.ichibi.eu/tag/bios" rel="nofollow noopener" target="_blank">#bios</a> (<a href="https://www.xtideuniversalbios.org/" rel="nofollow noopener" target="_blank">https://www.xtideuniversalbios.org/</a>) and a null modem cable to a windows computer. Unfortunately it seems the disk <a class="hashtag" href="https://social.ichibi.eu/tag/emulator" rel="nofollow noopener" target="_blank">#emulator</a> app is available only for Windows, but I imagine it could be implemented in a <a class="hashtag" href="https://social.ichibi.eu/tag/serial" rel="nofollow noopener" target="_blank">#serial</a> <a class="hashtag" href="https://social.ichibi.eu/tag/wifi" rel="nofollow noopener" target="_blank">#wifi</a> <a class="hashtag" href="https://social.ichibi.eu/tag/modem" rel="nofollow noopener" target="_blank">#modem</a> firmware (like <a class="hashtag" href="https://social.ichibi.eu/tag/zimodem" rel="nofollow noopener" target="_blank">#zimodem</a> or <a class="hashtag" href="https://social.ichibi.eu/tag/theoldnet" rel="nofollow noopener" target="_blank">#theoldnet</a> 's). Imagine having a <a class="hashtag" href="https://social.ichibi.eu/tag/samba" rel="nofollow noopener" target="_blank">#samba</a> share on your <a class="hashtag" href="https://social.ichibi.eu/tag/nas" rel="nofollow noopener" target="_blank">#NAS</a> and telling the wifi modem to mount an image on that, then turn on the old pc and boot it from your NAS via WIFI... awesome!!! <a class="hashtag" href="https://social.ichibi.eu/tag/retrocomputing" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a class="hashtag" href="https://social.ichibi.eu/tag/tandy" rel="nofollow noopener" target="_blank">#tandy</a> <a class="hashtag" href="https://social.ichibi.eu/tag/pc" rel="nofollow noopener" target="_blank">#pc</a>

Wintermute_BBSMilestone!!This rather unspectacular screenshot shows my <a href="https://oldbytes.space/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> desktop running <a href="https://oldbytes.space/tags/ArduinoIDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArduinoIDE</a> and <a href="https://oldbytes.space/tags/compiling" class="mention hashtag" rel="nofollow noopener" target="_blank">#compiling</a> <a href="https://oldbytes.space/tags/ESP8266" class="mention hashtag" rel="nofollow noopener" target="_blank">#ESP8266</a> code (<a href="https://oldbytes.space/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a> firmware). Serial communication also works, which is absolutely brilliant!It's been quite a ride until I got it all to work. It's a combination of the steps documented here:<a href="https://forums.freebsd.org/threads/a-guide-for-installing-esp8266-for-arduino-on-freebsd.78411/" rel="nofollow noopener" translate="no" target="_blank">https://forums.freebsd.org/threads/a-guide-for-installing-esp8266-for-arduino-on-freebsd.78411/</a>with additional info (checkout of <a href="https://oldbytes.space/tags/espressif" class="mention hashtag" rel="nofollow noopener" target="_blank">#espressif</a> 2.7.4 codebase) from here:<a href="https://imin.red/2021/05/12/compile-esp8266-esp32-arduino-code-with-gmake-on-freebsd/" rel="nofollow noopener" translate="no" target="_blank">https://imin.red/2021/05/12/compile-esp8266-esp32-arduino-code-with-gmake-on-freebsd/</a>but it also required me to set up <a href="https://oldbytes.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> compatibility (for the <a href="https://oldbytes.space/tags/xtensa" class="mention hashtag" rel="nofollow noopener" target="_blank">#xtensa</a> compiler which is a Linux x86_64 binary) and modify arduino-builder before installing it from <a href="https://oldbytes.space/tags/ports" class="mention hashtag" rel="nofollow noopener" target="_blank">#ports</a> I'll write down my steps in the next days, until then - if you have any questions - please comment. Thank you!

Wintermute_BBSIt's hot, I hate it - so I turn my attention the the <a href="https://oldbytes.space/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> 8251 <a href="https://oldbytes.space/tags/UART" class="mention hashtag" rel="nofollow noopener" target="_blank">#UART</a> which is being used in the MT Telcom II <a href="https://oldbytes.space/tags/modem" class="mention hashtag" rel="nofollow noopener" target="_blank">#modem</a> <a href="https://oldbytes.space/tags/cartridge" class="mention hashtag" rel="nofollow noopener" target="_blank">#cartridge</a> for <a href="https://oldbytes.space/tags/MSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSX</a> systems.I've already converted the cartridge to make use of an <a href="https://oldbytes.space/tags/esp8266" class="mention hashtag" rel="nofollow noopener" target="_blank">#esp8266</a> with <a href="https://oldbytes.space/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a> firmware and desoldered the relays etc. (see here: <a href="https://github.com/dromorobo/MSX-wifi" rel="nofollow noopener" translate="no" target="_blank">https://github.com/dromorobo/MSX-wifi</a>)I guess it shouldn't be too much of a hassle to adapt my existing <a href="https://oldbytes.space/tags/Forth" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forth</a> <a href="https://oldbytes.space/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#code</a> to that chip - that way I could have a very, very simplistic terminal program similar to the one that is included in the cartridge firmware. But unlike the firmware one, the Forth code would offer the chance to add minimalistic terminal emulation and hardware <a href="https://oldbytes.space/tags/flowcontrol" class="mention hashtag" rel="nofollow noopener" target="_blank">#flowcontrol</a>. Sounds like a nice rabbit hole to fall into - not that anyone would need such a software. But I could do it and I wonder wether I should ...<a href="https://oldbytes.space/tags/MSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSX</a> <a href="https://oldbytes.space/tags/WifiModem" class="mention hashtag" rel="nofollow noopener" target="_blank">#WifiModem</a> <a href="https://oldbytes.space/tags/Terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Terminal</a> <a href="https://oldbytes.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> <a href="https://oldbytes.space/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroComputing</a> <a href="https://oldbytes.space/tags/RetroCoding" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroCoding</a>

Wintermute_BBSI wanted to be able to connect to my <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#rc2014</a> CP/M system over the <a href="https://oldbytes.space/tags/LAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#LAN</a> but did not want to replace my <a href="https://oldbytes.space/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a> <a href="https://oldbytes.space/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#firmware</a> with ESP-link. Simple solution: use BYE.COM running as <a href="https://oldbytes.space/tags/RSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSX</a> while not working at the local console.<a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener" target="_blank">#cpm</a>

Wintermute_BBS... more progress on the <a href="https://oldbytes.space/tags/My4TH" class="mention hashtag" rel="nofollow noopener" target="_blank">#My4TH</a> <a href="https://oldbytes.space/tags/ForthDeck" class="mention hashtag" rel="nofollow noopener" target="_blank">#ForthDeck</a> <a href="https://oldbytes.space/tags/WifiModem" class="mention hashtag" rel="nofollow noopener" target="_blank">#WifiModem</a> front - here's the deck talking to my Zimodem firmware on a seperate <a href="https://oldbytes.space/tags/esp8266" class="mention hashtag" rel="nofollow noopener" target="_blank">#esp8266</a> - connection is done over <a href="https://oldbytes.space/tags/I2C" class="mention hashtag" rel="nofollow noopener" target="_blank">#I2C</a> and a <a href="https://oldbytes.space/tags/SC16IS750" class="mention hashtag" rel="nofollow noopener" target="_blank">#SC16IS750</a> <a href="https://oldbytes.space/tags/UART" class="mention hashtag" rel="nofollow noopener" target="_blank">#UART</a> no terminal emulation and no flow-control yet - this is only the raw data coming in. But it's a huge step towards the right direction!! 🥳<a href="https://oldbytes.space/tags/MyNOR" class="mention hashtag" rel="nofollow noopener" target="_blank">#MyNOR</a> <a href="https://oldbytes.space/tags/My4TH" class="mention hashtag" rel="nofollow noopener" target="_blank">#My4TH</a> <a href="https://oldbytes.space/tags/ForthDeck" class="mention hashtag" rel="nofollow noopener" target="_blank">#ForthDeck</a> <a href="https://oldbytes.space/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a> <a href="https://oldbytes.space/tags/WifiModem" class="mention hashtag" rel="nofollow noopener" target="_blank">#WifiModem</a> <a href="https://oldbytes.space/tags/SC16IS750" class="mention hashtag" rel="nofollow noopener" target="_blank">#SC16IS750</a>

Steve (hacks the) GibsonToday I successfully compiled and flashed the Zimodem firmware onto my ESP8266 WiFi board for the <a href="https://mastohack.com/tags/RC2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#RC2014</a>. I did have some trouble getting various clock/baud rates to work without garbling or dropping characters, so had to fall down to 4800 to get stable TX/RX (will troubleshoot this more later). I was then able to use QTerm to connect to the BBS that <a href="https://oldbytes.space/@Wintermute_BBS" class="u-url mention" rel="nofollow noopener" target="_blank">@Wintermute_BBS</a> runs on an RC2014 (rc2014.ddns.net:2014). At 4800 it was slooow, but very cool! 🔥😎<a href="https://mastohack.com/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#RetroComputing</a> <a href="https://mastohack.com/tags/Z80" class="mention hashtag" rel="nofollow noopener" target="_blank">#Z80</a> <a href="https://mastohack.com/tags/CPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPM</a> <a href="https://mastohack.com/tags/ESP8266" class="mention hashtag" rel="nofollow noopener" target="_blank">#ESP8266</a> <a href="https://mastohack.com/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a>

Wintermute_BBS<a href="https://toot.wales/@gilesgoat" class="u-url mention" rel="nofollow noopener" target="_blank">@gilesgoat</a> It's single user, yes. BYE.COM can only manage one connection coming in.There once was MP/M which is a multi-user variant of CP/M that could host multiple users. This is not what I run. I run the original CP/M 2.2.The <a href="https://oldbytes.space/tags/Zimodem" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zimodem</a> firmware of the WiFi modem module for my <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#rc2014</a> does the serial to TCP/IP translation and telnet gating. So it knows if a connection is already active and will show a "BUSY" message to anyone else trying to connect (via telnet).Basically, BYE.COM routes all console I/O to the serial port and, when idle, listens for incoming calls monitoring the DCD signal of the modem (which can also be a classic analog phone-line modem).The BYE.COM sources and overlays / code "inserts" (patches) for assembling it can be found here:<a href="http://cpmarchives.classiccmp.org/ftp.php?b=cpm%2Fmirrors%2Foak.oakland.edu%2Fpub%2Fcpm%2Fbye5" rel="nofollow noopener" target="_blank">http://cpmarchives.classiccmp.org/ftp.php?b=cpm%2Fmirrors%2Foak.oakland.edu%2Fpub%2Fcpm%2Fbye5</a>Generally, you should take some time and visit the complete site, as it's full of CP/M software, source codes and information:<a href="http://cpmarchives.classiccmp.org/" rel="nofollow noopener" target="_blank">http://cpmarchives.classiccmp.org/</a>

Recent searches

Search options

Administered by:

Server stats:

#zimodem