I updated the prealphas with some minor changes/fixes today.
www.mysticbbs.com/downloads/prealpha
I've updated the pre-alphas tonight after removing the old Python 2
engine and replacing it with the new one. I've also added a couple
I've updated the pre-alphas tonight after removing the old Python 2
engine and replacing it with the new one. I've also added a couple
other goodies too. Could use some tests with this build to make sure Python 2.7 is working well. Also new is the Pi version was compiled on
my Intel Linux machine and I could use some people to test it. This
means Pi versions will be compiled just as often as Windows and Linux moving forward, no more delays ever - assuming this experiment is successful! :)
Also new is the Pi version was compiled on my Intel Linux machine and I g0> could use some people to test it. This means Pi versions will be g0> compiled just as often as Windows and Linux moving forward, no more g0> delays ever - assuming this experiment is successful! :)
I assumed mys112a47_p32.zip was the new Pi build and I assumed correctly.
Can we also assume a 64 bit build for the Pi is on the horizon?
Just did the usual "./install replace /home/pi/mystic" and everything seems hunky-dory so far.
Awesome thanks for testing and let me know if you run into any issues!
Awesome thanks for testing and let me know if you run into any issues
One cool thing I've noticed is one of the mods I'm running for InterBBS One-Liners used to show a something like "api version mismatch" when it ran, and I haven't seen that with this build yet. :)
I've updated the pre-alphas tonight after removing the old Python 2
engine and replacing it with the new one. I've also added a couple
other goodies too. Could use some tests with this build to make sure Python 2.7 is working well. Also new is the Pi version was compiled on
my Intel Linux machine and I could use some people to test it. This
means Pi versions will be compiled just as often as Windows and Linux moving forward, no more delays ever - assuming this experiment is successful! :)
g00r00,
All went well with the RPI upgrade to the 1.24.21 prealpha; I don't know as of yet if it corrected the binkd connection issue; however a couple of
2. My SSH connection won't establish a connect now, just telnet. Any suggestions on the fix?
11:06:17 SSH > Connect on slot 1/5
11:06:17 SSH 1-HostName
11:06:17 SSH 1-Negotiating SSH session
11:06:17 SSH Unable to set key (-3 )
I tried dropping in the new headers from the beta version of Cryptlib
and maybe that is breaking things. I'll put the old ones back and try
to get some tests done tonight to make sure the latest non-beta release works. I'll put up a new build tonight if I make any changes.
I suspect Cryptlib might be trying to remove the CBC ciphers in the new version and maybe that is messing with things.
For what it's worth my SSH still works with me using Netrunner. I can't remembe r which version of cryptlib I have installed, 3.4.5 I think.
I just put the old headers back anyway and recompiled everything just in case.
I did a couple bugfixes and the ANSI editor works up to 160 columns now too so it was worth rebuilding the prealphas anyway!
Hopefully that works better. I don't know what is up with Cryptlib
3.4.6 hopefully it won't be a problem (and it will also replace the CBC SSH options).
Just updated to Jan 26th's build.
ssh -4 -p 2222 pi@bbs
I tried dropping in the new headers from the beta version of Cryptlib
and maybe that is breaking things. I'll put the old ones back and try
to get some tests done tonight to make sure the latest non-beta release works. I'll put up a new build tonight if I make any changes.
I suspect Cryptlib might be trying to remove the CBC ciphers in the new version and maybe that is messing with things.
Either Frank adjusted his binkd.cfg file or your fix is allowing him to connectto my RPI. If you thank you, if Frank, thank you :)
I did a couple bugfixes and the ANSI editor works up to 160 columns now too so it was worth rebuilding the prealphas anyway!
Hopefully that works better. I don't know what is up with Cryptlib 3.4.6 hopefully it won't be a problem (and it will also replace the CBC SSH options).
Either Frank adjusted his binkd.cfg file or your fix is allowing him to connect to my RPI. If you thank you, if Frank, thank you :)
1. At the moment within my Windows build, I have left py2 and py3 directories w ithin General Configuration blank. I'd like to set them
to the proper directori es for libraries if there is an advantage to
doing so? Before I download python 3.? I was curious to know if
doing so? Before I download python 3.? I was curious to know if
Windows Environment Variables still need to be set or not for each? I
Awesome about the ANSi editor - it'll make it much easier for me
creating mods; seeing as how I don't use 132c, but want to SUPPORT it, this is a cool addition. Thanks.
experiencing... for ME, on a Rasp berry Pi OS setup, leaving the Python2 and Python3 config lines BLANK fixed the problem, and all my [current] Python scripts are running just fine.
Thanks for all the hard work, and one day I'll [have to] UNDERSTAND what Py2 and Py3 needs to be set to - but its working on my basic Pi setup...
You forgot the third option! I broke into his house, had a little whiskey, admi red his retro hardware, and then switched him over from BINKD to Mystic while he was sleeping! Problem solved!
There shouldn't be any advantage to doing so. Mystic will search for
the defaul t library names and those values only need to be set if the defaults do not work for whatever reason. When its left blank its the same as if had set the values to "python27.dll" and "python38.dll" in Windows.
Turns out the block editing was still broke which I've mostly fixed up
now for the next build. It is nice to have it for quick edits and stuff at the least. At some point hopefully soon-ish Mystic is going to have
a full 132 default theme and I'll probably do all of the modding using
the built in ANSI editor.
Thanks for all the hard work, and one day I'll [have to] UNDERSTAND w Py2 and Py3 needs to be set to - but its working on my basic Pi setuBlank is fine if it works.
Leaving it blank should be the same as if you had typed in "libpython3.8.so.1.0" (or python38.dll in Windows). The reason for this option is because someone might be using Python 3.9 or 3.7 and will need to set their library name accordingly.
I did nothing, this is all g00r00 baby.
Well .. you replied to my emails and tried to help -- thats SOMETHING. ThanksFrank!
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 06:59:59 |
| Calls: | 516 |
| Files: | 7,012 |
| Messages: | 287,480 |