<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[CBMSTUFF FORUM - All Forums]]></title>
		<link>https://www.cbmstuff.com/forum/</link>
		<description><![CDATA[CBMSTUFF FORUM - https://www.cbmstuff.com/forum]]></description>
		<pubDate>Sun, 12 Apr 2026 02:36:03 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[Apple IIc + Proterm 3.1]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1248</link>
			<pubDate>Mon, 09 Feb 2026 21:27:02 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=10140">modemiic</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1248</guid>
			<description><![CDATA[Hello all,<br />
<br />
I use Proterm 3.1 with my Apple IIc and WiModem232 V2 @ 9600. I use the suggested initialization string and driver:<br />
<br />
Generic Fixed Speed (RTS/CTS) driver<br />
Init string: ATX1&amp;C0&amp;K1&amp;S1<br />
Apple //c Serial Port<br />
<br />
The cable is this:<br />
1 Handshake Out    20 DTR<br />
2 Data Out             2 TxD    <br />
3 Ground               7 Gnd    <br />
4 Data In               3 RxD      <br />
5 Handshake In      6 DSR    <br />
<br />
Proterm 3.1 can initialize the modem upon startup successfully. <br />
<br />
When I use Proterm's Dial function, Proterm does not recognize that the modem connected. I work around that by going on-line (solid-apple T) and dialing out using ATDS=X, where X is the index of the saved url.  Interestingly enough, Proterm 3.1 does dial out if I use the Smartmodem 300 driver.  <br />
<br />
ZModem downloads start giving errors after the first time the computer saves the file to disk; Proterm reports that it was expecting one type of packet but got another (don't recall the exact packet types now). I need to cancel the download manually and power cycle the modem.<br />
<br />
When I don't do a file transfer and use +++ to get the modem's attention, and then ATH to disconnect, I do not receive anything else from the modem. I can see the modem disconnected (through the OLED display), but I get no response from AT commands (although I also do see the modem gets the commands once again through the OLED display).<br />
<br />
Any ideas of what could be wrong?<br />
<br />
Thanks<br />
<br />
Armando]]></description>
			<content:encoded><![CDATA[Hello all,<br />
<br />
I use Proterm 3.1 with my Apple IIc and WiModem232 V2 @ 9600. I use the suggested initialization string and driver:<br />
<br />
Generic Fixed Speed (RTS/CTS) driver<br />
Init string: ATX1&amp;C0&amp;K1&amp;S1<br />
Apple //c Serial Port<br />
<br />
The cable is this:<br />
1 Handshake Out    20 DTR<br />
2 Data Out             2 TxD    <br />
3 Ground               7 Gnd    <br />
4 Data In               3 RxD      <br />
5 Handshake In      6 DSR    <br />
<br />
Proterm 3.1 can initialize the modem upon startup successfully. <br />
<br />
When I use Proterm's Dial function, Proterm does not recognize that the modem connected. I work around that by going on-line (solid-apple T) and dialing out using ATDS=X, where X is the index of the saved url.  Interestingly enough, Proterm 3.1 does dial out if I use the Smartmodem 300 driver.  <br />
<br />
ZModem downloads start giving errors after the first time the computer saves the file to disk; Proterm reports that it was expecting one type of packet but got another (don't recall the exact packet types now). I need to cancel the download manually and power cycle the modem.<br />
<br />
When I don't do a file transfer and use +++ to get the modem's attention, and then ATH to disconnect, I do not receive anything else from the modem. I can see the modem disconnected (through the OLED display), but I get no response from AT commands (although I also do see the modem gets the commands once again through the OLED display).<br />
<br />
Any ideas of what could be wrong?<br />
<br />
Thanks<br />
<br />
Armando]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Parallel addon]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1243</link>
			<pubDate>Wed, 14 Jan 2026 14:30:31 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=769">Digital Man</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1243</guid>
			<description><![CDATA[Can the supertracker be used in conjunction with a parallel addon in an 1541-ii?]]></description>
			<content:encoded><![CDATA[Can the supertracker be used in conjunction with a parallel addon in an 1541-ii?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Using EmPlant to Expand Memory on Vampire Boards?]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1241</link>
			<pubDate>Sat, 27 Dec 2025 09:40:38 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=9375">lylybrown</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1241</guid>
			<description><![CDATA[Hi everyone, I’m experimenting with EmPlant on my Amiga setup with a Vampire 68080 board. I was wondering if anyone has tried using EmPlant specifically to expand Fast RAM or chip RAM on these boards, and if there are any known compatibility issues with certain Kickstart versions or accelerator settings? Any tips or experiences would be really helpful!]]></description>
			<content:encoded><![CDATA[Hi everyone, I’m experimenting with EmPlant on my Amiga setup with a Vampire 68080 board. I was wondering if anyone has tried using EmPlant specifically to expand Fast RAM or chip RAM on these boards, and if there are any known compatibility issues with certain Kickstart versions or accelerator settings? Any tips or experiences would be really helpful!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Advanced Super Card Pro]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1240</link>
			<pubDate>Sat, 27 Dec 2025 00:24:03 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=286">grider</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1240</guid>
			<description><![CDATA[Jim, any news/updates on the Advanced Super Card Pro development?]]></description>
			<content:encoded><![CDATA[Jim, any news/updates on the Advanced Super Card Pro development?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[WiModem232 Pro BETA]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1239</link>
			<pubDate>Wed, 24 Dec 2025 03:37:22 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=1">admin</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1239</guid>
			<description><![CDATA[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.<br />
<br />
In your terminal, type:<br />
<br />
AT*BETA  (press RETURN afterwards)<br />
<br />
This will update the firmware to the latest BETA version.<br />
<br />
To go back tot e original version, type:<br />
<br />
AT*UPDATE (press RETURN afterwards)<br />
<br />
<br />
Please leave feedback if you try this new version!  Thanks!]]></description>
			<content:encoded><![CDATA[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.<br />
<br />
In your terminal, type:<br />
<br />
AT*BETA  (press RETURN afterwards)<br />
<br />
This will update the firmware to the latest BETA version.<br />
<br />
To go back tot e original version, type:<br />
<br />
AT*UPDATE (press RETURN afterwards)<br />
<br />
<br />
Please leave feedback if you try this new version!  Thanks!]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Trouble with Kaypro disks]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1237</link>
			<pubDate>Sat, 13 Dec 2025 17:37:14 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=9099">Wayback</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1237</guid>
			<description><![CDATA[Hey.<br />
<br />
Been using the SCP for years on my Commodore, but recently wanted to start playing around with my Kaypro.<br />
<br />
Starting off simple, I wanted to try backing up my Kaypro 2X boot disk to an SCP image, then write it out to a blank.  Kind of a proof of concept for me to verify that this thing works for Kaypro disks.<br />
<br />
Unfortunately I haven't had any success.  Perhaps the SCP isn't compatible with Kaypro disks....  I dunno.<br />
<br />
This is why I'm here.  If it doesn't support it, then so be it... but if it should, then could you please provide me with the appropriate settings I should use to backup/restore the disk?<br />
<br />
Thanks for your time.<br />
<br />
Wayback]]></description>
			<content:encoded><![CDATA[Hey.<br />
<br />
Been using the SCP for years on my Commodore, but recently wanted to start playing around with my Kaypro.<br />
<br />
Starting off simple, I wanted to try backing up my Kaypro 2X boot disk to an SCP image, then write it out to a blank.  Kind of a proof of concept for me to verify that this thing works for Kaypro disks.<br />
<br />
Unfortunately I haven't had any success.  Perhaps the SCP isn't compatible with Kaypro disks....  I dunno.<br />
<br />
This is why I'm here.  If it doesn't support it, then so be it... but if it should, then could you please provide me with the appropriate settings I should use to backup/restore the disk?<br />
<br />
Thanks for your time.<br />
<br />
Wayback]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Is there ANY updates available?]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1234</link>
			<pubDate>Sat, 29 Nov 2025 10:26:25 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=685">Mr.Micro</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1234</guid>
			<description><![CDATA[Hey Jim,<br />
<br />
Reaching out here to see if you can provide some sort of insight as to what the expectation level is for the Blingboard and the kepycap situation?<br />
<br />
Everythings been pretty quiet since that whole Chris/Commodore debate and with Commodores now shipping, seems like there should be something said regarding your Blingboard campaign. The 'natives' ae getting restles, but to be fair, the backers deserve am update.<br />
<br />
Best,<br />
J]]></description>
			<content:encoded><![CDATA[Hey Jim,<br />
<br />
Reaching out here to see if you can provide some sort of insight as to what the expectation level is for the Blingboard and the kepycap situation?<br />
<br />
Everythings been pretty quiet since that whole Chris/Commodore debate and with Commodores now shipping, seems like there should be something said regarding your Blingboard campaign. The 'natives' ae getting restles, but to be fair, the backers deserve am update.<br />
<br />
Best,<br />
J]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[WiModem232  OLED  LED  stopped working]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1230</link>
			<pubDate>Tue, 25 Nov 2025 19:31:23 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=1643">bbsing</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1230</guid>
			<description><![CDATA[Today I was using my WiModem232 and after a at&amp;w the LED went out. <br />
<br />
I modified a few things prior to the at&amp;w. <br />
<br />
at*busy=in a call write now call back later<br />
ats0=9<br />
at&amp;w<br />
<br />
that caused the LED to go out. <br />
<br />
I've tried to set the LED via at*led5, at*led0, at*led1, nothing is bring it back. <br />
<br />
I did reboot and complete power cycle nothing helped it. <br />
<br />
I use that LED to see who is trying to login to my system. <br />
<br />
I don't see anyone else with this issue.<br />
<br />
firmware: v6.50-01/20/25]]></description>
			<content:encoded><![CDATA[Today I was using my WiModem232 and after a at&amp;w the LED went out. <br />
<br />
I modified a few things prior to the at&amp;w. <br />
<br />
at*busy=in a call write now call back later<br />
ats0=9<br />
at&amp;w<br />
<br />
that caused the LED to go out. <br />
<br />
I've tried to set the LED via at*led5, at*led0, at*led1, nothing is bring it back. <br />
<br />
I did reboot and complete power cycle nothing helped it. <br />
<br />
I use that LED to see who is trying to login to my system. <br />
<br />
I don't see anyone else with this issue.<br />
<br />
firmware: v6.50-01/20/25]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[ICS64]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1227</link>
			<pubDate>Sun, 16 Nov 2025 22:42:17 -0500</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=8488">Chuck</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1227</guid>
			<description><![CDATA[Hi,<br />
<br />
    Having trouble with a second ICS64 build.  The board keeps failing during the diagnostic sound test (586220 diagnostic cartridge).  It stalls sounding one tone.  All the chips work when placed in the the first build.  The OLED display works fine and I can change to different OS systems loaded in the kernal chip.  Sometimes after turning on the board, without a diagnostic cartridge, the screen hick-ups and freezes with a fast blinking prompt.  The board passes the dead test.<br />
    I'm wondering if I could have cooked some SMD components the backside.  Any suggestions?  <br />
<br />
Thanks]]></description>
			<content:encoded><![CDATA[Hi,<br />
<br />
    Having trouble with a second ICS64 build.  The board keeps failing during the diagnostic sound test (586220 diagnostic cartridge).  It stalls sounding one tone.  All the chips work when placed in the the first build.  The OLED display works fine and I can change to different OS systems loaded in the kernal chip.  Sometimes after turning on the board, without a diagnostic cartridge, the screen hick-ups and freezes with a fast blinking prompt.  The board passes the dead test.<br />
    I'm wondering if I could have cooked some SMD components the backside.  Any suggestions?  <br />
<br />
Thanks]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Unable to upgrade firmware on wimodem232 pro]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1224</link>
			<pubDate>Tue, 21 Oct 2025 13:05:41 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=8048">780tech</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1224</guid>
			<description><![CDATA[at*update<br />
<br />
Process failed! - HTTP error: connection refused<br />
<br />
and YES I am connected to my wifi succesfully<br />
<br />
ideas ?]]></description>
			<content:encoded><![CDATA[at*update<br />
<br />
Process failed! - HTTP error: connection refused<br />
<br />
and YES I am connected to my wifi succesfully<br />
<br />
ideas ?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[SuperCard Pro Advanced]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1223</link>
			<pubDate>Sat, 18 Oct 2025 16:49:41 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=8004">andrean</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1223</guid>
			<description><![CDATA[Hello,<br />
<br />
On the main website, there is a button saying SuperCard Pro Advanced will be available, but I cannot find any additional information about it. Is it still under development, and is it perhaps known what will be the difference between this Advanced version and the already known SuperCardPro model?<br />
<br />
Thanks]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
On the main website, there is a button saying SuperCard Pro Advanced will be available, but I cannot find any additional information about it. Is it still under development, and is it perhaps known what will be the difference between this Advanced version and the already known SuperCardPro model?<br />
<br />
Thanks]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Trouble Imaging CP/M 5.25” SSSD Disks — No Flux Data Captured]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1213</link>
			<pubDate>Fri, 18 Jul 2025 09:29:35 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=1127">Tech</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1213</guid>
			<description><![CDATA[<span style="color: #000000;" class="mycode_color">I’m trying to preserve CP/M 5.25” single-sided, single-density floppy disks, which read and write well on the original CP/M computer.</span><br />
<br />
<span style="color: #000000;" class="mycode_color">Out of the four 5.25” drives I have, three display the message “no index pulse found” when attempting to read the disks using the SCP Disk Analyzer. When I select “Ignore Index Sensor” from the options menu, the software proceeds to read—but I still get <span style="font-weight: bold;" class="mycode_b">no flux data</span>.</span><br />
<br />
<span style="color: #000000;" class="mycode_color">The only drive that can read the disks <span style="font-weight: bold;" class="mycode_b">without</span> ignoring the index sensor also produces <span style="font-weight: bold;" class="mycode_b">no flux data</span>.</span><br />
<br />
<span style="color: #000000;" class="mycode_color">Below are screenshots showing the flux display for head 0 and head 1.</span><br />
<br />
<img src="https://musharka.s3.eu-central-1.amazonaws.com/findex_cpm_track0_flux.png" loading="lazy"  alt="[Image: findex_cpm_track0_flux.png]" class="mycode_img" /><br />
<br />
<img src="https://musharka.s3.eu-central-1.amazonaws.com/findex_cpm_track1_flux.png" loading="lazy"  alt="[Image: findex_cpm_track1_flux.png]" class="mycode_img" /><br />
<br />
<span style="color: #000000;" class="mycode_color">I’m wondering how I can successfully image these old disks. Any help would be greatly appreciated!</span>]]></description>
			<content:encoded><![CDATA[<span style="color: #000000;" class="mycode_color">I’m trying to preserve CP/M 5.25” single-sided, single-density floppy disks, which read and write well on the original CP/M computer.</span><br />
<br />
<span style="color: #000000;" class="mycode_color">Out of the four 5.25” drives I have, three display the message “no index pulse found” when attempting to read the disks using the SCP Disk Analyzer. When I select “Ignore Index Sensor” from the options menu, the software proceeds to read—but I still get <span style="font-weight: bold;" class="mycode_b">no flux data</span>.</span><br />
<br />
<span style="color: #000000;" class="mycode_color">The only drive that can read the disks <span style="font-weight: bold;" class="mycode_b">without</span> ignoring the index sensor also produces <span style="font-weight: bold;" class="mycode_b">no flux data</span>.</span><br />
<br />
<span style="color: #000000;" class="mycode_color">Below are screenshots showing the flux display for head 0 and head 1.</span><br />
<br />
<img src="https://musharka.s3.eu-central-1.amazonaws.com/findex_cpm_track0_flux.png" loading="lazy"  alt="[Image: findex_cpm_track0_flux.png]" class="mycode_img" /><br />
<br />
<img src="https://musharka.s3.eu-central-1.amazonaws.com/findex_cpm_track1_flux.png" loading="lazy"  alt="[Image: findex_cpm_track1_flux.png]" class="mycode_img" /><br />
<br />
<span style="color: #000000;" class="mycode_color">I’m wondering how I can successfully image these old disks. Any help would be greatly appreciated!</span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[OLED display faulty.]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1189</link>
			<pubDate>Sun, 25 May 2025 02:24:14 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=1565">Gods</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1189</guid>
			<description><![CDATA[Hello, the OLED display on my RS232 WIModem is faulty. It works intermittently, mostly off. <br />
It's definitely the display because I connected a different white one and it worked fine. But this one has the "VCC and GND" pins reversed, so it's not compatible. <br />
And what is its actual size?<br />
I ordered a 1.3-inch display (from AliExpress), but it's too big.<br />
What is its actual reference number? (It's difficult to find the layout of the "Vcc-Gnd-Scl-Sda" pins).<br />
I can't send it to you because I'm in Europe. Thank you.]]></description>
			<content:encoded><![CDATA[Hello, the OLED display on my RS232 WIModem is faulty. It works intermittently, mostly off. <br />
It's definitely the display because I connected a different white one and it worked fine. But this one has the "VCC and GND" pins reversed, so it's not compatible. <br />
And what is its actual size?<br />
I ordered a 1.3-inch display (from AliExpress), but it's too big.<br />
What is its actual reference number? (It's difficult to find the layout of the "Vcc-Gnd-Scl-Sda" pins).<br />
I can't send it to you because I'm in Europe. Thank you.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Telnet mode and TERM variable]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1183</link>
			<pubDate>Mon, 19 May 2025 10:41:43 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=2159">rbanffy@gmail.com</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1183</guid>
			<description><![CDATA[Hi.<br />
<br />
When accessing a server in the local network using telnet, I get TERM set to "wimodem", which makes programs confused about the features supported. Is there a register somewhere this string is stored so I can have "vt100", "ansi" or other configuration string compatible with the software running on the computer (or the physical terminal) attached to the modem? I can use my .profile script to force TERM to be something else if I login with it set to "wimodem", but it'd be cool if that could be configured on the modem itself.<br />
<br />
Cheers, and, again, thanks for the amazing product.]]></description>
			<content:encoded><![CDATA[Hi.<br />
<br />
When accessing a server in the local network using telnet, I get TERM set to "wimodem", which makes programs confused about the features supported. Is there a register somewhere this string is stored so I can have "vt100", "ansi" or other configuration string compatible with the software running on the computer (or the physical terminal) attached to the modem? I can use my .profile script to force TERM to be something else if I login with it set to "wimodem", but it'd be cool if that could be configured on the modem itself.<br />
<br />
Cheers, and, again, thanks for the amazing product.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[WiModem shows NO WIFI now]]></title>
			<link>https://www.cbmstuff.com/forum/showthread.php?tid=1169</link>
			<pubDate>Tue, 01 Apr 2025 18:53:53 -0400</pubDate>
			<dc:creator><![CDATA[<a href="https://www.cbmstuff.com/forum/member.php?action=profile&uid=1004">jdryyz</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.cbmstuff.com/forum/showthread.php?tid=1169</guid>
			<description><![CDATA[Not sure what change could have brought this on but I do not recall it happening prior to 6.4<span style="font-weight: bold;" class="mycode_b">1</span> firmware.<br />
<br />
Checking the manual, I may be experiencing the "too close" to my router problem? <span style="font-weight: bold;" class="mycode_b">My WiFi6 router is a relatively new addition to my home network (purchased nearly a year ago) but the WiModem didn't have a problem with it before. </span>I have a few C64s on my test bench which is 8 feet away from my router. Entering at*n does show all the available wi-fi access points. It just won't connect from this location it would seem.<br />
<br />
I connected the WiModem to my C128 which is farther away but still pretty close (it is an adjacent room) and it seems to have no trouble finding and connecting to the router. <br />
<br />
So how close is "too close"? More importantly, could something else have changed to cause this failure to connect?]]></description>
			<content:encoded><![CDATA[Not sure what change could have brought this on but I do not recall it happening prior to 6.4<span style="font-weight: bold;" class="mycode_b">1</span> firmware.<br />
<br />
Checking the manual, I may be experiencing the "too close" to my router problem? <span style="font-weight: bold;" class="mycode_b">My WiFi6 router is a relatively new addition to my home network (purchased nearly a year ago) but the WiModem didn't have a problem with it before. </span>I have a few C64s on my test bench which is 8 feet away from my router. Entering at*n does show all the available wi-fi access points. It just won't connect from this location it would seem.<br />
<br />
I connected the WiModem to my C128 which is farther away but still pretty close (it is an adjacent room) and it seems to have no trouble finding and connecting to the router. <br />
<br />
So how close is "too close"? More importantly, could something else have changed to cause this failure to connect?]]></content:encoded>
		</item>
	</channel>
</rss>