Basically, I've always run the buffer at 8192 using the AT*BL[x] command. That was the previous maximum. However, as of this update, it looks like Jim has dropped it down to -> 4096 <- . However, after the update, the buffer, according to AT&V, was still showing 8192 on all 3 of my WiModem232's. Now per Jim's advice, I did an AT&F, resetting to factory defaults on the WiModem232 on my Mega STe and then laboriously reset all my settings. I took a screenshot before resetting, BTW. After doing that and noticing that it gave me an error when I tried to do 8192 for the buffer I went back, D/L'ed the updated PDF manual and read about the change there (always, always read the instructions LAST, right?). Seeing Jim had changed it, I used the buffer command to set it to 4096, saved everything, then ran tests on it. It seems okay on that WiModem232 now. So...I thought, why not just try changing that on the other WiModems instead of a full factory reset. I went to my STacy and made the change there, then tested it. Boom! - seems to work okay. I just now made the change to the Mega ST4 that runs DarkForce! and so far, it seems okay there as well too.
Here's a screenshot of one of my WiModem232's, after the firmware update, but before I changed anything. Notice the buffer setting - it's still showing the old upper limit! 😀
For the WiModem232, Jim Drew divided the commands up into standard Hayes compatible commands, using the " & " character, for example, " AT&W " saves your settings and WiModem232 specific commands using the asterisk, for example, "AT*UPDATE" (self explanatory)...
Okay, more fun stuff (I'm using the word "fun" in a way most people wouldn't be familiar with). :)
So I was logged into DarkForce!, my BBS, calling in with Windows10 and SyncTerm. It suddenly stopped responding. I went over to the BBS (this was all in my man cave) and first off, the BBS was still "active" on the Mega ST4 itself. The WiModem232 had changed it's LED color to blue and was now scrolling the screens from the BBS on it's OLED! Weird.
As soon as the screen loaded all the way up on the BBS, it stopped scrolling on the OLED too. You can see it on the screenshots below. I powered the WiModem232 off and restarted it. For the moment, it's working again. I am clueless as to what is going on...
Okay, is anyone else having problems with this last WiModem232 update (3-5-2023)?
On the WiModem232 that I have on the Mega ST4 that runs my BBS, it's working fine for all *incoming* calls. There doesn't seem to be any problem on that end.
However, on the other 2 WiModem232's, whenever I use them to call *out* to my BBS, they work for so long, then it's like the WiModem232 drops back down to the initial startup mode where you can type the usual AT<whatever> commands. The call, meanwhile, is still connected to the BBS, but you can no longer give it commands. When it does this, an "OK" prompt is shown on the screen. I'm going to attach some screenshots to show what I mean. Also, and now it gets really weird, after it does this the "ATI" command says it has new firmware waiting again. Mind you, I've already updated it. I can unplug the WiModem232 and restart it and the new firmware message goes away. At least it does until I try to call the BBS again then it goes through the same cycle. I did try updating again and it reports that it's successful (again) but it didn't fix the problem.
I posted this over at CBM but Jim Drew hasn't responded yet.
Okay folks, from 3pm on, according to WYMT Weather and the Weather Channel, we're supposed to have really "bad stuff" <trademark pending> here so if you can't reach us, you know what happened.
I've had my UPS's kick on and off about 3 times in the last 1/2 hour alone...
Anyone else having difficulty logging on to Darkforce! today? I haven't been able to for about 12 hours, I get either disconnected immediately or I get "Auto-answer not turned on!"...tried multiple clients on multiple machines...
Okay, I think I found the problem...
Basically, I've always run the buffer at 8192 using the AT*BL[x] command. That was the previous maximum. However, as of this update, it looks like Jim has dropped it down to -> 4096 <- . However, after the update, the buffer, according to AT&V, was still showing 8192 on all 3 of my WiModem232's. Now per Jim's advice, I did an AT&F, resetting to factory defaults on the WiModem232 on my Mega STe and then laboriously reset all my settings. I took a screenshot before resetting, BTW. After doing that and noticing that it gave me an error when I tried to do 8192 for the buffer I went back, D/L'ed the updated PDF manual and read about the change there (always, always read the instructions LAST, right?). Seeing Jim had changed it, I used the buffer command to set it to 4096, saved everything, then ran tests on it. It seems okay on that WiModem232 now. So...I thought, why not just try changing that on the other WiModems instead of a full factory reset. I went to my STacy and made the change there, then tested it. Boom! - seems to work okay. I just now made the change to the Mega ST4 that runs DarkForce! and so far, it seems okay there as well too.
Here's a screenshot of one of my WiModem232's, after the firmware update, but before I changed anything. Notice the buffer setting - it's still showing the old upper limit! 😀
In the meantime...
Okay, more fun stuff (I'm using the word "fun" in a way most people wouldn't be familiar with). :)
So I was logged into DarkForce!, my BBS, calling in with Windows10 and SyncTerm. It suddenly stopped responding. I went over to the BBS (this was all in my man cave) and first off, the BBS was still "active" on the Mega ST4 itself. The WiModem232 had changed it's LED color to blue and was now scrolling the screens from the BBS on it's OLED! Weird.
As soon as the screen loaded all the way up on the BBS, it stopped scrolling on the OLED too. You can see it on the screenshots below. I powered the WiModem232 off and restarted it. For the moment, it's working again. I am clueless as to what is going on...
Okay, is anyone else having problems with this last WiModem232 update (3-5-2023)?
On the WiModem232 that I have on the Mega ST4 that runs my BBS, it's working fine for all *incoming* calls. There doesn't seem to be any problem on that end.
However, on the other 2 WiModem232's, whenever I use them to call *out* to my BBS, they work for so long, then it's like the WiModem232 drops back down to the initial startup mode where you can type the usual AT<whatever> commands. The call, meanwhile, is still connected to the BBS, but you can no longer give it commands. When it does this, an "OK" prompt is shown on the screen. I'm going to attach some screenshots to show what I mean. Also, and now it gets really weird, after it does this the "ATI" command says it has new firmware waiting again. Mind you, I've already updated it. I can unplug the WiModem232 and restart it and the new firmware message goes away. At least it does until I try to call the BBS again then it goes through the same cycle. I did try updating again and it reports that it's successful (again) but it didn't fix the problem.
I posted this over at CBM but Jim Drew hasn't responded yet.
And we're finally back online. From Friday evening until about 11:10pm today.
Here's what caused that (this is at Hollybush - about 1/2 mile from me), high winds:
Here's some poor people's home over at Cow Creek:
Ripped the roof right off...
WYMT was reporting widespread power outages, over a 1000 in my county alone:
Okay folks, from 3pm on, according to WYMT Weather and the Weather Channel, we're supposed to have really "bad stuff" <trademark pending> here so if you can't reach us, you know what happened.
I've had my UPS's kick on and off about 3 times in the last 1/2 hour alone...
This month, March 2023, the DarkForce! BBS is giving away a new copy of:
Droids: The Definitive Collection!
Droids: The Definitive Collection contains Droids I + Droids II plus a special STe version. More details here:
https://tinyurl.com/56yy86km
Great Atari game collection. Good luck to all, and thanks for calling! :)
Wow, didn't know we had our own special "event"... 😀
PS First person to post that this "sucks" loses points. 😁
Anyone else having difficulty logging on to Darkforce! today? I haven't been able to for about 12 hours, I get either disconnected immediately or I get "Auto-answer not turned on!"...tried multiple clients on multiple machines...