Win2000 Boot CD ??
Posted 12 August 2001 - 06:10 PM
Posted 12 August 2001 - 08:22 PM
Posted 13 August 2001 - 02:31 AM
Posted 13 August 2001 - 08:26 AM
I hope to have my computer assembled this week & will try to install it.
Posted 15 August 2001 - 04:52 PM
Posted 15 August 2001 - 08:07 PM
Posted 16 August 2001 - 12:08 AM
Posted 16 August 2001 - 03:20 AM
Posted 16 August 2001 - 07:33 AM
Posted 16 August 2001 - 07:57 AM
Yes, the PID area is not in the setup.inf file. You have to copy it in, then it'll work like a charm.
Posted 23 August 2001 - 08:22 PM
Posted 24 August 2001 - 09:19 AM
Posted 28 August 2001 - 08:45 AM
Posted 29 August 2001 - 05:25 PM
The best way that I've found is to run the setupmgr.exe file from deploy.cab (comes on win2k cd under the supporttools directory) and generate an answer file. If you place this file in the i386 directory on a bootable Win2K install CD and call it "WINNT.SIF" it will be used as an answer file for installs that boot off of the CD.
You can specify all kinds of things in that file. I would
recommend a good read of the unattend.doc that comes in that deploy.cab file and hand editing the WINNT.SIF file. It's pretty cool the things you can put in there.
For further customizations you can place files in a directory called $OEM$ off of the ROOT of the CD (NOT under the i386 directory like on network installs) and the Win2K install will use this as a OEM install files directory when installing from booting off the CD. You can place drivers under there and place commands to be run during the setup into the "cmdlines.txt" file. I put a customized NTUSER.DAT file onto the cd and called a a batch file from cmdlines.txt that overwrote the default user's with it to setup defaults for the machine. I also put a .reg file and merged a bunch of keys into the registry inside the same batch file. It's really nice to do that way because you set the defaults for all the users. I get rid of all that frilly web stuff in the Explorer folder views before I even see it.
It's also great to put network card drivers onto the CD for cards that aren't supported by default in WIN2K. It's such a pain to go dig up or create a driver CD for each type of NIC you run into while doing installs. I put them all in there and added them to the cd using the $1 directory that get's mapped to the primary win2k drive (usually C) under Driversmachinetypenic folders and then added them to the
OemPnPDriversPath in the WINNT.SIF file so that it installs the drivers for the cards during the setup process. It's really slick.
HINT: You can use the %USERPROFILE% variable in a batch file running out of cmdlines.txt to reference the default user's directory. It's usually C:Documents and SettingsDefault User but not always if you are upgrading.
That's how I copy the NTUSER.DAT file into the default user profile directory. It didn't seem to work if I put the command into the cmdlines.txt file but it worked in a batch file called from cmdlines.txt. The working directory for commands run out of the cmdlines.txt is the $OEM$ directory on the CD so you can reference files under there relatively i.e. .NTUSER.DAT If you want to poke around put a cmd.exe line into cmdlines.txt and run a shell.
Posted 01 September 2001 - 10:05 AM
turned on power, went into BIOS, made settings,Inserted the Win2000 Cd, Powered down, Powered up, answered a couple of prompts and it installed Win2000. It did not ask for any boot floppies, the Win2000 CD was self booting.
I'm kinda dense, again WHY are the 4 boot floppies needed that everone wants?
The Epox 8K7A+ MoBo/RAID 0, AMD 1.4/1.6GHz, IBM 75GXP 30GB HDs, Crucial 2100 512MB is a great system
Posted 01 September 2001 - 10:46 AM
Posted 01 September 2001 - 04:29 PM
Once these disks are made, then you WILL have a WAY to boot the computer, and further your failed atempt with the CD-ROM way, and install very happily the OS' that ran stable for at least 120 days under a very strenous test. (correct me?)
Posted 04 September 2001 - 01:50 PM
> There are other files besides the basic install files that are needed, to make the CD bootable (and are generally left out of such "distributions"). That's why I left out the files that are needed to boot the cd
I'm confused - what files did you "leave out", and left them out from where? I have the full Win2K CD and followed the instructions in your article (using CDRWin 4.0a beta), but my finished CD gives me "NTLDR not found" - won't boot.
What files might I have "left out"??
Thanks for any help!
Posted 04 September 2001 - 01:58 PM