System Deployment Image: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 14:45, 31 December 2018 edit StraussInTheHouse (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, File movers, New page reviewers, Pending changes reviewers, Rollbackers 35,927 edits m →top: has at least one reference, see info Tag: AWB ← Previous edit		Latest revision as of 23:57, 20 March 2025 edit undo Widefox (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers 110,645 edits m →top: bold alt article name per MOS,
(One intermediate revision by one other user not shown)
Line 4: }} A '''System Deployment Image''' (~~aka~~ '''SDI''') is a file format used primarily with [[Microsoft]] products to contain an arbitrary [[disk image]], including boot sector information. == Description == Line 10: The SDI file itself is partitioned into the following sections: ; Boot [[Binary large object\|BLOB]] : This contains the actual boot program, STARTROM.COM. This is analogous to the boot sector of a hard disk. ; Load BLOB : This typically contains [[NTLDR]] and is launched by the boot BLOB. ; Part BLOB : This contains the actual boot runtime (i.e. the contents of the disk image including any Operating System [OS] files) and also includes the [[boot.ini]] (used by NTLDR) and ntdetect.com files which should be located within the root directory of the runtime. The size of the runtime cannot exceed 500 MB. In addition to this requirement the runtime must also be capable of dealing with the fact that it is booting from a ramdisk. This implies that the runtime must include the "Windows [[RAM Disk]] Driver" component (specified within the boot.ini).