5eraph's post-SP2 Update Pack v2017-06_2
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
Updated to 2012-06_1. Please read the Changelog for full details.
Flash addons have been updated. If you use them, download the updated versions.
Flash addons have been updated. If you use them, download the updated versions.
Heard him say it on an episode of SecurityNow (I think when they were speaking about Windows 8, so it's a while ago); http://twit.tv/people/steve-gibson5eraph wrote:Did not know that. Do you have a link to where I can read more about it?
I listen to his audio-netcasts regularly, it's pretty good either way: http://leo.am/podcasts/sn
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
I just integrated 2012-10_2, and then I ran a comparison of files in the i386 directory with a RyanVM slipstream vs an nLite slipstream. Can you tell me why these files, while present in the nLite slipstream are absent in the RVM slipstream:
wbdaplgin.ax
WBDAPLGIN.AX_
wksproxy.ax
WKSPROXY.AX_
wkstvtune.ax
WKSTVTUNE.AX_
wkswdmcap.ax
WKSWDMCAP.AX_
WKSXBAR.AX
WKSXBAR.AX_
wmsdvbnp.ax
WMSDVBNP.AX_
WP2P.DLL
WP2P.DL_
wp2pgraph.dll
WP2PGRAPH.DL_
WP2PNETSH.DLL
WP2PNETSH.DL_
WPNRPNSP.DLL
WPNRPNSP.DL_
wpsisdecd.dll
WPSISDECD.DL_
WPSISRNDR.AX
WPSISRNDR.AX_
wvfwwdm32.dll
WVFWWDM32.DL_
wvidcap.ax
WVIDCAP.AX_
WWSHIRDA.DLL
WWSHIRDA.DL_
Thanks
wbdaplgin.ax
WBDAPLGIN.AX_
wksproxy.ax
WKSPROXY.AX_
wkstvtune.ax
WKSTVTUNE.AX_
wkswdmcap.ax
WKSWDMCAP.AX_
WKSXBAR.AX
WKSXBAR.AX_
wmsdvbnp.ax
WMSDVBNP.AX_
WP2P.DLL
WP2P.DL_
wp2pgraph.dll
WP2PGRAPH.DL_
WP2PNETSH.DLL
WP2PNETSH.DL_
WPNRPNSP.DLL
WPNRPNSP.DL_
wpsisdecd.dll
WPSISDECD.DL_
WPSISRNDR.AX
WPSISRNDR.AX_
wvfwwdm32.dll
WVFWWDM32.DL_
wvidcap.ax
WVIDCAP.AX_
WWSHIRDA.DLL
WWSHIRDA.DL_
Thanks
Those files are deleted by RVMi as specified in the [FileDelete] section of entries.ini. nLite is not coded to use the [FileDelete] section, so it does not delete the specified files.
I have them deleted because they are not ever used by Windows setup. All of those files are present in driver32.cab, and it is only from there that they will be installed. Microsoft erred by not accounting for this; a plain SP2 installation will use the older SP1 files in a driver32.cab that is not updated. Both RVMi and nLite now properly update driver32.cab with SP2 files, so the latest files are always kept and used.
I have them deleted because they are not ever used by Windows setup. All of those files are present in driver32.cab, and it is only from there that they will be installed. Microsoft erred by not accounting for this; a plain SP2 installation will use the older SP1 files in a driver32.cab that is not updated. Both RVMi and nLite now properly update driver32.cab with SP2 files, so the latest files are always kept and used.
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Thank you very much for that explanation.
I have another question. I am debating whether to include the IE 6 Addon, because in Windows XP x32, if you install with IE7/IE8, oobe activation fails and you end up stuck at the "Please Wait" screen, forcing a reboot.
Does IE6 integrate into WXP x64 sp2 transparently?
I have another question. I am debating whether to include the IE 6 Addon, because in Windows XP x32, if you install with IE7/IE8, oobe activation fails and you end up stuck at the "Please Wait" screen, forcing a reboot.
Does IE6 integrate into WXP x64 sp2 transparently?
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
You mean existing IE5 files, correct?
Yea, on an XP repair, if you don't boot into Recovery console or a PE and "batch spuninst.txt" in Windows\IEx directory, you get the aforementioned symptom...
IE7 and IE8 are different from the IE6 upgrade... IE6 is basically the same API as previous IE, but IE7 and 8 are completely different in the sense that slipstreaming them is not just an upgrade, but a seperate program install... I guess what I'm trying to ask is if the IE6 slipstream is "native" to the slipstreamed install os is it run as an additional install at the end of the setup.
Yea, on an XP repair, if you don't boot into Recovery console or a PE and "batch spuninst.txt" in Windows\IEx directory, you get the aforementioned symptom...
IE7 and IE8 are different from the IE6 upgrade... IE6 is basically the same API as previous IE, but IE7 and 8 are completely different in the sense that slipstreaming them is not just an upgrade, but a seperate program install... I guess what I'm trying to ask is if the IE6 slipstream is "native" to the slipstreamed install os is it run as an additional install at the end of the setup.
IE6 has always been included with Windows XP. That's the only reason Microsoft still releases updates for the eleven-year-old browser. I stopped including updates for IE6 in the update pack due to problems when slipstreaming IE7.
I haven't looked too deeply into the method nLite uses to slipstream IE7 x64, but the IE8 x64 addon is a true slipstream in that almost all IE6 files are replaced in the source by IE8 versions.
In short, the IE6 update addon really should not cause the OOBE problem you've previously experienced with XP x86. I'm not as certain about the IE8 x64 addon because the new additional files for which no IE6 equivalents exist are not copied to the destination until around T-22 when INF files are processed.
I haven't looked too deeply into the method nLite uses to slipstream IE7 x64, but the IE8 x64 addon is a true slipstream in that almost all IE6 files are replaced in the source by IE8 versions.
In short, the IE6 update addon really should not cause the OOBE problem you've previously experienced with XP x86. I'm not as certain about the IE8 x64 addon because the new additional files for which no IE6 equivalents exist are not copied to the destination until around T-22 when INF files are processed.
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Ahhhhh... So the IE6 "Addon" is really part of the update pack that branched off to prevent a conflict...
I have no intention of slipstreaming IE7 or IE8 into an install CD, I don't think that's a good idea at all, so of course I should install the IE6 "Addon" to give me the latest IE6 for X64.
Thank you very much, sorry for being such a nudnik, and keep up the great work.
I have no intention of slipstreaming IE7 or IE8 into an install CD, I don't think that's a good idea at all, so of course I should install the IE6 "Addon" to give me the latest IE6 for X64.
Thank you very much, sorry for being such a nudnik, and keep up the great work.
Updated to 2012-10_3. Updated Adobe Flash to v11.5.502.110 from v11.4.402.287.
-
- Posts: 48
- Joined: Tue Jun 10, 2008 11:05 am
- Location: Atlanta GA USA
5eraph!
Thank you again, my friend.
I can't help but wonder as another generation of Windows has been unleashed upon the world, how much longer do you think you'll make this required update for XP64?
I embraced W7 at a new job I took in March 2011, and have put W8 on my main desktop and laptop Core I7 systems (with Start menu restoration and W7 Gadget support). I only dabble now with XP and usually it's the lower x86 form.
BUT...
I will always remain an ardent supporter of yours, and be eternally grateful for the gracious and functional work you have provided so many of us for all these years.
I wish you the best in all things, now and always.
Your friend,
MARK STRELECKI
Atlanta, GA. USA
Thank you again, my friend.
I can't help but wonder as another generation of Windows has been unleashed upon the world, how much longer do you think you'll make this required update for XP64?
I embraced W7 at a new job I took in March 2011, and have put W8 on my main desktop and laptop Core I7 systems (with Start menu restoration and W7 Gadget support). I only dabble now with XP and usually it's the lower x86 form.
BUT...
I will always remain an ardent supporter of yours, and be eternally grateful for the gracious and functional work you have provided so many of us for all these years.
I wish you the best in all things, now and always.
Your friend,
MARK STRELECKI
Atlanta, GA. USA
I'm not going anywhere any time soon. Extended support for XP x86 and x64 ends 2014/04/08. It's hard to predict the future, but the pack should continue to be updated for as long as my current machine stays running and useful; it's perfectly happy with XPx64 and doesn't need a newer OS slowing it down.
Current desktop hardware:
Current desktop hardware:
- Gigabyte GA-G31M-ES2L (rev.2.0)
Intel Core 2 Quad Processor Q9650
4 GB SuperTalent DDR2 800 RAM
PowerColor PCS+ Radeon HD 5830
Well, I believe XPx64 is the fastest Microsoft x64 product ever, and I don't see any reason to move to NT6.x even on powerful hardware. Cuz I'm running it on i5-3570K @ 4.4GHz/8GB DDR3-2000/GTX480/128GB SSD. And I am very glad of its ultra fast response and featherweight. I have Win7 on my laptom only because of inability to install XP, and I am dissapointed and not happy of Win7 and Microsoft at all.
I know that one Japanese geek is still provides support for Win2000, and I think it is normal.
Thank you, 5eraph. I love your updatepack, it's the best!
I know that one Japanese geek is still provides support for Win2000, and I think it is normal.
Thank you, 5eraph. I love your updatepack, it's the best!
newer is not always better
Current files uploaded to SkyDrive (Public). It should not be necessary to log in when downloading individual files.
mockingbird wrote:I am debating whether to include the IE 6 Addon, because in Windows XP x32, if you install with IE7/IE8, oobe activation fails and you end up stuck at the "Please Wait" screen, forcing a reboot.
So, if I slipstream IE8 and I ever need to run a XP repair, does that mean I'll encounter issues?mockingbird wrote:Yea, on an XP repair, if you don't boot into Recovery console or a PE and "batch spuninst.txt" in Windows\IEx directory, you get the aforementioned symptom...
IE7 and IE8 are different from the IE6 upgrade... IE6 is basically the same API as previous IE, but IE7 and 8 are completely different in the sense that slipstreaming them is not just an upgrade, but a seperate program install... I guess what I'm trying to ask is if the IE6 slipstream is "native" to the slipstreamed install os is it run as an additional install at the end of the setup.
Is this true even if I do the repair using my XP CD that has IE8 slipstreamed into it?
Updated to 2012-12_1. Please read the Changelog for full details.
Current files are mirrored on SkyDrive, as requested previously.
Current files are mirrored on SkyDrive, as requested previously.
You're welcome. 
Updated to 2012-12_2. Please read the Changelog for full details.
Current files are mirrored on SkyDrive, as requested previously.

Updated to 2012-12_2. Please read the Changelog for full details.
Current files are mirrored on SkyDrive, as requested previously.
Updated to 2012-12_3. Unauthorized Digital Certificate revocations updated.
Current files are mirrored on SkyDrive, as requested previously.
Current files are mirrored on SkyDrive, as requested previously.