Ultimate Slipstream Guide (almost)
Posted 31 July 2002 - 12:27 AM
Ars Technica Slipstream Guide
Use this for much shorter instructions...may be better guide depending on your needs:
Roxio Easy CD Creator 5= www.roxio.com
Ahead Nero Burning ROM = http://www.nero.com/...x.html#download
CDRWIN = http://www.goldenhawk.com/
WINISO = www.winiso.com
WINIMAGE = www.winimage.com
DOWNLOAD THE BOOT SECTOR FILES
Get the CD-ROM boot sector and CD Marker files from here:
Windows 2000/XP Service Packs
Windows 2000 (Pro/Server/Advanced Server 32bit)
Windows XP (Home/Pro 32bit)
DOWNLOAD WINDOWS XP BOOT DISKS
No Service Pack
Professional = http://download.micr...P_EN_PRO_BF.EXE
Service Pack 1
WINDOWS 2000/XP CD'S THAT DO NOT BOOT
Place the appropriate files from neededfiles.zip into the root directory of the folder that you copied the Windows 2000/XP CD into.
WINDOWS 2000 BOOT FILES
Place CDROM_NT.5 into the root of the CD.
Also make sure these files are located in the root of your CD:
CDROM_IP.5 - If 2000 PRO then place this into the root.
CDROM_IS.5 - If 2000 SERVER then place this into the root.
CDROM_IA.5 - If 2000 ADVANCED SERVER then place this into the root.
CDROM_ID.5 - If 2000 DATACENTER then place this into the root.
WINDOWS XP BOOT FILES
WIN51IP - If XP PRO then place this into the root.
If you already have the CDROM_ or WIN51 files on your CD then do not use the ones included with the .zip's. Just don't worry about it. If your CD does not have these files then you will need to place the above files onto your CD.
The root of the Windows 2000 CD should contain these files:
cdrom_sp.tst (cdrom_sp.tst=SP1 cdromsp2.tst=SP2 cdromsp3.tst=SP3)
spnotes.htm (Only in SP2/SP3)
The root of the Windows XP Pro CD should contain these files:
You may also create these files yourself.
For Windows 2000's CDROM_ files simply open up notepad and create the filenames that I posted above then simply write the letters "w2k" at the very beginning of the file. For the .tst file just create a blank file with notepad.
For Windows XP's WIN51 files simply open up notepad and create the filenames that I posted above then simply write the letters "Windows" at the very beginning of the file. For the .SP1 just create a blank file with notepad.
Professional = W2PFPP_EN
Server = W2SFPP_EN
Advanced Server = W2AFPP_EN
DataCenter = W2DFPP_EN
Professional = WXPVOL_EN
SHORT & EAST INSTRUCTIONS FOR MAKING A BOOTABLE 2K/XP CD WITH INTEGRATED SERVICE PACK!
Insert 2K/XP CD into CDROM.
Go to Actions/Make ISO from CDROM
Pick the letter where your 2K/XP cd is located.
Pick the location where you wish to place the .ISO
Make sure ASPI is Selected!
When done go to
Open up your .ISO
Go to Actions/Extract
Extract 2K/XP to a directory
Do a S:\SP.exe (name of Service Pack file) -s:S:\2K/XP (Where your extracted 2K/XP CD is located) to slipstream 2K/XP with a service pack.
When done it will say "Integrated install has completed successfully."
Now delete all directories/files in the 2K/XP .ISO that you created.
Go to Actions/Add Files
Add all of the files from the root of the extracted CD to the image
Go to Actions/Add Directory
Add all of the directories from the extracted cd to the image.
Go to File/Save As and Save your image.
Your done! Now go install 2K/SP with integrated Service Pack!
** Some people have experienced problems when booting with a .ISO created with WINISO. For those people simply use WINIMAGE instead of WINISO to create the initial .ISO, then use WINISO for the rest of the instructions. Currently it is unknown why WINISO does this.
LONG & COMPLICATED INSTRUCTIONS FOR MAKING A BOOTABLE 2K/XP CD WITH INTEGRATED SERVICE PACK!
CREATING THE BOOT SECTOR FILE
There are 2 ways to extract the boot sector:
#1 Execute CDRWIN and go to the "Extract Disc/Tracks/Sectors" button.
For Extract Mode... : Choose "Select Sectors"
For CD Reader Select the current location of your 2K/XP CD.
For Image Filename choose a directory to place your file. Example: C:\2kboot.bin
For Sector Selection: "Start: 20 End: 20 Datatype: Data Mode1 (2048)"
Click the "START" button to create the Windows NT4/2K/XP/.NET boot sector file!
#2 Download Bart's Boot Image Extractor http://www.nu2.nu/nu2files/bbie10.zip
Extract the files and run BBie X: (Where X=the CDR where your NT4/2K/XP/.NET CD is located)
This only works in NT...but you can extract boot sectors from .ISO'S in 9x using this tool.
PREPARING THE WINDOWS 2000/XP CD FOR CD CREATION
Make a folder on your C: drive. Name it the same as that of your Windows 2000/XP CD. Example: W2PSEL_EN
Copy the entire Windows 2000/XP CD to the folder.
You will need at least 380MB on your hard drive just for the Windows 2000/XP CD.
SLIPSTREAMING WINDOWS 2000/XP WITH A SERVICE PACK
(CAN ONLY BE PERFORMED ON A 2K/XP/.NET BOX)
Copy SP1/SP2/SP3 to your C: drive.
Do a Start/Run/C:\sp1network.exe -S:C:\W2PSEL_EN to "slipstream" or update the windows 2000/XP CD with the latest service pack.
When it's done it will say "Integrated install has completed successfully". Click OK.
If it does not say this then you have done something wrong.
IF YOU EXPERIENCE PROBLEMS WITH SP1NETWORK.EXE/W2KSP2.EXE/W2KSP3.EXE
Do a Start/run/C:\sp1network.exe -X:C:\SP1 to extract the Service pack files to a subdirectory.
Click OK at the screen where it displays "C:\SP1"
When it's done extracting click OK.
Do a Start/Run/C:\SP1\i386\update\update.exe -s:C:\W2PSEL_EN to "slipstream" or update the windows 2000 CD/XP with the latest service pack.
When it's done it will say "Integrated install has completed successfully". Click OK.
If it does not say this then you have done something wrong.
BURN TO CD INSTRUCTIONS
CDRWIN is the preferred CDR burning program to burn Windows 2000/XP CD's. Using CDRWIN you can use the Windows 2000/XP boot feature EXACTLY as Windows 2000/XP does (No floppy Emulation). Adaptec can not. (floppy emulation)
Open CDRWIN and choose the File Backup and Tools option
In the BACKUP/TOOL Operation Choose the Build an ISO9660 Image File
In FILE BACKUP List click the DIRECTORY button and choose the directory where you copied the
Windows 2000 CD. Click OK. Then click the ADD button. You should see the directory in the big box now.
Check the INCLUDE HIDDEN FILES,LONG FILENAMES(JOLIET),INCLUDE SYSTEM FILES,RECURSE SUBDIRECTORIES. Uncheck PRESERVE FULL PATHNAMES.
For IMAGE FILENAME click the three dots at the right and choose a directory and a filename. Then
click Save. You should see the pathname and the filename of your .ISO in the box.
Check the DISABLE VERSION NUMBERS box.
Click the ADVANCED OPTIONS button.
For Volume Label use the name of the original Windows 2000 CD. Ex: W2PSEL_EN
For Volume Set Name use the name of the original Windows 2000/XP CD
Publisher Name: MICROSOFT CORPORATION
PREPARER NAME: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (206) 882-8080
Choose the BOOTABLE DISC tab.
Check the MAKE BOOTABLE DISC box.
For MEDIA EMULATION CHOOSE Custom
For Image File name use the boot sector file that you made.
For DEVELOPER NAME use MICROSOFT CORPORATION
For Load Sector Count use the number 4.
Click OK and then START to make your image!
When it's done open up any CDR burning program that supports .ISO's to burn your IMAGE to CD.
(It is recommended to use another program to burn the image file to CD due to the shareware version of CDRWIN only burning images at 1x!)
Nero Burning ROM v220.127.116.11
Make a file called nero.reg
Add the following to nero.reg and save it:
[HKEY_CURRENT_USER\Software\ahead\Nero - Burning ROM\General]
Now run nero.reg
Exit all open Nero Windows
Select "Image Record" if you wish to burn to .ISO.
Select your CDR if you wish to burn straight to CD.
Now go to FILE and then NEW
Choose CD-ROM (Boot)
Select Image File
Browse to your boot sector file.
For Kind of Emulation: Choose: "NO EMULATION"
Change "Number of loaded sectors" to 4.
Go to tab ISO
Volume Label W2SFPP_EN
Volume Set W2SFPP_EN
Publisher MICROSOFT CORPORATION
Data Preparer MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (206) 882-8080
Drag the Windows 2000/XP files into the ISO Window.
Right-click on the volum label in the ISO2 window and go to properties. Verify that the settings are correct.
Now Choose Burn Image!
Adaptec EZ CD Creator v5.02d
Start Easy CD Creator 5 Project Selector, select Make A Data CD, Select Data CD Project
Once EZ CD Creator has started go to File,New CD Project,Bootable CD
Change Bootable CD Type to "No Emulation"
Change Sector Count to 4
Choose "Browse" and locate the boot sector file that you made with CDRWIN.
Press OK to close this screen
Now in the lower left-hand screen right-click on the CD Icon and choose rename. I use "W2PSEL_EN" since that is the name of my original CD.
Now Right-click on the CD Icon again. Choose Properties.
For File system use: ISO9660
For Physical format of CD use: MODE 1: CDROM
Now locate your original 2K/XP CD files in the upper screen. Drag all files from the original 2K/XP CD into the lower left-hand side of the screen.
Now you can burn this project to CD or save it as an image file.
To save as an image file: Go to File,Create CD Hard Disk Image...,
Type in a name for the image and save it as either a .cif or a .iso.
(.CIF is an extension used by EZ CD Creator. I suggest using .ISO since most CD programs use that extension.)
To record to CD go to File,Record CD...
If at any time later you wish to burn your image file to CD then just go to File,Record CD From CD Image and burn it!
OTHER THINGS YOU CAN DO TO YOUR 2K/XP CD.
UP[censored] THE BOOT DISKS ON THE WINDOWS 2000/XP CD
When you integrate a Service Pack into Windows 2000/XP it does not update the boot disks on the CD. If you try to use the boot disks with your integrated Service Pack CD it will not work. Using the following script you can create updated boot disks to work with your updated Windows 2000/XP!
* Before performing ANY of the below: If you do not wish to go through the trouble of the following. (If you are in a hurry) then there is a quick way to get the boot disks working without going through the pain below.
1. Create the bootdisks as normal.
2. Replace the TXTSETUP.SIF on DISK 1 with the TXTSETUP.SIF from the updated SP.
3. What this does is get the bootdisks to work with your slipstreamed SP BUT the rest of the files on the floppies will not be updated to the Service Pack. What this means is that the part of the installation process that uses the floppies (All the drivers you see it load when you boot the floppies, Hardware detection, partition format) may be buggy, the updated Service Pack files *MAY* have fixes for these bugs. I am currently unaware of any serious bugs in the 2K/XP setup, none as serious as the NT4 setup so you should be able to perform this procedure without any problems.
BOOTDISK IMAGE UPDATE SCRIPT
Thanks Zarquon for the script!
Place the following lines in a text file called BDUP_NODISK.cmd to make your own BDUP_NODISK.cmd if you cannot download slipfiles.zip:
FOR %%i IN ("%~1\bootdisk\cdboot?.img") DO echo. & echo Extracting %%~nxi... & md %%~ni & pushd %%~ni & ..\extract -x %%~fi > NUL & echo. & echo Up[censored] files: & (FOR /F "usebackq skip=4 tokens=1" %%j IN (`..\extract -l %%~fi`) DO if exist "%~f1\i386\%%j" (echo %%j & xcopy /i /y "%~f1\i386\%%j" %%j > NUL)) & popd
echo. & echo Done. Consult README.HTML to merge updated files.
Copy BDUP_NODISK.CMD to anywhere on your hard drive. Doesn't matter where really.
Now download the following file and place it in the same directory where NDUP_NODISK.CMD is located or in your path (if running BDUP_NODISK.CMD from START/RUN then place EXTRACT.EXE in your PATH otherwise the program will not execute).
Now update the bootdisks by pointing the script to the updated Windows 2000/XP CD. Example: bdup.cmd X:\win2k (i386 does not have to be specified. Just the root of the CD).
*** The Boot Disks should be in the same directory as the I386 directory.
For XP create the BOOTDISK directory and place the downloaded bootdisks from Microsoft into this directory.
The script will run very fast and when done there should be 4 CDBOOT directories (for 2K) or 6 CDBOOT directories (for XP) located in the directory where you ran the script.
Now download Winimage.
Open each CDBOOT1 and delete all of the files.
Now inject each directory into the corresponding image.
Download the XP Boot Disks from MS
Now inject each directory into the corresponding image.
2ND METHOD (IF THE ABOVE PROCEDURE DOES NOT WORK! THE FOLLOWING ONLY WORKS WITH WINDOWS 2000 CURRENTLY!)
Make a file called MKDISK.BAT, copy the following into it and save it.
REM THIS BATCH FILE ASSUMES THAT THE CDROM WHERE YOUR WINDOWS 2000 CDROM RESIDES IS G:
REM IF YOURS IS DIFFERENT SIMPLY USE THE REPLACE COMMAND TO REPLACE G: WITH THE LETTER
REM OF YOUR CDROM DRIVE.
REM DISK 1
COPY /Y G:\i386\BIOSINFO.INF C:\BT2K\1\
COPY /Y DISK101 C:\BT2K\1\
COPY /Y G:\I386\NTDETECT.COM C:\BT2K\1\
COPY /Y G:\I386\NTKRNLMP.EX_ C:\BT2K\1\
COPY /Y G:\I386\SETUPLDR.BIN C:\BT2K\1\
COPY /Y G:\I386\TXTSETUP.SIF C:\BT2K\1\
REM DISK 2
COPY /Y G:\I386\1394BUS.SY_ C:\BT2K\2\
COPY /Y G:\I386\ACPI.SY_ C:\BT2K\2\
COPY /Y G:\I386\ACPIEC.SY_ C:\BT2K\2\
COPY /Y G:\I386\BOOTVID.DL_ C:\BT2K\2\
COPY /Y G:\I386\C_1252.NL_ C:\BT2K\2\
COPY /Y G:\I386\C_437.NL_ C:\BT2K\2\
COPY /Y DISK102 C:\BT2K\2\
COPY /Y G:\I386\DMIO.SY_ C:\BT2K\2\
COPY /Y G:\I386\DMLOAD.SY_ C:\BT2K\2\
COPY /Y G:\I386\FDC.SY_ C:\BT2K\2\
COPY /Y G:\I386\FTDISK.SY_ C:\BT2K\2\
COPY /Y G:\I386\HAL.DL_ C:\BT2K\2\
COPY /Y G:\I386\HALAACPI.DL_ C:\BT2K\2\
COPY /Y G:\I386\HALACPI.DL_ C:\BT2K\2\
COPY /Y G:\I386\HALAPIC.DL_ C:\BT2K\2\
COPY /Y G:\I386\HIDCLASS.SY_ C:\BT2K\2\
COPY /Y G:\I386\HIDPARSE.SY_ C:\BT2K\2\
COPY /Y G:\I386\HIDUSB.SY_ C:\BT2K\2\
COPY /Y G:\I386\I8042PRT.SY_ C:\BT2K\2\
COPY /Y G:\I386\INTELIDE.SY_ C:\BT2K\2\
COPY /Y G:\I386\ISAPNP.SY_ C:\BT2K\2\
COPY /Y G:\I386\KBDCLASS.SY_ C:\BT2K\2\
COPY /Y G:\I386\KBDHID.SY_ C:\BT2K\2\
COPY /Y G:\I386\LBRTFDC.SY_ C:\BT2K\2\
COPY /Y G:\I386\L_INTL.NL_ C:\BT2K\2\
COPY /Y G:\I386\MOUNTMGR.SY_ C:\BT2K\2\
COPY /Y G:\I386\OHCI1394.SY_ C:\BT2K\2\
COPY /Y G:\I386\OPENHCI.SY_ C:\BT2K\2\
COPY /Y G:\I386\PARTMGR.SY_ C:\BT2K\2\
COPY /Y G:\I386\PCI.SY_ C:\BT2K\2\
COPY /Y G:\I386\PCIIDE.SY_ C:\BT2K\2\
COPY /Y G:\I386\PCIIDEX.SY_ C:\BT2K\2\
COPY /Y G:\I386\PCMCIA.SY_ C:\BT2K\2\
COPY /Y G:\I386\SBP2PORT.SY_ C:\BT2K\2\
COPY /Y G:\I386\SCSIPORT.SY_ C:\BT2K\2\
COPY /Y G:\I386\SERENUM.SY_ C:\BT2K\2\
COPY /Y G:\I386\SERIAL.SY_ C:\BT2K\2\
COPY /Y G:\I386\SETUPDD.SY_ C:\BT2K\2\
COPY /Y G:\I386\SETUPREG.HIV C:\BT2K\2\
COPY /Y G:\I386\SPDDLANG.SY_ C:\BT2K\2\
COPY /Y G:\I386\UHCD.SY_ C:\BT2K\2\
COPY /Y G:\I386\USBD.SY_ C:\BT2K\2\
COPY /Y G:\I386\USBHUB.SY_ C:\BT2K\2\
COPY /Y G:\I386\USBSTOR.SY_ C:\BT2K\2\
COPY /Y G:\I386\VGA.SY_ C:\BT2K\2\
COPY /Y G:\I386\VGAOEM.FO_ C:\BT2K\2\
COPY /Y G:\I386\VIDEOPRT.SY_ C:\BT2K\2\
COPY /Y G:\I386\WMILIB.SY_ C:\BT2K\2\
REM DISK 3
COPY /Y G:\I386\ABP480N5.SY_ C:\BT2K\3\
COPY /Y G:\I386\ADPU160M.SY_ C:\BT2K\3\
COPY /Y G:\I386\AHA154X.SY_ C:\BT2K\3\
COPY /Y G:\I386\AIC116X.SY_ C:\BT2K\3\
COPY /Y G:\I386\AIC78U2.SY_ C:\BT2K\3\
COPY /Y G:\I386\AIC78XX.SY_ C:\BT2K\3\
COPY /Y G:\I386\AMSINT.SY_ C:\BT2K\3\
COPY /Y G:\I386\ASC.SY_ C:\BT2K\3\
COPY /Y G:\I386\ASC3350P.SY_ C:\BT2K\3\
COPY /Y G:\I386\ASC3550.SY_ C:\BT2K\3\
COPY /Y G:\I386\ATAPI.SY_ C:\BT2K\3\
COPY /Y G:\I386\BUSLOGIC.SY_ C:\BT2K\3\
COPY /Y G:\I386\CD20XRNT.SY_ C:\BT2K\3\
COPY /Y G:\I386\CPQARRAY.SY_ C:\BT2K\3\
COPY /Y G:\I386\CPQARRY2.SY_ C:\BT2K\3\
COPY /Y G:\I386\CPQFCALM.SY_ C:\BT2K\3\
COPY /Y G:\I386\CPQFWS2E.SY_ C:\BT2K\3\
COPY /Y G:\I386\DAC960NT.SY_ C:\BT2K\3\
COPY /Y DISK103 C:\BT2K\3\
COPY /Y G:\I386\DMBOOT.SY_ C:\BT2K\3\
COPY /Y G:\I386\FD16_700.SY_ C:\BT2K\3\
COPY /Y G:\I386\FIREPORT.SY_ C:\BT2K\3\
COPY /Y G:\I386\FLASHPNT.SY_ C:\BT2K\3\
COPY /Y G:\I386\INI910U.SY_ C:\BT2K\3\
COPY /Y G:\I386\IPSRAIDN.SY_ C:\BT2K\3\
COPY /Y G:\I386\LP6NDS35.SY_ C:\BT2K\3\
COPY /Y G:\I386\MRAID35X.SY_ C:\BT2K\3\
COPY /Y G:\I386\NCRC710.SY_ C:\BT2K\3\
COPY /Y G:\I386\QL1080.SY_ C:\BT2K\3\
COPY /Y G:\I386\QL10WNT.SY_ C:\BT2K\3\
COPY /Y G:\I386\QL1240.SY_ C:\BT2K\3\
COPY /Y G:\I386\QL2100.SY_ C:\BT2K\3\
COPY /Y G:\I386\SPARROW.SY_ C:\BT2K\3\
COPY /Y G:\I386\SYMC810.SY_ C:\BT2K\3\
COPY /Y G:\I386\SYMC8XX.SY_ C:\BT2K\3\
COPY /Y G:\I386\SYM_HI.SY_ C:\BT2K\3\
COPY /Y G:\I386\TFFSPORT.SY_ C:\BT2K\3\
COPY /Y G:\I386\ULTRA66.SY_ C:\BT2K\3\
REM DISK 4
COPY /Y G:\I386\CDFS.SY_ C:\BT2K\4\
COPY /Y G:\I386\CDROM.SY_ C:\BT2K\4\
COPY /Y G:\I386\CLASS2.SY_ C:\BT2K\4\
COPY /Y G:\I386\CLASSPNP.SY_ C:\BT2K\4\
COPY /Y G:\I386\DISK.SY_ C:\BT2K\4\
COPY /Y DISK104 C:\BT2K\4\
COPY /Y G:\I386\FASTFAT.SY_ C:\BT2K\4\
COPY /Y G:\I386\FLPYDISK.SY_ C:\BT2K\4\
COPY /Y G:\I386\KBDUS.DLL C:\BT2K\4\
COPY /Y G:\I386\NTFS.SY_ C:\BT2K\4\
COPY /Y G:\I386\SFLOPPY.SY_ C:\BT2K\4\
COPY /Y G:\I386\SPCMDCON.SYS C:\BT2K\4\
REM SYSTEM32 DIR
COPY /Y G:\I386\NTDLL.DLL C:\BT2K\4\SYSTEM32\
COPY /Y G:\I386\SYSTEM32\SMSS.EXE C:\BT2K\4\SYSTEM32\
Now download Winimage and install it.
Open the images in the BOOTDISK directory with Winimage.
Delete all of the files in CDBOOT1.IMG and inject all of the files in \BT2K\1 into the image.
Perform the same for the rest of the images.
Now copy the updates images to the BOOTDISK directory on your CD!
UP[censored] THE SUPPORT & DEPLOYMENT TOOLS
Windows 2000 SP3 Deployment Tools
Download the following and place them in the SUPPORT folder on your Windows 2000 CD. These are the SP3 tools there are also tools for each SP.
The Windows 2000 Resource Kit Deployment Tools (deploy.cab) assists system administrators in installing Windows 2000 on multiple computers. This file contains updates to the deployment tools and documentation.
Windows 2000 SP3 Support Tools
These updated Windows 2000 Support Tools (support.cab) will help support personnel and network administrators better manage their networks and troubleshoot problems.
REMOVE CD KEY PROMPT
In the \I386 folder, find SETUPP.INI
Set it’s attributes so that “read only” is unchecked (right-click, properties)
Open the file and change the Pid=51873000 to Pid=51873270 and save the file.
INSTALL WINDOWS 2000/XP ON A MACHINE WITH LESS THAN 64MB MEMORY
Edit the file TXTSETUP.SIF located in I386.
Search for RequiredMemory
Change this to 0.
Save the file
Now install Windows 2000/XP!
*This only works with the DOS installation using winnt.exe
FOR EXTRA SPACE
The Root and I386 directories are the only directories that are really needed for Slipstreaming and installing NT. All of the other directories can be deleted.
You may delete the LANG folder under I386 if you do not use any other languages.
You may also delete the I386\WIN9XMIG, I386\WIN9XUPG, and I386\WINNTUPG folders if you do not plan on upgrading.
FASTER BOOT SPEED & WINDOWS 2000/XP DUAL-BOOT FIX
Replace the NTLDR & NTDETECT.COM with the XP versions of these files. This is a good idea because if you install Windows 2000 as a dual-boot with Windows XP then the Windows XP NTLDR & NTDETECT.COM will be overwritten with the Windows 2000 versions which will make your Windows XP unable to boot. By replacing NTLDR & NTDETECT.COM on the CD then when you install Windows 2000 you will get the benefits of the updated NTLDR & NTDETECT.COM and also the ability to boot both operating systems. (If you do not do this then you will have to replace the files manually after installing Windows 2000)
Make sure that your bios is set to boot from CD before it boots from the Hard Drive.
Change it back to HD after you are done installing!
Slipstreamed Service Packs CAN NOT be uninstalled.
Windows NT 4.0 Service Packs do not have the ability to slipstream. To "slipstream" NT 4.0 you have to manually replace the files. This can be done and IT IS POSSIBLE. It just takes ALOT of time to integrate the service pack FULLY with Windows NT 4.0.
You can use the 2K/XP boot sector on the NT4 CD's! The benefits are obvious. If you have the original NT4 CD in your drive when you reboot the setup will immediately start. If you have the 2K/XP boot sector then you will get the "Press a key" prompt. This allows you to leave the CD in your servers and not having to worry about them when your server reboots! (You need to add bootfix.bin from your 2K/XP I386 directory to the I386 directory on your NT4 CD for this to work)
Windows XP NETBUI support is located in VALUEADD\MSFT\NET\NETBEUI.
Go here ftp://hotfix.microsoft.com/winnt for hotfixes for your version of NT. You will have to call Microsoft for the password for the hotfixes.
Zarquon for the BDUP.CMD script.
ACE for the Extract Link
Makers of Nero Burning ROM
Makers of CDRWIN
Makers of Adaptec EZ CD
The Tech Guide
Maker's of EXTRACT (Winimage)
Posted 31 July 2002 - 04:03 AM
Copy your W2K CD to a folder such as C:\W2KCD.
In a command prompt type: w2ksp3.exe /S:C:\W2KCD.
Then burn the contents of C:\W2KCD to a disk, using all your bootable CD options as mentioned elsewhere.
Posted 01 August 2002 - 09:18 PM
I just had a thought, should I copy extract.exe (this does exist on the win2k cd right?) to the directory i run the script from? I can't test this right now as I'm not around my own comptuer, but would still apreciate a response as to whether this would even solve my problem before trying it tonight.
On another note, the link to
http://www.soundcard...stream/bdup.cmd is broken.
Posted 01 August 2002 - 09:25 PM
Nope, you can't use the Extract.exe from your 2K CD....and I just noticed something. I asked if anyone had the original EXTRACT.EXE used by Zarqon @ arstechniica and someone responded that they had it and posted a link....but the posted EXTRACT.EXE doesn't seem to be the right one.
Sigh. I really do not want to post the other way to make bootdisks because this script makes things ALOT easier.
(Other way involves a crappy batch files that copies the files out of the I386 folder into respective # folders to match the # of the floppy disk. You then have to manually add these files to a floppy image. (This has to be done for each one PRO,SERVER,AS)
Hopefully I can find the proper EXTRACT.EXE tonight.
*Oh, You do not have to re-create the ISO to fix your bootdisks. Simply download WINISO and import your bootdisks directly into the .ISO. This makes it much simpler.
Posted 01 August 2002 - 09:47 PM
Indeed I am an avid user and great fan of WinISO, and plan to use it to update my ISO, but I should mention some problems I've encountered with it concerning the entire slipstream process. Basically, it should not be used to create the initial ISO, then import the boot sector... here are my experiences:
Attempt 1) I used WinISO to extract the boot information from original Win2k CD ISO. I then made a new ISO with SP3 integrated, and imported that boot information. Upon saving, burning, and rebooting to test the new CD, it turns out the computer wouldn't boot from the CD at all.
Attempt 2) I used WinISO to create a new ISO with SP3 integrated, then imported the boot information from the boot.bin which was downloaded from your guide. The computer found that it was a bootable CD, but didn't actually boot, it just sat there saying "Looking for boot information on CD... OK".
Attempt 3) Use CDRWin with the boot.bin from the guide. Works like a charm.
Posted 01 August 2002 - 09:48 PM
DO NOT USE ANY OTHER EXTRACT BUT THIS ONE!\
From Winimage's Site:
Place the EXTRACT.EXE from the .zip into your SYSTEM32 or add it to your PATH.
This is why BDUP.CMD was not working.
Posted 02 August 2002 - 07:07 PM
Create an .ISO using your original 2K CD.
Extract the entire CD to a subdir (Would say just extract I386 & Root files but this could be confused).
Slipstream the subdir
Using WinISO delete all of the files in the .ISO
Using WinISO import the subdir into the original .ISO.
Burn the CD.
This will remove the whole boot marker files/boot sector problem altogether for those with original 2K cd's that boot properly in the first place.
*Was testing last night and it seems that BDUP.CMD no longer works. Strange, because it worked a couple of months ago....
For now there are 2 ways that you can make your boot disks to get 'em working:
1. Take the TXTSETUP.SIF from the updated SP and update your floppy images with this one. (Up[censored] ALL of the files on the images is not required to perform an NT install...although it is recommended)
2. Manua update ALL of the files on the floppies yourself. This will give you a less buggy installation if you experience a problem using the original image files. This is what the BDUP.CMD was created for but I'll have to play around with it tonight to see if I can get it working.
Posted 02 August 2002 - 07:09 PM
Posted 02 August 2002 - 08:53 PM
When you say that bdup.cmd no longer works, are you implying that the process to update the images no longer works or that the process appears to work, but the images are not actually updated?
In my case, I put bdup.cmd and extract.exe in the same empty directory, ran the script, pointing it to the updated distribution that is still on my hard drive, and it appeared to work correctly, creating new images in the directory I ran bdup.cmd from. All of the new image files had creation and modification dates of 8/1/2002 also.
Note, when I pointed the script to an actual CD that had been slipstreamed, the script replied that it was unable to move files (makes sense considering it's a CD) but the new image files still managed to be copied to the script directory with proper modification dates.
Great workaround for using WinISO to slipstream the update!
Posted 02 August 2002 - 10:21 PM
You are correct, all of the files within the image contain old date stamps. Wish I could help you with the command script, but I can barely understand much of it at all, if I figure anything out I'll post though.
Posted 02 August 2002 - 11:46 PM
Posted 04 August 2002 - 10:58 PM
Nero Burning ROM v18.104.22.168
Currently NERO is unable to copy boot sector files or even use them. It can use floppy images for booting but this is not ideal for booting 2K CD's. So for now there really is no way to use 2K's CD boot sector using Nero Burning ROM.
I have Nero 22.214.171.124 and I think it allows us to use boot sector file and no emulation. You can even set number of load sectors(4 in this case). It's in the Boot tab when selecting a new CDROM(boot) compilation.
Anyone having success creating the CD with new versions of Nero?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users