Subj : KIA BBS issues
To   : Sniper
From : Digital Man
Date : Mon Sep 15 2025 14:45:11

  Re: KIA BBS issues
  By: Sniper to Digital Man on Mon Sep 15 2025 11:42 am

 >   Re: KIA BBS issues
 >   By: Digital Man to Sniper on Sun Sep 14 2025 01:13 pm
 >
 >  >   Re: KIA BBS issues
 >  >   By: Sniper to Digital Man on Sun Sep 14 2025 09:22 am
 >
 >  >  > Ok, I will rerun it.  To expand.  I attempted this multiple times,
 >  >  > initially, I tried to do the upgrade directly to 3.20 directly as was
 >  >  > not in the documentation.  That failed badly, wouldn't load after the
 >  >  > upgrade and yes, I ran the jsexec update.  So on the next attempt, I
 >  >  > decided to d each update indivudually, 17, 18, 19 and 20.  After 3.20
 >  >  > upgrade, and doi the jsexec update, the system reverted to new
 >  >  > install.  I verified each upgrade,  17, system was working, doors
 >  >  > weren't.  Next 18, after the upda the system worked, not the doors,
 >  >  > and 19 worked, and the doors worked.  W I did 3.20, the system was
 >  >  > destroyed, and was walking me through the init install, as I stated.
 >
 >  > The old (v3.19) *.cnf files are still there. Nothing was "destroyed". If
 >  > you ran v3.20 withOUT running 'jsexec update' first (e.g. as an
 >  > accident), you could have stock/new install .ini files ni your ctrl
 >  > directory. In that case running 'jsexec upgrade_to_v320' would fix that
 >  > situation.
 >
 >  >  > Currently, I did the individual upgrades again, and
 >  >  > stopped this time at 3.19, which is what I'm currently running.
 >  >  > However I getting the error mentioned, not finding the sbbs.ini.  So I
 >  >  > will attempt rerun of the jsexec update, and see if that fixes it.
 >  >  > I'll let you know a few.  :)
 >
 >  > "error finding sbbs.ini" doesn't sound like an upgrade issue. That sounds
 >  > li your SBBSCTRL environment variable isn't set correctly.
 >
 > Checking, and I find that under the Enviroment Variables, in the system
 > variables, there is an entry for SBBSCTRL for c:\sbbs\ctrl listed.

The SBBSCTRL environment variable was only suggested as a possible cause because you reported an error "not finding the sbbs.ini" - but that's not the actual error you're getting. Instead, it woulds like you're having an issue with sbbsctrl.exe *writing* to the sbbs.ini file, not finding or reading it.

 > I also checked the files properties to verify access levels.
 >
 > There is only one user account and it is the admin account.
 >
 > Authenticated Users M/R&E/R/W
 > System Users - All but Speical
 > Administrators = All but Special
 > Users = Read/Write
 >
 > That looks right to me...   Just for giggles, I changed them all to have
 > full permissions, including Special.  Rebooted just to ensure all are set,
 > still no joy.
 >
 > The BBS starts up, with no errors (minus gopher which I turned off).  Only
 > when I exit the BBS do I get that error.
 >
 > Appreciate any other ideas?  :)

I'm assuming this is an error only with sbbsctrl.exe (e.g. you get no error such error if you run sbbs.exe). Similarly, do you get an error if you run scfg.exe and save any changes? I can't think of anything special about sbbsctrl.exe that would prevent it from writing to your sbbs.ini file. Do you get the same error if you try to use the sbbsctrl File->Save Settings menu option?

If sbbsctrl.exe has a problem writing to sbbs.ini but scfg.exe does not, then I would presume they're running differently somehow. Did you check "Run as administrator" or something in some Windows shortcut?
-- 
                                            digital man (rob)

Synchronet "Real Fact" #27:
Rob Swindell (digital man) was born approximately 4 hours before the Unix epoch
Norco, CA WX: 90.2øF, 39.0% humidity, 10 mph WSW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.29-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.