Subj : ruling out
To   : g00r00
From : Rick Smith
Date : Fri Dec 30 2022 09:40 pm

Greetings g00r00!

Friday December 30 2022 21:36, you wrote to me about an urgent matter!:

gr>  * Forwarded from area 'MYSTIC'
RS>> I decided a brand new VM with ubuntu, fresh install mystic and
RS>> worked as expected, copied over my working mystic bbs minus
RS>> executables and I get the errors from previous message.  So has
RS>> to be something in the working

gr> I would suggest that you do the install fresh as you mentioned, and
gr> then try copying over things slowly to see when it breaks.  It could
gr> be that there is a "Pi" executable still there.

gr> Another possible issue is that your paths in your old configuration do
gr> not much the paths in your new configuration.  If they are not
gr> identical, then you'd have to try to find all the places in the
gr> configuration and change them to the correct locations.

gr> Also do you see anything in the log files when you try to run it?  Or
gr> anything in the errors.log?

I do not see anything in the logs.. The paths should be the same /mystic  I can now get mystic -cfg to work (turned out I did have a couple pi executables remain qwkpoll and couple others, took care of that did a whole fresh install on a new ubuntu machine.

now when I run ./mystic -l I simply get a blank screen that just says "busy" and have to ctrl c to get prompt back. ./mis starts and runs and appears fine.  Not sure what to check next to be honest.  I can start another vm and try again but I am pretty sure thats the definition of insanity! lol

Thank you for your help



----
Regards,


Rick Smith (Nitro)

... To go where no man has gone before... BBSing!
--- GoldED+/LNX 1.1.5-b20180707
* Origin:  ----> Abacus BBS! --->>>>bbs.abon.us:2323  (1:105/10)