I have a strange issue.
I have an XPe image running on a CF card with EWF. I have 9 instances
of this actually.
Intermittently I get this error message on boot.

\WINDOWS\SYSTEM32\CONFIG\SYSTEM is missing or corrupt

EWF is enabled.
The fix is to reboot the system repeatedly. At some point, it manages
to continue through the boot process successfully.
How is this possible? It can't be that the image is actually corrupt.
A few reboots fixes it. The image is read only with successful boots
after enabling read only.

I am using evaluation design tools, if that matters.

Any thoughts?

Thanks

On Jun 26, 3:14 pm, kareemsul...@gmail.com wrote:
> I have a strange issue.
> I have an XPe image running on a CF card with EWF. I have 9 instances
> of this actually.
> Intermittently I get this error message on boot.
>
Is it possible this is because the CF card is wearing away? What are
the signs of a dying CF card?

Thanks

> \WINDOWS\SYSTEM32\CONFIG\SYSTEM is missing or corrupt
>
> EWF is enabled.
> The fix is to reboot the system repeatedly. At some point, it manages
> to continue through the boot process successfully.
> How is this possible? It can't be that the image is actually corrupt.
> A few reboots fixes it. The image is read only with successful boots
> after enabling read only.
>
> I am using evaluation design tools, if that matters.
>
> Any thoughts?
>
> Thanks

I did some digging. Some people suspected this behavior could be
stemming from over used CF cards.
I've now used a brand new fresh CF card and have now gotten the same
error once.

There must be something else. Has no one else experienced this?

Thanks


On Jul 3, 2:11 pm, kareemsul...@gmail.com wrote:
> On Jun 26, 3:14 pm, kareemsul...@gmail.com wrote:> I have a strange issue.
> > I have an XPe image running on a CF card with EWF. I have 9 instances
> > of this actually.
> > Intermittently I get this error message on boot.
>
> Is it possible this is because the CF card is wearing away? What are
> the signs of a dying CF card?
>
> Thanks
>
> > \WINDOWS\SYSTEM32\CONFIG\SYSTEM is missing or corrupt
>
> > EWF is enabled.
> > The fix is to reboot the system repeatedly. At some point, it manages
> > to continue through the boot process successfully.
> > How is this possible? It can't be that the image is actually corrupt.
> > A few reboots fixes it. The image is read only with successful boots
> > after enabling read only.
>
> > I am using evaluation design tools, if that matters.
>
> > Any thoughts?
>
> > Thanks