Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNC_SYSOPS    |    Synchronet Multinode BBS Software Suppor    |    33,243 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 31,207 of 33,243    |
|    Digital Man to Rixter    |
|    Nightly Batch Maintennance generates err    |
|    20 Jan 25 11:21:34    |
      TZUTC: -0800       MSGID: 57240.sync_sys@1:103/705 2bf4b7d6       REPLY: 57236.sync_sys@1:103/705 2bf465cf       PID: Synchronet 3.20c-Linux master/f836639e8 Jan 19 2025 GCC 12.2.0       TID: SBBSecho 3.23-Linux master/f836639e8 Jan 19 2025 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       NOTE: FSEditor.js v1.105        Re: Nightly Batch Maintennance generates error code 10        By: Rixter to ALL on Mon Jan 20 2025 08:31 am               > Good Morning,        > I found one of my nightly maint batch files on a door I just installed        > generating an error code 10. It is performing the function correctly but I        > see in my events log an error code 10 for it. What is error code 10.              Non-zero error codes are unique to each program, so you'd have to check the       documention for the door in question to know what error condition that is       correlated with. Unfortuantely, many programs don't document their       result/error codes.               > I can run it from dos prompt with no error.              Did you check the error level (e.g. on Windows, that's 'echo %ERRORLEVEL%')?       Just because no error message was displayed doesn't mean that the program       returned an errorlevel of 0.               > All the other nightly maints work fine        > just the new door. It is for a program from shining star software called        > don't wake the sysop I have it set for nightly maint with no options. it        > generates the error code 10 no matter the maint m or maint w or maint        > commands in the events log. Running it locally in dos mode generates no        > error. I will probably just let it run with the error but I was curious what        > an error 10 is.              It's possible that it's not actually an error but rather indicating some other       state/status information. By convention, zero means "no error" and all other       values mean error, but in the DOS world (especially with hobby software), that       wasn't always true.              If you can't get the program to return a zero error level, sett its "Error Log       Level" to something less than "error" will prevent it from logging errors to       your error.log.       --         digital man (rob)              Synchronet "Real Fact" #130:       Synchronet v3.20b was released on January 3, 2025 (3 years after v3.19b)       Norco, CA WX: 62.6øF, 16.0% humidity, 6 mph NNE wind, 0.01 inches rain/24hrs       --- SBBSecho 3.23-Linux        * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)       SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 153/757 7715 154/10       SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114       SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512       SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757       SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888       SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35       PATH: 103/705 280/464 460/58 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca