I've been chasing this problem for awhile.

I have mystic installed on D:\Mystic
All of my scripts are in D:\Mystic\themes\default\scripts for all themes. Scripts that are in this directrory work fine.

However, Some scripts have additional files that are in different directories. RCS's new Game Room is an example. The Game Room menu files are in D:\mystic\themes\default\scripts\rcsmenus.
The script point to that directory. Under my current setup the script does not work as it can't seem to find the "rcsmenus" directory.

But... I setup a default Mystic install on C:\Mystic.
Nothing changed with the RCS GameRoom, same files, same location except under C:\.
And it works fine!

The only difference between the 2 is the location of the home Mystic Drive, C:\ vs. D:\. C works, D doesnt.

It not just this script, it appears to be any script that calls files outside of the script directory.

Is there any reason Mystic installed on D:\ would cause this? I'm out of ideas. Thanks!

|01 ├|06HSM|01─|14aka|01─|07Ga|08ry|01───────────────┐
|14 ┐|01│ Mystic|14.|01BBSGameTime|14.|01com|14:|0323|01 │|14┌
│|01│ ScoobysDoo|14.|01ddns|14.|01net|14:|032023|01 │|14│
│|01└───────────────────────────┘|14│

--- Mystic BBS v1.12 A47 2021/05/27 (Windows/32)
* Origin: BBS GameTime - mystic.BBSGameTime.com:23 (1:129/328)

Is there any reason Mystic installed on D:\ would cause this? I'm out of ideas. Thanks!

I can't tell you what is going on with that mod, but Mystic doesn't have any hard coded directories. I've had my BBS installed on drive D: since Mystic 0.01 (ie easily 25 years now) and it runs scripts all over the place just fine here.

There isn't enough detail for me to diagnose any issue with the script or how its executed.
--- Mystic BBS v1.12 A47 2021/05/26 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 5/27/2021 1:27 PM, Gary Ailes wrote:

The script point to that directory. Under my current setup the script does not
work as it can't seem to find the "rcsmenus" directory.

But... I setup a default Mystic install on C:\Mystic.
Nothing changed with the RCS GameRoom, same files, same location except under C:\.
And it works fine!

The only difference between the 2 is the location of the home Mystic Drive, C:\
vs. D:\. C works, D doesnt.

Sounds like the rcsmenu script has some hardcoding of C: in it.
--- SBBSecho 3.10-Win32
* Origin: IPTIA 1:275/301 bbs2.ipingthereforeiam.com:2323 (1:275/301)

On 28 May 2021, g00r00 said the following...

Is there any reason Mystic installed on D:\ would cause this? I'm ou ideas. Thanks!

I can't tell you what is going on with that mod, but Mystic doesn't have any hard coded directories. I've had my BBS installed on drive D: since Mystic 0.01 (ie easily 25 years now) and it runs scripts all over the place just fine here.

There isn't enough detail for me to diagnose any issue with the script
or how its executed.

Hi!
Here's an example from a script:

(original)
rcspath:=AddSlash(CfgMPEPath+'tdta')
(my fix)
rcspath:='D:\mystic\themes\default\scripts\rcstdta\'

The top line is what does not work for me but apparently
works for everyone else. Scripts that point to a directory outside of the default scripts directory don't load correctly because they can't find the needed files.

The second line is how I had to correct to make it work on my system.
This "fix" works on most scripts. With the directory hard coded it works, but shouldn't the original work as well?

It's definitley something on my end. I had this problem in Linux and it followed me to Windows when I migrated.

Thanks!

|01 ├|06HSM|01─|14aka|01─|07Ga|08ry|01───────────────┐
|14 ┐|01│ Mystic|14.|01BBSGameTime|14.|01com|14:|0323|01 │|14┌
│|01│ ScoobysDoo|14.|01ddns|14.|01net|14:|032023|01 │|14│
│|01└───────────────────────────┘|14│

--- Mystic BBS v1.12 A47 2021/05/27 (Windows/32)
* Origin: BBS GameTime - mystic.BBSGameTime.com:23 (1:129/328)

(original)
rcspath:=AddSlash(CfgMPEPath+'tdta')
(my fix)
rcspath:='D:\mystic\themes\default\scripts\rcstdta\'

The top line is what does not work for me but apparently
works for everyone else. Scripts that point to a directory outside of

CfgMPEPath is the current theme's script directory. That isn't always where the script runs from through if your theme inherits scripts for the default or a different theme. Its also looking in directory named 'tdta' for some reason, not rcstdta.

To get the directory where the script is running from you would get it like this:

RunningFrom := JustPath(ProgName);
--- Mystic BBS v1.12 A47 2021/05/28 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

Hi g00r00,

I try connect my boss via IPV6, but it seems i can make a connection but there seems to be some other problem when i see the log any idea?


Polling all nodes of session type ALL
Polling 2:292/854 on slot 1 via BINKP
Connecting to many-glacier.dyndns.org on port 24554
Using address 2A02:A03F:83A9:C400:4DF3:890A:8EC1:7CC0
Connected by IPV6 to 2A02:A03F:83A9:C400:4DF3:890A:8EC1:7CC0
RB Socket read status 107
RB Socket read result 107
Connection lost
Authorization failed
Polled 1 systems

Ward is using DBridge and with IPV4 connection it works fine so i have no idea what can be wrong...

Thanks!

Greetings,
Rudi

... Operator, give me the number for 911

--- Mystic BBS v1.12 A47 2021/08/15 (Linux/64)
* Origin: AfterShock Beta Tester (2:292/140)

Rudi,

Ward is using DBridge and with IPV4 connection it works fine so i have no idea what can be wrong...

Actually, the IPv6-part is handled by Binkd.

\%/@rd

--- DB4 - Jul 07 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

I try connect my boss via IPV6, but it seems i can make a connection but there seems to be some other problem when i see the log any idea?

This isn't a Mystic error its a network error so it would be difficult for me to diagnose that. What do the logs say on the system you are connecting to?

https://www.google.com/search?q=socket+error+107

... Redundant book title: DOS For Dummies

--- Mystic BBS v1.12 A47 2021/08/08 (Windows/32)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hi g00r00,

for me to diagnose that. What do the logs say on the system you are connecting to?

I dont know i will ask Ward that he can look into his logs and paste it here.

Greetings,
Rudi

... Confucius say: "Its stuffy inside fortune cookie"

--- Mystic BBS v1.12 A47 2021/08/15 (Linux/64)
* Origin: AfterShock Beta Tester (2:292/140)

Rudi,

I dont know i will ask Ward that he can look into his logs and paste it here.

There just is nothing there pointing to an IPv6 event initiated by yourself.

\%/@rd

--- DB4 - Jul 07 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)