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
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.
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)
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.
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!
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
What is the filename? If it's a *nix system, the file system will be case-se
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
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.
BullsEye just calls typeasc.js to display ASCII and ANSI. And typeasc.js jus
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.
Did you experiment with directly executing console.printfile() via the ;eval
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:
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... perh
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.
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.
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)
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
Try copying the file to your "ctrl" directory and run "?typeasc tw2002tw.ans
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
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
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
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.
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.
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
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.
It would go to the terminal server log output. In Synchronet Control Panel f
Maybe you have another coyp of typeasc.js somewhere on your system (e.g. mod
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.
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.
What if you include the ",0" argument? Does it still display then?
If in doubt, run
chmod 666 tw2002tw.ans
and try again
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 :)
Perhaps the console.aborted flag is set by something before console.printfil
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 606 |
Nodes: | 10 (0 / 10) |
Uptime: | 130:28:17 |
Calls: | 9,607 |
Calls today: | 2 |
Files: | 16,058 |
Messages: | 1,061,924 |
Posted today: | 7 |