Jump to content

comecme

Member
  • Posts

    7
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

About comecme

  • Birthday 03/23/1969

Contact Methods

  • Website URL
    http://

comecme's Achievements

0

Reputation

  1. What do you mean? I am installing the WUA via SvcPack without problems. Or at least that's what I thought. Where did you see it doesn't install in your case? And about direct integration. Are you sure that should be possible? AFAIK this installer doesn't support the /Integrate option.
  2. comecme

    MISE70 MUI Pack

    I'm using a Win XP SP2 Enu VLK with integrated MSIE70 using nLite. After installing the OS, I install the XP MUI. After that, Windows Update show me the Windows Internet Explorer 7.0 MUI Pack in Optional Software. I've downloaded it and was surprised to see that it supports the /Integrate switch. I don't really see how this could be usefull for two reasons: IE70 can't be slipstreamed (not officially that is) XP MUI Pack can't be slipstreamed So what could you integrate the MSIE70 MUI Pack in to?
  3. Anybody here who can successfully run SFC /ScanNow? If I run it (while no CD present) I get a lot of files that SFC wants to replace. Even if I put in the CD and let SFC replace everything, a new run will want to replace the files all over again. I've seen this both with XP SP1 and XP SP2, both with a Dutch and a US version.
  4. It appears that this behaviour also occurs with my base XP SP2 CD and even with my XP SP1 CD. In both cases, running SFC /ScanNow without the CD present will show that it's trying to repair a lot of files. Unfortunately I don't have any original CD (no SP) present, so I can't try what happens with that version. I wonder if there are some errors in my SP1/SP2 image. Or does this SFC stuff not work like it should at all?
  5. WFP/SFC problem still exists I'm not sure if you want to know if we still experience the SFC popup problem. Like you mentioned on the homepage, MSIE70 integration seems to cause the problem. I've seen the problem both with the original IE7 as with the new version. With the old IE7 I've had the problem both on an English and a Dutch XP Pro version. The new IE7 I've only tried so far on XP Pro English. Not only do I get the popup when I insert a USB Stick, I also get it when I run the Microsoft Baseline Security Analyzer. When I run MBSA on a XP setup with slipstreamed MSIE70 (no other hotfixes), the Windows File Protection pops up. But off course, it might just be that the popup is right in this case. It seems like MBSA starts with a download of a new version of the Windows Update Agent. Edit: I only get the SFC popup once. If I connect a USB stick first, I don't get the popup when running MBSA. And if I run MBSA first, I don't get the popup when connecting a USB stick. Edit2: If I insert a USB stick and supply my machine with an XP CD, the SetupApi.log shows: [2007/10/17 00:32:29 640.7] #-199 Executing "\??\C:\WINDOWS\system32\winlogon.exe" with command line: winlogon.exe #E197 Writing "C:\WINDOWS\inf\syssetup.inf" to "C:\WINDOWS\INF" is not an approved method of installing INF files. Use a 'CopyINF' entry instead. #W187 Install failed, attempting to restore original files. If I insert the USB stick and don't supply the machine with an XP CD, it shows: [2007/10/17 00:50:41 640.7] #-199 Executing "\??\C:\WINDOWS\system32\winlogon.exe" with command line: winlogon.exe #-167 SPFILENOTIFY_NEEDMEDIA: Tag = "\win51ip.sp2", Description= "Windows XP Professional Service Pack 2 CD", SourcePath = "D:\i386", SourceFile = "syssetup.inf", Flags = 0x00000000. #E169 SPFILENOTIFY_NEEDMEDIA: returned FILEOP_ABORT. Error 1223: The operation was canceled by the user. #W187 Install failed, attempting to restore original files. Another way to show there's something wrong would be to run SFC /ScanNow wihtout the CD present. This results in a lot of messages in setupapi.log (attached). It seems to me that all those files are indeed MSIE70 related. It looks like the MSIE70 files are integrated into the CD, but SFC/WFP doesn't know yet that those files are the correct ones. Even if I run SFC /ScanNow with the CD present, things don't get fixed. If I run SFC /ScanNow again later, without the CD present, it wants to repair a lot of files again. So to me it definitely seems like Windows doesn't accept the integrated MSIE70 files as "official microsoft files". SetupApi.log.txt
  6. Solved! For some reason, when no [GUIUnattended] section is present, the Welcome screen gets suppressed. But when you do add [GUIUnattended], you must specify OEMSkipWelcome=1 to achieve the same result. So, the complete WinNt.SIF becomes [Data] AutoPartition=0 MsDosInitiated=0 UnattendedInstall=Yes [Unattended] UnattendSwitch=Yes OEMSkipEULA=Yes OEMPreinstall=Yes [UserData] ProductID=xxxxx-xxxxx-xxxx-xxxx-xxxx [GuiUnattended] OEMSkipRegional=0 OEMSkipWelcome=1
  7. I want my WinNt.SIF to do just a few things. It only contains the following: [Data] AutoPartition=0 MsDosInitiated=0 UnattendedInstall=Yes [Unattended] UnattendSwitch=Yes OEMSkipEULA=Yes [UserData] ProductID=xxxxx-xxxxx-xxxx-xxxx-xxxxThis does the following: skip the Welcome page, Regional Settings, Network Settings and the Windows Welcome (OOBE). So what i DO get is the name/organization screen, computer name and admin password, TimeZone, Domain/Workgroup. I must say that I don't really know why all the other screens get skipped. I don't supply info for any of the screens after all, so why do they get skipped? However, there is one screen that I would like to have during setup. That's the Regional Settings screen. I've tried adding [GuiUnattended] OEMSkipRegional=0but when I do, the Welcome Page suddenly re-appears.
×
×
  • Create New...