Issues with dialing directory on Win11 25H2.
Something odd is occurring with the personal dialing directory...
I've experienced this issue twice in 3 days..
The issue presents as I am attempting to add a new entry to the dialing list.
SyncTERM allows me to add the entry without error and it appears in the dialing list in the application.
When I attempt to connect to the host the connection fails.
Upon inspection of the affected entry in the directory, the address and port settings are not saved.
Opening the syncterm.lst in Notepad++ shows that the entry has been added to the file...
however... The beginning of the file appears to be a truncated entry, only containing the fields "ConnectionType" "Port" "AddressFamily" TelnetBrokenTextmode" "ScreenMode" "ANSIMusic" and "BPSRate."
I have renamed the file and created a new one with a single entry and am not observing those fields at the beginning of the file.
I am attaching a copy of a broken file to this for review.
Anonymous
The items before the first entry are the Default Connection Settings, Program Settings, etc. It's normal to have at least a few things in there.
I don't see any items in the attached list that do not have an address... what are you seeing when the address and port settings are not saved? Do you have web lists with entries with the same name?
Hi Stephen,
Thank you for your response. Your description of those entries makes sense. I'm including a screenshot that includes the SyncTERM window showing what it is reading from the %appdata%\SyncTERM\syncterm.lst for the currently bugged Entry (No address, incorrect correct port#), the entry that is shown when viewing the %appdata%\SyncTERM\syncterm.lst in NotePad++ (including Find window showing only one match on the Entry Name, no duplicates there), the contents of the %appdata%\SyncTERM\syncterm.ini showing no WebLists, and an explorer window showing the contents of the %appdata%\SyncTERM\syncterm.ini.
I did originally have a WebList, but when the first personal list bugged out on me in this same way I nuked it thinking there might have been a conflict. I still have that one as well (old_syncterm.lst) and it exhibited the same behavior. It appears to save the data for the entry, and it the data is written to the directory list file, but it is not being read by SyncTERM when the list is loaded. It seems to happen when I get to around 30 entries.
I will do some additional testing on Monday to see if I can reproduce the break on demand as I have done it unintentionally twice so far.
Please let me know if there are any particular troubleshooting steps you would like me to perform.
Thank you!
Ok, update. I deleted an entry from the list and the entry that was having trouble updated to show the correct address and port info.
Is there a limit to how many entries you may have in a list?
The only limit is memory and disk space... my current theory is that somewhere the open/read/close thing that SyncTERM does for accessing the list may have a bug somewhere, so I'm combing though that.
Unfortunately, I'm traveling this week, so the work is going fairly slowly.
Would you like me to take a procmon trace or anything like that?
Ah no worries! Safe travels! Let me know if there is anything in particular I could try that may be helpful.
Honestly, I think the most helpful thing would be a series of steps that reproduces the problem every time.
Ticket moved from /p/syncterm/support-tickets/17/
Hi Stephen!
I have just downloaded v1.8 and will test this week.
FYI - https://sourceforge.net/projects/syncterm/files/latest/download still
links to 1.7.
Kind regards,
James Stockton
On Sun, Feb 22, 2026 at 4:01 PM Stephen James Hurd deuce@users.sourceforge.net wrote:
Yes, 1.8 is still in beta until I get all the bugs wrapped up. v1.7 is the current release version.
Understood!
On Mon, Feb 23, 2026, 09:25 Stephen James Hurd deuce@users.sourceforge.net
wrote:
I believe this issue is now fixed. Please download the newest build and confirm.
I run syncterm.exe on windows and I get a window that says failed to decrypt bbs, exiting. OK How do you correct this?
Please create a new issue using an account.
No confirmation after fix, assuming it works.