search

hlsantos / wcSDK

Wildcat! Interactive Net Server SDK/API
5 stars 1 forks source link

Standard DOOR CLI parameters #4

Open hlsantos opened 4 years ago

hlsantos commented 4 years ago

What would be the standard for passing Door.Sys or Door32.sys to a door application. In the wcDoor32 examples, I was using parameter #1 or argument #1 as the full path name to "door.sys".

The Door32.Sys is also generator and in the same location as the door path/directory. So what I did in in the my current pf wcDoor32 is use the 1st parament was the directory location of where the door.sys and door32.sys is located.

But I thinking using command line switches too.

But the issue and question is what do developers of the wcDoor32 API expect. They may have their own "standard" for readiing command line arguments?

jkulwicki commented 4 years ago

I like the idea of command line switches.

ie: doorname.exe /p or doorname.exe -p

Either way.

On Thu, May 14, 2020 at 9:52 AM hlsantos notifications@github.com wrote:

What would be the standard for passing Door.Sys or Door32.sys to a door application. In the wcDoor32 examples, I was using parameter #1 https://github.com/hlsantos/WcSDK/issues/1 or argument #1 https://github.com/hlsantos/WcSDK/issues/1 as the full path name to "door.sys".

The Door32.Sys is also generator and in the same location as the door path/directory. So what I did in in the my current pf wcDoor32 is use the 1st parament was the directory location of where the door.sys and door32.sys is located.

But I thinking using command line switches too.

But the issue and question is what do developers of the wcDoor32 API expect. They may have their own "standard" for readiing command line arguments?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/hlsantos/WcSDK/issues/4, or unsubscribe https://github.com/notifications/unsubscribe-auth/AESBKDLXMDNR4F4ZXE6HXPDRRQASDANCNFSM4NAYIP6A .

hlsantos commented 4 years ago

For wcDoor32 based doors, the switch /dp;{door_path} will be used to read both Door.Sys and Door32.sys

reapern66 commented 4 years ago

Hi will wins add variables for sockets handles and I think com sockets. simpler to how %wcnodeid% works.

 MYSTIC DOOR MCI Codes: (used when running a door only)

" %0 Socket handle on Windows (1 on Unix) %1 Returns 1 (old comport code from DOS version) %2 Returns 38400 (old baud rate from DOS version) %3 Node number %4 User's IP address %5 User's host name %# User's permanent index number %T User's time left %P Node's temporary directory (where door drop files are created) %U User's handle (All spaces replaced with _ characters)

 Adding /DOS on a door command line will tell Mystic to create a DOS format
 drop file (ie, lines ending with CRLF) even when running on an operating
 system that may use a different format (ie Linux, etc)

" http://wiki.mysticbbs.com/doku.php

regards.