Corrupt platform?

I created a new platform in PB4.2 the other day and it was working very
well. But since I rebooted my PC today I can't get back into it. (I
can load other platforms just fine.) Has anyone else seen this
succession of error messages?

---------------------------
Platform Builder
---------------------------
Unable to initialize feature information. The feature handler is not
available or the data is corrupt. Feature implementation information
will be reset to the default state and some features may need to be
resolved.
---------------------------
OK
---------------------------

[PB loads the platform up to the "Loading workspace: 100%" point]

---------------------------
Microsoft Visual C++ Runtime Library
---------------------------
Runtime Error!

Program:
This application has requested the Runtime to terminate it in an
unusual way.
Please contact the application's support team for more information.
---------------------------
OK
---------------------------

---------------------------
cepb.exe - Application Error
---------------------------
The exception unknown software exception (0x40000015) occurred in the
application at location 0x7c37380c.

Click on OK to terminate the program
Click on CANCEL to debug the program
---------------------------
OK Cancel
---------------------------

---------------------------
cepb.exe - Application Error
---------------------------
The instruction at "0x77f8206b" referenced memory at "0x02e109d4". The
memory could not be "read".

Click on OK to terminate the program
---------------------------
OK
---------------------------

0x77F8206B = cmp dword ptr [edx+14h],0
EDX = 02E109C0
but for all intents and purposes it's probably all garbage at this
point.

If anyone has any ideas I'd sure appreciate it. I don't want to have
to recreate the platform, but it looks like that's where I'm headed at
this point.

TIA,
Dan.

Steve
Tue Apr 11 14:29:50 CDT 2006

While I haven't seen that particular error before, those sorts of things are
usually due to a minor syntax change in one of your build files. (e.g. BAT
files, @CESSYGEN tags IF/ENDIF mismatch etc..) Unfortunately PB is
particularly sensitive to blowing up instead of providing useful error
messages if those are not quite right .

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Chris
Tue Apr 11 16:01:58 CDT 2006

Have you looked at the cepb.log file for more info ... it is in the
CEPB\BIN directory wherever you installed PB.

-Chris

Dan
Tue Apr 11 17:34:29 CDT 2006

Chris Edgington wrote:
> Have you looked at the cepb.log file for more info ... it is in the
> CEPB\BIN directory wherever you installed PB.

Perhaps that's a PB5.0 feature. I don't have a log file like that. I
do have lots of logs, but nothing that sheds any clues on my corrupted
platform. Fortunately I wrote up a procedure for how to build the
platform from scratch while I was creating it, so it shouldn't take too
long to recreate.

Thanks,
Dan.