https://www.cbmstuff.com/forum/ Mon, 24 Aug 2026 20:07:00 +0000 MyBB https://www.cbmstuff.com/forum/showthread.php?tid=1224 Tue, 21 Oct 2025 13:05:41 -0400 780tech]]> https://www.cbmstuff.com/forum/showthread.php?tid=1224
Process failed! - HTTP error: connection refused

and YES I am connected to my wifi succesfully

ideas ?]]>
Process failed! - HTTP error: connection refused

and YES I am connected to my wifi succesfully

ideas ?]]> https://www.cbmstuff.com/forum/showthread.php?tid=1151 Thu, 09 Jan 2025 18:50:48 -0500 mnewkirk]]> https://www.cbmstuff.com/forum/showthread.php?tid=1151
Anyone else been seeing this?
Mike]]>
Anyone else been seeing this?
Mike]]> https://www.cbmstuff.com/forum/showthread.php?tid=977 Sun, 05 Mar 2023 20:55:03 -0500 admin]]> https://www.cbmstuff.com/forum/showthread.php?tid=977
The issue with Mystic BBS using cursor keys has been resolved.  When you press certain keys on a modern keyboard, it generates an ESCape code followed by a 2 byte function code.  The WiModem sees the first character and sends it over the air to the router, followed by the remaining characters as individual transmissions.  Router and over-air communications are very slow due to the latency.  The Mystic BBS software is expecting the ESCape code and the function codes to arrive within a few characters times (microseconds) from each other, which is simply not possible in a WiFi environment when sent individually.  There are two new options that can be tweaked in the future to resolve any potential issues related to the WiModems being too fast for their own good!  This was the issue with the Mystic BBS software.

There is now an option to have the OLED screen power itself off after so many minutes.  These displays really do not have screen burn-in issues, but some people like to have the display dark when not in use.

The packet handling code has been re-written yet again, yielding more performance for uploads/downloads.

The big new feature for the v6.0 firmware is NULL MODEM cable emulation!   You can now use two WiModem or WiModem232 units together to emulate a NULL MODEM cable!  This means that you can use a WiModem232 with a desktop computer via a standard COM port and send data to a RS232 device (like a printer or plotter) that has the other WiModem232 plugged into it!  No more cable required!  You can also connect two computers together to do super fast file transfers - typically 20% faster than just "dialing" from one computer to the other.  NOTE:  When you use the NULL MODEM mode and you return to normal modem operation, the previous router setting will be gone... so you will have to re-establish a connection to your router.]]>
The issue with Mystic BBS using cursor keys has been resolved.  When you press certain keys on a modern keyboard, it generates an ESCape code followed by a 2 byte function code.  The WiModem sees the first character and sends it over the air to the router, followed by the remaining characters as individual transmissions.  Router and over-air communications are very slow due to the latency.  The Mystic BBS software is expecting the ESCape code and the function codes to arrive within a few characters times (microseconds) from each other, which is simply not possible in a WiFi environment when sent individually.  There are two new options that can be tweaked in the future to resolve any potential issues related to the WiModems being too fast for their own good!  This was the issue with the Mystic BBS software.

There is now an option to have the OLED screen power itself off after so many minutes.  These displays really do not have screen burn-in issues, but some people like to have the display dark when not in use.

The packet handling code has been re-written yet again, yielding more performance for uploads/downloads.

The big new feature for the v6.0 firmware is NULL MODEM cable emulation!   You can now use two WiModem or WiModem232 units together to emulate a NULL MODEM cable!  This means that you can use a WiModem232 with a desktop computer via a standard COM port and send data to a RS232 device (like a printer or plotter) that has the other WiModem232 plugged into it!  No more cable required!  You can also connect two computers together to do super fast file transfers - typically 20% faster than just "dialing" from one computer to the other.  NOTE:  When you use the NULL MODEM mode and you return to normal modem operation, the previous router setting will be gone... so you will have to re-establish a connection to your router.]]> https://www.cbmstuff.com/forum/showthread.php?tid=946 Mon, 07 Nov 2022 18:12:18 -0500 admin]]> https://www.cbmstuff.com/forum/showthread.php?tid=946
I also discovered a data type that was being set wrong which would wrap around a byte inside of a word pointer.  This means that any transfer block that exceeded 256 bytes would end up having the wrong data after the 256th byte.  I guess this does not happen very often - it's on the DCE (computer) side, not the internet side.  The baud rate throttles the buffering, and if the baud rate is fast enough with enough contiguous data (no pauses between bytes) this problem can occur (the modem could actually crash from this).  This fixed the odd issues experienced when using the COMMODORESERVER software at 38400 baud.

I added the ability to use your mobile phone to setup the WiModem router connection!  This is super handy and gives you the ability to enter characters for the router and/or password that is not available on the C64 keyboard.

Lots of other little, yet worthwhile features were added.  Check out the history for more details!]]>
I also discovered a data type that was being set wrong which would wrap around a byte inside of a word pointer.  This means that any transfer block that exceeded 256 bytes would end up having the wrong data after the 256th byte.  I guess this does not happen very often - it's on the DCE (computer) side, not the internet side.  The baud rate throttles the buffering, and if the baud rate is fast enough with enough contiguous data (no pauses between bytes) this problem can occur (the modem could actually crash from this).  This fixed the odd issues experienced when using the COMMODORESERVER software at 38400 baud.

I added the ability to use your mobile phone to setup the WiModem router connection!  This is super handy and gives you the ability to enter characters for the router and/or password that is not available on the C64 keyboard.

Lots of other little, yet worthwhile features were added.  Check out the history for more details!]]> https://www.cbmstuff.com/forum/showthread.php?tid=774 Thu, 26 Nov 2020 16:05:17 -0500 admin]]> https://www.cbmstuff.com/forum/showthread.php?tid=774
You can now change any of those when setting the baud rate.  To make the change, add the new config after the baud rate.  Example:

AT*B300,8E1

This would set the baud rate to 300 baud and set the number of data bits to 8, the parity to EVEN, and the number of stop bits to 1.  The following 12 options are available:

8N1
8E1
8O1
8N2
8E2
8O2
7N1
7E1
7O1
7N2
7E2
7O2


ATI now shows the baud rate along with the current data bits, parity, and stop bits.]]>
You can now change any of those when setting the baud rate.  To make the change, add the new config after the baud rate.  Example:

AT*B300,8E1

This would set the baud rate to 300 baud and set the number of data bits to 8, the parity to EVEN, and the number of stop bits to 1.  The following 12 options are available:

8N1
8E1
8O1
8N2
8E2
8O2
7N1
7E1
7O1
7N2
7E2
7O2


ATI now shows the baud rate along with the current data bits, parity, and stop bits.]]> https://www.cbmstuff.com/forum/showthread.php?tid=665 Thu, 28 Nov 2019 10:54:50 -0500 jdryyz]]> https://www.cbmstuff.com/forum/showthread.php?tid=665
I did not see v3.02 listed in the firmware updates thread.

What does it offer?]]>
I did not see v3.02 listed in the firmware updates thread.

What does it offer?]]> https://www.cbmstuff.com/forum/showthread.php?tid=554 Sun, 12 Aug 2018 13:19:05 -0400 tegmah]]> https://www.cbmstuff.com/forum/showthread.php?tid=554
The wimodem display is saying Update available but whenever I type atupdate the response is just error. I've done updates in the past so not sure what is going on. Is the update server online?

Thanks]]>
The wimodem display is saying Update available but whenever I type atupdate the response is just error. I've done updates in the past so not sure what is going on. Is the update server online?

Thanks]]> https://www.cbmstuff.com/forum/showthread.php?tid=499 Thu, 29 Mar 2018 18:37:12 -0400 duhproject]]> https://www.cbmstuff.com/forum/showthread.php?tid=499
Today I booted my c64 and saw a firmware update was available on the LCD display. 

I ran the update command and it updated, but the LCD display output was upside down and it still read there was an update.

I ran the command again and it updated, but now the display doesn't work at all, but the modem still does.

Any ideas on how to get the display back?

-Eric]]>
Today I booted my c64 and saw a firmware update was available on the LCD display. 

I ran the update command and it updated, but the LCD display output was upside down and it still read there was an update.

I ran the command again and it updated, but now the display doesn't work at all, but the modem still does.

Any ideas on how to get the display back?

-Eric]]> https://www.cbmstuff.com/forum/showthread.php?tid=467 Wed, 31 Jan 2018 22:54:41 -0500 eddiefrazetta]]> https://www.cbmstuff.com/forum/showthread.php?tid=467 I know that to upgrade the firmware, one uses at commands, but I was wondering if you'd be open to sharing a download link to the firmware. I would love to tinker with it when I have some spare time, maybe add new features or solder on things like buttons and switches. Thanks in advanced!]]> I know that to upgrade the firmware, one uses at commands, but I was wondering if you'd be open to sharing a download link to the firmware. I would love to tinker with it when I have some spare time, maybe add new features or solder on things like buttons and switches. Thanks in advanced!]]> https://www.cbmstuff.com/forum/showthread.php?tid=463 Sun, 28 Jan 2018 10:52:03 -0500 Amon_RA]]> https://www.cbmstuff.com/forum/showthread.php?tid=463
Hi,

I updated the firmware from v1.95 to v2.31 by entering ATUPDATE, but after the update zterm v1.0f is not returning any characters anymore...

I've set zterm to ASCII mode, and entered ATI but no letters are displayed on the screen and nothing is returned.
Dialing any BBS from the zterm phonebook also returns absolutely nothing anymore.

I switched to NovaTerm 9.0 and here I do get the correct output when I enter ati.
I entered at&f and an OK was returned.

I did however not fix the issues with zterm and the other terminal clients...

Is there a way I can downgrade the firmware back to v1.95 ?]]>
Hi,

I updated the firmware from v1.95 to v2.31 by entering ATUPDATE, but after the update zterm v1.0f is not returning any characters anymore...

I've set zterm to ASCII mode, and entered ATI but no letters are displayed on the screen and nothing is returned.
Dialing any BBS from the zterm phonebook also returns absolutely nothing anymore.

I switched to NovaTerm 9.0 and here I do get the correct output when I enter ati.
I entered at&f and an OK was returned.

I did however not fix the issues with zterm and the other terminal clients...

Is there a way I can downgrade the firmware back to v1.95 ?]]> https://www.cbmstuff.com/forum/showthread.php?tid=428 Wed, 27 Dec 2017 08:01:14 -0500 Zeropage]]> https://www.cbmstuff.com/forum/showthread.php?tid=428
No biggie, but just a heads up.

AT*HELP still lists ATI! for the verbose version of ATI (Instead of ATI1)]]>
No biggie, but just a heads up.

AT*HELP still lists ATI! for the verbose version of ATI (Instead of ATI1)]]> https://www.cbmstuff.com/forum/showthread.php?tid=403 Sat, 14 Oct 2017 15:11:22 -0400 Zeropage]]> https://www.cbmstuff.com/forum/showthread.php?tid=403
Is the AT*T1 setting supposed to survive a power cycle after I AT&W ?

It doesn't seem to, I find I have to re-issue the command every time.]]>
Is the AT*T1 setting supposed to survive a power cycle after I AT&W ?

It doesn't seem to, I find I have to re-issue the command every time.]]> https://www.cbmstuff.com/forum/showthread.php?tid=402 Wed, 11 Oct 2017 21:25:24 -0400 kd4cbm]]> https://www.cbmstuff.com/forum/showthread.php?tid=402
What happens after initial three-way-handshake is a single telnet packet is passed resulting in garbled characters and then hangs. I dropped Bo's firmware on a dev board and did some testing and it seems to connect as it should.

Any ideas on what this could be?]]>
What happens after initial three-way-handshake is a single telnet packet is passed resulting in garbled characters and then hangs. I dropped Bo's firmware on a dev board and did some testing and it seems to connect as it should.

Any ideas on what this could be?]]> https://www.cbmstuff.com/forum/showthread.php?tid=389 Mon, 12 Jun 2017 16:44:54 -0400 AgentFriday]]> https://www.cbmstuff.com/forum/showthread.php?tid=389
When using 38K, sequences of characters longer than 128 sent in close proximity seem to be getting truncated.  This even occurs without screen-blanking. enabled, which means that communication only occurs while the scanline is in the vertical border. 

If I had to speculate (and I know... I don't, but I can't help it... :p)  ...  I'd say there is a 128-byte buffer for receiving from the C64, and the packetization parameters are not tuned well, maybe a watermark needs to be reduced.  I'm kinda surprised that it happens with screen-blanking disabled, because in that mode only about 11 bytes may be transferred per VIC frame, with over 13 milliseconds between each group of 11.

I've only tested this with a program that generates one chat-oriented burst of bytes at a time, and not with the SAVE command, but I'm 99.9% sure that saves will be broken too.  I'll try to test that and post the results.

Let me know if you'd like me to share my test code.
// Agent Friday]]>
When using 38K, sequences of characters longer than 128 sent in close proximity seem to be getting truncated.  This even occurs without screen-blanking. enabled, which means that communication only occurs while the scanline is in the vertical border. 

If I had to speculate (and I know... I don't, but I can't help it... :p)  ...  I'd say there is a 128-byte buffer for receiving from the C64, and the packetization parameters are not tuned well, maybe a watermark needs to be reduced.  I'm kinda surprised that it happens with screen-blanking disabled, because in that mode only about 11 bytes may be transferred per VIC frame, with over 13 milliseconds between each group of 11.

I've only tested this with a program that generates one chat-oriented burst of bytes at a time, and not with the SAVE command, but I'm 99.9% sure that saves will be broken too.  I'll try to test that and post the results.

Let me know if you'd like me to share my test code.
// Agent Friday]]> https://www.cbmstuff.com/forum/showthread.php?tid=326 Thu, 04 Aug 2016 13:22:36 -0400 duhproject]]> https://www.cbmstuff.com/forum/showthread.php?tid=326