bb.donnay-software.com

Have a user added a new work station Every time he tries to print the program closes.


The xppfatal says os: 87: xpp40. windows 7 usually shows os: 0

the error is:

File: O:\oisbrokr\OPMENU.EXE
TimeStamp: 20130214 10:42
End of FATAL ERROR LOG.
FATAL ERROR LOG
System-Error
SYS Thread-ID: 1716
Module: MOM
Error Codes: EH: 4 Sub: 87(57) OS: 87 XPP: 40
Call Stack of Thread 1 (596):
@DC_GETLIST@I@EVENTLOOP(3917)
@DC_GETLIST@I@READGUI(3647)
DC_READGUI(103)
MAIN(2799)
Call Stack of GUI Thread (816):
Call Stack of Thread 3 (1716):
DC_PRINTERDIALOG(3005)
@DC_PRINTER@I@INIT(169)
DC_PRINTERON(3536)
PRINTJOB(220)
STRUN2(205)
(B)(B)MAIN@0250(1810)
File: O:\oisbrokr\OPMENU.EXE
TimeStamp: 20130214 10:50
End of FATAL ERROR LOG.

So all that is from Express, but maybe somebody has seen this occur before. They say its our fault..they have 20 other work stations that are fine..just this one.

Any idea??

Fred
Omni

Roger,

I see that the line is aList := oPrinter:List(). How can that cause alaska to just close? They are saying when this happens all printers are deleted from windows and have to be re-added. (I wonder if its the operating system. Waiting to hear back from them on what is is..is there an issue with new Windows 8?
I have not installed it here yet.

Fred

What happens if you run just a one line program?

wtf XbpPrinter():new():list()

This should return an array in the debug window.

I do not have access to his computer. I did have him send his printer list from windows and it shows 14 printers. Is the number a problem, or do you think its a name?
I guess I can give him a separate exe to run a test, but I do not think he is keen on having 14 printers deleted and have to reinstall them again.

Any other suggestions? Maybe doing an alert on every one until it stops or crashes?

Fred

omni wrote:They are saying when this happens all printers are deleted from windows and have to be re-added. (I wonder if its the operating system. Waiting to hear back from them on what is is..is there an issue with new Windows 8?

which Printer Driver they try to use ? i recommend to use ONLY Win8 Driver !
i did try to install a "old" PDF Printer Driver which wanted to install something in \SYSTEM32\SPOOL ...


Question : did we talk about Network or local Printer ?

Network Printer most have some Printer "Tools" ... if you have many Network Printer with many "Tools" they might hurt "other" ...

if you have access to "the" Printer where "your" Xbase++ Application work on try use a "fix IP" and install IP "as local Printer" (!) not using Printer Client Software but Win8 Driver. these Win8 Driver might have not all Property you need ... but they are stable !!!

Auge_Ohr wrote:

omni wrote: i did try to install a "old" PDF Printer Driver which wanted to install something in \SYSTEM32\SPOOL ...

If this is win2pdf, they have a windows 8 version. their earlier versions do not work on windows 8. We just hit this with a client of ours. In fact, their current non-windows 8 version doesn't work properly with windows 7!! We've had to use a much older version in w7.

Brian

Recompile all DLL and EXE ARC

I think I need to clarify the problem.

Client has 14 printers/spoolers. Most or all are network. He can print anything from other software. When he attempts to do a regular forced printjob, not using his default printer or prchoice, the system locks up. Based on error logs its when the printer array list is attempted to be created for him to select his printer.

Hope that clears it up.

(ie, is there something in _dcprc that actually deletes printer names. Appears there is, but not sure. And what does " oPrinter:status() # 1"?)

Could one bad name or resource cause the erase name to start?

Thanks

Fred

omni wrote:Client has 14 printers/spoolers.
...
they have 20 other work stations that are fine..just this one.

does other Client also have so many Printer installed ?

omni wrote:in _dcprc ...

hm does XbpPrinter():New() have a Parameter "cFilename" ?
just try this Code on "that" Client PC