home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   SYNCHRONET      Rob Swindell fetishistic worship forum      43,341 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 40,401 of 43,341   
   Digital Man to Nightfox   
   Problems after recent update of sychrone   
   13 Oct 24 13:39:45   
   
   TZUTC: -0700   
   MSGID: 52768.sync@1:103/705 2b723431   
   REPLY: 52766.sync@1:103/705 2b7230d8   
   PID: Synchronet 3.20a-Linux master/27ac33026 Oct 13 202 GCC 12.2.0   
   TID: SBBSecho 3.20-Linux master/639781e2a Oct 13 2024 02:23 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Problems after recent update of sychronet 3.20 files   
     By: Nightfox to Digital Man on Sun Oct 13 2024 01:15 pm   
      
    >   Re: Problems after recent update of sychronet 3.20 files   
    >   By: Digital Man to Amessyroom on Sun Oct 13 2024 02:34 am   
    >   
    >  >> !ERROR in prntfile.cpp line 287 (menu) checking "/sbbs/mods/../xtrn   
    >  >> /DigDist/DDLoginMatrixThemes/bordeaux-tower/LoginBackground.asc"   
    > access=0   
    >   
    >  DM> Does that file exist? The DDLoginMatrix may need to use the P_NOERROR   
    >  DM> flag in calls to menu() if they don't want failures to be reported as   
    >  DM> errors.   
    >   
    > I do want those reported as errors.  I think what may be happening is that   
    > DDLoginmatrix is unable to find the file to be used for the background   
    > (LoginBackground.asc in this case), perhaps because the theme is configured   
    > to look for that filename, or it's supposed to convert an image to sixel   
    > format and that's failing (and it's defaulting to .asc) - either way, it may   
    > indicate something needs to be fixed.   
      
   Okay, it's good that menu() failures are now logged as errors then. For the   
   longest time, menu() failures would be logged, but not as errors, and then a   
   few years back I accdientally introduced a bug that just silenced all menu()   
   failures. That's now fixed and I'm using the normal sbbs_t::errormsg()   
   function to log the details.   
   --    
                                               digital man (rob)   
      
   Synchronet "Real Fact" #48:   
   Synchronet directory naming (i.e. ctrl, exec, data) was suggested by S. Deppe   
   Norco, CA WX: 77.2øF, 41.0% humidity, 4 mph W wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.20-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 90/1 102/401 103/1 17 705 105/81 106/201 124/5016   
   SEEN-BY: 153/7715 218/0 1 215 601 700 840 860 870 880 930 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 266/512 280/464   
   SEEN-BY: 282/1038 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 5075/35   
   PATH: 103/705 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca