Jump to content
IGNORED

WiModem 232 settings to call a BBS


DarkLord

Recommended Posts

Hadn't actually seen a guide or message thread here and I need help, so... :)

 

I have the DarkForce! BBS running with a WiModem 232 now and it's (mostly)

going good. People are calling in and successfully downloading files, with some

various setups.

 

I however, can not get my Atari Mega STe with it's WiModem 232 to download

correctly from DarkForce.

 

It always gives (either) CRC errors or subpacket(s) too long and fails.

 

So I've got the WiModem 232, updated to version 4.x. I've got the Serial CPX

set to 19200 and 8N1. RTS/CTS is on (I've tried it with it on and off). I'm using

HSModem, setup for no RSVE hardware to fix the ST's serial port bugs.  Both

machines have the translation set to "raw".

 

Now I'm attaching a picture of TAZ, showing the results from the commands

"ati" and "at&v". If anyone can spot something out of place, I sure would

appreciate it being pointed out.  :)

 

Thanks.

 

 

1832324937_TAZ-WiModem232capture.thumb.JPG.2d32f29d89906bf318aa79e1d5777876.JPG

 

 

Edited by DarkLord
Link to comment
Share on other sites

Nice. 
 

I sent you a msg yesterday that I was able to download. It was crapping out at first but I pointed to the xyz.ttp file again (using ansiterm) and it all of a sudden started downloading and completed!  
 

I d/led the res switch file. Checked it and everything was there. 
 

yes I was in raw mode using ansiterm at 19.2 baud. 
 

great work!

 

craig

Link to comment
Share on other sites

I tested DarkForce over the last several weeks and most recently this weekend and today with every bit of hardware, emulator, term program.

Atari A8 - Term programs: BobTerm, Amodem, Express using the Wimodem and Emulator with all standard configurations - Tested Up/Dl and worked without issue as well as the bbs menus, inputs and message boards (RAW)

Mega ST - Term program used was FLASH, standard Wimodem settings, tested Up/Dl and worked without issue as well as the bbs menus, inputs and message boards

Also tested with SyncTerm - No issues on BBS including successful Up/Dl's

Standard Wimodem settings, latest firmware, no special AT commands used or other.. Board Looks and works great!  

Link to comment
Share on other sites

Just out of curiosity, since I'm having absolutely -zero-luck here, are

you using CPX on the Mega ST and the Serial port CPX?

 

I am, and have it set to 19200, 8n1, RTS/CTS on (although I've tried

it off as well, makes no difference here).

 

I'm also using HSModem 7, to fix the bugs in the ST's serial port/routines.

 

I've also tried with it disabled, but again, it makes no difference.

 

Thanks.

 

Link to comment
Share on other sites

Okay, just for the fun of it, I disconnected my Kubuntu Linux laptop from the LAN and reconnected it via WiFi.

I then launched SyncTerm, connected to DarkForce and downloaded a file. The file did download successfully, but look at SyncTerm's output:

 

(maybe I have something going on with my WiFi?)

 

Screenshot_20210818_012837.thumb.png.7343f8f44658f5f9da47e09fb5b520b8.png

 

Screenshot_20210818_012837b.thumb.png.7052bd189a85d39129e6a22cc92a2bb3.png

Link to comment
Share on other sites

Okay, was up late last night (nothing unusual there) so I fired up my

STacy, with the 3rd WiModem 232 that I bought and tried to down

load from DarkForce. Same exact results, failed with either/and/or

CRC error, subpackets too long, timed out.

 

I tried going with my LAN's IP address (192.168.x.xxx) as well as

the usual darkforce-bbs.dyndns.org blah, blah, blah. That makes

no difference either.

 

Starting to think it's something in my Linksys WiFi but I have no

idea what it could be.

 

Think I'll break a Lantronix UDS-10 back out, put it on my Mega

STe and see if it will download then. It's a straight to LAN CAT5

cable connection and no WiFi involved.

 

Will report back once I've tried it...

 

Link to comment
Share on other sites

Okay, with the Lantronx UDS-10 set to RAW (if it's telnet downloads won't even start),

and attached to my Mega STe, I connected to DarkForce and successfully downloaded

every file I tried.

 

No CRC errors, no subpackets too long, no timeouts. Fast and clean.

 

So it's got to be the Linksys WiFi doing something really strange. I don't have a clue,

nor where to start.  :(

 

Link to comment
Share on other sites

3 hours ago, moonlight_mile said:

Maybe try to backup your firmware setting and reset it to factory and work your way backwards to implement all the settings one by one. 
 

I had an Apple router that stopped port forwarding one of my ports. Couldn’t figure it out and I reset it and started over and it solved the problem. 

I don't know if it's just bit rot...but the last few routers I had seem to stop working after awhile. And a factory reset did not help. My current one seems to be the longest lasting one.

 

-JP
 

Edited by JohnPolka
Link to comment
Share on other sites

2 hours ago, JohnPolka said:

I don't know if it's just bit rot...but the last few routers I had seem to stop working after awhile. And a factory reset did not help. My current one seems to be the longest lasting one.

 

-JP
 

That is for sure. I have a few wrt120n’s floating around and I think both of them are toast. They were hardly used and I dragged them out to use as a switch some months ago and they didn’t work properly. 

Link to comment
Share on other sites

Well, the port forwarding is still working otherwise DarkForce wouldn't be accepting

outside calls at all.

 

The question is, what is WiFi doing that the direct connect LAN is not (or vice-versa)?

 

Uploads and downloads with DarkForce seem to be pretty solid now. It's just any

comp that uses WiFi *here* to access DarkForce for U/L's and D/L's hits a snag.

 

Worse comes to worse? I just leave the UDS-10 on the Mega STe.  :)

 

Link to comment
Share on other sites

  • 4 weeks later...

You're WIFI might need a channel change to avoid congestion or interference, you could also try changing the wifi's preamble length and if it waits it's turn or just trounces other adapters etc etc... you need to check all of you WIFI devices and make sure they are all set up the same way... make sure all of their parameters are the same across the line.

also consider that one wimodem might work fine, but using 2,3,4 or more might have issues depending on their implementation.

Edited by _The Doctor__
Link to comment
Share on other sites

I was able to "prioritize" in the Linksys router's settings. I gave high

priority to the WiModem 232 on DarkForce. It didn't seem to make a

difference.

 

Not sure about "preamble length?". I'll have to try and figure that one

out.

 

There are going to be some differences in the WiModem's, simply because only

1 is setup to receive calls and the other 2 are setup to dial out...

 

Thanks!  :)

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...