Deploying the Run-Time Image to CF including EWF

[Henrik Roland]

I have some problems with deploying my Run-Time Image to CF.

My system contain two partitions one for the OS and one for the
application, log files ect. The OS partition is protected with EWF.

After building the image on My develop PC I copy the image to a Hard
disk, move the Hard disk to My target PC and let FBA run.
The Hard disk has two partitions with the same size, File System
(NTFS) ect. as on the final CF (a Sandisk Flash that does not have the
removable bit set, so XP can see/handle the two partitions), and some
free space for the EWF partition.

After the FBA has booted twice and the OS is running, I set up static
IP-addresses for my network connection, and finally I delete the EWF
partition with "etprep / delete" included in the El-Torido component.
I then power off the Target and move the Hard disk back to the Develop
PC and make an "Xcopy <Hard disk> <CF> /H/C/S/E/D". The CF is the
moved to the target PC and everything works fine, but if I move the CF
to another Target identical to the one where the FBA was running I get
blue screen and the error message:

A problem has been detected and…
Technical information
*** STOP: 0x0000007B (…

I would prefer to deploy this way instead of including the Cloning
component.
First. identical SID will not cause problems (At least I don't think
so).
Second. If field updated to the OS are needed, then I can ship a
running Image, and the customer can switch the CF, no need for parts
of FBA to run, blue screens,windows message ect.

Does anyone have Ideas was causes the problem and how solve them, or
is it possible at all.


Henrik Roland

 

[Slobodan Brcin]

Henrik,

1. Since you are using RAM EWF you can configure it without creating
temporary partition. For more info browse www.xpefiles.com
2. Procedure you have described should work, if your target devices are same
(Hardware, BIOS, CMOS settings, CF adapter is connected at same controller
channel).

Since you are experiencing 7B error, this means that even file system is not
loaded correctly and this can be caused by some load errors caused by very
few critical drivers needed so support controllers and disk.

You could try to give us more info about you target devices.

Regards,
Slobodan

 

[Henrik Roland]

Hi

Thanks for quick replay.

I think that the problem is "CF adapter is connected at same
controller
channel" It actually was not. The PC card (Evalue ECM-5613) has two
IDE channels one with a "normal" IDE interface and one that fits to a
Compact Flash.

When I ran the FBA on the Hard disk, the hard disk was connected to
the normal IDE interface, and after I had made the XCOPY to CF I
placed the CF in the CF interface.

My problem is now do I need to make or buy (If so where to buy) an
adaptor that fits into a Compact Flash socket and converts it to an
IDE where I can connet my Hard disk, or is there a work around


Henrik

 

[Slobodan Brcin]

You don't have to buy adapter is should work.

But if CF is not on standard IDE channel, you will need to find what drivers
are required to support controller that CF is connected to.
Or at least to make sure that they are marked as critical for system boot.

In first main you said that it was working from CF on one device.
And when you move that CF to other "same" device it does not.

What is the exact difference between those two "same" devices?

Regards,
Slobodan

 

[h.roland]

Well in the first mail I did not see the difference.
After I let the Hard disk run the FBA on traget and after I made an
XCOPY on the develop PC from the Hard disk to the CF. I actually
connected the CF to the same IDE controler on the target as the hard
disk was connected to ( via an IDE to CF adaptor) and there every
thing runs perfect. Later on I found out that if I placed the CF to
the same target via the build in CF socket the image is not running
(forgive me I can't remember the error code I an writing this mail at
home).

I then tryed to let FBA from the Hard disk (the hard disk has two
partitions c and d drive)connected to the standard IDE channel and a
CF (two partitions identicat in size and File system as the two on the
hard disk) connected to the build in CF socket. After finnishing FBA I
made an XCOPY on the develop PC from the Hard disk to the CF, and the
placed the CF in the build in socken and nothing on the to the
standard IDE channel. but also this image is not running.

That was where I thought that it could be a good idea to have the
adaptor so I could connect the Hard disk to the build in CF socket. To
me it seems that if you are making any tiny little changes to the
system after the FBA has finished you get punished.

Slobodan what do you mean by "marked as critical for system boot"

 

[Slobodan Brcin]

Henrik,

Before continuing further try to connect CF on your target device before you
run FBA.
Then after FBA finished try to check if you can see and access CF from your
XPe.

If you can, then try to determine what drivers support your CF especially
bus and controller drivers it relies on.

Then if they are different than drivers used by IDE connection, try to
determine if they are loaded by ntldr. if not you must make them.

Also all this drivers must be listed in registry category
CriticalDeviceDatabase.

Regards,
Slobodan

 

[Henrik Roland]

Slobodan.

Before continuing further try to connect CF on your target device before you
run FBA.
Then after FBA finished try to check if you can see and access CF from your
XPe.

There is no problem in seeing the device


I partly solved the problem.

I simply ran the FBA on a MARSTER CF. I took a 512 MB Card as MARSTER
and made two partitions one on 455 MB for the OS one on 22 MB for the
application and the reset was left unpartitionated for the EWF.

After letting FBA run make my IP settings, and Delete the EWF
partition I made an Xcopy from what now is my MARSTER to another CF
(Lets call it Deploy).

The Deploy CF boots but the Splash Screen is now running for about 30
sec. was earlier les than 5 sec.

The good news is that the Deploy CF can be mover to another target and
it behave in the same way.

I doubbel checked the both Primary and secondary IDE Channels are im
the Target designer.

Do you still that this is a driver probelm?? or do you have any better
ideas

Henrik.

 

[Slobodan Brcin]

No, I don't think that it is driver problem any more.

Only thing you can try is to make a indentical copy of you MASTER CF.
Use ghost, or some low lever disk byte copy utility.

Regards,
Slobodan

 

[Henrik Roland]

Slobodan thanks for your help.

I finaly got it up running.

bacically the error was caused by two things:

1) Let FBA run on exactly the same IDE as the finaly image shall run
on. I my case I finished FBA ect.on HD located on IDE 0 (primary)
after copying the image to CF I placed the CF located on IDE 1
(Secondary), this gives the blue screen and an error message.

2) Make sure that BIOS and the actual/final setup match. In my case
BIOS first Boot device was HD-0 (Marster located on IDE 0), second and
third was disabled, Boot on Other divece was enabled (for some reson
this causes the CF to Boot). After disabling the first Boot device and
litting "Boot on Other divece" be my only boot selection the splash
screen apperince was reduced from 30 sec down to less than 5 sec.

regards

Henrik