>Is it possible in VFP to trap "Pure Virtual Function Call" errors generated by having an old or unreliable printer driver installed?
>
>I have code that has to interrogate the capabilities of the installed printing devices in order to present a customised dialogue for selection of a printer and a print output tray.
>
>Having tested this extensively, I've started to run into issues with some printer drivers, especially HP ones which produce these errors.
>
>I have found that printing from Word XP doesn't cause this problem, and works as expected. However I also found that printing from Notepad on Windows 98, I get an error with an Invalid Page Fault in the kernel, which may be relevant, I just don't know.
>
>This is really getting to the stage now of a re-design if this error cannot be trapped.

It sounds like you have to live with the buggy HP printer drivers which is too bad.

A few SWAGs:

- Tried _fpreset?
- Tried test printing to a file and/or the NUL device?
- You could farm out a test print to a module written in another language, that may be able to trap the error