This is a real technical question :
Does the machine code generated by the PB compiler deal with
Exception handling when working with Floating point calculations ?
The reason is, there is a problem with some Printer drivers, in particular
HP drivers.
The following Exception generated by Windows, has something to do
with the Math Coprocessors handling of exceptions with Floating point
code.
10h : Coprocessor Error Fault
I have been researching a problem with a particular Printer driver
being suspect. When I checked out the MSDN web site, there is a lot
of mention of particular Printer Drivers (mostly HP drivers) that
change the Math Coprocessors exception handling , but do not set it
back to the original setting after the driver loaded. This means
that if code is designed to handle the exception handling, the loading
of the HP driver will change how the CPU handles this and the code
will crash.
Microsoft suggests unloading the HP drivers and replacing them
with the closest thing you can find that comes with Windows.
Has anyone experienced strange exception errors when using HP drivers
and could someone tell me if the strange behavior of the HP drivers
would cause a problem for the Floating point code in a PB app ?
Microsoft list a bunch of its own apps that produce the 10h exception
error and they blame it on the HP drivers.
I do know that my HP DeskJet 672C print driver has a serious Resource
leak in it, but this adds more problems if it is so.
------------------
Does the machine code generated by the PB compiler deal with
Exception handling when working with Floating point calculations ?
The reason is, there is a problem with some Printer drivers, in particular
HP drivers.
The following Exception generated by Windows, has something to do
with the Math Coprocessors handling of exceptions with Floating point
code.
10h : Coprocessor Error Fault
I have been researching a problem with a particular Printer driver
being suspect. When I checked out the MSDN web site, there is a lot
of mention of particular Printer Drivers (mostly HP drivers) that
change the Math Coprocessors exception handling , but do not set it
back to the original setting after the driver loaded. This means
that if code is designed to handle the exception handling, the loading
of the HP driver will change how the CPU handles this and the code
will crash.
Microsoft suggests unloading the HP drivers and replacing them
with the closest thing you can find that comes with Windows.
Has anyone experienced strange exception errors when using HP drivers
and could someone tell me if the strange behavior of the HP drivers
would cause a problem for the Floating point code in a PB app ?
Microsoft list a bunch of its own apps that produce the 10h exception
error and they blame it on the HP drivers.
I do know that my HP DeskJet 672C print driver has a serious Resource
leak in it, but this adds more problems if it is so.
------------------
Comment