Logical Name of Epson printer

Epson provides an Epson ADK for .NET using which we can provide a logical name to the Epson printers. I am printing to the Epson printers using OPOS divers and I have to install the Epson ADK for .NET just so that I can give the printer a logical name. This needs to be done on the client machine as well. The problem is that this ADK is not really meant to be redistributed and moreoever, it is a large installation which further requires that Microsoft Point Of Service be present on the system. This means installing 2 softwares just so that we can give the printer a logical name. Is there any other way to give the printer a logical name? Any pointers would be most welcome.

Thanks in advance, Sankalp

Reply to
Sankalp
Loading thread data ...

Try using Epson's Windows driver. You can find it on the

formatting link
website.

Rob

"Sankalp" wrote:

Reply to
Rob

I have had a look-but basically Epson has not given clear examples on how to use iut. Further, OPOS provides a very powerful way of monitoring the health of the printer. So we want to use OPOS if possible. Its just that this logical name needs to be assigned to the device somehow without using the ADK for .NET. Can anyone help?

Sankalp

Reply to
Sankalp

I think you may have the wrong ADK... It is a pretty large install, but it's self contained - it should not require any additional install packages...

The version I install is at this location:

formatting link
I've used Version 2.4 and 2.5 with and without service packs without issue...

Reply to
Glenn Adams [MVP - Retail Mgmt]

The size of the 2 versions is 13MB, which again is huge considering the fact that we are wasting precious bandwidth downloading some software which just assigns the logical name to the device. How does Epson internally map this logical name to the hardware. Once we set the logical name, we can print to that device using a normal .NET application by using OPOS. There has to be some way Epson does it. Any pointers?

Sankalp

Reply to
Sankalp

It's all in the registry... Look under HKLM/SOFTWARE/OLEforRetail

You should be able to figure out what is happening from there, but you still need the drivers - part of what the registry entries define will be the driver to use when accessing the device...

Reply to
Glenn Adams [MVP - Retail Mgmt]

What's "big" in your terms?

I used OPOSADK250E.EXE, and it works fine at 14MB. You should also look for Service Pack 1 which is 2.5MB. That's small if you ask me, but maybe that's big to you.

David

"Sankalp" wrote:

Reply to
daytraitors

Yes 14MB is big as per me coz we dont burn a CD and give to the customers. We ask them to download the setup from our website. I dont see much user-friendliness in asking the user to first install our company product and then download and install the ADK and before that the Microsoft POS. Anyway, I just want to know what the error means and has someone seen this error previously. If yes, then what are the steps to work around this issue.

Thanks in advance. Sankalp

Reply to
Sankalp

Sankalp,

Just to make things clear, this is NOT the Microsoft Point of Service newsgroup. The newsgroup you are looking for is;

microsoft.public.windows.embedded.pointofservice

This group is a discussion/help/argumentive/yelling and screaming newsgroup for Microsoft's Point of Sale program and Microsoft's Retail Management System, Store Operations and Headquarters programs.

Reply to
Jeff

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.