Re: Explorer component
- From: Heidi Linda <heidi.linda@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 24 Jun 2006 16:39:35 +0100
paal.berg@xxxxxxxxxx wrote:
Hi,Is it running as a service? We had a problem with an app that can't print to the default printer because it's a service but which prints just fine to a named printer... then again, that happens in Pro as well I think... or might have been happening under win2k now I think about it...
We have encountered a strange problem for out kiosk that was supposed
to run XPe. We are using our own browser which is basically a .Net
windows application with the Internet Explorer component
(axWebBrowser).
At one of the pages in our web application we must print a receipt. To
avoid printer dialogs we are using an ActiveX component that prints
directly to the default printer without any user interactions. What we
experience is the following:
- Using our browser in XP Pro the page is printed
- Using our browser in XPe the page is not printed
- Going to the page by using the ordinary IE in XPe, the page is
printed
I would really need some advices for how to track down this problem. I
think it quite common to use a custom browser (for e.g. keeping an eye
on the network connection and try to get connected if the net goes
down) and an ActiveX component for printing to avoid the printer
dialogs (does anybody know a way without using an ActiveX?). Should
there be any difference in XPe and XP Pro for our application?
Regards,
Paal
Is the default printer actually behaving as a default printer otherwise? Could it be a security setting difference?
.
- Follow-Ups:
- Re: Explorer component
- From: Paal
- Re: Explorer component
- References:
- Explorer component
- From: paal . berg
- Explorer component
- Prev by Date: "HTML Help Author Message" from XPe SP2 Target Designer component help
- Next by Date: Re: Explorer component
- Previous by thread: Explorer component
- Next by thread: Re: Explorer component
- Index(es):
Relevant Pages
|