CompuServe Messages

Well, well, well… It appears that cpublit (!) is the culprit. I went ahead a renamed the WBStartup directory as you suggested (Neat idea, that!) and I also commented out all of the "unusual" stuff I start in my User-Startup (This included QMouse, cpublit, upd and resethandler). FCII then printed the document just fine. OK, re-boot with everything back to normal, on to the next step. Since I had noticed some problems I associated with cpublit before (with TurboText), I shut it down (cpublit -q) and tried to print… no problems. Startup cpublit again, try to print, BOOM! Hmmm, methinks cpublit must be stomping on someone elses memory. Just a guess, maybe cpublit has problems with programs that do extensive text blitting (such as FCII and TurboText). Thanks for the help. (Yea!) I never really tried to track this down before, since I loath resetting my system. Because it is a UUCP site I run it 24hrs 7 days a week. D*mn, I'm going to hate having my text flash in JR-Comm again (without cpublit running). *SIGH* Thanks again for your help! Bill