Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP6 locking up/Solutions??
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00168933
Message ID:
00169327
Views:
27
Marcus:

Here is a KB article that explains problems using HP printer drivers and MS products.

HTH,

--Paul

OFF: "Out of Memory" Messages When Running Microsoft Office
Last reviewed: September 21, 1998
Article ID: Q165985




--------------------------------------------------------------------------------

The information in this article applies to:
Microsoft Office for Windows 95, versions 7.0, 7.0a
Microsoft Office 97 for Windows


SYMPTOMS
When you run a Microsoft Office program, you may receive one or more of the following error messages:


Out of memory.

-or-

Not enough memory to display completely.

-or-

Your file could not be printed due to an error on .

-or-

This program has performed an illegal operation and will be shut down.
If the problem persists, contact the program vendor.

If you click Details, you receive an error message that is similar to
the following:

caused an invalid page fault in module MSO97.DLL at
.

In addition, the amount of available random access memory in your System and graphics device interface (GDI) memory heaps may drop to a very low level (10 percent or less).
These problems may occur especially when you use Microsoft Word as your e-mail editor.



CAUSE
These problems may occur if the following conditions are true:

A printer driver for any of the following printers is installed on your computer:


HP DeskJet 660C
HP DeskJet 670c
HP DeskJet 672c
HP DeskJet 680C
HP DeskJet 690C
HP DeskJet 694C
HP DeskJet 820
HP DeskJet 820C
HP DeskJet 820CSE
HP DeskJet 870Cse
HP DeskJet 870Cxi
HP DeskJet 890c
HP LaserJet 6P


-and-
One of these printers is the default printer.

WORKAROUND
You may be able to reduce the effects of this problem by doing one of the following:

It is possible that using an earlier version of the printer driver will correct the problem; however, this has not been confirmed by Microsoft.
It is also possible that the latest version of the printer driver will correct the problem. The latest versions of the printer drivers can be downloaded from the following Hewlett-Packard Internet web site:


http://www.hp.com/
The third-party contact information included in this article is provided to help you find the technical support you need. This contact information is subject to change without notice. Microsoft in no way guarantees the accuracy of this third-party contact information.

Before you start the Microsoft Office program or any other program in which the problem may occur, set the default printer to a printer that is different from the printers listed in this article.
If you must use one of the printers listed in this article, do not print or view the document in print preview unless it is necessary. Every time you use the printer driver more memory is lost in your System and graphics device interface (GDI) memory heaps.
Save your work often.
If you start to encounter problems that are related to memory, save your work, quit all open programs, and then restart your computer.

MORE INFORMATION
The printers listed in this article do not contain their own memory; instead, the printer drivers are designed to use the computer memory when rendering and processing print jobs.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

>Utilizing the vast resources of the UT, I have narrowed my freezing issues in Win95/98 to be the use of HP drivers. I can now recreate the locking up, or blue screen fatal exceptions my users were experiencing. Previous threads have noted that the _fpreset() function suggested by MSKB does NOT fix the problem, which is my experience also. It seems that the only solution is to switch users to MS versions of their printer drivers. Does this seem correct? Anyone know if this is being addressed at MS? Finally, does anyone know of a good article or document I can show my users to convince them that HP drivers are problematic (even though this issue may not be HP's fault) so that I don't look incompetent when I tell them my program can't use HP drivers? All feedback is most welcome.
>TIA
>Marcus.
Previous
Reply
Map
View

Click here to load this message in the networking platform