On 12-05-12, Nicholas Boel said the following...

Hello Gryphon,

On 04 Dec 12 at 21:02, you wrote to me:

Do you have to type the entire batch file's name (ie: START.BAT) when you call it? I don't know any better, as I've always wrote out the entire filename. *shrug*

You typically don't have to call START.BAT. Just START will do. But maybe that's my problem. I may have to do START $NODE. I'll give it a try.

Here it doesn't look like you're passing any variables into dosemu. My execution of dosemu looks more like this:

/usr/bin/dosemu -u virtual -I 'keystroke "\r"' NODE=$1 DOOR=$2 BBS=1 >/dev/null

What does passing the variables into dosemu help with? How is it applied?
Is there something in the dosemu.conf that uses it? My doors.ksh file uses those variables to create the DODOOR.BAT file, which is called by the autoexec.bat file.

pq gryphon
88 of
bd cyberia

--- Mystic BBS v1.10 A21 (Linux)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (2000:281/324)

On 12-05-12, Gryphon said the following...

On 12-05-12, Nicholas Boel said the following...

Hello Gryphon,

On 04 Dec 12 at 21:02, you wrote to me:

Do you have to type the entire batch file's name (ie: START.BAT) when y call it? I don't know any better, as I've always wrote out the entire filename. *shrug*

You typically don't have to call START.BAT. Just START will do. But
maybe that's my problem. I may have to do START $NODE. I'll give it a try.

Nope, that ain't it. I already had it that way.

pq gryphon
88 of
bd cyberia

--- Mystic BBS v1.10 A21 (Linux)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (2000:281/324)

Hello Gryphon,

On 05 Dec 12 at 20:32, you wrote to me:

On 12-05-12, Nicholas Boel said the following...

Hello Gryphon,

On 04 Dec 12 at 21:02, you wrote to me:

Do you have to type the entire batch file's name (ie: START.BAT)
when you call it? I don't know any better, as I've always wrote
out the entire filename. *shrug*

You typically don't have to call START.BAT. Just START will do. But maybe that's my problem. I may have to do START $NODE. I'll give it
a try.

Yeah, you definitely have to pass the node number into the batch file.

Here it doesn't look like you're passing any variables into
dosemu. My execution of dosemu looks more like this:

/usr/bin/dosemu -u virtual -I 'keystroke "\r"' NODE=$1 DOOR=$2
BBS=1

/dev/null

What does passing the variables into dosemu help with? How is it
applied? Is there something in the dosemu.conf that uses it? My
doors.ksh file uses those variables to create the DODOOR.BAT file,
which is called by the autoexec.bat file.

AFAIK, you need to pass any variable through _everything_. Your script, your batch files, etc. If you don't pass anything to your script, how does the batch files know what node number it's on? Or where the dropfile is located?

Also, when you actually execute the script from mystic, are you passing the variables there too?

Regards,
Nick


---
■ Synchronet ■ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)

On 12-06-12, Nicholas Boel said the following...

Hello Gryphon,
AFAIK, you need to pass any variable through _everything_. Your script, your batch files, etc. If you don't pass anything to your script, how
does the batch files know what node number it's on? Or where the dropfile is located?

My autoexec calls the DODOOR.BAT file. The DODOOR.BAT file is created by
the doors.ksh file each time it is called. The doors.ksh file creates the DODOOR.BAT file differently for each door. One of the things it does is
add the lines:
echo "M:" >> DODOOR.BAT
echo "CD \DOORS\LORD" >> DODOOR.BAT
echo "START $NODE" >> DODOOR.BAT

so when you view the DODOOR.BAT file, it looks like this:
...
M:
CD \DOORS\LORD
START 1
...

Also, when you actually execute the script from mystic, are you passing
the variables there too?

Yes, the Optional data line is "/home/bbs/doors.ksh LORD %3"

pq gryphon
88 of
bd cyberia

--- Mystic BBS v1.10 A21 (Linux)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX (2000:281/324)

Hello Gryphon,

On 06 Dec 12 at 22:20, you wrote to me:

Hello Gryphon,
AFAIK, you need to pass any variable through _everything_. Your
script, your batch files, etc. If you don't pass anything to your
script, how does the batch files know what node number it's on? Or
where the dropfile is located?

My autoexec calls the DODOOR.BAT file. The DODOOR.BAT file is created
by the doors.ksh file each time it is called. The doors.ksh file
creates the DODOOR.BAT file differently for each door. One of the
things it does is add the lines: echo "M:" >> DODOOR.BAT echo "CD \DOORS\LORD" >> DODOOR.BAT echo "START $NODE" >> DODOOR.BAT

so when you view the DODOOR.BAT file, it looks like this:
...
M:
CD \DOORS\LORD
START 1
...

Do you see anything even get to this point? To test further, add a pause to your autoexec.bat as well as your dodoor.bat files to see how far it actually makes it in this process. Did you mention prior that it actually starts dosemu as well, but hangs at a blank screen, or exits out of dosemu right away?

Also, when you actually execute the script from mystic, are you
passing the variables there too?

Yes, the Optional data line is "/home/bbs/doors.ksh LORD %3"

If you can tell that it actually starts running your script, then you're okay. If it errors out on your script, you might want to try adding "/bin/ksh" to the beginning of your script.

Otherwise, as I haven't spent a ton of time trying to get it to work right with Mystic quite yet.. You should see what version of dosemu Netsurge is using. His Mystic a21 seems to be running doors just fine.

Plus the fact that the Synchronet programming echo probably isn't really the best place for this discussion. :)

Regards,
Nick


---
■ Synchronet ■ thePharcyde_ >> telnet://bbs.pharcyde.org (Wisconsin)