Re: "No .rel file found for module "

So do a debug build, then copy dev*.* from the debug release dir to the
retail release dir.

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

"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:41504E8E-7C63-4C05-B98A-48AFE024B8D2@xxxxxxxxxxxxxxxx
That is what I would like to do. The problem is, a debug build is too
large
and gives an error that it overlaps the rom area. Also, with the source
code, I have not been able to get it in a fashion so that it will allow me
to
step through it. The source is from Freescale's BSP, and I am using a
different BSP and trying to integrate a driver from freescale. So while I
have the source, I've only been able to integrate the driver as a
stand-alone
DLL, and even then not successfully (as mentioned in my first post on this
thread).





"Dean Ramsier" wrote:

Have you done a debug build? That may tell you what device.exe doesn't
like
about your dll, assuming it has gotten far enough to attempt to load it.

You said you also have source? Use that to set a breakpoint in the init
code and step through the loading process.
--
Dean Ramsier - eMVP
BSQUARE Corporation


"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1DEFDB2D-A4E5-470D-8D16-A3B6509B5A7A@xxxxxxxxxxxxxxxx
Thanks. I did see the information on the web, but nothing gives a real
good
explanation for certain of what the problem is.

I thought maybe it was the registry data too, but it is pretty basic:

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\I2C]
"Prefix"="I2C"
"Dll"="i2c.dll"
"Index"=dword:1
"Order"=dword:30

The driver is straight from freescale and is supposedly good, looking
at
the
source it looks pretty straight-forward.

For my call to ActivateDeviceEx, I simply passed the dll name and then
zeros
for the rest. I would prefer to not even have to make the call though,
I
would prefer the OS loads it automatically. It appears to be trying to
(there is a gap in the number sequence of "Active" in the registry when
this
device is present, but it never actually gets loaded.

Any other ideas or clues as to what I can look at?


"Bruce Eitman [eMVP]" wrote:

A quick google groups search would give you tell you about that
message.

http://groups.google.com/groups?as_q=No+.rel+file+found+for+module&num=10&scoring=r&hl=en&as_epq=&as_oq=&as_eq=&as_ugroup=microsoft.public.windowsce.*&as_usubject=&as_uauthors=&lr=&as_drrb=q&as_qdr=&as_mind=1&as_minm=1&as_miny=1981&as_maxd=28&as_maxm=1&as_maxy=2008&safe=off

So since that information is available, I will give you the short
answer.
That is not the problem. The problem is probably the information in
the
registry, if we assume that the driver is good then it could also be
your
code for ActivateDeviceEx. Have you contacted the vendor?

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

"AD" <AD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E0A51B6C-6EEE-42F1-80BE-C062128197E7@xxxxxxxxxxxxxxxx
I am trying to build a platform with a new driver file for which I
only
have
the binary. I created a CEC file and all and was able to get the
driver
added to the registry in the "builtin" folder, but cannot get
WindowsCE
(5.0)
to load the driver and place it in "Active". I tried doing it
manually
with
a call to "ActivateDeviceEx", and get a return of 1610 (bad
configuration).

Going back through my platform builder warnings, I found one that
says
"No
.rel file found for module i2c.dll", which is the driver I'm having
problems
with.

Does anyone know what this means and how to fix it?

Thanks in advance for any suggestions.

Adam








.

Relevant Pages

  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... because my IT department is paranoid about what they let us install. ... You may want to look for a tool to get the registry out of the CAB file. ... beitman AT applieddata DOT net ... driver suite actually run as if a CAB had installed it. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: "No .rel file found for module "
    ... Do you have the debug output from loading with KITL enabled? ... Bruce Eitman (eMVP) ... I2C driver when it is launched through KITL. ... I thought maybe it was the registry data too, ...
    (microsoft.public.windowsce.app.development)
  • Re: how to load in a build in driver whose index is greater 10 in Windows CE
    ... about the fact that numbers in the registry files are all hexadecimal, ... You must use the $device mount point to reference such a driver. ... Bruce Eitman [eMVP] wrote: ... But I likt this VCA12 as a build in driver, which will be load when the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Incorporating a 3rd party driver into a BSP/Image
    ... You may want to look for a tool to get the registry out of the CAB file. ... beitman AT applieddata DOT net ... driver suite actually run as if a CAB had installed it. ... You're going to ship this BSP to others for use in creating their ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Problem with COM-Port after switching from Hive Based Registry -> RAM based
    ... Michel Verhagen, eMVP ... driver load order can change. ... "Order" values to the driver registry settings. ...
    (microsoft.public.windowsce.platbuilder)
Loading