Win2K/SP3 Slipstream booting confusion

[ck42]

I\'ve created a bootable Win2k/SP3 slipstream CD but upon booting up, the screen prompts me with this unexpected instruction:

 Please insert the disk labled Windows 2000 Professional CD into drive A:

If I insert ANY of the 4 win2k boot floppies, it doesn\'t even search the floppy drive...it appears to be searching the CDROM drive for whatever it\'s looking for.

I can\'t find a single instance on Google of anyone else posting this message screen.  What did I do wrong in making the boot CD/Slipstream?

[Anonymous]

That means win2k setup doesnt know where the cd is.

Win2k/winxp use files to identify the cd, if these files aren\'t in the root of the cdrom you\'ll have problems.

In the root of your cd make sure you have WIN50.SP3 or whatever the tag is.  To see what it looks for look in txtsetup.sif and look at the top for identification.

-gosh

[ck42]

I don\'t have any files named WIN50.SP3 or anything like that in the root.
The only thing in the root is a file named cdromsp3.tst and spnotes.htm

What section of the txtsetup.sif should I look at to ID the file it\'s wanting?  [SetupData]

...sorry to ask what is prolly common knowledge on these forums....this is my first attempt at slipstreaming and making bootable.

[gosh]

The following is for xp sp1 however it\'ll apply to all nt versions

When you boot from cd you\'re entering text mode (looks like dos but isn\'t).  This is a 16 bit mode that has many restrictions, such as no network access.  XP setup looks at txtsetup.sif for any information it needs.  If you\'re booting from cd xp setup will look at txtsetup.sif for SetupSourcePath, and use this value to look for the source files.

Before anything is done xp setup needs to verify the source files are correct.  To do this it looks for a cd tag, in the form of a file.  For each version of windows nt, including service packs, the tag is different.  This is so you don\'t boot from xp bootdisks then use a sp1 cd to install file, you would have mismatched files.

In my txtsetup.sif it has the following;

cdname = \"Windows XP Professional CD-ROM\"
productname = \"Windows XP Professional\"


bootname1    = \"Windows XP Professional SP1 Setup Boot Disk\"
bootname2    = \"Windows XP Professional SP1 Setup Disk #2\"
bootname3    = \"Windows XP Professional SP1 Setup Disk #3\"
bootname4    = \"Windows XP Professional SP1 Setup Disk #4\"
bootname5    = \"Windows XP Professional SP1 Setup Disk #5\"
bootname6    = \"Windows XP Professional SP1 Setup Disk #6\"

cdtagfile   = \"win51ip\"


cdtagfilei   = \"win51ip\"

cdtagfilem   = \"win51mp\"

boottagfile1   = \"disk101\"
boottagfile2   = \"disk102\"
boottagfile3   = \"disk103\"
boottagfile4   = \"disk104\"
boottagfile5   = \"disk105\"
boottagfile6   = \"disk106\"

spcdname = \"Windows XP Professional Service Pack 1 CD\"
spcdtagfilei   = \"win51ip.sp1\"

cd2name = \"Windows XP Professional CD2\"
cd2tagfilei = \"win51ip2\"


What this means is if you boot from floppies, on each floppy it\'ll look for diskxxx.  So floppy 3 will have disk003, if setup does not find this on a floppy it wont continue.  In a windows GUI if you run :i386winnt32 /noreboot, go through the prompts, then look at c:win_nt~bt, youll see it has the 6 diskxxx\'s.  This way when setup starts from the hard drive, it\'s fooled into thinking all 6 floppies were entered.

It also shows that on the root of the cdrom for cd1 it looks for win51ip.sp1.  If setup does not find this file in the root, it\'ll prompt you for the cd.  So look at your txtsetup.sif file and see what file it\'s looking for.

-gosh

[modown]

i had exactly the same situation few days ago. i found the solution too...

what i had done:
i have copied only the i386-directory from w2k server CD, and i built a bootable w2k CD with WinCDMan 1.03.

what i should have done:
inserted the w2k server CD and let the WinCDMan take everything it wanted from there.

there are some files in the CD which are needed, i386 directory is not enough. this was a stupid mistake i made, but easy to correct.

[Anonymous]

You need to make sure the following files are in the root of the CD:
CDROM_IA.5, CDROM_NT.5 (Advanced Server) CDROM_IS.5, CDROM_NT.5 (Server)
CDROM_IP.5, CDROM_NT.5 (Professional)

Be sure to copy the spnotes and cdromsp3.tst (if integrated SP3 to W2K).

Then use Nero or CDRWIN to make the bootable CD and it should do just fine.


If all else fails, try these links:

http://www.nu2.nu/bootcd/
http://www.bink.nu/Bootcd/default.htm

They have excellent guidelines on the material.

[Anonymous]

Those links are wonderful, but there is something wrong.  When you attempt to make an all 2k bootable CD with sp3, you cannot install any os at all.  It says there is something wrong with txtsetup.sif in the section [SourceDisksFile] for key sp3.cab  and it says value 0 is missing or corrupt.

I\'ve tried a few guesses at how to fix this, but none worked out.

If anyone figured this out, please email me at [email protected]
or
zzskylineEmail Removed

[evslin]

Best advice I can think of is redo the whole operation.  I slipstreamed SP3 into a Win2k pro (edited the setupp.ini file to disable upgrade eligibility check and not ask for cd key) and it worked the first try.  The only immediate concern I have is on the first boot a program which I had never seen or heard of in the 3 years that I\'ve been using 2k crashed.  I posted a screenshot of the entry in the application log at http://home.earthlink.net/~evslin/images/error.jpg.  Naturally I can\'t remember the program name and apparently neither can Windows.  The error didn\'t happen again, so maybe it was a one-time thing, but you gotta wonder. http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/wink.gif\' class=\'bbc_emoticon\' alt=\'\' />

[DeanJ]

We encountered the same error, we were easily able to create a streamline unattend setup CD with Windows 2000 Sp2, but when we tried it with SP3 we get The following value in the .SIF file used by Setup is corrupted or missing:

Value 0 on the line section [SourceDisksFiles] with key \"sp3.cab.\"

[johnm]

I had the same error  with source disk files , value 0 ,  as  DeanJ.
 I got the error during a repair session.

[gosh]

The best way to make an all in one cd is to do everything from scratch - dont use any wizards.  Then when your done in your mind picture how the cd boot's, from when setupldr starts setupdd.sys for text mode to the file copy phase.  Usually problems with all in one cd's are fixed when you go through the boot process.

-gosh

[meg]

I tried to slipstream sp3 to win2k (copied all I386 files to a disk, remove the read-only attributes to make sure), but always give me an error that say some or not all of the sp files were copied. Is this a known issue?

Thanks... http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/huh.gif\' class=\'bbc_emoticon\' alt=\':huh:\' />