Ramdisk Load error with Remote Boot Service?

[Guest]

Hey guys, I built an embedded image, deployed it onto a machine by just copying over what I was supposed to as per msdn tech articles. I also included the Windows Ram Disk component, and the System Cloning Utility component.. Ran the Image, it proceeded through both FBA, rebooted, and then I received the Machine Resealed Message, I booted the machine to my second hard drive that contained XP PRO. I captured the "Golden Image" using sdi manager and I was attemtping to load it via the Remote Boot Service Manager included with the windows embedded development package. It proceeded through "Loading Ramdisk Image" until about the 75% mark when I received the following error....

Windows Could not Start due to an Error While Loading from RamDisk

Windows Failed to open the RamDisk Image..

Does anyone have any ideas? My image is less than 400 mb and I believe the machines have like 512 memory. I remember reading something about the memory being double the size of the image. Would this cause that error? Stripping it down even further is just a pain but if I have to I have to.

Does anyone else have any first hand experience with this, or know a solution to this issue....Thanks

-Mark

 

[KM]

Mark,

There is no particular requirement to have RAM double size of your image.
Although, as the image is copied and ran from RAM it should definitely be
enough to fit the entire image + some memory enough to run your image
(depending on your image memory consumption).

400Mb image is pretty big, though 512RAM may be enough.

How did you use sdimgr to capture the image?
If you run "sdimgr your.sdi" what output do you see? Can you copy and paste
it here?
Search this NG archive for sdimgr to see how exactly you have to capture the
post-FBA image (concern on BLOB sections inside your SDI).

--
KM,
BSquare Corporation

Hey guys, I built an embedded image, deployed it onto a machine by just

copying over what I was supposed to as per msdn tech articles. I also
included the Windows Ram Disk component, and the System Cloning Utility
component.. Ran the Image, it proceeded through both FBA, rebooted, and
then I received the Machine Resealed Message, I booted the machine to my
second hard drive that contained XP PRO. I captured the "Golden Image"
using sdi manager and I was attemtping to load it via the Remote Boot
Service Manager included with the windows embedded development package. It
proceeded through "Loading Ramdisk Image" until about the 75% mark when I
received the following error.....

Windows Could not Start due to an Error While Loading from RamDisk.

Windows Failed to open the RamDisk Image...


Does anyone have any ideas? My image is less than 400 mb and I believe

the machines have like 512 memory. I remember reading something about the
memory being double the size of the image. Would this cause that error?
Stripping it down even further is just a pain but if I have to I have to.

Does anyone else have any first hand experience with this, or know a

solution to this issue....Thanks!

 

[KM]

Mark,

I don't see any obvious cause. Try these:

1. Make smaller image (< 64Mb with MinLogon or etc.) and boot in remotely
with the RBM. Do you still see the error? Is it on the same 75% of loading?

2. Try to boot off the SDI image locally on your dev machine where you were
FBA-ing the runtime. Use /rdpath option in your boot.ini ARC path to the XPe
partition (search this NG archive for more details on the switch).

3. Replace your memory sticks or test them on a different machine.

4. Connect Kernel Debugger remotely from your dev machine to the target
(through serial, e.g.) and see if ntldr throws any error in the output that
may explain why it stops at 75%.