John
Fri Jun 08 14:22:54 CDT 2007
Thank you for your help. If anyone is willing clarify the following I
would feel more comfortable understanding the change. I do not have
much experience deciphering BSP hierarchies.
1) Does it matter if I modify CurMSec before or after InitClock()/
anything within OEMInit()? (Should it just be the first thing?)
2) OEMInit() in \PUBLIC\COMMON\OAK\CSP\I486\OAL\cfwpc.c?
(Since the platform is x86 & appears to be based on the GEODE
platform, which appears to inherit from CEPC.)
3) Where is CurMSec actually defined / initialized? I could not find
an actual variable definition for CurMSec except in LoadCEPC.
Thanks again!
On Jun 8, 9:52 am, "Bruce Eitman [eMVP]"
<beitman.nos...@applieddata.net.nospam> wrote:
> Initialize CurMSec to a large number in OEMInit()
>
> --
> 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
>
> "John S." <john.spr...@apisoftwareinc.com> wrote in message
>
> news:1181311817.542358.116100@n4g2000hsb.googlegroups.com...
>
>
>
> > In Sue Loh's precursor to what is now the Windows CE Base Team Blog,
> > she mentions functionality incorporated into Windows CE debug builds
> > designed to catch misuse of the GetTickCount function:
>
> > GetTickCount - Truth and Fiction
> >
http://blogs.msdn.com/sloh/archive/2005/04/05/405724.aspx
> > "To help catch such errors in applications and drivers, Windows CE
> > does a little thing on debug builds - it initializes the tick count
> > such that it rolls over 3 minutes after boot."
>
> > I am not seeing this on my Windows CE 4.2 x86 debug build. Two
> > questions:
>
> > 1) Where did this start in Windows CE (which version), or is it BSP-
> > specific?
> > 2) How can I do this manually for my debug build?
>
> > Any help would be appreciated as the alternative is to wait ~50
> > days. :)- Hide quoted text -
>
> - Show quoted text -