Subj : BullsEye path limitations?
To   : Belly
From : Digital Man
Date : Wed May 18 2022 18:48:42

  Re: BullsEye path limitations?
  By: Belly to Digital Man on Wed May 18 2022 05:40 pm

 >   Re: BullsEye path limitations?
 >   By: Digital Man to Belly on Wed May 18 2022 11:27 am
 >
 >  > It would go to the terminal server log output. In Synchronet Control
 >  > Panel f
 >
 > Crap. Found it. Guess I was overly frustrated and blind last night.
 >
 > 5/18  05:28:16p  Node 1 <Belly> Calling console.printfile(TW2002TW.ANS, 0)
 >
 > That's the copy of TW2002TW.ANS that I placed in the CTRL directory. Nothing
 > was displayed when this was logged. An eval of console.printfile() still
 > does display the file properly.

What if you include the ",0" argument? Does it still display then?

 >  > Maybe you have another coyp of typeasc.js somewhere on your system (e.g.
 >  > mod
 >
 > I thought about that also, last night, and did a search of the C:\SBBS file
 > structure. I repeated that search just now. Nothing. MODS is empty. This is
 > a clean Win10 LTSB x86 VM.

Perhaps the console.aborted flag is set by something before console.printfile() is being invoked? You could try adding a "console.aborted = false" line before the call to console.printfile() in typeasc.js.

We're also using different versions of SBBS. I'm running the latest and greatest and you're still running v3.19b, though, I don't know of any change/fix in this regard. It shouldn't make a difference, but it would be a good test to go ahead and upgrade and try that.
-- 
                                            digital man (rob)

Synchronet "Real Fact" #84:
The Electronic Frontier Foundation used to run Synchronet (circa 1993)
Norco, CA WX: 74.4øF, 57.0% humidity, 7 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.