Re: Internal File Triggers

> Re: Internal File Triggers
>
> > Starting with VADV32 v2.6 there will be some file triggers that are buil
> > VADV32. There is only one so far, but if you have any requests then let
> > know. Basically these will be triggers to perform VADV32 actions.
> > All internal file triggers should be located in the main VADV directory
> > trigger will be deleted after it is executed.
> > In the 2.5.0605014 beta there is the trigger to kill nodes. This is a ha
> > terminate action and should only be used on nodes that are locked up. Th
> > trigger is "KILLNODE.xxx" where "xxx" is the node nu
> > written a short script that you can use to fix locked-up nodes from a re
> > location (very useful). Make sure that only you the sysop can use this o
> > users will have fun killing the other nodes 
>
> Just what I have been waiting for...  Can't count the number of times I have
> locked up my board using DOORWAY.  

Yeah I'm usually on vacation or away for a while when a node gets locked up. I
don't like to have VNC available to the outside world all the time so this
should come in handy.

Please test this feature and the "close node" option from the node list when
someone is online (preferably you). It works on my systems here but want to
make sure it is working ok on others as well. It is using common API calls but
the trick is to close the netcom.exe and the ntvdm for the particular node..
which are child processes of cmd.exe.

Oh, and if you do a "reset node" then "close node" will not work since the
handle information is deleted. I might try to find a solution for this but for
now, don't do a reset node if you really mean to do a close node 

Steve


--
[AT2k] -- Your VBBS/VADV Support Center -- [www.at2k.org] -- [bbs.at2k.org]