[tarquel]

Hi all

Just a quick note on the MSXML hotfix.

I'm about to add the "Hotfix for MSXML 4.0 Service Pack 2 - KB832414" hotfix (KB832414_MSXML4.0_x86.exe) in the DAH folder along with the MSXML V4 SP2 & MSXML V3 SP4 packages in the X2M folder.


My question(s) are:

- Do I need to include the MSXML V3 Update/hotfix as well (I'm gonna leave it there for now)?

- Anyone know if this will work?

Logically it makes sense but I dunno hehe

If anyone can reply with any answers soon as pos as I haven't finished updating the build I'm about to make so if it isn't gonna work, i can save some time

Regards,
N.

[GreenMachine]

You do not need any of them. XML V3 and V4 are not the same thing. Sometimes one is called for, sometimes another. If you install MSXML3USA.MSI (maybe there is a Welsh version!), you should install the update as well.

I see no reason not to install them all, so I do. Windows Update does not complain about them missing, but the Baseline Security Anayzer does.

[tarquel]

Hi GM

I never got a chance last night to reply (to myself) in order to beat you too it GM but I was gonna reply that it works

Quote

You do not need any of them. XML V3 and V4 are not the same thing. Sometimes one is called for, sometimes another. If you install MSXML3USA.MSI (maybe there is a Welsh version!), you should install the update as well.

This is true, however, may as well have it all in the build I create so this is what I did.

Strangely enough, I didn't check to see whether there was a Welsh version or not

Anyhow, assumed that if you install one version, then you should install the hotfix for it:

- V3 SP4 - install Hotfix
- V4 SP2 - install its hotfix too

Quote

I see no reason not to install them all, so I do. Windows Update does not complain about them missing, but the Baseline Security Anayzer does.

MBSA doesn't report any missing hotfixes or updates in my "fully-unattended SATA installed windows XP Home build w/sysprep" (accidentally running right at the start as soon as you first see the desktop) except it does mention something to do with one of the Media Player 9 files being a different version to 'what is expected' - maybe because of the tweak for media player?

This of course isn't connected to the internet so can't check windows update but my custom MBSA scan tells me what I need to know

Thanks,
Nathan

[GreenMachine]

Yes, the MBSA is a much better tool than the Windows Update. What you will always see, is the 3 hotfixes that cannot be validated and WMP with one file version higher than expected.

[tarquel]

The 3 that GrimSage mentions here!?:

http://www.msfn.org/board/index.php?showto...ndpost&p=131790

I only get the WMP message

Maybe thats to be expected.

Regards,
Nathan

PS Bear in mind, I've been working on the XP Home - shows it can be updated just as well as the Pro version (as there isn't much difference between them - but we all know that hehe)

[GreenMachine]

I do believe those three ( all "old" ) just cannot be confirmed by MBSA. They are OK: no worries.

[tarquel]

Excellent

Doh!...trying to catch you up in posts but its never gonna happen is it?

...now if I could just figure out CMDLINES.TXT...hmm....

N.

[GreenMachine]

CMDLINES.TXT?

http://greenmachine....NG/cmdlines.htm

[RyanVM]

Just so you know, SP2 comes with MSXML 3.0 SP5 (but no MSXML 4.0 of any revision as best I can tell).

Also, does anyone have a non-MSI MSXML 4.0 SP2 installer that can be run during the cmdlines.txt part of setup?

[GreenMachine]

Wonder why they didn't put V4?

I use the MSI version, wrapped in IEXPRESS. Not sure that counts as a non-MSI version, but it installs fine from SVCPACK.INF. After XPCREATE does its thing, you should see it in the NEWFILES directory. It uses the same switches as type II hotfixes.

[RyanVM]

Also, how does one go about using the CAB redistributable MS lets you download? It's just a CAB file with 3 dll files and an inf in it.

EDIT: I extracted the contents of the CAB file, added the updated msxml4.dll (the only updated file in the 832414 hotfix), changed the INF with the newer file version (4.20.9821 instead of 4.20.9818), and repacked the CAB archive. You can download it here:
http://msfn.ryanvm.net/msxml4.cab (515KB)

Please tell me how to integrate this into the XP install CD if you figure it out.

EDIT2: For reference sake, here's the page where you can download the original:
http://www.microsoft.com/downloads/details...&DisplayLang=en

[GreenMachine]

That would be interesting. I would guess right click, Install, or call RUNDLL and pass it some parameters. You could pack that into IExpress, and it calls the inf, and gets the files from the cab. Got a link?

[RyanVM]

GreenMachine, on May 17 2004, 09:51 AM, said:

That would be interesting. I would guess right click, Install, or call RUNDLL and pass it some parameters. You could pack that into IExpress, and it calls the inf, and gets the files from the cab. Got a link?

Now that's timing

[RyanVM]

I'm also going to take a look at msxml4.msi tonight in WinInstall LE and see what other registry entries and such are being made during that installation.

[GreenMachine]

First look suggests copy 3 files to system32, add the CLSID registry entries, and REGSVR32 the big file. I doubt that there is much more to it.

[RyanVM]

GreenMachine, on May 17 2004, 10:38 AM, said:

First look suggests copy 3 files to system32, add the CLSID registry entries, and REGSVR32 the big file. I doubt that there is much more to it.

Wanna have a go at it?

[RyanVM]

I'm playing with WinInstall LE right now hacking the MSI file. I added the new msxml4.dll file to it successfully. I'm trying to remove the SDK from the MSI to save some space, though, and while it shows as removed, the file size of the MSI doesn't change at all. Just for kicks, I tried removing all the files from the MSI file and it still shows the same size after saving (5.04MB).

I'm half beginning to think I might as well just create a new MSI from scratch with all the right files. Meh, we'll see

[GreenMachine]

I'm a little busy, but why all that new fangled stuff? Can't be much more than 5 lines of batch code ... I'll let you know when I get around to the Green Version, you keep me posted for the MSI!

[RyanVM]

GreenMachine, on May 17 2004, 12:53 PM, said:

I'm a little busy, but why all that new fangled stuff? Can't be much more than 5 lines of batch code ... I'll let you know when I get around to the Green Version, you keep me posted for the MSI!

Well, I hit a big snag on the MSI version. I think adding that file screwed up some checksums or something because the install fails (error code 2606 IIRC) with the newer DLL added in (of course, I also realized now that there's a manifest file I should be updating as well).

All I know for sure is that there appears to be a lot more stuff being added to the registry by the MSI installer (nothing that can't be exported, though ) that the INF file doesn't say anything about. Whether or not they're necessary is an entirely different matter, though.

[tarquel]

Just my two cents...

Quote

Just so you know, SP2 comes with MSXML 3.0 SP5 (but no MSXML 4.0 of any revision as best I can tell).

The final / finished SP2 will feature Microsoft Installer v3.0 so as that will be different (but backwards compatitible of course) then maybe they will supply a different version of MSXML too!?

PS Quick digression...is it possible to set up win xp so that the Documents and Settings folder appears on drive D (second hard drive) and when new users are created, they get created in the correct place i.e. D:\Documents and Settings\New User.......

I'm only putting this as you mentioned cmdlines.txt again....can it be done through this by adding a .reg file?

I dunno the reg setting that defines this tho Its what I was hoping to do with the xpcreate cd at the end you see

Regards,
N.