Re: new PC Card architecture in CE 5.0

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: bithead (darryln0_at_yahoo.com)
Date: 10/28/04 

Date: 28 Oct 2004 12:22:28 -0700

"Steve Maillet \(eMVP\)" <nospam1@EntelechyConsulting.com> wrote in message news:<#6uwzTPvEHA.3916@TK2MSFTNGP10.phx.gbl>...
> client drivers don't need lots of that. The classes mentioned are for
> implementing the socket controller driver.

Steve,
Just to clarify, I'm not writing a client driver, I'm writing a socket
service DLL for a proprietary BSP.

Is it better/easier to morph my existing, fully tested, fully
functional legacy PCMCIA socket PDD, instead of rewriting using the
bloated MS PCCARD classes?

There are 21K lines of common code, and only about 2K lines of
platform code. Judging by this, using the common code should, in
theory, result in less code maintenance over the long term...assuming
MS' common code works correctly now and in the future, and assuming
that a driver built from it is easily debugged.

The problem is that there is no info on how to use the common code,
other than the samples in the Mainstone and SDK2410 BSPs, which aren't
very heavily commented, plus I don't have either of those boards.

In the CE 5.0 web chat earlier today, MS said they're doing a white
paper on the new PCCARD architecture, with a "how-to" section. Nice,
but I can't wait on that.

Anyone got any advice on this?