POS for .NET and Epson OPOS

[Jeff Oakes]

We're using VS2008 SP1 on Vista SP1.
We have on a clean machine Epson OPOS for .NET 1.11.3 (tried .1 and .2 as
well)

I've created a logical device name for an Epson TM-T90 using Epson's setup
utility.
Epson's Check Health utility works fine.

When we run the sample app that is included with MS POS for .NET - we can
see the printer and its logical device name.

Use the source code for the same MS sample app, we get no printers listed
with logical names.

Using our own code - same problem.

It appears only pre-compiled applications can see these logical names. Of
course those apps were probably pre-compiled on VS2005 or pre SP1 VS2008.

All of these source versions worked fine prior to SP1 for VS2008 or SP1 for
Vista or SP1 for .NET Framework 3.5.

Any ideas? We cannot continue development as we can no longer see devices.

Thanks!
- Jeff

[Sylvester La Blanc MSFT]

Post by Jeff Oakes
We're using VS2008 SP1 on Vista SP1.
We have on a clean machine Epson OPOS for .NET 1.11.3 (tried .1 and .2 as
well)
I've created a logical device name for an Epson TM-T90 using Epson's setup
utility.
Epson's Check Health utility works fine.
When we run the sample app that is included with MS POS for .NET - we can
see the printer and its logical device name.
Use the source code for the same MS sample app, we get no printers listed
with logical names.
Using our own code - same problem.
It appears only pre-compiled applications can see these logical names. Of
course those apps were probably pre-compiled on VS2005 or pre SP1 VS2008.
All of these source versions worked fine prior to SP1 for VS2008 or SP1 for
Vista or SP1 for .NET Framework 3.5.
Any ideas? We cannot continue development as we can no longer see devices.
Thanks!
- Jeff

If the Sample Application is able to see the printer then you should be
able to as well.

Are you asking the POSExplorer to return a list of all available
printers or are you asking for the specific printer by name? Try asking
for a list and see if the printer in question is returned. If asking by
name, perhaps the name is not an exact match.

Hope this helps,

- Sylvester

[Horst Gassner]

Hello Jeff!

Same problem here. We are using an EPSON display device (DM-D210) and we
have no chance to get a connection using VS 2008.

I have compiled the sample provided by EPSON (1st Step for LineDisplay, the
very simple one which only connects to display and displays a line of text)
and it worked fine when using VS 2005 to compile. Compiling _the exactly
same_ sample code using VS 2008 leads to an error when trying to get the
deviceInfo (deviceInfo =
posExplorer.GetDevice(DeviceType.LineDisplay,strLogicalName);).

I also have tried to compile against .NET framework 2.0 and 3.5 - no change
- did not work.

Do you already have a solution for your problem, Jeff? I think we do have
exactly the same problem...

Thanx
Horst

[Horst Gassner]

Perhaps interesting news regarding this topic.

Just compiled the MS POS Sample Application using VS 2008 on a VISTA and on
a XP machine. Tested two devices - an EPSON DM-D210 line display and a HP
scanner.

Result using MS POS Sample Application:
# EPSON display works only on the XP machine
# HP scanner works on VISTA & XP machine

Our summary: we think that the problem is the driver of the EPSON display.
We are using OPSN V1.11.3.

Horst

[Sylvester La Blanc MSFT]

Post by Horst Gassner
Perhaps interesting news regarding this topic.
Just compiled the MS POS Sample Application using VS 2008 on a VISTA and on
a XP machine. Tested two devices - an EPSON DM-D210 line display and a HP
scanner.
# EPSON display works only on the XP machine
# HP scanner works on VISTA & XP machine
Our summary: we think that the problem is the driver of the EPSON display.
We are using OPSN V1.11.3.
Horst

I'll try to remember to test this out next week at work. If I forget,
you can send an e-mail to the POS for .NET team blog and mention this
issue to remind me. :-)

-- Sylvester

[Horst Gassner]

*reminder for Silvester* :-)

[Jeff Oakes]

As it turns out, there is a permissions problem in Windows Vista!

Epson/Microsoft found this out for me.

You have to use an XP machine to create the file using Epson's Setup
utility. Then copy that file over to Vista to use.

Once the file exists on the Vista machine it can be edited as usual. Just
can't be created from Vista to begin with!

[sd582]

Hi

I'm a colleague of Horst and at work on this problem now.
In beetween, I'm working on Windows7, having the same problem.

Post by Jeff Oakes
Epson/Microsoft found this out for me.
You have to use an XP machine to create the file using Epson's Setup
utility. Then copy that file over to Vista to use.
Once the file exists on the Vista machine it can be edited as usual. Just
can't be created from Vista to begin with!

Do you have any idea, which file are supposed here?

thanking you in anticipation

Franz

[sd582]

Hi

Now, I have found a better solution for this problem!

I have simply start Epson.opos.tm.setpos.exe elevated! And after
configuration is saved, it needs a shutdown/restart. Afterwards it works fine.

Regards,
Franz