[Heidi Linda]

I'm trying to remote boot a small image (under 80MB) with the RAM disk
component included. I've put my post-FBA c:\windows image into an .sdi file,
the client's finding it and downloading it without a problem, but then I get
the old missing/corrupt hal.dll problem.
I've tried everything I've seen suggested on the group so far, though I've
had no luck so perhaps my google-fu is weak today. I've spent the entire
afternoon fighting with this. The image mounts just fine, so I wouldn't have
thought it could be corrupted.
Ideas, anyone?

[JPR]

1. You say that you put your "post-FBA c:\windows image" in an SDI file.
Maybe I am not parsing your words correctly but I always put all of
C:\ in the file although boot.ini, ntdetect.com, and ntldr can be
omitted (per tutorial).

2. Do you create the SDI file in a two step process, i.e. create a SDI
disk first, format it, and copy files to it and then create an SDI file
with a /readpart:X: option where X: is the SDI disk? Frankly I don't
understand the rationale but that is the way it's done in the tutorial
and it has always worked for me.

Heidi Linda wrote:
> I'm trying to remote boot a small image (under 80MB) with the RAM disk
> component included. I've put my post-FBA c:\windows image into an .sdi file,
> the client's finding it and downloading it without a problem, but then I get
> the old missing/corrupt hal.dll problem.
> I've tried everything I've seen suggested on the group so far, though I've
> had no luck so perhaps my google-fu is weak today. I've spent the entire
> afternoon fighting with this. The image mounts just fine, so I wouldn't have
> thought it could be corrupted.
> Ideas, anyone?

[Heidi Linda]

"JPR" <blooline@online.nospam> wrote in message
news:OmSk5jJcFHA.1392@TK2MSFTNGP14.phx.gbl...
> 1. You say that you put your "post-FBA c:\windows image" in an SDI file.
> Maybe I am not parsing your words correctly but I always put all of
> C:\ in the file although boot.ini, ntdetect.com, and ntldr can be
> omitted (per tutorial).

I meant that my image booted to c:\windows, not some other windows
directory.
>
> 2. Do you create the SDI file in a two step process, i.e. create a SDI
> disk first, format it, and copy files to it and then create an SDI file
> with a /readpart:X: option where X: is the SDI disk? Frankly I don't
> understand the rationale but that is the way it's done in the tutorial
> and it has always worked for me.

I've tried both ways.

[Brad Combs]

Hi Heidi,

I noticed something in your post..."The image mounts just fine,"

Does that mean you can mount it in SDI Loader? If so then you have a Disk
SDI Image when all you need is a Partition SDI Image. Instead of creating
the SDI with SDI Loader and copying the files to it use sdimgr from the
command line to create a partition SDI and then copy the files to that. For
example...

sdimgr /new c:\mysdi.sdi
sdimgr c:\mysdi.sdi /readpart:d: (where D: contains your post FBA image)

Now use mysdi.sdi to boot from RBS.

HTH,
Brad



"Heidi Linda" <heidi.linda@inspiredbroadcast.net> wrote in message
news:OQzEgHEcFHA.3940@TK2MSFTNGP10.phx.gbl...
> I'm trying to remote boot a small image (under 80MB) with the RAM disk
> component included. I've put my post-FBA c:\windows image into an .sdi
> file,
> the client's finding it and downloading it without a problem, but then I
> get
> the old missing/corrupt hal.dll problem.
> I've tried everything I've seen suggested on the group so far, though I've
> had no luck so perhaps my google-fu is weak today. I've spent the entire
> afternoon fighting with this. The image mounts just fine, so I wouldn't
> have
> thought it could be corrupted.
> Ideas, anyone?
>
>

[KM]

Heidi,

You may want to show us the output of "sdimgr your_sdi_file" command.

As Brad pointed out, without a custom boot program you will need a PART blob
in your SDI file (use readpart switch of sdimgr).

You can always "test" your SDI file locally and boot it from HDD with rdpath
switch in boot.ini (search NG archive).

KM

> I'm trying to remote boot a small image (under 80MB) with the RAM disk
> component included. I've put my post-FBA c:\windows image into an .sdi
> file,
> the client's finding it and downloading it without a problem, but then I
> get
> the old missing/corrupt hal.dll problem.
> I've tried everything I've seen suggested on the group so far, though I've
> had no luck so perhaps my google-fu is weak today. I've spent the entire
> afternoon fighting with this. The image mounts just fine, so I wouldn't
> have
> thought it could be corrupted.
> Ideas, anyone?
>
>

[Heidi Linda]

Brad, you're a lifesaver. It's booted.

"Brad Combs" <brad@no.spam.imagotechnologies.nospam.com> wrote in message
news:udTvQ4PcFHA.584@TK2MSFTNGP15.phx.gbl...
> Hi Heidi,
>
> I noticed something in your post..."The image mounts just fine,"
>
> Does that mean you can mount it in SDI Loader? If so then you have a Disk
> SDI Image when all you need is a Partition SDI Image. Instead of creating
> the SDI with SDI Loader and copying the files to it use sdimgr from the
> command line to create a partition SDI and then copy the files to that.
For
> example...
>
> sdimgr /new c:\mysdi.sdi
> sdimgr c:\mysdi.sdi /readpart:d: (where D: contains your post FBA image)
>
> Now use mysdi.sdi to boot from RBS.
>
> HTH,
> Brad
>
>
>
> "Heidi Linda" <heidi.linda@inspiredbroadcast.net> wrote in message
> news:OQzEgHEcFHA.3940@TK2MSFTNGP10.phx.gbl...
> > I'm trying to remote boot a small image (under 80MB) with the RAM disk
> > component included. I've put my post-FBA c:\windows image into an .sdi
> > file,
> > the client's finding it and downloading it without a problem, but then I
> > get
> > the old missing/corrupt hal.dll problem.
> > I've tried everything I've seen suggested on the group so far, though
I've
> > had no luck so perhaps my google-fu is weak today. I've spent the entire
> > afternoon fighting with this. The image mounts just fine, so I wouldn't
> > have
> > thought it could be corrupted.
> > Ideas, anyone?
> >
> >
>
>