Yes, internal commands are performed first no matter what. And COMMAND.COM is not the kernel, it is a shell, equivelant to bash, ksh, csh, sh in UNIX. I'm not sure how easy it is to replace COMMAND.COM with another shell on Win9x, but in NT it's pretty easy to replace CMD.EXE with the windows version of "bash" or "ksh". That oughtta throw em for a loop.
In Win9x and below it would probably go something like:
SET COMSPEC=C:\BASH.EXE
in the AUTOEXEC.BAT or
SHELL=C:\BASH.EXE
in the CONFIG.SYS but I'm not going fire up Winblows to find out...
Of course remember that COMMAND.COM is also responsible for executing *.BAT files. Bash would not be able to execute batch files but would be able to execute Bash scripts.
[ August 02, 2002: Message edited by: VoidMain ]