BP> This is returning '0' to the log file when logging in from the command
BP> line. I wonder if possibly adding a servertype for local login might be
BP> simpler than doing the 'local' boolean. Perhaps adding servertype of 3
BP> for local.

I don't know what OS or version you're using but it seems to be working from
here I just tested it in Windows A48 and Linux. The simple test I did was
logged in and tried to download the BBS list and on both OSes it says "Local
mode:" and asked me to save.

Are you sure you're logging in with -L? Make sure you're not setting the value
of Local anywhere in any MPL anywhere, otherwise that will change it for the
entire connection.

The ServerType that is used internally by Mystic for terminal services does
have a Local mode value. They should be (as of A48 current releases):

0=telnet,1=rlogin,2=ssh,3=modem,4=local,5=other

5 is left open broadly so (for example) someone could use that as a packet
radio type if they wanted to and configure server type 5 to show up as "RADIO"
in the callers list (or whatever else they want).

.... No honey, I can't eat with the family. My computer gets lonely!

Hello g00r00!

Just a quick question. When trying to use the 'local' function in MPL, it
doesn't seem to ever return true. I'm actually logging into Mystic from the
command line, './mystic -l' and that function returns false.

Here is a snippet of how I'm trying to use it:

If Local Then SysopLog('Local Caller')
Else SysopLog(Int2Str(Callers.RServerType));

This is returning '0' to the log file when logging in from the command line. I
wonder if possibly adding a servertype for local login might be simpler than
doing the 'local' boolean. Perhaps adding servertype of 3 for local.

Has something changed with it, that hasn't made it's way into my documentation
yet? ;)

Thank you,

Black Panther

.... When I'm good, I'm great--when I'm bad, you're breathless

Hello g00r00!

05 Apr 22 13:00, you wrote to me:

BP>> This is returning '0' to the log file when logging in from the
BP>> command line. I wonder if possibly adding a servertype for local
BP>> login might be simpler than doing the 'local' boolean. Perhaps
BP>> adding servertype of 3 for local.

gr> I don't know what OS or version you're using but it seems to be
gr> working from here I just tested it in Windows A48 and Linux. The
gr> simple test I did was logged in and tried to download the BBS list and
gr> on both OSes it says "Local mode:" and asked me to save.

My test system is running Manjaro Linux 64-bit, with Kernel 5.15.28-1-MANJARO
x86_64.

Let me run a test using the bbs listing as see if that is any different.

gr> Are you sure you're logging in with -L? Make sure you're not setting
gr> the value of Local anywhere in any MPL anywhere, otherwise that will
gr> change it for the entire connection.

Yes, logging in either is -L or running the mpl from a command prompt with the
'./mystic -Uuser_Name -Ppassword -X'basicmpl test' format. Neither one will
show the local as being true. Also, the variable is not being changed anywhere
else in the code.

gr> The ServerType that is used internally by Mystic for terminal services
gr> does have a Local mode value. They should be (as of A48 current
gr> releases):

gr> 0=telnet,1=rlogin,2=ssh,3=modem,4=local,5=other

Ooooo. Didn't know about the others on here. So, when it's a local connection
the servertype should also be showing as 4. Looks like I have some more playing
to do. :)

Thank you,

Black Panther

.... C:\DOS;C:\WIN;C:\WIN\SCREW\UP;C:\ME\DEL\WIN;C:\ME\RUN\OS2

BP> Yes, logging in either is -L or running the mpl from a command prompt
BP> with the './mystic -Uuser_Name -Ppassword -X'basicmpl test' format.
BP> Neither one will show the local as being true. Also, the variable is not
BP> being changed anywhere else in the code.

The second one is not a local login because you're not telling it its a local
login with that command line. There is no -L

sudo ./mystic -l -ug00r00 -pMyPassword "-xbbslist bbslist"

Tested this again in Linux since I know thats what you're using with A48 and it
works for me. If I include -l it says local mode, if I don't it doesn't.

BP> Ooooo. Didn't know about the others on here. So, when it's a local
BP> connection the servertype should also be showing as 4. Looks like I have
BP> some more playing to do. :)

Probably depends on the version you're using but yes I think so.

.... No one knows what's next, but everybody does it.

Hello g00r00!

06 Apr 22 12:08, you wrote to me:

BP>> Yes, logging in either is -L or running the mpl from a command
BP>> prompt with the './mystic -Uuser_Name -Ppassword -X'basicmpl
BP>> test' format. Neither one will show the local as being true.
BP>> Also, the variable is not being changed anywhere else in the
BP>> code.

gr> The second one is not a local login because you're not telling it its
gr> a local login with that command line. There is no -L

That was a error when typing it into the message... I do use the -L in the
command to run from the command line. They say the mind is the second thing to
go... I'll be damned if I remember what the first was... ;)

I just upgraded to a48, at least for my test system here, and it seems to be
working now. It was strange that it wasn't in a47.

I threw together a quick little mpl to test it, as I've modified my
bbslist.mps. :)

Begin
ClrScr;
WriteLn('|CR');
If Local Then WriteLn('Local Login');
Else WriteLn('Remote Login');
End.

Now it shows 'Local Login'.

gr> sudo ./mystic -l -ug00r00 -pMyPassword "-xbbslist bbslist"

You use the same password that I do!! ;) BTW, I don't run Mystic with sudo.

BP>> Ooooo. Didn't know about the others on here. So, when it's a
BP>> local connection the servertype should also be showing as 4.
BP>> Looks like I have some more playing to do. :)

gr> Probably depends on the version you're using but yes I think so.

I've edited some code here, but haven't tested it to see if it does. I'll let
you know. :)

Thank you,

Black Panther

.... Sometimes I think line noise is deliberate.

BP> I just upgraded to a48, at least for my test system here, and it seems
BP> to be working now. It was strange that it wasn't in a47.

Could very well be broken in A47. I think I did change some stuff surrounding
the server types between A46 and A47 which could have broke it.

Now you'll have access to MysticScript also :)

.... There are three kinds of people: Those who can count, and those who can't