Kurt_Aust

Just to clarify: 1. I have no issues with the RST management application once installed, the problems I have pointed out only apply to the actual act of installing the program. 2. These limitations compared to previous versions of the installer will not be limited to XP only, they will also apply to Vista and Win 7.

I'm not seeking to integrate it exactly, rather I'm seeking to script it for silent install along with all my other applications on subsequent reboot passes once the OS has been installed. I'm using RAID 10, so there is some benefit and as I only reboot about once a week or less, slightly longer startup time is not really an issue. Still, none of this changes the fact that Intel did a poor job on the installer.

Actually, the Setup.iss file for v9.5.6.1001 is still useless, here's its contents: [InstallShield Silent] Version=v7.00 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{9068B2BE-D93A-4C0A-861C-5E35E2C0E09E}-DlgOrder] Count=0 And here's an example of what a response file should look like (from PowerDVD5): [InstallShield Silent] Version=v6.00.000 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [Application] Name=PowerDVD Version=5.0 Company=CyberLink Lang=0009 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-DlgOrder] Dlg0={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdWelcome-0 Count=10 Dlg1={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdLicense-0 Dlg2={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdDisplayTopics-0 Dlg3={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdRegisterUserEx-0 Dlg4={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdAskDestPath-0 Dlg5={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdSelectFolder-0 Dlg6={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SELECTSKINDIALOG-0 Dlg7={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SHOW_CLPV_CLEV_DIALOG-1 Dlg8={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdFinish-0 Dlg9={6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-AskYesNo-0 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdWelcome-0] Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdLicense-0] Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdDisplayTopics-0] Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdRegisterUserEx-0] szName=Kermit the Frog szCompany=The Muppet Show szSerial=Dream on Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdAskDestPath-0] szDir=C:\Program Files (x86)\CyberLink\PowerDVD Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdSelectFolder-0] szFolder=CyberLink PowerDVD Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SELECTSKINDIALOG-0] DefaultSkin=Glow Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SHOW_CLPV_CLEV_DIALOG-1] Result=1 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-SdFinish-0] Result=1 bOpt1=0 bOpt2=0 [{6811CAA0-BF12-11D4-9EA1-0050BAE317E1}-AskYesNo-0] Result=0

I took the opportunity to do a quick (partially) automated install and the latest drivers do seem to work on real hardware, mind you I still find it strange that integrating the textmode driver will BSOD VM's when the previous version had no such problem. I remain most unimpressed with the installer for the management console however: 1). As I noted before, it tries to extract itself to the current drive rather than the system temp folder, so if you are running it off a CD the installation will fail. 2). Even if you are running the installer on a hard drive, you can't do a silent install (/S). The "setup.iss" response file is there, but it's empty.

I burnt a copy of the image that BSOD'd in the various VMs, on real hardware it got through to detecting the hard drives, but I didn't proceed any further. Rather strange that the drivers should explode a VM when after all, they shouldn't even be loaded as the HWID's won't match.

Well so far I've only tested it in a VM, either Sun VirtualBox or VMware Server, both of which result in BSOD. As the machine it would be loaded onto is my main production machine I'm sure you can understand that I can't afford to risk using unstable drivers. So for now it looks like I will continue to use the older 8.9.0.1023 textmode drivers.

I've just done a test with the beta versions, they also fail. And here's a not so happy snappy of the error under Sun VirtualBox (same under VMware Server): I've also tried integrating only the \64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_10R driver but still get the same result.

Well I can't say I'm impressed with these latest drivers from Intel, integrating the latest 9.5.0.1037 textmode drivers in XP x64 gives me a BSOD just before the installer detects hard drives: [Drivers] D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_5 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_5_1 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_5_1_1 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_ESB2 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaStor_ESB2 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_10DDO D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_10R D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_7MMDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaStor_7MDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_7RDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaStor_7RDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaStor_8ME9ME5 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_8MEM D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_8RDHDO D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaStor_8R9R10RDO5 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_9MEM D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v9.5.0.1037 WHQL\iaAHCI.inf,iaAHCI_9RDODH D:\Operating_Systems\Drivers\EP45\2_Chipset_infinst911autol\All\2008s4el.inf,0 D:\Operating_Systems\Drivers\EP45\3_Audio_WDM_R241\WDM\HDA.inf,0 D:\Operating_Systems\Drivers\EP45\4_LAN_Driver_XP_5742_01202010\Netrtle.inf,0 D:\Operating_Systems\Drivers\EP45\5_Video_Driver_8-12\Driver\XP6A_INF\CA_72273.inf,0 Using the exact same setting with the older 8.9.0.1023 textmode drivers results in no problems: [Drivers] D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_ESB2 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaStor_ESB2 D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_10DDO D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_10R D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_7MMDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaStor_7MDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_7RDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaStor_7RDH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaStor_8ME9MEPCHM D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_8MEM D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_8RDHDO D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaStor_8R9R10RDOPCH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_9MEM D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_9RDODH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_PCH D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_PCHM D:\Operating_Systems\Drivers\EP45\1_64bit_Intel_textmode_driver_v8.9.0.1023_WHQL\iaAHCI.inf,iaAHCI_PCHM_1 D:\Operating_Systems\Drivers\EP45\2_Chipset_infinst911autol\All\2008s4el.inf,0 D:\Operating_Systems\Drivers\EP45\3_Audio_WDM_R241\WDM\HDA.inf,0 D:\Operating_Systems\Drivers\EP45\4_LAN_Driver_XP_5742_01202010\Netrtle.inf,0 D:\Operating_Systems\Drivers\EP45\5_Video_Driver_8-12\Driver\XP6A_INF\CA_72273.inf,0 Also one used to be able to script the install of the management console from the CD as shown IATA89ENU.exe /S However using the /S switch with the latest installer (STOR_allOS_9.5.0.1037_PV.exe) from the CD will result in failure as it tries to extract itself to its current directory (the CD) rather than the system temp folder.

TweakUI is not a hotfix and hence can't be integrated, 7-Zip is used to extract it to %SystemRoot% as noted in it's description "there are no silent install switches". All items in the \RunOnce and \AddOns folders (with the possible exception of Windows Search 4.0 and it's hotfix) can't be integrated, if they could they would be in the \Hotfix folder. Strel is correct in assuming that it is T-13 AddOns that give problems, the programs themselves install, but their related file associations are not registered, hence if the program doesn't have file associations there should be no problem using a T-13 AddOn. The batch file approach used in this guide allows an easy way to install such programs on first or subsequent logons and allows the end user to add their own programs to the install with relative ease. Also it means they don't have to wait for someone to repackage an updated version into an AddOn.

My list of WMP11 updates are those that are offered by Windows update, a far more conservative list than Boooggy's. For one thing my lists of updates will only ever include those items freely available on the Windows download site, they won't include hotfixes that you have to specifically request from Microsoft.

Post 1 answers: 1. Yes, they are included in 5eraph's pack. 2. You won't be bugged by Windows Update for the others (.Net 3.5 will show as an optional). 3. 5eraph's pack doesn't include Visual C++ 2008, so some other program on your system must have installed it. Still as a general rule you should apply all fixes. 4. nLite can't integrate these items, they must be silently installed. Post 7: Visual C++ 2008 is NOT cumulative with Visual C++ 2005. For some insane reason they both have the same filename on the MS download site so to make it easier for those who download everything themselves I've only scripted the install for VC05, mainly because I've never come across a program that requires VC08.

January update Deletion: Hotfix\894-Windows2000-KB961371-V2-x86-ENU.exe Addition: Hotfix\946-Windows2000-KB972270-x86-ENU.exe 581,872 However I won't be updating the archive for this one pis-ant little change.

January update Deletion: Hotfix\260-WindowsServer2003.WindowsXP-KB961371-v2-x64-ENU.exe Addition: @ Hotfix\352-WindowsServer2003.WindowsXP-KB972270-x64-ENU.exe 868,720 MS10-001 - Embedded OpenType Font Engine Unfortunately MediaFire is giving me trouble uploading the updated archive, but rather than waiting for goodness knows how long before I can get it up (insert snide comment here), I'll just note that the one updated hotfix is less than a megabyte and doesn't require a reboot.

There's no point deleting the files, they're less than half a meg and don't use system resources, besides there are times where even Administrators are unable to access files and you can then use the utility to grant yourself access (the leftover .Net 3.5 setup folder for instance).

Actually no, the survey is asking "Did you create your 64-bit XP install disk on a 32-bit XP system?". You'll need a completely different hotfix list to create a 32-bit XP install disk. One can create W2K, XP-32 & XP-64 install disks on 64-bit XP without problems.

To the best of my knowledge nobody has written such a guide and I don't have the time to do so, also as I don't use 32-bit XP I couldn't test it properly.That being said, the concepts used in the guide are transferable to 32-bit XP with one important change. Specifically that the TimeOut command does NOT exist on 32-bit XP systems so you have to replace TimeOut /T xwith (20>21, not 20>20+1) Ping -n x+1 127.0.0.1 > nulwhere x is the delay in seconds.

Well the thing is until you try a disk with just the driver integrated, we can't be sure it's the problem and hence we could be spending all our time barking up the wrong tree. Also I've had cases where I've loaded Last_Session.ini files posted by others and they prove to be a disaster (BSOD on install), but they work if I enter the values manually. P.S. I'll be out of contact for the next couple of days.

Just looking at your last session file, you seem to have yanked a fair bit out of the OS. Have you tried it without removing any components?

Possible updated INF utility (no .zip file as yet): http://downloadcenter.intel.com/Detail_Des...16〈=eng

I don't know about XP x32 sp3 (don't have any systems running it), but I can tell you the list of supported operating systems detailed on the download page is not accurate, because KB973686 works on Windows 2000 systems and Windows update will prompt for it if you have an older version of MSXML6sp2 installed.

December updates Deletions: Hotfix\036-Windows2000-KB911280-v2-x86-ENU.exe (users of older 5.1.2195.21 version of SP5 only) Hotfix\450-Windows2000-KB945553-x86-ENU.exe Hotfix\520-Windows2000-KB951748-x86-ENU.exe Hotfix\680-msxml6-KB954459-enu-x86.exe Hotfix\914-IE6.0sp1-KB974455-Windows2000-x86-ENU.exe Hotfix\932-IE6.0sp1-KB976749-Windows2000-x86-ENU.exe RunOnce\msxml.msi RunOnce\Windows2000-DirectX9-KB971633-x86-ENU.exe Additions: Hotfix\932-IE6.0sp1-KB976325-Windows2000-x86-ENU.exe 4,238,728 Hotfix\934-Windows2000-KB951748-V2-x86-ENU.exe 856,816 Hotfix\936-Windows2000-KB974318-x86-ENU.exe 558,320 Hotfix\938-Windows2000-KB974392-x86-ENU.exe 930,544 Hotfix\940-Windows2000-KB955759-x86-ENU.exe 689,912 Hotfix\942-msxml4-KB973685-enu.exe 2,046,296 Optional, Microsoft XML Core Services 4 sp3 Hotfix\944-msxml6-KB973686-enu-x86.exe 956,248 Optional, Microsoft XML Core Services 6 sp2 RunOnce\Windows2000-DirectX9-KB976138-x86-ENU.exe 1,008,520 RunOnce\Windows2000-KB973904-x86-ENU.exe 880,888 Replacements: RunOnce\install_flash_player_ax.exe 1,956,528 Optional, Adobe Flash ActiveX control for I.E. updated 8 Dec RunOnce\WindowsUpdateAgent30-x86.exe 6,776,168 Updated (in this guide) 8 Dec Targaff, are you sure that the High Encryption pack is still applicable? It predates SP1 and over the years restrictions on encryption technology have been relaxed, for instance IE6 uses 128-bit encryption.

December updates Deletions: Hotfix\144-WindowsServer2003.WindowsXP-KB955069-x64-ENU.exe Hotfix\148-msxml6-KB954459-enu-amd64.exe Hotfix\256-WindowsServer2003.WindowsXP-KB970653-v3-x64-ENU.exe Hotfix\904-IE8-WindowsServer2003.WindowsXP-KB974455-x64-ENU.exe Hotfix\906-IE8-WindowsServer2003.WindowsXP-KB976749-x64-ENU.exe RunOnce\msxml.msi RunOnce\WindowsServer2003.WindowsXP-KB926139-v2-x64-ENU.exe Additions: @ . . . Hotfix\312-msxml4-KB973685-enu.exe .. . . . . . . . . . . . . . . . . . . . . . . . . . 2,046,296 Microsoft XML Core Services 4.0 SP3 @ . . . Hotfix\316-msxml6-KB973686-enu-amd64.exe .. . . . . . . . . . . . . . . . . . . . 1,862,488 Microsoft XML Core Services 6.0 SP2 @ . . . Hotfix\320-WindowsServer2003.WindowsXP-KB973687-x64-ENU.exe .. . 2,775,408 Microsoft XML Core Services 3.0 @ . . . Hotfix\324-WindowsServer2003.WindowsXP-KB976098-v2-x64-ENU.exe .. 705,904 Time Zone - December 2009 - Cumulative @ . . . Hotfix\328-WindowsServer2003.WindowsXP-KB974318-x64-ENU.exe . . . . 891,248 MS09-071 - Internet Authentication Service @ . . . Hotfix\332-WindowsServer2003.WindowsXP-KB974392-x64-ENU.exe . . . . 950,128 MS09-069 - Local Security Authority Subsystem Service (LSASS) @ . . . Hotfix\336-WindowsServer2003.WindowsXP-KB955759-x64-ENU.exe .. . 1,272,192 Indeo Codec @ . . . Hotfix\340-WindowsServer2003.WindowsXP-KB973904-x64-ENU.exe .. . 1,721,728 MS09-073 - WordPad Text Converter @ . . . Hotfix\344-WindowsServer2003.WindowsXP-KB970430-x64-ENU.exe .. . 1,104,240 Extended Protection for Authentication - http.sys @ . . . Hotfix\348-WindowsServer2003.WindowsXP-KB971737-x64-ENU.exe .. . 1,054,080 Extended Protection for Authentication - WinHTTP # ▼ Hotfix\904-IE8-WindowsServer2003.WindowsXP-KB976325-x64-ENU.exe 39,470,464 MS09-072 - Cumulative Security Update # ▼ RunOnce\WindowsServer2003-KB968930-x64-ENG.exe 10,334,496 PowerShell 2.0 Replacements: # ▼ Hotfix\900-5er_IE8_Addon_2009-03_3_x64.7z 24,202,707 5eraph's Internet Explorer 8 AddOn, optional - the older versions still work fine @ . . . RunOnce\install_flash_player_ax.exe 1,956,528 Updated 8 Dec # ▼ RunOnce\WindowsUpdateAgent30-x64.exe 7,749,976 Updated (in this guide) 8 Dec .. . . . . RunOnce\WinUp.lnk When updating the security certificate, Microsoft forgot to include update.microsoft.com, doh! Actually, my main rig also uses the UAA HD audio driver (Realtek), rather strange they didn't include it in SP2. Mind you I get a vicious driver conflict (BSOD) if I try to install the audio drivers for the HDMI output on my video card (ATI/Realtek). It doesn't much like the manufacturer's .inf file for my monitor either (plug in mic, screen goes blank).

According to the documentation, the /q:a switch should work. If it did work then rsaenhs.dll should exist in your \system32 folder. As it doesn't interfere with anything else, it can go pretty much anywhere.

Here you are butting up against one of the design concepts behind the guide, being that minimal third party software shall be used in a default install, in fact the only 3rd party software included by default is Adobe flash. If you can point me to a utility inherent to the XP x64 install disk I'll use it, but otherwise the guide will be sticking with TimeOut commands. Naturally there is some slack in the time allowed (for safety purposes), but still in a standard 2 batch file pass install I doubt you could save more than 3 minutes.

Actually, that looks like an XP (32-bit) OEM CD's directory structure to me. John, I think you might be confusing yourself and Patosan by comparing to the base directory structure of an XP (64-bit) OEM CD, they do not have the same files and folders. On another note, that's a weird name for that particular hotfix, the English version is called: msxml6-KB954459-enu-x86.exe EDIT: Disregard the above line, there is a version for XP sp3 English that looks like yours.