OPOS DRIVER - to starting

I am in a project that aims to build a opos driver, a species of intermediary
between application and opos devices that support the standard. The opos
driver is divided in two parts: The Control Object(CO), that makes the
interface with application and the Service Object(SO), that makes the
interface with the devices. The CO makes methods calls in the SO.
My problem is the following one: The CO are ActiveX controls(ocx) and SO are
dlls. I am not knowing that type of project I must create in the Visaul c++
and how do I link the CO and the SO? I need them( ocx and dll) will be
invisible at runtime. I would like that somebody help about that. Somekind of
help is welcome. I wait reply! Grateful! Helio

P.S.: for more information about opos standard "monroecs.com/opos.htm"

Hi OPOS
there's a new NG... microsoft.public.windows.embedded.pointofservice It's
for WEPoS, and SO/CO type questions... WEPoS is built on UPOS 1.8
(combination of OPOS and JPOS) and uses a MS SDK called POS for .NET...
excellent stuff, like full PnP for POS peripherals and such... I would post
the question there, or contact me OL and I can point you in the right
direction.

HTH,
JC

--
John Coyne
Windows XP Embedded Black Belt
Windows CE Black Belt
Arrow Electronics, OCS division
When replying directly to this message remove the NOSPAM_ from the address




"OPOS DRIVER" <OPOSDRIVER@discussions.microsoft.com> wrote in message
news:08924A05-0A6D-4880-B541-DA08A5B7AE76@microsoft.com...
>I am in a project that aims to build a opos driver, a species of
>intermediary
> between application and opos devices that support the standard. The opos
> driver is divided in two parts: The Control Object(CO), that makes the
> interface with application and the Service Object(SO), that makes the
> interface with the devices. The CO makes methods calls in the SO.
> My problem is the following one: The CO are ActiveX controls(ocx) and SO
> are
> dlls. I am not knowing that type of project I must create in the Visaul
> c++
> and how do I link the CO and the SO? I need them( ocx and dll) will be
> invisible at runtime. I would like that somebody help about that. Somekind
> of
> help is welcome. I wait reply! Grateful! Helio
>
> P.S.: for more information about opos standard "monroecs.com/opos.htm"