DVD recording process

1. DVD recorders in the closet should be on already and should not be turned off. If the power happens to be off, press the power button to turn the machine on, but there is a time lag of 5-10 minutes before the machine is ready to record.
2. Press the [OPEN/CLOSE] button to open the DVD drive bay and insert the DVD-Ram disk. Do not use DVD-R, DVD-RW, or CD-RW disks.
3. Press the [OPEN/CLOSE] button again to close the drive.
4. Press the [CHANNEL UP / DOWN] button to set the recorder to your office channel.
5. Press the [RECORD] button to begin recording.
6. Flip the camera switch in your office to [ON] after the client gives their consent to be recorded.
7. When recording is finished, press the [STOP] button.
8. Press the [OPEN/ CLOSE] button to open the drive door and remove the disk from the drive. Press the [OPEN/ CLOSE] button again to close the drive.

DVD recording process

Burn DVD
Menu: Project - Burn DVD from disk

This is the last step in the DVD creation process.


With our DVD Project having been Compiled, there are a set of files that DVD-lab has prepared for you in the Output folder as set in the Compile process. At this point, the DVD Author has choices as to how to convert this set of files into a DVD master disc. You can either use the DVD-lab built-in recording module or you can choose to use a third party DVD recording software such as Nero, Prassi, Gear, etc...



It is common that you are supplied with a DVD recording software that was bundled with your DVD-R/DVD+R burner. This software may be better optimized for your particular drive. The DVD-lab built-in DVD recording module is a general ASPI writing application and should work fine. In an ideal world, either one would work equally well.

DVD-lab Disc record window

The DVD-lab Disc record window is automatically detached. That means it runs as a separate process independent from DVD-lab, you could even close DVD-lab and the recording will continue.


Here are some of the parameter choices for the DVD-lab Disc record window.

Input Folder
The Input Folder is the same as the Output folder in Compile. That means this is the folder where the VIDEO_TS and AUDIO_TS folders are expected to be.

Device
The DVD recording drive you want to write to, presented as the O/S recognizes it.

Media Type
Set if you want to burn DVD Video or a Mini-DVD.
Mini-DVD is a DVD format burned on the CD-R. Obviously you can put far less data on a CD-R (about 700 MB) than on DVD (4.3 GB)




The size indicator on the bottom can help you to determine how much data you can record to the disc. You have to keep your data below the red area.



Note: While you will be able to play the CD-R on a computer not all standalone players will be able to play the Mini-DVD. In fact such format is not officially supported. The reason is that CD's have far less density of data so in order to play the large DVD video bitrate they have to spin much faster than DVD. Not all DVD drives in players are ready for this so the functionality to DVD files from CD-R is often simply disabled. However a number of Asian or re-branded Asian US models of players use a standard PC type of DVD drive which allows for fast spin of CD.

DVD-RW/DVD+RW Tools
For those using a re-writable media, the DVD-RW needs to be formatted if they were already used - click the Erase/Format button to do this. The more common DVD-R media do not need any formatting.

The DVD-RW and +RW needs to be finalized after writing. This takes quite a large amount of time on RW media. Please be patient until this important process is completed.

Options
Test Write checkbox
Use this option by checking the Test Write checkbox to have DVD-lab do a trial run at writing a DVD. This option does not write anything to disk or your hard drive, it merely goes through the motions to insure that all of the content and menus within the DVD project are correctly prepared and defined.


Volume Name input
Enter here a name for the DVD volume that will appear when placed in a computer drive. A standalone DVD player just ignores this.


Create Image checkbox
You can choose to have DVD-lab create a large file on your hard drive which is an the image of a DVD disc instead of burning. The result will be one big IMG file. That IMG file can be used with a number of third party DVD recording software to replicate a DVD disc from this image file, as many times as you like, whenever you like. Some software will look for a ISO file name extension, if so, just rename the file to a .ISO extension. This method has the advantage of speed as the DVD image is all prepared on your hard drive, it is then a just matter of how fast your DVD burner drive will burn that image.


Hybrid DVD Writing button
You can add additional files and folders to the DVD master disc with the Hybrid DVD Writing option. What this option will do is setup an alternate filesystem on the DVD master disc which is called an ISO filesystem. The ISO format is what a standard CD uses while the DVD video is in UDF/ISO. This is perfectly DVD "legal" as the DVD player doesn't know or care about this ISO filesystem's contents, it just looks for a UDF filesystem.

It doesn't matter at all what the content or nature of these files are. They are just files, not Windows or Mac or Linux files, just files. As they are recorded into the ISO file system domain, they are available on any computer with a DVD drive. This offers the DVD-lab Author some creative options for bonus content that would be available to a computer user on any O/S that supports a DVD drive.



For example, you can create an autorun project in Multimedia Builder and record it to DVD as an extra feature when used on PC. HTML based content may be placed here as well, be sure to indicate to your computer users where to find your HTML starting page (ex: index.html).

Note: The space used by the Hybrid DVD Writing option counts in the entire Project space value. You only get so much space on a DVD (4.7G), this option uses part of that. Do the math to be sure you have room for this extra area.


Write button
As expected, click this button to start the DVD writing (burn) process.

Note: It is not recommended to do any work on the computer during DVD writing. Things like reading/writing to hard-drive may easily ruin your DVD-R. Try to let the burning process be the only thing your computer is running until it is completed.

CPU socket

A CPU socket or CPU slot is a connector on a computer's motherboard that accepts a CPU and forms an electrical interface with it. As of 2007, most desktop and server computers, particularly those based on the Intel x86 architecture, include socketed processors.

Most CPU-sockets interfaces are based on the pin grid array (PGA) architecture, in which short, stiff pins on the underside of the processor package mate with holes in the socket. To minimize the risk of bent pins, zero insertion force (ZIF) sockets allow the processor to be inserted without any resistance, then grip the pins firmly to ensure a reliable contact after a lever is flipped.

As of 2007, several current and upcoming socket designs use land grid array (LGA) technology instead. In this design, it is the socket which contains pins. The pins contact pads or lands on the bottom of the processor package.

In the late 1990s, many x86 processors fit into slots, rather than sockets. CPU slots are single-edged connectors similar to expansion slots, into which a PCB holding a processor is inserted. Slotted CPU packages offered two advantages: L2 cache memory could be upgraded by installing an additional chip onto the processor PCB, and processor insertion and removal was often easier. However, slotted packages require longer traces between the CPU and chipset, and therefore became unsuitable as clock speeds passed 500 MHz. Slots were abandoned with the introduction of AMD's Socket A and Intel's Socket 370.

CPU package types

1.)S.E.C.C. Package Type

S.E.C.C. is short for Single Edge Contact Cartridge. To connect to the motherboard, the processor is inserted into a slot. Instead of having pins, it uses goldfinger contacts, which the processor uses to carry its signals back and forth. The S.E.C.C. is covered with a metal shell that covers the top of the entire cartridge assembly. The back of the cartridge is a thermal plate that acts as a heatsink. Inside the S.E.C.C., most processors have a printed circuit board called the substrate that links together the processor, the L2 cache and the bus termination circuits. The S.E.C.C. package was used in the Intel Pentium II processors, which have 242 contacts and the Pentium® II Xeon™ and Pentium III Xeon processors, which have 330 contacts.



2.)S.E.C.C.2 Package Type


The S.E.C.C.2 package is similar to the S.E.C.C. package except the S.E.C.C.2 uses less casing and does not include the thermal plate. The S.E.C.C.2 package was used in some later versions of the Pentium II processor and Pentium III processor (242 contacts).




3.S.E.P. Package Type


S.E.P. is short for Single Edge Processor. The S.E.P. package is similar to a S.E.C.C. or S.E.C.C.2 package but it has no covering. In addition, the substrate (circuit board) is visible from the bottom side. The S.E.P. package was used by early Intel Celeron processors, which have 242 contacts.



4.FC-PGA Package Type

The FC-PGA package is short for flip chip pin grid array, which have pins that are inserted into a socket. These chips are turned upside down so that the die or the part of the processor that makes up the computer chip is exposed on the top of the processor. By having the die exposed allows the thermal solution can be applied directly to the die, which allows for more efficient cooling of the chip. To enhance the performance of the package by decoupling the power and ground signals, FC-PGA processors have discrete capacitors and resistors on the bottom of the processor, in the capacitor placement area (center of processor). The pins on the bottom of the chip are staggered. In addition, the pins are arranged in a way that the processor can only be inserted one way into the socket. The FC-PGA package is used in Pentium® III and Intel® Celeron® processors, which use 370 pins.



5.FC-PGA2 Package Type

FC-PGA2 packages are similar to the FC-PGA package type, except these processors also have an Integrated Heat Sink (IHS). The integrated heat sink is attached directly to the die of the processor during manufacturing. Since the IHS makes a good thermal contact with the die and it offers a larger surface area for better heat dissipation, it can significantly increase thermal conductivity. The FC-PGA2 package is used in Pentium III and Intel Celeron processor (370 pins) and the Pentium 4 processor (478 pins).



6.OOI Package Type

OOI is short for OLGA. OLGA stands for Organic Land Grid Array. The OLGA chips also use a flip chip design, where the processor is attached to the substrate facedown for better signal integrity, more efficient heat removal and lower inductance. The OOI then has an Integrated Heat Spreader (IHS) that helps heatsink dissipation to a properly attached fan heatsink. The OOI is used by the Pentium 4 processor, which has 423 pins.



7.PGA Package Type

PGA is short for Pin Grid Array, and these processors have pins that are inserted into a socket. To improve thermal conductivity, the PGA uses a nickel plated copper heat slug on top of the processor. The pins on the bottom of the chip are staggered. In addition, the pins are arranged in a way that the processor can only be inserted one way into the socket. The PGA package is used by the Intel Xeon™ processor, which has 603 pins.



8.PPGA Package Type

PPGA is short for Plastic Pin Grid Array, and these processors have pins that are inserted into a socket. To improve thermal conductivity, the PPGA uses a nickel plated copper heat slug on top of the processor. The pins on the bottom of the chip are staggered. In addition, the pins are arranged in a way that the processor can only be inserted one way into the socket. The PPGA package is used by early Intel Celeron processors, which have 370 pins.

Form Factors of the Motherboard

NLX (New Low Profile Extended) was a form factor proposed by Intel and developed jointly with IBM, DEC, and other vendors for low profile, low cost, mass-marketed retail PCs. Release 1.2 was finalized in March 1997 and release 1.8 was finalized in April 1999. NLX was similar in overall design to LPX, including a riser card and a low-profile slimline case. It was modernized and updated to allow support for the latest technologies while keeping costs down and fixing the main problems with LPX.

Many slimline systems that were formerly designed to fit the LPX form factor were modified to fit NLX. NLX is a true standard, unlike LPX, making interchangeability of components easier than it was for the older form factor. IBM, Gateway, and NEC produced a fair number of NLX computers in the late 1990s, primarily for Socket 370 (Pentium II-III and Celeron), but NLX never enjoyed the widespread acceptance that LPX had. Most importantly, one of the largest PC manufacturers, Dell decided against using NLX and created their own proprietary motherboards for use in their slimline systems. Although many of these computers and motherboards are still available secondhand, new production has essentially ceased, and in the slimline and small form factor market, NLX has been superseded by the Micro-ATX, FlexATX, and Mini-ITX form factors



LPX (form factor)

LPX (Low Profile eXtension), originally developed by Western Digital, was a loosely defined motherboard format (form factor) widely used in the 1990s.

There was never any official LPX specification, but the design normally featured the main I/O ports mounted on the back of the motherboard (something that was later adopted by the ATX form factor), and a riser card in the center of the motherboard, on which the PCI and ISA slots were mounted. Due to the lack of standardised specification, riser cards were seldom compatible from one motherboard design to another, much less one manufacturer to another. The internal PSU connector was of the same type used in the AT form factor; most LPX cases were compatible with AT power supplies, though some used models that were smaller than standard, and usually manufacturer-specific.

The specification was very popular in the early-mid 90's, and briefly displaced the AT form factor as the most commonly used. However, the release of the Pentium II in 1997 highlighted the flaws of the format, as a good airflow was important in Pentium II systems, owing to the relatively high heat dispersal requirements of the processor. LPX systems suffered a restricted airflow due to the centrally placed riser cards. The introduction of the AGP format further complicated matters, as the design not only increased the pincount on riser cards, but it limited most cards to one AGP, one PCI and one ISA slot, which was too restrictive for most users. Some lower-quality LPX boards didn't even feature a real AGP slot, but simply used a physical AGP slot and connected it to the PCI bus. This was seldom noticed however, as many "AGP" graphics cards of the time were in fact PCI cards internally, and did not take advantage of the features offered by AGP.

LPX was phased out around 1998. NLX was the intended successor, though many manufacturers chose MicroATX or proprietary motherboard formats instead.



ATX (form factor)

The ATX (for Advanced Technology Extended) form factor was created by Intel in 1995. It was the first big change in computer case and motherboard design in many years. ATX overtook AT completely as the default form factor for new systems. ATX addressed many of the AT form factor's annoyances that had frustrated system builders. Other standards for smaller boards (including microATX, FlexATX and mini-ITX) usually keep the basic rear layout but reduce the size of the board and the number of expansion slot positions. In 2003, Intel announced the new BTX standard, intended as a replacement for ATX. As of January 2007 the ATX form factor remains the industry standard for do-it-yourselfers; BTX has however made inroads into pre-made systems, being adopted by computer makers like Dell, Gateway, and HP.

The official specifications were released by Intel in 1995, and have been revised numerous times since, the most recent being version 2.2[1], released in 2004.

A full size ATX board is 12" wide by 9.6" deep (305 mm x 244 mm). This allows many ATX form factor chassis to accept microATX boards as well.

ATX was originally designed with the power supply drawing air into the case and exhausting it down onto the motherboard. The plan was to deliver cool air directly to the CPU's and power regulation circuitry's location, which was usually at the top of the motherboard in ATX designs. This was not particularly useful for a variety of reasons. Early ATX systems simply didn't have processors or components with thermal output that required special cooling considerations. Later ATX systems with significantly greater heat output would not be aided in cooling by a power supply delivering its often significantly heated exhaust into the case. As a result, the ATX specification was changed to make PSU airflow optional.[2]

With the introduction of the Pentium 4, the standard 20-pin ATX power connector was deemed inadequate to supply increasing electrical load requirements. The standard was revised with an extra 4-pin, 12-volt connector. This was later adopted by Athlon XP and Athlon 64 systems. Various high-end systems may have other forms of supplemental power connections.

Because video card power demands have dramatically increased over the 2000s, some high-end graphics cards have power demands that exceed AGP or PCIe slot capabilities. For these cards, supplementary power was delivered through a standard power connector like those used for hard drives or floppy drives. PCI Express-based video cards manufactured after 2004 typically use a standard 6 or 8-pin PCIe power connector directly from the PSU.

Because the ATX PSU uses the motherboard's power switch, turning on the power in situations that do not utilize an ATX motherboard is possible by shorting the green wire from the ATX connector to any black wire on the connector (or ground). This allows re-use of an old PC power supply for tasks other than powering a PC, but one must be careful to observe the minimum load requirements of the PSU.

The ATX form factor has had five, main power supply designs throughout its lifetime:

ATX - 20 pin connector (Used through Pentium III and early Athlon XP)
WTX - 24 pin connector (Pentium II and III, Xeon and Athlon MP)
AMD GES - 24 pin main connector, 8 pin secondary connector (some dual-processor Athlon)
EPS12V - 24 pin main connector, 8 pin secondary connector, optional 4 pin tertiary connector (Xeon and Opteron) defined in SSI specification
ATX12V - 20 pin main connector, 4 pin secondary connector, 8 pin tertiary connector (Pentium 4 and mid/late Athlon XP & Athlon 64)
ATX12V 1.3 - guidance for the -5 volt feed was removed. This was only used by legacy ISA add-in cards
ATX12V 2.0 - 24 pin main connector, 4 pin secondary connector (Pentium 4, Core 2 Duo, and Athlon 64 with PCI Express)
ATX12V 2.2 - One 20/24-pin connector, one ATX12V 4 pin connector. Many power supply manufacturers include a 4 plus 4 pin, or 8 to 4 pin secondary connector instead, which can also be used as the secondary EPS12V connector.



AT and Baby AT

Up until recently, the AT and baby AT form factors were the most common form factor in the motherboard world. These two variants differ primarily in width: the older full AT board is 12" wide. This means it won't typically fit into the commonly used "mini" desktop or minitower cases. There are very few new motherboards on the market that use the full AT size. It is fairly common in older machines, 386 class or earlier. One of the major problems with the width of this board (aside from limiting its use in smaller cases) is that a good percentage of the board "overlaps" with the drive bays. This makes installation, troubleshooting and upgrading more difficult.

The Baby AT motherboard was, through 1997, the most common form factor on the market. After three years and a heavy marketing push from Intel, the ATX form factor is now finally overtaking the AT form factor and from here out will be the most popular form factor for new systems. AT and Baby AT are not going anywhere, however, because there are currently just so many baby AT cases, power supplies and motherboards on the market. These will need an upgrade path and I believe that at least some companies will make motherboards for the newer technology in AT form factor for some time, to fill this upgrade market demand.

Baby AT motherboards are distinguished by their shape, and usually by the presence of a single, full-sized keyboard connector soldered onto the board. The serial and parallel port connectors are almost always attached using cables that go between the physical connectors mounted on the case, and pin "headers" located on the motherboard.

The AT and Baby AT form factors put the processor socket(s)/slot(s) and memory sockets at the front of the motherboard, and long expansion cards were designed to extend over them. When this form factor was designed, over ten years ago, this worked fine: processors and memory chips were small and put directly onto the motherboard, and clearance wasn't an issue. However, now we have memory in SIMM/DIMM sockets, not directly inserted onto the motherboard, and we have larger processors that need big heat sinks and fans mounted on them. Since the processor is still often in the same place, the result can be that the processor+heat sink+fan combination often blocks as many as three of the expansion slots on the motherboard! Most newer Baby AT style motherboards have moved the SIMM or DIMM sockets out of the way, but the processor remains a problem. ATX was designed in part to solve this issue.

AT
(form factor)

The AT form factor was the first modern form factor to be widely used. AT (Advanced Technology) was released in 1984 by IBM. Unlike the PC and XT form factors that preceded it, AT became a widely used design as a result of the booming home computer market in the 1980s. IBM clones made at the time began using AT compatible designs, contributing to its popularity. In the 1990s many computers still used AT and its variants, but ATX has been the most popular standard since 1997.
Design
Main article: Industry Standard Architecture
The original AT motherboard, later known as "Full AT", is 12 inches (305 mm) wide and 13.8 inches (350 mm) deep, which means it will not fit in "mini desktop" or "minitower cases". The board's size also means that it takes up space behind the drive bays, making installation of new drives more difficult. The power connectors for AT motherboards are two nearly identical 6-pin cords. Unfortunately, the two power connectors it requires are not easily distinguishable, leading many people to damage their boards when they were misconnected. However, technicians need only remember the phrase "black wires together in the middle" or "red and red and you are dead" to prevent this. When plugged in, the two black wires on each connector must be adjacent to each other, creating a row of 4 black cords (out of the total 12) and a correct connection.
Variants

installation and procedure (Windows 98)

How to Install Windows 98
After you partition and format your hard disk, you can install Windows 98: 1. Insert the Windows 98 Startup disk in the floppy disk drive, and then restart your computer.
2. When the Windows 98 Startup menu is displayed, choose the Start computer with CD-ROM support option, and then press ENTER.
3. If CD-ROM support is provided by the generic drivers on the Startup disk, you receive one of the following messages, where X is the drive letter that is assigned to your CD-ROM drive:
Drive X: = Driver MSCD001

Drive X: = Driver OEMCD001
NOTE: If your CD-ROM drive is not available after you boot from the Windows 98 Startup disk, install the CD-ROM drivers that are included with your CD-ROM drive. For information about how to obtain and install the most current driver for your CD-ROM drive, view the documentation that is included with your device, or contact your hardware manufacturer.


4. Insert the Windows 98 CD-ROM in the CD-ROM drive, type the following command at a command prompt, and then press ENTER
X:\setup
where X is the drive letter that is assigned to your CD-ROM drive.

5. When you receive the following message, press ENTER, and then follow the instructions on the screen to complete the Setup procedure:
Please wait while the Setup initializes. Setup is now going to perform a routine check on your system. To continue press Enter.

HOW TO INSTALL THE WINDOWS 98 UPGRADE ON A NEW HARD DISK DRIVE
Last updated: 07/29/03
PROCEDURE. A simple solution to the problem is to "put the cart before the horse." That is, Install FAT32 on the new hard disk before installing Windows. Here's how (do the following steps at your own risk):

Preferably, before buying it, make sure your computer will support the new drive (LBA, cable, drive bays,, etc.). I am assuming here that both drives are IDE hard disks.

Make sure your old hard disk is in good condition. Run SpinRite, scandisk or chkdsk/f and fix any problems.

Back-up your old hard disk, or, at minimum, backup everything that is important: accounting data, documents, Internet Favorites, etc. In particular, back-up your CD-ROM driver, AUTOEXEC.BAT, and CONFIG.SYS.

Make and test a Windows 98 Startup floppy.

This can be done from the Windows 98 Upgrade CD without first installing Windows 98. Put the XCOPY files on the Startup Floppy (see my instructions) if you have Windows or Windows for Workgroups 3.x on your old hard disk, and you want to move the contents of the old hard disk to the new one and perform an upgrade on top of your old Windows (i.e., actually upgrade it). XCOPY cannot be used to move Windows 95 from an old disk to a new one, but XCOPY should be handy for moving application and data files.

Unfortunately, the Windows 95/98 XCOPY command will not copy system and hidden files when used from the DOS prompt. Also, in general, Windows 95/98 cannot be copied from one hard disk to another and work by simply copying files. There are other programs which claim to have the ability to move Windows 95 from one hard disk to another by copying files, but I don't use them. There are programs, such as Powerquest's PartitionMagic and Samantec's Ghost, which can copy an image of a partition on an old drive to a new drive and expand the partition on the new drive, and Windows will work if copied using this method. Western Digital WD DIAGS has this capability, albeit limited, as well.

Shut-down, power-off, unplug the power cord, and remove your old hard disk. Install your new hard disk as a master, single-drive.

To avoid a serious mistake, I always remove the old hard disk before running FDISK or FORMAT on a new one. I usually do not mount a new hard disk in a computer before completing the transfer of data from the old one. It's usually easier to plug and unplug cables when the drive is out of the case. Be sure to protect the bottom of the drive from shorting-out when laying it on the case or lay it on the case up-side-down.

Also, I usually remove all expansion boards from the computer except the display adapter and disconnect Zip drives, etc. Once Windows 98 and any motherboard-specific display adapter software is installed, I reinstall all of the expansion boards, etc., one-at-time.

Set-up your CMOS for the new drive. AMI and Award BIOS "Auto" should work on most new IDE drives.

installation and procedure (Windows 2000)

--------------------------------------------------------------------------------

During a standalone installation, hotfixes are applied to a computer that is already running Windows 2000. When you run the hotfix package, it automatically installs the updated system files and makes the necessary registry changes. After the computer is restarted (required only for some system files that are used during the installation), the installation is complete and Windows 2000 runs with an updated file set.

You can install hotfixes by running the hotfix package, which extracts the hotfix files and runs the Update.exe installation program. Update.exe then checks the service pack version you are currently using. If the service pack version was released before the hotfixes, and the language is the same, the Update.exe program installs the hotfixes automatically. If your service pack version was released after the hotfixes, the installation is not completed and an error message appears, stating that the version is incorrect.

Note

If your service pack version was released after the hotfixes, and you were completing an unattended installation (using either the /U or /Q option), Setup does not continue and no message appears.

If the language of the hotfixes does not match the language you have set up for Windows 2000, Setup does not continue. If there are no version conflicts, Setup continues the installation. The Update.exe program registers the hotfixes under the following registry keys:

HKEY_LOCAL_MACHINE \Software\Microsoft\WindowsNT\CurrentVersion\Hotfix\
KB######

HKEY_LOCAL_MACHINE \Software\Microsoft\Updates\Windows 2000\SP5\KB######

During the installation, information for removing the hotfixes is stored in a hidden folder named systemroot\$NtUninstallKB######$.For information about removing hotfixes, see Removing Windows 2000 Hotfixes later in this document.

The following sections describe how to install Windows hotfixes from a shared network distribution folder.

Standalone Installation Methods
There are several ways you can perform a standalone installation. These include running the Windows2000-KB######-x86-LLL.exe program manually with a combination of installation options, using Microsoft Systems Management Server (SMS), or using Microsoft Windows Installer.

You can distribute hotfixes either by using a shared network distribution folder or by downloading the hotfixes from the Web. Because this guide is intended primarily for corporate users, the standalone installation procedures in this guide focus on the shared network distribution method, which is the most common means of hotfix distribution for this audience.

The instructions in this section explain how to install hotfixes on computers that are already running Windows 2000.

Command-Line Options for the Hotfix Package
The following table identifies the command-line options that the hotfix package supports.

Command-line option Description
/F Forces other applications to close after installation is completed and before the computer restarts.
/N Does not back up files for removing hotfixes.
/Z Does not restart the computer after the installation is completed.
/Q Uses quiet mode; shows no user interface.
/U Uses unattended Setup mode. Requires no user interaction and shows only critical errors.
/L Lists installed hotfixes.


Installing Hotfixes on Computers Running Windows 2000
To install a single hotfix on a single computer

To install a Windows 2000 hotfix on a single computer, run the hotfix package on the computer that you want to update. The hotfix package is formatted as follows:

Windows2000-KB######-x86-LLL.exe

You can create a shared distribution folder on the network for the hotfix if you want to install it on more than one computer. The following procedure describes how to install one or more Windows 2000 hotfixes using this method.

Note

In the following procedure, Drive represents the drive of the network or computer where your distribution folder is located.

To install a hotfix by running a hotfix package from a shared distribution folder

Connect to the network or computer on which you want to create the distribution folder.
On the network or the computer, create a distribution folder for the hotfix files.
For example, to create a distribution folder named Hotfix, type the following:

mkdir Drive:\Hotfix

Navigate to the folder you want, right-click the folder, and then click Properties.
Click the Sharing tab, and then click Share This Folder.
In Share Name, enter a name for the folder.
Click Permissions, and then add permissions that allow users to install their hotfixes from this folder.
If you are using an NTFS file system partition, click the Security tab, confirm that the permissions listed there do not conflict with those on the Sharing tab, and then click OK.
Copy the Windows 2000 Hotfix package to the distribution folder that you created in step 2.
To install the hotfix from the shared network distribution folder, run:
Windows2000-KB######-x86-LLL.exe

For example, to install the hotfix from the distribution folder named Hotfix, you would type the following:

\\servername\sharename\Hotfix\Windows2000-KB######-x86-LLL.exe

Use the command-line options described in the table provided in the preceding section.

To ensure that your hotfixes take effect, restart your computer after you finish installing all of the hotfixes.
Installing Several Hotfixes Together
You can group multiple hotfixes together in a batch file and install them as a unit. This prevents you from having to restart your computer after each hotfix is installed.

The following code sample is a batch file that installs hotfixes and ensures that the correct files are replaced after the computer is restarted.

@echo off
setlocal
set PATHTOFIXES=Drive:\hotfix

%PATHTOFIXES%\Windows2000-KB######-x86-LLL.exe /Z /U
%PATHTOFIXES%\Windows2000-KB######-x86-LLL.exe /Z /U
%PATHTOFIXES%\Windows2000-KB######-x86-LLL.exe /Z /U
Important

To ensure that the hotfixes you installed take effect, restart the computer if the batch file does not automatically restart it for you.

The Combination Installation Back to Top

--------------------------------------------------------------------------------

The combination installation installs hotfixes and one or more of the following:

Windows 2000.
Windows 2000 service packs.
Additional software from Microsoft or other companies. This additional software might be included on a service pack CD.
This section provides instructions you can use to perform a combination installation that includes Windows 2000 and hotfixes in unattended Setup mode.

You can perform a combination installation by including the components that you want to install with the hotfixes as entries in the Svcpack.inf file. You can also choose to install SP4 at the same time.

Installing Windows 2000 with the Service Pack and Hotfixes
This section explains how to perform a combination installation of Windows 2000 integrated with the service pack and post-service pack hotfixes. It also explains how to copy to a shared distribution folder on your network each of the elements to be installed. This is part of preparing for a combination installation.

The combination installation makes it unnecessary for you to perform separate installations of Windows 2000, the service pack, or the Windows 2000 hotfixes.

Important

To install Windows 2000 with hotfixes, you must use the method described in this section.
Make sure that any hotfixes you install were released after the service pack version with which you want to install them. For more information about this, see article 290074, "Slipstreaming Earlier Fixes Into an Integrated Installation Share Breaks the Share," in the Microsoft Knowledge Base.
This process installs the Windows 2000 hotfixes during Windows 2000 Setup.
You cannot remove hotfixes that were installed by using the combination installation method unless you reinstall Windows 2000.
Preparing for the Combination Installation
Before you run Windows 2000 Setup to deploy the installation of Windows 2000, SP4, and hotfixes across a network, you must copy the installation files for Windows 2000 and the hotfixes to a shared distribution folder. You must then complete the additional steps described in the procedure, To create and set up the required folders and files, later in this section.

If you are an OEM, and you plan to install additional OEM files (for example, device driver, application, or component files) on the destination computers, create a \$1 subfolder within the \$OEM$ subfolder. The \$1 subfolder maps to systemdrive, the destination drive for the Windows 2000 combination installation.

Note

In the following procedure, Drive represents the drive name of the network or computer where your distribution folder is located.

To create and set up the required folders and files

Connect to the network or computer on which you want to create the distribution folder.
In the shared folder on the network, create a distribution folder for the Windows 2000 installation files. For example, to create a distribution folder named W2000, type the following:
mkdir Drive:\W2000\

Ensure that only the system administrator has full access to this folder. Other users should have only Read and Execute permissions.

To verify that you have assigned the appropriate permissions, use steps 3 through 7 in the preceding procedure, "To install a hotfix by running a hotfix package from a shared distribution folder."

Insert your Windows 2000 product CD into the CD-ROM drive, and then, using the following syntax, copy the contents of the CD to the distribution folder that you created in step 2:
xcopy /E /I /V D:\i386 Drive:\W2000\i386

Remove the Windows 2000 product CD from the CD-ROM drive, and then, to perform a combined installation that includes SP4, insert the service pack CD. Otherwise, to install hotfixes with Windows 2000 only, skip to step 7.
Apply the service pack source files to the Windows 2000 Installation files located in the folder named W2000\i386 by typing the following:
W2ksp4.exe /S:Drive:\W2000

Note

For a list of command-line options you can use with this command, see "Command-Line Options for Update.exe and W2ksp4," in Microsoft Windows 2000 Service Pack 4 Installation and Deployment Guide (SPDeploy.htm).

Edit Drive:\i386\dosnet.inf to add svcpack to the [OptionalSrcDirs] section as follows:
[OptionalSrcDirs]
uniproc
svcpack
Create a Drive:\i386\svcpack subfolder.
Copy the hotfix package (Windows2000-KB######-x86-LLL.exe ) to the Drive:\i386\svcpack folder by using the 8.3 naming format (KB######.exe), where ###### represents the actual hotfix number.
If you are deploying multiple hotfixes, copy and rename all of the hotfix executable files.

Expand the hotfix to a unique temporary location. For example, to expand the files to a folder called samplefolder, type the following:
Drive:\i386\svcpack\KB###### /X:Drive:\samplefolder

From samplefolder, for each hotfix, copy a catalog file (KB######.cat) and hotfix binary files (such as .exe, .dll, or .sys) as follows:
Copy KB######.cat to the Drive:\i386\svcpack folder. If you are deploying multiple hotfixes together, copy the catalog file from each of the hotfixes to be deployed. Each hotfix has a unique catalog file that you must copy in the format KB######.cat. Do not copy empty.cat.
If the same binary file exists in multiple hotfix packages, keep only the file with the highest version number.
For each binary file included in the package, determine whether the same file exists in the i386 folder. (You can usually identify these files in the shared folder by the underscore (_) at the end of each file name.) Delete these binary files that will be replaced in the i386 folder.
Copy the hotfix binary files and any subfolders for the hotfix to the i386 folder.
For example, i386\uniproc\* files in the hotfix must be copied to the i386\uniproc folder of the shared installation folder. You do not need to copy Update.exe, Update.inf, SPmsg.dll, SPcustom.dll, SPuninst.exe, Update.ver, or symbols files.

For each file copied in step 10 (except for KB######.cat), check Dosnet.inf to determine whether each hotfix binary file name is listed under the [Files] section. All files listed under [Files] are preceded by "d1,". This appears as follows:
d1,Filename

If a hotfix binary file name is not listed for each hotfix under the [Files] section, add an entry using the syntax:

d1,Filename.

For example, if a hotfix contains Win32k.sys, because Win32k.sys is not listed in Dosnet.inf, "d1,win32k.sys" must be added under the [Files] section of Dosnet.inf. This ensures that the hotfix version of Win32k.sys will be copied during Windows 2000 Setup.

Delete the Drive:\i386\Svcpack.in_ file.
Create a new Svcpack.inf file in Drive:\i386 by using the applicable following content, depending on whether you want to deploy a single hotfix or multiple hotfixes. (Replace ###### with the numbers for your hotfix .cat file).
To deploy a single hotfix, set up your file as follows:

[Version]
Signature="$Windows NT$"
MajorVersion=5
MinorVersion=0
BuildNumber=2195
[SetupData]
CatalogSubDir="\i386\svcpack"[ProductCatalogsToInstall]
KB######.cat
[SetupHotfixesToRun]
KB######.exe /options
The recommended options for hotfixes are /Q, /N, and /Z. These options prevent messages from being displayed on computers to which you are deploying the hotfixes. This makes the hotfix installation invisible to user.

To deploy multiple hotfixes, set up your file as follows:

If you are deploying multiple hotfixes simultaneously, add an entry for each hotfix under both [ProductCatalogsToInstall] and [SetupHotfixesToRun] (as shown in the example that follows).

The following lines illustrate how these sections they would appear for an installation in which multiple hotfixes are installed. If you are installing a service pack, you do not need to include details about the service pack because it is included in the installation, independent of this process.

[ProductCatalogsToInstall]
KB123456.cat
KB123478.cat
KB123490.cat
[SetupHotfixesToRun]
KB123456.exe /options
KB123478.exe /options
KB123490.exe /options
The recommended options for hotfixes are /Q, /N, and /Z.

Using Svcpack.inf to Deploy the Combination Installation
You can deploy Windows 2000 and the hotfixes to multiple computers from a shared distribution folder on a network. During the standard installation process, Windows 2000 Setup (Winnt.exe or Winnt32.exe in unattended Setup mode) installs the operating system and applies the hotfixes.

To deploy the installation

Customize Windows 2000 Setup, as necessary. For more information about how to do this, you can view Help by entering the following command from the deployment folder:
\i386\winnt32.exe /?

For more detailed information, see the Winnt32.exe command syntax topic in the Microsoft Windows 2000 Professional Resource Kit.

Run Windows 2000 Setup (Winnt.exe or Winnt32.exe in unattended Setup mode) to deploy the installation of Windows 2000 and the hotfixes to multiple computers from the shared distribution folder.
Removing Windows 2000 Hotfixes Back to Top

--------------------------------------------------------------------------------

You can use Add/Remove Programs in Control Panel to remove a Windows 2000 hotfix. You cannot remove hotfixes that were installed as part of a combination installation, however, unless you reinstall Windows 2000.

If you install multiple hotfixes that each replace the same files, and you want to return your computer to its original state, you must remove the most recently installed hotfix first, the next most recently installed hotfix second, and so on.

For example, assume that you installed HotfixA, then HotfixB, and then HotfixC, and they each replace the same file. To return your computer to the state it was in before you installed HotfixA, you must remove HotfixC first, followed by HotfixB, and then HotfixA. If you try to uninstall the hotfixes in the wrong order, a warning appears listing all hotfixes and programs installed since you installed the hotfix that you are trying to remove. If you proceed, these hotfixes and programs might not work correctly.

To remove a Windows 2000 hotfix

Click Start, point to Settings, and then click Control Panel.
Double-click Add/Remove Programs, click KB######, and then click Change/Remove.
Follow the instructions that appear on your screen.