Making a Bootable Windows 2000 CD with Service Pack Integrated |
On this page are the instructions of making a bootable Win2k CD (Professional or server editions) with the integrated Service Pack and while your at it, you can add extra files, like drivers or Internet Explorer 6 setup files.
With unattended scripts (winnt.sif) you could
auto install this software.
see MS
website
SP4 can be downloaded here (English version 129 MB)
See MS KB about
adding hotfixes
using unattended scripts, which is not slipstreaming.
New better article:
http://support.microsoft.com/default.aspx?scid=kb;EN-GB;q296723 http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/support/spdeploy.asp
For booting to work you
need Identifier files (see win2k instructions below)
So use the right
files.
How to make your XP bootable |
Make your own bootable XP CD!
Download bootsector for XP
Extract your XP ISO file with ISO Buster to D:\winxpcd
This article is based on Easy CD creator 5.02b, you can also use Nero but need to run this Registry file first!
Then interpret these instructions for use with Nero!

The Instructions
Note that screenshots are about sp3 but interpret them as
sp4, will re-screenshot later :-)

slipstream is in progress, wait till:

| w2kboot.bin | CD bootsector |
| CDROM_NT.5 | NT5 CD Identifier file |
| CDROM_IP.5 | Professional CD Identifier file |
| CDROM_IS.5 | Server CD Identifier file |
| CDROM_IA.5 | Advanced Server CD Identifier File |
| CDROM_ID.5 | Datacenter CD Identifier File |
| CDROM_SP.TST | Service Pack1 CD Identifier File |
| CDROMSP2.TST | Service Pack2 CD Identifier File |
| CDROMSP3.TST | Service Pack3 CD Identifier File |
| CDROMSP4.TST * | Service Pack4 CD Identifier File * |
Depending of which edition af
Win2k edition you want to burn you choose the CDROM-Ix.5 Identifier
file
Where x is the edition of Windows 2000 (See above table)
On every
CD you need the CDROM_NT.5 file and because the Service Pack is integrated in
the i386 folder
you also add a CDROMSP?.TST file. depending on your sp
level
(CDROM_SP.TST if you are
making a SP1 CD!!!)
This file may already be there after the slipstream
process.
All the identifier files need to be in the root of your CD, so
copy it to D:\CD-root
* The cdromsp4.tst is not in the zipfile, but don't panic! The file is placed in the root of your CD patch by the slipstream process, it is also in the extracted SP4 location in the folder root!
Note! Be sure only one
"CDROM_Ix.5" file is in the root, otherwise booting will
fail!!
Check this step! I get a lot of people mailing me because
about the CD asking "put the SPx CD into drive A:"
This is because they
forgot to put a CDROMSPx.TST file in the root.

[Pid]
ExtraData=646E77637A6F6D79626A1D94089595
Pid=51873000
Change the last 3 digits of the Pid number to 270
Now it looks like this:
[Pid]
ExtraData=646E77637A6F6D79626A1D94089595
Pid=51873270Note: This works on my MSDN version of Win2k If you get an error during windows setup about the product ID try using the exactly the same setupp.ini as mine and use my Volume label (later on this page).
Some visitors mailed me that this trick didn't work for them, so no guarantee!

Choose image file and browse to the
w2kboot.bin file where you extracted it from the bootfiles.zip (in browse window
set filter to all file (*.*)
Check "Enable expert settings
Set to "No Emulation"
Leave Boot message
Leave "load segment
SET "Number of loaded sectors" to 4 !!!
don't forget this last setting otherwise booting will fail!!!
Now go to TAB ISO:
Set everything as in the picture. except the Caracter set, experience shows that choosing DOS is better.
ISO 9660 may cause problems with longfilenames and copying from CD in DOS and win9x
Important to set the "Do not add the ';1' ISO file version
extension" !!!!
Otherwise booting will fail
Now goto TAB "Label"
Set Volume Label as you wish.
You also
may leave it the same as your original CD.
My MSDN win2k CD's have
these
labels:
Professional
W2PFPP_EN
Server
W2SFPP_EN
Advanced Server
W2AFPP_EN
DataCenter
W2DFPP_EN
The rest may be ignored
Now press the "New" button
Go with the file browser to d:\cd-root and select all the folders and files in it. Now drag them to the other window "ISO1"

When done press the Burn button

Set theses settings
click write!
Burn baby burn !!!


You're done ! Now try it out !
If booting fails make sure your BIOS is set to boot from CD first, if the booting gives an error, try booting at lower speed.
When trying to create a bootable copy of an OS from the MSDN cd's, you'll get an error during install: End User License Agreement (EULA) Not Found. The solution for this is to edit the file i386/txtsetup.sif section [SetupData], and change the setup source path, it should read: SetupSourcePath = "\". (because on the MSDN CD the setup root is not the root directory of the CD).
Get all win2k versions on 1 CD !!!!! See instructions on this site Twinkie's How-to Website
There is a new util that can get the any bootsector from bootable CD's!
Get it here, free! http://www.nu2.nu/bbie/
ISObuster, WinISO are GUI tools that also can do this



NT4: To Boot or not to Boot
Want to make custom NT4 boot CD,
get the NT4
bootsector-file, get identifier files from original NT4
CD-rom.
Or better use the win2kboot file and when you boot your
NT4 CD you get the choice to boot or not!
You need a extra Win2k file in your NT4 i386
folder to get this trick to work! Get the bootfix.bin from the i386 folder on
the Win2k CD.
This is cool cause everyone has experiences rebooting an NT4 box with the NT4 CD still in the drive, few minutes later you'll find you NT4 box in setup. This is more inconvenient if you remotely rebooted your NT4 box!
Extra TIP! after installing your servers change the BIOS settings of the server only to boot from the hard drive and not floppy or CD-rom. Then you won't have the surprise of remotely rebooting a machine from your home to solve a problem and discover it won't come up, after driving to the office on your free Sunday you find a floppy in the drive.....
NT 4 Enterprise Edition is a double CD, but you can
make it one by creating your custom boot enterprise CD:
Remove the install
files of the CPU type you'll never use, in most cases just leave the install
files of i386.
Now you have space to fill with the second CD and an unpacked
Service Pack6!