|
Posted by Manas on May 1, 2008, 10:24 pm
Please log in for more thread options Hi Raj,
We are the medica device manufacturer and the driver is developed by
me. I have installed the driver on to Flame, that involves some registry
settings and placing the driver dll into the \windows folder. I don't know
how does this matters with activesync because the device works fine with
flame, but once we connect with active sync, and then conncet back the
devices, it fails. thr is no other option than to reset flame.
"Raj Pillai" wrote:
> Hi Manas,
>
> My guess would be as good as yours. Have you tried contacting the medical
> device manufacturer support? They might be able to give you better
> information about this behavior.
>
> --
> Regards,
> Raj Pillai
> Microsoft MVP - Mobile Devices
> http://www.pocketpcfaq.com/raj
>
>
>
> > Hi Raj,
> > Thanx for the reply. That did not work. The issue still remains. Is
> > it something to do with security? The driver that I installed on Flame is
> > not
> > signed. My guess is on certificate sign because, I have noticed this
> > problem
> > in another situation. If I keep the medical device connected to Flame and
> > reset Flame. After it boots up, I see the same "Unidentified devcie"
> > message.
> > But if I unplug and plug in the cable, it identifies. Can u derive some
> > clue
> > from that.
> > rgds,
> > Manas.
> >
> > "Raj Pillai" wrote:
> >
> >> Hi Manas,
> >>
> >> Not sure what might be causing this issue but I would suggest you to
> >> close
> >> ActiveSync in memory of the device (Tap Start -> Settings -> System
> >> tab ->
> >> Memory -> Running Program) and then connect your medical device. See if
> >> that
> >> helps.
> >>
> >> --
> >> Regards,
> >> Raj Pillai
> >> Microsoft MVP - Mobile Devices
> >> http://www.pocketpcfaq.com/raj
> >>
> >>
> >>
> >> > Hi,
> >> > I have installed an USB driver for our medical device device, on
> >> > O2
> >> > Flame (running WM 5). So now when I connect the medical device to the
> >> > O2
> >> > Flame (OTG mini-A i.e. Flame as host), the medical device gets
> >> > identified
> >> > and
> >> > the driver loads fine. And all the communication works fine.
> >> > But there are some problems:
> >> > If I connect the O2 Flame with the PC through ActiveSync for syncing
> >> > some
> >> > other files. Then I connect back the Flame to the device, Flame fails
> >> > to
> >> > identify the device and prompts for the driver dll ("Unidentified
> >> > devcie").
> >> > Whereas the device was working fine with Flame before I connect Flame
> >> > to
> >> > PC
> >> > over ActiveSync.
> >> > Have anyone faced any problem like this. Surprisingly, in case of a
> >> > mass
> >> > storage connecting to Flame, there isn't any such problem. I don't
> >> > understand
> >> > why it has the problem with my driver, while it works fine in all other
> >> > situation.
> >> > Can someone please help.
> >> > Thanks
> >> > Manas
> >>
> >>
>
>
| 
XML Sitemap