i updated one that was in c:\synchronet and it didn't work out well
What happened?
i also set the environment in the Os.
Okay. But what happened?
Like i said, The update scripts wouldn't work correctly.
update.js you mean?
I had to change everything to sbbs\ and then change it back later.
That's pretty weird.
Re: chksetup.js output
By: Digital Man to MRO on Sat Apr 25 2026 09:12 pm
i updated one that was in c:\synchronet and it didn't work out well
What happened?
i also set the environment in the Os.
Okay. But what happened?
Like i said, The update scripts wouldn't work correctly.
update.js you mean?
I had to change everything to sbbs\ and then change it back later.
That's pretty weird.
https://www.veed.io/view/ad2b464a-af68-43c3-96eb-8802f0ad396d?source=editor& pa nel=share
https://tinyurl.com/sbbsupdate1
so i nailed it down i think. i typed c:\synchronet in the update program and the upgrade scripts still try for sbbs\ if there is no sbbsctrl or sbbsnode environment set.
i was doing this on a vm.
this was on windows 8 32bit because the sysops bbs was running on that os.
after i set the environments and ran it again it worked correctly.
environment variable would have been set already as well. The fact
that the prerequisite MSVC libraries weren't already installed (as demonstrated in the video) is another good clue that Synchronet
wasn't previously installed on that system.
after i set the environments and ran it again it worked correctly.
I don't see anything to change from my perspective.
Re: chksetup.js output
By: Digital Man to MRO on Sun Apr 26 2026 01:05 pm
environment variable would have been set already as well. The fact
that the prerequisite MSVC libraries weren't already installed (as demonstrated in the video) is another good clue that Synchronet
wasn't previously installed on that system.
well it's not a clue. i said that. i told you i was updating it in a vm.
the sysop runs his bbs on shitty windows 8 so i made a vm to update it to make sure things would run for him.
after i set the environments and ran it again it worked correctly.
I don't see anything to change from my perspective.
if you run the update, and you type in the path in the update program the updater script wont use that path and expects sbbs/. it should atleast nag the person to set the environment variable. and i thought we didn't have to do that manually anymore?
it would be ideal if the update script actually used the path it asks the user to provide. https://i.imgur.com/NX3gcEd.png
in the install i typed in the correct path to the synchronet install, and the update script still expects sbbs
And why are you still using the windows registry when you have all these ini files?
"updating in a vm" is not the same as "upgrading a non-installed Synchronet".
Maybe actually install it first, next time.
("c:\sbbs") - if you're using a custom/non-standard install
location, then yes, you need to. And the installer does it for you
- when you use it.
It will in the next release. But it also would've worked just fine
had you just installed sbbs before upgrading it.
"updating in a vm" is not the same as "upgrading a non-installed Synchronet".
well it depends on what you consider installed.
the files were there on the system.
i was updating it in a vm.
Maybe actually install it first, next time.
i come from a time when you didn't install it, you just
got the files and ran it.
("c:\sbbs") - if you're using a custom/non-standard install
location, then yes, you need to. And the installer does it for you
- when you use it.
i used the updater and it asked for the synchronet path. why couldn't it update it using the path i provided? you explain why, but it should.
it should be looking for the synchronet/ctrl because i typed in synchronet for the directory location.
It will in the next release. But it also would've worked just fine
had you just installed sbbs before upgrading it.
if you say so, i didn't think it was such a big deal.
the files were in the directory. i thought that was good enough.
i'm just telling you what i ran into.
Obviously people aren't speaking up when they run into issues or they are just being npcs; there's been a lot of issues with this 3.21x release. people didn't test things.
This sysop ran synchronet in a weird directory and something came up. i thought it was worth telling you about it. sorry for being edgy!
well it depends on what you consider installed.
"installed" means having run the installer.
Synchronet has always had an installer, even going back to the MS-DOS
days.
| Sysop: | Greg Meckel |
|---|---|
| Location: | Anchorage, AK |
| Users: | 8 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 26:01:30 |
| Calls: | 198 |
| Files: | 2,681 |
| Messages: | 24,218 |
| Sysop: | Greg Meckel |
|---|---|
| Location: | Anchorage, AK |
| Users: | 8 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 26:01:30 |
| Calls: | 198 |
| Files: | 2,681 |
| Messages: | 24,218 |