BikinDutchman

It is part of xable's post SP2 package. If you do not want the whole deal you may be able to figure out how he did it.

I have no clue either, but one of the hotfixes that you routinely add for wireless is 917021 This is mostly a WPA2 fix, but if your access points are all WPA2 that may explain the observed behavior. I hope is helps. Otherwise you go the long and winding road of removing nLite options until it works.

HALs: see here. Sysprep: I never used it, no idea, sorry .

Do not even look at the information and warning messages. You can double-click the error events to get some more information. I reinstalled my desk PC 2/20/2008 with nLite, xable, boooggy, and a few more small things and, in the mean time, scored some 100 errors, most application hangs in syslog. It seems to me that most event errors are timing issues: PC is busy, a service thinks it is time to do something, does not get enough resources and freaks out. I cannot look in your event files, they are encoded. It seems to me nothing serious is going on but I am just guessing, it is you responsibily! -If something is really wrong you get loads of error events, every few seconds. Depending on what you install there may be more logging locations. PS I am not sure you know, but nLite is only for private use. However imho Nuhi should think about a license for professional use, maybe after SP3 with nLite reaching a certain level of stability.

I have seen eventlog errors on every computer I have installed with very clean installations. You need to look into the messages if it is something real. If they occur once in a while I would not bother.

I believe you do not need KB939653, ii is superseeded by 944533 The problem with the MSUpdate addon is caused by IE7 integration, I reported that alreasy and report again for all 3 windows versions. -I looks like there is nothing reinstalled, just a reinitialization.

You need to integrate kb938127 AND kb944533 to avoid them showing up under WUpdate There were problems with plugin.ocx and Xable with previous versions of nLite, I thought they fixed that in nLite version 1.4.1 what version do you have? -Also see my old post here. -I believe it is not good to ignore the plugin.ocx crash because it may lead to other problems. The Xable post SP2 update only integrates generic CRITICAL updates. You can get the WGAN from his addons page. -There maybe critical updates that are for specific computers such as the Intel minicode update (KB936357). Good luck

For WMP11 it is on Boooggy's http://web.clicknet.ro/boooggy/#hotfixes For IE7 I use KB938127 and KB944533, the latter supersedes KB942615. I am not aware of any others.

I found sometime ago that it helps to integrate something small (such as a monitor driver) and then integrate WMP11 with the SlipStreamer. The occurrence of these error messages also depends on the type of your install: -CD install (errors less likely to occur) -WinNT32 install (errors more to occur) Also I had quite some error messages with WinXP x65 and posted in Boooggy's topic.

Is a little off-topic bvg: how can you guess alper60's computer type Most modern PCs are ACPI+APIC uni-processor (UP) or multi-processor (MP) -ACPI is modern power management -APIC provides additional (virtual) interrupt vectors The default setting provides the most advanced configuration possible. You normally do not touch this unless you want to downgrade, for instance no ACPI, APIC -> PIC, MP -> UP -you downgrade if your experience certain problems, mostly with special hardware. -if this already drives you nuts, stay with the default setting and stop reading. Combining ACPI or not, APIC or PIC, and UP or MP gives you 8 possibilities of which 6 generics actually exist: -Standard PC: Non-ACPI, PIC, UP: Hal.dll -MPS Uniprocessor PC: Non-ACPI, APIC, UP: Halapic.dll -MPS Multiprocessor PC: Non-ACPI, APIC, MP: Halmps.dll -Advanced Configuration and Power Interface (ACPI) PC: ACPI, PIC, UP: Halacpi.dll -ACPI Uniprocessor PC: ACPI APIC, UP: Halaacpi.dll -ACPI Multiprocessor PC: ACPI APIC, MP: Halmacpi.dll The dll's are the hardware abstraction layer, installed early in the process. Well that was it for today kids, man this is

Hi Nuhi (and maybe Boooggy). If you have absolute nothing else to do you might want to look into this one: -I have both nLite and slipstreamer installed. I tried automatic integration of WMP11, and fixes with nLite into Windows 2003 (W2K3). -Well, of course, I got a bunch of messages saying that WMP11 and the fixes are not meant for W2K3. -Yet, as we all know, it is possible to integrate WMP11 into W2K3 with slipstreamer. Possible solutions: -Make an exception for WMP11 and all known fixes (should be doable). -Try to make an exception for all future fixes that are intended for WMP11 (much more difficult I guess). -Provide an advanced option that lets the user turn off the OS verification (should be doable but really, another option?)

Integrating WindowsServer2003-KB941569-x86-ENU.exe in WMP11 Hi Boooggy, I found another very unlikely way to cause some problems: -I used slipstreamer 99 to integrate WMP11 and all fixes into a Windows 2003 Standard installation folder I got the following in the message window: System.IO.FileNotFoundException: Could not find file 'I:\Win2003\i386\wmp11temp\Fixes\Update\Update.inf'. File name: 'I:\Win2003\i386\wmp11temp\Fixes\Update\Update.inf' at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks) at Epsilon.Text.Ini.SimpleIniEditor..ctor(String filename) at WMP11Slipstreamer.Backend.standardHotfixApply(String fixesFolder, Dictionary`2 hotfixFileDictionary) at WMP11Slipstreamer.Backend.ApplyFixes() at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings) Deleting "I:\Win2003\i386\wmp11temp"... Done! The source being modified has not been damaged. All changes have been successfully reverted. This problem disappeared when using WindowsXP-KB941569-x86-ENU.EXE instead of WindowsServer2003-KB941569-x86-ENU.exe:). Not exactly an urgent problem, but maybe something for the next release or something to point out for this oh so special KB941569.

GTO, look here.

Boogy, I did a WinNT32 install from a Windows XP x64 SP2 installation (copied from the CD and SP2 slipstreamed). That Windows XP x64 SP2 installation has always worked so far, also with IE7 and hotfixes integrated with nLite. The errors show up only recently after integration of WMP11. I tried several things but could not find the problem. I have a suspicion that it has to do with the WinNT32 installation. I had similar issues with that before. I will now go back to basics, fresh source and CD install, and report as soon as I am done with that. And this get boring but yet want to repeat: you do a great job for something so complicated .

Boooggy, I believe my WinXPx64 set is allright. I do not get these errors if I do not use the slipstreamer. Does that tell you anything?

x64: Setuperr.log errors: Boooggy: After integrating WMP11x64 with slip streamer 0.99i in a clean WinXPx64 SP2 I get loads of errors in Setuperr.log. I believe that did not happen with version 0.98i; can you put old versions back on the download location? I attach my Setuperr.log setuperr_log.txt

You need to look in the *.inf file and see what is needed (*.cat, *.sys, etc)

I have nLite 1.4.1 and Boooggy slipstreamer 0.99 installed. I tried to integrated WMP11 with all hotfixes, directly in a clean Windows XP x64 SP2. That means my list of nLite hotfixes contains: -wmp11-windowsxp-x64-enu.exe -windowsmedia11-kb928788-x64-intl.exe -WindowsMedia11-KB929399-v2-x64-INTL.exe -windowsmedia11-kb929773-x64-intl.exe -windowsmedia11-kb932390-x64-intl.exe -windowsmedia11-kb933547-x64-intl.exe -windowsmedia11-kb935551-x64-intl.exe -windowsmedia11-kb935552-x64-intl.exe -windowsmedia11-kb939209-x64-intl.exe -WindowsMedia11-KB939683-x64-ENU.exe -WindowsMedia11-KB941569-x64-ENU.exe -windowsmedia11-kb942264-x64-intl.exe -windowsmedia11-kb943335-x64-intl.exe -windowsmedia11-kb944110-x64-intl.exe -windowsmedia11-kb944882-x64-intl.exe During integration, nLite starts the slipstreamer, and that goes well. However integration of of the last five (941569, 942264, 943335, 944110, 944882) fails. I do not have any such problem with direct integration with the slipstreamer. Also all is well with WinXP and Win2003 x86. Your input is greatly appreciated as always

This might be related to boot problems. Do you have just one partition and is it active?

See my recent post and responses

Boooggy, Sorry to upset you, but I found that one already: It does not seem to be an update for WMP11 but instead for WinXP. -The filename of that update is "WindowsXP-KB941569-x86-ENU.EXE" I was confused to find: "WindowsMedia11-KB941569-x64-ENU.exe" for x64 -but not: "WindowsMedia11-KB941569-x86-ENU.exe" for x86 There are similar issues with filenames for updates to WinXP and IE7 and it does matter so I became a little cautious.

Hi Boooggy, What do I need to download for the KB941569 x86 version? I found the x64 version (WindowsMedia11-KB941569-x64-ENU.exe) but for x86 only updates for Windows XP, Server, Vista. Thanks for looking

Hi Boooggy, I did a fresh install and got KB941569 in MS Update. Is this anything for your hotfix list?

I forgot how it worked for Office XP but I remember it is pretty similar as for Office 2003: You can edit Office 2003\FILES\SETUP\SETUPPRO.INI and/or using command line arguments when actually executing SETUPPRO. I execute SETUPPRO /qn and use the modified SETUPPRO shown below. ; Microsoft Office SETUP.EXE settings file. [MSI] MSI=PRO11.MSI [Product] ProductCode={90110409-6000-11D3-8CFE-0150048383C9} ProductName=Microsoft Office 2003 ProductVersion=11.0.5614.0 Recache=1 [MST] MST1=YourMST.MST [Options] [Display] [Logging] Template=Microsoft Office 2003 Setup(*).txt Type=piwaeo [MinOSRequirement] VersionNT_1=500 WindowsBuild_1=2195 ServicePackLevel_1=3 [Cache] CDCACHE=auto DELETABLECACHE=1 PURGE=0 [OfficeWebComponents] MSI=OWC11.MSI [ChainedInstall_1] TaskType=msi Path=OCONVPCK\ocp11.msi Display=None [ChainedInstall_2] TaskType=msi Path=rhdtool\RHD.msi Display=None [ChainedInstall_3] TaskType=msi Path=TZMove\TZMove.msi Display=None [ChainedInstall_4] TaskType=exe Path=FileFormatConverters.exe Cmdline= /quiet [ChainedInstall_5] TaskType=exe Path=compatibilitypacksp1-kb940289-fullfile-en-us.exe Cmdline= /quiet

Two options: -The hard way: start with no addons and gradually add until you find what is causing this. --To do it fast there is a process called bisection: cut in half and try, keep the halfs that work, toss the ones that don't etc etc etc -Try the XAble addons for windows updates and WGAN I use the following set of hotfixes and installers and get a clean Setuperr.log (but for sfc): 1. nLite/WinXPAddon_UpdatePack_v3.0.7a.7z, (Xable) 2. nLite/WinXPAddon_WGAN_1.1.cab, (Xable) 3. nLite/WinXPAddon_MSUpdate_v1.1.cab, (Xable) 4. nLite/WinXPAddon_QFECheck_1.1.cab, (Xable) 5. nLite/WinXPAddon_DX9_0.3.4CNC.7z, (Xable) 6. Microsoft/IE7/IE7-WindowsXP-x86-enu.exe, (MS) 7. Microsoft\IE7\IE7-WindowsXP-KB938127-x86-ENU.exe, (MS) 8. Microsoft/IE7/IE7-WindowsXP-KB939653-x86-ENU.exe, (MS) 9. Microsoft/UAA/hdaudbus.inf, (KB888111 for HD Audio driver) 10. nLite/ProgramsAddon_dt4112_spdt153_x86.cab, (johndoe74 Daemon tools) 11. nLite\ProgramsAddon_Unlocker-Light-v1.8.5.cab, (Xable from the Ryan site) After that I Boooggy with all WMP11 hot fixes -Note I changed the names of the add-ons a bit, you see I am an Xable fan . -I did not test the newer hot fixes for IE7 so far