Hiya Rob...
Updated all the new dev files and ctrl/fonts files from sbbs_run this morning. Ran JSEXEC update.js and I'm now getting the following errors in my Terminal Server window
2/2 11:11:52a Node 1 Bill McGarrity running external program: MegaSlots
2/2 11:12:45a Node 1 Failed to activate font: 0
Should I be worried?
Digital Man wrote to Bill McGarrity on 02-02-18 13:25 <=-
Re: Font Errors
By: Bill McGarrity to Digital Man on Fri Feb 02 2018 11:25 am
Hiya Rob...
Updated all the new dev files and ctrl/fonts files from sbbs_run this morning. Ran JSEXEC update.js and I'm now getting the following errors in my Terminal Server window
2/2 11:11:52a Node 1 Bill McGarrity running external program: MegaSlots
2/2 11:12:45a Node 1 Failed to activate font: 0
Should I be worried?
No, it just indicates you're running a now-unsupported build of
SyncTERM (not 1.0 and not a current 1.1b build) - so update or
downgrade SyncTERM and you should not see those errors. I hope. :-)
Digital Man wrote to Bill McGarrity on 02-02-18 13:25 <=-
Re: Font Errors
By: Bill McGarrity to Digital Man on Fri Feb 02 2018 11:25 am
Hiya Rob...
Updated all the new dev files and ctrl/fonts files from sbbs_run this morning. Ran JSEXEC update.js and I'm now getting the following errors in my Terminal Server window
2/2 11:11:52a Node 1 Bill McGarrity running external program: MegaSlots
2/2 11:12:45a Node 1 Failed to activate font: 0
Should I be worried?
No, it just indicates you're running a now-unsupported build of SyncTERM (not 1.0 and not a current 1.1b build) - so update or downgrade SyncTERM and you should not see those errors. I hope. :-)
OK. I'm not using SyncTerm to access the board. Thanks...
Is there anyway you can check to see if the term program isn't SyncTerm and bypass it all?
Digital Man wrote to Bill McGarrity on 02-03-18 02:27 <=-
No, it just indicates you're running a now-unsupported build of SyncTERM (not 1.0 and not a current 1.1b build) - so update or downgrade SyncTERM and you should not see those errors. I hope. :-)
OK. I'm not using SyncTerm to access the board. Thanks...
Is there anyway you can check to see if the term program isn't SyncTerm and bypass it all?
Yeah, it's supposed to be already be doing that. What terminal program
are you using?
Digital Man wrote to Bill McGarrity on 02-03-18 02:27 <=-
No, it just indicates you're running a now-unsupported build of SyncTERM (not 1.0 and not a current 1.1b build) - so update or downgrade SyncTERM and you should not see those errors. I hope. :-)
OK. I'm not using SyncTerm to access the board. Thanks...
Is there anyway you can check to see if the term program isn't SyncTerm and bypass it all?
Yeah, it's supposed to be already be doing that. What terminal program are you using?
An old one... Procomm +
Digital Man wrote to Bill McGarrity on 02-03-18 19:24 <=-
Re: Font Errors
By: Bill McGarrity to Digital Man on Sat Feb 03 2018 05:59 pm
Digital Man wrote to Bill McGarrity on 02-03-18 02:27 <=-
No, it just indicates you're running a now-unsupported build of SyncTERM (not 1.0 and not a current 1.1b build) - so update or downgrade SyncTERM and you should not see those errors. I hope. :-)
OK. I'm not using SyncTerm to access the board. Thanks...
Is there anyway you can check to see if the term program isn't SyncTerm and bypass it all?
Yeah, it's supposed to be already be doing that. What terminal program are you using?
An old one... Procomm +
Well then it certainly shouldn't be trying to load any fonts. :-(
I'll look into and likely commit a fix soon.
An old one... Procomm +
Well then it certainly shouldn't be trying to load any fonts. :-(
I'll look into and likely commit a fix soon.
An old one... Procomm +
Well then it certainly shouldn't be trying to load any fonts. :-(
I'll look into and likely commit a fix soon.
Just updated... it's fixed...
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 216:35:55 |
Calls: | 14,143 |
Calls today: | 1 |
Files: | 295 |
Messages: | 551,128 |