• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Hermes BBS install

Byte Knight

Well-known member
I just noticed this on my own local testing instance :p

I'm curious why so many of the externals/addons simply don't work at all - they either crash the BBS or the OS entirely. Presumably at some point they worked, so it's puzzling.
From what I've read, different versions of Hermes require different headers in the externals, so that would explain compatibility issues among the different Hermes II versions.

3.1.1 does seem like the ideal version if running doors is the goal since it has the greatest compatibility. I'd love to be able to run this in Basilisk and have it accept incoming telnet connections but can't wrap my head around how to get that done. I guess I'd need a virtual serial modem in the host OS or something?
Agreed. I haven't tried running v3.1.1 in Basilisk II, but it looks like it may be possible with a USB to serial converter. There's a guide for setting up the emulator with a serial connection on a modern Windows PC here.
 

Byte Knight

Well-known member
With my setup, trying to download a file under v3.1.1 causes the whole BBS to crash shortly after the transfer starts. Uploads cause it to crash as well. I wonder if this is another punishment for running a bad serial number?

@icbrkr - have you noticed this behavior with downloading / uploading files?
 

Byte Knight

Well-known member
3.1.1 does seem like the ideal version if running doors is the goal since it has the greatest compatibility. I'd love to be able to run this in Basilisk and have it accept incoming telnet connections but can't wrap my head around how to get that done. I guess I'd need a virtual serial modem in the host OS or something?
Ok, this should totally be doable in SheepShaver with a WiModem232. I was able to hook up a wifi modem to my MacBook Pro using a USB to RS-232 Adapter and connect to my BBS via ZTerm. I physically attached the adapter, listed all the files in my /dev/ directory, found my adapter (cu.usbserial-A105ZATW) in the list, and added it to the Modem Port Device Settings in SheepShaver. For whatever reason, setting up the serial port the same way in Basilisk II doesn't work, as reported by others...

Screenshot 2024-01-13 at 4.16.56 PM.png

 

cloverskull

Active member
Well now this is interesting! Bummer about it not working in Basilisk, that runs significantly faster for me.

Question - is the device name in your filesystem static? I.e., can it be set and forget, surviving reboots?

This is...frankly amazing. ;)
 
Top