Re: Incorporating a 3rd party driver into a BSP/Image

I appologize about my bat/dat confusion. I know that the "File System
Files", referenced in the Platform Builder help article with the same name,
are .dat files. I also pulled the poorly referenced 'source code' from that
article.

I am now able to configure the file system, and by extension get all of my
files where they need to be.

The next step is configuring the registry, then on to making the whole
driver suite actually run as if a CAB had installed it.

Thank you for your patience, I am a terrible internet newbie, and an
entry-level programmer, essentially fresh out of college.

Also, as my fiance keeps telling me, my written skills are abysmal... sorry
to make you all suffer because of them.

Once again, thank you for pointing me in the right direction.

"Bruce Eitman [eMVP]" wrote:

And what sample code worked? I don't recall that we this thread discussed
any sample code, I though we were talking about a the Summit binaries.

Keep in mind that we don't know what you are doing, looking at, working
with... unless you tell us. There is no one size fits all to this.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:eCbJ2dO4HHA.5984@xxxxxxxxxxxxxxxxxxxxxxx
Again with bat files? What bat files? Most of the postmakeimg.bat and
such files don't have any defauilt operations in them. They're available
for you to use, but they don't do anything that Microsoft needs.

Paul T.

"Roger Williamson" <RogerWilliamson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:A7E1427A-ED85-4E55-8C37-6A6CD6C4E236@xxxxxxxxxxxxxxxx
Paul,

I looked at that help file, and nothing in it worked. I've been
pulling
my hair out trying to figure out what type of build I have to do in order
for
the changes I make to the .dat files take effect in the image. I've
tried
sysgen, I've tried make runtime image.

Suddently, to my suprise, I deleted my .bat files, and the example code
worked! I feel like my brain is melting, what just happened has got to
be
impossible.

Also, all the .bat files I've seen are empty (or have a comment from
Microsoft) is that correct what I should expect to see?

Thank you for your help and patience with such a CE newb like me,
Roger

"Paul G. Tobey [eMVP]" wrote:

In the Windows CE 5.0 help, find a page titled "File System File". It
tells
you how to use the platform.dat file to create folders and copy files
from
the \Windows folder at run-time to where you want them to go (it's not a
batch file, AT ALL).

Paul T.

"Bruce Eitman [eMVP]" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OpuwYC43HHA.1900@xxxxxxxxxxxxxxxxxxxxxxx
That is platform.Dat with a D. It happens long before you will need
the
driver.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Roger Williamson" <RogerWilliamson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:61BA5B0D-AAAA-4108-94E1-690C707B73ED@xxxxxxxxxxxxxxxx
I've realized a few issues:
--Which platform.bat file should I be modifying?
--Will the platform.bat execute in time to have a item moved to the
startup
folder and run?

Thanks again,
Roger

"Paul G. Tobey [eMVP]" wrote:

Hang on. It's binary files, right? Put it in platform.bib and
everything
will go into the \Windows folder (that's the only choice and
non-negotiable). If you need to have the files *copied* from
\Windows
to
some other location at run-time, you can do that with entries in the
platform.dat file.

As far as 'making it part of my BSP', I'm not sure what that means
to
you.
You're going to ship this BSP to others for use in creating their
own OS
configurations for your hardware? If not, you can put the entries
for
your
driver into its own catalog item and add/remove them from any OS
configuration, regardless of what BSP it's targeting.

Can we know what WiFi card we're talking about?

Paul T.

"Roger Williamson" <RogerWilliamson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:555E2858-0C80-4490-9E07-E3D14C32A3DE@xxxxxxxxxxxxxxxx
I have a .CAB file which installs a WiFi card driver onto the CE
device
I'm
developing. I've been able to extract out all the binary files,
and
the
registry changes necessary to get the driver up and running, but
I've
run
into a problem.

I don't know how to incorporate a binary-only driver into a BSP
(especially
not one with several components which installs itself across
subdirectories
in the \Windows folder)

Even worse, the word from higher-ups says I have to get rid of the
CAB
support since it is taking up too much space, so I have to
incorporate
this
driver into my image at least, even if it is impossible to make it
part of
the BSP.













.

Relevant Pages

  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... any sample code, I though we were talking about a the Summit binaries. ... folder and run? ... As far as 'making it part of my BSP', I'm not sure what that means ... driver into its own catalog item and add/remove them from any OS ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I looked at that help file, ... folder and run? ... You're going to ship this BSP to others for use in creating their own OS ... driver into its own catalog item and add/remove them from any OS ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I see what my problem was with the extra directories, ... create a folder for them in my release directory in the hope that the folder ... The higher ups at the company want the driver added to the BSP because ... As far as 'making it part of my BSP', I'm not sure what that means to you. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I don't think I'm modifying the right platform .dat file, ... BSP, at least any with an ARM processor in it). ... Since the driver has *no* ... create a folder for them in my release directory in the hope that the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Compiling modified driver
    ... new driver folder to set RELEASETYPE to PLATFORM and TARGETTYPE to DYNLINK. ... and mdd to be compiled if I select my own usb function driver, ... find the result dll to copy it in file system of remote system, ...
    (microsoft.public.windowsce.embedded)