Subj : Re: Timed Events..
To   : Al DeRosa
From : Digital Man
Date : Thu Nov 10 2022 17:30:57

  Re: Re: Timed Events..
  By: Al DeRosa to Digital Man on Thu Nov 10 2022 06:48 pm

 > On 10 Nov 2022, Digital Man said the following...
 >
 >
 >  DM> A "255 result code in the error log" sounds like the Synchronet even
 >  DM> thread is running and its attempting to run the events. If you try to
 >  DM> force an event to run, do you see new activity in the event thread log
 >  DM> output or a new error?
 >
 > I see a new error every time I try to force a event to run.
 >
 >
 >  DM> I'm assuming the Tradewars maintence is a 16-bit DOS program. Do native
 >  DM> 32-bit Windows events run okay? It'd be good to isolate which *kinds*
 >  DM> of events you're having problems with. If only 16-bit DOS events are
 >  DM> failing, then that would start to indicate a problem with NTVDM
 >  DM> (assuming we're talking about a Windows version of Synchronet here) -
 >  DM> is this a 32-bit Windows install or are you using NTVDMx64?
 >
 >
 > I am running 16 bit maint progams on a 32 bit Windows Install, I just tried
 > to force a AVAT in and see nothing on the services window, or Terminal
 > Server window of it running.

Timed events are logged in the "Events" window of SBBSCTRL.

 >  DM> The pasted output of your event log would help too.

 > Here is the end of it, nothing about AVAT-IN being run and this is the
 > results of the maint files trying to run..
 >
 > Thu Nov 10 00:00:00 2022 master/a2a9dc027
 > evnt GO Timed event: GO returned 255
 >
 > Thu Nov 10 00:01:00 2022 master/a2a9dc027
 > evnt TJLOTTOM Timed event: TJLOTTOM returned 255
 >
 > Thu Nov 10 00:15:00 2022 master/a2a9dc027
 > evnt TWARAM Timed event: TWARAM returned 255
 >
 > Thu Nov 10 00:15:00 2022 master/a2a9dc027
 > evnt TW3MAINT Timed event: TW3MAINT returned 255
 >
 > Thu Nov 10 02:00:00 2022 master/a2a9dc027
 > evnt TW2MAINT Timed event: TW2MAINT returned 255
 >
 > Is it possible the event services aren't running?

Not sure what an "event services" is. The event *thread* is running or else you wouldn't be seeing these errors.

 > This set up is a 3.19b
 > which was installed from scratch then a migration from a 3.18 system took
 > place
 > after I upgraded that system to 3.19b. Thanks for the help..

No matter. So are only 16-bit DOS programs failing? Do 16-bit DOS programs run successfully as doors on that same BBS?
-- 
                                            digital man (rob)

Synchronet "Real Fact" #122:
Synchronet v2.30a (DOS & OS/2) was released on 5-30-97, 20 months after v2.20b
Norco, CA WX: 59.6øF, 53.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.