Just jumping in with a few thoughts.
We get a number of "odd" problems in various software apps which seem to defy logic. My most frequent approach is to assume that the computer in question is suffering from either memory leakage or hard disk overload.
In the m-l scenario, everything you did today leaves something in RAM which eventually clogs up and causes an interference at a critical address, which shows up in either the screen redraw or the printer buffer (which are probably low in the useage heierarchy.
In the h-d-o scenario, all the temporary files which you write to the hd every time you flip out of a screen or window, eventually interfere with the processor's ability to find a big enough contiguous block to reserve for the next command, which again may be a screen redraw or print spooling.
In the majority of cases the rule is "save frequently and always be prepared to reboot". That way you will avoid, or at least work out of many of the sillier problems.
When we find something which, reliably will not work on one computer but will work on another, upgrading the first to the memory size of the second is the most likely solution.
You can get downloadable memory managers like RAMIdle which will handle the day to day chores of cleaning out the memory leakage but they too sometimes cause the problem (due to address interferences?)
We have also had printing problems which cropped up on the way to a network plotter because of some sort of incompatibilities with the spooling capacity of the computer, the intermediate server, the router and the plotter. We solved that by hard coupling the computer to the plotter for those files which didn't make it properly.
Funny things computers!!
Good luck
![[smile] [smile] [smile]](/data/assets/smilies/smile.gif)
David