× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You must be running Windows2000 Pro.  This 'memory could not be "read"'
msg seems to appear quite often in Win2000. You would have probably found
that after a reboot you could have carried on without the error.  I was
getting this quite often after upgrading from Win98 to Win2000.  Had
version 9.0 Millennium edition of Lotus SmartSuite.  Reinstalled a few
times, sometimes I could open WordPro docs, and sometimes I couldn't.
Problem also extended to opening Word Docs with an old viewer program for
Word97.  Uninstalled the IBM ViaVoice integration piece from SmartSuite
and it seems to have solved the problem with both WordPro and older MSWord
viewer.  But it's not completely gone.  Occasionally I will still get this
'cannot "read" memory' msg, a reboot usually makes it go away and let me
get at my documents again.

...Neil





Jeff Crosby <jlcrosby@dilgardfoods.com>
Sent by: midrange-nontech-admin@midrange.com
2002-03-05 10:29
Please respond to midrange-nontech


        To:     midrange-nontech@midrange.com
        cc:
        Subject:        Re: Weird Word printer problem


Jeff Crosby wrote:

> If I click the Properties button in the print dialog, nothing happens,
> it just sits there.
>
> If I click the Options button, I get an error stating that a particular
> memory location could not be "read" (the error box has the quotes around
> "read").  When I click OK, I get an error stating that a particular
> memory location could not be "written" (the error box has the quotes
> around "written").  When I click OK, W2K bombs out of Word 97
> completely.
>
> The above only happens in Word

I realized my PC came with MS Works, so I installed Word 2002 from
there.  Now everything is A-OK.  But it sure is strange that it was fine
for months until yesterday.  Must have been that WDT Service Pack 4 I
installed.

--
-Jeff







As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.