Hi sir
Thanks for ur response
Now i have made changes in only Platform.reg and .bib files. The respective
changes are
1)In PLATFORM.BIB:-
IF BSP_NODISPLAY !
IF BSP_CERDISP
DISP.dll $(_FLATRELEASEDIR)\DISP.dll NK
SH
ENDIF
ENDIF

2)In PLATFORM.REG:-
IF BSP_NODISPLAY !
[HKEY_LOCAL_MACHINE\System\GDI\Drivers]
"Display"="DISP.dll"

IF BSP_CERDISP
[HKEY_LOCAL_MACHINE\Drivers\Display\DISP]
"DisplayType"="DISP"
"CxScreen"=dword:280 ; 640
"CyScreen"=dword: f0 ; 240
"Bpp"=dword:4
ENDIF
ENDIF BSP_NODISPLAY !
Warning: Found duplicate entry 'DISP.dll NK
C:\WINCE420\PUBLIC\CSB337\DISP\CSB337__ARMV4IRel\DISP.dll 00000007'
...skipping

Warning: Using old fixup style in module DISP.dll

I dont know why the process gwes.exe is aborting.As it is giving this error
while loading kernel image onto the board.




"Richard Lee" <richardl@ati.com_nospam> wrote in message
news:eu4zyYhLEHA.4052@TK2MSFTNGP11.phx.gbl...
> Hi Gaurav,
>
> You do not want to add the display driver to both PLATFORM.BIN and
> COMMON.BIB. That;s the origin of the
> "Warning: Found duplicate entry 'DISP.dll NK"
> message. Changing COMMON files is generally not a good idea, and is never
> necessary. Custom drivers tend to be platform specific, so putting the
entry
> in PLATFORM.BIB is good.
>
> The crash looks like GWES did not find the registry entries for the new
> display driver. You have different variables for including the driver in
the
> image (DISP_DISPLAY) and the registry entries for the driver
(BSP_CERDISP).
> After MAKEIMG completes, check the contents of REGINIT.INI file in the
> release directory to verify that the registry entries you expect are
actualy
> present.
>
> You may want to experiment with a debug build to get more messages out of
> GWES. I'd also recommend putting a few RETAILMSG() statements in your
> driver to log intiaialization and function return values, until you get
past
> this fault.
>
> --
> Richard R. Lee, eMVP
> ATi technologies
>
>

Re: Help me build kernel? by Xu

Xu
Mon May 03 13:53:53 CDT 2004

Try debugging your display driver. If you driver has bugs and it can be
loaded successfully then GWE will abort.

Xu Jun

"George" <gaurav@blr.sarayusoftech.com> wrote in message
news:Oe3eg5PMEHA.3664@TK2MSFTNGP10.phx.gbl...
> Hi sir
> Thanks for ur response
> Now i have made changes in only Platform.reg and .bib files. The
respective
> changes are
> 1)In PLATFORM.BIB:-
> IF BSP_NODISPLAY !
> IF BSP_CERDISP
> DISP.dll $(_FLATRELEASEDIR)\DISP.dll NK
> SH
> ENDIF
> ENDIF
>
> 2)In PLATFORM.REG:-
> IF BSP_NODISPLAY !
> [HKEY_LOCAL_MACHINE\System\GDI\Drivers]
> "Display"="DISP.dll"
>
> IF BSP_CERDISP
> [HKEY_LOCAL_MACHINE\Drivers\Display\DISP]
> "DisplayType"="DISP"
> "CxScreen"=dword:280 ; 640
> "CyScreen"=dword: f0 ; 240
> "Bpp"=dword:4
> ENDIF
> ENDIF BSP_NODISPLAY !
> Warning: Found duplicate entry 'DISP.dll NK
> C:\WINCE420\PUBLIC\CSB337\DISP\CSB337__ARMV4IRel\DISP.dll 00000007'
> ...skipping
>
> Warning: Using old fixup style in module DISP.dll
>
> I dont know why the process gwes.exe is aborting.As it is giving this
error
> while loading kernel image onto the board.
>
>
>
>
> "Richard Lee" <richardl@ati.com_nospam> wrote in message
> news:eu4zyYhLEHA.4052@TK2MSFTNGP11.phx.gbl...
> > Hi Gaurav,
> >
> > You do not want to add the display driver to both PLATFORM.BIN and
> > COMMON.BIB. That;s the origin of the
> > "Warning: Found duplicate entry 'DISP.dll NK"
> > message. Changing COMMON files is generally not a good idea, and is
never
> > necessary. Custom drivers tend to be platform specific, so putting the
> entry
> > in PLATFORM.BIB is good.
> >
> > The crash looks like GWES did not find the registry entries for the new
> > display driver. You have different variables for including the driver in
> the
> > image (DISP_DISPLAY) and the registry entries for the driver
> (BSP_CERDISP).
> > After MAKEIMG completes, check the contents of REGINIT.INI file in the
> > release directory to verify that the registry entries you expect are
> actualy
> > present.
> >
> > You may want to experiment with a debug build to get more messages out
of
> > GWES. I'd also recommend putting a few RETAILMSG() statements in your
> > driver to log intiaialization and function return values, until you get
> past
> > this fault.
> >
> > --
> > Richard R. Lee, eMVP
> > ATi technologies
> >
> >
>
>
>
>



Re: Help me build kernel? by Bruce

Bruce
Mon May 03 14:54:04 CDT 2004

Eliminate the makeimg warning about duplicate entries. Look in ce.bib to
see the two entries. My guess is that you wrapped your bib file entry with
the same environment variables as another driver. You don't need to do
this, you need to use your own variables since it is your driver. If this
is not the case then you need to turn off the variable that control the
other driver. It is important to do this, so that you know which driver is
being loaded by GWES.

What is the error that you see in gwes?

You should consider using the PB debugger or debug messages, these can help
you track down the cause of exceptions.

Then, instead of starting new threads for each of your posts, try replying
to an existing thread that you started on the same topic. Helps keep things
organized. Then try a subject that has something to do with your question,
you may just get someone who is interested in display drivers to notice your
question.

--
Bruce Eitman (eMVP)
Senior Engineer
Accelent Systems Inc.
www.accelent.com



Re: Help me build kernel? by George

George
Wed May 05 21:28:30 CDT 2004

This is a multi-part message in MIME format.

------=_NextPart_000_0020_01C432D7.25905570
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Sir
Thanks for ur response.
the problem i am facing is that when i am tring to port image including =
my display driver dll it is giving error which i have shown in bold =
letters.

Data Abort: Thread=3D81ceb114 Proc=3D80b38ac0 'gwes.exe'
AKY=3D00000011 PC=3D000538ac RA=3D0004c6bc BVA=3D0a000008 FSR=3D00000007

i have done respective entry in .reg and .bib files for my driverand set =
my own envirnoment variable for the driver.after building image ,i am =
getting the respective entry in REGINIT file for my driver also.but when =
i am trying to port the image on to the board still i am gettiing the =
same error.
while buiding the image on platform buider i am sometimes getting the =
following warning.=20

Warning: Found duplicate entry 'DISP.dll NK
C:\WINCE420\PUBLIC\CEE221\DISP\CEE221__ARMV4IRel\DISP.dll 00000007'
...skipping

Warning: Using old fixup style in module DISP.dll
DISP.dll is our own display driver for our graphic board which we have =
developed.

Sir i am so confused .please help me out why above error is being =
occuring while porting OS image with our display driver.

Thanks & Regards
George

"Bruce Eitman (eMVP)" <beitmannospam@accelentnospam.com> wrote in =
message news:eWUrlhUMEHA.752@TK2MSFTNGP10.phx.gbl...
> Eliminate the makeimg warning about duplicate entries. Look in ce.bib =
to
> see the two entries. My guess is that you wrapped your bib file entry =
with
> the same environment variables as another driver. You don't need to =
do
> this, you need to use your own variables since it is your driver. If =
this
> is not the case then you need to turn off the variable that control =
the
> other driver. It is important to do this, so that you know which =
driver is
> being loaded by GWES.
>=20
> What is the error that you see in gwes?
>=20
> You should consider using the PB debugger or debug messages, these can =
help
> you track down the cause of exceptions.
>=20
> Then, instead of starting new threads for each of your posts, try =
replying
> to an existing thread that you started on the same topic. Helps keep =
things
> organized. Then try a subject that has something to do with your =
question,
> you may just get someone who is interested in display drivers to =
notice your
> question.
>=20
> --=20
> Bruce Eitman (eMVP)
> Senior Engineer
> Accelent Systems Inc.
> www.accelent.com
>=20
>=20

------=_NextPart_000_0020_01C432D7.25905570
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>Hi Sir</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Thanks for ur response.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the problem i am facing is that when i =
am tring to=20
port image including my display driver dll it is giving error which i =
have shown=20
in bold letters.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG>Data Abort: Thread=3D81ceb114 =
Proc=3D80b38ac0=20
'gwes.exe'<BR>AKY=3D00000011 PC=3D000538ac RA=3D0004c6bc BVA=3D0a000008=20
FSR=3D00000007</STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>i have done respective entry in .reg =
and .bib files=20
for my driverand set my own envirnoment variable for the driver.after =
building=20
image ,i am getting the respective entry in REGINIT file for my driver =
also.but=20
when i am&nbsp;trying to port the&nbsp;image on to the board still i am =
gettiing=20
the same error.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>while buiding the image on platform =
buider i=20
am&nbsp;sometimes getting&nbsp;the following warning.&nbsp;</DIV>
<DIV></FONT><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG>Warning: Found duplicate entry=20
'DISP.dll&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
NK<BR>C:\WINCE420\PUBLIC\CEE221\DISP\CEE221__ARMV4IRel\DISP.dll=20
00000007'<BR>...skipping</STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG>Warning: Using old fixup style =
in module=20
DISP.dll</STRONG></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>DISP.dll is our own display driver for =
our graphic=20
board which we have developed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Sir i am so confused .please help me =
out why above=20
error is being occuring while porting OS image with our display=20
driver.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks &amp; Regards</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>George</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>"Bruce Eitman (eMVP)" &lt;</FONT><A=20
href=3D"mailto:beitmannospam@accelentnospam.com"><FONT face=3DArial=20
size=3D2>beitmannospam@accelentnospam.com</FONT></A><FONT face=3DArial =
size=3D2>&gt;=20
wrote in message </FONT><A=20
href=3D"news:eWUrlhUMEHA.752@TK2MSFTNGP10.phx.gbl"><FONT face=3DArial=20
size=3D2>news:eWUrlhUMEHA.752@TK2MSFTNGP10.phx.gbl</FONT></A><FONT =
face=3DArial=20
size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>&gt; Eliminate the =
makeimg=20
warning about duplicate entries.&nbsp; Look in ce.bib to<BR>&gt; see the =
two=20
entries.&nbsp; My guess is that you wrapped your bib file entry =
with<BR>&gt; the=20
same environment variables as another driver.&nbsp; You don't need to =
do<BR>&gt;=20
this, you need to use your own variables since it is your driver.&nbsp; =
If=20
this<BR>&gt; is not the case then you need to turn off the variable that =
control=20
the<BR>&gt; other driver.&nbsp; It is important to do this, so that you =
know=20
which driver is<BR>&gt; being loaded by GWES.<BR>&gt; <BR>&gt; What is =
the error=20
that you see in gwes?<BR>&gt; <BR>&gt; You should consider using the PB =
debugger=20
or debug messages, these can help<BR>&gt; you track down the cause of=20
exceptions.<BR>&gt; <BR>&gt; Then, instead of starting new threads for =
each of=20
your posts, try replying<BR>&gt; to an existing thread that you started =
on the=20
same topic.&nbsp; Helps keep things<BR>&gt; organized.&nbsp; Then try a =
subject=20
that has something to do with your question,<BR>&gt; you may just get =
someone=20
who is interested in display drivers to notice your<BR>&gt; =
question.<BR>&gt;=20
<BR>&gt; -- <BR>&gt; &nbsp;&nbsp; Bruce Eitman (eMVP)<BR>&gt; =
&nbsp;&nbsp;=20
Senior Engineer<BR>&gt; &nbsp;&nbsp; Accelent Systems Inc.<BR>&gt; =
&nbsp;&nbsp;=20
</FONT><A href=3D"http://www.accelent.com"><FONT face=3DArial=20
size=3D2>www.accelent.com</FONT></A><BR><FONT face=3DArial size=3D2>&gt; =
<BR>&gt;=20
</FONT></BODY></HTML>

------=_NextPart_000_0020_01C432D7.25905570--


Re: Help me build kernel? by Bruce

Bruce
Wed May 05 11:19:14 CDT 2004

Okay, so review my previous posting, then get back to us after you have done
some debugging.

You do know that your display driver is loaded by GWES don't you? So any
error messages about your driver will indicate that the app is gwes.exe. So
the error is probably not really so much about gwes, but about your driver.

--
Bruce Eitman (eMVP)
Senior Engineer
Accelent Systems Inc.
www.accelent.com




Help me build kernel? by Michael

Michael
Fri May 07 22:51:04 CDT 2004

How do i get ahold of Bruce Eitman. His email address is
not working

>-----Original Message-----
>Hi sir
>Thanks for ur response
>Now i have made changes in only Platform.reg and .bib
files. The respective
>changes are
>1)In PLATFORM.BIB:-
> IF BSP_NODISPLAY !
> IF BSP_CERDISP
> DISP.dll $(_FLATRELEASEDIR)
\DISP.dll NK
>SH
> ENDIF
> ENDIF
>
>2)In PLATFORM.REG:-
> IF BSP_NODISPLAY !
> [HKEY_LOCAL_MACHINE\System\GDI\Drivers]
> "Display"="DISP.dll"
>
> IF BSP_CERDISP
> [HKEY_LOCAL_MACHINE\Drivers\Display\DISP]
> "DisplayType"="DISP"
> "CxScreen"=dword:280 ; 640
> "CyScreen"=dword: f0 ; 240
> "Bpp"=dword:4
> ENDIF
> ENDIF BSP_NODISPLAY !
>Warning: Found duplicate entry 'DISP.dll NK
>C:\WINCE420\PUBLIC\CSB337\DISP\CSB337__ARMV4IRel\DISP.dll
00000007'
>....skipping
>
>Warning: Using old fixup style in module DISP.dll
>
>I dont know why the process gwes.exe is aborting.As it is
giving this error
>while loading kernel image onto the board.
>
>
>
>
>"Richard Lee" <richardl@ati.com_nospam> wrote in message
>news:eu4zyYhLEHA.4052@TK2MSFTNGP11.phx.gbl...
>> Hi Gaurav,
>>
>> You do not want to add the display driver to both
PLATFORM.BIN and
>> COMMON.BIB. That;s the origin of the
>> "Warning: Found duplicate entry 'DISP.dll NK"
>> message. Changing COMMON files is generally not a good
idea, and is never
>> necessary. Custom drivers tend to be platform specific,
so putting the
>entry
>> in PLATFORM.BIB is good.
>>
>> The crash looks like GWES did not find the registry
entries for the new
>> display driver. You have different variables for
including the driver in
>the
>> image (DISP_DISPLAY) and the registry entries for the
driver
>(BSP_CERDISP).
>> After MAKEIMG completes, check the contents of
REGINIT.INI file in the
>> release directory to verify that the registry entries
you expect are
>actualy
>> present.
>>
>> You may want to experiment with a debug build to get
more messages out of
>> GWES. I'd also recommend putting a few RETAILMSG()
statements in your
>> driver to log intiaialization and function return
values, until you get
>past
>> this fault.
>>
>> --
>> Richard R. Lee, eMVP
>> ATi technologies
>>
>>
>
>
>
>
>.
>

Re: Help me build kernel? by Dean

Dean
Fri May 14 06:54:15 CDT 2004

I let him know you're looking for him...

--
Dean Ramsier - eMVP

"Michael Seday" <anonymous@discussions.microsoft.com> wrote in message
news:9f3201c434af$afe247e0$a401280a@phx.gbl...
> How do i get ahold of Bruce Eitman. His email address is
> not working
>
> >-----Original Message-----
> >Hi sir
> >Thanks for ur response
> >Now i have made changes in only Platform.reg and .bib
> files. The respective
> >changes are
> >1)In PLATFORM.BIB:-
> > IF BSP_NODISPLAY !
> > IF BSP_CERDISP
> > DISP.dll $(_FLATRELEASEDIR)
> \DISP.dll NK
> >SH
> > ENDIF
> > ENDIF
> >
> >2)In PLATFORM.REG:-
> > IF BSP_NODISPLAY !
> > [HKEY_LOCAL_MACHINE\System\GDI\Drivers]
> > "Display"="DISP.dll"
> >
> > IF BSP_CERDISP
> > [HKEY_LOCAL_MACHINE\Drivers\Display\DISP]
> > "DisplayType"="DISP"
> > "CxScreen"=dword:280 ; 640
> > "CyScreen"=dword: f0 ; 240
> > "Bpp"=dword:4
> > ENDIF
> > ENDIF BSP_NODISPLAY !
> >Warning: Found duplicate entry 'DISP.dll NK
> >C:\WINCE420\PUBLIC\CSB337\DISP\CSB337__ARMV4IRel\DISP.dll
> 00000007'
> >....skipping
> >
> >Warning: Using old fixup style in module DISP.dll
> >
> >I dont know why the process gwes.exe is aborting.As it is
> giving this error
> >while loading kernel image onto the board.
> >
> >
> >
> >
> >"Richard Lee" <richardl@ati.com_nospam> wrote in message
> >news:eu4zyYhLEHA.4052@TK2MSFTNGP11.phx.gbl...
> >> Hi Gaurav,
> >>
> >> You do not want to add the display driver to both
> PLATFORM.BIN and
> >> COMMON.BIB. That;s the origin of the
> >> "Warning: Found duplicate entry 'DISP.dll NK"
> >> message. Changing COMMON files is generally not a good
> idea, and is never
> >> necessary. Custom drivers tend to be platform specific,
> so putting the
> >entry
> >> in PLATFORM.BIB is good.
> >>
> >> The crash looks like GWES did not find the registry
> entries for the new
> >> display driver. You have different variables for
> including the driver in
> >the
> >> image (DISP_DISPLAY) and the registry entries for the
> driver
> >(BSP_CERDISP).
> >> After MAKEIMG completes, check the contents of
> REGINIT.INI file in the
> >> release directory to verify that the registry entries
> you expect are
> >actualy
> >> present.
> >>
> >> You may want to experiment with a debug build to get
> more messages out of
> >> GWES. I'd also recommend putting a few RETAILMSG()
> statements in your
> >> driver to log intiaialization and function return
> values, until you get
> >past
> >> this fault.
> >>
> >> --
> >> Richard R. Lee, eMVP
> >> ATi technologies
> >>
> >>
> >
> >
> >
> >
> >.
> >