Sorry to bring this up again (Google Groups shows it was mentioned in
February) but SDI2HD downloads nearly all of my .sdi file across the
network, and then hangs - one progress bar division from the end. The
network traffic continues, but no further accesses occur on the disk
holding the .sdi file.

I've looked all over the 'net for guidance but to no avail. Am I missing
something in the build sequence such that the sdi image is not properly
closed? (And can SDI2HD really make a bootable image on a blank HDD?)

I have been following the MS documentation where there is no mention of
the partition blobs I have seen in posts around here. Are they relevant?

TIA

David Dunning.

I don't know why you have problem with sdi2hd.

PART blob is used with RAM boot scenarios. They are not relevant to your
case.

You must use disk blob if you deploy image on empty HDD.
Will it work? This is hard to tell but if you have imaged exactly the same
disk then is should.

Regards,
Slobodan

"David Dunning" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Sorry to bring this up again (Google Groups shows it was mentioned in
> February) but SDI2HD downloads nearly all of my .sdi file across the
> network, and then hangs - one progress bar division from the end. The
> network traffic continues, but no further accesses occur on the disk
> holding the .sdi file.
>
> I've looked all over the 'net for guidance but to no avail. Am I missing
> something in the build sequence such that the sdi image is not properly
> closed? (And can SDI2HD really make a bootable image on a blank HDD?)
>
> I have been following the MS documentation where there is no mention of
> the partition blobs I have seen in posts around here. Are they relevant?
>
> TIA
>
> David Dunning.
>