NTDOC,
Sorry for the verbal diarrhea. That's what happens when you burn the midnight oil. I was trying to explain two different situations.

1. The generation of the zero where none was expected. That was resolved by defining $chk = "" or by changing the to ? "NAV is " + $CHK


2. The third Case that wasn't coded for. If neither "rtvscan.exe" nor "rtvscn95.exe" were found, there was not a Case for it. Unfortunately my sloppy coding example didn't cut it, hence the hasty rebuttal.

What I propose is as follows:

code:

Break ON
If @INWIN = 1 ;NT/2K
	SHELL '%comspec% /c %windir%\pv.exe -q | find /i "rtvscan.exe"'
	If @error = 0
		$CHK = "NAVNT"	
		? "NAV is "$CHK 
		? "This should say NAVNT"
	Else
        	;unknown problem
		? "NAV is "$CHK 
		? "This should say nothing.  File entry was not found, that is why this is displaying."
	EndIf
EndIf
GoTo END
; Else must be 9X
SHELL '%comspec% /c %windir%\pv.exe -q | find /i "rtvscn95.exe"'
If @error = 0
	$CHK = "NAV9X"	
	? "NAV is "$CHK 
	? "This should say NAV9X"
	GOTO END
Else
        ;unknown problem
	? "NAV is "$CHK 
	? "This should say nothing.  File entry was not found, that is why this is displaying."
EndIf
:END
Get $
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.