TZUTC: -0400
MSGID: 58602.sync_sys@1:103/705 2d2e98c9
REPLY: 58597.sync_sys@1:103/705 2d2d3ccc
PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan  2 2022 MSC 1928
TID: SBBSecho 3.29-Linux master/869dac47e Sep 14 2025 GCC 12.2.0
BBSID: KIA
CHRS: CP437 2
FORMAT: flowed
NOTE: SyncEdit 2.50
  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.  

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?  :)





Sniper

Killed In Action BBS, telnet://kiabbs.org

---
 þ Synchronet þ Killed In Action BBS - kia.zapto.org
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 601 610 700 840
SEEN-BY: 218/860 880 226/30 227/114 229/110 206 317 400 426 428 470
SEEN-BY: 229/700 705 266/512 280/464 291/111 301/1 320/219 322/757
SEEN-BY: 342/200 396/45 460/58 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426