CompuServe Messages

Alan, The answer probably lies in the programs you are running in your User-startup and WBStartup drawer. If another program patches the same OS libraries and calls as the ones MagicMenu does, then it can effectively "wipe out" MagicMenu even when Exchange says it is still running. Try removing your WBStartup programs out of WBStartup sequentially and reboot each time. Eventually ( hopefully ) MagicMenu will start working again and you will have found the conflicting program. Once you know which program(s) conflict with MagicMenu you can alter the CX_PRIORITY tooltype so that they run before MagicMenu at boot up. I noticed this problem when I ran Arq AFTER MagicMenu. Arq BEFORE MagicMenu is O.K. Happy detective work, Tony W. Driving my deck on AutoPilot