Re: ClearCase + WINCE 5.0 = headache

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

Bruce,

It would appear that the two directories have different ce.bib and
reginit.ini files. The ce.bib file has one big difference that I noticed
right off the bat: In the projects which have the discontiguous memory
error, the "PROFILE" option is off, in the projects which do not, the
"PROFILE" option is on.

Additionally several components were missing out of the ce.bib file, all
of which had their registry entries missing in the reginit.ini file.

I wonder how such a thing could happen, are there more files in the
workspace directory that I need to include?

Thank you so much for pointing me in that direction,
Roger

"Bruce Eitman [eMVP]" wrote:

I would diff the ce.bib, reginit.ini file in the _FLATRELEASEDIR between a
good and bad build.

When getting full source, they should do a Sysgen, that is anyting the
PBWorkspace changes do a Sysgen.

Do all of these workstations have the same QFEs installed?

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

"Roger Williamson" <RogerWilliamson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:42D373BF-6210-4CE7-B07F-15D2A520CF0C@xxxxxxxxxxxxxxxx
Valter,

I am pretty sure that the config.bib is the same. Additionally, I just
found that one of my projects on my machine started doing the
discontiguous
memory nonsense as well.

I think that I would be doing that except that the only other machine
that I have to work with refuses to zip large files properly, it gets to
the
first folder in PBWorkspaces and dies. I'm searching for a way to fix
this.

When someone new gets all of my source files integrated into their
developement environement, and has no binary files, what OS build option
should they use? "Build and Sysgen the BSP", or just "Sysgen"?

"Valter Minute" wrote:

It seems that there is a difference in memory layout configuration.
Check that config.bib is the same on both building machines.
Check also that the .bat file of the BSP are the same.

If you can't work out the differences, you may use a "brute force"
approach by running CSDiff or another diff tool on the whole WINCEE
subtree.


--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)




.

Relevant Pages

  • Re: Cache enabled with MMU Disabled on VxWorks 5.4 PPC
    ... sysPhyMemDesc, as you suggested, but then my system wont boot at all ... everything to BAT and, in a desperate attempt, marked all memory as ... Now as to why my system was not coming up with sysPhyMemDesc[]. ... memory for use by vxWorks and by the main application (which has its ...
    (comp.os.vxworks)
  • MMU question for PPC 603
    ... registers within the PowerPC e300 MMU. ... BAT hits take precedence ... The primary means of memory control for VxWorks is the MMU PTE ...
    (comp.os.vxworks)
  • Configuring BAT and PTE, VwWorks5.5
    ... I try to make a MPC755 Board with TSI107 Controller and Intel Strata Flash ... I have Basic Memory Management enabled. ... vxWorks does only boot if I have the ... Flash configured in the BAT and in the PTE in syslib.c ...
    (comp.os.vxworks)