So, I've been having issues getting DarkForce to play nicely with my STe of late. It worked fine (really well) for months and months with my setup, but just in the last month or so things have gone wonky. I've also posted this issue on DarkForce itself but since I cannot post photos there, DarkLord suggested I post them here. Regardless, my setup is a 4MB STe with an Adspeed Accelerator, Wimodem (latest firmware) and any terminal program. Used to use FDT the most, but also AnsiTerm, Flash and Taz. I constantly get missed lines and missing characters and it makes it hard to use. See the photos...
Further...I've tried rebooting the router, the cable modem, the wimodem, and even switched wifi networks.
Thoughts or ideas?
Dang. Sorry to hear that - hope you can get it resolved soon.
Hate it that sometimes these things are darned near impossible to figure out. I still can't figure out why I can't do a wireless download across my own LAN. Direct (LAN to LAN) works fine. Still working on that one...
Did you ever get the problem with DarkForce resolved?
Ill check this out as it may go to a spam filter. Thanks for the heads up and all your support! Appreciate you keeping the BBS world going!
Agreed. Hope to see you around southernamis.ddns.net:23
it definitely seems like a wifi issue on my end. thanks for the help. I'll try some more wifi troubleshooting and running the update again... the issues on the fujinet make me think it's not the wimodem though...
I logged in to your account on DarkForce using Syncterm and my Win10 box. Everything was fine there.
Logged in using both TAZ and ANSITerm with a WiModem 232 on my Mega STe. Again, everything was fine.
So I think it's safe to conclude it's not your DarkForce account, TAZ, ANSITERM, the WiModem 232, etc, etc,..
I had an issue with the modem when updating to the latest firmware and the mesh router. One day it was bad, unplugged the wimodem and next time it worked fine. Maybe try another AT*UPDATE and see if the firmware update is the cause. Might just need another run at the update
It is, It's a linksys Velop mesh system. But I can go around it and connect directly to the wifi signal from the cable modem...same issue. What boggles me, is that it worked great for months and months....
Works with SyncTerm but not the wimodem. I think this maybe a router issues. Not location but possible mismatch between the modem and router. What router are you using? is a Mesh System?
I am, yes.
I'm assuming that you're using the WiModem 232 in "raw" mode.
The command is "at*t0" which is the default. "at*t1" makes the translation telnet instead.
We used the telnet translation with the UDS-10 that we were using before, for years. When we switched to the WiModem 232, we changed to raw....
Well scratch the location theory... it's happening in the my STe's old home too. It also happens on my 8bit when I call darkforce using fujinet and ICE-T, it doesn't happen from my PC (Windows) or laptop (Linux) - both with SyncTerm.
I've tried sfhq, I get similar issues, it works better on VT-52 than ANSI but I get issues regardless. However, when I call the bottomless abyss I don't have any issues at all. I use FDT for that one, it's the only ST terminal software I've found that works with it.
Random thought occurred to me last night. I moved my STe physically about four feet. Doesn't sound like much but now the wimodem is within 18 inches of the main electrical panel for my house. Would that make a difference?
What other bbs's do you call? Happening anywhere else?
Well that looks interesting.. Its cutting of a big section of data. Almost looks like a buffer issue. Is the WiModem a CBMstuff 232?