I appologize again as i finally realized this is the correct space for Synchronet Support. When i try to run a basic custom shell, I get this error:

9/19 02:09:20p Node 1 <Taalmahret> !ERROR 2 (No such file or directory) (WinError 2) in main.cpp line 4346 (node_thread) opening "D:\Tools\sbbs\exec\loquinth.bin" access=0

It is looking for a bin file. In this scenario I wrote the code in javascript and then saved the file named loquinth.js in the exec directory. The filename matches the internal code.

I verified that all shells installed with the latest version of synchronet have a .bin file in the exec directory that when i remove them the BBS fails to find a suitable .bin file. Even when the shell as a matching .js file this error occurs.

Are we supposed to compile the .js somehow or is there a step that I am missing in order to get the BBS to execute these .js files as a custom shell?

Sincerely,
David Tawater
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Synchronet Custom Shells
By: Taalmahret to Digital Man on Fri Sep 20 2024 07:34:13

9/19 02:09:20p Node 1 <Taalmahret>> "D:\Tools\sbbs\exec\loquinth.bin"

javascript and then saved the file named loquinth.js in the exec

What version of Synchronet are you running?

Until somewhat recently only Baja (.src compiled to .bin) shells were supported. The technique to launch a JS shell was to create a Baja stub. You'd create a file called "loquinth.src" containing this:

exec "?loquinth.js"

then build it with "baja ./loquinth.src" to get "loquinth.bin". When the BBS launches the LOQUINTH command shell, it executes this module, which in turn invokes the JS.

Assuming you're on an old version, you can either upgrade or use this old technique.

echicken
electronic chicken bbs - bbs.electronicchicken.com
---
þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Synchronet Custom Shells
By: Taalmahret to Digital Man on Fri Sep 20 2024 07:34 am

I appologize again as i finally realized this is the correct space for Synchronet Support. When i try to run a basic custom shell, I get this error:

9/19 02:09:20p Node 1 <Taalmahret> !ERROR 2 (No such file or directory) (WinError 2) in main.cpp line 4346 (node_thread) opening "D:\Tools\sbbs\exec\loquinth.bin" access=0

It is looking for a bin file. In this scenario I wrote the code in javascript and then saved the file named loquinth.js in the exec directory. The filename matches the internal code.

I verified that all shells installed with the latest version of synchronet have a .bin file in the exec directory that when i remove them the BBS fails to find a suitable .bin file. Even when the shell as a matching .js file this error occurs.

Are we supposed to compile the .js somehow or is there a step that I am missing in order to get the BBS to execute these .js files as a custom shell?

It sounds like you're not running SBBS v3.20 (still in development). JavaScript command shell support is a feature of v3.20. In v3.19 and earlier, you'd need a small "stub" (.bin) file to invoke the JavaScript shell (see Deuce's lbshell as an example). You don't need the stub in any more in v3.20.
https://wiki.synchro.net/install:dev
--
digital man (rob)

Synchronet/BBS Terminology Definition #17:
CRC = Cyclic Redunancy Check
Norco, CA WX: 73.5øF, 52.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Synchronet Custom Shells
By: echicken to Taalmahret on Fri Sep 20 2024 10:50 am

Until somewhat recently only Baja (.src compiled to .bin) shells were supported. The technique to launch a JS shell was to create a Baja stub. You'd create a file called "loquinth.src" containing this:

Wow. Thank you a million. So simple but spot on. Im now off to the races so to speak. I'll post my BBS when i get all the dust cleared.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)