|
Chuck, Well I don't use Outlook so I probably won't be able to contribute anything more helpful! :) I'd recommend exiting Outlook. Go into the task manager and make sure that the Outlook process has is no longer there. End it (the process) if you have to. Then Click the CPU header (to sort) under the Processes tab and see if anything else is using that memory. If it is *only* Outlook doing this, then it's probably safe to assume Outlook is causing the problem and not a memory chip. Didn't Microsoft make Outlook? <g> :) Mike > Yep, Outlook is the main pig, but exiting it doesn't make one bit (no pun > intended) of difference. Exiting anything doesn't. This is a weird one, as I > noted :-) > > Thanks ! > > Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.