Close - no need for double $ outside of quotes. There's also an odd double-quote there. Since you're calling a child Kix script and passing args, the whole thing can be in a string.

Again, try building your command as a string so you can display it during development and debugging:
 Code:
$Cmd = '%COMSPEC% /s %SYSTEMDRIVE%\NETWORK\KIX32.EXE '
$Cmd = $Cmd + 'S:\network\pathman.kix '

; sanity will complain about this $ - is OK, but MUST have NoVarsInStrings active
$Cmd = $Cmd + '$ACTION="REM" '

; Sanity won't complain about this line - the $ is replaced with Chr(36) outside the string
$Cmd = $Cmd + Chr(36) + 'PATH="DL\PTC\Intralink 3.4\Bin"'  

; Should have WrapAtEOL turned on to properly see a long command line
; These can be removed or commented after testing.
'About to execute the following command:' ?
$Cmd ?

; Uncomment this line when the output string looks correct
; You can even copy the output line from the screen and paste it into 
; a command prompt to verify that it works.
; Shell $Cmd
By using "$Cmd = $Cmd + something", you can build the command bit by bit and easily see where quote or $ issues can arise. All of the lines are valid, but Sanity will complain about the first form because it sees a variable inside quotes. With NoVarsInStrings turned on in the beginning of your script, Kix won't interpret the variable, but Sanity doesn't know that (or recognize the NoVarsInStrings setting).

I'd suggest using the second format (Chr(36) + 'var=value') format as it will work regardless of the NoVarsInStrings setting, and won't trigger a Sanity warning.

Keep in mind that Sanity never issues errors! It warns you that it detected something that COULD be an issue. If you span a string across 2 or more lines - Sanity will warn about mismatched quotes - a heads up that this might not be what you intended. When I code with KGen, I closely examine the Sanity warnings and make note if which/how many I can safely ignore (usually in Execute statements or KixForms declarations) and make sure that I always get that number of warnings. The whole point it to have it find and eliminate the common, stupid errors that are just damn hard to find after staring at code for hours (or days).

Glenn
_________________________
Actually I am a Rocket Scientist! \:D