I put together a little tool to allow non-Synchronet BBS systems to send custom fonts to SyncTERM. You run it right at connect to load a handful
of fonts from a config file, and then you can switch to them with ANSI escape codes (for example to load the LORE game font before running LORE, or if you wanted to make a newspaper font for your daily news or something I duno..).
I threw it up on another.tel and bbs.anduin.net filename stfn-02b.zip or via http @ https://kirin.dcclost.com/~alex/stfn-02b.zip
Let me know how it goes :)
https://kirin.dcclost.com/~alex/stfn-03b.zip for the updated version..
https://kirin.dcclost.com/~alex/stfn-03b.zip for the updated version..
I haven't gotten it working, it returns errorlevel 1 each time it's run and doesn't seem to send anything to the com port.
Is the FOSSIL port # 0-based or 1-based?
The .CFG file has 3 fonts listed but only one font file is in the directory. I commented out the 2 fonts that I don't have files for, but
it doesn't seem to have made a difference.
Are the font #s in SyncTerm 0-based or 1-based? When I look through the font list in SyncTerm I count 43. Should the first font listed in the .CFG file be 43 or 44?
When I run "ST16 1" (or "ST16 0") it doesn't output anything on the console. Just errorlevel 1.
sigh.. updated again :) i should perhaps be a little
nicer about game devs that ship buggy games.. then again
we don't get paid for bbs stuff ;) https://kirin.dcclost.com/~alex/stfn-04b.zip
sorry, yeah it's just an example. either the link in the
config file, or the windows syncterm package should
include a bunch more fonts. wasn't really sure about
just nicking the whole set.
Seems to have the same behaviour on my system. Nothing output, returns errorlevel 1.
The fonts included in the Syncterm package will already be available in Syncterm, I assume? So they're just for illustrative purposes (but wouldn't actually provide an additional font)?
I assume only .F16 fonts (4KB filesize) are supported?
Is there documentation on the font support in SyncTerm? I didn't search too hard but didn't find anything describing the escape sequences used other than the brief description in STFN.DOC.
BTW the file endings on the doc and cfg are unix-style, so they don't display quite right in DOS.
Seems to have the same behaviour on my system.
Nothing output, returns errorlevel 1.
made a little video for how i run it. not really sure
why it's misbehaving now..
Now, when I run it, in Syncterm I see:
ST-FONT v0.4b (c) 2024 Alexander Grotewohl (fusion)
Terminal type is... NOT SyncTERM. Bailing.
Now, when I run it, in Syncterm I see:
ST-FONT v0.4b (c) 2024 Alexander Grotewohl (fusion)
Terminal type is... NOT SyncTERM. Bailing.
Looking at the serial log, after "ESC[c" is sent by ST16, Syncterm responds "ESC[=67;84;101;114;109;1;31c".
However, once "ESC[=67;84;" has been received, ST16 immediately responds that the terminal is NOT Sycnterm.
okie dokie, https://kirin.dcclost.com/~alex/stfn-05b.zip
hopefully that's the last one hehe
Sysop: | tracker1 |
---|---|
Location: | Phoenix, AZ |
Users: | 54 |
Nodes: | 25 (0 / 25) |
Uptime: | 174:22:29 |
Calls: | 367 |
Files: | 1,364 |
Messages: | 36,299 |