[jvidal]

Also, clean your Hotfixes, you have redudant ones, eg: 972260 and 974455...

[emzendron]

Sorry... With the O version i have the wpdshext problem, but not the mfplat.dll and wmp11.inf.

This post has been edited by emzendron: 16 October 2009 - 10:20 AM

[jvidal]

p version fixes the wpdshext.res problem. works 100% for me (though I'm not including MSI 4.5)
Although that's weird, rev m and rev p work fine. it's rev n and o that give the wpdshext.res error.
You should re-check your HF list and clean it up.

This post has been edited by jvidal: 16 October 2009 - 10:19 AM

[emzendron]

jvidal, on Oct 16 2009, 11:08 AM, said:

Also, clean your Hotfixes, you have redudant ones, eg: 972260 and 974455...

But they will appear in WU...

[jvidal]

No, they won't: KB974455 is a cumulative update, it REPLACES KB972260.
PLEASE recheck your HF list.

[emzendron]

I'd tested 2 times... Anyway.... Do you have a list (site) where i can see wich new HF replaces the old ones?

Thankz.

[tommyp]

emzendron, on Oct 16 2009, 01:06 PM, said:

I'd tested 2 times... Anyway.... Do you have a list (site) where i can see wich new HF replaces the old ones?

Thankz.

hotfix 099 - http://www.microsoft...ty/current.aspx

[emzendron]

I remade the process... and guess what? Now it's working... I don't know what cause the error, but i should have done something stupid...

Thankz.

This post has been edited by emzendron: 16 October 2009 - 12:36 PM

[jvidal]

yeah, like including unneeded/obsolete/redundant hotfixes.

Just for kicks, I rebuilt using beta q and everything went just fine, no errors whatsoever.
Although I didn't include MSI 4.5 (is it really necessary??? I don't think so)
bye!
(and thx again, tommyp)

This post has been edited by jvidal: 16 October 2009 - 12:54 PM

[Acheron]

Many thanks for Windows Installer 4.5 support!

I have tested Windows Installer 4.5 using Dutch Windows XP Pro SP3 including Windows Media Player 11, Internet Explorer 8 and all security and other hotfixes and everything works flawlessly!

 HFSLIP_revQ.zip (1.99K)
Number of downloads: 13

It's a shame Microsoft still haven't fixed their Windows Installer 4.5 installer as all included files have no valid digital signature. When installing Windows Installer 4.5 manually you would get big trouble whenever sfc reverts to Windows Installer 3.1 files.

Using HFSLIP SFC reports no errors to the user or asks for CD's, except the event log will contain notices.

@jvidal. MSI 4.5 isn't required, but is much faster than MSI 3.1 and contains additional features.

This post has been edited by Acheron: 17 October 2009 - 07:27 AM

[jvidal]

It is?
I have it installed, but I did so manually, I do not put on my slipstreamed CDs.
Maybe I should...now that it is handled correctly...

thx!

[tommyp]

New beta R is up that addresses some 2k WMP and WM hotfixes. The changes do not affect XP.

[gluon]

nice release tommyp, MSI 4.5 is neatly slipstreamed ever since downloading DX9 August 2009 I just realised some DX11 runtime is included. The new dx11 dlls are slipstreamed perfectly and there is also a new library d3dcsx.

So I've got a feature request for a d3dcsx slipstream if you don't mind. The following modification is just a suggestion and most probably not be the best way of doing things.
Line 2144 needs to be modified to
IF EXIST HFCABS\*d3d*_x86.cab FOR /F %%I IN ('DIR/B/A-D/ON HFCABS\*d3d*_x86.cab') DO EXPAND HFCABS\%%I -F:* WORK\DX9EXTRA >NUL

and the following should be added to line 2167 (after D3DCompiler slipstream)

IF EXIST WORK\DX9EXTRA\d3dcsx* FOR /F "TOKENS=2* DELIMS=_" %%I IN ('DIR/B/A-D/ON WORK\DX9EXTRA\d3dcsx*.dll') DO (
	REN WORK\DX9EXTRA\d3dcsx_%%I d3dcsx_%%I
	ECHO>>SOURCESS\I386\TXTSETUP.SIF d3dcsx_%%I = 1,,,,,,,2,0,0,d3dcsx_%%I&ECHO>>SOURCESS\I386\DOSNET.INF d1,d3dcsx_%%I
)

[Tomalak]

Hello,

Just wanted to let you know that in a another hfslip run (with version "r" this time) I had several files in the textmode phase of setup with the "could not be copied" error message. Files seemed not to be related to each other or to all belong to the same patch. Nothing changed compared to my previous attempts (except that I this time installed on a real system instead of a virtual one), so I'm really puzzled.
Not a big problem, as all these files (6 or 7 IIRC, among them "advpack.dll.mui", "jscript.dll.mui") were translation files only, i.e. "<something>.mui", but strange nevertheless. By the way, "wpdshext.res" was not affected this time.

What's going on here? Can someone confirm, or is this something only I experience with the new beta?

[Acheron]

Have you actually checked if all these extra DirectX dll's are actually installed by default on Windows XP?

[tommyp]

Tomalak - did you have the same issues with a VM? Or just the real install? Are those files missing inside the sourcess\i386 folder? If the files are in the sourcess, chances are it's a bad burn. I typically test the CDs out on a VM prior to a real install to verify the burn is ok.

This post has been edited by tommyp: 18 October 2009 - 07:19 AM

[Tomalak]

tommyp, on Oct 18 2009, 03:16 PM, said:

Tomalak - did you have the same issues with a VM? Or just the real install? Are those files missing inside the sourcess\i386 folder? If the files are in the sourcess, chances are it's a bad burn. I typically test the CDs out on a VM prior to a real install to verify the burn is ok.

Well, to be honest what I said above is not exactly true: one change I did was the replacement of the SOURCE folder content. I was doing my tests so far (for MSI installer and debugging some other things) with an XP Pro source and in a VM, but now as I wanted to install XP on a netbook, I used the respective XP Home source which I extracted from the recovery DVD.

I didn't create an ISO image (so a bad burn cannot be the reason), but put the resulting SOURCESS directory to an USB stick and did the installation from there, with the help of WinSetupFromUSB. This might have been the source of my problems (the tool does some modifications to the source, i.e. it adapts the "WINNT.SIF" file).
So I wanted to try with the exact same configuration as before, but this time in a VM and from CD, to see if the copy problems occur there also. But now I'm not even able to get that far! See screenshot below, this appears directly after booting from the CD. It requests me to put a floppy disk named "Windows XP Home Edition Service Pack" into drive A:. I cannot go on from there, and only abort the setup at this point. What the hell?

Has anyone experienced that before, any ideas? Incomplete source (don't think so, as the Windows installation from the USB stick went fine), wrong WINNT.SIF (but tried even without such file, therefore cannot be a wrong parameter I think), wrong CD label (tried "GRTMHOEM_DE" and "GRTMHFPP_DE" which seem appropriate for me) or some hfslip hiccup? I'm perplexed, never seen that. Cannot reproduce the other problems as long as this big obstacle stands between me and another test install What's wrong with my XP Home source?

Attached File(s)

•  WinXP_FloppyDisk_Problem.png (3.57K)
  Number of downloads: 18

[tommyp]

Sure doesn't sounds like an hfslip related issue at first glance. Question for you - did you/can you test your dvd extracted source by itself to see if it installs? Remember, hfslip creates bootable cd images. If you do something else with it, you're on your own. Sorry. Perhaps you should ask on that forum instead? I did see a similar prob once, it was an XP home upgrade cd. For it to work, you needed to have an old OS installed on it prior to installing.

[Tomalak]

tommyp, on Oct 19 2009, 12:26 AM, said:

Sure doesn't sounds like an hfslip related issue at first glance.

Well, it was not. Of course. I meanwhile found out the reason... Stupid me

tommyp, on Oct 19 2009, 12:26 AM, said:

Question for you - did you/can you test your dvd extracted source by itself to see if it installs?

Yes, that was exactly what I was doing next - testing with unmodified source. Failed as well, so no hfslip issue.

And then I had the crucial idea: I was able to get the full i386 directory from the DVD (resp. Ghost image on it), but not the few files on top level (e.g. setup.exe), they are not stored in the image. So I took these files from the XP Pro source. What I didn't know is that the identifier files for Windows and the applied service packs have different names for XP Home and Pro. So renaming "WIN51IP", "WIN51IP.SP2" and "WIN51IP.SP3" to "WIN51IC", "WIN51IC.SP2" and "WIN51IC.SP3" was the solution!
Looks as if installation would work now with unmodified source (due to time I didn't try further than to the start of the file copy in text mode phase, but I assume everything will go smooth from there on). Strange thing is that I wasn't immediately able to recognize that because installation from the USB stick worked, only occurs for the CD based setup.

Maybe this post is of help to someone else some day when he/she encounters that strange behaviour. Sorry for the unneccessary disconcertment.

Now I can finally retry everything from an ISO image and in a VM and see whether the problems described before are caused by hfslip or only a result of the "transfer to USB" program. But not today, too late. Will report back tomorrow...

Good night,
Tomalak

[gluon]

Acheron, on Oct 18 2009, 11:28 PM, said:

Have you actually checked if all these extra DirectX dll's are actually installed by default on Windows XP?

Yes, d3dcsx_42.dll [5,373 KB] will be installed in system32 if I run directx_aug2009_redist.exe manually. That's the only dll currently missing from the slipstreaming process.