WiModem232 Pro BETA
#1
I have released a BETA version of the firmware for the WiModem232 Pro (only).  This update has the entire TCP/IP handler re-written with multiple buffers and interrupt driven.  This seems to resolve all of the Z-modem transfer issues I have seen.

In your terminal, type:

AT*BETA  (press RETURN afterwards)

This will update the firmware to the latest BETA version.

To go back tot e original version, type:

AT*UPDATE (press RETURN afterwards)


Please leave feedback if you try this new version!  Thanks!
Reply
#2
I have downloaded and installed it. Zmodem downloads here seem to be a little bit better.

If you recall, I've had quite a few problems where with my wireless and downloading.

Using my Atari Mega STe with a WiModem232 Pro, at 38400 baud, I successfully download
files via Zmodem from my BBS (DarkForce!) which is an Atari Mega ST using a regular
WiModem232 running at 38400 baud. I usually do have a few CRC errors but they do
correct, continue, and finish the download. For example, last night I D/L'ed a 300k
file. It had 14 CRC errors during the download. It did download successfully though
and the ZIP was intact, no corruption.

What I am still seeing is dropped characters. For example, when I use " ? " to cycle
the main menu on DarkForce!, it almost always has a line that's incomplete, with some
garbled or missing text or characters from the screen. It's why I reverted back to the
regular WiModem232 on my BBS instead of the WiModem232 Pro.

When I call in with SyncTerm from my Kubuntu Linux laptop or my Win10 computer, I
don't get the dropped characters.

Here, it's always if there is a WiModem232 Pro anywhere in the connection chain. Whether
that's using it to receive calls or using it to call in. For example, I can call in to DarkForce!
with it's regular WiModem232 with my Atari Mega STe using a Lantronix UDS10 at 19.2k and
I don't see this problem. If I hook up the WiModem232 Pro to DarkForce! and call in with the
Atari Mega STe and the Lantronix UDS10, I get dropped/garbled characters.

I'm open to suggestions on what to do. Thank you so much for these great products and your
continued support.
Reply
#3
This is the first I have heard of any dropped characters. Until this beta, the code was 100% identical between the Pro and non-Pro versions, so this can't be a coding issue really. Did the dropped characters change with the new BETA? The hardware for the WiModem232 is MUCH slower than the WiModem232 Pro, so I wonder if this is a timing issue where responses are happening too fast. Does this occur exactly the same with low baud rates?

Provide me with the info for your Darkforce BBS and I will call it with my Amiga and PC using the WiModem232 Pro.

I am glad to see your Zmodem now goes through. I have tried 300 baud to 460800 baud and I don't even get a single Zmodem CRC error now with the latest beta when using my Amiga or old school DELL Windows XP laptop.
Reply
#4
Okay, it's The DarkForce! BBS:

darkforce-bbs.dyndns.org 1040

You will have to go through the registration process if you've not been there before.

Thanks!

PS Bear in mind DarkForce! is running on the old WiModem232 at 38400 baud currently.
Reply




Users browsing this thread: 1 Guest(s)