Hi, all,

I have a file that BullsEye bulletins refuses to display. I was wondering if its location, in the /sbbs/xtrn directory (instead of in a subdirectory) might be the issue. It's just a Tradewars high sore file (.ANS), but I am at my wits' end with it. BullsEye just goes right back to its menu when that option is selected.

Thanks

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net - WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to All on Thu May 12 2022 10:07 pm

I have a file that BullsEye bulletins refuses to display. I was wondering if its location, in the /sbbs/xtrn directory (instead of in a subdirectory) mig

It turns out not to be path-related. A text file in the same directory works fine. There just seems to be something about that .ans file that it doesn't like, althoughwhen peeking at it in other editors, I see nothing obviously wrong (although I am definitely no expert)

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net - WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to All on Thu May 12 2022 10:07 pm

Hi, all,

I have a file that BullsEye bulletins refuses to display. I was wondering if its location, in the /sbbs/xtrn directory (instead of in a subdirectory) might be the issue. It's just a Tradewars high sore file (.ANS), but I am at my wits' end with it. BullsEye just goes right back to its menu when that option is selected.

That should work fine. What are the contents of your bullseye.cfg file?

There's also BullsHit (xtrn/bullshit) which you might want to give a try.
--
digital man (rob)

This Is Spinal Tap quote #45:
I don't really think the end can be assessed as of itself as being the end Norco, CA WX: 80.8øF, 19.0% humidity, 2 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Belly on Fri May 13 2022 08:48 am

Re: BullsEye path limitations?
By: Belly to All on Thu May 12 2022 10:07 pm

I have a file that BullsEye bulletins refuses to display. I was wondering if its location, in the /sbbs/xtrn directory (instead of in a subdirectory) mig

It turns out not to be path-related. A text file in the same directory works fine. There just seems to be something about that .ans file that it doesn't like, althoughwhen peeking at it in other editors, I see nothing obviously wrong (although I am definitely no expert)

What is the filename? If it's a *nix system, the file system will be case-sensitve. Could that be the issue (e.g. filename.ans vs. FILENAME.ANS)?
--
digital man (rob)

This Is Spinal Tap quote #34:
We'd love to stand around and chat, but we've gotta sit down in the lobby Norco, CA WX: 80.8øF, 19.0% humidity, 2 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 10:33 am

That should work fine. What are the contents of your bullseye.cfg file?

I have placed a copy at http://music.brazi.net/temp/bullseye.cfg

and the problematic .ANS file: http://music.brazi.net/temp/TW2002TW.ANS

As I mentioned in another post, replacing TW2002TW.ANS in the bullseye.cfg with the TW2002TW.TXT text version works... Just not as colorfully!

There's also BullsHit (xtrn/bullshit) which you might want to give a try.

I saw that! Lots of new stuff during the 15 years I was away! I might give it a try if I get time.

Thanks,

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net - WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Fri May 13 2022 01:04 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 10:33 am

That should work fine. What are the contents of your bullseye.cfg file?

I have placed a copy at http://music.brazi.net/temp/bullseye.cfg

and the problematic .ANS file: http://music.brazi.net/temp/TW2002TW.ANS

As I mentioned in another post, replacing TW2002TW.ANS in the bullseye.cfg with the TW2002TW.TXT text version works... Just not as colorfully!

That TW2002TW.ANS displays fine using BullsEye for me: https://1drv.ms/u/s!ApZPvWcrEaRQ1LchKaxzvel_3-dNuw?e=YMNHxe

BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js just calls console.printfile(). So you could experiment with the ;exec Sysop command (to execute typeasc.js) or ;eval command (to execute console.printfile) and perhaps find what's failing for you exactly, but it's working fine here.
--
digital man (rob)

Breaking Bad quote #18:
Already, Operation: TBD, thanks for nothing Gomey. - Hank Schrader
Norco, CA WX: 82.8øF, 17.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)

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 10:33 am

I have placed a copy at http://music.brazi.net/temp/bullseye.cfg

and the problematic .ANS file: http://music.brazi.net/temp/TW2002TW.ANS

As I mentioned in another post, replacing TW2002TW.ANS in the bullseye.cfg with the TW2002TW.TXT text version works... Just not as colorfully!

I saw that! Lots of new stuff during the 15 years I was away! I might give it a try if I get time.

Thanks,

o
(O)
BeLLy

---
â–  Synchronet â–  bbs.brazi.net - WARNING: May contain nuts

Synchronet BBS is chocked full of goodies. :-)

$ The Millionaire $
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 10:35 am

What is the filename? If it's a *nix system, the file system will be case-se

It's Windows. And I tried ensuring it matched, just in case. Puzzling.

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net - WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 11:45 am

That TW2002TW.ANS displays fine using BullsEye for me:

Curioser and curioser...

BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js jus

I might have tried the ;list sysop command on it, too, which is why I decided it was an issue with the file. I was very sleepy at the time.

Thank you for your help. I shall poke at it further.

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net - WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Fri May 13 2022 03:09 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 10:35 am

What is the filename? If it's a *nix system, the file system will be case-se

It's Windows. And I tried ensuring it matched, just in case. Puzzling.

Sounds like it's not an issue with the filename.
--
digital man (rob)

Breaking Bad quote #32:
Don't think so hard it's gonna hurt your brain! - Hank Schrader
Norco, CA WX: 92.4øF, 13.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 11:45 am

BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js jus

Okay... Incoming weirdness!

I tried ;exec ?typeasc.js ../xtrn/tw2002tw.ans ... nothing. Right back to the menu.

But: ;exec ?typeasc.js ../xtrn/tw2002tw.txt ... my "control" test, works fine.

I promise that the first file, with the .ans extension, DOES exist in that location.

As an experiment, I pulled in the entire sbbs/exec tree from Git, just to make sure nothing's corrupt. The strange behavior persists.

Wondering now if I should just save some things, blow the whole thing away, and rebuild. This install dates from 2004.

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net - WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Fri May 13 2022 10:50 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 11:45 am

BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js jus

Okay... Incoming weirdness!

I tried ;exec ?typeasc.js ../xtrn/tw2002tw.ans ... nothing. Right back to the menu.

But: ;exec ?typeasc.js ../xtrn/tw2002tw.txt ... my "control" test, works fine.

I promise that the first file, with the .ans extension, DOES exist in that location.

As an experiment, I pulled in the entire sbbs/exec tree from Git, just to make sure nothing's corrupt. The strange behavior persists.

Wondering now if I should just save some things, blow the whole thing away, and rebuild. This install dates from 2004.

No, I would not recomend doing that.

Did you experiment with directly executing console.printfile() via the ;eval sysop command?
--
digital man (rob)

Breaking Bad quote #3:
Please tell me: how much is enough? How big does this pile have to be? - Skyler Norco, CA WX: 63.7øF, 61.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Sun May 15 2022 10:58 pm

Did you experiment with directly executing console.printfile() via the ;eval

Okay... Kind of feeling dumb here, but the menu shell cuts off my input and I don't have enough room to enter the entire eval command... Increasing terminal width doesn't help, either. Suggestions?

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Mon May 16 2022 04:46 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Sun May 15 2022 10:58 pm

Did you experiment with directly executing console.printfile() via the ;eval

Okay... Kind of feeling dumb here, but the menu shell cuts off my input and I don't have enough room to enter the entire eval command... Increasing terminal width doesn't help, either. Suggestions?

Type ;eval and hit enter, it'll prompt for the parameter:

;eval
Parameter(s): console.printfile("../xtrn/tw2002tw.ans")


Trade Wars 2002 Trader Rankings : 05/13/34 00:25:27 AM

# Rank Title Corp Trader Name Ship Type
-+- --------------------- -- ------------------------------ ------------------
1 Warrant Officer ** Belly Scout Marauder Result (boolean): true
--
digital man (rob)

This Is Spinal Tap quote #29:
I find lost luggage. I locate mandolin strings in the middle of Austin!
Norco, CA WX: 75.4øF, 51.0% humidity, 10 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Mon May 16 2022 04:48 pm

Type ;eval and hit enter, it'll prompt for the parameter:

Thanks!

That does display the file properly, for me. It's the only method to do so, thus far.


o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Mon May 16 2022 09:08 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Mon May 16 2022 04:48 pm

Type ;eval and hit enter, it'll prompt for the parameter:

Thanks!

That does display the file properly, for me. It's the only method to do so, thus far.

Okay, well, typeasc.js is just a wrapper for console.printfile(). So... perhaps there's something different/wrong/old with your copy of typeasc.js?
--
digital man (rob)

Sling Blade quote #18:
Karl Childers: Some folks call it Hell, I call it Hades.
Norco, CA WX: 65.4øF, 67.0% humidity, 5 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Mon May 16 2022 08:15 pm

Okay, well, typeasc.js is just a wrapper for console.printfile(). So... perh

I had pulled down the entire /exec directory from Git on Friday. Just now, I extracted a fresh copy of typeasc.js to make sure. No change in behavior.

It's perplexing, but not really a huge deal. I'll keep using the text version.

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Mon May 16 2022 11:33 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Mon May 16 2022 08:15 pm

Okay, well, typeasc.js is just a wrapper for console.printfile(). So... perh

I had pulled down the entire /exec directory from Git on Friday. Just now, I extracted a fresh copy of typeasc.js to make sure. No change in behavior.

It's perplexing, but not really a huge deal. I'll keep using the text version.

Try copying the file to your "ctrl" directory and run "?typeasc tw2002tw.ans" (no path)? The ctrl directory is the current working directory when running sbbs or (by default) JSexec. I would like to help you get to the bottom of this.
--
digital man (rob)

Rush quote #81:
Catch the witness, catch the wit, catch the spirit, catch the spit
Norco, CA WX: 58.1øF, 90.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Fri May 13 2022 03:13 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 11:45 am

That TW2002TW.ANS displays fine using BullsEye for me:

Curioser and curioser...

BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js jus

I might have tried the ;list sysop command on it, too, which is why I decided it was an issue with the file. I was very sleepy at the time.

Thank you for your help. I shall poke at it further.

do you actually HAVE that file in your xtrn/ directory or is it in a sub dir? it's kinda messy to put it in the xtrn/ dir and not the sub dir of the doorgame.

maybe you have the path wrong in the cfg
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Fri May 13 2022 10:50 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Fri May 13 2022 11:45 am

BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js jus

Okay... Incoming weirdness!

I tried ;exec ?typeasc.js ../xtrn/tw2002tw.ans ... nothing. Right back to the menu.

But: ;exec ?typeasc.js ../xtrn/tw2002tw.txt ... my "control" test, works fine.

I promise that the first file, with the .ans extension, DOES exist in that location.

As an experiment, I pulled in the entire sbbs/exec tree from Git, just to make sure nothing's corrupt. The strange behavior persists.

Wondering now if I should just save some things, blow the whole thing away, and rebuild. This install dates from 2004.

o
(O)

it's something weird with the filename
i have to go to sleep soon but here's what i see.

https://i.imgur.com/Md3jizk.png
https://i.imgur.com/7V38t1W.png
https://i.imgur.com/9qGlqKX.png
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Mon May 16 2022 04:46 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Sun May 15 2022 10:58 pm

Did you experiment with directly executing console.printfile() via the ;eval

Okay... Kind of feeling dumb here, but the menu shell cuts off my input and I don't have enough room to enter the entire eval command... Increasing terminal width doesn't help, either. Suggestions?

o

change the filename length. it's too long.
your menu won't let you type the entire thing in unless you do ;exec THEN type in ?typeasc.js TW2002TW.ANS

i originally thought i had the same problem as you until i saw i typed in tw2022
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Tue May 17 2022 09:31 am

Try copying the file to your "ctrl" directory and run "?typeasc tw2002tw.ans

I just gave that a try. Unchanged behavior:

;exec ?typeasc tw2002tw.ans <- immediate return to menu
;eval console.printfile("tw2002tw.ans") <- displays the file

Thank you for your help :)

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: MRO to Belly on Fri May 13 2022 05:46 pm

it's kinda messy to put it in the xtrn/ dir and not the sub dir of the doorg

maybe you have the path wrong in the cfg

I don't know why TW is putting it there, instead of its subdir. And no, I have the path right. I've done many stupid things, but this isn't one of them.

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: MRO to all on Sat May 14 2022 09:31 am

it's something weird with the filename
i have to go to sleep soon but here's what i see.

https://i.imgur.com/Md3jizk.png

You typoed the filename in the ";exec" test, as seen in your screenshot.
--
digital man (rob)

Breaking Bad quote #21:
You? No. The only shooting you do is into a Kleenex. - Hank Schrader
Norco, CA WX: 72.4øF, 56.0% humidity, 13 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Tue May 17 2022 05:22 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Tue May 17 2022 09:31 am

Try copying the file to your "ctrl" directory and run "?typeasc tw2002tw.ans

I just gave that a try. Unchanged behavior:

;exec ?typeasc tw2002tw.ans <- immediate return to menu
;eval console.printfile("tw2002tw.ans") <- displays the file

I guess the next thing I would do is add a couple log() calls to exec/typeasc.js:

else { // added opening brace
log(format("Calling console.printfile(%s, %s)", f.name, mode));
console.printfile(f.name, mode);
} // added closing brace

And then see what is logged when you try to use typeasc.js to display that file.
--
digital man (rob)

Rush quote #35:
Static on your frequency, electrical storm in your veins
Norco, CA WX: 70.9øF, 58.0% humidity, 12 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to MRO on Tue May 17 2022 05:43 pm

Re: BullsEye path limitations?
By: MRO to Belly on Fri May 13 2022 05:46 pm

it's kinda messy to put it in the xtrn/ dir and not the sub dir of the doorg

maybe you have the path wrong in the cfg

I don't know why TW is putting it there, instead of its subdir. And no, I have the path right. I've done many stupid things, but this isn't one of them.

i had an archiver issue so my msgs got sent out late.
i think it's your filename length.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to MRO on Tue May 17 2022 04:50 pm

Re: BullsEye path limitations?
By: MRO to all on Sat May 14 2022 09:31 am

it's something weird with the filename
i have to go to sleep soon but here's what i see.

https://i.imgur.com/Md3jizk.png

You typoed the filename in the ";exec" test, as seen in your screenshot.

yeah i see. i also keep doing that.

i think he has problems because his filename is so long
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Digital Man to Belly on Tue May 17 2022 05:14 pm

I guess the next thing I would do is add a couple log() calls to exec/typeas

else { // added opening brace
log(format("Calling console.printfile(%s, %s)", f.name, mode));
console.printfile(f.name, mode);
} // added closing brace

And then see what is logged when you try to use typeasc.js to display that f

My brain is hurting.

I added your logging. I did an 'exec ?typeasc.js blah'. I looked in every log I could find. Nothing.

I added another log() just before the for() loop that parses the switches, so I could see if typeasc.js was being called at all. Ran it a few times. Ran bullseye to look at some bulletins. Checked every log I could find. Still nothing.

I think I'm going insane.

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: Belly to Digital Man on Tue May 17 2022 08:40 pm

Re: BullsEye path limitations?
By: Digital Man to Belly on Tue May 17 2022 05:14 pm

I guess the next thing I would do is add a couple log() calls to exec/typeas

else { // added opening brace
log(format("Calling console.printfile(%s, %s)", f.name, mode));
console.printfile(f.name, mode);
} // added closing brace

And then see what is logged when you try to use typeasc.js to display that f

My brain is hurting.

I added your logging. I did an 'exec ?typeasc.js blah'. I looked in every log I could find. Nothing.

It would go to the terminal server log output. In Synchronet Control Panel for windows, that's the "Terminal Server" tab.

I added another log() just before the for() loop that parses the switches, so I could see if typeasc.js was being called at all. Ran it a few times. Ran bullseye to look at some bulletins. Checked every log I could find. Still nothing.

I think I'm going insane.

Maybe you have another coyp of typeasc.js somewhere on your system (e.g. mods directory) and that's being executed instead of exec/typeasc.js.
--
digital man (rob)

Synchronet/BBS Terminology Definition #9:
BPS = Bits Per Second
Norco, CA WX: 66.2øF, 75.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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.

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.


o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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)

I tried ;exec ?typeasc.js ../xtrn/tw2002tw.ans ... nothing. Right back to the menu.

But: ;exec ?typeasc.js ../xtrn/tw2002tw.txt ... my "control" test, works fine.

I promise that the first file, with the .ans extension, DOES exist in that location.

Check file permissions.
ls -l tw2002tw.*

If in doubt, run
chmod 666 tw2002tw.ans
and try again

I've had similar issues before and it came down to the file having the SBBS user ownership, but still being in the root group and read permission not set for the group. 'chgrp SBBS tw2002tw.ans' (with the correct group of course) would fix that if it was your problem.

JD
--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/1.1)

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

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

Yes. console.printfile("tw2002tw.ans",0) still does the trick.

If I get time later to VPN home, I'll try the other suggestions.

Thanks

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: John Dovey to Belly on Fri May 13 2022 11:41 pm

If in doubt, run
chmod 666 tw2002tw.ans
and try again

Thank you, but that probably won't work on Win10 :)

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: BullsEye path limitations?
By: John Dovey to Belly on Fri May 13 2022 11:41 pm

If in doubt, run
chmod 666 tw2002tw.ans
and try again

Thank you, but that probably won't work on Win10 :)

Damn! ;-)

--- AfterShock/Android 1.6.8
* Origin: Firecat Mobile (4:920/1.1)

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

Perhaps the console.aborted flag is set by something before console.printfil

Setting console.aborted to false before calling console.printfile() cause no change, unfortunately.

Perhaps sometime this weekend I can pull down the dev build and see if that makes a difference.

Thanks

o
(O)
BeLLy

---
þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)