Subj : Re: Door problems
To   : Digital Man
From : Cisop
Date : Tue Sep 27 2005 10:14 pm

 >   Re: Re: Door problems
 >   By: Cisop to Digital Man on Tue Sep 27 2005 12:20 am
 > 
 >  >  >   Re: Re: Door problems
 >  >  >   By: Cisop to Digital Man on Mon Sep 26 2005 09:38 am
 >  >  >
 >  >  >  >  >   Re: Re: Door problems
 >  >  >  >    >
 >  >  >  >  >  >  I removed the sbbsnode value from windows and the doors work
 > fi
 >  >  > now
 >  >  >  > But
 >  >  >  >  >  > when I tried to use the ;shell command I found it would not
 > work
 >  > In
 >  >  > f
 >  >  >  >  > no
 >  >  >  >  >  > of the sysop commands will work. The screen blinks almost
 > instan
 >  >  > an
 >  >  >  > the
 >  >  >  >  >  > prompt returns. Could this be related?
 >  >  >  >  >
 >  >  >  >  > Nope, different problem. What's your security level? What 
command
 >  > shell
 >  >  > a
 >  >  >  >  > you
 >  >  >  >  > using? If you hit '!' to see the sysop menu?
 >  >  >
 >  >  >  > I am using the Classic shell. I get the sysop menu when I hit "!". 
My
 >  >  > securi
 >  >  >  > level is 99.
 >  >  >
 >  >  > Do you have str_cmds.js in your exec directory? If so, remove it.
 > 
 >  > Yes I did have that file. After I removed it the sysop commands worked
 > again
 >  > However when I run the ;SHELL command it opens an exe/dosxtrn window.
 > 
 > Are you running Windows 9x or an NT-based OS?
 > 
 > ;SHELL should *not* open a DOSXTRN window on NT-based OSes since your 
command
 > shell (cmd.exe) is not a DOS program in that case. If you are running an
 > NT-based OS and ;SHELL is opening a DOSXTRN window, then it sounds like
 > "cmd.exe" is missing from your SCFG->External Programs->Native Program List.
 > 
 >                                                   digital man
 I had "cmd" in the native program list. When I changed it to "cmd.exe" 
everything worked fine.

thanks

-
pete

---
 þ Synchronet þ SBBS Orillia -- Telnet://bbsorillia.com

.