>>>>Hi, Fred...
>>>>
>>>>When I first read your message, I wondered what was in those doughnuts you've been eating <g>, but figured I'd give it a shot. (I've wondered about video drivers, but never suspected a printer driver.)
>>>>
>>>>And you were right!
>>>>
>>>>I don't have an HP driver, but I do have a driver for a color laser printer called Tectronix (or something like that). The driver is from the manufacturer. When I remove the driver, everything works OK.
>>>>
>>>>Now the hard part....explaining it!
>>>>
>>>>Thanks for the info!
>>>>
>>>Hi Kevin,
>>>
>>>PMFJI, but what's happening is that the printer driver is setting the math co-processor to a state where the calling application (in this case VFP) is expected to handle division by zero. VFP expects the co-processor to take care of it. See Q183522 in the MS Knowledge base for further details.
>>>
>>
>>That said George, would it be difficult for MS to fix the behavior?
>
>Infinitely more difficult than it would be for HP to save and restore the state of the FPU when they receive control, or at least to leave it in a consistant and usable state.

That would seem proper. HP is renowned for their sloppy windows device drivers.