Loging Problems

Posted by: @codetsu

↑

I've been fighting BBS crashes for quite some time now but I still haven't gotten it to the level I'd like caused by internet interference that messes up the BBS or freezes it in place.

usually it happens in the IM program on line 3536 when I get it fixed the next freeze happens on line 82 where array tables 1-4 are cleaned i've added program lines to the IM program in the 900-999 area mainly to clean up user writes from the buffer before issuing the ATA command and after that this has helped a little with the freezes but not completely still sometimes it stops at line 82 it would be nice to know what is actually done on that line and what causes the freeze

Is this happening by the press delete key routine? If so, are you running in a SCPU enviroment? If both questions are yes, install the latest updates from 12/31/25. They turn off the SCPU at waiting for call and by doing so it slows the BBS down so bot hits don't crash it. If it is somewhere else on the BBS, please provide me with your setup, real hardware, SDIDE etc. If emulation then SCPU, Lt Kernal etc..

HardWare is the same as always
C64
2x SD2iec
SDPET+ (for RTC)
c1541-II
Zimmer Wimodem Link232

The freeze occurs when the user (Scanner) logs in sometimes the screen has time to print Image 3.0 advertising text sometimes not at all the SFI indicators remain at the bottom right, they do not blink when I made changes to clear the modem input buffer before issuing the ATA command (manual line opening), that text was completely removed and is only printed on the C64 screen but not on the user screen

I think I have the first IM 3.0 version on my test machine, it's newer, but it had similar symptoms until the modem broke down.

The indicator in the lower right corner is constantly on and I can't get it off. I've already considered modifying the modem myself to make it work the way IM wants, but I haven't done that yet. Another option is to abandon the Wifi modem.

despite that, printing to the screen should not crash the machine, nor should resetting the variable array

try to edit the text but time out was to sort...
Let me clarify that I have two C64 systems the main BBS is that C64 2xSD2iec WiModem link232 it has the old IM3.0.

the other C64 2x 1581 1xSD2iec (User-Port) Wimodem the newer IM3.0 It also has a Chameleon card, but it's mainly used for troubleshooting. I've tried it in turbo mode, but the disk drives slow it down so much that you can barely notice the difference.

All have JiffyDos

Posted by: @codetsu

↑

try to edit the text but time out was to sort...
Let me clarify that I have two C64 systems the main BBS is that C64 2xSD2iec WiModem link232 it has the old IM3.0.

the other C64 2x 1581 1xSD2iec (User-Port) Wimodem the newer IM3.0 It also has a Chameleon card, but it's mainly used for troubleshooting. I've tried it in turbo mode, but the disk drives slow it down so much that you can barely notice the difference.

All have JiffyDos

If you have a checkmark all the time on the lower right corner that is because the modem is telling the BBS that carrier is present, try playing with the left side of the DSR lightbar on I think page 3, if it is on turn it off. Or the opposite, then hit 6 to see if it goes off, if not, the modem is not detecting DCD properly. Since we both feel this is a bot issue and you are not running in a SCPU enviroment, see if your modem has a way to delay dropping carrier, in BBS Server you can leave carrier present like in the dial up days when the modem would answer then it would sit there for like 15 seconds while it was waiting to receive a carrier. That might be the only way to prevent this from happening. I am going to bring in @larryhedman to see if he might have any suggestions... Check out those 2 ideas I have suggested and see what happens...

I have tried that setting a million times and haven't noticed any effect  I already read an earlier post about a similar issue and I last tested it a couple of days ago.

but today I tested it again on the main hardware the 6 key didn't do anything to it the hook stays on permanently but today I did something extraordinary and went to the terminal side when its menus were loaded I noticed that the carrier hook was gone I went back to the main screen and it was still gone finally some progress! let's go with this for a few days and see how it affects if it looks good I will make that permanent thanks! it could be that the other one test system Wimodem (user-port) doesn't respond in the same way to that setting and that's why it didn't work on the test hardware I'll try that one later thanks a million even though I should have known how to do this myself and in a way I did but not to the end ! This has been a problem since the beginning that I have not been able to fix (2018) the faster modem has been in use for much less time maybe that's why I had already given up hope of getting the hook to go away because I started with that older User-port version that was in use for at least 5 years if not longer

One more question (in the program IM) when the variable table is cleaned on line 82 what is the & command actually trying to do why does the program hang on that line and the SFI characters stay on as far as I know this function should have nothing to do with the modem?!? Secondly what is the correct way to close the line and check for the existence of the carrier in my own code on lines 900-999 (I can post those lines later, I don't have time now)

the next problem is apparently the BBS out flow management problem which I only have when the other side is PC or Amiga and ANSI I strongly suspect that it is a problem with the modem itself because I have not heard of anyone having similar problems. I have discussed the matter with the modem manufacturer so much that he probably does not want to help me with it anymore :/ because he cannot reproduce my problem and changing the BBS program is not really an option and the problem is not solved, what is the my reason behind it to solve ? .

I confirm that the User-Port Wifimodem (no zimmer core) carrier hook cannot be removed, no setting will make it go away, forcing the modem to invert the polarity of the pins will disable BBS functionality

Posted by: @codetsu

↑

I confirm that the User-Port Wifimodem (no zimmer core) carrier hook cannot be removed, no setting will make it go away, forcing the modem to invert the polarity of the pins will disable BBS functionality

Try this, go into IM from the main prompt, hit J for modem config, and invert DTR, see if that helps with the DCD carrier detect. It might help.. As for the bot issue, using such a low port 1023 I think makes you very susceptible to attacks, I am on 3000 and was getting hit nightly. I ended up having someone write a bot blocker which I run in Linux, it answers the call, if they do not hit // within 5 seconds they get disconnected. It has helped my board tremendously with bot attacks.. You might want to look into something like that, you can set up a Mystic BBS as a front end and use the Phenom bot blocker.. Sorry I can't be much more help other then suggesting you change your port address to something higher..