If you are using a newer model
HP LaserJet printer
, such as HP 4000 series or HP 1000 series, you may run into an error which displays ‘Pure Virtual Function Call’. This is caused by newer 32 – bit printer drivers and FoxPro, which is what Power Broker is developed with. As this error is intermittent and does not happened to everyone, there is no definite solution, but
there are some items that can be done to prevent this from happening.
May 15/2002
Here is a link that was found by one of
our techs in relation to a Pure Virtual Function Call solution.
http://www.hp.com/cposupport/printers/support_doc/bpl10995.html
April 8/2002
One of our clients has generously reported that when
downloading drivers from your printer manufactures website, to try downloading
and installing "Postscript" drivers. The Pure Virtual Function Call error
has not shown it's ugly head for the past two weeks since the change was made.
In this example, an HP LaserJet for Windows XP "PostScript Driver" was found.
Do a search for your specific printer make and model to verify if your printer
manufacture has a "PostScript" Driver that will work for you.
Another solution was: If the user
can use an older printer driver (HP 4 for example), this will usually fix the
problem, although they may not get full functionality out of their printer (it
might not recognize paper trays or duplexing units, etc.)
March 15/2002
It has been recently reported that changing the "DPI" settings from 1200 DPI to
600 DPI on your Printer Properties, and also changing your USB port to a simple
Parallel Port has eliminated the Pure Virtual Function Call for this one
customer.
We have NOT
verified this with any other broker
Should you do these changes, and it
works, then please notify our office.
Should it NOT work, then we are
tremendously sorry for any inconvenience.
March 21/2002
It has been recently reported that allowing the Novell Network print spooler to
control the print job rather than allowing the Windows Environment spooler to
take control has eliminated Pure Virtual Function Call.
1. Try to uninstall the Printer driver and reinstall it.
2. Uninstall the printer driver and install the PCL 5E drivers.
3. Uninstall the printer driver and install the HP driver that is in Windows. Example, Laserjet 4+ driver.
4. Try to free up some system resources by following these steps:
- Reboot the computer and try printing again.
- Close any open programs.
- Check the Start-up, Run= and Load= lines in your WIN.INI file for extra applications that may be starting that you do not need, and stop them from automatically starting up at Windows launch.
- Delete temp files in your system.
- Change the Spool Settings to RAW or Print Directly to Printer. (To find Spool Settings, click on Start, Settings, Printers. Right click on your printer icon, and select Properties. Select the Details tab, and click on Spool Settings.)
- Try uninstalling and reinstalling the printer driver.
5. Try to install the Operating System.
6. Check with
www.hp.ca
and see if there are any updated drivers for your printer and install it.
7. We have had some success fixing this error by sitting at the server when doing the Foxfix, Pack and Reindex, Insert Policy Controls (from the Utilities Menu in PB), checking the config.sys, checking the config.fpw, deleting the "M" files, and changing the "Y" to and "N" in the User
Preferences, Define your Company Information, EDI/Misc options. The question asks if you would like to allow users to select printers, yes or no.
8. HP has indicated that should you have the item in a subdirectory that
is too deep, then you may receive a Pure Virtual Function error.
(i.e. C:\temp\this\is\six\deep\test.doc)
The steps in number 7. may be done with the help of a Power Broker Technical Support person.
|
|
