Problem with cloning

[ms]

Hi,

I have added to System cloning component to known good image. After FBA
reboot and reseal machine reboots, on the 3rd reboot where
it says resetting setup flag when machine restarts i get error Windows
could not start because following file is missing or corrupt
Windows root\system32\hal.dll , please reinstall copy. I've searched the NG
archives but all i get is this error happens when boot ARC is
wrong. I do have a dual boot setup but i've checked my boot.ini and target
device settings where i have root drive is c:\ and folders
are in D:\Program Files etc and all is ok so can't be that simple. I feel
its something to do with the cloning gone wrong. Any ideas.

Regards
ms

 

[Slobodan Brcin \(eMVP\)]

Ms,

It is probably problem with ARC path even if you say that it is not.

D:, C: do not tell us about ARC path. Have you changed somethig is BIOS or
in hardware. For instance after cloning, you use different disk, right?

What happened to your first disk that you have used for dual boot?

Regards,
Slobodan

 

[ms]

Hi Slobodan

I am using same disk that i used for dual boot, so FBA runs on partition 2
( drive d) of
hard disk. I just thought i'd run FBA and reseal and clonig on the same
disk to test it out.

Regards
ms

 

[KM]

ms,

If you didn't change anything in the hardware the hal.dll error should not happen. Interesting..
Did you check the boot.ini file after the cloning?

KM

 

[ms]

Hi KM,

I removed the System cloning component and the error has gone away, this i
suppose is expected as
it only came when i added it. In order to redeploy my image without the
cloning component i had to blow away
the 2nd partition recreate and format. It was a logical partition on
extended so i had to blow away extended.
I also noticed a Non Dos partition which i suppose the cloning phase
created.
So it appears you can't run cloning phase in a dual boot scenario. Is this
correct?

Regards
ms

 

[Slobodan Brcin \(eMVP\)]

ms,

Do you use EWF?
This non DOS partition could be partition belonging to EWF?

Also while working with XPe try to use only primary partitions and not the
logical ones.

Regards,
Slobodan

 

[ms]

Hi Slobodan

Yes, i'm using EWF it is set to start disabled though and is RAM reg. I'll
try again with the dual boot
but with primary partition D. I take it the boot.ini and target paths
remain the same.

Regards
ms

 

[Slobodan Brcin \(eMVP\)]

ms,

missing hal.dll problem is related only to ARC path in boot.ini.

For C:, D: and other assignements please read trough:
http://msdn.microsoft.com/embedded/community/community/tips/xp/rtpartin/default.aspx

Basicaly fbreseal if configured that way will detele MontedDevices and PnP
will reassign volume letters.

Please type ewfmgr D: to make sure that there are no remnants of EWF
partition.

You should see statement that you use Reg RAM overley.

Regards,
Slobodan

 

[KM]

ms,

Just to add to Solodan's reply.. Can you show us your FBAlog.txt file? I am wondering what it says around EWF.