Re: Compiling modified driver

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

As Paul pointed out earlier, don't modify files in the Public folder, so
don't modify common.reg.

You have a project.reg for that kind of registry setting.

--
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

"Shahrad" <shahradp@xxxxxxxxx> wrote in message
news:bHRVi.162689$th2.61863@xxxxxxxxxxxx
Thanks Paul,

Make it works with adding necessary libraries to SOURCES for subproject
and
also setting the SYSGEN flag for tranciever driver in projectsysgen.bat
for
project.
One more thing that need to be added, is to put registery information for
new function driver in common.reg with appropriate flag.

Regards,
Shahrad

"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news:eAe2Jw0GIHA.280@xxxxxxxxxxxxxxxxxxxxxxx
Now you need to know a little about how the build system builds stuff in
PUBLIC.

Almost everything in public is built in two stages: actually building it
based on the SOURCES files that you have in each directory, resulting in
a
library (TARGETTYPE=LIBRARY), and creating the final target type using
cesysgen.mak.

So, to capture the bits that get set during the sysgen step, you need to
use
sysgen_capture, which will generate for you a SOURCES.<component name>
file.
You can either follow the help for sysgen_capture, or I'll try to
indicate
what you need to do here.

1. Open a build MS-DOS window using the Open Release Directory menu item
from PB/VS2005.

2. Navigate to the new folder you've created for your modified driver.

3. Run something like the following:

sysgen_capture -p common <original driver name>

For example, I just did this for the FATUTIL component because I have to
change some of the resources to fit on our screen.

sysgen_capture -p common fatutil

The result, for me, was a file called SOURCES.FATUTIL, which contained
the
SOURCELIBS, TARGETLIBS, etc. settings that are needed to actually build
FATUTIL.DLL. You should be able to get something similar, from which
you'll
want to grab the SOURCELIBS and TARGETLIBS settings and copy those to
your
actual SOURCES file.

Paul T.

"Shahrad" <shahradp@xxxxxxxxx> wrote in message
news:%LOVi.161235$1y4.94739@xxxxxxxxxxxx
Thanks for reply,
While compiling seperate usb function driver as a subproject (as you
said
by just moving a copy of driver to subproject area), got unresolved
function
on different layers (like CloseBusAccessHandle function ....). So what
library or setting in the project I missed?

Shawn,
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT
com> wrote in message news:u8p$SnzGIHA.6068@xxxxxxxxxxxxxxxxxxxxxxx
You don't have to link with or include anything that the original
driver
didn't have to, so all you need to do is assure that the pointers to
the
right folders are there. You should be able to, if your directory
layout
is
somewhat standard, add the folder for this thing to
\platform\<xyz>\drivers\<this driver's name>, and add <this driver's
name>
to the list of directories to be built in
\platform\<xyz>\drivers\dirs.
Initially, all you should have to try changing is the SOURCES file in
the
new driver folder to set RELEASETYPE to PLATFORM and TARGETTYPE to
DYNLINK.
Right now, those two variables probably are not set in SOURCES...

Paul T.

"Shahrad" <shahradp@xxxxxxxxx> wrote in message
news:u_MVi.159835$Da.106076@xxxxxxxxxxxx
ok, but two more questions,

Using it as a subproject need to make somehow the flags for usb
tranciever
and mdd to be compiled if I select my own usb function driver, so
how
can
I
do that?
and also need to using related ddk librariees, right? If yes, then
could
you
point out which and how?

Thanks,
Shawn
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no
spam
DOT
com> wrote in message news:up0mzHzGIHA.1548@xxxxxxxxxxxxxxxxxxxxxxx
Don't modify files in the PUBLIC subdirectories. If you check the
archives
of the Platform Builder newsgroup,
microsoft.public.windowsce.platbuilder,
you'll find that over and over and over. If you move a copy of the
driver
to your platform directory, changing and rebuilding the driver will
be
very
easy.

Paul T.

"Shahrad" <shahrad@xxxxxxxxxxx> wrote in message
news:L7MVi.159772$Da.65451@xxxxxxxxxxxx
Hello,

After modifying a driver in usb function category and build it,
where
can
I
find the result dll to copy it in file system of remote system,
instead
of
do SYSGEN again to let platform builder update it? The second way
takes
long
and want shortest way.

Thanks for any help,

Shawn
















.

Relevant Pages

  • Re: Unable to load stream interface driver
    ... And specify it in the registry if it is different from the default. ... Interface Drivers, ie. export Stream Interface Driver functions. ... Here is what my modified sources file looks like (Note. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Unable to load stream interface driver
    ... Can you connect the remote registry editor and check if your registry settings are *really* in the device? ... I added your suggestions to my sources file, but I still don't see my driver loaded. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Compiling modified driver
    ... HIVE BOOT REGISTRY, or something? ... Paul T. ... If I put it in project.reg, usbfn mdd cannot find the function driver ... all you should have to try changing is the SOURCES file ...
    (microsoft.public.windowsce.embedded)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... I got the registry entries by opening the CAB file with WinCE CAB Manager. ... Paul T. ... driver suite actually run as if a CAB had installed it. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: NIC fails in RELEASE build CE 5.0
    ... Paul T. ... When the driver called InterruptInitialize(), ... changing in the registry might be telling the driver which of the chip ...
    (microsoft.public.windowsce.platbuilder)