missing \WINDOWS\SYSTEM32\CONFIG\SYSTEM licensing?

[Santi]

Hi All,

Here's a problem that is stumping me. I made some xpe images using the
evaluation version of XP Embedded Studio and everything worked fine except
the OS expired. No surprise there.

So I purchased the real version of Embedded Studio and some runtimes and
make another image, with the licensing all set up. When I boot it I get the
message of Missing or corrupt \WINDOWS\SYSTEM32\CONFIG\SYSTEM whatever
that means.

I suspected that this may have something to do with my using a
configuration I generated with the evaluation versions so I created the
configuration from scratch. Same problem.

I am using the devices component that made with the evaluation software.

I am booting from compactflash with no EWF.

Any suggestions are greatly appreciated.

Happy Holidays to all!

-Santi

 

[KM]

Santi,


- Double check your Configuration Target Device settings in TD.
- If you happened to use EWF before make sure you don't have EWF Config volume left on the card.
- Check your boot.ini ARC path

http://groups-beta.google.com/group...dded&q=\SYSTEM32\CONFIG\SYSTEM+corrupt&qt_g=1

Btw, this is not a good practice to run on CF without EWF. E.g., the registry hives are getting accessed much (and the access goes
to pretty much the same blocks on CF) and you will finally damage some blocks of CF card. Very likely the blicks will be for the
system/software hives. After that it will be hard to understand if this is not the root of your issues.

 

[Guest]

I have been seeing this same problem with my CF XPe image. I was once able
to get through the FBA, and then it crashed. From that point on, even with
the same image, I get "Windows could not start because the following file is
missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM" Does this mean the CF
is totally shot now?

 

[KM]

MJ,

That message could mean something else (e.g., wrong path to the system hive) but in any case you should not do FBA on your CF card
as it will wear it out pretty soon (if have't already).

Regarding the error message, pleasr analyze the FBALog.txt and SetupApi.log on your target.

KM