Jump to content

RyanVM Windows XP SP2 Update Pack


Recommended Posts

In the mean time, if you must make an ISO, and have a nLited XPCD

ready with Ryan's update pack already in it, just open nLite and stop at

the slipstream page and browse to the new up date and integrate it,

just like it was sp2, works perfect.

Yes, nLite patches sysoc.inf by itself, so this issue is irrelevant if you're using nLite. The updated sysoc.inf is only needed if you're manually integrating it.

Link to comment
Share on other sites


RyanVM, where do you get the value %12% from, I cant find anything in your inf that its refuring to

HKLM,"%SP3UPDATES%\KB885894\Filelist\1","Location",0x00000000,"%10%\AppPatch"

Could I use

HKLM,"%SP3UPDATES%\KB885932\Filelist\0","Location",0x00000000,"%CommonProgramFiles%\microsoft shared\vgx"

or is there a better variable I could use?

{Added}
;# KBKB885932 - Microsoft Internet Explorer 6.0 Crashes or Stops responding and receave an access violation in Vgx.dll
;#   Date         Version        Size       Filename
;#   ------------------------------------------------------
;#   24-Sep-2004  6.0.2900.2523  848,896    Vgx.dll
;#

{Edited}
AddReg  =KB831240.AddReg,KB834707.AddReg,KB873374.AddReg,KB884020.AddReg,KB885523.AddReg,KB885626.AddRe
g,KB885894.AddReg,KB885932.AddReg

{Added}
[KB885932.AddReg]
HKLM,"%SP3UPDATES%\KB885932","Description",0x00000000,"Windows XP Hotfix - KB885932"
HKLM,"%SP3UPDATES%\KB885932","InstalledBy",0x00000000,"%NAME%"
HKLM,"%SP3UPDATES%\KB885932","InstalledDate",0x00000000,"%VERSION%"
HKLM,"%SP3UPDATES%\KB885932","Type",0x00000000,"Update"
HKLM,"%SP3UPDATES%\KB885932\Filelist\0","BuildCheckSum",0x00000000,"d3803"
HKLM,"%SP3UPDATES%\KB885932\Filelist\0","BuildDate",0x00000000,"Wed Oct 27 04:14:48 2004"
HKLM,"%SP3UPDATES%\KB885932\Filelist\0","FileName",0x00000000,"vgx.dll"
HKLM,"%SP3UPDATES%\KB885932\Filelist\0","Location",0x00000000,"%CommonProgramFiles%\microsoft shared\vgx"
HKLM,"%SP3UPDATES%\KB885932\Filelist\0","Version",0x00000000,"6.0.2900.2539"
HKLM,"%HFREGPATH%\KB885932","Backup Dir",0x00000000,""
HKLM,"%HFREGPATH%\KB885932","Comments",0x00000000,"Windows XP Hotfix - KB885932"
HKLM,"%HFREGPATH%\KB885932","Fix Description",0x00000000,"Windows XP Hotfix - KB885932"
HKLM,"%HFREGPATH%\KB885932","Installed",0x00010001,1
HKLM,"%HFREGPATH%\KB885932","Installed By",0x00000000,"%NAME%"
HKLM,"%HFREGPATH%\KB885932","Installed On",0x00000000,"%VERSION%"
HKLM,"%HFREGPATH%\KB885932","Service Pack",0x00010001,3
HKLM,"%HFREGPATH%\KB885932","Valid",0x00010001,1
HKLM,"%HFREGPATH%\KB885932\File 1","Flags",0x00000000,""
HKLM,"%HFREGPATH%\KB885932\File 1","New File",0x00000000,""
HKLM,"%HFREGPATH%\KB885932\File 1","New Link Date",0x00000000,""
HKLM,"%HFREGPATH%\KB885932\File 1","Old Link Date",0x00000000,""

{Edited}
NAME="RyanVM Update Pack - Code Junkie MOD"
VERSION="Version 1.0.2.1 Unofficial Release"

Hows that looking, Hope you dont mind

I have also added the cat file to the [ProductCatalogsToInstall] section too, and compressed the file and put them into what I consider the correct locations

-I386

VGX.DL_

RVMUPPCK.IN_

RVMUpPck.cabFiles from full pack

DOSNET.INF (Edited as stated on your site)

TXTSETUP.SIF (also edited as stated on your site)

other Files from your full pack

-I386\svcpack

compressed cat files

this patch is UNTESTED!!!!! Should will more then likely work.

Download the Unofficial Patch Here :P

Link to comment
Share on other sites

RyanVM, where do you get the value %12% from, I cant find anything in your inf that its refuring to

HKLM,"%SP3UPDATES%\KB885894\Filelist\1","Location",0x00000000,"%10%\AppPatch"

Could I use

HKLM,"%SP3UPDATES%\KB885932\Filelist\0","Location",0x00000000,"%CommonProgramFiles%\microsoft shared\vgx"

or is there a better variable I could use?

<snip>

%12% is the alias for the windows drivers directory.

And I'm going to be using "%16427%\Microsoft Shared\VGX" as the path.

EDIT: And seriously, do you ever bother to do your homework? :rolleyes: You might want to think about how willing you are to support every user who downloads your release before you start cluttering my thread with your releases.

Link to comment
Share on other sites

What about the people that use WMP10?

would it be possable to replace WMP9 with 10 on the CD/DVD?

Im just using the RunOnceEx at the mo

My intention for doing my update is to understand the way the updates are added to I can create a programme that will do it all with a little user input.

Link to comment
Share on other sites

What about the people that use WMP10?

would it be possable to replace WMP9 with 10 on the CD/DVD?

Im just using the RunOnceEx at the mo

Funny you should ask, because there's a big thread going about it in the Application Switches forum. I'm personally not touching it, though. Those that install WMP10 will have to install that update afterwards on their own.
My intention for doing my update is to understand the way the updates are added to I can create a programme that will do it all with a little user input.
Whatever floats your boat.
Link to comment
Share on other sites

I'm testing 1.0.3 right now on my system. It'll be adding the two new hotfixes (KB885932 and KB887078) that were recently released.

An advance word of warning to nLite users, KB887078 includes an updated version of wmvcore.dll. If you use nLite to remove WMP9 from your XP CD, this updated file will also be removed (my pack is extracted prior to component removal). As a result, qfecheck will almost certainly say that KB887078 must be reinstalled (there will be registry entries saying it's installed but the files won't be present on the system). You can safely ignore that warning from qfecheck. I just wanted to warn you guys in advance before some of you start experiencing that.

Link to comment
Share on other sites

Ah crap, looks like I have a typo or something (actually, I think I forgot to copy a file to my i386 directory before building the ISO). More testing here we come :P

crap.png

EDIT: Yup, that's exactly what I did. I forgot to copy the newer svcpack.in_ to i386, so the product catalogs didn't get installed. My bad :P

Link to comment
Share on other sites

Quick question - if I'm using WMP10 instead of WMP9, will installing the KB887078 hotfix mess up WMP10? My guess is no, since svcpack.inf runs at the ~13 minute mark of setup, and I'm currently installing WMP10 in RunOnceEx. Is my assumption correct?

However, what if I were to alter my setup to install WMP10 at the ~13 minute mark - would this cause a problem? (Maybe I'll just have to test this out this weekend if all else fails.)

Link to comment
Share on other sites

I'm testing 1.0.3 right now on my system. It'll be adding the two new hotfixes (KB885932 and KB887078) that were recently released.

An advance word of warning to nLite users, KB887078 includes an updated version of wmvcore.dll. If you use nLite to remove WMP9 from your XP CD, this updated file will also be removed (my pack is extracted prior to component removal). As a result, qfecheck will almost certainly say that KB887078 must be reinstalled (there will be registry entries saying it's installed but the files won't be present on the system). You can safely ignore that warning from qfecheck. I just wanted to warn you guys in advance before some of you start experiencing that.

Hi RyanVM,

I'm testing 1.0.3 right now on my system. It'll be adding the two new hotfixes (KB885932 and KB887078) that were recently released.

That's good to hear ;-) Hope the testing goes well.

Have you ever posted a full article which explains how you create you created and how to update your packs?

I am sure it would make interesting reading and I for one would then understand what your pack does and how it does it :D

Kind Regards

PsiMoon

Link to comment
Share on other sites

Quick question - if I'm using WMP10 instead of WMP9, will installing the KB887078 hotfix mess up WMP10?  My guess is no, since svcpack.inf runs at the ~13 minute mark of setup, and I'm currently installing WMP10 in RunOnceEx.  Is my assumption correct?

However, what if I were to alter my setup to install WMP10 at the ~13 minute mark - would this cause a problem?  (Maybe I'll just have to test this out this weekend if all else fails.)

No. Think about it for a minute. The hotfixed files are directly slipstreamed into your CD. That means the updated wmvcore.dll is already on your CD from the start. There's no reason it would interfere with WMP10 being installed at a later time, just like having WMP9 installed doesn't interfere with WMP10 being installed. Just be aware that you'd have to install the WMP10 version of the hotfix afterwards.
Have you ever posted a full article which explains how you create you created and how to update your packs?

I am sure it would make interesting reading and I for one would then understand what your pack does and how it does it

No. Primarily because I simply don't have the time. Maybe in December when I'm on Christmas break and have some free time to kill. However, it is setup in a way that people who take the time to really look at and study what I've done should be able to figure it out on their own. It's really not that complicated.
ryan, how can i slipstream the kb834707 into my dvd like you do (not english versoin, dutch version)?
Extract the updated files. Makecab them. Add the needed registry entries to the INF (you can figure that out by doing a registry trace before and after hotfix installation). I'd also recommend you read up on the new update.exe so you understand the difference between GDR and QFE versions of the files contained within, along with the Microsoft documentation on INF editing (I also used gosh's pages quite a bit for learning how to use them).

It takes some work, but once you understand the basic process, it's quite straightforward.

Link to comment
Share on other sites

when you release 1.0.3 (or any update) , would it be safe to just put the FULL version .cab file into Windows folder that already has 1.0.2 using nLite?

or do you recommend clean integration of your patch? :)

thanks,

If you've already got 1.0.2 integrated, you'll be able to use the 1.0.2-->1.0.3 upgrade pack I'll be making as well. Those can be directly extracted into i386 with no further work necessary.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...