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.
Wednesday, December 5, 2007
Tuesday, December 4, 2007
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.
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.
installation and procedure (Windows Vista)
Notes
If you are using a fingerprint reader or other biometric device to log on to your computer, make sure you write down your password before upgrading. You must log on by typing your user name and password the first time that you use Windows after upgrading.
For detailed information about upgrading from language versions of Windows XP to Windows Vista, go to You cannot upgrade certain language versions of Windows XP to Windows Vista online.
1. Insert the Windows installation disc into your computer's DVD or CD drive. You must start Windows installation while running your existing version of Windows.
2. On the Install Windows page, click Install now.
Install Windows page
3. On the Get important updates for installation page, we recommend getting the latest updates to help ensure a successful installation and to help protect your computer against security threats. You will need an Internet connection to get installation updates.
4. On the Type your product key for activation page, we strongly recommend that you type your 25-character product key to help avoid problems during activation.
5. On the Please read the license terms page, if you accept the license terms, click I accept the license terms.
6. On the Which type of installation do you want? page, click Upgrade to begin the upgrade. You might see a compatibility report.
Which type of installation do you want? page
7. Follow the instructions.
Remember to reinstall antivirus software
After installing Windows, don't forget to enable existing, or install new, antivirus software.
To install Windows by performing a clean installation
You can use the following procedure when performing a clean installation of a 32-bit or 64-bit version of Windows Vista.
When you perform a clean installation, your existing version of Windows, including all of your files, settings, and programs, is automatically replaced. You can back up your files and settings, but you must manually reinstall your programs and restore backed-up files when the installation is done. For information about how to restore your files after a clean installation, go to How to restore your personal files after you perform a custom installation online.
Perform a clean installation if your computer has no operating system installed, or you want to delete your current operating system and replace it with Windows Vista, or you want to partition your hard disk and install Windows Vista on a specific partition.
Before you install Windows, check your hardware compatibility. Go to the Windows Vista Upgrade Advisor on the Microsoft website. Alternatively, you can run the Windows Vista Upgrade Advisor during installation by clicking Check compatibility online on the Install Windows page. If you start the installation from the installation disc, this link to the Windows Vista Upgrade Advisor does not appear on the Install Windows page.
NoteYou cannot install an upgrade copy of Windows Vista on a partition unless a copy of Windows 2000 or Windows XP is already installed on that partition. Depending on which version if Windows you are upgrading to and from, you might have to perform a clean installation.
1. Turn on your computer, insert the Windows installation disc into the computer's DVD or CD drive, and then do one of the following:
• If your computer already has an operating system installed, and if you do not want to create, extend, delete, or format partitions, go to step 2.
• If your computer does not have an operating system installed or if you want to create, extend, delete, or format partitions, you need to restart your computer with the installation disc inserted in your CD or DVD drive. This will cause your computer to start (or "boot") from the installation CD or DVD. If you are asked to press a key to boot from DVD or CD, press any key. If the Install Windows page appears, go to step 2.
If the Install Windows page does not appear and you're not asked to press a key to start from DVD or CD, you might have to specify that your computer use its DVD or CD drive as the startup device. This means that you need to set the DVD or CD drive to be the first startup device in the basic input/output system (BIOS). To learn how to do this, see Start Windows from a CD or DVD. After you select your DVD or CD drive as the startup device, restart your computer, and then start Windows from the installation DVD or CD as previously described.
2. On the Install Windows page, follow any instructions that are displayed, and then click Install now.
3. On the Get important updates for installation page, we recommend getting the latest updates to help ensure a successful installation and to help protect your computer against security threats. You will need an Internet connection to get installation updates.
4. On the Type your product key for activation page, we strongly recommend that you type your 25-character product key to help avoid problems during activation.
NoteIf you have an upgrade copy of a 32-bit version of Windows Vista, you will see a message telling you to restart your computer and start Windows installation from within your existing operating system.
5. On the Please read the license terms page, if you accept the license terms, click I accept the license terms.
6. On the Which type of installation do you want? page, click Custom.
NoteAfter you click Custom, if you have an upgrade copy of a 64-bit version of Windows Vista and do not have a version of Windows that can be upgraded, the installation cannot continue. You will need to install a copy of Windows 2000 or Windows XP to proceed with this installation method.
7. On the Where do you want to install Windows? page, select where you want to install Windows.
• If you don't partition your hard disk, click Next. The installation will start automatically. You might see a compatibility report that lists which programs and software drivers won't work after the installation. You can resolve any issues after the installation is complete.
• If you have an existing partition and want to have more than one operating system on the same computer, you can install Windows on a specific partition. (This is called a dual-boot or multiboot configuration.) If you do this, be sure to install Windows on a different partition from the partition where your current version of Windows is installed. To install Windows on an existing partition, select the partition you want to use, and then click Next to begin the installation. You might see a compatibility report.
• If you want to create, extend, delete, or format a partition, you must start Windows from the installation DVD or CD. If you did not begin the installation process this way, follow the instructions for starting Windows from the installation DVD or CD that appear in the first step of this procedure, and then follow the instructions on each screen. On the Where do you want to install Windows? page, click Drive options (advanced), click the option you want, and then follow the instructions. Click Next to begin the installation. You might see a compatibility report.
8. Follow the instructions.
NoteBe sure to enable existing, or install new, antivirus software after the installation is complete.
To reinstall Windows Vista
If you want to reinstall Windows Vista by performing a clean installation—possibly to restore the default Windows settings—here's how to do it. (If you're having a problem with Windows, first see What to do if Windows won't start correctly, which explains how to use the Windows installation disc to fix problems without completely reinstalling Windows.)
Back up your files before you begin reinstalling Windows, even if you're reinstalling Windows on a hard disk partition. A clean installation replaces the current version of Windows and all personal files.
1. Turn on your computer and insert the Windows Vista DVD or CD.
2. On the Install Windows page, follow any instructions that might appear, and then click Install now.
3. On the Get important updates for installation page, we recommend getting the latest updates to help ensure a successful installation and to help protect your computer against security threats. You will need an Internet connection to get installation updates.
4. On the Type your product key for activation page, we strongly recommend that you type your 25-character product key to help avoid problems during activation.
5. On the Please read the license terms page, if you accept the license terms, click I accept the license terms.
6. Follow the instructions on each page. On the Which type of installation do you want? page, click Custom.
7. On the Where do you want to install Windows? page, select the partition where you want to install Windows.
8. Click Next to begin the installation. You might see a compatibility report.
9. Follow the instructions.
Note
Be sure to enable existing, or install new, antivirus software after the installation is complete.
If you are using a fingerprint reader or other biometric device to log on to your computer, make sure you write down your password before upgrading. You must log on by typing your user name and password the first time that you use Windows after upgrading.
For detailed information about upgrading from language versions of Windows XP to Windows Vista, go to You cannot upgrade certain language versions of Windows XP to Windows Vista online.
1. Insert the Windows installation disc into your computer's DVD or CD drive. You must start Windows installation while running your existing version of Windows.
2. On the Install Windows page, click Install now.
Install Windows page
3. On the Get important updates for installation page, we recommend getting the latest updates to help ensure a successful installation and to help protect your computer against security threats. You will need an Internet connection to get installation updates.
4. On the Type your product key for activation page, we strongly recommend that you type your 25-character product key to help avoid problems during activation.
5. On the Please read the license terms page, if you accept the license terms, click I accept the license terms.
6. On the Which type of installation do you want? page, click Upgrade to begin the upgrade. You might see a compatibility report.
Which type of installation do you want? page
7. Follow the instructions.
Remember to reinstall antivirus software
After installing Windows, don't forget to enable existing, or install new, antivirus software.
To install Windows by performing a clean installation
You can use the following procedure when performing a clean installation of a 32-bit or 64-bit version of Windows Vista.
When you perform a clean installation, your existing version of Windows, including all of your files, settings, and programs, is automatically replaced. You can back up your files and settings, but you must manually reinstall your programs and restore backed-up files when the installation is done. For information about how to restore your files after a clean installation, go to How to restore your personal files after you perform a custom installation online.
Perform a clean installation if your computer has no operating system installed, or you want to delete your current operating system and replace it with Windows Vista, or you want to partition your hard disk and install Windows Vista on a specific partition.
Before you install Windows, check your hardware compatibility. Go to the Windows Vista Upgrade Advisor on the Microsoft website. Alternatively, you can run the Windows Vista Upgrade Advisor during installation by clicking Check compatibility online on the Install Windows page. If you start the installation from the installation disc, this link to the Windows Vista Upgrade Advisor does not appear on the Install Windows page.
NoteYou cannot install an upgrade copy of Windows Vista on a partition unless a copy of Windows 2000 or Windows XP is already installed on that partition. Depending on which version if Windows you are upgrading to and from, you might have to perform a clean installation.
1. Turn on your computer, insert the Windows installation disc into the computer's DVD or CD drive, and then do one of the following:
• If your computer already has an operating system installed, and if you do not want to create, extend, delete, or format partitions, go to step 2.
• If your computer does not have an operating system installed or if you want to create, extend, delete, or format partitions, you need to restart your computer with the installation disc inserted in your CD or DVD drive. This will cause your computer to start (or "boot") from the installation CD or DVD. If you are asked to press a key to boot from DVD or CD, press any key. If the Install Windows page appears, go to step 2.
If the Install Windows page does not appear and you're not asked to press a key to start from DVD or CD, you might have to specify that your computer use its DVD or CD drive as the startup device. This means that you need to set the DVD or CD drive to be the first startup device in the basic input/output system (BIOS). To learn how to do this, see Start Windows from a CD or DVD. After you select your DVD or CD drive as the startup device, restart your computer, and then start Windows from the installation DVD or CD as previously described.
2. On the Install Windows page, follow any instructions that are displayed, and then click Install now.
3. On the Get important updates for installation page, we recommend getting the latest updates to help ensure a successful installation and to help protect your computer against security threats. You will need an Internet connection to get installation updates.
4. On the Type your product key for activation page, we strongly recommend that you type your 25-character product key to help avoid problems during activation.
NoteIf you have an upgrade copy of a 32-bit version of Windows Vista, you will see a message telling you to restart your computer and start Windows installation from within your existing operating system.
5. On the Please read the license terms page, if you accept the license terms, click I accept the license terms.
6. On the Which type of installation do you want? page, click Custom.
NoteAfter you click Custom, if you have an upgrade copy of a 64-bit version of Windows Vista and do not have a version of Windows that can be upgraded, the installation cannot continue. You will need to install a copy of Windows 2000 or Windows XP to proceed with this installation method.
7. On the Where do you want to install Windows? page, select where you want to install Windows.
• If you don't partition your hard disk, click Next. The installation will start automatically. You might see a compatibility report that lists which programs and software drivers won't work after the installation. You can resolve any issues after the installation is complete.
• If you have an existing partition and want to have more than one operating system on the same computer, you can install Windows on a specific partition. (This is called a dual-boot or multiboot configuration.) If you do this, be sure to install Windows on a different partition from the partition where your current version of Windows is installed. To install Windows on an existing partition, select the partition you want to use, and then click Next to begin the installation. You might see a compatibility report.
• If you want to create, extend, delete, or format a partition, you must start Windows from the installation DVD or CD. If you did not begin the installation process this way, follow the instructions for starting Windows from the installation DVD or CD that appear in the first step of this procedure, and then follow the instructions on each screen. On the Where do you want to install Windows? page, click Drive options (advanced), click the option you want, and then follow the instructions. Click Next to begin the installation. You might see a compatibility report.
8. Follow the instructions.
NoteBe sure to enable existing, or install new, antivirus software after the installation is complete.
To reinstall Windows Vista
If you want to reinstall Windows Vista by performing a clean installation—possibly to restore the default Windows settings—here's how to do it. (If you're having a problem with Windows, first see What to do if Windows won't start correctly, which explains how to use the Windows installation disc to fix problems without completely reinstalling Windows.)
Back up your files before you begin reinstalling Windows, even if you're reinstalling Windows on a hard disk partition. A clean installation replaces the current version of Windows and all personal files.
1. Turn on your computer and insert the Windows Vista DVD or CD.
2. On the Install Windows page, follow any instructions that might appear, and then click Install now.
3. On the Get important updates for installation page, we recommend getting the latest updates to help ensure a successful installation and to help protect your computer against security threats. You will need an Internet connection to get installation updates.
4. On the Type your product key for activation page, we strongly recommend that you type your 25-character product key to help avoid problems during activation.
5. On the Please read the license terms page, if you accept the license terms, click I accept the license terms.
6. Follow the instructions on each page. On the Which type of installation do you want? page, click Custom.
7. On the Where do you want to install Windows? page, select the partition where you want to install Windows.
8. Click Next to begin the installation. You might see a compatibility report.
9. Follow the instructions.
Note
Be sure to enable existing, or install new, antivirus software after the installation is complete.
Windows XP installation and procedure
Installation process
Part 1: Begin the installation
1.
Insert the Windows XP CD into your computer and restart your computer.
2.
If prompted to start from the CD, press SPACEBAR. If you miss the prompt (it only appears for a few seconds), restart your computer to try again.
3.
Windows XP Setup begins. During this portion of setup, your mouse will not work, so you must use the keyboard. On the Welcome to Setup page, press ENTER.
4.
On the Windows XP Licensing Agreement page, read the licensing agreement. Press the PAGE DOWN key to scroll to the bottom of the agreement. Then press F8.
5.
This page enables you to select the hard disk drive on which Windows XP will be installed. Once you complete this step, all data on your hard disk drive will be removed and cannot be recovered. It is extremely important that you have a recent backup copy of your files before continuing. When you have a backup copy, press D, and then press L when prompted. This deletes your existing data.
6.
Press ENTER to select Unpartitioned space, which appears by default.
7.
Press ENTER again to select Format the partition using the NTFS file system, which appears by default.
8.
Windows XP erases your hard disk drive using a process called formatting and then copies the setup files. You can leave your computer and return in 20 to 30 minutes.
Part 2: Continue the installation
9.
Windows XP restarts and then continues with the installation process. From this point forward, you can use your mouse. Eventually, the Regional and Language Options page appears. Click Next to accept the default settings. If you are multilingual or prefer a language other than English, you can change language settings after setup is complete.
10.
On the Personalize Your Software page, type your name and your organization name. Some programs use this information to automatically fill in your name when required. Then, click Next.
11.
On the Your Product Key page, type your product key as it appears on your Windows XP CD case. The product key is unique for every Windows XP installation. Then, click Next.
12.
On the Computer Name and Administrator Password page, in the Computer name box, type a name that uniquely identifies your computer in your house, such as FAMILYROOM or TOMS. You cannot use spaces or punctuation. If you connect your computer to a network, you will use this computer name to find shared files and printers. Type a strong password that you can remember in the Administrator password box, and then retype it in the Confirm password box. Write the password down and store it in a secure place. Click Next.
13.
On the Date and Time Settings page, set your computer’s clock. Then, click the Time Zone down arrow, and select your time zone. Click Next.
14.
Windows XP will spend about a minute configuring your computer. On the Networking Settings page, click Next.
15.
On the Workgroup or Computer Domain page, click Next.
Part 3: Complete the installation
16.
Windows XP will spend 20 or 30 minutes configuring your computer and will automatically restart when finished. When the Display Settings dialog appears, click OK.
17.
When the Monitor Settings dialog box appears, click OK.
18.
The final stage of setup begins. On the Welcome to Microsoft Windows page, click Next.
19.
On the Help protect your PC page, click Help protect my PC by turning on Automatic Updates now. Then, click Next.
20.
Windows XP will then check if you are connected to the Internet:
• If you are connected to the Internet, select the choice that describes your network connection on the Will this computer connect to the Internet directly, or through a network? page. If you’re not sure, accept the default selection, and click Next.
• If you use dial-up Internet access, or if Windows XP cannot connect to the Internet, you can connect to the Internet after setup is complete. On the How will this computer connect to the Internet? page, click Skip.
21.
Windows XP Setup displays the Ready to activate Windows? page. If you are connected to the Internet, click Yes, and then click Next. If you are not yet connected to the Internet, click No, click Next, and then skip to step 24. After setup is complete, Windows XP will automatically remind you to activate and register your copy of Windows XP.
22.
On the Ready to register with Microsoft? page, click Yes, and then click Next.
23.
On the Collecting Registration Information page, complete the form. Then, click Next.
24.
On the Who will use this computer? page, type the name of each person who will use the computer. You can use first names only, nicknames, or full names. Then click Next. To add users after setup is complete or to specify a password to keep your account private, read Create and customize user accounts.
25.
On the Thank you! page, click Finish.
Part 1: Begin the installation
1.
Insert the Windows XP CD into your computer and restart your computer.
2.
If prompted to start from the CD, press SPACEBAR. If you miss the prompt (it only appears for a few seconds), restart your computer to try again.
3.
Windows XP Setup begins. During this portion of setup, your mouse will not work, so you must use the keyboard. On the Welcome to Setup page, press ENTER.
4.
On the Windows XP Licensing Agreement page, read the licensing agreement. Press the PAGE DOWN key to scroll to the bottom of the agreement. Then press F8.
5.
This page enables you to select the hard disk drive on which Windows XP will be installed. Once you complete this step, all data on your hard disk drive will be removed and cannot be recovered. It is extremely important that you have a recent backup copy of your files before continuing. When you have a backup copy, press D, and then press L when prompted. This deletes your existing data.
6.
Press ENTER to select Unpartitioned space, which appears by default.
7.
Press ENTER again to select Format the partition using the NTFS file system, which appears by default.
8.
Windows XP erases your hard disk drive using a process called formatting and then copies the setup files. You can leave your computer and return in 20 to 30 minutes.
Part 2: Continue the installation
9.
Windows XP restarts and then continues with the installation process. From this point forward, you can use your mouse. Eventually, the Regional and Language Options page appears. Click Next to accept the default settings. If you are multilingual or prefer a language other than English, you can change language settings after setup is complete.
10.
On the Personalize Your Software page, type your name and your organization name. Some programs use this information to automatically fill in your name when required. Then, click Next.
11.
On the Your Product Key page, type your product key as it appears on your Windows XP CD case. The product key is unique for every Windows XP installation. Then, click Next.
12.
On the Computer Name and Administrator Password page, in the Computer name box, type a name that uniquely identifies your computer in your house, such as FAMILYROOM or TOMS. You cannot use spaces or punctuation. If you connect your computer to a network, you will use this computer name to find shared files and printers. Type a strong password that you can remember in the Administrator password box, and then retype it in the Confirm password box. Write the password down and store it in a secure place. Click Next.
13.
On the Date and Time Settings page, set your computer’s clock. Then, click the Time Zone down arrow, and select your time zone. Click Next.
14.
Windows XP will spend about a minute configuring your computer. On the Networking Settings page, click Next.
15.
On the Workgroup or Computer Domain page, click Next.
Part 3: Complete the installation
16.
Windows XP will spend 20 or 30 minutes configuring your computer and will automatically restart when finished. When the Display Settings dialog appears, click OK.
17.
When the Monitor Settings dialog box appears, click OK.
18.
The final stage of setup begins. On the Welcome to Microsoft Windows page, click Next.
19.
On the Help protect your PC page, click Help protect my PC by turning on Automatic Updates now. Then, click Next.
20.
Windows XP will then check if you are connected to the Internet:
• If you are connected to the Internet, select the choice that describes your network connection on the Will this computer connect to the Internet directly, or through a network? page. If you’re not sure, accept the default selection, and click Next.
• If you use dial-up Internet access, or if Windows XP cannot connect to the Internet, you can connect to the Internet after setup is complete. On the How will this computer connect to the Internet? page, click Skip.
21.
Windows XP Setup displays the Ready to activate Windows? page. If you are connected to the Internet, click Yes, and then click Next. If you are not yet connected to the Internet, click No, click Next, and then skip to step 24. After setup is complete, Windows XP will automatically remind you to activate and register your copy of Windows XP.
22.
On the Ready to register with Microsoft? page, click Yes, and then click Next.
23.
On the Collecting Registration Information page, complete the form. Then, click Next.
24.
On the Who will use this computer? page, type the name of each person who will use the computer. You can use first names only, nicknames, or full names. Then click Next. To add users after setup is complete or to specify a password to keep your account private, read Create and customize user accounts.
25.
On the Thank you! page, click Finish.
Tuesday, November 20, 2007
Windows Vista
Windows Vista (IPA: /ˈvɪs.tə/) is a line of graphical operating systems used on personal computers, including home and business desktops, laptops, Tablet PCs, and media centers. Prior to its announcement on July 22, 2005, Windows Vista was known by its codename "Longhorn".[1] Development was completed on November 8, 2006; over the following three months it was released in stages to computer hardware and software manufacturers, business customers, and retail channels. On January 30, 2007, it was released worldwide to the general public,[2] and was made available for purchase and downloading from Microsoft's web site.[3] The release of Windows Vista comes more than five years after the introduction of its predecessor, Windows XP, making it the longest time span between two releases of Microsoft Windows.
Windows Vista contains hundreds of new and reworked features; some of the most significant include an updated graphical user interface and visual style dubbed Windows Aero, improved searching features, new multimedia creation tools such as Windows DVD Maker, and completely redesigned networking, audio, print, and display sub-systems. Vista also aims to increase the level of communication between machines on a home network using peer-to-peer technology, making it easier to share files and digital media between computers and devices. For developers, Vista includes version 3.0 of the .NET Framework, which aims to make it significantly easier for developers to write applications than with the traditional Windows API.
Microsoft's primary stated objective with Windows Vista, however, has been to improve the state of security in the Windows operating system.[4] One common criticism of Windows XP and its predecessors has been their commonly exploited security vulnerabilities and overall susceptibility to malware, viruses and buffer overflows. In light of this, Microsoft chairman Bill Gates announced in early 2002 a company-wide "Trustworthy Computing initiative" which aims to incorporate security work into every aspect of software development at the company. Microsoft stated that it prioritized improving the security of Windows XP and Windows Server 2003 above finishing Windows Vista, thus delaying its completion.[5]
Windows Vista is the target of a number of negative assessments by various groups. Criticisms of Windows Vista include protracted development time, more restrictive licensing terms, the inclusion of a number of new Digital Rights Management technologies aimed at restricting the copying of protected digital media, lack of device drivers for some hardware, and the usability of other new features such as User Account Control.
Unix
Unix (officially trademarked as UNIX®, sometimes also written as Unix or Unix® with small caps) is a computer operating system originally developed in 1969 by a group of AT&T employees at Bell Labs including Ken Thompson, Dennis Ritchie and Douglas McIlroy. Today's Unix systems are split into various branches, developed over time by AT&T as well as various commercial vendors and non-profit organizations.
As of 2007, the owner of the trademark UNIX® is The Open Group, an industry standards consortium. Only systems fully compliant with and certified to the Single UNIX Specification qualify as "UNIX®" (others are called "Unix system-like" or "Unix-like").
During the late 1970s and early 1980s, Unix's influence in academic circles led to large-scale adoption of Unix (particularly of the BSD variant, originating from the University of California, Berkeley) by commercial startups, the most notable of which is Sun Microsystems. Today, in addition to certified Unix systems, Unix-like operating systems such as Linux and BSD are commonly encountered. Sometimes, "traditional Unix" may be used to describe a Unix or an operating system that has the characteristics of either Version 7 Unix or UNIX System V.
Linux
MS-DOS (short for Microsoft Disk Operating System) is an operating system commercialised by Microsoft. It was the most commonly used member of the DOS family of operating systems and was the dominant operating system for the PC compatible platform during the 1980s. It has gradually been replaced on consumer desktop computers by various generations of the Windows operating system.
MS-DOS was originally released in 1981 and had eight major versions released before Microsoft stopped development in 2000. It was the key product in Microsoft's growth from a programming languages company to a diverse software development firm, providing the company with essential revenue and marketing resources. It also provided the platform on which early versions of Windows ran.
Description Bosanski: Tux, maskota Linuxa
Deutsch: Tux, der Linux-Pinguin
English: Tux, the Linux penguin
Հայերեն: Տուքս պինգվինը՝ Լինուքսի հմայիլը
Français : Le manchot Tux, la mascotte de Linux
Português: O Pinguim Tux, mascote do Linux
Polski: Pingwin Tux - maskotka Linuksa
Română: Pinguinul Tux, mascota Linuxului
Source Based on original image by Larry Ewing, created using Sodipodi
Date
Author gg3po (kde-look.org source)
Permission
(Reusing this image) (c) Larry Ewing, Simon Budig und Anja Gerwinsk
Linux (pronunciation: IPA: /ˈlɪnʊks/, lin-uks) is a Unix-like computer operating system. Linux is one of the most prominent examples of free software and open source development; its underlying source code can be freely modified, used, and redistributed by anyone.[1]
The Linux kernel was first released to the public on 17 September 1991, for the Intel x86 PC architecture. The kernel was augmented with system utilities and libraries from the GNU project to create a usable operating system, which later led to an alternate term, GNU/Linux.[2] Linux is now packaged for different uses in Linux distributions, which contain the sometimes modified kernel along with a variety of other software packages tailored to different requirements.
Predominantly known for its use in servers, Linux is supported by corporations such as Dell, Hewlett-Packard, IBM, Novell, Oracle Corporation, Red Hat, and Sun Microsystems. It is used as an operating system for a wide variety of computer hardware, including desktop computers, supercomputers,[3] video game systems such as PlayStation 2, 3, several arcade games and embedded devices such as mobile phones and routers.
In 1992, Linus Torvalds explained that he pronounces Linux as /ˈlɪnʊks/,[4] though other variations are common.
MS-DOS was originally released in 1981 and had eight major versions released before Microsoft stopped development in 2000. It was the key product in Microsoft's growth from a programming languages company to a diverse software development firm, providing the company with essential revenue and marketing resources. It also provided the platform on which early versions of Windows ran.
Description Bosanski: Tux, maskota Linuxa
Deutsch: Tux, der Linux-Pinguin
English: Tux, the Linux penguin
Հայերեն: Տուքս պինգվինը՝ Լինուքսի հմայիլը
Français : Le manchot Tux, la mascotte de Linux
Português: O Pinguim Tux, mascote do Linux
Polski: Pingwin Tux - maskotka Linuksa
Română: Pinguinul Tux, mascota Linuxului
Source Based on original image by Larry Ewing, created using Sodipodi
Date
Author gg3po (kde-look.org source)
Permission
(Reusing this image) (c) Larry Ewing, Simon Budig und Anja Gerwinsk
Linux (pronunciation: IPA: /ˈlɪnʊks/, lin-uks) is a Unix-like computer operating system. Linux is one of the most prominent examples of free software and open source development; its underlying source code can be freely modified, used, and redistributed by anyone.[1]
The Linux kernel was first released to the public on 17 September 1991, for the Intel x86 PC architecture. The kernel was augmented with system utilities and libraries from the GNU project to create a usable operating system, which later led to an alternate term, GNU/Linux.[2] Linux is now packaged for different uses in Linux distributions, which contain the sometimes modified kernel along with a variety of other software packages tailored to different requirements.
Predominantly known for its use in servers, Linux is supported by corporations such as Dell, Hewlett-Packard, IBM, Novell, Oracle Corporation, Red Hat, and Sun Microsystems. It is used as an operating system for a wide variety of computer hardware, including desktop computers, supercomputers,[3] video game systems such as PlayStation 2, 3, several arcade games and embedded devices such as mobile phones and routers.
In 1992, Linus Torvalds explained that he pronounces Linux as /ˈlɪnʊks/,[4] though other variations are common.
MS-DOS
An example of MS-DOS's command-line interface, this one showing that the current directory is the root of drive C.
Company/
developer: Microsoft Corporation
OS family: DOS
Source model: Closed source
Latest stable release: 8.0 / September 14, 2000
Marketing target: ?
Available language(s): C, Pascal, QBasic, etc.
Supported platforms: x86
Kernel type: Monolithic kernel
Default user interface: Command line interface, Text user interface
License: Proprietary
Working state: Discontinued
MS-DOS (short for Microsoft Disk Operating System) is an operating system commercialised by Microsoft. It was the most commonly used member of the DOS family of operating systems and was the dominant operating system for the PC compatible platform during the 1980s. It has gradually been replaced on consumer desktop computers by various generations of the Windows operating system.
MS-DOS was originally released in 1981 and had eight major versions released before Microsoft stopped development in 2000. It was the key product in Microsoft's growth from a programming languages company to a diverse software development firm, providing the company with essential revenue and marketing resources. It also provided the platform on which early versions of Windows ran.
Windows XP
Windows XP is a line of operating systems developed by Microsoft for use on general-purpose computer systems, including home and business desktops, notebook computers, and media centers. The letters "XP" stand for eXPerience.[2] It was codenamed "Whistler", after Whistler, British Columbia, as many Microsoft employees skied at the Whistler-Blackcomb ski resort during its development. Windows XP is the successor to both Windows 2000 Professional and Windows Me, and is the first consumer-oriented operating system produced by Microsoft to be built on the Windows NT kernel and architecture. Windows XP was first released on October 25, 2001, and over 400 million copies were in use in January 2006, according to an estimate in that month by an IDC analyst.[3] It is succeeded by Windows Vista, which was released to volume license customers on November 8, 2006, and worldwide to the general public on January 30, 2007.
The most common editions of the operating system are Windows XP Home Edition, which is targeted at home users, and Windows XP Professional, which has additional features such as support for Windows Server domains and two physical processors, and is targeted at power users and business clients. Windows XP Media Center Edition has additional multimedia features enhancing the ability to record and watch TV shows, view DVD movies, and listen to music. Windows XP Tablet PC Edition is designed to run the ink-aware Tablet PC platform. Two separate 64-bit versions of Windows XP were also released, Windows XP 64-bit Edition for IA-64 (Itanium) processors and Windows XP Professional x64 Edition for x86-64.
Windows XP is known for its improved stability and efficiency over the 9x versions of Microsoft Windows. It presents a significantly redesigned graphical user interface, a change Microsoft promoted as more user-friendly than previous versions of Windows. New software management capabilities were introduced to avoid the "DLL hell" that plagued older consumer-oriented 9x versions of Windows. It is also the first version of Windows to use product activation to combat software piracy, a restriction that did not sit well with some users and privacy advocates. Windows XP has also been criticized by some users for security vulnerabilities, tight integration of applications such as Internet Explorer and Windows Media Player, and for aspects of its default user interface.
Windows XP had been in development since early 1999, when Microsoft started working on Windows Neptune, an operating system intended to be the "Home Edition" equivalent to Windows 2000 Professional. It was eventually merged into the Whistler project, which later became Windows XP.
Mac OS
Mac OS is the trademarked name for a series of graphical user interface-based operating systems developed by Apple Inc. (formerly Apple Computer, Inc.) for their Macintosh line of computer systems. The Macintosh user experience is credited with popularizing the graphical user interface. The original form of what Apple would later name the "Mac OS" was the integral and unnamed system software first introduced in 1984 with the original Macintosh, usually referred to simply as the System software.
Apple deliberately downplayed the existence of the operating system in the early years of the Macintosh to help make the machine appear more user-friendly and to distance it from other operating systems such as MS-DOS, which were portrayed as arcane and technically challenging. Much of this early system software was held in ROM, with updates typically provided free of charge by Apple dealers on floppy disk. As increasing disk storage capacity and performance gradually eliminated the need for fixing much of an advanced GUI operating system in ROM, Apple explored cloning while positioning major operating system upgrades as separate revenue-generating products, first with System 7 and System 7.5, then with Mac OS 7.6 in 1997.
Earlier versions of the Mac OS were compatible only with Motorola 68000-based Macintoshes. As Apple introduced computers with PowerPC hardware, the OS was upgraded to support this architecture as well. Mac OS X, which has superseded the "Classic" Mac OS, is compatible with both PowerPC and Intel processors.
Monday, November 19, 2007
64-bit operating system
Description Logo for the Microsoft Windows line of operating systems. Introduced in late 2006 as a replacement for a prior logo, available here.
Source Microsoft PressPass
Article [[{{{Article}}}]]
Portion used The entire work illustrated is covered by this rationale
Low resolution? Low Resolution of 300*213 pixels
Purpose of use The Microsoft Windows logo - used in the main article and in other articles about the software itself
Replaceable? Not replaceable.
Other information This image is only being used in Wikipedia articles for informational and educational purposes.
The image's inclusion here will not result in financial loss to the creator of the original drawing or Microsoft.
A logo is very safe territory
Wikipedia is a non-profit organisation, downstream providers who are not non-profit will need to consider whether they will take the risk in using this image
[edit] 64-bit operating systems
The current Windows logoWindows NT included support for several different platforms before the x86-based personal computer became dominant in the professional world. Versions of NT from 3.1 to 4.0 supported DEC Alpha and MIPS R4000, which were 64-bit processors, although the operating system treated them as 32-bit processors.
With the introduction of the Intel Itanium architecture, which is referred to as IA-64, Microsoft released new versions of Windows 2000 to support it. Itanium versions of Windows XP and Windows Server 2003 were released at the same time as their mainstream x86 (32-bit) counterparts. On April 25, 2005, Microsoft released Windows XP Professional x64 Edition and x64 versions of Windows Server 2003 to support the AMD64/Intel64 (or x64 in Microsoft terminology) architecture. Microsoft dropped support for the Itanium version of Windows XP in 2005. Windows Vista is the first end-user version of Windows that Microsoft has released simultaneously in 32-bit and x64 editions. Windows Vista does not support the Itanium architecture. The modern 64-bit Windows family comprises AMD64/Intel64 versions of Windows Vista, and Windows Server 2003, in both Itanium and x64 editions
Hybrid 16/32-bit operating system
Description Logo for Microsoft Windows, circa 2000. Introduced in late 1999 as part of the Windows 2000 branding.
The Windows logo that was used from 2001 to November 2006.
Source Microsoft documentation on Windows 2000.
Article [[{{{Article}}}]]
Portion used The entire work illustrated is covered by this rationale
Low resolution? Low Resolution of 262*192 pixels
Purpose of use The Windows 2000 logo - used in articles describing Microsoft Windows and its history at around the time of Windows 2000's release
Replaceable? Not replaceable.
Other information This image is only being used in Wikipedia articles for informational and educational purposes.
The image's inclusion here will not result in financial loss to the creator of the original drawing or Microsoft.
A logo is very safe territory
Wikipedia is a non-profit organisation, downstream providers who are not non-profit will need to consider whether they will take the risk in using this image
This family of Windows systems was fashioned and marketed for higher reliability business use, and was unencumbered by any Microsoft DOS patrimony.[citation needed] The first release was Windows NT 3.1 (1993, numbered "3.1" to match the Windows version and to one-up OS/2 2.1[citation needed], IBM's flagship OS co-developed by Microsoft and was Windows NT's main competitor at the time), which was followed by NT 3.5 (1994), NT 3.51 (1995), and NT 4.0 (1996); NT 4.0 was the first in this line to implement the Windows 95 user interface. Microsoft then moved to combine their consumer and business operating systems. Their first attempt, Windows 2000, failed to meet their goals,[citation needed] and was released as a business system. The home consumer edition of Windows 2000, codenamed "Windows Neptune," ceased development and Microsoft released Windows Me in its place.[citation needed] Eventually "Neptune" was merged into their new project, Whistler, which later became Windows XP, which came in both home and professional versions. Then, Windows Server 2003 brought Windows Server up to date with Windows XP. Since then, Windows Vista was released and Windows Server 2008 will bring Windows Server up to date with Windows Vista. Windows CE, Microsoft's offering in the mobile and embedded markets, is also a true 32-bit operating system that offers various services for all sub-operating workstations.
Microsoft_Windows.svg
Description Logo for Microsoft Windows from 1992 to 1999.
Source This vector image was created by converting the Encapsulated PostScript file available at brandsoftheworld.com - to see it there, click here. If it is not free content, remember to only render it at web resolution to comply with our fair-use policy.
Article [[{{{Article}}}]]
Portion used The entire work illustrated is covered by this rationale
Low resolution? SVG
Purpose of use The Classic Microsoft Windows logo - used in the main article and in other articles about the software itself
Replaceable? Not replaceable.
Other information This image is only being used in Wikipedia articles for informational and educational purposes.
The image's inclusion here will not result in financial loss to the creator of the original drawing or Microsoft.
A logo is very safe territory
Wikipedia is a non-profit organisation, downstream providers who are not non-profit will need to consider whether they will take the risk in using this image
Windows/386 introduced a 32-bit protected mode kernel and virtual machine monitor. For the duration of a Windows session, it created one or more virtual 8086 environments and provided device virtualization for the video card, keyboard, mouse, timer and interrupt controller inside each of them. The user-visible consequence was that it became possible to preemptively multitask multiple MS-DOS environments in separate Windows (graphical applications required switching the window to full screen mode). Windows applications were still multi-tasked cooperatively inside one of such real-mode environments.
Windows 3.0 (1990) and Windows 3.1 (1992) improved the design, mostly because of virtual memory and loadable virtual device drivers (VxDs) which allowed them to share arbitrary devices between multitasked DOS windows.[citation needed] Because of this, Windows applications could now run in 16-bit protected mode (when Windows was running in Standard or 386 Enhanced Mode), which gave them access to several megabytes of memory and removed the obligation to participate in the software virtual memory scheme. They still ran inside the same address space, where the segmented memory provided a degree of protection, and multi-tasked cooperatively. For Windows 3.0, Microsoft also rewrote critical operations from C into assembly, making this release faster and less memory-hungry than its predecessors.
Windows
Description Logo for the Microsoft Windows line of operating systems. Introduced in late 2006 as a replacement for a prior logo, available here.
Source Microsoft PressPass
Article [[{{{Article}}}]]
Portion used The entire work illustrated is covered by this rationale
Low resolution? Low Resolution of 288*76 pixels
Purpose of use The Microsoft Windows logo - used in the main article and in other articles about the software itself
Replaceable? Not replaceable.
Other information This image is only being used in Wikipedia articles for informational and educational purposes.
The image's inclusion here will not result in financial loss to the creator of the original drawing or Microsoft.
A logo is very safe territory
Wikipedia is a non-profit organisation, downstream providers who are not non-profit will need to consider whether they will take the risk in using this image
Screenshot of Windows Vista Ultimate, the latest version of Microsoft Windows (Build 6000).
Company/developer: Microsoft Corporation
OS family: MS-DOS/9x-based, Windows CE, Windows NT
Source model: Closed source
Stable release: Windows Vista
NT 6.0 (November 8, 2006) [+/-]
Preview release: Windows Server 2008
Release Candidate 0
NT 6.0.6001.16648 (September 2007) [+/-]
Microsoft Windows is the name of several families of software operating systems by Microsoft. Microsoft first introduced an operating environment named Windows in November 1985 as an add-on to MS-DOS in response to the growing interest in graphical user interfaces (GUIs).[1] Microsoft Windows eventually came to dominate the world's personal computer market, overtaking Mac OS, which had been introduced previously. At the 2004 IDC Directions conference, IDC Vice President Avneesh Saxena stated that Windows had approximately 90% of the client operating system market.[2] The current client version of Windows is Windows Vista. The current server version of Windows is Windows Server 2003. The successor to Windows Server 2003, Windows Server 2008 is currently being beta tested.
OS/2 WRAP
OS/2 version 3.0, released in 1994, was labelled as "OS/2 Warp" to highlight the new performance benefits, and generally to freshen the product image. "Warp" had originally been the internal IBM name for the release: IBM claimed that it had used Star Trek terms as internal names for past OS/2 releases, and that this one seemed appropriate for external use as well.
At the launch of OS/2 Warp in 1994, Patrick Stewart was to be the Master of Ceremonies; however Kate Mulgrew of the then-upcoming series Star Trek: Voyager was substituted at the last minute.
OS/2 Warp offered a host of benefits over OS/2 2.1, notably broader hardware support, greater multimedia capabilities, Internet-compatible networking, and it included a basic office application suite known as IBM Works. It was released in two versions: the less-expensive "Red Spine" and the more-expensive "Blue Spine" (named for the color of their boxes). "Red Spine" was designed to support Microsoft Windows applications by finding and using Windows already installed on the computer's hard drive. "Blue Spine" included Windows support in its own installation, and so could support Windows applications without a Windows installation. As most computers were sold with Microsoft Windows pre-installed, "Red Spine" was the far more popular product. OS/2 Warp Connect, which had full network support built-in, followed in mid-1995, again in "Red Spine" and "Blue Spine" versions.[5]
Mozilla 1.7.13 for OS/2 Warp 4In 1996, Warp 4 added Java and speech recognition software. IBM also released server editions of Warp 3 and Warp 4 which bundled IBM's LAN Server product directly into the operating system installation. The UK-distributed free demo CD-ROM of OS/2 Warp essentially contained the entire OS and was easily, even accidentally, cracked, meaning that even people who liked it didn't have to buy it. This was seen as a backdoor tactic to increase the number of OS/2 users, in the belief that this would increase sales and demand for third-party applications, and thus strengthen OS/2's desktop numbers.[citation needed] This suggestion was bolstered by the fact that this demo version had replaced another which was not so easily cracked, but which had been released with trial versions of various applications.[citation needed] In 2000 the July edition of Australian Personal Computer magazine bundled software CD-ROMs, included a full version of Warp 4 that required no activation and was essentially a free release.
Warp 4 was the last widely distributed version of OS/2, and IBM soon announced the end of marketing the operating system to individual users.
IBM (OS/2)
Size of this preview: 497 × 599 pixels
Full resolution (600 × 723 pixels, file size: 181 KB, MIME type: image/png)
[edit] Summary
OS/2 version 2 box jacket. The purpose of this image's existence in Wikipedia is to illustrate an article that describes the product. In the version depicted, the product packaging says it:
Requires 4MB RAM
Intel 80386SX or higher CPU
either 1 CD-ROM or (in this box) Diskette media: 25 5.25-inch HD (1.2MB) diskettes
Box says it runs Windows 2.0/386 applications, DOS applications and OS/2 applications.
Can use HPFS- or FAT-formatted hard disks.
IBM grew concerned about the delays in development of OS/2 2.0 and the diversion of IBM funds earmarked for OS/2 development towards Windows[citation needed]. Initially, the companies agreed that IBM would take over maintenance of OS/2 1.0 and development of OS/2 2.0, while Microsoft would continue development of OS/2 3.0. In the end, Microsoft decided to recast NT OS/2 3.0 as Windows NT, leaving all future OS/2 development to IBM. From a business perspective, it was logical to concentrate on a consumer line of operating systems based on DOS and Windows, and to prepare a new high-end system in such a way as to keep good compatibility with existing Windows applications. While waiting for this new high-end system to develop, Microsoft would still receive licensing money from Xenix and OS/2 sales. Windows NT's OS/2 heritage can be seen in its initial support for the HPFS filesystem, text mode OS/2 1.x applications, and OS/2 LAN Manager network support. Some early NT materials even included OS/2 copyright notices embedded in the software.[citation needed]
One example of NT OS/2 1.x support is in the WIN2K resource kit. OS/2 support also includes Presentation Manager support with the addition of the Windows NT Add-On Subsystem for Presentation Manager
Sunday, November 18, 2007
OS/2
A typical OS/2 Warp 4 desktop
Company/
developer: Microsoft, IBM
OS family: OS/2
Source model: Closed source
Latest stable release: 4.52 / December 2001
Marketing target: Professionals, servers
Kernel type: Hybrid kernel
License: Proprietary
Working state: Obsolescent
OS/2 is a computer operating system, initially created by Microsoft and IBM, then later developed by IBM exclusively. The name stands for "Operating System/2," because it was introduced as the preferred operating system for IBM's "Personal System/2 (PS/2)" line of second-generation Personal Computers. OS/2 is no longer marketed by IBM, and IBM standard support for OS/2 was discontinued on December 31, 2006.[1] Currently, Serenity Systems sells OS/2 under the brand name eComStation.
OS/2 was intended as a protected mode successor of MS-DOS and Microsoft Windows. Notably, basic system calls were modeled after MS-DOS calls; their names even started with "Dos" and it was possible to create "Family Mode" applications: text mode applications that could work on both systems.[2] Because of this heritage, OS/2 is like Windows in many ways, but it also shares similarities with Unix and Xenix.
OS/2 is also remembered for being the first major operating system to have its own advocacy group. Team OS/2 was a grassroots, ad-hoc organization of volunteers, who promoted and supported the operating system and applications designed for it.
Windows (September 2007)
16-bit operating environments
The box art of Windows 1.0, the first version that Microsoft released to the public.The early versions of Windows were often thought of as just graphical user interfaces, mostly because they ran on top of MS-DOS and used it for file system services.[citation needed] However even the earliest 16-bit Windows versions already assumed many typical operating system functions, notably having their own executable file format and providing their own device drivers (timer, graphics, printer, mouse, keyboard and sound) for applications. Unlike MS-DOS, Windows allowed users to execute multiple graphical applications at the same time, through cooperative multitasking. Finally, Windows implemented an elaborate, segment-based, software virtual memory scheme which allowed it to run applications larger than available memory: code segments and resources were swapped in and thrown away when memory became scarce, and data segments moved in memory when a given application had relinquished processor control, typically waiting for user input.[citation needed] 16-bit Windows versions include Windows 1.0 (1985), Windows 2.0 (1987) and its close relative Windows/286.
List of Windows OS (logos and description)
MS-DOS
From Wikipedia, the free encyclopedia
Jump to: navigation, search
MS-DOS
An example of MS-DOS's command-line interface, this one showing that the current directory is the root of drive C.
Company/
developer: Microsoft Corporation
OS family: DOS
Source model: Closed source
Latest stable release: 8.0 / September 14, 2000
Marketing target: ?
Available language(s): C, Pascal, QBasic, etc.
Supported platforms: x86
Kernel type: Monolithic kernel
Default user interface: Command line interface, Text user interface
License: Proprietary
Working state: Discontinued
MS-DOS (short for Microsoft Disk Operating System) is an operating system commercialised by Microsoft. It was the most commonly used member of the DOS family of operating systems and was the dominant operating system for the PC compatible platform during the 1980s. It has gradually been replaced on consumer desktop computers by various generations of the Windows operating system.
MS-DOS was originally released in 1981 and had eight major versions released before Microsoft stopped development in 2000. It was the key product in Microsoft's growth from a programming languages company to a diverse software development firm, providing the company with essential revenue and marketing resources. It also provided the platform on which early versions of Windows ran.
An example of MS-DOS's command-line interface, this one showing that the current directory is the root of drive C.
Company/
developer: Microsoft Corporation
OS family: DOS
Source model: Closed source
Latest stable release: 8.0 / September 14, 2000
Marketing target: ?
Available language(s): C, Pascal, QBasic, etc.
Supported platforms: x86
Kernel type: Monolithic kernel
Default user interface: Command line interface, Text user interface
License: Proprietary
Working state: Discontinued
Tuesday, November 13, 2007
Latest Slots
Most PCs from the leading vendors now include at least one PCI Express slot. The most common slot sizes are x1 and x16. The x1 slot is a general-purpose slot that can host devices such as NI PCIe M Series data acquisition and NI PCIe GPIB devices. Currently, server-class machines are required for x4 and x8 slots which are used by devices including the NI PCIe Camera Link image acquisition device. “Server” does not imply high price, though, as tower servers are available for prices comparable to desktop machines. For example, as of May 2005, the Dell SC420 server has one x1 and one x8 PCI Express slot in addition to three PCI slots starting at $299 (USD).
Figure 4. Most motherboards have a combination of PCI and PCI Express slots
It is important when choosing a computer to make sure that the PCI Express connectors are wired to the physical connection size. For instance, some vendors use motherboards with x8 connectors that are wired as x4. Devices in these slots will only operate at x4 data rates. In the case that you are up-plugging a PCI Express device, make sure that the computer you are using supports up-plugging at the maximum data rate supported by your device. The PCI Express specification only requires up-plugging to operate at the x1 data rate. This could result in a x4 device that is plugged into a x8 connector to operate at x1 data rates (250 MB/s).
Figure 4. Most motherboards have a combination of PCI and PCI Express slots
It is important when choosing a computer to make sure that the PCI Express connectors are wired to the physical connection size. For instance, some vendors use motherboards with x8 connectors that are wired as x4. Devices in these slots will only operate at x4 data rates. In the case that you are up-plugging a PCI Express device, make sure that the computer you are using supports up-plugging at the maximum data rate supported by your device. The PCI Express specification only requires up-plugging to operate at the x1 data rate. This could result in a x4 device that is plugged into a x8 connector to operate at x1 data rates (250 MB/s).
Latest Motherboard
Gigabyte GA-P35T-DQ6 (Socket 775) PCI-Express DDR3 Motherboard
The GA-P35T-DQ6 is GIGABYTE next generation, high performance platform based on the killer combination of the new Intel P35 chipset plus support for the latest multi-core processors up to FSB 1333MHz, including the upcoming 45nm platform. Delivering higher memory performance with less power consumption, the GIGABYTE GA-P35T-DQ6 supports DDR3 memory, a critical component for running next generation applications such as high-definition video and 3D visualization.
The GA-P35T-DQ6 is GIGABYTE next generation, high performance platform based on the killer combination of the new Intel P35 chipset plus support for the latest multi-core processors up to FSB 1333MHz, including the upcoming 45nm platform. Delivering higher memory performance with less power consumption, the GIGABYTE GA-P35T-DQ6 supports DDR3 memory, a critical component for running next generation applications such as high-definition video and 3D visualization.
Latest Memory
2GB G.Skill DDR3 PC3-10600 (1333MHz) CL8-8-8...
you are here: G.Skill Computer Memory DDR3 2GB G.Skill DDR3 PC3-10600 (1333MHz) CL8-8-8 HK Series Dual Channel kit
you are here: G.Skill Computer Memory DDR3 2GB G.Skill DDR3 PC3-10600 (1333MHz) CL8-8-8 HK Series Dual Channel kit
Latest Processor
AMD Athlon 64 X2 Dual-Core 5200+ 2.60GHz Processor
Increase your performance by up to 80% with the AMD Athlon 64 X2 Dual-Core processor. Work or play with multiple programs without any stalling or waiting. Dual-core technology is like having two processors, and two working together is better and faster than one working alone.
Increase your performance by up to 80% with the AMD Athlon 64 X2 Dual-Core processor. Work or play with multiple programs without any stalling or waiting. Dual-core technology is like having two processors, and two working together is better and faster than one working alone.
Subscribe to:
Posts (Atom)
