Any former C-Net 12.0 Sysops out there? reddit / bbs ---------------------------------------------------------------------- jimmyzeet · 2023-11-25 02:18 I’ve recently started to comb through my c64 disks and convert them to d64. I’ve found tons of pfiles as well as gfiles showing bug fixes and mods etc. All gathered when I was running my former bbs back in the 80s. I’ve even found some of the bigger games like empire, dragon world and murder motel. It’s gotten me fired up to see if I can get my bbs up and running in vice. If nothing else but for the challenge of it. Anyone have a place where one can get pfiles or whatever? Im sure there were hundreds. It would be cool to look at the code and see what made them tick. As I try to get mine running under vice I see I’m missing a few still…. I know someone has them on a floppy in the basement. Somewhere out there! ---------------------------------------------------------------------- Bucko2109 · 2023-11-25 18:16 The problem with 12.0 running in vice is you need a single if it is not cracked. Then getting it to reset to waiting for call with vice and tcpser. Not sure if it is DCD issue or DTR issue but it won't set up properly. If you do get it running document it so the rest of us trying can get ours going. ---------------------------------------------------------------------- jimmyzeet · 2023-11-26 19:44 I definitely got it working and then some. Now I just have to figure out how to get it to see the emulated modem via TCPSER. What settings did you use with Vice and what modem did you select in C-Net 12 setup? The three options are: 1 - HesModem/Mitey Mo/MPS 1064 2 - 1650/Total Tel/Westridge 3 - 1670/Hayes Compatable I definitely remember the dongle. Unfortunately I lost mine and after trying to build one based on the documents out there I had to give up and find a copy that didn't require the dongle. Are you saying that the copy I have has something wrong with it that it won't work to receive calls via TCPSER? Or are the two issues independent? I still have my original copy but no dongle.... ---------------------------------------------------------------------- Bucko2109 · 2023-11-26 19:50 No you are good, the problem is getting it to see tcpser. You would choose option 3 because tcpser would be hayes compatible. It's just for some reason it doesn't see it. ---------------------------------------------------------------------- SpitfireTN · 2023-11-27 16:38 I am a current C-Net SysOp for C-Net DS-II, C-Net 128 and C-Net Amiga. [http://www.rofbbs.com](http://www.rofbbs.com) You may be needing that Dongle. Otherwise option 3 is what you should be using on the C-Net side. I will have to load up my emulated version of C-Net to see how its set up. I am currently running under real hardware (C64) and using BBS Server on a PC. ---------------------------------------------------------------------- jimmyzeet · 2023-11-28 13:59 That would be great. I called your BBS a couple days ago. Nice setup. Cool to see where Image went and is still going. I never got my C-Net 12.1 since it was turned into Image 1.0. But my BBS did incorporate a lot of the mods that came out for 12.0 there were based on Image or C-Net 128. Looking up the settings would be a great help. Currently, I have vice setup to enable ACIA/RS232 on Serial 4. Serial 4 is setup as [127.0.0.1](https://127.0.0.1) : 25232 @ 38400 baud. I wasn't sure if I should be doing 2400. For TCPSER, I had it starting with the following command line: tcpser.exe -v 25232 -s 2400 -p 6400 -l 4 -i "V0X1E0&C1&D2" C-Net 12.0 doesn't seem to see the modem upon startup. The other idea I had was to get ahold of the files shown in this youtube video: [http s://www.youtube.com/watch?v=TfqavlrZOlo&t=1727s](https://www.youtube.c om/watch?v=TfqavlrZOlo&t=1727s). It's C-Net DS II but you can see in a few moments where the guy has modem configs and other things setup. He also can call him C-Net BBS from the same machine. That's what I'm trying to do as well. ---------------------------------------------------------------------- jimmyzeet · 2023-12-02 01:27 >I am a current C-Net SysOp for C-Net DS-II, C-Net 128 and C-Net Amiga. http://www.rofbbs.com > >You may be needing that Dongle. Otherwise option 3 is what you should be using on the C-Net side. I will have to load up my emulated version of C-Net to see how its set up. I am currently running under real hardware (C64) and using BBS Server on a PC. Did you ever dig up those settings? Well, I've gotten a bit further. With my goal of trying to host my C-Net 12.0 BBS locally and calling it with another vice instance runing a terminal program. I think I've got C-Net talking to TCPSER. But the logging, even at level 7, leaves something to be desired. Any thoughts on what I can do next? BBS Vice Setup Using userpost RS232 Emulation Serial 3, 127.0.0.1:25232, 1200 baud cmd: tcpser.exe -v 25232 -s 1200 -p 6400 -i "V0X1E0&C1&D2" -l7 Terminal Program Vice Setup Using ACIA RS232 Interface Serial 4, 127.0.0.1:25233, 38400 baud cmd: tcpser.exe -s 38400 -v 25233 -p 6401 -i "q0e1v1h0x4s0=0&D2&C1&K3" -l4 -tsS -I When the BBS starts up I do get lines in the command window. And it appears to be at least talking to it. *2023-12-01 18:53:43:16469712:DEBUG:Data available on serial port* *2023-12-01 18:53:43:16469712:ENTER\_EXIT:Entering ip232\_read function* *2023-12-01 18:53:43:16469712:INFO:No ip232 socket data read, assume closed peer* *2023-12-01 18:53:43:16469712:ENTER\_EXIT:Exitting ip232\_read function* *2023-12-01 18:53:43:16469712:DEBUG:Read 0 bytes from serial port* *2023-12-01 18:53:43:16469712:DEBUG\_X:Waiting for modem/control line/timer/socket activity* *2023-12-01 18:53:43:16469712:DEBUG\_X:Command Mode=1, Connection status=0* *2023-12-01 18:53:43:16457112:DEBUG:Incoming ip232 connection* *2023-12-01 18:53:43:16457112:DEBUG\_X:Waiting for incoming ip232 connections* When I try to connect to the BBS from the terminal using atdt localhost:6400 it says connected at 38400. I get the following output on the BBS TCPSER instance. *2023-12-01 19:05:57:16469712:DEBUG:Sending 'RING' to modem* *2023-12-01 19:05:57:16469712:DEBUG:Sending RING response to modem* *2023-12-01 19:05:57:16469712:DEBUG\_X:Sending numeric response* *2023-12-01 19:05:57:16469712:DEBUG\_X:Sent #6 ring* *2023-12-01 19:05:57:16469712:DEBUG\_X:Waiting for modem/control line/timer/socket activity* *2023-12-01 19:05:57:16469712:DEBUG\_X:Command Mode=1, Connection status=0* *2023-12-01 19:05:57:16469712:DEBUG\_X:Setting timer for rings* *2023-12-01 19:06:01:16469712:DEBUG:Sending 'RING' to modem* *2023-12-01 19:06:01:16469712:DEBUG:Sending RING response to modem* *2023-12-01 19:06:01:16469712:DEBUG\_X:Sending numeric response* That's where I'm stuck at right now....... I'm not sure if the BBS side is working right or not. But it's definitely "talking" to the modem to some degree. But the BBS won't pickup.... but I don't know if the dual TCPSER instances are fighting with each other. Also wondering if the logs I'm getting from the BBS side actually are validating that the BBS is getting "called". Any ideas?