BikinDutchman

Yes it is obsolete: KB912945 removes plugin.ocx the official way, so no SFC complaints, and no side effects. (It also changes ActiveX control behavior.) But I am discussing how to get rid of plugin.ocx in the initial Windows installation without side effects. I found it out now but it is pretty complicated: -add plugin.ocx = 16 to [fileflags] to TXTSETUP.sif -do not remove the plugin.oc_ otherwise -hex edit sfcfiles.dll to replace all plugin.ocx by <NUL>lugin.ocx (with xvi32) --repair the checksum (with PEChkSum) --compress (with cabarc -m LZX:21) -unreg and delete plugin.ocx after installation A few questions: -Did someone ever try to integrate KB912945 upfront (with nLite, Ryan)? -What about adding a feature to nLite to remove files from sfcfiles.dll (as I did manually)?

No it was vanilla! I did not try the tweaked yet.

Problem with "Play All" feature in WinXPx64 I did a CD installation for WinXP x64, integrated withg v0.95 and all hotfixes. I observed a problem that I also had with the x64 add-on (now pulled): For a music folder it is possible to select "Play All" in the left panel of an explorer window. This starts WMP11 that plays all files sequentially (you can skip forward and backward). However this does not work in the above integrated install. WMP11 opens just one file from the list (looks like the oldest file). This problem is gone after I overinstall with the official installer (no mistakes this time ). I do not see this problem in x86 installations. This looks like some registration error to me but actually have no clue. Boooggy, I hope you can figure it out; I will test immediately.

Kel: I do not believe this has anything to do with hotfixes. I had an up to date installation (Xable) and could get rid of the error by: -Adding "plugin.ocx = 16" to the fileflags list in TXTSETUP.SIF. -Removing any [obsolete_files] entries for plugin.ocx from addons Also I have indications that the registration error has side effects (Boooggy WMP11 integration), I will try to reproduce that (costs time) and report later. My main point is that it is risky to ignore installation errors however small they may be. I have bad experience with that myself. In this case the solution is imho: leave it in and uninstall it later. (I am now running into the issue that plugin.ocx is protected by sfc but maybe more about that later).

Boooggy, Sorry I just picked the wrong installer file (WindowsServer2003.WindowsXP-KB930627-x64-ENU.exe) file . I would certainly help if the integrator would detect such stupid moves, but for that you would need some positive identification of the real installers. Thanks for help anyway, I will keep looking into the other problem.

redxii: ouch! newsposter: It is the plugin.ocx that comes with the WinXP SP2 installation (I slipstreamed RTM with the SP2 update)

Unhandled exception, problems with WinXP x64 SP2 If have done this one or two times but now for the first time an UEE: WMP11Slipstreamer v0.95 System.ComponentModel.Win32Exception: The system cannot find the file specified at Epsilon.Win32.Resources.ResourceEditor.throwWin32Exception() at Epsilon.Win32.Resources.ResourceEditor.loadResourceLibrary() at WMP11Slipstreamer.CM.GetCabData(String pathToSfxCab) at WMP11Slipstreamer.Backend.NativeExtractHotfix(String hotfixInstaller, String destinationPath) at WMP11Slipstreamer.Backend.ExtractWMP11Installer() at WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings) In a previous installation I had problems that: -"Play All" from an Explorer window did not start with the first file -Skip forward and backward did not work I use a WinNT32 installation, just wanted to try a CD install but cannot get past the UEE

Warning: this gets a little techical I have been testing Boooggy's WMP11 integrator and found some strange behavior for plugin.ocx. I know that plugin.ocx is obsolete and a security risk, and we all hope that WinXP SP3 arrives soon so that we can forget it. Right now it is common to just delete plugin.ocx from nLite WinXP SP2 integrations and that results in the following message in Setuperr.log: "Setup could not register the OLE Control C:\WINDOWS\system32\plugin.ocx because of the following error: LoadLibrary returned error 126 (the specified module could not be found)." Well, that seems pretty harmless but I decided to fix it so added "plugin.ocx = 16" to the fileflags list in TXTSETUP.SIF. After that I suddenly got many signing errors in Setuperr.log for WMP11 files because I used the WMP11 integrator without nLite in a WinNT32 install (will report that later). IMHO this indicates that the plugin.ocx registration failure led to skipping other steps. My suggestion is: Do not just remove plugin.ocx during integration (by addons), add it to the FileFlags list (Nuhi?), and uninstall it after installation (regsvr32 /s /u & DEL) This problem will go away soon enough enough but there will be other crap files in the future; so also for those: remove them without any installer errors because you never know what other effects these errors have.

Hi all, After integrating Xable's MS Update addon v1.1 and the regular MS IE7 installer with nLite 1.4 Final I found the following: After performing the installation with the WinNT32 method I logon and start MS Update: The unexpected behavior is that the MS Update page requests to install the MS Update ActiveX (information bar etc) while it is already installed. After executing that unexpected ActiveX everything looks normal. I do not see the (unexpected) ActiveX popping up if I integrate IE7 with MrNxDmx's addon or if I install IE7 afterwards. Also I do not believe that using the WinNT32 method matters. The big advantage of Xable's addon is that MS Update works right away, no buttons have to be pushed. That advantage is partly undone as described. No big deal but it may be an indication for something else. I attached my Last Session.ini, some of the addons are renamed but it is self-explanatory. Nuhi, Xable can you please look into this? Last_Session.ini

Problem with WinNT32 installation Hi Boooggy, Thanks for all the good work integrating WMP11. I found something strange; maybe you can have a look. I started from a clean WinXP Pro, integrate SP2 with the MS method, and also integrate RAID drivers with the MS method ($OEM$ etc) After that I integrated WMP11 vanilla with your 0.95 integrator and all hotfixes applied. I installed the integrated WinXP with the WinNT32.exe method (from one partition to another); when it comes to component registration I get a message that ICFGNT.dll cannot be registered (because it is not found). After that the completed windows is largely disfunctional. ICFGNT.dll is not normally present in a clean install. The only reference to ICFGNT.dll is in I386\WIN9XUPg\MIGDB.inf. A similar problem is also discussed here. It looks like some upgrade installation is attempted. EDIT: After I integrate IE7 with nLite 1.4 the IFCGNT.dll problem is gone. Well you might say you do not support WinNT32 installations, but I got it going for pretty complex installations, and also your previous add-ons. I found that the WinNT32.exe method is generally a little more picky than CD installations. Maybe it gives a clue for some problem. Thanks for looking,

Look here. Good luck and let us know if it works.

In your installation folder create: I386\$OEM$\$Docs\All Users\Desktop\Software\Your goodies For x64 replace "I386" becomes "AMD64" You migh replace "All Users" by "your_logon_name". Good luck

It described what hardware abstraction layer (HAL) you will use. See for instance here. During installation windows figures out to most comprehensive HAL; that depends on: -single or multiple processor, -APCI or not (power management), -APIC or PIC (interrupt reassignment). That gives 8 combinations of which 2 are ruled out. You only change the HAL from the default if you experience problems with power management or interrupt assignment. If you do not understand what APCI or APIC means search for it first before you touch the HAL.

A few years ago PC Magazine recommended to disable the following: • Netmeeting Remote Desktop Sharing service , • Remote Desktop Help Session Manager service, • Remote Registry service, • SSDP Discovery Service, • Universal Plug and Play Device Host service. They are not very useful and impose a security risk. It is what I typically disable in some 40 PCs and never any issues.

Well, I did a small experiment I made a bootable WinPE 2.0 usb stick, using WAIK. After that I copied my customized, and nLited "WinXP" folder to the root of that stick. I booted WinPE 2.0 from the USB stick, and executed M:\WinXP\i386\winnt32 /s:M:\WinXP\i386 /syspart:C /tempdrive:C /udf:ComputerName,UdbFile /unattend:AnswerFile M: is the drive letter of the stick; C: is the drive letter of the target partition. The arguments after tempdrive depend on what and how you want to customize. I already had two different RAID drivers integrated in the WinPE 2.0 image, and in the WinXP installation. Making it ready for the usb was a 30' job; works like a charm ; WinPE 2.0 is free, easy to use and customize, and for the first time ever, offers easy and consistent mass storage driver integration. The catch is: the WinPE 2.0 image takes 100 MB stick space . And btw the Vista installation is also based on a WinPE implementation.

Well, I tried the $OEM$\$2 theory but that had no effect, nothing writting to the second volume . But, another thing to consider is folder permissions: the Windows, Program Files, Documents and Settings (and Windows\System32) all have non-inherited permissions. Folders in $OEM$\$1 are created on the system drive with permissions inherited from the root. So this becomes also a matter of timing. If a $oem$\$1 Windows folder is created first, it will have inherited permissions. Also the windows installer may not like a Windows folder already present. An then, the Windows folder may be assigned another name, like WinNT32 or whatever. I assume (hope) the $oem$\$$ contents will end up in the actual "windows" folder no matter its name. And lastly "Boot drive" and "System Drive" are not neccessarily the same, for instance in dual boot configuration. The link provided by AgiHammerKlau is not to clear about that.

My 2 cents: the $1 is volume 1 (I believe there can also be $2: volume 2 etc) The Windows etc is defined separate from the volume #

As far as I know the F6 method only works with a clean WinXP installation. (As opposed to OEM installations that have additional folders and/or a WinNT.sif file).

There is an old HP utility that does the trick: search for SP27608.exe. Under Vista it is very easy: make the partition of the USB drive active, see the WinPE 2.0 guide If you have no Vista you can download the WAIK here, obtain a WinPE 2.0 iso, make a WinPE 2.0 CD, boot from that CD and do the above. Making WinXP (installation) bootable from USB is quite a challenge, see extrabigmehdi's post. I think that, eventually, someone will figure it out but it will take a while; MS will not be happy. Good luck,

No full format needed. Switching from IDE to AHCI, or RAID JBOD has no effect on disk content (except for possibly the driver integrated or not).

You can try a repair install with an nLited WinXP

You need to obtain the most recent set of Intel drivers from the Intel website. including the txtsetup.oem file. If you integrate that set with nLite, you can pick either *.inf but for consistency choose the iaahci.inf. nLite gives you a choice out of two and you pick "Intel® SATA RAID/AHCI Controller" You do not need to install any other driver after windows starts (it is already these otherwise Windows would not start) You do not need to install the Intel Matrix Storage but it does not hurt (pretty useless since you do not use matrix storage) Good luck

I found an interesting post here One of the last sentences in naviscan's post is "If RAID is not enabled on installation drive port, then only "NVIDIA nForce Storage Controller" is required." That seems to apply to your installation.

You can try, but drivers on the origal CD are generally out of date. The first thing I do after opening the box is tossing the driver CD. I recommend you try a test install with Windows XP SP2 (vanilla: no slipstream, no tweaks, nothing) on an unused partition. If that works you need no drivers. However, I am a little curious about your disk managament screen shot; I see no drive letters on the HDD, and no System or Boot volume, just one Active volume. DISK1/PARTITION 1 has no volume name. -What drive letters, volume names show up if you open My Computer? -What version of windows do you have? Any other operating systems (LINUX etc)? -In what partition is the \Windows folder actually located? -What are the other partitions used for (no content details, just something like file storage)?

The plot thickens: you have no RAID but you DO have your SATA controller enabled. My educated guess is you have two choices: Turn the SATA controller off and work in emulated IDE mode. That means no driver, you can install vanilla WinXP SP2, but your HDD data rate may be limited to UDMA 5 (100 Mbps). Leave the SATA controller on. That means you need a driver and can obtain, in theory, a SATA II data rate (300 Mbps). You can experiment with this after copying all your essential data to the second disk, DISCONNECT THAT DISK FROM THE MOTHERBOARD, and perform some test installs. The differences in performance may be hardly noticeable. If you want the SATA mode, probably the best way to figure this out further, is downloading the "Make NVIDIA 32bit SATA RAID Driver" driver from the ASUS site and use a vanilla WinXP SP2 installation, the F6 method to integrate the driver, and document the SATA/RAID related dialog. After having that we may help you out further. Good luck. PS HDD driver integration is one of the most convulated parts of the WinXP installations. It would indeed be good to have a tutorial.