> On 32-bit Windows, you can log on locally to SBBS from the GUI by selecting
> BBS, then Login. Works great, been using it for years.

> On 64-bit Windows, this doesn't work. Every time I try to do it, it ignores
> it.

I can confirm this behaviour on a 64bit install here.  Some additional info:

- Win+R to run telnet://127.0.0.1 launches telnet.exe and connects to the BBS,
so telnet.exe is installed and setup as the default handler.
- Entering telnet://127.0.0.1 in Chrome also launches telnet.exe and connects
to the BBS
- These login commands do NOT work:
  - telnet://127.0.0.1
  - telnet 127.0.0.1
  - C:\Windows\System32\telnet.exe 127.0.0.1
- These login commands DO work:
  - C:\Program Files (x86)\SyncTERM\syncterm.exe 127.0.0.1
  - notepad (of course by "work" I mean it opens notepad, not that it connects
to the BBS)

After confirming what did and didn't work with the default settings, I set
SyncTERM as the telnet handler (set HKEY_CLASSES_ROOT\telnet\shell\open\command
to "C:\Program Files (x86)\SyncTERM\syncterm.exe" %1), and at that point the
default login command of telnet://127.0.0.1 works as expected (ie it opens
SyncTERM and connects to the BBS)

So it seems like Synchronet is unable to launch telnet.exe on at least some
64bit installs, not by the default telnet handler, or even by specifying the
full path to telnet.exe.

> I created an icon shortcut on the desktop to do a "telnet
> ftelnet.synchro.net" and that is a good work around.

ftelnet.synchro.net is my dns name, which would cause the shortcut to connect
to my test system, so I'm guessing that was just a typo?

---
 þ Synchronet þ fTelnet Demo Server - ftelnet.synchro.net