CompuServe Messages

I'm not exactly sure who to address this to, so I'm going to throw it out to the general masses and hope someone can give me a clue… I recently received my upgrade to WShell 2.0 (less than a week turn-around – thanks Bill!), and after installing it, I've run into 2 seperate problems. Well, only one is a problem, the other an inconvenience. The "problem" is that I can no longer get Directory Opus to do any kind of archive operation, mainly because I can't get it to open a shell window to do it in. I've played with the DirOpus configuration options for the past two days now, to no avail. It _will_ open a WShell on the Workbench when I click on the RUN gadget, but any gadgets that cause a DirOpus script to run (like archiving operations) no longer work. In fact, they hang until I press SHIFT+ESC, but no shell window ever opens, not on the Opus screen nor on Workbench. I don't know if I have the Opus configuration wrong, or if I need to change something in my WShell configuration. Any help would be greatly appreciated. The "inconvenience" concerns the recently released ToolsX program (SteveX's pgm to launch pgms from the WB2.0 Tools menu). After installing WShell, every time something is launched from the Tools menu, a shell window appears on my WB screen and stays there until I close it. As I said, it's not really a problem, just an inconvenience. Any know how to get rid of it? I've been a WShell user for years now, and can't live without it. The new version is really nice and I recommend it highly. If I have to live with these problems, I will, but I'd really appreciate any advice any of you may have that would help me rectify them. Thanks! – via Whap!