Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Printer.Handle access sometimes blows Win2000 to BSOD

Status
Not open for further replies.

wgcs

Programmer
Mar 31, 2002
2,056
EC
On one Win2k machine accessing a "SHARP AR-337 PCL5e on svr1" printer (it is a network printer that was installed by pointing to the printer share on the print server), my delphi 3 program blows up every time it accesses "Printer.Handle". ( The program runs fine on other Win2k computers that had the printer installed the same way, and even prints without any errors).

I can't trap the error, and windows sometimes gives the "black screen of death".. dumps memory, and immediately reboots. Here's the code:

if Printer.handle=0 {v3.0.7}

So I can't even check if the Handle is Good before doing anything. When I don't get the BSOD/reboot, I get various Memory Access errors at locations in memory like 00000015,00000017,00000034, etc. They seem to repeat in a pattern.. (that is, when you click OK to close one, the next appears, in a pattern, endlessly).

When I'm disconnected from the network (I usually work offsite and am offsite now) I get the exception "EPrinter: Printer Selected Not Valid".

Does anyone who has more experience with network printing have any suggestions on what to do? or even on safer ways to identify whether a printer can be manipulated/printed to before trying to? (all must be done programmatically... the whole purpose of this program is to help print things)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top