Hi Virusim,

I don't know anything about your OPOS print driver and may not be of much help. It has been my observation that most of the printer checking functions return a value that seem to indicate that the printer is there and ready all the time. I'm not sure if this is related to the Windows print spooler or not. When sending to a print spooler, the application doesn't even have to know if the printer is ready, online, paper out or not. The applications usually let Windows print engine handle this task and simply send the print output to the print queue. This is very convenient from a programming standpoint.

You might try setting up your printer driver properties to disable print spooling and send output directly to the printer. This might (or might not) make a difference with the return values of the printer checking functions in VFP or API. I really don't know since I always assume spooled print and I haven't had the need to check, but it might be worth a try. Be advised, in previous versions of Foxpro, disabling the print spooler has been known to cause Foxpro to lock up in some instances. I'm not sure if Foxpro overruns the printer or if you would have to put in your own printer checking functions to control output when not spooling print.

HTH




>Hi,
>
>On this issue, I facing the same problem of getting status from the printer.
>This is especially problematic for me since my application is a kiosk application. If only we had some solution to this issue. I be glad and
>save me some sleepless night. I am not getting much help on my OPOS
>driver. If you know anything about it, please advise. Thank you
>