Problem to load Stream Drivers in release configuration

I've developped a Stream Driver. Everything looks fine in Debug Configuration
and works pretty well on my Device. Then I sysgen My OS + My Driver in
RELEASE Configuration. I run it on my Device,.In this case My driver is not
loaded by The Device Manager. I cannot figure out why, I checked registry
key, exported functions...I cannot figure out why it works in debug and not
in release.

Any clues.

Nat

Bruce
Wed Oct 31 10:43:24 PDT 2007

Is the driver actually on the device? Is the driver failing becuase of
variable initialization, that is handled better with a debug build?

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

"Nat" <Nat@discussions.microsoft.com> wrote in message
news:5B5775C7-7277-42C5-8A7C-7C4921765C5E@microsoft.com...
> I've developped a Stream Driver. Everything looks fine in Debug
> Configuration
> and works pretty well on my Device. Then I sysgen My OS + My Driver in
> RELEASE Configuration. I run it on my Device,.In this case My driver is
> not
> loaded by The Device Manager. I cannot figure out why, I checked registry
> key, exported functions...I cannot figure out why it works in debug and
> not
> in release.
>
> Any clues.
>
> Nat

Nat
Wed Oct 31 11:28:01 PDT 2007

Yes, the driver is on the device. I checked the registry: I can see it in the
<built in>, but not in the <active>.
What kind of variables could bring the driver to fail?

Nat.


"Bruce Eitman [eMVP]" wrote:

> Is the driver actually on the device? Is the driver failing becuase of
> variable initialization, that is handled better with a debug build?
>
> --
> 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
>
> "Nat" <Nat@discussions.microsoft.com> wrote in message
> news:5B5775C7-7277-42C5-8A7C-7C4921765C5E@microsoft.com...
> > I've developped a Stream Driver. Everything looks fine in Debug
> > Configuration
> > and works pretty well on my Device. Then I sysgen My OS + My Driver in
> > RELEASE Configuration. I run it on my Device,.In this case My driver is
> > not
> > loaded by The Device Manager. I cannot figure out why, I checked registry
> > key, exported functions...I cannot figure out why it works in debug and
> > not
> > in release.
> >
> > Any clues.
> >
> > Nat
>
>
>

voidcoder
Wed Oct 31 11:37:17 PDT 2007


Make sure the binary itself (the .DLL) is on the device.
In debug mode KITL is usually turned on so that the KD
can pick up the DLL at runtime from the release dir...

--
Oleg


Nat wrote:
> Yes, the driver is on the device. I checked the registry: I can see it in the
> <built in>, but not in the <active>.
> What kind of variables could bring the driver to fail?
>
> Nat.
>
>
> "Bruce Eitman [eMVP]" wrote:
>
>> Is the driver actually on the device? Is the driver failing becuase of
>> variable initialization, that is handled better with a debug build?
>>
>> --
>> 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
>>
>> "Nat" <Nat@discussions.microsoft.com> wrote in message
>> news:5B5775C7-7277-42C5-8A7C-7C4921765C5E@microsoft.com...
>>> I've developped a Stream Driver. Everything looks fine in Debug
>>> Configuration
>>> and works pretty well on my Device. Then I sysgen My OS + My Driver in
>>> RELEASE Configuration. I run it on my Device,.In this case My driver is
>>> not
>>> loaded by The Device Manager. I cannot figure out why, I checked registry
>>> key, exported functions...I cannot figure out why it works in debug and
>>> not
>>> in release.
>>>
>>> Any clues.
>>>
>>> Nat
>>
>>

Bruce
Wed Oct 31 13:04:01 PDT 2007

Having a registry setting for the driver and having the driver actually be
on the device are two different things altogether.

Is the driver on the device?

> What kind of variables could bring the driver to fail?
Any variable that you did not initialize, but instead assume an initial
state which was valid with a debug build and not valid with a retail build.

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

"Nat" <Nat@discussions.microsoft.com> wrote in message
news:38E24505-9E99-47E8-84A2-8629EF325E80@microsoft.com...
> Yes, the driver is on the device. I checked the registry: I can see it in
> the
> <built in>, but not in the <active>.
> What kind of variables could bring the driver to fail?
>
> Nat.
>
>
> "Bruce Eitman [eMVP]" wrote:
>
>> Is the driver actually on the device? Is the driver failing becuase of
>> variable initialization, that is handled better with a debug build?
>>
>> --
>> 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
>>
>> "Nat" <Nat@discussions.microsoft.com> wrote in message
>> news:5B5775C7-7277-42C5-8A7C-7C4921765C5E@microsoft.com...
>> > I've developped a Stream Driver. Everything looks fine in Debug
>> > Configuration
>> > and works pretty well on my Device. Then I sysgen My OS + My Driver in
>> > RELEASE Configuration. I run it on my Device,.In this case My driver
>> > is
>> > not
>> > loaded by The Device Manager. I cannot figure out why, I checked
>> > registry
>> > key, exported functions...I cannot figure out why it works in debug and
>> > not
>> > in release.
>> >
>> > Any clues.
>> >
>> > Nat
>>
>>
>>

Nat
Wed Oct 31 13:42:01 PDT 2007

You're right: the DLL was not on the device because of an error in the
Driver.bib file. I did not specify MODULES at the top of the file. Since it
was the first line of the pbUserProjects.bib, the Dll was not transfered to
the windows Directory.

Thank you for your help.
Nat


"voidcoder" wrote:

>
> Make sure the binary itself (the .DLL) is on the device.
> In debug mode KITL is usually turned on so that the KD
> can pick up the DLL at runtime from the release dir...
>
> --
> Oleg
>
>
> Nat wrote:
> > Yes, the driver is on the device. I checked the registry: I can see it in the
> > <built in>, but not in the <active>.
> > What kind of variables could bring the driver to fail?
> >
> > Nat.
> >
> >
> > "Bruce Eitman [eMVP]" wrote:
> >
> >> Is the driver actually on the device? Is the driver failing becuase of
> >> variable initialization, that is handled better with a debug build?
> >>
> >> --
> >> 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
> >>
> >> "Nat" <Nat@discussions.microsoft.com> wrote in message
> >> news:5B5775C7-7277-42C5-8A7C-7C4921765C5E@microsoft.com...
> >>> I've developped a Stream Driver. Everything looks fine in Debug
> >>> Configuration
> >>> and works pretty well on my Device. Then I sysgen My OS + My Driver in
> >>> RELEASE Configuration. I run it on my Device,.In this case My driver is
> >>> not
> >>> loaded by The Device Manager. I cannot figure out why, I checked registry
> >>> key, exported functions...I cannot figure out why it works in debug and
> >>> not
> >>> in release.
> >>>
> >>> Any clues.
> >>>
> >>> Nat
> >>
> >>
>

Nat
Wed Oct 31 14:05:01 PDT 2007

The DLL was not on the device because of an error in the
Driver.bib file. I did not specify MODULES at the top of the file. Since it
was the first line of the pbUserProjects.bib, the Dll was not transfered to
the windows Directory.

Thank you for your help.
Nat



"Bruce Eitman [eMVP]" wrote:

> Having a registry setting for the driver and having the driver actually be
> on the device are two different things altogether.
>
> Is the driver on the device?
>
> > What kind of variables could bring the driver to fail?
> Any variable that you did not initialize, but instead assume an initial
> state which was valid with a debug build and not valid with a retail build.
>
> --
> 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
>
> "Nat" <Nat@discussions.microsoft.com> wrote in message
> news:38E24505-9E99-47E8-84A2-8629EF325E80@microsoft.com...
> > Yes, the driver is on the device. I checked the registry: I can see it in
> > the
> > <built in>, but not in the <active>.
> > What kind of variables could bring the driver to fail?
> >
> > Nat.
> >
> >
> > "Bruce Eitman [eMVP]" wrote:
> >
> >> Is the driver actually on the device? Is the driver failing becuase of
> >> variable initialization, that is handled better with a debug build?
> >>
> >> --
> >> 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
> >>
> >> "Nat" <Nat@discussions.microsoft.com> wrote in message
> >> news:5B5775C7-7277-42C5-8A7C-7C4921765C5E@microsoft.com...
> >> > I've developped a Stream Driver. Everything looks fine in Debug
> >> > Configuration
> >> > and works pretty well on my Device. Then I sysgen My OS + My Driver in
> >> > RELEASE Configuration. I run it on my Device,.In this case My driver
> >> > is
> >> > not
> >> > loaded by The Device Manager. I cannot figure out why, I checked
> >> > registry
> >> > key, exported functions...I cannot figure out why it works in debug and
> >> > not
> >> > in release.
> >> >
> >> > Any clues.
> >> >
> >> > Nat
> >>
> >>
> >>
>
>
>

AndrewB
Tue Nov 06 06:56:03 PST 2007

I'm having a similar problem but with a twist.

I've created two stream driver dlls (using Mike Halls stream driver wizard),
one for working with a 16x2 character display and one for working with
onboard EEPROM. If I make sure that the first subproject in the build order
has the MODULES entry in its .bib file then both dlls are included in the
build, but the stream drivers do not get loaded on start up, so the devices
don't appear in the remote system information utility.

If I remove the MODULES entry then neither DLL is included in the build, but
the system loads them across the network from the Release directory on start
up - both devices appear in the remote system information utility and the
test executables can call them correctly.

Can someone let me know what's going on here as I starting to pull my hair
out?

Thanks in advance,

Andrew

voidcoder
Tue Nov 06 07:18:06 PST 2007


Show the BIB entry for your stream driver. Also what
CE version is the talk about?


--
Oleg


AndrewB wrote:
> I'm having a similar problem but with a twist.
>
> I've created two stream driver dlls (using Mike Halls stream driver wizard),
> one for working with a 16x2 character display and one for working with
> onboard EEPROM. If I make sure that the first subproject in the build order
> has the MODULES entry in its .bib file then both dlls are included in the
> build, but the stream drivers do not get loaded on start up, so the devices
> don't appear in the remote system information utility.
>
> If I remove the MODULES entry then neither DLL is included in the build, but
> the system loads them across the network from the Release directory on start
> up - both devices appear in the remote system information utility and the
> test executables can call them correctly.
>
> Can someone let me know what's going on here as I starting to pull my hair
> out?
>
> Thanks in advance,
>
> Andrew

AndrewB
Tue Nov 06 07:31:07 PST 2007

Hi,

Thanks for the help, I'm using WinCE 6.0 and here is the generated
PBUserProjects.bib:

MODULES
LM4900.dll $(_FLATRELEASEDIR)\LM4900.dll NK SH
EEPROM.dll $(_FLATRELEASEDIR)\EEPROM.dll NK SH
lcdtest.exe $(_FLATRELEASEDIR)\lcdtest.exe NK


"voidcoder" wrote:

>
> Show the BIB entry for your stream driver. Also what
> CE version is the talk about?
>
>
> --
> Oleg
>
>
> AndrewB wrote:
> > I'm having a similar problem but with a twist.
> >
> > I've created two stream driver dlls (using Mike Halls stream driver wizard),
> > one for working with a 16x2 character display and one for working with
> > onboard EEPROM. If I make sure that the first subproject in the build order
> > has the MODULES entry in its .bib file then both dlls are included in the
> > build, but the stream drivers do not get loaded on start up, so the devices
> > don't appear in the remote system information utility.
> >
> > If I remove the MODULES entry then neither DLL is included in the build, but
> > the system loads them across the network from the Release directory on start
> > up - both devices appear in the remote system information utility and the
> > test executables can call them correctly.
> >
> > Can someone let me know what's going on here as I starting to pull my hair
> > out?
> >
> > Thanks in advance,
> >
> > Andrew
>

voidcoder
Tue Nov 06 07:41:46 PST 2007


For 6.0 you are missing "K" flag to get the modules
loaded in kernel mode. Replace with:

LM4900.dll $(_FLATRELEASEDIR)\LM4900.dll NK SHK
EEPROM.dll $(_FLATRELEASEDIR)\EEPROM.dll NK SHK


--
Oleg


AndrewB wrote:
> Hi,
>
> Thanks for the help, I'm using WinCE 6.0 and here is the generated
> PBUserProjects.bib:
>
> MODULES
> LM4900.dll $(_FLATRELEASEDIR)\LM4900.dll NK SH
> EEPROM.dll $(_FLATRELEASEDIR)\EEPROM.dll NK SH
> lcdtest.exe $(_FLATRELEASEDIR)\lcdtest.exe NK
>
>
> "voidcoder" wrote:
>
>> Show the BIB entry for your stream driver. Also what
>> CE version is the talk about?
>>
>>
>> --
>> Oleg
>>
>>
>> AndrewB wrote:
>>> I'm having a similar problem but with a twist.
>>>
>>> I've created two stream driver dlls (using Mike Halls stream driver wizard),
>>> one for working with a 16x2 character display and one for working with
>>> onboard EEPROM. If I make sure that the first subproject in the build order
>>> has the MODULES entry in its .bib file then both dlls are included in the
>>> build, but the stream drivers do not get loaded on start up, so the devices
>>> don't appear in the remote system information utility.
>>>
>>> If I remove the MODULES entry then neither DLL is included in the build, but
>>> the system loads them across the network from the Release directory on start
>>> up - both devices appear in the remote system information utility and the
>>> test executables can call them correctly.
>>>
>>> Can someone let me know what's going on here as I starting to pull my hair
>>> out?
>>>
>>> Thanks in advance,
>>>
>>> Andrew

AndrewB
Tue Nov 06 09:12:00 PST 2007

Brilliant - now working perfectly. If only all my problems could be so easily
fixed.

Thanks for your help,

Andrew

"voidcoder" wrote:

>
> For 6.0 you are missing "K" flag to get the modules
> loaded in kernel mode. Replace with:
>
> LM4900.dll $(_FLATRELEASEDIR)\LM4900.dll NK SHK
> EEPROM.dll $(_FLATRELEASEDIR)\EEPROM.dll NK SHK
>
>
> --
> Oleg
>
>
> AndrewB wrote:
> > Hi,
> >
> > Thanks for the help, I'm using WinCE 6.0 and here is the generated
> > PBUserProjects.bib:
> >
> > MODULES
> > LM4900.dll $(_FLATRELEASEDIR)\LM4900.dll NK SH
> > EEPROM.dll $(_FLATRELEASEDIR)\EEPROM.dll NK SH
> > lcdtest.exe $(_FLATRELEASEDIR)\lcdtest.exe NK
> >
> >
> > "voidcoder" wrote:
> >
> >> Show the BIB entry for your stream driver. Also what
> >> CE version is the talk about?
> >>
> >>
> >> --
> >> Oleg
> >>
> >>
> >> AndrewB wrote:
> >>> I'm having a similar problem but with a twist.
> >>>
> >>> I've created two stream driver dlls (using Mike Halls stream driver wizard),
> >>> one for working with a 16x2 character display and one for working with
> >>> onboard EEPROM. If I make sure that the first subproject in the build order
> >>> has the MODULES entry in its .bib file then both dlls are included in the
> >>> build, but the stream drivers do not get loaded on start up, so the devices
> >>> don't appear in the remote system information utility.
> >>>
> >>> If I remove the MODULES entry then neither DLL is included in the build, but
> >>> the system loads them across the network from the Release directory on start
> >>> up - both devices appear in the remote system information utility and the
> >>> test executables can call them correctly.
> >>>
> >>> Can someone let me know what's going on here as I starting to pull my hair
> >>> out?
> >>>
> >>> Thanks in advance,
> >>>
> >>> Andrew
>