Discussion:
x64 opos drivers
(too old to reply)
e***@go.com
2009-02-02 19:58:59 UTC
Permalink
Surprisingly, I have not seen this issue discussed anywhere else.
Hopefully someone has some experience here.

With a x64 client, is it even possible to use legacy OPOS service
objects? As far as I can tell, to run an application with legacy OPOS
service objects at all, one would need to use WOW64. An even then
compatibility is questionable...

Which leads me to my next point. Does Microsoft or anyone else have
plans to write a WePOS service object for a pinpad. If not, this
could spell trouble for anyone attempting to migrate to x64 systems.
Sylvester La Blanc MSFT
2009-02-17 04:13:49 UTC
Permalink
In article
Post by e***@go.com
Surprisingly, I have not seen this issue discussed anywhere else.
Hopefully someone has some experience here.
With a x64 client, is it even possible to use legacy OPOS service
objects? As far as I can tell, to run an application with legacy OPOS
service objects at all, one would need to use WOW64. An even then
compatibility is questionable...
Which leads me to my next point. Does Microsoft or anyone else have
plans to write a WePOS service object for a pinpad. If not, this
could spell trouble for anyone attempting to migrate to x64 systems.
OPOS is not compatible with 64 bit applications on x64 platforms, but
can be used by 32 bit applications (using WOW) on x64 systems.

POS for .NET is compatible with both 64 and 32 bit applications on x64
platforms. If running the app as 32-bit you can also use the legacy
OPOS service objects. When running as 64 bit application, you must use
native .NET service objects, and these service objects must not rely on
any 32 bit technology.

- Sylvester
--
This posting is provided "As Is" with no warranties, and confers no rights.
X-Face: 3bv|Grp$j"BCYpET|y@@/5=;***@Zuc[XSbP7Ui8#`J0J|PX0c!m9=]McR9PPq
\TvMOAvJUes)hkN;<}cLH#}@F~*t`[>9@,;4`@OEs?BpPKrJ+x.E{1i.AEbJ6ul-~X/1
6Hqa0bJ4m]?***@j?dy.l_=|b[iZjr>!x:P_&p"[OI@^'^-U[^6FHdTI5~"Ak[Vp%?ba?/
CcQZS+nKY[D!H~08:[_F8^I{%c#yh8;#u7$m0^dZ3DOr=6=!*`"(z3%$HUBVFlfAn4H0
\<f:HYfWP:g<P:3gp?6d,ge~y
Sylvester La Blanc MSFT
2009-02-17 04:18:23 UTC
Permalink
In article
Post by e***@go.com
Surprisingly, I have not seen this issue discussed anywhere else.
Hopefully someone has some experience here.
With a x64 client, is it even possible to use legacy OPOS service
objects? As far as I can tell, to run an application with legacy OPOS
service objects at all, one would need to use WOW64. An even then
compatibility is questionable...
Which leads me to my next point. Does Microsoft or anyone else have
plans to write a WePOS service object for a pinpad. If not, this
could spell trouble for anyone attempting to migrate to x64 systems.
For more info on POS for .NET support on 64-bit editions of Microsoft
Windows Operating Systems, see KB#959944:

http://support.microsoft.com/kb/959944

- Sylvester
--
This posting is provided "As Is" with no warranties, and confers no rights.
X-Face: 3bv|Grp$j"BCYpET|y@@/5=;***@Zuc[XSbP7Ui8#`J0J|PX0c!m9=]McR9PPq
\TvMOAvJUes)hkN;<}cLH#}@F~*t`[>9@,;4`@OEs?BpPKrJ+x.E{1i.AEbJ6ul-~X/1
6Hqa0bJ4m]?***@j?dy.l_=|b[iZjr>!x:P_&p"[OI@^'^-U[^6FHdTI5~"Ak[Vp%?ba?/
CcQZS+nKY[D!H~08:[_F8^I{%c#yh8;#u7$m0^dZ3DOr=6=!*`"(z3%$HUBVFlfAn4H0
\<f:HYfWP:g<P:3gp?6d,ge~y
Loading...