Re: build -c from Mystery Solved

Tech-Archive recommends: Fix windows errors by optimizing your registry

Oh, forgot to answer all your questions.
In step 1 of Bryans posting he advises a change in the
READ_BUFFER_LENGTH_MAX value in fat.h.
In step 2 he then says to rebuild the bootloader by running build -c in the
WinCE500\Public\common\oak\csp\x86\biosloader\loader directory.

This is where I am at.

Paul
--
Paul A. Lowe
Sr Project Engineer
Eaton Electrical


"Bruce Eitman (eMVP)" wrote:

> Have you fully built the platform at least once? Any other errors proceed
> that?
>
> --
> 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
>
>
> "Paul A. Lowe" <PaulALowe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C2DADCDF-0282-4475-A38F-7B3B085D4BE0@xxxxxxxxxxxxxxxx
> > Thank you Bruce.
> > I ran it from PB->BuildOS->Open release Directory.
> > Have an Nmake error. The command window shows:
> > BUILD: [01:0000000061:ERRORE] NMAKE : U1073: don't know how to make
> > 'C:\WINCE500\public\common\oak\lib\x86\debug\iniparse.lib'
> > BUILD: [01:0000000063:ERRORE] NMAKE.exe -i -c BUILDMSG=Stop. NOLINK=1
> > NOPASS0=1 failed -rc = 2
> >
> > What am I doing wrong?
> >
> > Paul
> >
> > --
> > Paul A. Lowe
> > Sr Project Engineer
> > Eaton Electrical
> >
> >
> > "Bruce Eitman (eMVP)" wrote:
> >
> >> You need some environment variables set correctly to do that. The
> >> easiest
> >> way would be to use the Platform Builder Build\Open Release... menu.
> >> This
> >> opens a window with the environment set up, but you will need to change
> >> directories to the directory that you want to 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
> >>
> >>
> >> "Paul A. Lowe" <PaulALowe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:08EBC17F-0439-4AFC-A6FC-7139E1268A6B@xxxxxxxxxxxxxxxx
> >> > Hi
> >> > New to WinCe.
> >> > Am trying to follow the instructions Bryan Everly posted in Mystery
> >> > Solved.
> >> > Problem I am having is step #2. I have tried to run the build -c
> >> > command
> >> > in
> >> > Command Prompt window and from the Run command off the Start bar. Both
> >> > come
> >> > back telling me there is no program named build. I have searched
> >> > through
> >> > the
> >> > directories and found a build.exe and build.bat. Not sure if either of
> >> > these
> >> > is correct and if so how to use the correct one. Could someone dumb
> >> > down
> >> > the
> >> > instructions so I can do this? Please???
> >> >
> >> > Paul
> >> > --
> >> > Paul A. Lowe
> >> > Sr Project Engineer
> >> > Eaton Electrical
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: build -c from Mystery Solved
    ... Paul A. Lowe ... "Bruce Eitman " wrote: ... >> Sr Project Engineer ... >>> beitman AT applieddata DOT net ...
    (microsoft.public.windowsce.platbuilder)
  • Re: build -c from Mystery Solved
    ... Paul A. Lowe ... "Bruce Eitman (eMVP)" wrote: ... >> Sr Project Engineer ...
    (microsoft.public.windowsce.platbuilder)
  • Re: build -c from Mystery Solved
    ... > Paul A. Lowe ... >> Bruce Eitman ... >> Senior Engineer ... >> beitman AT applieddata DOT net ...
    (microsoft.public.windowsce.platbuilder)
  • Re: build -c from Mystery Solved
    ... Paul A. Lowe ... "Bruce Eitman " wrote: ... >> Sr Project Engineer ... >>> beitman AT applieddata DOT net ...
    (microsoft.public.windowsce.platbuilder)
  • Re: build -c from Mystery Solved
    ... Yes, it sounds like you need to make sure that you've built the OS, ... Paul T. ... >> beitman AT applieddata DOT net ... >>> Sr Project Engineer ...
    (microsoft.public.windowsce.platbuilder)