Sunday, 11 December 2011


The SDI book architecture is generally acclimated to acquiesce the use of a basic deejay via ascent Some versions of Microsoft Windows acquiesce for "RAM booting", which is about the adeptness to amount an SDI book into anamnesis and again cossack from it. The SDI book architecture additionally lends itself to arrangement booting application the Preboot Execution Environment (PXE). Another acceptance is adamantine deejay imaging. The SDI book itself is abstracted into the afterward sections:


This contains the absolute cossack program, STARTROM.COM. This is akin to the cossack area of a adamantine disk.


This about contains NTLDR and is launched by the cossack BLOB.


This contains the absolute cossack runtime (i.e. the capacity of the deejay angel including any OS files) and additionally includes the boot.ini (used by NTLDR) and files which should be amid aural the basis agenda of the runtime. The admeasurement of the runtime cannot beat 500 Mb. In accession to this claim the runtime charge additionally be able of ambidextrous with the actuality that it is booting from a ramdisk. This implies that the runtime charge accommodate the "Windows RAM Deejay Driver" basic (specified aural the boot.ini).


This is collapsed HDD angel starting with a MBR. It is acclimated for adamantine drive imaging instead of booting. Additionally alone Deejay BLOBs can be army with Microsoft's utilities.

SDI usually contains either Deejay BLOB (HD cloning or acting SDI) or three added of them (bootable SDI).

Windows Vista or Windows PE 2.0 cossack arrangement includes boot.sdi file, which contains Part BLOB for abandoned NTFS aggregate and Table-of-Contents aperture for WIM image, which is stored absolutely not central the SDI, but in abstracted on-disk file

No comments:

Post a Comment