Sorry - you are actually CORRECT, too. *I* did have a problem; and on of my sysOp friends told me today that he has the exact one, so...

No worries, mate! I noticed today that I still may not have fixed my problem with SyncTerm. I am going to have to check and see if its been overwritten, or if I've encountered something else.

Thats one thing I always struggle with. 2o is setup to BEST work with SyncTerm... when testing things with the BBS its best to test both Sync and Netrunner... and heck, even more - but for mine.... its just NR & Sync. I'm to heavy ANSI for anything less. :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

When and were did the new version come out? My py script quit grabbi

Yeah ... I shouldn't have said "new"... its the v2 script from mid-2020. Cool script/idea in any case.
Strange the yours quit working. Did you change python versions by
chance? Are you able to exec the script locally and get the file using
the same paths used in your cron/events entry?

So I switched from Windows to Linux on a Raspberry Pi4. Ever since, the python script does not work. It doesn't API the ansi file. Matter of fact a lot of my RSS feeds don't work as frequently either: fox, cnn, nfl, etc. etc.

I've triple checked the py script for proper directories. It executes from CLI just not from mystic. Mystic is pointing to where the file should be but it's never there when executed through mystic. So to be honest I haven't spent much time focused on it, so I may have a directory wrong, but I am having issues with any new pre alpha beyond 5.3.21 with MIS freezing when attempting to poll ... so not sure if it's MY Pi Setup or changes within Mystic causing issues. Everything worked fine up until I think it was the 5.14 release, so I rolled back to 5.3 and have been stuck here ever since.

Random thoughts provide by...

-tG

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)

Thats one thing I always struggle with. 2o is setup to BEST work with SyncTerm... when testing things with the BBS its best to test both Sync and Netrunner... and heck, even more - but for mine.... its just NR & Sync. I'm to heavy ANSI for anything less. :P

Eh, Syncterm sucks. Kidding Brother lol! (Inside joke)

So to add to Paulie's point which I 100% agree with .. You also want to either suggest peeps turn off their status bar and/or def test with syncterms status bar on while setting up mod or ansi line lengths. I suggest the "forget about the status bar approach," it's not needed and those using it are just causing you to reduce your ansi's to 22-23 lines .. which for netrunner users looks like a lot of black space below the ansi prior to the pause at line 25. I quit worrying about status bars and suggest everyone just turn it off. I mean ... maybe theres a purpose for the status bar in 2021? I dunno.

-tG

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165)