I'm working on adding DOOR32.SYS and socket sharing to ENiGMA. Using the latest Legion release that was just hatched, I run as follows: c:\path\to\legion.exe -D c:\path\to\DOOR32.SYS -N <node>
You need a batch file to change to your Legion RPG directory, otherwise there will be problems (a bug I'm needing to fix). Try something like:
Enig supports 'cwd' which I'm switching to. I'll double check that it's actually working, but I'm pretty sure it is. For good measure, I'll do
the batch approach so it can be ruled out.
Sounds good. I don't want any limit on which systems run the Legion RPG door. I would like to expand support it for whichever system a SysOp chooses, not specifically one or another as well as the platform.
On Friday, March 30th cr1mson was heard saying...
Sounds good. I don't want any limit on which systems run the Legion door. I would like to expand support it for whichever system a SysOp chooses, not specifically one or another as well as the platform.
Tried the batch file thing, no luck :( It simply launches the executable and exits. Maybe I'll get a process monitor log just to see if anything stands out.
Here is an example door32.sys:
----/cut/-----
2
1152
57600
ENiG
1
Bryan Ashby
NuSkooler
100
546
1
1
----/cut/-----
On Friday, March 30th cr1mson was heard saying...
Sounds good. I don't want any limit on which systems run the Legion door. I would like to expand support it for whichever system a SysOp chooses, not specifically one or another as well as the platform.
Tried the batch file thing, no luck :( It simply launches the executable and exits. Maybe I'll get a process monitor log just to see if anything stands out.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 57 |
Nodes: | 4 (0 / 4) |
Uptime: | 34:52:01 |
Calls: | 513 |
Files: | 6,925 |
Messages: | 286,365 |