I've been testing, learning and working on setting up an IMAGE 3.0 BS (using BBS on a Stick) to go online and join the growing community of retro computer advocates. But I keep running into a reliability issues time and again no mater what settings or OS I use.
I've had the same issues running IMAGE on Commodore OS Vision 3.0 (Linux MX), Linux Debian 12, Linux Ubuntu 24 LTS & Windows 10 Enterprise LTSC 21H2.
Everything works perfectly fine with the inbound telnet connections through TCPser to IMAGE, running Vice on all systems, provided you log out of the system perfectly. It seems any abnormal carrier disconnect fails to be reset unless I go into the system remotely and reset the C64 machine in Vice. The images shown represents a 1984 C64 Breadbin connected over my LAN using an Ultimate II+L at 38400 port 6411. I was testing an upload to IMAGE when the carrier dropped unexpectedly. IMAGE never reset the connection despite the C64 actually be completely powered off and unplugged. IMAGE ran for 84 hrs and it never reset the "modem", still thought the connection was still active and was counting up. Also sometimes happens when you "dial-in" and hang up on the login prompt, or elsewhere on the BBS.
What can I do to make this reliable? What am I missing and is there something else I can run to use the Switflink TCP connection when using Vice? Anything available for running on a Mac?
I'd love to run IMAGE on my Breadbin with the Ultimate II+L but it seems the Swiftlink emulation with IMAGE doesn't work yet.
Thanks for any guidance you might have!
Image BBS 3.0 (BBS on a Stick) running inside of VICE 64 on a CommodoreOS Vision 3.0 system (Linux MX) on a late 2012 Apple Mac Mini Server i7 w/ 16GB RAM 1TB SSD. BBS still being developed.
I will leave this to @Bucko to answer, especially the Linux setup. He usually lurks these forums on the regular so I am sure he will have some input for you on this.
The Kats Alley BBS -=[ tka.8bitboyz.com:6400 ]=- ....Running Image 3.0 for the C64
8-Bit Boyz BBS -=[ bbs.8bitboyz.com:6502 ]=- ....Running Mystic on Windows
WEB -=[ www.8bitboyz.com ]=-
I've been testing, learning and working on setting up an IMAGE 3.0 BS (using BBS on a Stick) to go online and join the growing community of retro computer advocates. But I keep running into a reliability issues time and again no mater what settings or OS I use.
I've had the same issues running IMAGE on Commodore OS Vision 3.0 (Linux MX), Linux Debian 12, Linux Ubuntu 24 LTS & Windows 10 Enterprise LTSC 21H2.
Everything works perfectly fine with the inbound telnet connections through TCPser to IMAGE, running Vice on all systems, provided you log out of the system perfectly. It seems any abnormal carrier disconnect fails to be reset unless I go into the system remotely and reset the C64 machine in Vice. The images shown represents a 1984 C64 Breadbin connected over my LAN using an Ultimate II+L at 38400 port 6411. I was testing an upload to IMAGE when the carrier dropped unexpectedly. IMAGE never reset the connection despite the C64 actually be completely powered off and unplugged. IMAGE ran for 84 hrs and it never reset the "modem", still thought the connection was still active and was counting up. Also sometimes happens when you "dial-in" and hang up on the login prompt, or elsewhere on the BBS.
What can I do to make this reliable? What am I missing and is there something else I can run to use the Switflink TCP connection when using Vice? Anything available for running on a Mac?
I'd love to run IMAGE on my Breadbin with the Ultimate II+L but it seems the Swiftlink emulation with IMAGE doesn't work yet.
Thanks for any guidance you might have!
Carrier Detect works fine, I know I am being a jerk. All kidding aside, make sure you have both checkmarks on DSR (both sides). WHen you are at the idle screen make sure there is no checkmark on the lower right side corner of the screen, if there is, it is showing carrier present. Make sure both of those checkmarks are set (then make them permanent via the IM lightbar command) then hit 6 and see if that checkmark goes off if it does you are good to go, if a user drops carrier the BBS will reset to waiting for call. Now there are exceptions, we have been working on fixing for a bit, when a file transfer is in the middle and a user drops carrier it is not resetting, and sometimes it will not reset when someone is in the editor writing a message and they drop carrier. We are working on fixing both of these. Hopefully, we will have fixes for those soon.. Hope that helps a bit..
Bucko
Wrong Number Family of BBS'
Website: www.wrgnbr.com
Wrong Number ][ BBS - wn2.wrgnbr.com:23 (Mystic BBS)
Wrong Number ]I[ BBS - wn3.wrgnbr.com:6400 (CNet Amiga BBS)
Wrong Number IV BBS - wn4.wrgnbr.com:3000 (Image BBS v3.0)
Wrong Number VI BBS - wn6.wrgnbr.com:6411 (ORIGINAL Wrong Number ][ Retro 1993 BBS)
The Time Warp BBS - twb.wrgnbr.com:6896 (Centipede 128 Dual Line BBS)
twb.wrgnbr.com:6897
Image BBS 3.0 (BBS on a Stick) running inside of VICE 64 on a CommodoreOS Vision 3.0 system (Linux MX) on a late 2012 Apple Mac Mini Server i7 w/ 16GB RAM 1TB SSD. BBS still being developed.
Bucko
Wrong Number Family of BBS'
Website: www.wrgnbr.com
Wrong Number ][ BBS - wn2.wrgnbr.com:23 (Mystic BBS)
Wrong Number ]I[ BBS - wn3.wrgnbr.com:6400 (CNet Amiga BBS)
Wrong Number IV BBS - wn4.wrgnbr.com:3000 (Image BBS v3.0)
Wrong Number VI BBS - wn6.wrgnbr.com:6411 (ORIGINAL Wrong Number ][ Retro 1993 BBS)
The Time Warp BBS - twb.wrgnbr.com:6896 (Centipede 128 Dual Line BBS)
twb.wrgnbr.com:6897