CompuServe Messages

Steven, Well, maybe it wasn't the ECHO that fixed it. At the time, I also stopped using WShell with the CON: device. I use the CNC: device for all my shells, so I really didn't need to use it with CON: anyway. Frankly, I don't entirely understand the differences between the two devices, mostly because I haven't had time to study the manual yet. I never used the CNC: device until I started having trouble with the old version of WShell under earlier versions of WB2.0. I remember Bill suggesting the switch back then, and now the WShell 2.0 manual seems to use CNC: as its primary device, so I've stuck with it. The manual also showed how to use it with CON: by first dismounting it, then using the DHOpts command to assign it to a WShell. Apparently that's what caused the problems with Opus, and maybe with ToolsX too. Anyhow, now I only have six WShell-related lines in my user-startup file, which are: DHOpts PIP: CNC:0/11/640/200/WShell/CLOSE MENU S:CNC-Menus resident Shell l:wshellseg system pure resident WShell l:wshellseg system pure FComp Newwsh popcli 99999 newwsh Actually, the main reason for these little problems I've been having is probably because WShell 2.0 seems so different from previous releases, and it's just going to take some time to become familiar with all of its many features and how they work. In time, I'll get the hang of it. Mike – via Whap!