Windows XP Pro Home Bootable CD :: CRACK-LOCATOR.COM

Bart's way to create bootable CD-Roms (for Windows-Dos).mht: From: <Opgeslagen in Microsoft Internet Explorer 5> Subject: Bart's way to create bootable CD-Roms (for Windows/Dos) Date: Wed, 7 Jan 2004 07:02:18 +0100 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_000_0000_0 9;C3D4EC.3047FB60"; type="text/html" X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C3D4EC.3 8;47FB60 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Location: =?utf-8?Q?http://www.nu2.nu/bootcd/?= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" 2; <HTML><HEAD><TITLE>Bart's way to create boota ble CD-Roms (for = Windows/Dos)</TITLE><LINK=20 href=3D"http:/ /www.nu2.nu/style.css" type=3Dtext/css rel=3Dstylesheet> <META http-equiv=3Dcontent-type content=3D"text/html; = charset=3DUTF-8"><LINK=20 media=3Dprint href=3D"http://www.nu2.nu/bootcd/index.php?p=3D1" = rel=3Dalternate> <META content=3D"MSHTML 5.50.4807.2300" name=3DGENER ATOR></HEAD> <BODY> <TABLE cellSpacing=3D0 cellPadding=3D0 width=3D"100% " bgColor=3D#93b2fc = border=3D0> <TBODY> <TR> <TD width=3D87><A href=3D"http://www.nu2.nu/"><IMG height=3D87 = alt=3DHome=20 src=3D"http://w ww.nu2.nu/gfx/nu2top.jpg" width=3D171></A>< /TD> <TD> <TABLE cellSpacing=3D1 cellPadding=3D0 width=3D"10 0%" border=3D0> <TBODY> <TR> <TD align=3Dright height=3D66> <TABLE cellSpacing=3D0 cellPadding=3D3 border=3D0> <TBODY> <TR> <TD class=3Dbutbar> <TABLE class=3Dsponsortable cellSpacing=3D1 = cellPadding=3D1> <TBODY> <TR> <TD class=3Dsponsorhead width=3D170><A =20 title=3D"Sponsored link..." target=3D_blank=2 8; href=3D"http://www.therightstuff.org/">All the = Right=20 Stuff!!!</A></TD></TR> <TR> <TD class=3Dsponsortext>Some of the best stuf f on = the=20 web!</TD></TR> <TR> <TD class=3Dsponsortext>Free software,free = internet=20 access!</TD></TR></TBODY></TAB LE> <TD><A target=3D_blank=20 href=3D"http://www.avast.com/i_idt_154.html"></A> 0;/TD> <TD> <SCRIPT language=3DJavaScript>=0A= =0A= </SCRIPT> <SCRIPT language=3DJavaScript type=3Dtext/javascript& #62;  </SCRIPT> <SCRIPT language=3DJavaScript1.2 = type=3Dtext/javascript>  </SCRIPT> <SCRIPT language=3DJavaScript type=3Dtext/javascript& #62;  </SCRIPT> </TD></TR></TBODY ></TABLE></TD></TR> <TR> <TD height=3D14> <TABLE cellSpacing=3D0 cellPadding=3D0 width=3D540 = border=3D0> <TBODY> <TR> <TD><A class=3Dbutbar title=3DHome=20 href=3D"http://www.nu2.nu/">HOME</A> <IMG = height=3D5=20 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3D"Bootable CD"=20 = href=3D"http ://www.nu2.nu/bootablecd/">BOOTCD</A> <IMG=20 height=3D5 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DSCSI=20 href=3D"http://www.nu2.nu/scsi/">SCSI</A> <IMG = height=3D5=20 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DUtilities=20 = href=3D"http: //www.nu2.nu/utilities/">UTILITIES</A> <IMG=20 height=3D5 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DBootdisk=20 href=3D"http://www.nu2.nu/bootdisk/">BOOT = DISK</A> <IMG=20 height=3D5 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DMultimedia=20 = href=3D"http ://www.nu2.nu/multimedia/">MULTIMEDIA</A> <IMG=2 8; height=3D5 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DLinks=20 href=3D"http://www.nu2.nu/links/">LINKS</A> <IMG = height=3D5=20 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DOther=20 href=3D"http://www.nu2.nu/other/">OTHER</A> <IMG = height=3D5=20 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DSitemap=20 = href=3D"http:// www.nu2.nu/sitemap/">SITEMAP</A> <IMG=20 height=3D5 src=3D"http://www.nu2.nu/gfx/dot.gif" = width=3D3> <A=20 class=3Dbutbar title=3DAbout=20 = href=3D"http://ww w.nu2.nu/about/">ABOUT</A></TD></TR></TB ODY></TABLE></TD= ></TR></TBODY></TABLE></TD></TR>< ;/TBODY></TABLE> <DIV style=3D"LEFT: 0px; POSITION: absolute; TOP: 80px "> <HR width=3D"100%" color=3D#ff0000> </DIV> <TABLE cellSpacing=3D1 cellPadding=3D5 border=3D0> <TBODY> <TR> <TD class=3Dtop><A=20 title=3D"Printer friendly version of this page."=20 = href=3D"http ://www.nu2.nu/bootcd/index.php?p=3D1">Print</A>= </TD> <TD class=3Dtop><A title=3D"About bart..."=20 = href=3D"http ://www.nu2.nu/about/bart/">About Bart 0;/A><= /TD> <TD class=3Dtop><A=20 title=3D"When you really like what Bart is doing, try to help him, = read here..."=20 = href=3D"htt p://www.nu2.nu/thanks/bart/">Help Bart&# 60;/A><= /TD> <TD class=3Dtop><A title=3D"Click here to contact = Bart..."=20 = href=3D"ht tp://www.nu2.nu/contact/bart/">Contact Bart</B&# 62;</A></FO= NT></TD></TR></TBODY></TABLE> <DIV style=3D"MARGIN-LEFT: 18px; MARGIN-RIGHT: 18px 4;> <H1>Bart's way to create bootable CD-Roms (for = Windows/Dos)</H1>Beware of...=20 Bart's PE Builder... it's near... 0;B><A title=3D#revision=20 href=3D"http://w ww.nu2.nu/bootcd/#revision">Version = 0.48</A> Created: May=20 10, 2000 Last updated: Apr 25, 2003 <H2>Page contents</H2><A name=3DTOC></A> <TABLE class=3Dnu2tocbar> <TBODY> <TR> <TD>:: <A class=3Dnu2 toc accessKey=3Di=20 href=3D"ht tp://www.nu2.nu/bootcd/#intro">Introduction</A> & #60;FONT = color=3Dblack>:: <A class=3Dnu2toc accessKey=3Di=2& #48; href=3D"ht tp://www.nu2.nu/bootcd/#whatis">What is a bootable=20 CD-Rom?</A> :: </FONT&# 62;<A class=3Dnu2toc = accessKey=3Di=20 href=3D"ht tp://www.nu2.nu/bootcd/#howboot">How does a PC boot from = CD-Rom?=20 (technical)</A> :: </FO NT><A class=3Dnu2toc = accessKey=3Dr=20 href=3D"ht tp://www.nu2.nu/bootcd/#require">Requirements for = building the=20 examples</A> :: <A class=3Dnu2toc = accessKey=3DS=20 href=3D"ht tp://www.nu2.nu/bootcd/#cdromsi">Bootable Dos CD-Rom = (single boot=20 image) [updated! nov 4, 2002]</A>&# 60;BR>:: = <A=20 class=3Dnu2toc accessKey=3DM = href=3D"http://w ww.nu2.nu/bootcd/#cdrommi">Bootable=20 Dos CD-Rom (multiple boot images) [updated! nov 28,=20 2002]</A> <A class=3Dnu2toc = accessKey=3DC=20 href=3D"ht tp://www.nu2.nu/bootcd/#corpmb">Corporate Modboot CD-Rom = (multiple=20 boot images) [new! dec 13, 2002]</A > ::=20 <A class=3Dnu2toc accessKey=3DS=20 href=3D"ht tp://www.nu2.nu/bootcd/#clean">Clean Bootable CD-Rom = (for BIOS=20 upgrade) [new! dec 16, 2002]</A> ; :: = <A=20 class=3Dnu2toc accessKey=3DS=20 href=3D"ht tp://www.nu2.nu/bootcd/#singledemu">Single boot image=20 (Diskemu)</A> :: <A class=3Dnu2toc = accessKey=3DM=20 href=3D"ht tp://www.nu2.nu/bootcd/#multibios">Multiple boot images=20 (BIOS)</A> :: Multiple boot = images=20 (isolinux/memdisk)</A> ;:: <A = class=3Dnu2toc=20 accessKey=3DN href=3D"http://www.nu2.nu/bootcd/#nt4">Bootable = Windows NT 4.0=20 installation CD-Rom</A> :: <A = class=3Dnu2toc=20 accessKey=3DW href=3D"http://www.nu2.nu/bootcd/#w2k">Bootable = Windows 2000=20 installation CD-Rom (with SP3) [updated! dec 17, = 2002]</A> <FONT=20 color=3Dblack>:: <A class=3Dnu2toc accessKey=3DX=2& #48; href=3D"ht tp://www.nu2.nu/bootcd/#wxp">Bootable Windows XP = installation=20 CD-Rom (with SP1) [updated! dec 17, 2002]</A> <FONT=20 color=3Dblack>:: <A class=3Dnu2toc accessKey=3DE=2& #48; href=3D"ht tp://www.nu2.nu/bootcd/#elghost">Bootable Ghost restore = CD-Rom=20 "ELGHOST"</A> :: &# 60;/FONT><A class=3Dnu2toc = accessKey=3Da=20 href=3D"ht tp://www.nu2.nu/bootcd/#aboutdd">About = dd.exe</A> <FONT=20 color=3Dblack>:: <A class=3Dnu2toc accessKey=3Da=2& #48; href=3D"ht tp://www.nu2.nu/bootcd/#aboutmkisofs">About=20 mkisofs.exe</A> :: 0;/FONT><A class=3Dnu2toc = accessKey=3Da=20 href=3D"ht tp://www.nu2.nu/bootcd/#aboutmkbootcd">About=20 mkbootcd.exe</A> :: &# 60;/FONT><A = class=3Dnu2toc=20 accessKey=3Da = href=3D"http://w ww.nu2.nu/bootcd/#aboutcdrecord">About=20 cdrecord.exe</A> :: &# 60;/FONT><A = class=3Dnu2toc=20 accessKey=3Da href=3D"http://www.nu2.nu/bootcd/#aboutmake">About=20 make.exe</A> :: <A class=3Dnu2toc = accessKey=3Da=20 href=3D"ht tp://www.nu2.nu/bootcd/#aboutbootcat">About=20 bootcat.bin</A> :: </FO NT><A class=3Dnu2toc = accessKey=3Da=20 href=3D"ht tp://www.nu2.nu/bootcd/#aboutghost">About = Ghost</A> <FONT=20 color=3Dblack>:: <A class=3Dnu2toc accessKey=3Df=2& #48; href=3D"ht tp://www.nu2.nu/bootcd/#faq">Frequently asked=20 questions</A> :: <A class=3Dnu2toc = accessKey=3Dl=20 href=3D"ht tp://www.nu2.nu/bootcd/#links">Links</A> <FON T = color=3Dblack>::=20 <A class=3Dnu2toc accessKey=3Dh=20 href=3D"ht tp://www.nu2.nu/bootcd/#revision">Revision = history</A> <FONT=20 color=3Dblack>:: <A class=3Dnu2toc accessKey=3Dt=2& #48; href=3D"ht tp://www.nu2.nu/bootcd/#thanks">Thank = you</A></TD></TR></TBODY></TABLE> <H2>Welcome to <A=20 title=3Dhttp:/ /www.google.com/search?hl=3Den&safe=3Doff&q=3Dboota= ble+cd=20 target=3D_blank=20 href=3D"ht tp://www.google.com/search?hl=3Den&safe=3Doff&q=3Dboota= ble+cd">world's=20 #1</A> page about creating bootable CD-Roms for PC!</H2>< ;A name=3Dintro=20 href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG = src=3D"http://www.nu2 .nu/gfx/arrowright.gif"> Introduction</H2><BR& #62; <DIV class=3Dbig>...Bart's way of creating bootable CDs is not just = another way,=20 it is "THE SOLUTION" for your company...</DIV > You (the = technical guy)=20 can create and prepare the structure for bootable installation, = diagnostics or=20 other CDs. And anybody in your company (without any knowledge about CD = burning)=20 can create and maintain these CDs by adding or changing files when = needed. He=20 just has to start a batchfile and select "Build & burn" to create a = CD. For whom is this page? This page is for you if you want = to: <UL> <LI>create bootable CD-Roms on a regular basis=20 <LI>build and burn fully automatic (optional blank CDRW before burn)=2 0 <LI>use only freeware software to create your CDs=20 <LI>create a bootable CD-Rom with multiple boot images=20 <LI>create a Dos bootable CD-Rom using a hardware independent CD-Rom = driver=20 (for SCSI and ATAPI) </LI></UL> This page is not for you = if: <UL> <LI>you want to create just 1 simple bootable CD-Rom. You should u se = Cdrwin,=20 Nero or any other well known application to create CDs=20 <LI>you do not understand basic things like; <UL> <LI>difference between a bootdisk and a boot image=20 <LI>CDR, CDRW medium=20 <LI>unpacking, copying, editing or renaming files = </LI></UL></LI></UL>From Sep=20 5, 2002 sections will be added to this page that use <A title=3D/bcd /=20 href=3D"http://www. nu2.nu/bcd/">BCD</A> (build CD) instead of cdrpack=20 1.3. Why use BCD? Cdrpack 1.x is single user/single computer = by=20 design. BCD has multi-user/multi-computer support, you can put BCD on = your=20 fileserver and run it from any workstation, no need to install any files = on the=20 workstation. <A name=3Dwhatis = href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> What is a = bootable=20 CD-Rom?</H2> A bootable CD-Rom is a CD from which you boot th e PC. = This means=20 putting the CD in your CD-Rom drive and power-on or reboot your system. = The PC=20 will load a boot image from the CD-Rom and control is given to this boot = image. A bootable CD-Rom is not a CD that you insert into = your=20 CD-Rom drive and windows will start something from this CD-Rom. This = is=20 called an "autoplay" CD-Rom. I've just put this informati on here so = that=20 people who do not known the difference between a bootable and a = "autoplay"=20 CD-Rom can leave this page and look here: <A title=3D/links#autorun=20 href=3D"http://www .nu2.nu/links#autorun">NU2-links: autorun</A>. &# 60;A=20 name=3Dhowboot href=3D"http://www.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> How does a = PC boot=20 from CD-Rom? (technical)</H2> A PC can boot from a CD-Rom if the PCs = BIOS=20 supports the <A title=3D http://www.phoenix.com/resources/specs-cdrom.pdf = target=3D_blank = href=3D"http://www.phoen ix.com/resources/specs-cdrom.pdf">El Torito=20 Bootable CD-ROM Format Specification v1.0</A>. This s pecification = provides a=20 way of getting to the location on the CD that will provide the boot = information,=20 while maintaining ISO-9660 compatibility. <IM G=20 alt=3D"El Torito is not mexican food, it is the bootable CD-Rom = specification"=20 src=3D"http://www.nu2 .nu/gfx/bootcd_logo.gif" align=3Dright> The El = Torito=20 specification was created in january 1995, by Curtus E. Stevens = (Phoenix) and=20 Stan Merkin (back then IBM). And it was called after a restaurant, the = "El=20 Torito grill", where they went to eat and talk about bootable CD-Roms. = <A=20 title=3Dhttp://www.cdpage.com/Compact_Disc_Variations/danaboot.htm l = target=3D_blank=20 href=3D"http://www.cdpage.com/Compact_Disc_Variations/danaboot .html">Clic= k here=20 for the full story...</A> The ISO-9660 de fines that a "Primary = Volume=20 Descriptor" must reside at sector 10h (16 decimal), relative to the = start of the=20 session. The El Torito specification uses a <A title=3D#bootrecord=20 href=3D"http://w ww.nu2.nu/bootcd/#bootrecord">Boot Record</A> Volume = Descriptor.=20 This Boot Record must be located at sector 11h (17 decima l) in the = last=20 session of the CD. The boot record contains a n absolute = pointer to=20 the boot catalog. This catalog allows the system to pick a proper boot = image to=20 boot from. Boot Record Volume Descriptor <A=20 name=3Dbootrecord></A> <TABLE class=3Dnu2table cellSpacing=3D1 cellPadding=3D2> <TBODY> <TR class=3Dnu2tr> <TH class=3Dnu2th>Offset</TH> <TH class=3Dnu2th>Type</TH> <TH class=3Dnu2th>Description</TH></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>0</TD> <TD class=3Dnu2td>Byte</TD> <TD class=3Dnu2td>Boot record Indicator, must be 0</TD>& #60;/TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>1-5</TD> <TD class=3Dnu2td>Byte</TD> <TD class=3Dnu2td>ISO-9660 Identifier, must be "CD0& #48;1"</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>6</TD> <TD class=3Dnu2td>Byte</TD> <TD class=3Dnu2td>Version of this descriptor, must be 1</TD& #62;</TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>7-26</TD> <TD class=3Dnu2td>Byte</TD> <TD class=3Dnu2td>Boot system identifier, must be "EL TORITO = SPECIFICATION"=20 padded with 0's.</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>27-46</TD> <TD class=3Dnu2td>Byte</TD> <TD class=3Dnu2td>Unused, must be 0</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>47-4A</TD> <TD class=3Dnu2td>Dword</TD> <TD class=3Dnu2td>Absolute pointer to first sector of Boot = catalog.</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>4A-7FF</TD> <TD class=3Dnu2td>Byte</TD> <TD class=3Dnu2td>Unused, must be = 0</TD></TR></TBODY></TABLE> <DIV class=3Dbig align=3Dcenter>...BIOS vendors do not implement the = full El Torito=20 specification...</DIV> This all sounds very great , a nice and = clear=20 specification about bootable CD-Roms and if all BIOS vendors would = implement the=20 complete specification, there would be nothing to worry a bout. = But the=20 BIOS vendors do no follow the full El Torito specification! <BR&# 62;Below = is a=20 list of my findings, and if it is supported on all system s or=20 not... (I'm not sure if 100% correct) < ;BR> <TABLE class=3Dnu2table cellSpacing=3D1 cellPadding=3D2> <TBODY> <TR class=3Dnu2tr> <TH class=3Dnu2th>Description</TH> <TH class=3Dnu2th>What systems support it?</TH></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Single boot image configuration</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Multiple boot image configuration</TD> <TD class=3Dnu2td>Some</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Boot record volume descriptor</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Validation entry</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Boot Indicator 88 "Bootable"</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Boot Indicator 00 "Not bootable"&# 60;/TD> <TD class=3Dnu2td>None</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Boot media type 0 "No emulation"</ TD> <TD class=3Dnu2td>All <A title=3D#aha2940note=20 href=3D"ht tp://www.nu2.nu/bootcd/#aha2940note">*1</A>< /TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Boot media type 1,2,3 "Floppy emulation 4;</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Boot media type 4 "Harddisk emulation"< ;/TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Sector count</TD> <TD class=3Dnu2td>Many <A title=3D#sectornote=20 href=3D"ht tp://www.nu2.nu/bootcd/#sectornote">*2</A></TD>< /TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Load RBA</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Header indicator</TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Platform ID</TD> <TD class=3Dnu2td>Many <A title=3D#platformnote=20 href=3D"ht tp://www.nu2.nu/bootcd/#platformnote">*3</A></TD> 0;/TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>ID string</TD> <TD class=3Dnu2td>Some <A title=3D#idstringnote=20 href=3D"ht tp://www.nu2.nu/bootcd/#idstringnote">*4</A></TD> 0;/TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Section entry extensions</TD> <TD class=3Dnu2td>I've never used it</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Int 13 function 4A - Initiate disk emulation&# 60;/TD> <TD class=3Dnu2td>None <A title=3D#int13note=20 href=3D"ht tp://www.nu2.nu/bootcd/#int13note">*5</A></TD>&# 60;/TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Int 13 function 4B - Terminate disk emulation& #60;/TD> <TD class=3Dnu2td>All</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Int 13 function 4C - Initiate disk emulation a nd = boot</TD> <TD class=3Dnu2td>None <A title=3D#int13note=20 href=3D"ht tp://www.nu2.nu/bootcd/#int13note">*5</A></TD>&# 60;/TR> <TR class=3Dnu2tr> <TD class=3Dnu2td>Int 13 function 4D - Return boot catalog</ TD> <TD class=3Dnu2td>Some</TD></TR></TBODY>< ;/TABLE> <TABLE class=3Dnu2table cellSpacing=3D1 cellPadding=3D2> <TBODY> <TR class=3Dnu2tr> <TD class=3Dnu2td><A name=3Daha2940note></A> *1</TD> <TD class=3Dnu2td>Adaptec aha2940 supports no emulation mode from = firmware=20 revision 1.25</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td><A name=3Dsectornote></A>*2</T D> <TD class=3Dnu2td>Some systems do not support reading more than 1 ;=20 sector</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td><A name=3Dplatformnote></A>*3< /TD> <TD class=3Dnu2td>Some systems do not check the platform = ID</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td><A name=3Didstringnote></A>*4< /TD> <TD class=3Dnu2td>I've only seen adaptec SCSI adapters support = this</TD></TR> <TR class=3Dnu2tr> <TD class=3Dnu2td><A name=3Dint13note></A>*5< ;/TD> <TD class=3Dnu2td>This one hurts, I wanted to use this function=2 8; badly</TD></TR></TBODY></TABLE> 0;BR>New mainboards come out all the = time. I=20 see that more and more new mainboards do not support mult iboot = images=20 configurations. <A name=3Drequire = href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Requirements = for=20 building the examples</H2> This is what you need:=20 <OL> <LI>PC running Windows NT 4.0 SP4+, Windows 2000 or Wi ndows XP.=20 <LI>SCSI or ATAPI based CD-recorder or rewriter.=20 <LI>ASPI manager (see also: <A title=3D/aspi/=20 href=3D"http://w ww.nu2.nu/aspi/">Bart's page about ASPI</A>).=20 <LI>1 recordable (CDR) or rewritable (CDRW) CD, at firs t try, use a = rewritable if you can.=20 <LI>To test if the completed CD works, you'll need a PC capable of = booting=20 CD-Roms.=20 <LI>Some basic skills for copying, unpacking and editing some files.=2 0 </LI></OL><A name=3Dcdromsi href=3D"http://www.nu2.nu/bootcd/#TOC"&# 62;</A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Bootable Dos = CD-Rom=20 (single boot image) [updated! nov 4, 2002]</H 2> This will = create a=20 bootable CD-Rom using one boot image. The boot image is a sector by = sector image=20 taken from a bootable floppy. When a PC boots from floppy this is = normally done=20 from the first floppy drive, known as drive number 0 or as drive A:. So, = to let=20 the CD-Rom boot there must be some mechanism that emulates a floppy = drive (drive=20 number 0). Using this method your PC BIOS provides th e emulation = for=20 you. If you are unsure or confused by the information on this page = then this=20 example is probably what you are looking for. This e xample will = use the=20 <A title=3D/bootdisk/cdrom/ = href=3D" http://www.nu2.nu/bootdisk/cdrom/">CD-Rom boot=20 disk</A>. The steps to create are: <OL> <LI>If you haven't already installed BCD, please do so now. BCD=20 installation instructions: Download <A= 20 title=3D/download.php?sFile=3Dbcd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcd111.zip"> BCD full = package=20 v1.1.1</A> (523KB). Or update from previous version: <A=20 title=3D/download.php?sFile=3Dbcdupd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcdupd111.zip"&# 62;BCD = update package=20 (v1.1.0-v1.1.1)</A> (5KB). Whe n updating from previous = versions, just=20 extract the package over the previous version, overwrite any existin g = files.=20 The <TT>bcd.cfg</TT> file will not get overwritten! ; Unpack the = BCD=20 package to some folder for example <TT>d:\bcd</TT>. If yo u want to be = able to=20 run it from a server you should unpack it to a share from where your=20 workstations can run it. You will need to map a drive letter to that = share and=20 run bcd using that drive letter. Make sure you also unpack the=2 8; subdirectories! Download <A = title=3Dftp://ftp.nero.com/wnaspi32.dll=20 target=3D_blank href=3D"ftp://ftp.nero.com/wnaspi32.dll">Nero Aspi = Library=20 (wnaspi32.dll)</A> and copy it into BCD's <TT>d:\bcd\bin&# 60;/TT>=20 directory. I have asked Ahead Software AG if I could di stribute = their=20 aspi manager with my BCD package but they said: "...due to our = licence=20 agreement you could only let your users download it freely from our = web=20 site...". <LI>If you haven't already installed BFD, please do so now. BFD=20 installation instructions: Please download: <A=20 title=3D/download.php?sFile=3Dbfd107.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbfd107.zip">BFD full = package=20 v1.0.7</A> (1.45MB). Or update from previous versions: <A=20 title=3D/download.php?sFile=3Dbfdupd107.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbfdupd107.zip">B FD = update package=20 (v1.0.x-v1.0.7)</A> (410KB).<BR& #62;When updating from previous = versions,=20 just extract the package over the previous version, overwrite any = existing=20 files. The <TT>bfd.cfg</TT> file will not get = overwritten! Unpack BFD=20 in the same directory as BCD, for example <TT>d:\bcd</TT> . If you = have=20 already unpacked BCD, then some files from BFD will overlap with files = from=20 BCD, like the <TT>nu2lic.txt</TT> and the <TT>bch oice.exe</TT>. This = is no=20 problem, just skip or overwrite them. Make sure you also unpack the = subdirectories! <LI>Download <A title=3D/download.php?sFile=3Dcdromsi.zip=20 = href=3D"http://www.nu2.nu/download.php?sFile=3Dcdromsi.zip">cdromsi.zip = (updated=20 Nov 4, 2002)</A> (1KB) and unpack it into the same fo lder as = where you=20 have installed BCD/BFD. <LI>Now you can customize things like: <UL> <LI>Adding programs and files to "cds\cdromsi\files\" folder . These = will=20 appear in the root of your CD-Rom filesystem.=20 <LI>Change the file "cds\cdromsi\files\autorun.bat" you can add any = commands=20 you want, like starting some application that is located on the = CD-Rom.=20 </LI></UL> <LI>When you're done customizing, you open a command prompt, chang e to = the BCD=20 folder and run "bcd cdromsi" to build your ISO image and burn it to = your CD=20 writer (if you have one). </LI></OL>Was n't that simple or=20 what?!? <A name=3Dcdrommi = href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Bootable Dos = CD-Rom=20 (multiple boot images) [updated! nov 28, 2002] 0;/H2> <IMG = alt=3D"NU2 Tux"=20 src=3D"http://www.nu2 .nu/gfx/nu2tux.gif" align=3Dright> This will show = you how to=20 build a multiboot CD-Rom using isolinux and memdisk. Memdisk simulates a = disk by=20 claiming a chunk of high memory for the disk and a (very small - 2K = typical)=20 chunk of low (DOS) memory for the driver itself, then hooking the INT = 13h (disk=20 driver) and INT 15h (memory query) BIOS interrupts. Memdisk is very=20 fast! Note: some people think this section is for linu 0; only... = Wrong! it=20 is also for MS-Dos and other OSes. Note: < ;B>you cannot build = an ISO=20 image that boots isolinux.bin correctly using nero, cdrwin or other = buyware=20 recording software, you have to use bcd (you can record the = generated ISO=20 image generate by bcd using nero, cdrwin or others). This example = uses=20 the <A title=3D/bootdisk/cdrom/ = href=3D" http://www.nu2.nu/bootdisk/cdrom/">CD-Rom=20 boot disk</A>. This example uses the <A title=3D/boo tdisk/network/=20 href=3D"http://www.nu2.nu/bootdisk/network/">Network boot = disk</A>. This=20 example uses the <A = title=3Dhttp://home.eune t.no/~pnordahl/ntpasswd/bootdisk.html=20 target=3D_blank=20 href=3D"http://home. eunet.no/~pnordahl/ntpasswd/bootdisk.html">Offline = NT Password=20 & Registry Editor, Bootdisk</A> (c) 1998-2001 ; Petter Nordahl-Hagen = (GNU-GPL=20 license). NOTE: The 'chntpw' binary contains crypt ograhic = algorithms, like=20 DES and others, which may be illegal to re-export from your = country. <TABLE class=3Dnu2table cellSpacing=3D1> <TBODY> <TR> <TH class=3Dnu2th>screen shot</TH></TR> <TR> <TD class=3Dnu2td><PRE> = =20 = =20 ISOLINUX 2.00 2002-10-25 Copyright (C) 1994 -2002 H. Peter Anvin = =20 = =20 Bart's way to create bootable CD-Roms = =20 Bootable Dos CD-Rom (multiple boot image) = =20 http://www.nu2.nu/bo otcd/ = =20 = =20 Choose system/configuration to boot... = =20 Pressing [Enter] defaults to item "0" = =20 = =20 0) Boot from first harddisk (drive 80h) = =20 = =20 1) Boot Dos with CD-Rom support = =20 2) Boot Dos with Network support = =20 3) Offline NT Password & Registry Editor, Bootdisk (linux) = =20 = =20 a) Boot from first floppy drive (drive 0h) = =20 q) Skip CD-Rom boot (boot next device) = =20 = =20 Type selection at boot prompt = =20 Timeout: 20 seconds = =20 = =20 boot: = =20 </PRE></TD></TR></TBODY></TAB LE>(screen created with <A = title=3D/scr2htm=20 href=3D"http://w ww.nu2.nu/scr2htm">scr2htm</A>) The s teps to = create=20 are: <OL> <LI>If you haven't already installed BCD, please do so now. BCD=20 installation instructions: Download <A= 20 title=3D/download.php?sFile=3Dbcd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcd111.zip"> BCD full = package=20 v1.1.1</A> (523KB). Or update from previous version: <A=20 title=3D/download.php?sFile=3Dbcdupd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcdupd111.zip"&# 62;BCD = update package=20 (v1.1.0-v1.1.1)</A> (5KB). Whe n updating from previous = versions, just=20 extract the package over the previous version, overwrite any existin g = files.=20 The <TT>bcd.cfg</TT> file will not get overwritten! ; Unpack the = BCD=20 package to some folder for example <TT>d:\bcd</TT>. If yo u want to be = able to=20 run it from a server you should unpack it to a share from where your=20 workstations can run it. You will need to map a drive letter to that = share and=20 run bcd using that drive letter. Make sure you also unpack the=2 8; subdirectories! Download <A = title=3Dftp://ftp.nero.com/wnaspi32.dll=20 target=3D_blank href=3D"ftp://ftp.nero.com/wnaspi32.dll">Nero Aspi = Library=20 (wnaspi32.dll)</A> and copy it into BCD's <TT>d:\bcd\bin&# 60;/TT>=20 directory. I have asked Ahead Software AG if I could di stribute = their=20 aspi manager with my BCD package but they said: "...due to our = licence=20 agreement you could only let your users download it freely from our = web=20 site...". <LI>If you haven't already installed BFD, please do so now. BFD=20 installation instructions: Please download: <A=20 title=3D/download.php?sFile=3Dbfd107.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbfd107.zip">BFD full = package=20 v1.0.7</A> (1.45MB). Or update from previous versions: <A=20 title=3D/download.php?sFile=3Dbfdupd107.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbfdupd107.zip">B FD = update package=20 (v1.0.x-v1.0.7)</A> (410KB).<BR& #62;When updating from previous = versions,=20 just extract the package over the previous version, overwrite any = existing=20 files. The <TT>bfd.cfg</TT> file will not get = overwritten! Unpack BFD=20 in the same directory as BCD, for example <TT>d:\bcd</TT> . If you = have=20 already unpacked BCD, then some files from BFD will overlap with files = from=20 BCD, like the <TT>nu2lic.txt</TT> and the <TT>bch oice.exe</TT>. This = is no=20 problem, just skip or overwrite them. Make sure you also unpack the = subdirectories! <LI>Download <A title=3D/download.php?sFile=3Dcdrommi.zip=20 = href=3D"http://www.nu2.nu/download.php?sFile=3Dcdrommi.zip">cdrommi.zip&# 60;/= A> (16KB)=20 and unpack it into the same folder as where you have installed=20 BCD/BFD. <LI>To enable option 3 you must download the <A=20 title=3Dhttp://ntp ass.blaa.net/bd011022.zip target=3D_blank=20 href=3D"http:/ /ntpass.blaa.net/bd011022.zip">Offline NT Password & amp; = Registry=20 Editor, Bootdisk</A>. Unzip the <TT>bd011022.z ip</TT> file and extract = the=20 files from the <TT>bd011022.bin</TT> floppy im age using <A=20 title=3Dhttp://www.w inimage.com target=3D_blank=20 href=3D"http:// www.winimage.com/">winimage</A>. Copy the files = <TT>vmlinuz</TT>=20 and <TT>initrd.gz</TT> files into the = <TT>cds\cdrommi\files\chntpw\</TT>=20 folder. <LI>Now you can customize things like: <UL> <LI>Adding programs and files to "cds\cdrommi\files\" folder . These = will=20 appear in the root of your CD-Rom filesystem.=20 <LI>Change the file "cds\cdrommi\files\autorun.bat" you can add any = commands=20 you want, like starting some application that is located on the = CD-Rom. By=20 default the path is set to %cddrv%\ and %cddrv%\bin (where %cddrv%=20 environment variable is set to your CD-Rom driveletter). = </LI></UL> <LI>When you're done customizing, you open a command prompt, chang e to = the BCD=20 folder and run "bcd cdrommi" to build your ISO image and burn it to = your CD=20 writer (if you have one). </LI></OL>Was n't that also simple or=20 what?!? <A name=3Dcorpmb = href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Corporate = Modboot=20 CD-Rom (multiple boot images) [new! dec 13, 2002]</B& #62;</H2> So, you = wanna=20 create a monster bootable CD-Rom? Containing things like: <UL> <LI>Disktool=20 <LI>Volkov Commander v5=20 <LI>Symantec Ghost=20 <LI>PowerQuest PartitionMagic=20 <LI>Winternals ERD Commander 2002=20 <LI>Virus scanner, Mcafee or F-Prot=20 <LI>NTFS Dos/Pro=20 <LI>PCI bus scanner=20 <LI>Bios/chipset detect </LI></UL>Checkout the <A = title=3D/corpmodboot/=20 href=3D"htt p://www.nu2.nu/corpmodboot/">Corporate Modboot</A> = page. <A=20 name=3Dclean href=3D"http://www.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Clean = Bootable CD-Rom=20 (for BIOS upgrade) [new! dec 16, 2002]</H 2> Some people ask me = if it=20 is possible to create a bootable CD-Rom to update/flash their BIOS, on a = system=20 that has no floppy disk drive. I realize that some new PC's nowadays = also don't=20 have a floppy drive so this problem may affect more people in future... = This is=20 probably is easiest bootable CD-Rom I've ever built. This Clean = Bootable=20 CD-Rom can be used for flashing your BIOS or other programs that need to = be run=20 from a "clean-booted" Dos operating system. The s teps to create = are: <OL> <LI>If you haven't already installed BCD, please do so now. BCD=20 installation instructions: Download <A= 20 title=3D/download.php?sFile=3Dbcd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcd111.zip"> BCD full = package=20 v1.1.1</A> (523KB). Or update from previous version: <A=20 title=3D/download.php?sFile=3Dbcdupd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcdupd111.zip"&# 62;BCD = update package=20 (v1.1.0-v1.1.1)</A> (5KB). Whe n updating from previous = versions, just=20 extract the package over the previous version, overwrite any existin g = files.=20 The <TT>bcd.cfg</TT> file will not get overwritten! ; Unpack the = BCD=20 package to some folder for example <TT>d:\bcd</TT>. If yo u want to be = able to=20 run it from a server you should unpack it to a share from where your=20 workstations can run it. You will need to map a drive letter to that = share and=20 run bcd using that drive letter. Make sure you also unpack the=2 8; subdirectories! Download <A = title=3Dftp://ftp.nero.com/wnaspi32.dll=20 target=3D_blank href=3D"ftp://ftp.nero.com/wnaspi32.dll">Nero Aspi = Library=20 (wnaspi32.dll)</A> and copy it into BCD's <TT>d:\bcd\bin&# 60;/TT>=20 directory. I have asked Ahead Software AG if I could di stribute = their=20 aspi manager with my BCD package but they said: "...due to our = licence=20 agreement you could only let your users download it freely from our = web=20 site...". <LI>If you haven't already installed BFD, please do so now. BFD=20 installation instructions: Please download: <A=20 title=3D/download.php?sFile=3Dbfd107.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbfd107.zip">BFD full = package=20 v1.0.7</A> (1.45MB). Or update from previous versions: <A=20 title=3D/download.php?sFile=3Dbfdupd107.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbfdupd107.zip">B FD = update package=20 (v1.0.x-v1.0.7)</A> (410KB).<BR& #62;When updating from previous = versions,=20 just extract the package over the previous version, overwrite any = existing=20 files. The <TT>bfd.cfg</TT> file will not get = overwritten! Unpack BFD=20 in the same directory as BCD, for example <TT>d:\bcd</TT> . If you = have=20 already unpacked BCD, then some files from BFD will overlap with files = from=20 BCD, like the <TT>nu2lic.txt</TT> and the <TT>bch oice.exe</TT>. This = is no=20 problem, just skip or overwrite them. Make sure you also unpack the = subdirectories! <LI>Download <A title=3D/download.php?sFile=3Dclean10.zip= 20 href=3D"http://www.nu2.nu/download.php?sFile=3Dclean10.zip">Cle an v1.0 = package=20 (clean.zip)</A> (2KB) and unpack it into the same folder as where = you=20 have installed BCD/BFD. <LI>Add the files needed to upgrade your BIOS to = <TT>cds\clean\bootdisk\</TT>=20 folder. You have about 2.5MB available space on the bootimage (2.88MB = floppy=20 emulation). Do not add your files to <TT>cds\cl ean\files\</TT>=20 folder! Optionally you can edit the file=20 <TT>cds\clean\bootdisk\autorun.bat</TT> and append a line to r un your = flash=20 program. <LI>When you're done customizing, you open a command prompt, chang e to = the BCD=20 folder and run "bcd clean" to build your ISO image and burn it to your = CD=20 writer (if you have one). </LI></OL> 0;B>Warning! Use this = Clean=20 Bootable CD-Rom at your own risk. I only tried Asus <TT>aflash.exe& #60;/TT> = flash=20 program and that works OK! <A name=3Dsingledemu=20 ; href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Single boot = image=20 (Diskemu)</H2> Using this method a special program called 4;diskem1x" = is=20 loaded first and that program will provide the emulation for the boot = images.=20 Use this if you want to boot "dos" based operating systems like Dos = 5.x/6.x,=20 Windows 9x, Windows ME... The advantage of using diskem1 x is that it = works=20 together with a special Dos CD-Rom driver, called "eltorito.sys", which = is based=20 on INT13 extensions and is hardware independent (more info on this look = <A=20 title=3D/diskemu/ = href=3D"http:// www.nu2.nu/diskemu/">here</A>). The s teps to=20 create are: <OL> <LI>If you have not already setup cdrpack version 1.3 then downloa d <A = title=3D/download.php?sFile=3Dcdrpack13.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dcdrpack13.zip">cdrpa ck=20 v1.3</A> (624KB). This file contains a workspace w here you can = build=20 your bootable CD's from. Unpack the cdrpack13.zip file to a = directory on=20 your local harddisk. Make sure you expand the subdi rectories! So = when=20 using pkunzip.exe use the -d option! <LI>If you have not already setup diskemu add-on, version 1.1 = (11/07/01) then=20 download <A title=3D/download.php?sFile=3Ddiskemu_addon.zip=20 = href=3D"http://www.nu2.nu/download.php?sFile=3Ddiskemu_addon.zip">diskemu = =20 add-on</A> (11KB). Unpack the diskemu_addon.zi p file into the=20 same directory as cdrpack 1.3. <LI>Download <A title=3D/download.php?sFile=3Dsingle_diskemu_addon .zip = = href=3D"http://www.nu2.nu/download.php?sFile=3Dsingle_diskemu_addon.zip"> = single=20 diskemu add-on</A> (2KB). Unpack the single_diskemu_addon.zip = file into=20 the same directory as cdrpack 1.3. Make sure you expand = the=20 subdirectories! So when using pkunzip.exe use the -d = option! <LI>Follow the steps in the <A title=3D/bootdisk/cdrom/=20 href=3D"http://www.nu2.nu/bootdisk/cdrom/">CD-Rom boot disk</A> pa ge = to create=20 the CD-Rom boot disk bootdisk. Create a boot image file from the = "CD-Rom=20 boot disk" bootdisk using <A title=3D#aboutdd=20 href=3D"http:/ /www.nu2.nu/bootcd/#aboutdd">dd.exe</A>, you should cal l = this boot=20 image "cdrom.img" and put it into the "cds\single_diskemu\disk1 ;"=20 directory. Note! You have to rename the boot image to=2& #48; lowercase! <LI>All other files and folders you want in the CD-Rom filesystem must = also be=20 copied into cds\single_diskemu\disk1 directory. <LI>Customize the file cds\single_diskemu\disk1\diskemu.cmd for yo ur = personal=20 needs. <LI>Change cds\single_diskemu\disk1\autorun.bat you can add any = commands you=20 want. For example start an application from CD-Rom. Edit the file cds\single_diskemu\build.mak and put your name into = the=20 "preparer" variable. <LI>Start the batch file "run.bat". From the "M ain menu" select = "Build=20 & Burn" and "single_diskemu". </LI& #62;</OL>Good = luck! <A=20 name=3Dmultibios href=3D"http://www.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Multiple = boot images=20 (BIOS)</H2> This example goes about creating a bootable CD-Rom using = multiple=20 boot images in floppy emulation. You can build your own boot images, = or add=20 more images if you like. <H2>Warning!</H2>It is possible that your BIOS does n ot support El = Torito=20 multiple boot image configuration! There is no easy way to check. When = your PC=20 boots only the first image, your BIOS does not support = multiboot! The=20 boot images used in this example are: <UL> <LI>cdrom.img - <A title=3D/bootdisk/cdrom/=20 href=3D"http://www.nu2.nu/bootdisk/cdrom/">CD-Rom boot disk</A>=2& #48; <LI>msnet.img - <A title=3D/bootdisk/network/=20 href=3D"http://www.nu2.nu/bootdisk/network/">Network boot disk</A 2;=20 <LI>scsitool.img - <A title=3D/scsitool/makedisk/=20 href=3D"http://www.nu2.nu/scsitool/makedisk/">SCSITOOL bootdisk</A& #62;=20 <LI>cpuid.img - <A=20 title=3Dhttp://support.intel.com/support/processors/tools/fre quencyid/ = target=3D_blank=20 = href=3D"http://support.intel.com/support/processors/tools/f requencyid/">T= he=20 Intel=C2=AE=C2=AE Processor Frequency ID Utility</A> </LI>< ;/UL> <OL> <LI>If you have not already setup cdrpack version 1.3 then downloa d <A = title=3D/download.php?sFile=3Dcdrpack13.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dcdrpack13.zip">cdrpa ck=20 v1.3</A> (624KB). This file contains a workspace w here you can = build=20 your bootable CD's from. Unpack the cdrpack13.zip file to a = directory on=20 your local harddisk. Make sure you expand the subdi rectories! So = when=20 using pkunzip.exe use the -d option! <LI>Download <A title=3D/download.php?sFile=3Dmulti_eltorito_addon .zip = = href=3D"http://www.nu2.nu/download.php?sFile=3Dmulti_eltorito_addon.zip"> = multi=20 eltorito add-on</A> (1KB). Unpack the multi_eltorito_addon.zi p = file into=20 the same directory as cdrpack 1.3. Make sure you expand = the=20 subdirectories! So when using pkunzip.exe use the -d = option! <LI>Follow the steps in the <A title=3D/bootdisk/cdrom/=20 href=3D"http://www.nu2.nu/bootdisk/cdrom/">CD-Rom boot disk</A> pa ge = to create=20 the CD-Rom boot disk bootdisk. Create a boot image file from the = "CD-Rom=20 boot disk" bootdisk using <A title=3D#aboutdd=20 href=3D"http:/ /www.nu2.nu/bootcd/#aboutdd">dd.exe</A>, you should cal l = this boot=20 image "cdrom.img" and put it into the "cds\multi_eltorito\disk1 ;"=20 directory. Note! You have to rename the boot image to=2& #48; lowercase! <LI>Follow the steps in the <A title=3D/bootdisk/network/=20 href=3D"http://www.nu2.nu/bootdisk/network/">Network boot disk</A 2; = page to=20 create the Network boot disk bootdisk. Create a boot image file = from the=20 "Network boot disk" bootdisk using <A title=3D#aboutdd=20 href=3D"http:/ /www.nu2.nu/bootcd/#aboutdd">dd.exe</A>, you should cal l = this boot=20 image "msnet.img" and put it into the "cds\multi_eltorito\disk1 ;"=20 directory. Note! You have to rename the boot image to=2& #48; lowercase! <LI>Follow the steps in the <A title=3D/scsitool/makedisk/=20 href=3D"http://www.nu2.nu/scsitool/makedisk/">SCSITOOL</A> page to = create the=20 SCSITOOL bootdisk. Create a boot image file from the "SCSITOOL& #34; = bootdisk=20 using <A title=3D#aboutdd = href=3D"http://w ww.nu2.nu/bootcd/#aboutdd">dd.exe</A>,=20 you should call this boot image "scsitool.img" and put it into the=2&# 48; "cds\multi_eltorito\disk1" directory. Note! You have to rename = the boot=20 image to lowercase! <LI>Follow the steps in the <A=20 title=3Dhttp://support.intel.com/support/processors/tools/fre quencyid/ = target=3D_blank=20 = href=3D"http://support.intel.com/support/processors/tools/f requencyid/">C= PUID</A>=20 page to create the CPUID bootdisk. Create a boot image file from = the=20 "CPUID" bootdisk using <A title=3D#aboutdd=20 href=3D"http:/ /www.nu2.nu/bootcd/#aboutdd">dd.exe</A>, you should cal l = this boot=20 image "cpuid.img" and put it into the "cds\multi_eltorito\disk1 ;"=20 directory. Note! You have to rename the boot image to=2& #48; lowercase! <LI>All other files and folders you want in the CD-Rom filesystem must = also be=20 copied into cds\multi_eltorito\disk1 directory. <LI>Change cds\multi_eltorito\disk1\autorun.bat you can add any = commands you=20 want. For example start an application from CD-Rom. Edit the file cds\multi_eltorito\build.mak and put your name into = the=20 "preparer" variable. <LI>Start the batch file "run.bat". From the "M ain menu" select = "Build=20 & Burn" and "multi_eltorito". </LI& #62;</OL>Done! <A=20 name=3Dmultimemdisk href=3D"http://www.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Multiple = boot images=20 (isolinux/memdisk)</H2> <IMG alt=3D"NU2 Tux "=20 src=3D"http://www.nu2 .nu/gfx/nu2tux.gif" align=3Dright> This will show = you how to=20 build a multiboot CD-Rom using isolinux and memdisk. Memdisk simulates a = disk by=20 claiming a chunk of high memory for the disk and a (very small - 2K = typical)=20 chunk of low (DOS) memory for the driver itself, then hooking the INT = 13h (disk=20 driver) and INT 15h (memory query) BIOS interrupts. Memdisk is very=20 fast! Note: some people think this section is for linu 0; only... = Wrong! it=20 is also for MS-Dos and other OSes. Note: 0;B>you cannot build = an ISO=20 image that boots isolinux.bin correctly using nero, cdrwin or other = buyware=20 recording software, you have to use cdrpack/mkisofs (you can record = the=20 generated ISO image generate by cdrpack/mkisofs using nero, cdrwin or = others). I=20 will create a patched version of isolinux.bin that can also be used with = nero or=20 so when I have some spare time. The boot images used in t his = example=20 are: <UL> <LI>cdrom.img - <A title=3D/bootdisk/cdrom/=20 href=3D"http://www.nu2.nu/bootdisk/cdrom/">CD-Rom</A>=20 <LI>msnet.img - <A title=3D/bootdisk/network/=20 href=3D"http://www.nu2.nu/bootdisk/network/">Network</A>=20 <LI>tomsrtbt.img (Eltorito.288) - <A title=3Dhttp://www.toms.net/rb/=20 target=3D_blank href=3D"http://www.toms.net/rb/">The most linux on one = disk - by=20 Tom Oehser</A> </LI></UL>You can build your own boot i mages, or add = more images=20 if you like. The steps to create are: <OL> <LI>If you have not already setup cdrpack version 1.3 then downloa d <A = title=3D/download.php?sFile=3Dcdrpack13.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dcdrpack13.zip">cdrpa ck=20 v1.3</A> (624KB). This file contains a workspace w here you can = build=20 your bootable CD's from. Unpack the cdrpack13.zip file to a = directory on=20 your local harddisk. Make sure you expand the subdi rectories! So = when=20 using pkunzip.exe use the -d option! <LI>Download <A title=3D/download.php?sFile=3Dmulti_memdisk_addon. zip=20 = href=3D"http://www.nu2.nu/download.php?sFile=3Dmulti_memdisk_addon.zip">m = ulti=20 memdisk add-on</A> (14KB). Unpack the multi_memdisk_addon.zip = file into=20 the same directory as cdrpack 1.3. Make sure you expand = the=20 subdirectories! So when using pkunzip.exe use the -d = option! The=20 addon contains: <A title=3Dhttp://syslinux.zytor.com/ = target=3D_blank=20 href=3D"http://syslinux.zytor.com/">ISOLINUX 1.67 and MEMDISK 1.67</A> = Copyright=20 2001 H. Peter Anvin. The isolinux is a little bit modified by = <A=20 title=3D/contact/bart/ href=3D"http://www.nu2.nu/contact/bart/">Bart = Lagerweij</A>=20 to support loading of NT CD-Rom bootsectors (.bin files). If you = want to=20 add loading of Windows NT4/2000/XP bootsectors or other applicatio ns = that=20 build on the NT bootsector, like ERD commander, you must add the = following=20 lines to the isolinux.cfg file: <PRE>label 9 kernel w2ksect.bin </PRE> Note! file must have ".bin" ex tension, not .dat like in the = Windows 2000 example. A bo otmsg.txt file, this will create = a screen=20 similar to the one seen below:=20 <TABLE class=3Dnu2table cellSpacing=3D1> <TBODY> <TR> <TH class=3Dnu2th>bootmsg.txt - output</TH></TR&# 62; <TR> <TD class=3Dnu2td><PRE> = =20 ISOLINUX 1.68 0x3c7f7718 Copyright (c) 1994-20 02 H. Peter Anvin = =20 = =20 =E2=94=8C=E2=94=80=E2=94=80=E2=94=80 ;=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=8 8;=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=& #57;4=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=8 0=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=8 8;=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=90 0;SPAN style=3D"BACKGROUND: #000000; = COLOR: #ffffff"> =20 =E2=94=82 Bart's way to create bootable CD-Roms </SPA N>=E 2=94=82=E2=94=82 http://www.nu2.nu/bootcd/ =E 2=94=82=E2=94=94=E2=94=80=E2=94=80=E2=94=8 0=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=8 8;=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=& #57;4=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=8 0=E2=94=80=E2=94=80=E2=94=80=E2= =94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=8 8;=E2=94=80=E2=94=80=E2=94=80=E2=94= =80=E2=94=80=E2=94=80=E2=94=98<SP AN style=3D"BACKGROUND: #000000; = COLOR: #ffffff"> =20 = =20 = 0) Boot from first harddisk (0x80) =20 = =20 1) Boot Dos with CD-Rom support = =20 2) Boot Dos with Network support = =20 3) Boot Dos with CD-Rom (eltorito.sys) support = =20 4) Boot Linux (tomsrtbt) = =20 = =20 a) Boot from first floppy drive (0x00) = =20 q) Skip CD-Rom boot (try next boot device) = =20 = =20 When no key is pressed for 20 sec, or when you hit Enter "0" wil l be = run... =20 = =20 Type command at the prompt... = =20 boot: = = =20 = =20 </PRE></TD></TR></TBODY></TAB LE>(screen created with <A = title=3D/scr2htm=20 href=3D"http:/ /www.nu2.nu/scr2htm">scr2htm</A>) A i solinux.cfg = file,=20 looks like this:=20 <TABLE class=3Dnu2table cellSpacing=3D1> <TBODY> <TR> <TH class=3Dnu2th>isolinux.cfg</TH></TR> <TR> <TD class=3Dnu2td><PRE>default 0 display bootmsg.txt prompt 1 label 0 localboot 0x80 label a localboot 0x00 label q localboot -1 label 1 kernel memdisk append initrd=3Dcdrom.img label 2 kernel memdisk append initrd=3Dmsnet.img label 3 kernel memdisk append initrd=3Dtomsrtbt.img timeout 200 </PRE></TD></TR></TBODY></TABLE><BR& #62; <LI>Follow the steps in the <A title=3D/bootdisk/cdrom/=20 href=3D"http://www.nu2.nu/bootdisk/cdrom/">CD-Rom boot disk</A> pa ge = to create=20 the CD-Rom boot disk bootdisk. Create a boot image file from the = "CD-Rom=20 boot disk" bootdisk using <A title=3D#aboutdd=20 href=3D"http:/ /www.nu2.nu/bootcd/#aboutdd">dd.exe</A>, you should cal l = this boot=20 image "cdrom.img" and put it into the = "cds\multi_memdisk\disk1\isolinux"=20 directory. Note! You have to rename the boot image to=2& #48; lowercase! <LI>Follow the steps in the <A title=3D/bootdisk/network/=20 href=3D"http://www.nu2.nu/bootdisk/network/">Network boot disk</A 2; = page to=20 create the Network boot disk bootdisk. Create a boot image file = from the=20 "Network boot disk" bootdisk using <A title=3D#aboutdd=20 href=3D"http:/ /www.nu2.nu/bootcd/#aboutdd">dd.exe</A>, you should cal l = this boot=20 image "msnet.img" and put it into the = "cds\multi_memdisk\disk1\isolinux"=20 directory. Note! You have to rename the boot image to=2& #48; lowercase! <LI>Get the 2.88MB Eltorito image from <A = title=3Dhttp://www.tom s.net/rb/=20 target=3D_blank = href=3D"http://www .toms.net/rb/">http://www.toms.net/rb/</A> call=20 the image "tomsrtbt.img" and put it in the = "cds\multi_memdisk\disk1\isolinux"=20 directory. <LI>All other files and folders you want in the CD-Rom filesystem must = also be=20 copied into cds\multi_memdisk\disk1 directory. <LI>Change cds\multi_memdisk\disk1\autorun.bat you can add any = commands you=20 want. For example start an application from CD-Rom. Edit the file cds\multi_memdisk\build.mak and put your name into = the=20 "preparer" variable. <LI>Start the batch file "run.bat". From the "M ain menu" select = "Build=20 & Burn" and "multi_memdisk". </LI&# 62;</OL>Done! <A = name=3Dnt4=20 href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Bootable = Windows NT=20 4.0 installation CD-Rom</H2> This will show you how to cr eate a = bootable=20 Windows NT 4.0 Workstation or Server CD-Rom. It uses the bootstrap = loader from=20 Windows 2000 to have a "press any key to boot from CD" optio n. It has an = updated=20 atapi driver to support harddisks larger than 10GB. Optionally you can = add=20 service packs, security hotfixes and other stuff to your CD. The boot = catalog=20 and NT bootstrap loader are hidden, just like the original bootable = Windows NT=20 4.0 CD-Rom. Joliet extensions are enabled by def ault, so you can = have=20 long filenames on the CD, the original Microsoft Windows NT 4.0 bootable = CD-Rom=20 uses only ISO9660. The steps to create are: <OL> <LI>If you have not already setup cdrpack version 1.3 then downloa d <A = title=3D/download.php?sFile=3Dcdrpack13.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dcdrpack13.zip">cdrpa ck=20 v1.3</A> (624KB). This file contains a workspace w here you can = build=20 your bootable CD's from. Unpack the cdrpack13.zip file to a = directory on=20 your local harddisk. Make sure you expand the subdi rectories! So = when=20 using pkunzip.exe use the -d option! <LI>Download <A title=3D/download.php?sFile=3Dnt4_addon.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dnt4_addon.zip">Windows = NT 4.0=20 add-on</A> (3KB). Unpack the nt4_addon.zip file into the = same=20 directory as cdrpack 1.3. Make sure you expand the = subdirectories! So=20 when using pkunzip.exe use the -d option! <BR& #62;The add-on = contains, the=20 Windows 2000 bootstrap loader, the Windows 2000 bootfi x.bin and the=20 "build.mak" file. We will be using the bootstrap loader fro m = Windows 2000,=20 this will give us the "Press any key to boot from CD" option.<BR&# 62; <LI>From Windows NT 4.0 CD copy the "i386" folder to=20 ; cds\nt4ws_us\disk1\. You will find the cds\nt4ws_us\disk1\ folder = in the=20 same directory as where you have unpacked the cdrpack and Windows NT = 4.0=20 add-on. <LI>From Windows NT 4.0 CD copy into cds\nt4ws_us\disk1\ the f ollowing = files: If you are building a Windows NT 4.0 workstation CD copy :=20 cdrom_w.40 If you are building a Windows NT 4.0 server CD c opy:=20 cdrom_s.40 <LI>Optionally copy (from Windows NT 4.0 CD) into cds\nt4ws_us\dis k1\ = the=20 following files: autorun.inf <LI>If you have copied Windows NT 4.0 from MSDN CD... E dit the file = i386/txtsetup.sif section [SetupData], and change SetupSourceP ath = =3D=20 "\"  <LI>Copy Service Pack 6a, the Post-SP6a Security Rollup Package (SRP) = and=20 maybe some other security fixes to cds\nt4ws_us\disk1\. &# 60;BR> <LI>Update Atapi driver. Unpack Service Pack 6a to a = temporarily folder=20 using /x parameter. From this temporarily folder copy into=2&# 48; cds\nt4ws_us\disk1\i386 the following files: <UL> <LI>ntldr=20 <LI>ntdetect.com=20 <LI>atapi.sys </LI></UL> <LI>All other files and folders you want in the CD-Rom filesystem must = also be=20 added to cds\nt4ws_us\disk1. Things you could add are: latest = internet=20 explorer, directx, ... <LI>Edit the file cds\nt4ws_us\build.mak change the "volumeid" if you = like and=20 put your name into the "preparer" variable. <LI>Let's check some files to see if they are in the right = place. Make sure=20 that the following files exist: <UL> <LI>cds\nt4ws_us\disk1\w2ksect.dat=20 <LI>cds\nt4ws_us\disk1\i386\bootfix.bin=20 <LI>cds\nt4ws_us\disk1\i386\setupldr.bin=20 <LI>If you are building a Windows NT 4.0 workstation CD:=20 cds\nt4ws_us\disk1\cdrom_w.40 If you are building a Windo ws NT = 4.0 server=20 CD: cds\nt4ws_us\disk1\cdrom_s.40 </LI></UL&# 62; If one or more = files are=20 missing do not continue! Go back to correct it!<BR& #62; <LI>Start the batch file "run.bat". From the "M ain menu" select = "Build=20 & Burn" and "nt4ws_us". </LI>&# 60;/OL>To have more Windows NT = 4.0=20 versions available from cdrpack to build, you can just rename the = "nt4ws_us"=20 folder to any other name you want, and go again from step=20 2. Done! <A name=3Dw2k = href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Bootable = Windows 2000=20 installation CD-Rom (with SP3) [updated! dec 17, = 2002]</H2> This will=20 show you how to create a bootable Windows 2000 Professional, Server or = Advanced=20 Server CD-Rom. Optionally you can integrate (slipstream) service pack 3, = and add=20 other stuff you want to your CD. The boot catalog and the NT bootstrap = loader=20 are hidden, just like the original bootable Windows 2000 = CD-Rom. For=20 multiboot (3-in-1) check out <A title=3Dhttp://www.tech-hints.com/ = target=3D_blank=20 href=3D"http:// www.tech-hints.com/">Twinkie's How-to = Website</A>. Joliet=20 extensions are enabled by default, so you can have long filenames on the = CD, the=20 original Microsoft Windows 2000 bootable CD-Rom uses only = ISO9660. The=20 steps to create are: <OL> <LI>BCD installation instructions: & #60;BR>Download <A=20 title=3D/download.php?sFile=3Dbcd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcd111.zip"> BCD full = package=20 v1.1.1</A> (523KB). Or update from previous version: <A=20 title=3D/download.php?sFile=3Dbcdupd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcdupd111.zip"&# 62;BCD = update package=20 (v1.1.0-v1.1.1)</A> (5KB). Whe n updating from previous = versions, just=20 extract the package over the previous version, overwrite any existin g = files.=20 The <TT>bcd.cfg</TT> file will not get overwritten! ; Unpack the = BCD=20 package to some folder for example <TT>d:\bcd</TT>. If yo u want to be = able to=20 run it from a server you should unpack it to a share from where your=20 workstations can run it. You will need to map a drive letter to that = share and=20 run bcd using that drive letter. Make sure you also unpack the=2 8; subdirectories! Download <A = title=3Dftp://ftp.nero.com/wnaspi32.dll=20 target=3D_blank href=3D"ftp://ftp.nero.com/wnaspi32.dll">Nero Aspi = Library=20 (wnaspi32.dll)</A> and copy it into BCD's <TT>d:\bcd\bin&# 60;/TT>=20 directory. I have asked Ahead Software AG if I could di stribute = their=20 aspi manager with my BCD package but they said: "...due to our = licence=20 agreement you could only let your users download it freely from our = web=20 site...". <LI>Download <A title=3D/download.php?sFile=3Dw2k10.zip=2& #48; href=3D"http://www.nu2.nu/download.php?sFile=3Dw2k10.zip">Windo ws 2000 = package=20 v1.0 (w2k10.zip)</A> (7KB). Unpack it into the BCD directory,=20 <TT>d:\bcd</TT>. Make sure you also unpack the = subdirectories! The=20 Windows 2000 package contains the Windows 2000 bootstr ap loader (boot = sector)=20 and some other files used to build the CD. <LI>You must copy the <TT>i386</TT> folder from your W indows 2000=20 installation/setup CD-Rom. For Windows 2000 Professiona l copy it to = the=20 <TT>d:\bcd\cds\w2kpro\files\</TT> folder. For Windo ws 2000 Server = copy it=20 to the <TT>d:\bcd\cds\w2ksrv\files\</TT> folder. Fo r Windows 2000 = Advanced=20 Server copy it to the <TT>d:\bcd\cds\w2kadv\files\</TT> = folder. Make sure=20 you copy all files and all subdirectories! If you'r e Windows = 2000 files=20 are already "slipstreamed" with a service pack you must also copy the= 20 <TT>CDROM_SP.TST</TT> or <TT>CDROMSPx.TST</TT > file. This will = prevent the=20 CD asking "put the SPx CD into drive A:" during install.<BR&# 62; <LI>Optionally you can also copy the following files (not needed for = bootable=20 CD=20 = installation): <TT>autorun.inf</TT> <T T>read1st.txt</TT> <TT>rea= dme.doc</TT> <TT>setup.exe</TT><BR&# 62; <LI>If you have a Windows 2000 CD from MSDN... Edit the file=20 <TT>i386\txtsetup.sif</TT> section [SetupData] , and change the = setup source=20 path, it should read: SetupSourcePath =3D "\" <LI>If you have copied Windows 2000 from MSDN CD you can d isable the = product=20 key prompt: Edit i386/setupp.ini file, remove the read-only = attribute and=20 open the file in notepad. Change the last 3 digits of t he Pid = number to=20 = 270 Example: [Pid] ExtraData=3D&# 49;23456789012345678901234567890<BR= >Pid=3D12345270 <LI>You can apply Service Pack 3 to this installation (integrated=2 8; installation). So that you have an installation CD-ROM with the = service pack=20 built in. Apply service pack 3 to your files using the "-s" option = (you=20 must supply full path). <TABLE cellSpacing=3D0 cellPadding=3D0> <TBODY> <TR> <TD>For Windows 2000 Professional:</TD> <TD><TT>w2ksp3.exe -s:d:\bcd\cds\w2kpro\files\</T T></TD></TR> <TR> <TD>For Windows 2000 Server:</TD> <TD><TT>w2ksp3.exe -s:d:\bcd\cds\w2ksrv\files\</T T></TD></TR> <TR> <TD>For Windows 2000 Advanced Server: </TD 2; <TD><TT>w2ksp3.exe=20 = -s:d:\bcd\cds\w2kadv\files\</TT></TD></TR></TBODY 2;</TABLE> Notes:</= B> <UL> <LI>The w2ksp3.exe can only be run on a Windows 2000 ; or XP PC!=20 <LI>You should now have a <TT>CDROMSP3.TST</TT> file in the = <TT>files</TT>=20 directory. Check this, to prevent the CD asking "put the SP3 CD into = drive=20 A:" during install. </LI></UL> <LI>All other files and folders you want on the CD-Rom must also be = added to=20 the <TT>files</TT> directory, these files will not be integrat ed in = the=20 Windows 2000 installation, they're just parked there. Things y ou could = add=20 are: latest patches, internet explorer, directx. <BR& #62;Add your files = to: For Windows 2000 Professional:=20 <TT>d:\bcd\cds\w2kpro\files\</TT>. For Windows 2 8;00 Server:=20 <TT>d:\bcd\cds\w2ksrv\files\</TT>. For Windows 2 8;00 Advanced = Server:=20 <TT>d:\bcd\cds\w2kadv\files\</TT>. <LI>Open a command prompt, go to the <TT>d:\bcd</TT> f older and = run: For=20 Windows 2000 Professional: <TT>bcd w2kpro</TT>. 0;BR>For Windows 2000 = Server:=20 <TT>bcd w2ksrv</TT>. For Windows 2000 A dvanced Server: <TT>bcd=20 w2kadv</TT>. This will build the (bootable) ISO image and b urn it = to your=20 recorder. </LI></OL>Done! &# 60;BR><A name=3Dwxp=20 href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Bootable = Windows XP=20 installation CD-Rom (with SP1) [updated! dec 17, = 2002]</H2> This will=20 show you how to create a bootable Windows XP Home Edition or = Professional=20 installation/setup CD-Rom. Optionally you can integrate (slipstream) = service=20 pack 1, and add other stuff you want to your CD. The boot catalog and = the NT=20 bootstrap loader are hidden, just like the original bootable Windows XP=20 CD-Rom. Joliet extensions are enabled by default, so you can have = long=20 filenames on the CD. Note: This will create a = "dual"=20 bootable XP CD with Home edition and Professional together on one = CD. The=20 steps to create are: <OL> <LI>BCD installation instructions: & #60;BR>Download <A=20 title=3D/download.php?sFile=3Dbcd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcd111.zip"> BCD full = package=20 v1.1.1</A> (523KB). Or update from previous version: <A=20 title=3D/download.php?sFile=3Dbcdupd111.zip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dbcdupd111.zip"&# 62;BCD = update package=20 (v1.1.0-v1.1.1)</A> (5KB). Whe n updating from previous = versions, just=20 extract the package over the previous version, overwrite any existin g = files.=20 The <TT>bcd.cfg</TT> file will not get overwritten! ; Unpack the = BCD=20 package to some folder for example <TT>d:\bcd</TT>. If yo u want to be = able to=20 run it from a server you should unpack it to a share from where your=20 workstations can run it. You will need to map a drive letter to that = share and=20 run bcd using that drive letter. Make sure you also unpack the=2 8; subdirectories! Download <A = title=3Dftp://ftp.nero.com/wnaspi32.dll=20 target=3D_blank href=3D"ftp://ftp.nero.com/wnaspi32.dll">Nero Aspi = Library=20 (wnaspi32.dll)</A> and copy it into BCD's <TT>d:\bcd\bin&# 60;/TT>=20 directory. I have asked Ahead Software AG if I could di stribute = their=20 aspi manager with my BCD package but they said: "...due to our = licence=20 agreement you could only let your users download it freely from our = web=20 site...". <LI>Download <A title=3D/download.php?sFile=3Dwxp10.z ip=20 href=3D"http://www.nu2.nu/download.php?sFile=3Dwxp10.zip"> Windows XP = package v1.0=20 (wxp10.zip)</A> (5KB). Unpack it into the BCD directory,=20 <TT>d:\bcd</TT>. Make sure you also unpack the = subdirectories! The=20 Windows XP package contains the Windows XP bootstrap loader (same as = Windows=20 2000) and some other files used to build the CD. <LI>You must copy the <TT>i386</TT> folder from your W indows XP=20 installation/setup CD-Rom. For Windows XP Home Edition copy it to = the=20 <TT>d:\bcd\cds\wxphome\files\</TT> folder. For Windows XP = Professional copy=20 it to the <TT>d:\bcd\cds\wxppro\files\</TT> folder.Make sure you = copy all=20 files and all subdirectories! If you're Windows XP files are = already=20 "slipstreamed" with a service pack you must also copy the = <TT>win51ic.SPx</TT>=20 or <TT>win51ip.SPx</TT> file. This will pr event the CD asking "put = the SPx=20 CD into drive A:" during install. The location of t he i386 = folder may=20 differ, for example when you have a dual boot MSDN cd-rom it will be = in=20 \%lang%\winxp\%edition%, where %lang% is your language, like = "ENGLISH",=20 "GERMAN" and %edition% is "Home" or "Pro". Other CD 9;s may have it just = in the=20 root or in some other location. <LI>Optionally you can also copy the following files (not needed for = bootable=20 CD=20 = installation): <TT>autorun.inf</TT> <T T>readme.htm</TT> <TT>setu= p.exe</TT> <LI>If you have a Windows XP CD from MSDN... Edit the file= 20 <TT>i386\txtsetup.sif</TT> section [SetupData] , and change the = setup source=20 path, it should read: SetupSourcePath =3D "\" <LI>You can apply Service Pack 1 to this installation (integrated= 20 installation). So that you have an installation CD-ROM with the = service pack=20 built in. Apply service pack 1 to your files using the "-s& #34; option = (you=20 must supply full path). <TABLE cellSpacing=3D0 cellPadding=3D0> <TBODY> <TR> <TD>For Windows XP Home edition: </TD> <TD><TT>xpsp1_en_x86.exe = -s:d:\bcd\cds\wxphome\files\</TT></TD></TR> <TR> <TD>For Windows XP Professional:</TD> <TD><TT>xpsp1_en_x86.exe=20 = -s:d:\bcd\cds\wxppro\files\</TT></TD></TR></TBO DY></TABLE> Notes:</= B> <UL> <LI>The Service Pack file can have another name, like=20 <TT>xpsp1_nl_x86.exe</TT> for Dutch langu age.=20 <LI>The xpsp1_en_x86.exe can only be run on a Win dows 2000 or XP PC! = <LI>You should now have a <TT>win51ic.sp1 or = </TT><TT>win51ip.sp1</TT> file=20 in the <TT>files</TT> directory. Check this, to prevent the CD = asking "put=20 the SP1 CD into drive A:" during install. </LI></UL> <LI>All other files and folders you want on the CD-Rom must also be = added to=20 the <TT>files</TT> directory, these files will not be integrat ed in = the=20 Windows XP installation, they're just parked there. Things you could = add are:=20 latest patches, internet explorer, directx. A dd your files = to: For=20 Windows XP Home edition: <TT>d:\bcd\cds\wxphome\files\</TT 2;. For = Windows XP=20 Professional: <TT>d:\bcd\cds\wxppro\files\</TT>.<BR&# 62; <LI>Open a command prompt, go to the <TT>d:\bcd</TT> f older and = run: For=20 Windows XP Home edition: <TT>bcd wxphome</TT>. ;For Windows XP = Professional:=20 <TT>bcd wxppro</TT>. This will build the (boot able) ISO image and = burn it=20 to your recorder. </LI></OL>Done! <A name=3Delghost=20 href=3D"http://w ww.nu2.nu/bootcd/#TOC"></A> <H2><IMG src=3D"http://www.nu2.nu/gfx/arrowright.gif"> Bootable = Ghost restore=20 CD-Rom "ELGHOST"</H2> The ELGHOST v2.0 bootable C D-Rom uses = isolinux.bin,=20 memdisk and the eltorito.sys (hardware independent CD-Rom = driver). See also:=20 <A title=3D#aboutghost = href=3D"http://w ww.nu2.nu/bootcd/#aboutghost">About=20 ghost</A>. Requirements:=20 <UL> <LI>Norton Ghost (from symantec) </LI></UL>The boot im age used in this = example=20 is: <UL> <LI>cdrom.img - <A title=3D/bootdisk/cdrom/=20 href=3D"http://www.n

CRACK LOCATOR