PC> set os2_shell=d:\os2\cmd.exe /k d:\os2init.cmd

 MS> Well, you could run the CMD.EXE with the /k from the command line. 
 MS> I'm running an OS/2 window from an Icon on my desktop using the
 MS> /kos2init.cmd method and its working fine.  Just another option...

I'm still having a problem with ...

set os2_shell=d:\os2\cmd.exe /k d:\os2init.cmd

in my config.sys.  For some reason the " /k ..." is not appended
to the same
line, but is being interpreted as a carriage return, so when I type "set"
from the command prompt, I get

os2_shell=D:\os2\cmd.exe
/k d:\os2init.cmd

instead of

os2_shell=D:\os2\cmd.exe /k d:\os2init.cmd

argh... btw, I sorted my config.sys alphabetically with QEdit (don't worry,
I know that certain file must be listed first), suppose this could have
something to do with it.  However, I've tried moving the line near beginning
and the end of config.sys, but it makes no difference.

btw, I'm running CMD.EXE as my WPS, not PMSHELL.EXE, wonder if this could be
the problem??

Phil


--- Blue Wave/Max v2.20p OS2 Beta