Help
Ultimate Slipstream Guide (almost)
#2
Davros 
- enthusiast
- Group: Members
- Posts: 347
- Joined: 21-March 02
Posted 31 July 2002 - 04:03 AM
For service pack 3, the commands are a bit different.
Download SP3.
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.
Download SP3.
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.
#3
SHS
- veteran
-
- Group: Moderators
- Posts: 1245
- Joined: 16-July 99
Posted 31 July 2002 - 04:22 AM
And what wrong with my Slipstream Guide DosFreak
http://www.ntcompatible.com/content.php?page_id=15
Davros you should be able to unpack the file, I guest when get this new sp3 download I find out.
When did add new option /S
http://www.ntcompatible.com/content.php?page_id=15
Davros you should be able to unpack the file, I guest when get this new sp3 download I find out.
When did add new option /S
#7
Davros
- enthusiast
- Group: Members
- Posts: 347
- Joined: 21-March 02
Posted 01 August 2002 - 02:47 AM
Quote:
then it should be "w2ksp3.exe -s:c:\w2kcd"
You can use -s or /s. They are both interpreted correctly. My personal default setting is /
I guess that's why I wrote / before when - is listed in the options.
#8 Guest__*
Posted 01 August 2002 - 09:18 PM
In order to perform the boot disk update, do you need to be running win2k? I tried running it under winxp pro, but the files were not updated, an error in the command window read something like, "extract not a valid command or filename". Indeed all 4 of the boot disk images were copied to the directory I ran the script from, but they still retained their original date of creation and modification, so in other words, they weren't updated. (Note: Yes, I ran the script after slipstreaming the SP3 update, which worked beautifully I must say, and I do thank you kindly for the instructions).
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.soundcardcentral.com/funstuff/slipstream/bdup.cmd is broken.
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.soundcardcentral.com/funstuff/slipstream/bdup.cmd is broken.
#9
DosFreak
- Carpal Tunnel
-
- Group: Moderators
- Posts: 3885
- Joined: 04-February 00
Posted 01 August 2002 - 09:25 PM
Nope, go the OS doesn't matter for BDUP.CMD as long as it's NT. It requires NT due to the .CMD extensio and primarily because of EXTRACT.EXE .
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.
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.
#10 Guest__*
Posted 01 August 2002 - 09:47 PM
Quote:
*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.
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.
#11
DosFreak
- Carpal Tunnel
-
- Group: Moderators
- Posts: 3885
- Joined: 04-February 00
Posted 01 August 2002 - 09:48 PM
FOUND IT.
DO NOT USE ANY OTHER EXTRACT BUT THIS ONE!\
EXTRACT
From Winimage's Site:
http://ourworld.compuserve.com/homepages/gvollant/extrac21.zip
ftp://ftp.winimage.com/extrac21.zip
Place the EXTRACT.EXE from the .zip into your SYSTEM32 or add it to your PATH.
This is why BDUP.CMD was not working.
DO NOT USE ANY OTHER EXTRACT BUT THIS ONE!\
EXTRACT
From Winimage's Site:
http://ourworld.compuserve.com/homepages/gvollant/extrac21.zip
ftp://ftp.winimage.com/extrac21.zip
Place the EXTRACT.EXE from the .zip into your SYSTEM32 or add it to your PATH.
This is why BDUP.CMD was not working.
#12
DosFreak
- Carpal Tunnel
-
- Group: Moderators
- Posts: 3885
- Joined: 04-February 00
Posted 02 August 2002 - 07:07 PM
Yep, the procedure that I will list in the Guide for WinISO.
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. (Updating 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.
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. (Updating 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.
#13
DosFreak
- Carpal Tunnel
-
- Group: Moderators
- Posts: 3885
- Joined: 04-February 00
Posted 02 August 2002 - 07:09 PM
Also to clear things up in case people get confused. If your EXTRACT.EXE does not have the -I option. Then do not use it. So to verify that you have the porper one in your path simply go to your Command line and run EXTRCT. If you do not see the -I option then you will need to download EXTRACT from the link I posted.
#14 Guest__*
Posted 02 August 2002 - 08:53 PM
Quote:
*Was testing last night and it seems that BDUP.CMD no longer works. Strange, because it worked a couple of months ago....
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!
#15
DosFreak
- Carpal Tunnel
-
- Group: Moderators
- Posts: 3885
- Joined: 04-February 00
Posted 02 August 2002 - 09:01 PM
Check the datetime stamp in the images that you created. They should match the datetime stamp in SP3 if they updated correctly.
For me I get the same datetime stamp as in the original bootdisks.
For me I get the same datetime stamp as in the original bootdisks.
#16 Guest__*
Posted 02 August 2002 - 10:21 PM
Quote:
Check the datetime stamp in the images that you created.
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.
#17 Guest__*
Posted 02 August 2002 - 11:46 PM
I've been playing around with the script for a while, and I don't believe there is anything wrong with it. I do believe the problem lies in extract.exe. Testing the program by hand, it seems extract isn't inserting the files like it should with the -i switch. The problem seems to be in overwriting files which are already in the img file. I have successfully used extract -i to inject a different file (a small txt), which then ended up with the correct date stamp, size, etc. Although success is reported by the program when inserting a file which already exists in the image, it's simply not true. I also attempted using a -oi switch, since I noticed the extract files command had an overwrite option, but my efforts were unsuccessful. Please test extract.exe for yourself, and determine if you believe this is the problem also.
#18
shearerc
- newbie
- Group: Members
- Posts: 31
- Joined: 23-July 02
Posted 04 August 2002 - 10:58 PM
Quote:
Nero Burning ROM v5.5.6.9
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 5.5.8.2 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?
