Subj : Re: Something at least
To   : Janis Kracht
From : Nicholas Boel
Date : Mon Oct 05 2015 16:09:22

Hello Janis,

On 05 Oct 15 10:35, Janis Kracht wrote to Nicholas Boel:

 JK> I'm trying to find that v20e version for linux, it's out there
 JK> somewhere I'd expect.  I'll look some more today.

..24 is only an upgrade package. You'll need a full install prior to upgrading. 
http://usurper.info

 >> Are you running the door with the /P switch? And if so, I'm not sure
 >> if "/P/path/to/drop/file" would actually work (ie: slashes being
 >> backwards might interfere with old DOS ways?), as I didn't bother
 >> attempting it since Synchronet has a "%n" macro for the node
 >> directory..

 JK> Can you copy the directory structure for your Sync/Doors/USURPER/NODE
 JK> directory here?

/sbbs/xtrn/usurper is where the game is located.
/sbbs/nodeX are the node directories (where X is the node number).

So my node directory only contains DOOR32.SYS (I think it has to be uppercase 
for Usurper, and my usurper directory contains a full install of v.20e 
installed, then .24 copied over the top. Then I had to chmod +x USURPER and 
EDITOR. Ran EDITOR, only changed my sysop name and BBS name.. then tried 
"USURPER /L" which worked. Then ran it from the BBS with "USURPER /P%n", 
Stanrard IO with no echo to the console, and a DOOR32.SYS dropped in the node 
directory.

I remember doing a heck of a lot more the first time around, but came to find 
out most of it was unnecessary. Your main usurper directory shouldn't have any 
..CTL files, as it might cause a lock up.

Once you're able to run the game properly, you can create an empty USURP.CTL 
file in your usurper directory and the warning message (USURP.CTL can't be 
found, or something) when the game launches will disappear.

 JK> The way I'm calling the door, I tell bbbs to find the drop file in
 JK> doors/USURPER/NODE/ and I also write it out to
 JK> doors/USURPER/NODE/nodenumber 'just in case' (i.e., directory names
 JK> 0-14 since I have 15 nodes running here and I created the 15
 JK> directories in the NODE directory).

 JK> ~/ls -1 doors/usurper/NODE
 JK> 0
 JK> 1
 JK> 10
 JK> 11
 JK> 12
 JK> 13
 JK> 14
 JK> 2
 JK> 3
 JK> 4  <---DOOR32.SYS also in this directory since I logged in with
 JK> telnet. 5 6 7 8 9 DOOR32.SYS


 JK> If usurper is expecting something like a directory name such as node#
 JK> (like NODE/NODE1 or NODE/NODE2, etc.) I need to change the string I
 JK> create :)

As long as the "%u" you're using points to doors/usurper/NODE/4/ I would think 
you should be alright with that.

 JK> So, here's what I'm seeing now:

 JK> When I enter the door locally I can play the game (./USURPER /L in a
 JK> terminal).

 JK> When I telnet in, I see this:

 JK> ====cut here===
 JK>  Your version of Usurper needs to be upgraded.
 JK>    Current: UNKNOWN
 JK>    New    : 0.24

 JK>  I tried to upgrade for you, but failed:
 JK>  Unknown/unsupported version

 JK>  Please see UPGRADE.DOC for further instructions.

Looks like you're trying to run the EDITOR binary from the BBS? At least that's 
the only place I've seen the "I tried to upgrade for you, but failed" text.

 JK> ===cut here===

 JK> The above makes me think I do need to find v20e for Linux.

 JK> When I log onto my bbs node 2 and enter the door (which is really a
 JK> local call to the door) I see the same as when I telnet in.. hmmm....
 JK> maybe I need to extend that string that calls the door to include an
 JK> "if local" kind of line to call the door with /L for when I log onto
 JK> the bbs from a console.

 JK> Argh.. then again, it's Monday <vbg>

That could definitely be a part of it. My least favorite day of the week. :)

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20150715
 * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/701)

.