社区
Windows Server
帖子详情
WinXP Professional Update 问题
ahchiee
2003-10-21 10:45:12
每次Update时,点“扫描以寻找更新”,就死在那里,过约5分钟后,出现错误
信息。咋回事?
...全文
49
10
打赏
收藏
WinXP Professional Update 问题
每次Update时,点“扫描以寻找更新”,就死在那里,过约5分钟后,出现错误 信息。咋回事?
复制链接
扫一扫
分享
转发到动态
举报
写回复
配置赞助广告
用AI写文章
10 条
回复
切换为时间正序
请发表友善的回复…
发表回复
打赏红包
luckufo
2003-10-21
打赏
举报
回复
网站的问题,要不不要升级,只要直接下补丁
hnzhb
2003-10-21
打赏
举报
回复
在晚上12点以后升级
mjlwt
2003-10-21
打赏
举报
回复
网站的事,换个时间升级,我就是这样的。
guoke7984
2003-10-21
打赏
举报
回复
这说明你在SP1有问题。这个问题我也碰到过,我没办法,只能重新买了一光盘
vieritjh
2003-10-21
打赏
举报
回复
你去換一個版本啊,你這個太爛了吧,
ahchiee
2003-10-21
打赏
举报
回复
我重装了系统以后,第一次可以update XP SP1,sp1装完重启之后,就是上面说的现象了。
ahchiee
2003-10-21
打赏
举报
回复
谢谢大家,都有
kittyhust
2003-10-21
打赏
举报
回复
可能是网速问题
其实现在市面上有很多打了补丁的盘,我用的那盘是SP2完美版,这种街上很多的
ravenkatte
2003-10-21
打赏
举报
回复
最近Windows Update就是这样,你换一个时段再试试
kbkingbird
2003-10-21
打赏
举报
回复
1、可能与你的os有关系~~不知道是那个版本?
2、与网速有关~~
3、与网站当时情况有关~
good luck~~
70-270 ata 中文题库
1 你负责在
Win
dows2000专业版的机器上安装
Win
dows
XP
专业版。在你开始安装之前,你建立了一个共享文建夹 \\FileSrr01\
Win
Xp
你需要把
Win
dows
XP
专业版的安装文件拷贝到此文件夹。然后你用56-Kbps的连接接入英特网,从
Win
dows更新网站下载更新文件到\\FileSrv01\
XP
Update
s 现在你需要安装
Win
dows
XP
,因为你的办公室的网络用于其他的用途,在安装时,你想用最小的网络带宽。你还希望利用最小的管理来将电脑更新。 A 运行\\FileSrv01\
Win
XP
\
Win
nt32/dudisable命令 B 运行\\FileSrv01\
Win
XP
\
Win
nt32/copydir:i386\
XP
Update
s/dudisable命令 C 运行\\FileSrv01\
Win
XP
\
Win
nt32命令,接受动态更新默认设置并安装更新 D 运行\\FilesSrv01\
Win
XP
\
Win
nt32/duprepare:\\FileSrv01\
XP
Update
s命令 然后,运行\\ FilesSrv01\
Win
XP
\
Win
nt32/dushare:\\FileSrv01\
XP
Update
s命令 答案 D /dushare:pathname 将以前从
Win
dows
Update
网站下载的“动态更新”文件(更新的文件在安装时使用)的目录指定为共享。当从安装共享处运行并使用 /duprepare 时,该选项将执行准备操作,这样,经过更新的文件才能在基于网络的客户端安装中使用。如果没有使用/duprepare并且在客户端上运行,则指定客户端安装将使用位于 pathname 所指定的共享位置的更新文件。 /duprepare 进行安装共享准备,使从
Win
dows
Update
网站下载的“动态更新”文件可以使用它。然后,该共享可用于多个客户端的
Win
dows
XP
安装。只能与 /dushare 一起使用。 在您下载完
Win
dows
XP
动态更新程序包之后,请准备好一个文件夹: 1. 将这些文件提取到一个文件夹中,例如,c:\DU 文件夹。之后,您就应该有两个文件夹。
Win
dows
XP
Pro
f
ession
al
被提取到 IP 文件夹中,而
Win
dows
XP
Home Edition 被提取到 IC 文件夹中。 2. 在您的
Win
dows
XP
光盘上,运行
win
nt32.exe /duprepare:到动态更新程序包文件的路径 命令。在步骤 1 的示例中,您应该运行命令
win
nt32.exe /duprepare:c:\du。 3. 在准备好文件夹之后,将内容复制到另外一个文件夹中,然后将您刚向其中复制内容的那一文件夹设为共享。 4. 在您希望在其上运行安装程序的计算机上,运行
win
nt32.exe /dushare:\\服务器名\共享名 命令。 注意:您还可以将下面的项添加到您的 Unattend.txt 文件中,而不必使用
win
nt32.exe /dushare 这一命令: [Unattended] Dushare=\\服务器名\共享名 2 你是公司的桌面机的管理员。你需要在一台当前运行
Win
dows98的机器上干净的安装
Win
dows
XP
专业版。你开始了安装,文本部分的安装的成功结束了,在基于图形用户界面的安装开始前,电脑没有了响应。你调查并分析发现有个设备的驱动有
问题
。你想知道哪个设备造成了这样的
问题
,你要怎么做? A 在boot.ini文件中加入/fastdetect命令选项,进行硬件
问题
的查找 B 在boot.ini文件中加入/sos命令选项,进行硬件
问题
的查找 C 使用/dudisable命令选项重新开始安装 D 使用/dushare命令选项重新开始安装 E 重启计算机从恢复控制读Dr.Watson.log文件 F 重启计算机从恢复控制读Comsetup.log文件 答案 B
网管教程 从入门到精通软件篇.txt
网管教程 从入门到精通软件篇 ★一。★详细的
xp
修复控制台命令和用法!!! 放入
xp
(2000)的光盘,安装时候选R,修复!
Win
dows
XP
(包括
Win
dows 2000)的控制台命令是在系统出现一些意外情况下的一种非常有效的诊断和测试以及恢复系统功能的工具。小编的确一直都想把这方面的命令做个总结,这次辛苦老范给我们整理了这份实用的秘笈。 Bootcfg bootcfg 命令启动配置和故障恢复(对于大多数计算机,即 boot.ini 文件)。 含有下列参数的 bootcfg 命令仅在使用故障恢复控制台时才可用。可在命令提示符下使用带有不同参数的 bootcfg 命令。 用法: bootcfg /default 设置默认引导项。 bootcfg /add 向引导列表中添加
Win
dows 安装。 bootcfg /rebuild 重复全部
Win
dows 安装过程并允许用户选择要添加的内容。 注意:使用 bootcfg /rebuild 之前,应先通过 bootcfg /copy 命令备份 boot.ini 文件。 bootcfg /scan 扫描用于
Win
dows 安装的所有磁盘并显示结果。 注意:这些结果被静态存储,并用于本次会话。如果在本次会话期间磁盘配置发生变化,为获得更新的扫描,必须先重新启动计算机,然后再次扫描磁盘。 bootcfg /list 列出引导列表中已有的条目。 bootcfg /disableredirect 在启动引导程序中禁用重定向。 bootcfg /redirect [ PortBaudRrate] |[ useBiosSettings] 在启动引导程序中通过指定配置启用重定向。 范例: bootcfg /redirect com1 115200 bootcfg /redirect useBiosSettings hkdsk 创建并显示磁盘的状态报告。Chkdsk 命令还可列出并纠正磁盘上的错误。 含有下列参数的 chkdsk 命令仅在使用故障恢复控制台时才可用。可在命令提示符下使用带有不同参数的 chkdsk 命令。 vol [drive:] [ chkdsk [drive:] [/p] [/r] 参数 无 如果不带任何参数,chkdsk 将显示当前驱动器中的磁盘状态。 drive: 指定要 chkdsk 检查的驱动器。 /p 即使驱动器不在 chkdsk 的检查范围内,也执行彻底检查。该参数不对驱动器做任何更改。 /r 找到坏扇区并恢复可读取的信息。隐含着 /p 参数。 注意 Chkdsk 命令需要 Autochk.exe 文件。如果不能在启动目录(默认为 %systemroot%System32)中找到该文件,将试着在
Win
dows 安装 CD 中找到它。如果有多引导系统的计算机,必须保证是在包含
Win
dows 的驱动器上使用该命令。 Diskpart 创建和删除硬盘驱动器上的分区。diskpart 命令仅在使用故障恢复控制台时才可用。 diskpart [ /add |/delete] [device_name |drive_name |partition_name] [size] 参数 无 如果不带任何参数,diskpart 命令将启动 diskpart 的
Win
dows 字符模式版本。 /add 创建新的分区。 /delete 删除现有分区。 device_name 要创建或删除分区的设备。设备名称可从 map 命令的输出获得。例如,设备名称: DeviceHardDisk0 drive_name 以驱动器号表示的待删除分区。仅与 /delete 同时使用。以下是驱动器名称的范例: D: partition_name 以分区名称表示的待删除分区。可代替 drive_name 使用。仅与 /delete 同时使用。以下是分区名称的范例: DeviceHardDisk0Partition1 大小 要创建的分区大小,以兆字节 (MB)表示。仅与 /add 同时使用。 范例 下例将删除分区: diskpart /delete Device HardDisk0 Partition3 diskpart /delete F: 下例将在硬盘上添加一个 20 MB 的分区: diskpart /add Device HardDisk0 20 Fixboot
联想旭日420A
XP
系统芯片组驱动
************************************************************ *
Pro
duct: Intel(R) Chipset Software Inst
al
lation Utility * Release:
Pro
duction * Version: 7.2.2.1006 * Target Chipset(s)#: 955X/XM/975X/945G/P/PL/GM/PM/GMS/940GML/E7230/E8501 * Date: October 13 2005 ************************************************************ NOTE: For the list of supported chipsets, please refer to the Release Notes ************************************************************ * CONTENTS OF THIS DOCUMENT ************************************************************ This document contains the follo
win
g sections: 1. Overview 2. System Requirements 3. Contents of the Distribution Package 4. List of Available Command Line Flag Options 5. Contents of the Extracted Files 6. Inst
al
ling the Software in Interactive Mode 7. Inst
al
ling the Software in Silent Mode 8. Inst
al
ling the INF Files Prior to OS Inst
al
lation 8A. Inst
al
ling the
Win
dows* 2000 INF Files Prior to OS Inst
al
lation 8B. Inst
al
ling the
Win
dows*
XP
INF Files Prior to OS Inst
al
lation 8C. Inst
al
ling the
Win
dows Server* 2003 INF Files Prior to OS Inst
al
lation 9. Inst
al
ling the INF Files After OS Inst
al
lation 9A. Inst
al
ling the
Win
dows* 2000 INF Files After OS Inst
al
lation 9B. Inst
al
ling the
Win
dows*
XP
INF Files After OS Inst
al
lation 9C. Inst
al
ling the
Win
dows Server* 2003 INF Files After OS Inst
al
lation 10. Verifying Inst
al
lation of the Software and Identifying the Software Version Number 11. Troubleshooting ************************************************************ * 1. OVERVIEW ************************************************************ The Intel(R) Chipset Software Inst
al
lation Utility inst
al
ls
Win
dows* INF files to the target system. These files outline to the operating system how to configure the Intel(R) chipset components in order to ensure that the follo
win
g features function
pro
perly: - Core PCI and ISAPNP Services - PCIe Support - IDE/ATA33/ATA66/ATA100 Storage Support - SATA Storage Support - USB Support - Identification of Intel(R) Chipset Components in the Device Manager This software can be inst
al
led in three modes: Interactive, Silent and Unattended Preload. Interactive Mode requires user input during inst
al
lation; Silent Mode and Unattended Preload do not. This software
al
so offers a set of command line flags, which
pro
vide addition
al
inst
al
lation choices. The command line flags are not case sensitive. Refer to Section 4 for detailed descriptions of these flags. Important Note: The Intel(R) Chipset Software Inst
al
lation Utility is distributed in two formats: self extracting .EXE files (INFINST_AUTOL.EXE) or compressed .ZIP files (INFINST_AUTOL.ZIP). Depending on which distribution format is being executed, the command-line syntax may differ. Refer to Section 4 for more details. ************************************************************ * 2. SYSTEM REQUIREMENTS ************************************************************ 1. Please refer to the Release Notes to view the list of chipsets that the software included with this distribution package is designed to operate with. 2. One of the follo
win
g operating systems must be fully inst
al
led and running on the system before inst
al
ling this software: Microsoft
Win
dows* Server 2003 with Service Pack 1 Microsoft
Win
dows Server 2003 x64 Edition* Microsoft
Win
dows
XP
Pro
f
ession
al
x64 Edition Microsoft
Win
dows
XP
with Service Pack 2 Microsoft
Win
dows 2000 with Service Pack 4 NOTE: This software is designed for the latest service pack releases of above operating systems. To verify which operating system has been inst
al
led onto the target system, follow the steps below: a. Click on Start. b. Select Settings. c. Select Control Panel. d. Double-click on the System icon. e. Click on the Gener
al
system
pro
perties tab. f. Verify which OS has been inst
al
led by reading the System information. 3. It is recommended that the software be inst
al
led on systems with at least 64MB of system memory when using
Win
dows* 2000,
Win
dows*
XP
and
Win
dows Server* 2003. 4. It is recommended that there be a minimum of 5MB of hard disk space on the system in order to inst
al
l this software. 5. The operating system must be fully inst
al
led and running on the system before running this software. 6. Close any running applications to avoid inst
al
lation
pro
blems. 7. It is recommended that the Intel(R) Chipset Software Inst
al
lation Utility be inst
al
led onto the target system prior to the inst
al
lation of other drivers. Please check with the system
pro
vider to determine which operating system and Intel(R) chipset are used in the system. ************************************************************ * 3. CONTENTS OF THE DISTRIBUTION PACKAGE ************************************************************ The Intel(R) Chipset Software Inst
al
lation Utility package contains the follo
win
g items: File(s) ------- INFINST_AUTOL.EXE -or- INFINST_AUTOL.ZIP README.TXT, RELEASE_xxx.HTM *** NOTE: Only the files that reference the currently detected devices are copied to the system. If the -A option is exercised, the files are not copied to the <
Win
dows>\INF directory. Refer to Section 4 for more information. ************************************************************ * 4. LIST OF AVAILABLE COMMAND LINE FLAG OPTIONS ************************************************************ The Intel(R) Chipset Software Inst
al
lation Utility supports sever
al
command line flags for various inst
al
lation options. Due to the different distribution formats available for the Intel(R) Chipset Software Inst
al
lation Utility, the command line flag syntax may vary: 1. Self-Extracting .EXE Distribution: When inst
al
ling this software using the .EXE distribution, an extra '-A' must be appended to the INFINST_AUTOL.EXE
pro
gram c
al
l (i.e. INFINST_AUTOL.EXE -A) in order to successfully pass command line flags. NOTE: The extra '-A' flag for the self-extracting .EXE package is different from the '-A' command line flag option described under Compressed .ZIP Distribution. Example: To extract INF files using the '-A' flag described below, the inst
al
lation
pro
gram should be invoked as follows: INFINST_AUTOL.EXE -A -A (option
al
-P) 2. Compressed .ZIP Distribution: When inst
al
ling this software using the .ZIP distribution, use the command line flags exactly as described below. Example: To extract INF files using the '-A' flag described below, the inst
al
lation
pro
gram should be invoked as follows: SETUP.EXE -A (option
al
-P) Below is a list of
al
l the available command line flags that may be used with the
pro
gram c
al
l. Note that the '-L' and the '-S' flags MUST be specified at the end of the command line flag list. Flag Description ---- ----------- -? Displays the list of available command line flags. This flag works in Interactive Mode only. -A Extracts
al
l the INF files and Readme to either "C:\
Pro
gram Files\Intel\InfInst" or the
allation Path> directory specified using the '-P' flag. The software will NOT inst
al
l these INF files to the system. This flag can be combined only with the '-P' flag.
Al
l other options will be ignored if the '-A' flag is specified. This flag works in Interactive Mode only. -Aonly Extracts only the INF files necessary for the current system. If the inst
al
l has been run once successfully, '-Aonly' will not return any INFs. When used in conjunction with '-over
al
l' switch,
al
l the needed INFs for the system will be extracted. -B Automatic
al
ly reboots the system after inst
al
lation. This flag is ignored if '-A' flag is specified. This flag works in either Silent Mode or Interactive Mode. -f2
Specifies an
al
ternate location and name of the log file created by Inst
al
lShield Silent. This option is used for silent inst
al
lation from a CD. 'Path' indicates the directory path where inst
al
lation status is logged in file 'Logfile' -L
Forces the inst
al
ler user interface to display the specified language during setup. Note that there should be NO space between '-L' and the 4-digit language code (see below). This flag must be placed at the end of the command line flag list. This flag works in Interactive Mode only. -NOLIC Does not display the license agreement di
al
og box during inst
al
lation. This parameter works in Interactive Mode only. -NOREAD Does not display the Readme display during inst
al
lation. This flag works in Interactive Mode only. -NOWEL Does not display the welcome screen during inst
al
lation. This flag works in Interactive Mode only. -OVER
AL
L
Update
s
AL
L INF drivers on
al
l available devices even if third party drivers are currently inst
al
led. This flag works in Interactive Mode only. -OVERIDE
Update
s the storage drivers even if a third party storage driver is currently inst
al
led. This flag works in Interactive Mode only. -OVERSMB
Update
s the SMBus drivers even if third party SMBus drivers are currently inst
al
led. This flag works in Interactive Mode only. -P
allation Path> Specifies the hard disk location to which the INF
pro
gram files are copied. If this flag is not specified at the command line, the
allation Path> directory is as follows: C:\
Pro
gram Files\Intel\INFInst If this flag is used without the '-A' option, only the Readme will be copied to
allation Path>. The directory name can include spaces, but then a pair of double quotes (") must enclose the directory name. There should not be any space between the switch '-p' and the directory name. This flag works in either Silent Mode or Interactive Mode. -S Runs the Inst
al
ler in Silent Mode (no user interface is displayed). This flag and the '-L' flag must be placed at the end of the command line flag list. -SKIP
Suppresses the inst
al
lation of one or more devices.This flag works in either Silent Mode or Interactive Mode. Below are the language codes used with the '-L' flag:
Language -------- ---------- 0001 Arabic (Internation
al
) 0804 Chinese (Simplified) 0404 Chinese (Tradition
al
) 0005 Czech 0006 Danish 0013 Dutch 0009 English (United States) 000B Finnish 040C French (Internation
al
) 0007 German 0008 Greek 000D Hebrew 000E Hungarian 0010 It
al
ian 0011 Japanese 0012 Korean 0014 Norwegian 0015 Polish 0416 Portuguese (Brazil) 0816 Portuguese (Standard) 0019 Russian 000A Spanish (Internation
al
) 001D Swedish 001E Thai 001F Turkish ************************************************************ * 5. CONTENTS OF THE EXTRACTED FILES ************************************************************ INF files are copied to the hard disk after running the Intel(R) Chipset Software Inst
al
lation Utility executable with an '-A' flag (i.e., "INFINST_AUTOL.EXE -A -A" or "SETUP.EXE -A"). The location of the INF files depends on whether a '-P' flag is specified
al
ong with the '-A' flag: 1. If a '-P' flag is not specified, then the INF files are copied to the follo
win
g directory: "C:\
Pro
gram Files\Intel\INFINST" 2. If a '-P' flag is specified, then the INF files are copied to the location listed immediately after the '-P' flag. Refer to Section 4 for more information on flag usage. After INF file extraction, the INF files and components are copied to the
. These files and components are categorized according to the operating system. The follo
win
g table summarizes the locations of the INF files by operating system: The directories are classified according to the operating system that they are designed for:
Win
2000\ Contains INF files designed for
Win
dows* 2000 ONLY.
XP
\ Contains INF files designed for
Win
dows*
XP
ONLY.
Win
2003\ Contains INF files designed for
Win
dows Server* 2003 ONLY. NOTE: The sub directories (e.g. SP) contains speci
al
INFs. NOTE: INFAnswr.TXT makes a CUSTOM.INF template that inst
al
ls the INF files for Intel(R) chipsets during operating system setup. OEMs can incorporate this file into the Setup directory for the OEM Preload Kit. (Refer to Section 8 for more details.) ************************************************************ * 6. INST
AL
LING THE SOFTWARE IN INTERACTIVE MODE ************************************************************ 1. Verify that
al
l system requirements have been met as described in Section 2 above. 2. Run the inst
al
lation
pro
gram: Self-extracting .EXE distribution: INFINST_AUTOL.EXE Compressed .ZIP distribution: SETUP.EXE 3. You will be
pro
mpted to agree to the license agreement. If you do not agree, the inst
al
lation
pro
gram will exit before extracting any files. 4. Once the operating system reboots, follow the on-screen instructions and accept default settings to complete the setup. ************************************************************ * 7. INST
AL
LING THE SOFTWARE IN SILENT MODE ************************************************************ 1. Verify that
al
l system requirements have been met as described in section 2. 2. Run the inst
al
lation
pro
gram: For silent inst
al
l with auto-reboot: Self-extracting .EXE distribution: INFINST_AUTOL.EXE -a -b -s Compressed .ZIP distribution: SETUP.EXE -b -s - or - For silent inst
al
l without auto-reboot: Self-extracting .EXE distribution: INFINST_AUTOL.EXE -a -s Compressed .ZIP distribution: SETUP.EXE -s 3. The utility will perform the necessary
update
s and record the inst
al
lation status in the follo
win
g system registry key: HKEY_LOC
AL
_MACHINE\Software\Intel\INFInst 4. If the utility was invoked with the "-b" flag, the system will automatic
al
ly reboot if the
update
was successful. NOTE: The system MUST be rebooted for
al
l device
update
s to take effect. 5. To determine whether the inst
al
l was successful, verify the "inst
al
l" v
al
ue in the registry key specified in Step 3. 6. In Silent Mode the utility will not display the license agreement. When using Silent Mode the license agreement, license.txt, will be placed in the follo
win
g folder:
Pro
gram Files/Intel/INFInst folder. Please read this agreement. The follo
win
g describes the various parameters: Name: "inst
al
l" Type: String Data: "success" The inst
al
lation was successful. Data: "fail" The inst
al
lation was not successful. No INF files were copied to the system. Name: "reboot" Type: String Data: "Yes" A reboot is required to complete the inst
al
lation. Data: "No" No reboot is required to complete the inst
al
lation. Name: "version" Type: String Data:
Current version number of the Intel(R) Chipset Software Inst
al
lation Utility ************************************************************ * 8. INST
AL
LING THE INF FILES PRIOR TO OS INST
AL
LATION ************************************************************ This
pro
cedure requires a minimum of 5MB of hard disk space. It is important to make sure there is enough disk space before beginning the copy
pro
cess. Copy the operating system inst
al
lation files from the setup directory to a directory on the hard disk. This can be done by opening 'My Computer', right-clicking on the correct drive, and selecting '
Pro
perties'. The directories sh
al
l be referred to as follows:
Win
dows* 2000 : <
WIN
2000 Setup Directory>
Win
dows*
XP
: <
XP
Setup Directory>
Win
dows Server* 2003 : <
WIN
2003 Setup Directory> ************************************************************ * 8A. INST
AL
LING THE
WIN
DOWS* 2000 INF FILES PRIOR TO * OS INST
AL
LATION ************************************************************ NOTE: The
Win
dows* 2000 OEM Preload Kit distribution CD contains a setup directory with
al
l the base operating system setup files and inst
al
lation
pro
grams (
WIN
NT.EXE and
WIN
NT32.EXE). The name of the directory may vary depending on the distribution CD (e.g., \I386\). 1. Create the follo
win
g directory structure under the <
WIN
2000 Setup Directory>: \$OEM$\$$\INF 2. Copy the
Win
dows* 2000 INF files from
\
Win
2000 to the directory created in Step 1 above: <
WIN
2000 Setup Directory>\$OEM$\$$\INF 3. Create the follo
win
g directory structure under the <
WIN
2000 Setup Directory>: \$OEM$\$1\drivers\IntelINF 4. Copy the
Win
dows* 2000 INF files and the cat
al
og files (.CAT) from
\
Win
2000 to the directory created in Step 3 above: <
WIN
2000 Setup Directory>\$OEM$\$1\drivers\IntelINF 5. Either modify the default
Win
dows* 2000 inst
al
lation answer file, UNATTEND.TXT, located in <
WIN
2000 Setup Directory>, or create a customized answer file. The answer file must include the follo
win
g information: [Unattended] OemPreinst
al
l = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Software Inst
al
lation utility files is available at:
\
Win
2000\INFAnswr.TXT For more information about
Win
dows* 2000 answer files and unattended inst
al
lations, please refer to the Microsoft*
Win
dows* 2000 Guide to Unattended Setup. If you are a computer manufacturer, refer to the Microsoft
Win
dows* 2000 OEM Preinst
al
lation Kit (OPK) User Guide for more information about the \$OEM$ folder. Otherwise, refer to the Microsoft
Win
dows* 2000 Deployment Guide. 6. Run "
WIN
NT.EXE /u:
/s:<
WIN
2000 Setup Directory>" to inst
al
l
Win
dows* 2000. ************************************************************ * 8B. INST
AL
LING THE
WIN
DOWS*
XP
INF FILES PRIOR TO * OS INST
AL
LATION ************************************************************ NOTE: The
Win
dows*
XP
OEM Preload Kit distribution CD contains a setup directory with
al
l the base operating system setup files and inst
al
lation
pro
grams (
WIN
NT.EXE and
WIN
NT32.EXE). The name of the directory may vary depending on the distribution CD (e.g., \I386\). 1. Create the follo
win
g directory structure under the <
WIN
XP
Setup Directory>: \$OEM$\$$\INF 2. Copy the
Win
dows*
XP
INF files from
\
XP
to the directory created in Step 1 above: <
WIN
XP
Setup Directory>\$OEM$\$$\INF 3. Create the follo
win
g directory structure under the <
WIN
XP
Setup Directory>: \$OEM$\$1\drivers\IntelINF 4. Copy the
Win
dows*
XP
INF files AND the cat
al
og files (.CAT) from
\
XP
to the directory created in Step 3 above: <
WIN
XP
Setup Directory>\$OEM$\$1\drivers\IntelINF 5. Either modify the default
Win
dows*
XP
inst
al
lation answer file, UNATTEND.TXT, located in <
WIN
XP
Setup Directory>, or create a customized answer file. The answer file must include the follo
win
g information: [Unattended] OemPreinst
al
l = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Software Inst
al
lation utility files is available:
\
XP
\INFAnswr.TXT If you are a computer manufacturer, refer to the Microsoft*
Win
dows*
XP
Guide to Unattended Setup for more information about
Win
dows*
XP
answer files and unattended inst
al
lations. For more information about the \$OEM$ folder, refer to the Microsoft
Win
dows*
XP
OEM Preinst
al
lation Kit (OPK) User Guide. If you are not a manufacturer, refer to the Microsoft
Win
dows*
XP
Deployment Guide. 6. Run "
WIN
NT.EXE /u:
/s:<
WIN
XP
Setup Directory>" to inst
al
l
Win
dows*
XP
. ************************************************************ * 8C. INST
AL
LING THE
WIN
DOWS SERVER* 2003 INF FILES PRIOR * TO OS INST
AL
LATION ************************************************************ NOTE: The
Win
dows Server* 2003 OEM Preload Kit distribution CD contains a setup directory with
al
l the base operating system setup files and inst
al
lation
pro
grams (
WIN
NT.EXE and
WIN
NT32.EXE). The name of the directory may vary depending on the distribution CD (e.g., \I386\). 1. Create the follo
win
g directory structure under the <
WIN
2003 Setup Directory>: \$OEM$\$$\INF 2. Copy the
Win
dows Server* 2003 INF files from
\
Win
2003 to the directory created in Step 1 above: <
WIN
2003 Setup Directory>\$OEM$\$$\INF 3. Create the follo
win
g directory structure under the <
WIN
2003 Setup Directory>: \$OEM$\$1\drivers\IntelINF 4. Copy the
Win
dows Server* 2003 INF files and the cat
al
og files (.CAT) from
\
Win
2003 to the directory created in Step 3 above: <
WIN
2003 Setup Directory>\$OEM$\$1\drivers\IntelINF 5. Either modify the default
Win
dows Server* 2003 inst
al
lation answer file, UNATTEND.TXT, located in <
WIN
2000 Setup Directory>, or create a customized answer file. The answer file must include the follo
win
g information: [Unattended] OemPreinst
al
l = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Software Inst
al
lation utility files is available:
\
Win
2003\INFAnswr.TXT For more information about
Win
dows Server* 2003 answer files and unattended inst
al
lations, please refer to the Microsoft
Win
dows Server* 2003 Guide to Unattended Setup. If you are a computer manufacturer, refer to the Microsoft
Win
dows Server* 2003 OEM Preinst
al
lation Kit (OPK) User Guide for more information about the \$OEM$ folder. Otherwise, refer to the Microsoft
Win
dows Server* 2003 Deployment Guide. 6. Run "
WIN
NT.EXE /u:
/s:<
WIN
2003 Setup Directory>" to inst
al
l
Win
dows* 2000. ************************************************************ * 9. INST
AL
LING THE INF FILES AFTER OS INST
AL
LATION ************************************************************ ************************************************************ * 9A. INST
AL
LING THE
WIN
DOWS* 2000 INF FILES AFTER OS * INST
AL
LATION ************************************************************ Some Intel(R) chipset platforms
al
ready are supported by
Win
dows* 2000, so it may not be necessary to use the INF files
pro
vided by this software to
update
Win
dows* 2000. The follo
win
g steps describe the inst
al
lation
pro
cess of the
Win
dows* 2000 INF files. You may need to repeat these steps to
update
al
l Intel(R) chipset devices not supported by
Win
dows* 2000. 1. Copy the contents of the
\
Win
2000 directory to the root directory of the floppy disk (A:\). 2. Close
al
l
pro
grams currently running on the system. 3. Click on Start. 4. Select Settings. 5. Select Control Panel. 6. Double-click on the System icon. 7. Click on the Hardware tab. 8. Click on the Device Manager button. 9. Select "Devices by connection" under the View menu. 10. Click on MPS Uni
pro
cessor PC -OR- MPS Multi
pro
cessor PC. NOTE: Only one of the above items will be displayed for a given system. 11. Click on PCI bus. 12. Right-click on the line containing the description PCI standard host CPU bridge -or- PCI standard ISA bridge -or- PCI standard PCI-to-PCI bridge -or- PCI System Management Bus -or- Standard Du
al
PCI IDE Controller -or- Standard Univers
al
PCI to USB Host Controller (This line will be selected.) 13. Select
Pro
perties from the pull-down menu. 14. Click on the Driver tab. 15. Click on the
Update
Driver button. 16.
Win
dows* 2000 will launch the Upgrade Device Driver Wizard. Select Next. 17. Ensure that the follo
win
g choice is selected: Search for a suitable driver for my device (recommended) 18. Insert the floppy containing the
Win
dows* 2000 INF files into the floppy drive. 19. Select Next. 20.
Win
dows* 2000 will list locations from where the
update
d driver file can be found. Ensure that the follo
win
g choice is selected: Floppy disk drives 21. Select Next. 22.
Win
dows* 2000 should report that a driver has been found: (The detected device name will be displayed.) Select Next. 23. Select Finish. 24. Reboot the system when
pro
mpted to do so. ************************************************************ * 9B. INST
AL
LING THE
WIN
DOWS*
XP
INF FILES AFTER OS * INST
AL
LATION ************************************************************ Some Intel(R) chipset platforms
al
ready are supported by
Win
dows*
XP
so it may not be necessary to use the INF files
pro
vided by this software to
update
Win
dows*
XP
. The follo
win
g steps describe the inst
al
lation
pro
cess of the
Win
dows*
XP
INF files. You may need to repeat these steps to
update
al
l Intel(R) chipset devices not supported by
Win
dows*
XP
. 1. Copy the contents of the
\
XP
directory to the root directory of the floppy disk (A:\). 2. Close
al
l
pro
grams currently running on the system. 3. Click on Start. 4. Select Settings. 5. Select the Control Panel. 6. Double-click on the System icon. 7. Click on the Hardware tab. 8. Click on the Device Manager button. 9. Select "Devices by connection" under the View menu. 10. Click on MPS Uni
pro
cessor PC -OR- MPS Multi
pro
cessor PC. NOTE: Only one of the above items will be displayed for a given system. 11. Click on PCI bus. 12. Right-click on the line containing the description PCI standard host CPU bridge -or- PCI standard ISA bridge -or- PCI standard PCI-to-PCI bridge -or- PCI System Management Bus -or- Standard Du
al
PCI IDE Controller -or- Standard Univers
al
PCI to USB Host Controller (This line will be selected.) 13. Select
Pro
perties from the pull-down menu. 14. Click on the Driver tab. 15. Click on the
Update
Driver button. 16.
Win
dows*
XP
will launch the Upgrade Device Driver Wizard. Select Next. 17. Ensure that the follo
win
g choice is selected: Search for a suitable driver for my device (recommended) 18. Insert the floppy containing the
Win
dows*
XP
INF files into the floppy drive. 19. Select Next. 20.
Win
dows*
XP
will list locations from where the
update
d driver file can be found. Ensure that the follo
win
g choice is selected: Floppy disk drives 21. Select Next. 22.
Win
dows*
XP
should report that a driver has been found: (The detected device name will be displayed.) Select Next. 23. Select Finish. 24. Reboot the system when
pro
mpted to do so. ************************************************************ * 9C. INST
AL
LING THE
WIN
DOWS SERVER* 2003 INF FILES AFTER * OS INST
AL
LATION ************************************************************ Some Intel(R) chipset platforms
al
ready are supported by
Win
dows Server* 2003 so it may not be necessary to use the INF files
pro
vided by this software to
update
Win
dows Server* 2003. The follo
win
g steps describe the inst
al
lation
pro
cess of the
Win
dows*
XP
INF files. You may need to repeat these steps to
update
al
l Intel(R) chipset devices not supported by
Win
dows Server* 2003. 1. Copy the contents of the
\
Win
2003 directory to the root directory of the floppy disk (A:\). 2. Close
al
l
pro
grams currently running on the system. 3. Click on Start. 4. Select Settings. 5. Select the Control Panel. 6. Double-click on the System icon. 7. Click on the Hardware tab. 8. Click on the Device Manager button. 9. Select "Devices by connection" under the View menu. 10. Click on MPS Uni
pro
cessor PC -OR- MPS Multi
pro
cessor PC. NOTE: Only one of the above items will be displayed for a given system. 11. Click on PCI bus. 12. Right-click on the line containing the description PCI standard host CPU bridge -or- PCI standard ISA bridge -or- PCI standard PCI-to-PCI bridge -or- PCI System Management Bus -or- Standard Du
al
PCI IDE Controller -or- Standard Univers
al
PCI to USB Host Controller (This line will be selected.) 13. Select
Pro
perties from the pull-down menu. 14. Click on the Driver tab. 15. Click on the
Update
Driver button. 16.
Win
dows Server* 2003 will launch the Upgrade Device Driver Wizard. Select Next. 17. Ensure that the follo
win
g choice is selected: Search for a suitable driver for my device (recommended) 18. Insert the floppy containing the
Win
dows Server* 2003 INF files into the floppy drive. 19. Select Next. 20.
Win
dows Server* 2003 will list locations from where the
update
d driver file can be found. Ensure that the follo
win
g choice is selected: Floppy disk drives 21. Select Next. 22.
Win
dows Server* 2003 should report that a driver has been found: (The detected device name will be displayed.) Select Next. 23. Select Finish. 24. Reboot the system when
pro
mpted to do so. ************************************************************ * 10. IDENTIFYING THE SOFTWARE VERSION NUMBER ************************************************************ The version numbers displayed by Device Manager for a given device may not be the same as the Intel(R) Chipset Software Inst
al
lation Utility version. The correct version number is shown at the top of this file. ************************************************************ * 11. TROUBLESHOOTING ************************************************************ It is assumed that the system requirements in Section 2 above have been satisfied. Issue: At the end of executing the Chipset Software Inst
al
lation Utility, the USB keyboard and mouse will stop functioning. This
pro
blem only occurs when using
Win
dows
XP
with SP1 or
Win
dows 2000 Server with SP4 on a system configured with a USB keyboard and/or mouse. This condition is temporary until a system reset. Solution1: A recommended fix has been
pro
vided by Microsoft in Knowledge Base article(822603). For addition
al
information, please refer to the KB article located at http://support.microsoft.com/default.aspx?scid=kb;[LN];822603 Please use the follo
win
g inst
al
lation
pro
cedures: -
Win
dows
XP
inst
al
led with SP1 - QFE (822603) inst
al
led - Latest Chipset Utility Software inst
al
led. Solution2: The command line flag "-Skip
" can be used with the Intel(R) Chipset Software Inst
al
lation Utility
pro
gram to cause the USB2 driver not to be inst
al
led. The DevID's for ICH4/ICH5 are 24CD/24DD. This will cause the USB2 controller to have a yellow exclamation point in Device Manager (Usu
al
ly located under Other Devices and identified as "Univers
al
Seri
al
Bus (USB) Controller"). To inst
al
l the USB2 driver right-click this entry, select
update
driver, and
al
low the system to inst
al
l automatic
al
ly. When completed, nothing more should be required. Issue: System locks up during Device Manager Remove or during restart. Solution: System lockup can occur during reboot as a result of sever
al
possible system issues. In the event of system lockup, reboot the machine and view Device Manager. If devices are listed
pro
perly and the system e
xp
eriences no further
pro
blems, then the .INF file restore
pro
cess was successful. If devices are not configured correctly, try re-running the
pro
cedures outlined in Section 3. If this does not fix the issue or further issues are e
xp
erienced, reinst
al
l the operating system. Issue: After running the setup
pro
gram and rebooting the machine,
Win
dows reports that it cannot find one of the follo
win
g files: ESDI_506.pdr Solution: Click Browse in the di
al
og box where this issue occurs, locate the <
Win
dows>\System\IOSubsys directory. Click OK. The system should be able to locate this file in this directory and continue re-enumerating for the new devices. Issue: After running the setup
pro
gram and rebooting the machine,
Win
dows reports that it cannot find one of the follo
win
g files: UHCD.SYS USBD.SYS USBHUB.SYS Solution: Click Browse in the di
al
og box where this issue occurs and locate the follo
win
g directory: <
Win
nt>\System32\drivers Click OK. The system should be able to locate the files in this directory and continue re-enumerating for the new devices. Issue: After running the setup
pro
gram and rebooting the machine,
Win
dows reports that it cannot find the follo
win
g file: ISAPNP.VXD Solution: Click Browse in the di
al
og box where this issue occurs and locate the <
Win
nt>\System directory. Click OK. The system should be able to locate this file in this directory and continue re-enumerating for the new devices. Issue: After performing the silent inst
al
l, the HKLM\Software\Intel\InfInst key was not created or the data of the v
al
ue "inst
al
l" is not "success". Solution: This is caused by one of the follo
win
g scenarios: - The current system does not contain a supported operating system, or -or- - The current system does not contain a supported chipset. Verify that the System Requirements are met as outlined in Section 2. ************************************************************ * DISCLAIMER ************************************************************ Intel is making no claims of usability, efficacy or warranty. The Intel(R) SOFTWARE LICENSE AGREEMENT (OEM / IHV / ISV Distribution & Single User) completely defines the licensed use of this software. ************************************************************ Information in this document is
pro
vided in connection with Intel(R)
pro
ducts. No license, e
xp
ress or implied, by estoppel or otherwise, to any intellectu
al
pro
perty rights is granted by this document. Intel assumes no liability whatsoever, and Intel disclaims any e
xp
ress or implied warranty relating to s
al
e and/or use of Intel(R)
pro
ducts, including liability or warranties relating to fitness for a particular purpose, merchantability or infringement of any patent, copyright or other intellectu
al
pro
perty right. Intel(R)
pro
ducts are not intended for use in medic
al
, life saving, or life-sustaining applications. ************************************************************ Intel Corporation disclaims
al
l warranties and liabilities for the use of this document and the information contained herein, and assumes no responsibility for any errors which may appear in this document, nor does Intel make a commitment to
update
the information contained herein. Intel reserves the right to make changes to this document at any time, without notice. ************************************************************ ************************************************************ * Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. * Other brands and names are the
pro
perty of their respective owners. Copyright (c) Intel Corporation, 1997-2005
微软MSDN原版系统—
Win
dows
XP
*******************************************************************************************************
Update
Rollup 2 for
Win
dows
XP
Media Center Edition 2005 (Simplified Chinese)包括: Media Center文件
最全面的
Win
dows
XP
原版系统镜像下载
ed2k://|file|CN_
WIN
XP
_
PRO
_ISO.img|530186240|7855069CE4216615D761654E2B75A4F7|/ed2k://|file|CN_
WIN
XP
_HOME_ISO.img|513515520|58373CA20ABB0438AF5858AEBF22E983|/ed2k://|file|cn_
win
dows_internet_e
xp
lorer_8_for_
win
dows_
xp
_x86.exe|16901472|22A386A900AD11E034839A1
Windows Server
6,850
社区成员
178,035
社区内容
发帖
与我相关
我的任务
Windows Server
Windows 2016/2012/2008/2003/2000/NT
复制链接
扫一扫
分享
社区描述
Windows 2016/2012/2008/2003/2000/NT
社区管理员
加入社区
获取链接或二维码
近7日
近30日
至今
加载中
查看更多榜单
社区公告
暂无公告
试试用AI创作助手写篇文章吧
+ 用AI写文章