It seems that I should be able to use WCEUSBSH.sys to communicate from a PC
to a PocketPC over USB, but I can find very little information. I've seen
message that I should be able to use CreateFile on "\\Device\\WCEUSBSH001",
but I can't find any evidence of a device by that name, even using
DeviceTree. Is this the Intel version only? I need to be able to do it
with Microsofts version. How does ActiveSync communicate with the device?

Thanks!

Re: Using WCEUSBSH to communicate over USB by Doug

Doug
Sun May 30 23:10:59 CDT 2004

Hi John,

Have you checked out RAPI ? Easier and includes all ActiveSync
connectivities.

Cheers

Doug Forster

"John Lathem" <lathem@z-space.com> wrote in message
news:%23Rmt3ZpREHA.624@TK2MSFTNGP11.phx.gbl...
> It seems that I should be able to use WCEUSBSH.sys to communicate from a
PC
> to a PocketPC over USB, but I can find very little information. I've seen
> message that I should be able to use CreateFile on
"\\Device\\WCEUSBSH001",
> but I can't find any evidence of a device by that name, even using
> DeviceTree. Is this the Intel version only? I need to be able to do it
> with Microsofts version. How does ActiveSync communicate with the device?
>
> Thanks!
>
>



Re: Using WCEUSBSH to communicate over USB by Nick

Nick
Sun May 30 23:29:07 CDT 2004

This is exactly what I'm trying to do. It's turning out to be real hard. I
do know that the argument you want to pass to CreateFile is
"\\.\WCEUSBSH001". This is the virtual com port exposed by the wceusbsh.sys
usb driver.

nick

"John Lathem" <lathem@z-space.com> wrote in message
news:%23Rmt3ZpREHA.624@TK2MSFTNGP11.phx.gbl...
> It seems that I should be able to use WCEUSBSH.sys to communicate from a
PC
> to a PocketPC over USB, but I can find very little information. I've seen
> message that I should be able to use CreateFile on
"\\Device\\WCEUSBSH001",
> but I can't find any evidence of a device by that name, even using
> DeviceTree. Is this the Intel version only? I need to be able to do it
> with Microsofts version. How does ActiveSync communicate with the device?
>
> Thanks!
>
>



Re: Using WCEUSBSH to communicate over USB by patrox

patrox
Mon May 31 04:08:00 CDT 2004

you need to use CeCreateFile

All the commands starting with "Ce" are for pocket pc connectivity.

pat.



Re: Using WCEUSBSH to communicate over USB by John

John
Mon May 31 15:40:06 CDT 2004

Doug,

Yes, I've used RAPI before, but it requires an ActiveSync connection to be
active. For this application, I need to be able to communicate without an
ActiveSync connection. (Why, you ask? Although these devices are running
PocketPC, they are data collection devices, not PDAs. Customers are
complaining that they have to connect with ActiveSync, establish
partnerships, turn off all the sync, etc. They don't need contacts or
calendars on the shop floor.) However, ActiveSync is the only way I can see
to communicate over USB.

Thanks!

-John

"Doug Forster" <doug at _ZAPTHIS_
toniq_ZAPTHIS_DOT_ZAPTHIS_co_ZAPTHIS_DOTnz> wrote in message
news:uQ5rHVsREHA.3528@TK2MSFTNGP09.phx.gbl...
> Hi John,
>
> Have you checked out RAPI ? Easier and includes all ActiveSync
> connectivities.
>
> Cheers
>
> Doug Forster
>
> "John Lathem" <lathem@z-space.com> wrote in message
> news:%23Rmt3ZpREHA.624@TK2MSFTNGP11.phx.gbl...
> > It seems that I should be able to use WCEUSBSH.sys to communicate from a
> PC
> > to a PocketPC over USB, but I can find very little information. I've
seen
> > message that I should be able to use CreateFile on
> "\\Device\\WCEUSBSH001",
> > but I can't find any evidence of a device by that name, even using
> > DeviceTree. Is this the Intel version only? I need to be able to do it
> > with Microsofts version. How does ActiveSync communicate with the
device?
> >
> > Thanks!
> >
> >
>
>



Re: Using WCEUSBSH to communicate over USB by John

John
Mon May 31 15:41:11 CDT 2004

Nick,

Does your PC expose WCEUSBSH001? I can't find that on mine, even using
DeviceTree.

Thanks!

-John


"Nick" <n a r i n @ v o y a g e r . n e t> wrote in message
news:nwyuc.18572$pt3.1386@attbi_s03...
> This is exactly what I'm trying to do. It's turning out to be real hard.
I
> do know that the argument you want to pass to CreateFile is
> "\\.\WCEUSBSH001". This is the virtual com port exposed by the
wceusbsh.sys
> usb driver.
>
> nick
>
> "John Lathem" <lathem@z-space.com> wrote in message
> news:%23Rmt3ZpREHA.624@TK2MSFTNGP11.phx.gbl...
> > It seems that I should be able to use WCEUSBSH.sys to communicate from a
> PC
> > to a PocketPC over USB, but I can find very little information. I've
seen
> > message that I should be able to use CreateFile on
> "\\Device\\WCEUSBSH001",
> > but I can't find any evidence of a device by that name, even using
> > DeviceTree. Is this the Intel version only? I need to be able to do it
> > with Microsofts version. How does ActiveSync communicate with the
device?
> >
> > Thanks!
> >
> >
>
>



Re: Using WCEUSBSH to communicate over USB by John

John
Mon May 31 15:42:41 CDT 2004

pat,

Doesn't this require an ActiveSync connection to be already established for
RAPI to work? I need to do it without the ActiveSync connection.

Thanks!


"patrox" <misterbanned@hotmail.com> wrote in message
news:40baf3db$0$308$7a628cd7@news.club-internet.fr...
> you need to use CeCreateFile
>
> All the commands starting with "Ce" are for pocket pc connectivity.
>
> pat.
>
>



Re: Using WCEUSBSH to communicate over USB by hel

hel
Mon May 31 16:48:51 CDT 2004

>However, ActiveSync is the only way I can see
>to communicate over USB.

It can be done without activesync. I did it a couple of years
ago as an experiment, but passthrough came in AS 3.5 (think
it was 3.5, w/PPC 2002) and I dropped it once I discovered that.

First, the usb serial port from the wceusbsh thing went the way
of the dodo in AS31. Only AS gets to use it (and AS has to
be off for my way to work). Like somebody wrote, that serial
device isn't even exposed anymore (there was a AS 3.1 doc that
mentioned using that exposed device, I think).

The PPC side was a serial setup, and so limited the max possible
speed due to the small buffer size allowed (I think the buffer
was allowed to reach maybe 4 KB, with linear rate increases as
the buffer was enlarged up to the 4 KB, after which it didn't
accept larger sizes). I topped out at about 0.23 MB/sec while
AS pass-through was getting a good 0.33 MB/s (that's MB, as in
1024*1024 bytes). That's once it gets going; using short blocks
would drop that rate down to much less since USB has huge startup
costs.

On the PC side you need to register with some USB thing so you
can get connection notifications, and that's where the boys get
separate from the men (as far as robust implementations goes).

Unfortunately, that's all I can tell you because that goes back
two years and I don't have any code from two years ago within
arm's reach.


>> "\\Device\\WCEUSBSH001",

Whoops! Power failure. Gots to go.
--
40th Floor - Software @ http://40th.com/
iPlay : the ultimate audio player for iPAQs
mp3, ogg, mp4, m4a, aac, wav, and then some