installshield中的Path设置

meetwinter 2003-08-20 04:39:18
在用installshield制作安装程序的时候,我想在目的计算机上的path搜索路径中加上执行文件的路径,如:TARGET ^ "bin";%PATH%

我采用的方法是首先RegDBGetKeyValueEx()函数得到原始的Path值,然后将此值与TARGET ^ "bin"相拼接,最后再用RegDBSetKeyValueEx()写入。
现在的问题是当我卸载程序的时候,整个Path都被删除掉了,这当然不是我所期望的,不知有什么好的办法可以避免,或者说是否有一种更巧妙的方法实现我的目的。
...全文
219 4 打赏 收藏 转发到动态 举报
写回复
用AI写文章
4 条回复
切换为时间正序
请发表友善的回复…
发表回复
meetwinter 2003-08-28
  • 打赏
  • 举报
回复
问题已解决。遇到同样情况的各位同行可参照以下代码:
function AddPath(szDir)
STRING svShortDir;
STRING szNewPath;
STRING szOldPath;
NUMBER nvResult;
NUMBER nvAlreadyThere;
STRING svResult;
begin

Disable(LOGGING);

svShortDir=szDir;
LongPathToShortPath ( svShortDir );

nvAlreadyThere = FALSE;
if (GetEnvVar("PATH",szOldPath)=0) then
nvAlreadyThere = szOldPath % svShortDir;
endif;

if (!nvAlreadyThere) then

GetSystemInfo ( OS , nvResult , svResult );

// us a different routine if we are in Windows NT
if (nvResult = IS_WINDOWSNT) then
nvResult = AddNTPath(svShortDir);
else
svShortDir = "%PATH%;" + svShortDir;
nvResult = EzBatchAddPath ( "PATH" , svShortDir , "" , AFTER );
endif;

endif;

Enable(LOGGING);

return nvResult;

end;

// SIAS
// ----
// There are also problems with InstallShield's environment variable handling
// this set of routines handles them better
//
// First - make an environment variable - general routine
function MakeEV(szVar,szValue)
NUMBER nvResult;
STRING svResult;
STRING svFileName;
begin

GetSystemInfo ( OS , nvResult , svResult );
// use a different routine for NT
if (nvResult = IS_WINDOWSNT) then
return MakeNTEV(szVar,szValue);
else
BatchGetFileName ( svFileName );
//ZapBatchLine (svFileName, "SET " + szVar );
EzBatchAddString((szVar + "=" + szValue),"",REPLACE);
return EzBatchReplace ( "SET " + szVar + "=" + szValue );
endif;

end;

// Same routine as "MakeEV" above but specifically for NT
function MakeNTEV(szVar,szValue)
NUMBER nResult;
POINTER pEnv;
STRING szKey,szEnv;
begin

szKey = "SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment";
RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
nResult = RegDBSetKeyValueEx(szKey, szVar, REGDB_STRING, szValue, -1);
if (nResult >= 0) then
// Flush the NT registry to all applications.
szEnv = "Environment";
pEnv = &szEnv;
SendMessage (HWND_BROADCAST, WM_WININICHANGE, 0, pEnv );
endif;

return nResult;

end;

// Ass to the NT PATH Environment variable
function AddNTPath(szDir)
NUMBER nResult;
POINTER pEnv;
STRING szKey,szEnv;
STRING szOldPath,szNewPath;
NUMBER nvLen,nvType;
begin


szKey = "SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment";
RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE);
nResult = RegDBGetKeyValueEx(szKey, "Path", nvType, szOldPath, nvLen);
if (nResult >= 0) then
szNewPath=szOldPath + ";" + szDir;
nResult = RegDBSetKeyValueEx(szKey,"Path", REGDB_STRING, szNewPath, -1);
if (nResult >= 0) then
// Flush the NT registry to all applications.
szEnv = "Environment";
pEnv = &szEnv;
SendMessage (HWND_BROADCAST, WM_WININICHANGE, 0, pEnv );
endif;
endif;
return nResult;

end;
踏岸寻柳 2003-08-28
  • 打赏
  • 举报
回复
2000以后的都是在系统环境变量中设置path,原来的autoexec.bat已经没有作用了???

是这样的吗!?我不是很清楚!

其实在InstallShield里面有这样的函数:BatchAdd,顾名思义,就是在OS的Autoexec.bat文件中添加信息的,不仅仅局限于路径信息 :)

在IS 6.22的帮助文件中是这么说的:
For example, if you want to add the environment variable TEMP to the Autoexec.bat file, you would want to add a statement like this:
SET TEMP=C:\Windows\Temp
To add the TEMP variable after the PATH statement:
SET PATH=C:\Win32s
Use this code in your setup script:
BatchAdd("TEMP", "C:\\Windows\\Temp", "PATH", AFTER);
When you set an environment variable, do not end the statement with a semicolon.
The BatchAdd function automatically adds the word "SET" before the environment variable and the equal sign (=) after the environment variable. The BatchAdd function does not add anything if szKey is a command statement (specified with the COMMAND option).
When you are finished making the changes to the Autoexec.bat file, call the BatchFileSave function to save the changes to disk. When you save the file, you can also create a backup file.

但是,它并没有涉及到如何卸载一部分配置信息的问题,再考虑考虑。
sljz 2003-08-20
  • 打赏
  • 举报
回复
因为2000以后的都是在系统环境变量中设置path,原来的autoexec.bat已经没有作用了,是不是可以这样:
path在autoexec.bat中添加
OpenFileMode(FILE_MODE_APPEND);
OpenFile(nvFileHandle,"C:\\","Autoexec.bat");
WriteLine(nvFileHandle,"SETPATH=%PATH%;C:\\bin");

然后反安装的时候将这行删除。。。

我没有测试过,不知道说的对不对,请批评指正。
lqbn 2003-08-20
  • 打赏
  • 举报
回复
您的思想其实是正确的,我也是这样想的。

其实在OnFirstUIAfter函数中加入安装时的注册表操作;然后相应的在OnMoving函数中加上卸载时的注册表操作即可。
************************************************************ * Product: Intel(R) Chipset Software Installation Utility * Release: Production * 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 following 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. Installing the Software in Interactive Mode 7. Installing the Software in Silent Mode 8. Installing the INF Files Prior to OS Installation 8A. Installing the Windows* 2000 INF Files Prior to OS Installation 8B. Installing the Windows* XP INF Files Prior to OS Installation 8C. Installing the Windows Server* 2003 INF Files Prior to OS Installation 9. Installing the INF Files After OS Installation 9A. Installing the Windows* 2000 INF Files After OS Installation 9B. Installing the Windows* XP INF Files After OS Installation 9C. Installing the Windows Server* 2003 INF Files After OS Installation 10. Verifying Installation of the Software and Identifying the Software Version Number 11. Troubleshooting ************************************************************ * 1. OVERVIEW ************************************************************ The Intel(R) Chipset Software Installation Utility installs Windows* 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 following features function properly: - 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 installed in three modes: Interactive, Silent and Unattended Preload. Interactive Mode requires user input during installation; Silent Mode and Unattended Preload do not. This software also offers a set of command line flags, which provide additional installation 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 Installation 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 following operating systems must be fully installed and running on the system before installing this software: Microsoft Windows* Server 2003 with Service Pack 1 Microsoft Windows Server 2003 x64 Edition* Microsoft Windows XP Professional x64 Edition Microsoft Windows XP with Service Pack 2 Microsoft Windows 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 installed 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 General system properties tab. f. Verify which OS has been installed by reading the System information. 3. It is recommended that the software be installed on systems with at least 64MB of system memory when using Windows* 2000, Windows* XP and Windows Server* 2003. 4. It is recommended that there be a minimum of 5MB of hard disk space on the system in order to install this software. 5. The operating system must be fully installed and running on the system before running this software. 6. Close any running applications to avoid installation problems. 7. It is recommended that the Intel(R) Chipset Software Installation Utility be installed onto the target system prior to the installation of other drivers. Please check with the system provider 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 Installation Utility package contains the following 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 \INF directory. Refer to Section 4 for more information. ************************************************************ * 4. LIST OF AVAILABLE COMMAND LINE FLAG OPTIONS ************************************************************ The Intel(R) Chipset Software Installation Utility supports several command line flags for various installation options. Due to the different distribution formats available for the Intel(R) Chipset Software Installation Utility, the command line flag syntax may vary: 1. Self-Extracting .EXE Distribution: When installing this software using the .EXE distribution, an extra '-A' must be appended to the INFINST_AUTOL.EXE program call (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 installation program should be invoked as follows: INFINST_AUTOL.EXE -A -A (optional -P) 2. Compressed .ZIP Distribution: When installing 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 installation program should be invoked as follows: SETUP.EXE -A (optional -P) Below is a list of all the available command line flags that may be used with the program call. 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 all the INF files and Readme to either "C:\Program Files\Intel\InfInst" or the Path> directory specified using the '-P' flag. The software will NOT install these INF files to the system. This flag can be combined only with the '-P' flag. All 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 install has been run once successfully, '-Aonly' will not return any INFs. When used in conjunction with '-overall' switch, all the needed INFs for the system will be extracted. -B Automatically reboots the system after installation. This flag is ignored if '-A' flag is specified. This flag works in either Silent Mode or Interactive Mode. -f2<path\Logfile> Specifies an alternate location and name of the log file created by InstallShield Silent. This option is used for silent installation from a CD. 'Path' indicates the directory path where installation status is logged in file 'Logfile' -L Forces the installer 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 dialog box during installation. This parameter works in Interactive Mode only. -NOREAD Does not display the Readme display during installation. This flag works in Interactive Mode only. -NOWEL Does not display the welcome screen during installation. This flag works in Interactive Mode only. -OVERALL Updates ALL INF drivers on all available devices even if third party drivers are currently installed. This flag works in Interactive Mode only. -OVERIDE Updates the storage drivers even if a third party storage driver is currently installed. This flag works in Interactive Mode only. -OVERSMB Updates the SMBus drivers even if third party SMBus drivers are currently installed. This flag works in Interactive Mode only. -PPath> Specifies the hard disk location to which the INF program files are copied. If this flag is not specified at the command line, the Path> directory is as follows: C:\Program Files\Intel\INFInst If this flag is used without the '-A' option, only the Readme will be copied to 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 Installer 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 installation 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 (International) 0804 Chinese (Simplified) 0404 Chinese (Traditional) 0005 Czech 0006 Danish 0013 Dutch 0009 English (United States) 000B Finnish 040C French (International) 0007 German 0008 Greek 000D Hebrew 000E Hungarian 0010 Italian 0011 Japanese 0012 Korean 0014 Norwegian 0015 Polish 0416 Portuguese (Brazil) 0816 Portuguese (Standard) 0019 Russian 000A Spanish (International) 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 Installation 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 along with the '-A' flag: 1. If a '-P' flag is not specified, then the INF files are copied to the following directory: "C:\Program 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 following 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: Win2000\ Contains INF files designed for Windows* 2000 ONLY. XP\ Contains INF files designed for Windows* XP ONLY. Win2003\ Contains INF files designed for Windows Server* 2003 ONLY. NOTE: The sub directories (e.g. SP) contains special INFs. NOTE: INFAnswr.TXT makes a CUSTOM.INF template that installs 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. INSTALLING THE SOFTWARE IN INTERACTIVE MODE ************************************************************ 1. Verify that all system requirements have been met as described in Section 2 above. 2. Run the installation program: Self-extracting .EXE distribution: INFINST_AUTOL.EXE Compressed .ZIP distribution: SETUP.EXE 3. You will be prompted to agree to the license agreement. If you do not agree, the installation program 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. INSTALLING THE SOFTWARE IN SILENT MODE ************************************************************ 1. Verify that all system requirements have been met as described in section 2. 2. Run the installation program: For silent install with auto-reboot: Self-extracting .EXE distribution: INFINST_AUTOL.EXE -a -b -s Compressed .ZIP distribution: SETUP.EXE -b -s - or - For silent install 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 updates and record the installation status in the following system registry key: HKEY_LOCAL_MACHINE\Software\Intel\INFInst 4. If the utility was invoked with the "-b" flag, the system will automatically reboot if the update was successful. NOTE: The system MUST be rebooted for all device updates to take effect. 5. To determine whether the install was successful, verify the "install" value 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 following folder: Program Files/Intel/INFInst folder. Please read this agreement. The following describes the various parameters: Name: "install" Type: String Data: "success" The installation was successful. Data: "fail" The installation was not successful. No INF files were copied to the system. Name: "reboot" Type: String Data: "Yes" A reboot is required to complete the installation. Data: "No" No reboot is required to complete the installation. Name: "version" Type: String Data: Current version number of the Intel(R) Chipset Software Installation Utility ************************************************************ * 8. INSTALLING THE INF FILES PRIOR TO OS INSTALLATION ************************************************************ This procedure requires a minimum of 5MB of hard disk space. It is important to make sure there is enough disk space before beginning the copy process. Copy the operating system installation 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 'Properties'. The directories shall be referred to as follows: Windows* 2000 : Windows* XP : Windows Server* 2003 : ************************************************************ * 8A. INSTALLING THE WINDOWS* 2000 INF FILES PRIOR TO * OS INSTALLATION ************************************************************ NOTE: The Windows* 2000 OEM Preload Kit distribution CD contains a setup directory with all the base operating system setup files and installation programs (WINNT.EXE and WINNT32.EXE). The name of the directory may vary depending on the distribution CD (e.g., \I386\). 1. Create the following directory structure under the : \$OEM$\$$\INF 2. Copy the Windows* 2000 INF files from \Win2000 to the directory created in Step 1 above: \$OEM$\$$\INF 3. Create the following directory structure under the : \$OEM$\$1\drivers\IntelINF 4. Copy the Windows* 2000 INF files and the catalog files (.CAT) from \Win2000 to the directory created in Step 3 above: \$OEM$\$1\drivers\IntelINF 5. Either modify the default Windows* 2000 installation answer file, UNATTEND.TXT, located in , or create a customized answer file. The answer file must include the following information: [Unattended] OemPreinstall = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Software Installation utility files is available at: \Win2000\INFAnswr.TXT For more information about Windows* 2000 answer files and unattended installations, please refer to the Microsoft* Windows* 2000 Guide to Unattended Setup. If you are a computer manufacturer, refer to the Microsoft Windows* 2000 OEM Preinstallation Kit (OPK) User Guide for more information about the \$OEM$ folder. Otherwise, refer to the Microsoft Windows* 2000 Deployment Guide. 6. Run "WINNT.EXE /u: /s:" to install Windows* 2000. ************************************************************ * 8B. INSTALLING THE WINDOWS* XP INF FILES PRIOR TO * OS INSTALLATION ************************************************************ NOTE: The Windows* XP OEM Preload Kit distribution CD contains a setup directory with all the base operating system setup files and installation programs (WINNT.EXE and WINNT32.EXE). The name of the directory may vary depending on the distribution CD (e.g., \I386\). 1. Create the following directory structure under the : \$OEM$\$$\INF 2. Copy the Windows* XP INF files from \XP to the directory created in Step 1 above: \$OEM$\$$\INF 3. Create the following directory structure under the : \$OEM$\$1\drivers\IntelINF 4. Copy the Windows* XP INF files AND the catalog files (.CAT) from \XP to the directory created in Step 3 above: \$OEM$\$1\drivers\IntelINF 5. Either modify the default Windows* XP installation answer file, UNATTEND.TXT, located in , or create a customized answer file. The answer file must include the following information: [Unattended] OemPreinstall = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Software Installation utility files is available: \XP\INFAnswr.TXT If you are a computer manufacturer, refer to the Microsoft* Windows* XP Guide to Unattended Setup for more information about Windows* XP answer files and unattended installations. For more information about the \$OEM$ folder, refer to the Microsoft Windows* XP OEM Preinstallation Kit (OPK) User Guide. If you are not a manufacturer, refer to the Microsoft Windows* XP Deployment Guide. 6. Run "WINNT.EXE /u: /s:" to install Windows* XP. ************************************************************ * 8C. INSTALLING THE WINDOWS SERVER* 2003 INF FILES PRIOR * TO OS INSTALLATION ************************************************************ NOTE: The Windows Server* 2003 OEM Preload Kit distribution CD contains a setup directory with all the base operating system setup files and installation programs (WINNT.EXE and WINNT32.EXE). The name of the directory may vary depending on the distribution CD (e.g., \I386\). 1. Create the following directory structure under the : \$OEM$\$$\INF 2. Copy the Windows Server* 2003 INF files from \Win2003 to the directory created in Step 1 above: \$OEM$\$$\INF 3. Create the following directory structure under the : \$OEM$\$1\drivers\IntelINF 4. Copy the Windows Server* 2003 INF files and the catalog files (.CAT) from \Win2003 to the directory created in Step 3 above: \$OEM$\$1\drivers\IntelINF 5. Either modify the default Windows Server* 2003 installation answer file, UNATTEND.TXT, located in , or create a customized answer file. The answer file must include the following information: [Unattended] OemPreinstall = Yes OemPnPDriversPath="drivers\IntelINF" A sample answer file for preloading the Intel(R) Chipset Software Installation utility files is available: \Win2003\INFAnswr.TXT For more information about Windows Server* 2003 answer files and unattended installations, please refer to the Microsoft Windows Server* 2003 Guide to Unattended Setup. If you are a computer manufacturer, refer to the Microsoft Windows Server* 2003 OEM Preinstallation Kit (OPK) User Guide for more information about the \$OEM$ folder. Otherwise, refer to the Microsoft Windows Server* 2003 Deployment Guide. 6. Run "WINNT.EXE /u: /s:" to install Windows* 2000. ************************************************************ * 9. INSTALLING THE INF FILES AFTER OS INSTALLATION ************************************************************ ************************************************************ * 9A. INSTALLING THE WINDOWS* 2000 INF FILES AFTER OS * INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows* 2000, so it may not be necessary to use the INF files provided by this software to update Windows* 2000. The following steps describe the installation process of the Windows* 2000 INF files. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows* 2000. 1. Copy the contents of the \Win2000 directory to the root directory of the floppy disk (A:\). 2. Close all programs 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 Uniprocessor PC -OR- MPS Multiprocessor 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 Dual PCI IDE Controller -or- Standard Universal PCI to USB Host Controller (This line will be selected.) 13. Select Properties from the pull-down menu. 14. Click on the Driver tab. 15. Click on the Update Driver button. 16. Windows* 2000 will launch the Upgrade Device Driver Wizard. Select Next. 17. Ensure that the following choice is selected: Search for a suitable driver for my device (recommended) 18. Insert the floppy containing the Windows* 2000 INF files into the floppy drive. 19. Select Next. 20. Windows* 2000 will list locations from where the updated driver file can be found. Ensure that the following choice is selected: Floppy disk drives 21. Select Next. 22. Windows* 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 prompted to do so. ************************************************************ * 9B. INSTALLING THE WINDOWS* XP INF FILES AFTER OS * INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows* XP so it may not be necessary to use the INF files provided by this software to update Windows* XP. The following steps describe the installation process of the Windows* XP INF files. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows* XP. 1. Copy the contents of the \XP directory to the root directory of the floppy disk (A:\). 2. Close all programs 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 Uniprocessor PC -OR- MPS Multiprocessor 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 Dual PCI IDE Controller -or- Standard Universal PCI to USB Host Controller (This line will be selected.) 13. Select Properties from the pull-down menu. 14. Click on the Driver tab. 15. Click on the Update Driver button. 16. Windows* XP will launch the Upgrade Device Driver Wizard. Select Next. 17. Ensure that the following choice is selected: Search for a suitable driver for my device (recommended) 18. Insert the floppy containing the Windows* XP INF files into the floppy drive. 19. Select Next. 20. Windows* XP will list locations from where the updated driver file can be found. Ensure that the following choice is selected: Floppy disk drives 21. Select Next. 22. Windows* 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 prompted to do so. ************************************************************ * 9C. INSTALLING THE WINDOWS SERVER* 2003 INF FILES AFTER * OS INSTALLATION ************************************************************ Some Intel(R) chipset platforms already are supported by Windows Server* 2003 so it may not be necessary to use the INF files provided by this software to update Windows Server* 2003. The following steps describe the installation process of the Windows* XP INF files. You may need to repeat these steps to update all Intel(R) chipset devices not supported by Windows Server* 2003. 1. Copy the contents of the \Win2003 directory to the root directory of the floppy disk (A:\). 2. Close all programs 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 Uniprocessor PC -OR- MPS Multiprocessor 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 Dual PCI IDE Controller -or- Standard Universal PCI to USB Host Controller (This line will be selected.) 13. Select Properties from the pull-down menu. 14. Click on the Driver tab. 15. Click on the Update Driver button. 16. Windows Server* 2003 will launch the Upgrade Device Driver Wizard. Select Next. 17. Ensure that the following choice is selected: Search for a suitable driver for my device (recommended) 18. Insert the floppy containing the Windows Server* 2003 INF files into the floppy drive. 19. Select Next. 20. Windows Server* 2003 will list locations from where the updated driver file can be found. Ensure that the following choice is selected: Floppy disk drives 21. Select Next. 22. Windows 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 prompted 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 Installation 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 Installation Utility, the USB keyboard and mouse will stop functioning. This problem only occurs when using Windows XP with SP1 or Windows 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 provided by Microsoft in Knowledge Base article(822603). For additional information, please refer to the KB article located at http://support.microsoft.com/default.aspx?scid=kb;[LN];822603 Please use the following installation procedures: - Windows XP installed with SP1 - QFE (822603) installed - Latest Chipset Utility Software installed. Solution2: The command line flag "-Skip " can be used with the Intel(R) Chipset Software Installation Utility program to cause the USB2 driver not to be installed. The DevID's for ICH4/ICH5 are 24CD/24DD. This will cause the USB2 controller to have a yellow exclamation point in Device Manager (Usually located under Other Devices and identified as "Universal Serial Bus (USB) Controller"). To install the USB2 driver right-click this entry, select update driver, and allow the system to install automatically. 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 several possible system issues. In the event of system lockup, reboot the machine and view Device Manager. If devices are listed properly and the system experiences no further problems, then the .INF file restore process was successful. If devices are not configured correctly, try re-running the procedures outlined in Section 3. If this does not fix the issue or further issues are experienced, reinstall the operating system. Issue: After running the setup program and rebooting the machine, Windows reports that it cannot find one of the following files: ESDI_506.pdr Solution: Click Browse in the dialog box where this issue occurs, locate the \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 program and rebooting the machine, Windows reports that it cannot find one of the following files: UHCD.SYS USBD.SYS USBHUB.SYS Solution: Click Browse in the dialog box where this issue occurs and locate the following directory: \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 program and rebooting the machine, Windows reports that it cannot find the following file: ISAPNP.VXD Solution: Click Browse in the dialog box where this issue occurs and locate the \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 install, the HKLM\Software\Intel\InfInst key was not created or the data of the value "install" is not "success". Solution: This is caused by one of the following 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 provided in connection with Intel(R) products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty relating to sale and/or use of Intel(R) products, including liability or warranties relating to fitness for a particular purpose, merchantability or infringement of any patent, copyright or other intellectual property right. Intel(R) products are not intended for use in medical, life saving, or life-sustaining applications. ************************************************************ Intel Corporation disclaims all 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 property of their respective owners. Copyright (c) Intel Corporation, 1997-2005
1 , TaskBar_v0.5.zip"Form_Taskbar is a control for Visual Basic which, once placed onto a form, makes the form act like the Taskbar (minus the Start Menu)." -- David Newcum2 , RemBuilderplus.zip"Rem Builder will auto load on startup to use Rem Builder; start your Visual Basic program with your project code showing, right click and you should see "Rem Builder".3 , syntax.zipThis is an excellent example of how to highlight HTML code in a rich textbox. I encourage everyone to check it out.4 , status.zipThis example demonstrates how to display text about each control the mouse is currently above.5 , dm10e.zipThis COM object allows you to send SMTP mail from many of the most used applications, including:Active Server Pages (Microsoft IIS or Chili!ASP extensions) Microsoft Visual Basic 4.x/5.x/6.x Microsoft Word, Access, Excel 95/97 (VBA) Windows Scripting Host (cscript / wscript) Perl 5.x for Win32 Inprise Delphi 4 Microsoft Visual C++ 4.x/5.x/6.x Microsoft Visual J++ 1.x/6.0 (Java) 6 , ocxex.zip"This is a quick example I made to show you how to use Events and properties in a OCX."7 , news.exeThis control aids as a complete Newsgroup control. It can post messages and recieve messages through the internet.8 , optiondemo.zipThis example demonstrates how to create realistic Option Buttons in Visual Basic.9 , mencrypt.zipThis ocx allows you to encrypt strings while utilizing a password shift method.10 , listtxt.zipThis shows how to retrieve the text from the current selection in a listbox.11 , list_index.zipThis example tells you if the inputted List Index is selected or not.12 , fade.zipThis is a bas to fade a pictuerbox. Can be used to make a progressbar13 , subcls32.zipThis demonstrates hoe to write a subclassing control. And it has many examples as to how to use the control (included.)14 , djmeter.zipThis is the source for a Progress Bar control. Also includes a helpful example.15 , progress.zipThis is an example on how to use the Progress Bar included with Microsoft's Visual Basic.16 , slider.zip"This is a sample of the Slider control that is part of the Microsoft Windows Common Controls(COMCTL32.OCX). "17 , statusbar.zip"This is a sample of the StatusBar control that is part of the Microsoft Windows Common Controls(COMCTL32.OCX). "18 , tabstrip.zip"This is a sample of the TabStrip control that is part of the Microsoft Windows Common Controls(COMCTL32.OCX). "19 , uncommondialog.zipThis is an alternative to Microsoft's (tm) Common Dialog control by Nick Mancini.20 , ucmdex.zipThis is the example to go with Uncommon Dialog OCX.21 , scroll.zipThis demonstrates how to create an auto-scrolling textbox.22 , splitter.zipThis demonstrates how to "split" controls. This is an excellent example, and I reccomend this file for everyone. 23 , mtymse.zip"This project is a fully working ActiveX control, with code, that allows you to control almost every aspect of the mouse. You can move the mouse, click the buttons and adjust the click time from your application."24 , ucmdsrc.zipThis is the source to my OCX. This demontrates how to create a basic OCX. This will aid anyone who wants to create an OCX.25 , avb-systray.zipThis is a good example to add your programs' icon to the Systray. This Zip also includes a helpful example.26 , cmdex.zipThis is an example of how to use the Common Dialog. This demonstrates most of the event procedures of the CM Dialog control.27 , campbell-reg.zipThis demonstrates how to write and retrieve information from the registry.28 , basChangeCursor.zipThis module demonstrates how to animate your cursor through Visual Basic, and Win32.29 , hdcat.zipThis will grab every file on your hard drive and add its path to a listbox.30 , vbo_bump.zipThis DLL allows programmers to easily draw 3D grippers and lines on Device Contexts (DC). 31 , vbo_user32_bas.zipThis BAS file contains many functions to ease the process of using the USER32 DLL. 32 , vbo_gdi32_bas.zipThis BAS File conatains many functions to ease the process of using the GDI32 DLL. 33 , vbo_button_bas.zipThis bas contains functions to manipulate Button class objects34 , LPT_Port.zipRead/write to LPT parallel port35 , DancingBaby.zipA Dancing Baby Screen Saver Which Dance on A Famous Song Macarena ( With Sound ) A Very Cute Screen Saver ,with source code, If you want more avi files then please mail me.36 , superwriter.zipA complete Wordprocessor, with source code. You can save, open files, print them out, copy, cut, paste, well you know the concept!37 , LogOff.zipThis conveniently placed program allows you to log off from your system tray.38 , ChPass.zipChanges NT Domain Passord. This program has two compenants... a server and a a client. The Server must run on a Domain Controller.39 , Reboot.zipThis conveniently placed program allows you to restart your computer more easily, from your system tray. 40 , analogclock.zipThis is a very good demo OCX for an analog clock. Although quite big in size, this is due to the very good background to the clock face. The analog click itself is very accurate and looks very impressive.41 , edge.zipThis program uses a few API calls/functions to set 3D, sunken and etched effects to an image inside an image control. It also has an example of how to change a label control to a 3D command button.42 , splitpanel2.zipA re-written version of the SplitPanel that David originally put onto this site about a year ago. It basically is a control that you place on a form and you can put other controls on the form and by dragging the splitpanel bar around, it does the resizing for you. 43 , avcontrol.zipThis control takes care of many audio and visual functions needed for game and graphical programmers. You can easily retrieve or change the screen resolution and color depth, play audio CDs and standard wave files 44 , fsocontrol.zipThis demonstration version of this control is a wrapper around the FileSystemObject - and makes using the FSO much easier.45 , slidingtoolbar.zipThis project shows how to implement a sliding toolbar in an application using one quick Kernel32 API function "Sleep". The application is fairly simple and easy to implement. 46 , dcsize.zipWhen this control is put onto a form, it ensures that all other controls retain the correct aspect-ratio from the design time view. Basically, it resize all controls on a form when the form resizes. This code is 100% free.47 , colorchooseocx.zipThis great OCX allows you to have a drop down list of colors to allow your user to choose from. The control itself has all the events and properties that you need.48 , xgraphmeter.zipThis is XGraphMeter, a bargraph/meter control good for displaying constantly changing values such as CPU usage or DUN throughput.49 , dynlistmnu.zipWhile trying to come up with a Dynamic menu in VB, I decided that VBs menu object was just too much of a pain to work with This project contains a form to mimic the functionality that I was looking for.. Part of my design criteria was that the menu form 50 , runtime.zipSupposedly, what this code does cannot be done... But it works. Basically, its a demonstration of how you can change control properties at run-time. If you try it in VB, you will get a runtime error, but this code shows you how to do it. Gilbert says51 , ledbulb.zipThis is a first for this author. Its an OCX which represents a characters in the form of led bulbs.52 , textapiroutines.basContained here is a small set of routines can be used with a Rich Text box (RTF) control. It can be used for other controls as well with minor modifications. You are welcome to change, use and distribute the code as you see fit.53 , xflatbutton.zipFlatButton is an owner-drawn flat button that pops up when the mouse passes over it. This version is text-only, but has flexible color support.54 , urllabel.zipWith the development of the internet and intranet applications, this control could could in more and more useful. Its a hyperlink label which will change color or underline when the mouse goes over it 55 , progbar.zipThis is a great replacement for the standard VB progress bar. Its smooth, totally free (all the source code is here), and more versitile than the one that comes with VB.56 , splitpanel.zipThis little control with full source code is remarkably compact but does a lot of fancy things. It allows you to be able to split panels and handles all the resizing behind it. We couldn't think of how to describe it properly, but 下载 it and try it57,basicreg.zipBasic Save and Retrieve Functions58,proguse.zipKeep Track of a Programs Usage59,millisec.zipCount Time in Milliseconds 60,getday.zipGet the Day of Week that a Day Falls On61,shellend.zipNotify the User when a Shelled Process Ends 62,varlist.zipGet a List of Windows Variables 63,detdisp.zipDetermine Display Colors 64,ctrlntwk.zipControl Panel - Network65,ctrluser.zipControl Panel - User Properties66,ctrltwui.zipControl Panel - TweakUI67,ctrlthm.zipControl Panel - Themes68,ctrltele.zipControl Panel - Telephony69,ctrlsys.zipControl Panel - System Properties70,ctrlscrn.zipControl Panel - Screen Savers71,ctrlreg.zipControl Panel - Regional Settings72,ctrlprnt.zipControl Panel - Printers73,ctrlpwr.zipControl Panel - Power Management74,ctrlpw.zipControl Panel - Passwords75,ctrlodbc.zipControl Panel - ODBC3276,ctrlmm.zipControl Panel - Multimedia77,ctrlmdm.zipControl Panel - Modem78,ctrlkbd.zipControl Panel - Keyboard79,ctrlmous.zipControl Panel - Mouse80,ctrlpoa.zipControl Panel - Post Office Admin81,ctrlotlk.zipControl Panel - Outlook82,ctrljoy.zipControl Panel - Joystick83,ctrlie4.zipControl Panel - Internet Explorer 84,ctrlgame.zipControl Panel - Game Controllers85,ctrlfont.zipControl Panel - Fonts86,ctrlarmp.zip Control Panel - Add/Remove Programs87,ctrlanh.zipControl Panel - Add New Hardware88,ctrlanp.zipControl Panel - Add New Printer89,ctrlaccs.zipControl Panel - Accessibility90,ctrlbrf.zipControl Panel - Create Briefcase91,ctrlcdsk.zipControl Panel - Copy Disk92,ctrlcns.zipControl Panel - Create New Shortcut93,ctrldun.zipControl Panel - Dial-Up Networking94,ctrldisp.zipControl Panel - Display Properties95,RegControl.zipFree Registry ActiveX Control. Read/Write String/Binary/DWord values, Check if key/value exists, CreateKey, Delete key/value and enumerate keys/values!96,MouseEvent.zipThis is a Mouse Event procedure that is pretty cool. It can be used for Web designing. Check it out!97,ShellTrayIcon.zipThe CShellTrayIcon class allows your VB application to set, change and delete icons in the system's tray 98,Reboot2.zipReboot remotely. I wrote this to reboot selected PC's during off hours. It is a standalone application that will display a 10 second countdown. Any open data will try to be saved prior to the shutdown process.99,S-Secure.zipThis is S-Secure.....a security program I've coded for Windows. It has 4 modules each in a separate VB project. 100,DriveSpace.zipThis Program finds and displays the Drive's Space.101,Disable_X.zipThis user control allows you to disable the windows close "X" button. Example program included.102,SetParnt.zipShows how to assign controls to different forms at run time. 103,phone.zipA Cellular Phone Application Uses MSCOMM, Modem and normal telephone lines to make calls. You can use this application to make local as well as International calls. 104,Timer01.zipSimple program demonstrating how to create a stop watch using the Timer control. 105,Bubblesort.zipA simple Bubble Sort code that shows how the program works within a VB program. 106,systray.zipJust another Systray Utility, but worse than the others !!! static, flashing and animated Tray-Icons 107,FolderFiles.zipDemonstrates usage of progress bar and list box controls. Its purpose is to get all the files from a specified folder while showing the progress completed. 108,MultipleDataSets.zipThis is a simple, (1) form VB 6.0 program which demonstrates how to plot multiple sets of data on the same graph using the MSChart Control 6.0 (OLEDB). 109,MthVwPrj.zipMonthView control. Lets users view and set date information via a calendar-like interface. 110,calculator4.zipI know this is wierd but I made a calculator control. Just add it to your control bar, double click, and you can use the calculator when your project is at run-time. Source included.111,GradientButton.zipThis button was created to be an enhanced replacement for Visual Basic's standard command button by adding 2 more Border appearance schemes, 2 more button styles, and hover effects. 112,MSChart.zipMSChart. You can view MSChart in Line graph,Pie , Area, etc.. also you can update data provided in the Grid.. Very interesting must see it... 113,printing_tut.zipI made this for a freind to help him out with some basic Printing, i got the idea from a printing tut i found on the net, so the code is not mine. 114,treeview.zipThis code can as many child nodes to a tree view control and can save the data and structure of the treeview control in a text file. Later the data and structure can be retrieved from the text file and filled in the tree view control by clicking the load button. 115,alarm_clock.zipIt simulates an alarm clock. 116,DesktopByAlexDrankus.zipThis program hides/shows desktop, hides/shows taskbar, hides it self from the ctrl+alt+delete, uses pictures to create the forms (pretty cool forms) and many other functions just place this program and all components in a sub-folder 117,Label3D.zipLabel3D lets you change the Label Face Color Shadow Color ON/OFF Shadow. 118,HotLinks.zip Custom Control which acts like a text box, except the developer can specify hot links in the control which act like web page links allowing users to click them, while allowing the developer full control over the result of the click. 119,custbutt.zipThis application shows how to create non rectangular buttons. 120,grid.zipComplete grid coded in vb. supports : locked rows/columns , fg/bg colors , text alignment , cell-edge styles , different selectionstyles . texbox/dropdown cells , cell icons and lots more... 121,analogmeter.zipCreate your own analog meters using MSPaint. These .bmp or .gif files become your meter face. Use the (analogmeter) subroutine to automatically draw the meter needle over the meter face 122,wheel.zipSpinWheel control to be used in place of either the UpDown control or the ScrollBar control.123,ArielBrowseFolder.zipA browse folder control resembling a combobox. When the dropdown button is clicked, browse through a folder treeview to select a directory. Uses the SHBrowseForFolder function, amongst other APIs. A call back procedure is implemented showing the currently selected folder in the browse for folder dialog. 124,pp_prj.zipThis program shows you how to create a sample project that adds print preview capabilities to your Visual Basic program by using a generic object and the Printer object. 125,popup.zipPopUp buttons with only 4 lines of code. 126,adbevel.zipThe bevel control in Delphi is now available in VB. 127,rainbow.zipCool! Have a ProgressBar like in InstallShield!With free selectable fore- and backcolor and the percent value displayed in the middle!Check it out.128,gb12.zipWell folks. Another version of Gold Button is here. I've added a few things. Here they are: Property descriptions, MaskColor, UseMask, Base Address in OCX, picture will now automatically align with text and when you are in desing mode and OnUp property is bsNone, a Dash-Dot-Dot box is drawn over the button, so you can see th button's area. 129,gb11.zipA new version of Gold Button is here dudes.New version has Picture Property and Skin Support. 130,BIGDOGMEDIA.zipMEDIA PLAYER THAT SUPPORTS FORMATS LIKE MP3,AVI,MPEG,WAV ECT.EXAMPLE OF USING ANIMATION WHEN PLAYER IS LAUNCHED. 131,HTML.zipAn HTML editor with complete VB source code. 132,PrintPreview1.zipPrint Setup, and Print Priview application. 133,RTFEditor.zipRTF text editor, HTML text editor, web browser, and more...Try it. Note, make sure your printer is turned on before running the application. 134,VBExplorer-II.zipVBExplorer file utility application. This application uses the Visual Basic TreeView and ListView controls to create a file management application similar to Windows Explorer.135,resizepic.zipShows how to resize a picture box control on a form at run time.

4,164

社区成员

发帖
与我相关
我的任务
社区描述
Windows专区 一般软件使用
社区管理员
  • 一般软件使用社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧