FiSH <span dir="ltr">K6FSH</span> wrote:<br>
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'lucida console',sans-serif">
<div></div>
<div>Look in config.h for <span style="FONT-FAMILY: times,serif">MBX_AREA_PROMPT and MBX_MORE_PROMPT. They should be DEFINEd by default for the "old" behavior. To get the behavior that you want, they both should be UNDEFINEd after or instead of the DEFINE. And this only applies to JNOS 2.0i and later versions.</span></div>
</div></div></blockquote>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div>
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'lucida console',sans-serif">
<div>Undefining <span style="FONT-FAMILY: times,serif">MBX_AREA_PROMPT and MBX_MORE_PROMPT has no effect on users (calls) that are already known to jnos (they have an entry in users.dat). But when a NEW user connects, jnos should automatically create that new user with the desired preferences, including the one that turns off "</span><span style="FONT-FAMILY: 'times new roman','new york',times,serif">The alphabet-soup prompt".</span></div>
</div></div></blockquote>
<div><br>Hi FiSH,<br><br>It took until this morning for me to get back to playing with this, and I wanted to report my findings -- you might find them interesting.</div>
<div><br>I rebuilt JNOS with of the following preprocessor directives set as shown -- each with a sense opposite to the sense they had in the stock config.h file:</div>
<div><font face="courier new,monospace">-----------<br>#define MBX_TAC_CALLCHECK<br>#undef MBX_AREA_PROMPT<br>#undef MBX_MORE_PROMPT <br>----------</font><font face="courier new,monospace"><br></font></div>
<div>On the intial Outpost connect from a tactical callsign that has an entry in ftpusers ("25A25" in this case), but no entry in users.dat, I see the following:</div>
<div><font face="courier new,monospace">----------</font></div>
<div><font face="courier new,monospace">[JNOS-2.0i-B2FHIM$]<br>You have 0 messages.<br>Current msg# 0.<br>?,A,B,C,CONV,D,E,F,H,I,IH,IP,J,K,L,M,N,NR,O,P,PI,R,S,T,U,V,W,X,Z ></font></div>
<div><font face="courier new,monospace">LM<br>No messages<br>Current msg# 0.<br>?,A,B,C,CONV,D,E,F,H,I,IH,IP,J,K,L,M,N,NR,O,P,PI,R,S,T,U,V,W,X,Z ></font></div>
<div><font face="courier new,monospace">----------</font></div>
<div>and the interaction wedges because, although the area prompt (and presumably the more prompt) are off, the "alphabet soup prompt" is still in force. According to the Outpost page on JNOS: 'The JNOS BBS prompt picks up the last message ID that was read as part of the prompt. Outpost will use the "<font face="Courier New" size="2">) ></font><font face="Arial" size="2">" prompt sequence as the JNOS prompt.'</font></div>
<div> </div>
<div>After this incomplete interaction, the automagically-created entry for 25A25 in users.dat looks like:</div>
<div><font face="courier new,monospace">----------</font></div><font face="courier new,monospace">25a25 0 M0 A P CA</font>
<div><font face="courier new,monospace">----------</font></div>
<div><font face="arial,helvetica,sans-serif">The "0" in the timestamp field looks a little suspicious, but I'm guessing it's the result of the interaction not actually going to completion. I believe I aborted it from the Outpost Packet Session Manager.</font></div>
<div> </div>
<div>"Okay, fine," (I sez to myself) "so every Tactical Callsign needs to sign on once manually to set expert mode. Not a huge deal." </div>
<div> </div>
<div>(Actually over the longer term it *could* be a somewhat big deal, depending on how many tactical calls we end up with, but I can get into the code and figure out what needs to be done. For now, I can live with it.)</div>
<div> </div>
<div>So I go ahead and log in manually to set expert mode for 25A25:</div>
<div><font face="courier new,monospace">----------</font></div>
<div><font face="courier new,monospace">[JNOS-2.0i-B2FHIM$]<br>You have 0 messages.<br>Area: 25a25 Current msg# 0.<br>?,A,B,C,CONV,D,E,F,H,I,IH,IP,J,K,L,M,N,NR,O,P,PI,R,S,T,U,V,W,X,Z ></font></div>
<div><font face="courier new,monospace">x</font></div>
<div><font face="courier new,monospace">Area: 25a25 (#0) ></font></div>
<div><font face="courier new,monospace">lm</font></div>
<div><font face="courier new,monospace">No messages<br>Area: 25a25 (#0) ></font></div>
<div><font face="courier new,monospace">b</font></div>
<div><font face="courier new,monospace">Thank you 25a25, for calling n6orc JNOS.</font></div>
<div><font face="courier new,monospace">----------</font></div>
<div>"Huh? So why is the Area prompt back on now? Oh... I guess it must be that 'A' in the users.dat record..." </div>
<div> </div>
<div>Now the users.dat entry for 25A25 looks like:</div>
<div><font face="courier new,monospace">----------</font></div>
<div><font face="courier new,monospace">25a25 1302968588 M0 A X P -n -h -e CA</font></div>
<div><font face="courier new,monospace">----------</font></div>
<div>I'm guessing that that "M0" is the setting for the "More prompt," and is the result of #undef-ing MBX_MORE_PROMPT, which is the compiled-in setting equivalent to having manually issued the BBS command "XM 0" ... (Right?)</div>
<div> </div>
<div>(Maybe you see now why I was wishing for some definitive documentation on the content/layout of users.dat records... :-)</div>
<div> </div>
<div>Anyway, the good news is that, even with the Area prompt on, as long as the Alphabet Soup prompt is off, Outpost is happy. So that's it for now, we're off to integration testing this afternoon!</div>
<div> </div>
<div>73, Michael KI6TYV</div></div>