So I'm reading the Synchronet Docs and it says "(LOGON2, LOGON3, ... LOGON9 also supported)" I take it that means I can have multiple logon screens. No? So if my first logon screen for an ansi user is logon.ans
the next one would be named logon2.ans ?? and Synchronet would call
the second screen? Is that right? What am I doing wrong?
So I'm reading the Synchronet Docs and it says "(LOGON2, LOGON3, ...LOGON9
also supported)" I take it that means I can have multiple logon screens.No?
So if my first logon screen for an ansi user is logon.ans the next onewould
be named logon2.ans ??
and Synchronet would call the second screen?
Is tha right? What am I doing wrong?
So I'm reading the Synchronet Docs and it says "(LOGON2, LOGON3, ...It'll actually display logon1.* as well (if you have it).
LOGON9 also supported)" I take it that means I can have multiple logon
screens. No? So if my first logon screen for an ansi user is logon.ans
the next one would be named logon2.ans ??
and Synchronet would call the second screen?
Display it (send it to the remote terminal), yes.
Is tha right? What am I doing wrong?
So I'm reading the Synchronet Docs and it says "(LOGON2, LOGON3, ...It'll actually display logon1.* as well (if you have it).
LOGON9 also supported)" I take it that means I can have multiple logon
screens. No? So if my first logon screen for an ansi user is logon.ans
the next one would be named logon2.ans ??
and Synchronet would call the second screen?
Display it (send it to the remote terminal), yes.
I have logon.ans and logon1.ans in /sbbs/text/menu logon.ans displays but logon1.ans does not display.Is tha right? What am I doing wrong?
So I'm reading the Synchronet Docs and it says "(LOGON2, LOGON3, ... LOGON9 also supported)" I take it that means I can have multiple logon screens. No? So if my first logon screen for an ansi user is logon.ansthe
next one would be named logon2.ans ?? and Synchronet would call thesecond
screen? Is that right? What am I doing wrong?
Re: Logon Screens
By: Digital Man to HusTler on Sun Jun 02 2019 07:05 pm
So I'm reading the Synchronet Docs and it says "(LOGON2, LOGON3, ...It'll actually display logon1.* as well (if you have it).
LOGON9 also supported)" I take it that means I can have multiple logon
screens. No? So if my first logon screen for an ansi user is logon.ans
the next one would be named logon2.ans ??
and Synchronet would call the second screen?
Display it (send it to the remote terminal), yes.
I have logon.ans and logon1.ans in /sbbs/text/menu logon.ans displays but logon1.ans does not display.Is tha right? What am I doing wrong?
The logon screens require user access?
So I have to edit logon.js also?
forI have logon.ans and logon1.ans in /sbbs/text/menu logon.ans displaysIs tha right? What am I doing wrong?
but logon1.ans does not display.
The logon screens require user access?
I'm not really sure what you're asking. The logon screens are displayed during *logon* (after a user is authenticated and granted *access* to the BBS).
So I have to edit logon.js also?
No, not normally.
Do you have logon1.asc file as well? A .msg or .asc file is *required*
every set of menu files you want to display.
Do you have logon1.asc file as well? A .msg or .asc file is *required*for
every set of menu files you want to display.
digital man
Do you have logon1.asc file as well? A .msg or .asc file is
*required* for every set of menu files you want to display.
Oh..No.. I don't. I figured if my term is ansi I would just need logon1.ans. I'll try adding logon1.asc
Oh..No.. I don't. I figured if my term is ansi I would just need
logon1.ans. I'll try adding logon1.asc
might be better to go with *.msg format since it can contain color codes which will be transmitted or not as the remote end needs...
Re: Logon Screens
By: Digital Man to HusTler on Mon Jun 03 2019 01:04 am
Do you have logon1.asc file as well? A .msg or .asc file is *required* for every set of menu files you want to display.
digital man
Thank you sir. This resolved the problem.
Oh..No.. I don't. I figured if my term is ansi I would just need
logon1.ans. I'll try adding logon1.asc
might be better to go with *.msg format since it can contain color
codes which will be transmitted or not as the remote end needs...
Same with .asc.. .asc files can contain Synchronet color codes, which will be converted to ANSI or left out, depending on the user's
terminal capabilities.
On 2019 Jun 03 09:17:38, you wrote to me:
Oh..No.. I don't. I figured if my term is ansi I would just need
logon1.ans. I'll try adding logon1.asc
might be better to go with *.msg format since it can contain color
codes which will be transmitted or not as the remote end needs...
Same with .asc.. .asc files can contain Synchronet color codes, which will be converted to ANSI or left out, depending on the user's
terminal capabilities.
interesting... wonder what msg brings to the table? i guess i need to do some more reading...
willOh..No.. I don't. I figured if my term is ansi I would just need
logon1.ans. I'll try adding logon1.asc
might be better to go with *.msg format since it can contain color
codes which will be transmitted or not as the remote end needs...
Same with .asc.. .asc files can contain Synchronet color codes, which
be converted to ANSI or left out, depending on the user's terminal
I've been meaning to ask about that. I get the ans2asc and asc2ans and have been using them. What is a msg file? Why no ans2msg or asc2msg? Is this another syncronet creation?
Re: Logon Screensterminal
By: Nightfox to mark lewis on Mon Jun 03 2019 09:17 am
Oh..No.. I don't. I figured if my term is ansi I would just need
logon1.ans. I'll try adding logon1.asc
might be better to go with *.msg format since it can contain color
codes which will be transmitted or not as the remote end needs...
Same with .asc.. .asc files can contain Synchronet color codes, which will be converted to ANSI or left out, depending on the user's
I've been meaning to ask about that. I get the ans2asc and asc2ans andhave
been using them. What is a msg file? Why no ans2msg or asc2msg? Is this another syncronet creation?
Re: Logon ScreensIs
By: HusTler to Nightfox on Mon Jun 03 2019 07:39 pm
I've been meaning to ask about that. I get the ans2asc and asc2ans and have been using them. What is a msg file? Why no ans2msg or asc2msg?
suitedthis another syncronet creation?
I read the wiki and still don't "get it".
.asc ASCII characters (CP437 characters, optionally)
.msg ASCII/CP437 characters 1)
.seq PETSCII characters and control-sequences
.ans ASCII/CP437 characters and ANSI X3.64 Terminal control-sequences
.mon ASCII/CP437 characters and ANSI X3.64 Terminal control-sequences
for monochrome displays
.rip ASCII/CP437 characters and RIPscrip Terminal control-sequences
Same with .asc.. .asc files can contain Synchronet color codes,
which will be converted to ANSI or left out, depending on the
user's terminal
I've been meaning to ask about that. I get the ans2asc and asc2ans and have been using them. What is a msg file? Why no ans2msg or asc2msg? Is this another syncronet creation?
I've been meaning to ask about that. I get the ans2asc and asc2ans
and have been using them. What is a msg file? Why no ans2msg or
asc2msg? Is this another syncronet creation?
I read the wiki and still don't "get it".
.asc ASCII characters (CP437 characters, optionally)
.msg ASCII/CP437 characters 1)
.seq PETSCII characters and control-sequences
.ans ASCII/CP437 characters and ANSI X3.64 Terminal control-sequences
.mon ASCII/CP437 characters and ANSI X3.64 Terminal control-sequences suited for monochrome displays
.rip ASCII/CP437 characters and RIPscrip Terminal control-sequences
The ans2asc utility *used* to be called ans2msg. The .msg files are the identical format to .asc but may be displayed in place of .asc if they both exist, depending on the user's terminal capabilities.
I've been meaning to ask about that. I get the ans2asc and asc2ansand have een using them. What is a msg file? Why no ans2msg or
The ans2asc utility *used* to be called ans2msg. The .msg files are the identical format to .asc but may be displayed in place of .asc if they both exist, depending on the user's terminal capabilities.
Re: Logon Screens
By: HusTler to all on Mon Jun 03 2019 08:08 pm
I've been meaning to ask about that. I get the ans2asc and asc2ans
and have been using them. What is a msg file? Why no ans2msg or
asc2msg? Is this another syncronet creation?
I read the wiki and still don't "get it".
.asc ASCII characters (CP437 characters, optionally)
.msg ASCII/CP437 characters 1)
.seq PETSCII characters and control-sequences
.ans ASCII/CP437 characters and ANSI X3.64 Terminal control-sequences .mon ASCII/CP437 characters and ANSI X3.64 Terminal control-sequences suited for monochrome displays
.rip ASCII/CP437 characters and RIPscrip Terminal control-sequences
What specifically do you not get? Do you have any specific questions? Personally I'm still a little confused about how .msg and .asc are supposed to be different. It sounds like they both can contain ASCII and CP437 characters, and I know they both can contain Synchronet color/attribute codes that will be displayed only if the user has a compatible (ANSI) terminal. I'm not sure why I'd choose .msg over .asc and vice-versa.
Re: Logon Screensthe
By: Digital Man to HusTler on Mon Jun 03 2019 10:06 pm
The ans2asc utility *used* to be called ans2msg. The .msg files are
identical format to .asc but may be displayed in place of .asc if they both exist, depending on the user's terminal capabilities.
My understanding is that .asc and .msg files can both contain Synchronet color/attribute codes, is that correct? I'm not sure why I'd choose .msg over .asc or vice-versa when creating a menu file.
selectionSame with .asc.. .asc files can contain Synchronet color codes,
which will be converted to ANSI or left out, depending on the
user's terminal
My understanding is that .asc and .msg files are pretty much the same format, so an ans2msg and msg2ans really isn't needed. If you want to characters optionally, and .msg files contain ASCII/CP437 characters. I'm not really clear on how .asc and .msg files are supposed to be different, but there's a table on that page explaining the priority of file
I've never understood why someone would call a BBS in a terminal that doesn't support ansi. It's the ansi colors that makes BBSes sointeresting
to me. My first monitor was monochrome but once I got a color monitor I never wanted to see plain text ever again. In todays environment I really can't understand it. ASC and ANS is all I need and I don't even test the
Re: Logon Screens
By: Nightfox to HusTler on Tue Jun 04 2019 09:17 am
Same with .asc.. .asc files can contain Synchronet color codes,
which will be converted to ANSI or left out, depending on the
user's terminal
My understanding is that .asc and .msg files are pretty much the same format, so an ans2msg and msg2ans really isn't needed. If you want to characters optionally, and .msg files contain ASCII/CP437 characters. I'm not really clear on how .asc and .msg files are supposed to be different, but there's a table on that page explaining the priority of file selection
I've never understood why someone would call a BBS in a terminal that doesn't support ansi.
Yeah, in all the time I've been using BBSes (since 1992), I've always used N>ANSI. My first monitor was a Hercules monochrome, but I was still able to us
software that supported ANSI. I just couldn't see the color until I upgraded N>VGA months later.
On 06-06-19 08:56, Daryl Stout wrote to NIGHTFOX <=-s
Yeah, in all the time I've been using BBSes (since 1992), I've always used
ANSI. My first monitor was a Hercules monochrome, but I was still able to
software that supported ANSI. I just couldn't see the color until I upgraded
VGA months later.
Similar to me...although I was dialing into local BBS's in the mid 1980's, and was also on CompuServe.
Yes, my first setup was a Hercules card and monochrome monitor. Then I switched to CGA with a green screen. Was a bit longer, because I couldsee
anything more than "greyscale" for ANSI colours.
On 06-09-19 22:00, Nightfox wrote to Tony Langdon <=-
I don't think I've seen CGA with a green screen. I know CGA supported several colors.. Did they have CGA monitors that only displayed shades
of green? I know they made similar VGA monitors that only displayed in greyscale, as a form of cost savings..
Yes, my first setup was a Hercules card and monochrome monitor. Then
I switched to CGA with a green screen. Was a bit longer, because I
could see anything more than "greyscale" for ANSI colours.
I don't think I've seen CGA with a green screen. I know CGA supported several colors.. Did they have CGA monitors that only displayed
shades of green?
I don't think I've seen CGA with a green screen. I know CGA supported several
colors.. Did they have CGA monitors that only displayed shades of green? I >know they made similar VGA monitors that only displayed in greyscale, as a form
of cost savings..
On 06-10-19 19:00, Mike Powell wrote to NIGHTFOX <=-everal
I don't think I've seen CGA with a green screen. I know CGA supported
colors.. Did they have CGA monitors that only displayed shades of green? I
know they made similar VGA monitors that only displayed in greyscale, as a
form
of cost savings..
I had one that had a switch on it that could display in amber or green, depending on where you set the switch.
I just want to make sure I understand this .... If I want to add screens as a user logs in... its logon1.asc...logon10.asc ... BUT if I have on for the a security level I do logon??.asc where ??= the security level??
I just want to make sure I understand this .... If I want to add screens as a user logs in... its logon1.asc...logon10.asc ... BUT if I have on for the a security level I do logon??.asc where ??= the security level??
I just want to make sure I understand this .... If I want to add screens as a user logs in... its logon1.asc...logon10.asc ... BUT if I have on for the a security level I do logon??.asc where ??= the security level??
Did you not read this before you posted it..
what file name do I use to have multiple logom screens come up during the logon process... and what do I name one of these files if I want a certain security level to see one...
Re: Logon Screens
You got it right. logon.*, logon1.*, logon2.* for 3 logon messages for everyone and then logon10.* for a message displayed only to users of level 10 or higher. You can follow the logic in exec/logon.js.
Re: Logon Screens
By: Digital Man to Ib Joe on Fri Apr 16 2021 11:28 am
Re: Logon Screens
You got it right. logon.*, logon1.*, logon2.* for 3 logon messages for everyone and then logon10.* for a message displayed only to users of level 10 or higher. You can follow the logic in exec/logon.js.
I get it.... 1-9 regulogon stuff... whereas 10-?? will be for security levels..
Re: Logon Screens
By: Ib Joe to Digital Man on Fri Apr 16 2021 01:56 pm
Not necessarily. If you want to specify logon message for levels 5+ you could use logon5.*, but you then you couldn't have consecutive logon,1,2,3,4.* screens. You need a "gap" somewhere between your successive logon screens and your level-specific ones.
Re: Logon Screens
By: Digital Man to Ib Joe on Fri Apr 16 2021 04:45 pm
Re: Logon Screens
By: Ib Joe to Digital Man on Fri Apr 16 2021 01:56 pm
Not necessarily. If you want to specify logon message for levels 5+ you could use logon5.*, but you then you couldn't have consecutive logon,1,2,3,4.* screens. You need a "gap" somewhere between your successive logon screens and your level-specific ones.
So, then logon,1,2,3,4 for my consecutive logon screens.... followed by logon55.* for my special security level logon screen... the gap between logon4.* and logon55.*
Correct??
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (2 / 14) |
Uptime: | 88:06:38 |
Calls: | 6,496 |
Calls today: | 7 |
Files: | 12,100 |
Messages: | 5,277,265 |