CompuServe Messages

Sandy Have just been reading the string of messages on you MSCDEX problem and can suggest one other possible cause for it: When you go through the sequence you describe and Word for Windows fails to find that .DLL (you thought it might be TOOLS.DLL), I assume Word then fails to start. What *might* be happening is: Word begins reading .DLLs into memory to support its operation, is unable to find one of them, and drops back to the Program Manager or Norton environment without flushing what it has just stuffed into memory. You then try to run another CD-ROM and the "residue" of Word's aborted load sequence gets in the way of the new program. I have had this problem with a Windows program I am developing, where an early and inevitably "buggy" version was crashing in the load sequence. I was monitoring the system and noticed resources were disappearing and not reappearing after each crash – sure enough, code from a .DLL was still in memory. If you do not have the problem anywhere except in the sequence Corel -> Word you described, dropping MSCDEX 2.21 in favor of an earlier version may not be the best way to go, as there seems to be a growing volume of software being written which requires at least 2.2 or later. Ric