Jump to content

GreenMachine

Developer
  • Content Count

    3,070
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About GreenMachine

  • Rank
    ineXPlicable

Contact Methods

  • Website URL
    http://greenmachine.msfnhosting.com/XPCREATE/

Profile Information

  • OS
    Server 2012R2

Recent Profile Visitors

2,253 profile views
  1. Just an update ... A few more updates than on the first post in this thread. Still the same problem with Windows Search, and it's subsequent update: "WindowsSearch-KB940157-XP-x86-enu.exe /Quiet /NoRestart" "WindowsServer2003.WindowsXP-KB963093-x86-ENU.exe /Quiet /NoRestart" Also WGA (KB905474) seems to now require interactive installation. After install, only KB940157 and KB905474 are listed as needed by Windows Update. SVCPACK.INF [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="\i386\svcpack" [SetupHotfixesToRun] "
  2. Following is my current version, taking into consideration last weeks patches. Still having the same problem with Windows Search 4, and I suspect that will not go away until either that issue is corrected in the software, or Windows Search no longer shows up in Windows Update. SVCPACK.INF [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="\i386\svcpack" [SetupHotfixesToRun] ; ---------- SVC-D1F Files ---------- "DotNet11.exe /Q:A /C:""INSTALL /Q""" ; ---------- SVC-D1U Files ---------- "NDP1.1SP1-KB867460-x86.exe /Q" "ND
  3. Following is my current version, taking into consideration last weeks patches. Still having the same problem with Windows Search 4, and I suspect that will not go away until either that issue is corrected in the software, or Windows Search no longer shows up in Windows Update (my prefered option ... ) I was also having problems with KB956391, until I realized that it needed to be installed AFTER IE7. [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="\i386\svcpack" [SetupHotfixesToRun] ; ---------- SVC-D1F Files ----------
  4. Typo indeed. TermService was intended. In any event the NET STOP/START commands are invalid for this service, even on an up and running XP. Obviously, i would prefer not to start a bunch of services. I was hoping for a little registry entry that either instructed the program to install anyway, or fooled it into thinking all the prerequisites had been met. Installing after the final reboot is a valid solution, but right now my efforts are concentrated on doing it from SVCPACK.INF. Any other ideas? Thanks!
  5. In the continued search for perfection, here is my latest, and not yet perfected, SVCPACK.INF. [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=1 BuildNumber=2600 [SetupData] CatalogSubDir="\i386\svcpack" [SetupHotfixesToRun] ; ---------- SVC-D1F Files ---------- "DotNet11.exe /Q:A /C:""INSTALL /Q""" ; ---------- SVC-D1U Files ---------- "NDP1.1SP1-KB867460-x86.exe /Q" "NDP1.1sp1-KB928366-X86.exe /Q" ; ---------- SVC-D2F Files ---------- "REG DELETE HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /F" "REG ADD HKLM\SYSTEM\Setup /V SystemSetupInProgress /T RE
  6. I am trying to install Windows Search (WindowsSearch-KB940157-XP-x86-ENU.exe) from SVCPACK.INF during Windows XP SP3 installation. The unattended command line, WindowsSearch-KB940157-XP-x86-ENU.exe /Q /NoRestart, works fine in an up and running XP installation. From SVCPACK.INF, the command silently fails: no error message and Windows Search NOT installed. The log file, KB940157, reads as such: 00:00.000: ======================================================================= 00:00.070: INFO: Opening log for preliminary WDSSetup.exe actions 00:00.070: Started: 2008/10/14 (Y/M/D) 01:00:00.000
  7. In the never ending search for the complete, up to date Windows XP Installation, here is my latest SVCPACK.INF, used to install all the updates and hotfixes for Windows XP Service Pack 3. This list of updates and hotfixes are those I have determined to be necessary to show Zero Updates needed, High Priority or Recommended, in Windows Update. One major obstacle is finding the hotfixes. I use a combination of standard hotfix downloads from Microsoft, inspection of WindowsUpdate.log for update URLs, and NirSoft's SmartSniff to detect from where the hotfixes are downloaded. Please do the same to f
  8. @Bitfrotter: Correct me if I am wrong, but your posts have led me to believe you are using XPCREATE in a commercial environment. Is that correct? I will not be updating this SVCPACK.INF any longer, as I have moved on to SP3.
  9. @giarc: Yes, this works on an attended install, as well as an unattended. You have the wrong switches, or the wrong update file for the hotfix that is prompting you for an extraction path. You could try a quiet installation, as opposed to an unattended installation, and then you should have more luck finding the culprit. To do so, change all the /Q /U /O /N /Z to /U /O /N /Z, and the /Q:A /R:N to /Q:U /R:N. Integration using the /integrate switch will result in a larger installation source, as the updates are still run as shown above, but unpacked files will then replace packed files in the i3
  10. I WAS missing something ... seems I skipped right over that response that said what I said. Must have come out of hibernation too early ...
  11. Personally ... I like the simple approach. "I would like to check in a cmd if a file was deleted or not ". I read that to mean that if it still exists, it was not deleted, no? Am I missing something here?
  12. @smilodn: This list is for XP Pro. Forgot to mention that ... @Yzöwl: I suspect that the SVC-IEU (IE Updates) files that did not install are due to not including the IE7 iexplore.ex_ in your I386 installation directory. WIthout this, the IE Updates will think that IE6 is installed, and not install. That is one of the "smoke and mirror" tricks I needed to use. @spitf1f3: Perhaps it will work for both Home and Pro: I never use nor test the Home version. It takes quite a while to install this way, but most of the time is for .Net, which is unavoidable unless you find a method to slipstream .Net (
  13. Yes, I do have it ... And you can find it, too! I assume you already looked in C:\Windows\WindowsUpdate.log. If you do not find it there, go to NirSoft (www.nirsoft.net), and download SmartSniff. Start SmartSniff, and let Windows Update download the file(s) in question. Now, examine the streams tracked by SmartSniff, and you will find the link(s)!
×
×
  • Create New...