!
Full Version: HFSLIP - Test releases
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45
Hmmm...I find it amusing that 61001a was 141 KB and 61004b is back to 147 KB !
!
Sorry for the delay, I was done for the day. 
(should actually be a YAWNING smilie)
11am:
YOU ARE DA MAN! (as always). Build completed 100% no errors.
(should actually be a YAWNING smilie)QUOTE (Tomcat76 @ Oct 4 2006, 06:48 PM) 
Is PLAYLIST.IN_ present in the I386 folder of the new source?
yes. it is there.QUOTE
If it's in the new source then 61004b should fix it.
Giving it a go right now. will let you know in a few hours how it went.11am:
YOU ARE DA MAN! (as always). Build completed 100% no errors.
QUOTE (Super-Magician @ Oct 5 2006, 02:27 AM)
Hmmm...I find it amusing that 61001a was 141 KB and 61004b is back to 147 KB !
WMP9, ya know... ! QUOTE (NtegrA @ Oct 5 2006, 01:06 PM)
Build completed 100% no errors.
Nice 
I know HFSLIP recently added support for MSXML2, but I have 2 questions:
1)If I were to slipstream MSXML 3 SP7 on 2000/XP (2003 SP1 includes it), would I have duplicate entries in txtsetup.sif/doesnet.inf?
2)Is KB832414 supported for MSXML 2.5 on 2000 SP4 (included in XP SP2 (not sure about SP1) and 2003 SP1)?
Other that that, Looks great Tomcat.
the_guy
1)If I were to slipstream MSXML 3 SP7 on 2000/XP (2003 SP1 includes it), would I have duplicate entries in txtsetup.sif/doesnet.inf?
2)Is KB832414 supported for MSXML 2.5 on 2000 SP4 (included in XP SP2 (not sure about SP1) and 2003 SP1)?
Other that that, Looks great Tomcat.
the_guy
Seems we're pretty much ready for a new final - especially since we haven't released one since August!
But, I guess we should wait until AFTER October 10
.
But, I guess we should wait until AFTER October 10
.
QUOTE (the_guy @ Oct 5 2006, 09:12 PM)
1)If I were to slipstream MSXML 3 SP7 on 2000/XP (2003 SP1 includes it), would I have duplicate entries in txtsetup.sif/doesnet.inf?
Don't see why. The file names are different: msxml2.dll and msxml2r.dll vs. msxml3.dll and msxml3r.dll...QUOTE (the_guy @ Oct 5 2006, 09:12 PM)
2)Is KB832414 supported for MSXML 2.5 on 2000 SP4 (included in XP SP2 (not sure about SP1) and 2003 SP1)?
It is now... 
QUOTE (Super-Magician @ Oct 5 2006, 10:35 PM)
Seems we're pretty much ready for a new final
I prefer to have some more test results come in...QUOTE (Super-Magician @ Oct 5 2006, 10:35 PM)
But, I guess we should wait until AFTER October 10 .
This is a good way to test how well the renewed HFSLIP script does... .
@Tomcat: I just read my question, and it doesn't apply to 2000 as 891861 is what introduces MSXML 3. What I meant was, XP SP2 includes MSXML 3 SP5, and if I were to slipstream MSXML 3 SP7, would there be duplicate entries? They both include msxml3(a/r).dll.
the_guy
the_guy
Your posts are getting confusing. I'll clarify....
Win2K has:
- MSXML 2.5 version 8.0.6730.0
Win 2K can be upgraded to all of these:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
WinXP SP1 has:
- MSXML 2.5 version 8.0.6730.0
- MSXML 2 SP? version 8.30.8709.0
- MSXML 3 SP3 version 8.30.9926.0
WinXP SP1 can be upgraded to all of these:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
WinXP SP2 has:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP? version 8.30.9529.0
- MSXML 3 SP5 version 8.50.2162.0
WinXP SP2 can be upgraded to all of these:
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
Win2K3 SP1 has:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP? version 8.30.9528.0
- MSXML 3 SP7 version 8.70.1104.0
Win2K3 SP1 can be upgraded to all of these:
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
Win2K has:
- MSXML 2.5 version 8.0.6730.0
Win 2K can be upgraded to all of these:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
WinXP SP1 has:
- MSXML 2.5 version 8.0.6730.0
- MSXML 2 SP? version 8.30.8709.0
- MSXML 3 SP3 version 8.30.9926.0
WinXP SP1 can be upgraded to all of these:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
WinXP SP2 has:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP? version 8.30.9529.0
- MSXML 3 SP5 version 8.50.2162.0
WinXP SP2 can be upgraded to all of these:
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 3 SP7 version 8.70.1104.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
Win2K3 SP1 has:
- MSXML 2.5 version 8.0.7002.0
- MSXML 2 SP? version 8.30.9528.0
- MSXML 3 SP7 version 8.70.1104.0
Win2K3 SP1 can be upgraded to all of these:
- MSXML 2 SP6 version 8.30.9531.0
- MSXML 4 SP2 version 4.20.9828.0
- MSXML 6 version 6.0.3883.0
QUOTE (the_guy @ Oct 5 2006, 11:34 PM)
What I meant was, XP SP2 includes MSXML 3 SP5, and if I were to slipstream MSXML 3 SP7, would there be duplicate entries? They both include msxml3(a/r).dll.
No; HFSLIP only adds entries in TXTSETUP.SIF and DOSNET.INF for new binaries, not updated binaries.
What I mean is:
I have XP SP2 in my source folder. It has MSXML 3 SP5. I put MSXML 3 SP7 in to be slipstremed (msxml3.msi in HF). Will I have d1,msxml3.dll showing up twice in my dosnet.inf? That's what I meant. That list you posted is quite good, thanks Tomcat.
the_guy
I have XP SP2 in my source folder. It has MSXML 3 SP5. I put MSXML 3 SP7 in to be slipstremed (msxml3.msi in HF). Will I have d1,msxml3.dll showing up twice in my dosnet.inf? That's what I meant. That list you posted is quite good, thanks Tomcat.
the_guy
QUOTE (the_guy @ Oct 5 2006, 07:59 PM)
What I mean is:
I have XP SP2 in my source folder. It has MSXML 3 SP5. I put MSXML 3 SP7 in to be slipstremed (msxml3.msi in HF). Will I have d1,msxml3.dll showing up twice in my dosnet.inf? That's what I meant. That list you posted is quite good, thanks Tomcat.
Doesn't this right here answer your question quite clearly??I have XP SP2 in my source folder. It has MSXML 3 SP5. I put MSXML 3 SP7 in to be slipstremed (msxml3.msi in HF). Will I have d1,msxml3.dll showing up twice in my dosnet.inf? That's what I meant. That list you posted is quite good, thanks Tomcat.
QUOTE (Tomcat76 @ Oct 5 2006, 07:09 PM)
No; HFSLIP only adds entries in TXTSETUP.SIF and DOSNET.INF for new binaries, not updated binaries.
I get it now. I thought that that was an issue at one time. It's porbably long-fixed by now.
the_guy
the_guy
Things are fine on my end now. Any stress-test volunteers?
To test:
- 2KSP4 (with/without IE6, DX9 and WMP9)
- XPSP1 (with/without WMP10)
- XPSP2 (with/without WMP10)
- 2K3SP1
Remove the addons while testing.
BTW... I forgot to mention this in the changelog a few days ago but the MSXML3.DLL error that used to appear in setuperr.log has been dealt with...
To test:
- 2KSP4 (with/without IE6, DX9 and WMP9)
- XPSP1 (with/without WMP10)
- XPSP2 (with/without WMP10)
- 2K3SP1
Remove the addons while testing.
BTW... I forgot to mention this in the changelog a few days ago but the MSXML3.DLL error that used to appear in setuperr.log has been dealt with...
*maybe* XP SP1 and SP2 without WMP.
(let's say I work maths 7 hours per day, every day)
(let's say I work maths 7 hours per day, every day)
I have tested windows 2000 with dx9 but without mp and IE do you want results?
How much does swflash.cab add to the size of the iso ?
I'm not slipstreaming it ATM but I may since it shouldn't add too much to my iso.
I'm not slipstreaming it ATM but I may since it shouldn't add too much to my iso.
QUOTE (Camarade_Tux @ Oct 7 2006, 10:45 AM)
*maybe* XP SP1 and SP2 without WMP.
(let's say I work maths 7 hours per day, every day)
XPSP1 is enough. And do it when you have the time (let's say I work maths 7 hours per day, every day)
QUOTE (dirtwarrior @ Oct 7 2006, 12:48 PM)
I have tested windows 2000 with dx9 but without mp and IE do you want results?
Yes, please. I changed something in the INF handling of IE5; HFSLIP used to duplicate the Rollup INF with the first copy having Windows setup execute the portion relevant to Windows and the second copy execute the stuff for IE5. This is now done from one INF.QUOTE (Camarade_Tux @ Oct 7 2006, 01:45 PM)
How much does swflash.cab add to the size of the iso ?
If using Flash 9, the OCX is 989KB and SWFLASH.IN_ (only for 2K and 2K3) is 1.03KB large.
If you still need testing, I'll do it for XPSP2 w/ WMP10 and possibly 2KSP4 w/ IE6+DX9+WMP9.
On a side-note: Why has FDV's domain been suspended??
On a side-note: Why has FDV's domain been suspended??
QUOTE (Tomcat76 @ Oct 7 2006, 02:55 PM)
QUOTE (Camarade_Tux @ Oct 7 2006, 10:45 AM)
*maybe* XP SP1 and SP2 without WMP.
(let's say I work maths 7 hours per day, every day)
XPSP1 is enough. And do it when you have the time (let's say I work maths 7 hours per day, every day)
No problem today. I only wackoed my HF_SP1 and HF_SP2.
In fact, I did not have any problem : I forgot to rename HF_SP1 to HF.
QUOTE (Tomcat76 @ Oct 7 2006, 02:55 PM)
QUOTE (Camarade_Tux @ Oct 7 2006, 01:45 PM)
How much does swflash.cab add to the size of the iso ?
If using Flash 9, the OCX is 989KB and SWFLASH.IN_ (only for 2K and 2K3) is 1.03KB large.Thanks for the info.
I've just compared both ocx files and v9 is maybe 100KB bigger so I've added it.
One last thing : I use Console on my desktop and once hfslip is done, when I press "Enter", hfslip exits Console.
Since this is by default on some OS, could a check be added so it closes only when really needed.
Thanks.
All patchs correctly installed under XP SP1 according to HfNetChk (and of course some warnings with file version greater than expected).
But note, I'm not updating MDAC and I'm using nlite. I'll make a new build without nlite.
edit : w/o wmp10
But note, I'm not updating MDAC and I'm using nlite. I'll make a new build without nlite.
edit : w/o wmp10
Some problems in fact when trying without nlite. 
-installation did not complete : it restarted after T-9 without throwing any error and did not seem to crash
-then all or fast all hfslp*.inf files were missing
-restarted again
Nothing special in it but here is the hfslip.log:
HFSLIP Version - 61006a
HFSLIP Path - E:\Adrien\yAXM\hfslip\
OS in SOURCESS - XP SP1 French
DirectX9c Slipstreamed
Drivers - SPX.CAB Added
CD Install Path - Default
CDTAG - WIN51
===============================================================================
Files in your FIX folder:
Files in your HF folder:
DirectX90-KB839643-x86-FRA.EXE
FRN_Q832483_MDAC_x86.EXE
IE6.0sp1-KB833989-x86-FRA.exe
IE6.0sp1-KB918439-Windows-2000-XP-x86-FRA.exe
IE6.0sp1-KB918899-Windows-2000-XP-v2-x86-FRA.exe
IE6.0sp1-KB918899-Windows-2000-XP-v3-x86-FRA.exe
IE6.0sp1-KB925486-WindowsXP-x86-FRA.exe
OE6.0sp1-KB911567-Windows-2000-XP-x86-FRA.exe
Q322011_WXP_SP2_x86_FRA.exe
Q327979_WXP_SP2_x86_FRA.exe
Q810243_WXP_SP2_x86_ENU.exe
Q814995_WXP_SP2_x86_FRA.exe
WindowsInstaller-KB893803-v2-x86.exe
WindowsMedia-KB911564-x86-FRA.exe
WindowsMedia-Q828026-x86-FRA.exe
WindowsMedia8-KB817787-x86-FRA.exe
WindowsMedia8-KB917734-x86-FRA.exe
WindowsXP-KB817778-x86-FRA.exe
WindowsXP-KB822603-x86-FRA.exe
windowsxp-kb823182-x86.exe
windowsxp-kb824105-x86-fra.exe
WindowsXP-KB826939-x86-FRA.exe
WindowsXP-KB826942-x86-FRA.exe
windowsxp-kb828035-x86-fra.exe
windowsxp-kb833987-x86-fra.exe
windowsxp-kb835732-x86-fra.exe
windowsxp-kb837001-x86-fra.exe
windowsxp-kb840987-x86-fra.exe
windowsxp-kb841356-x86-fra.exe
windowsxp-kb841533-x86-fra.exe
windowsxp-kb841873-x86-fra.exe
WindowsXP-KB873339-x86-FRA.exe
WindowsXP-KB873376-x86-fra.exe
WindowsXP-KB885626-v2-x86-fra.exe
windowsxp-kb885835-x86-fra.exe
windowsxp-kb885836-x86-fra.exe
WindowsXP-KB887472-x86-SP1-FRA.exe
windowsxp-kb888302-x86-fra.exe
windowsxp-kb890046-x86-fra.exe
windowsxp-kb890859-x86-fra.exe
WindowsXP-KB891711-x86-FRA.exe
windowsxp-kb891781-x86-fra.exe
WindowsXP-KB892944-x86-FRA.exe
windowsxp-kb893756-x86-fra.exe
windowsxp-kb896358-x86-fra.exe
windowsxp-kb896423-x86-fra.exe
windowsxp-kb896424-x86-fra.exe
windowsxp-kb896428-x86-fra.exe
windowsxp-kb899587-x86-fra.exe
WindowsXP-KB899589-x86-FRA.exe
WindowsXP-KB899591-x86-FRA.exe
windowsxp-kb900725-x86-fra.exe
WindowsXP-KB901017-x86-FRA.exe
WindowsXP-KB901190-x86-FRA.exe
windowsxp-kb901214-x86-fra.exe
WindowsXP-KB904706-DX9-x86-FRA.exe
windowsxp-kb905414-x86-fra.exe
windowsxp-kb905495-x86-fra.exe
windowsxp-kb905749-x86-fra.exe
WindowsXP-KB908519-x86-FRA.exe
WindowsXP-KB908531-v2-x86-FRA.exe
WindowsXP-KB910437-x86-FRA.exe
WindowsXP-KB911280-v2-x86-FRA.exe
WindowsXP-KB911562-x86-FRA.exe
WindowsXP-KB911927-x86-FRA.exe
WindowsXP-KB912817-v2-x86-FRA.exe
WindowsXP-KB912919-x86-FRA.exe
WindowsXP-KB913580-x86-FRA.exe
WindowsXP-KB914388-x86-FRA.exe
WindowsXP-KB914389-x86-FRA.exe
WindowsXP-KB914798-v2-x86-FRA.exe
WindowsXP-KB917159-x86-FRA.exe
WindowsXP-KB917422-x86-FRA.exe
WindowsXP-KB917537-x86-FRA.exe
WindowsXP-KB917953-x86-FRA.exe
WindowsXP-KB919007-x86-FRA.exe
WindowsXP-KB920670-x86-FRA.exe
WindowsXP-KB920683-x86-FRA.exe
WindowsXP-KB920685-x86-FRA.exe
WindowsXP-KB921398-x86-FRA.exe
WindowsXP-KB921883-x86-FRA.exe
WindowsXP-KB922616-x86-FRA.exe
WindowsXP-Windows2000-Script56-KB917344-x86-fra.exe
xpsp1a_fr_x86.exe
msxml6.msi
Files in your HFCABS folder:
BDA.cab
BDANT.cab
BDAXP.cab
DirectX.cab
dxdllreg_x86.cab
dxnt.cab
dxupdate.cab
Feb2006_MDX1_x86.cab
Feb2006_MDX1_x86_Archive.cab
Feb2006_xact_x86.cab
Oct2005_xinput_x86.cab
swflash.cab
Files in your HFSVCPACK folder:
Files in your HFSVCPACK_SW folder:
Files in your HFTOOLS folder:
modifyPE.exe
Files in your HFEXPERT folder:
E:\Adrien\yAXM\hfslip\HFEXPERT\APPREPLACEMENT\SFCFILES.DLL
===============================================================================
HFSLIP run time: 5m51s
-installation did not complete : it restarted after T-9 without throwing any error and did not seem to crash
-then all or fast all hfslp*.inf files were missing
-restarted again
Nothing special in it but here is the hfslip.log:
CODE
HFSLIP Version - 61006a
HFSLIP Path - E:\Adrien\yAXM\hfslip\
OS in SOURCESS - XP SP1 French
DirectX9c Slipstreamed
Drivers - SPX.CAB Added
CD Install Path - Default
CDTAG - WIN51
===============================================================================
Files in your FIX folder:
Files in your HF folder:
DirectX90-KB839643-x86-FRA.EXE
FRN_Q832483_MDAC_x86.EXE
IE6.0sp1-KB833989-x86-FRA.exe
IE6.0sp1-KB918439-Windows-2000-XP-x86-FRA.exe
IE6.0sp1-KB918899-Windows-2000-XP-v2-x86-FRA.exe
IE6.0sp1-KB918899-Windows-2000-XP-v3-x86-FRA.exe
IE6.0sp1-KB925486-WindowsXP-x86-FRA.exe
OE6.0sp1-KB911567-Windows-2000-XP-x86-FRA.exe
Q322011_WXP_SP2_x86_FRA.exe
Q327979_WXP_SP2_x86_FRA.exe
Q810243_WXP_SP2_x86_ENU.exe
Q814995_WXP_SP2_x86_FRA.exe
WindowsInstaller-KB893803-v2-x86.exe
WindowsMedia-KB911564-x86-FRA.exe
WindowsMedia-Q828026-x86-FRA.exe
WindowsMedia8-KB817787-x86-FRA.exe
WindowsMedia8-KB917734-x86-FRA.exe
WindowsXP-KB817778-x86-FRA.exe
WindowsXP-KB822603-x86-FRA.exe
windowsxp-kb823182-x86.exe
windowsxp-kb824105-x86-fra.exe
WindowsXP-KB826939-x86-FRA.exe
WindowsXP-KB826942-x86-FRA.exe
windowsxp-kb828035-x86-fra.exe
windowsxp-kb833987-x86-fra.exe
windowsxp-kb835732-x86-fra.exe
windowsxp-kb837001-x86-fra.exe
windowsxp-kb840987-x86-fra.exe
windowsxp-kb841356-x86-fra.exe
windowsxp-kb841533-x86-fra.exe
windowsxp-kb841873-x86-fra.exe
WindowsXP-KB873339-x86-FRA.exe
WindowsXP-KB873376-x86-fra.exe
WindowsXP-KB885626-v2-x86-fra.exe
windowsxp-kb885835-x86-fra.exe
windowsxp-kb885836-x86-fra.exe
WindowsXP-KB887472-x86-SP1-FRA.exe
windowsxp-kb888302-x86-fra.exe
windowsxp-kb890046-x86-fra.exe
windowsxp-kb890859-x86-fra.exe
WindowsXP-KB891711-x86-FRA.exe
windowsxp-kb891781-x86-fra.exe
WindowsXP-KB892944-x86-FRA.exe
windowsxp-kb893756-x86-fra.exe
windowsxp-kb896358-x86-fra.exe
windowsxp-kb896423-x86-fra.exe
windowsxp-kb896424-x86-fra.exe
windowsxp-kb896428-x86-fra.exe
windowsxp-kb899587-x86-fra.exe
WindowsXP-KB899589-x86-FRA.exe
WindowsXP-KB899591-x86-FRA.exe
windowsxp-kb900725-x86-fra.exe
WindowsXP-KB901017-x86-FRA.exe
WindowsXP-KB901190-x86-FRA.exe
windowsxp-kb901214-x86-fra.exe
WindowsXP-KB904706-DX9-x86-FRA.exe
windowsxp-kb905414-x86-fra.exe
windowsxp-kb905495-x86-fra.exe
windowsxp-kb905749-x86-fra.exe
WindowsXP-KB908519-x86-FRA.exe
WindowsXP-KB908531-v2-x86-FRA.exe
WindowsXP-KB910437-x86-FRA.exe
WindowsXP-KB911280-v2-x86-FRA.exe
WindowsXP-KB911562-x86-FRA.exe
WindowsXP-KB911927-x86-FRA.exe
WindowsXP-KB912817-v2-x86-FRA.exe
WindowsXP-KB912919-x86-FRA.exe
WindowsXP-KB913580-x86-FRA.exe
WindowsXP-KB914388-x86-FRA.exe
WindowsXP-KB914389-x86-FRA.exe
WindowsXP-KB914798-v2-x86-FRA.exe
WindowsXP-KB917159-x86-FRA.exe
WindowsXP-KB917422-x86-FRA.exe
WindowsXP-KB917537-x86-FRA.exe
WindowsXP-KB917953-x86-FRA.exe
WindowsXP-KB919007-x86-FRA.exe
WindowsXP-KB920670-x86-FRA.exe
WindowsXP-KB920683-x86-FRA.exe
WindowsXP-KB920685-x86-FRA.exe
WindowsXP-KB921398-x86-FRA.exe
WindowsXP-KB921883-x86-FRA.exe
WindowsXP-KB922616-x86-FRA.exe
WindowsXP-Windows2000-Script56-KB917344-x86-fra.exe
xpsp1a_fr_x86.exe
msxml6.msi
Files in your HFCABS folder:
BDA.cab
BDANT.cab
BDAXP.cab
DirectX.cab
dxdllreg_x86.cab
dxnt.cab
dxupdate.cab
Feb2006_MDX1_x86.cab
Feb2006_MDX1_x86_Archive.cab
Feb2006_xact_x86.cab
Oct2005_xinput_x86.cab
swflash.cab
Files in your HFSVCPACK folder:
Files in your HFSVCPACK_SW folder:
Files in your HFTOOLS folder:
modifyPE.exe
Files in your HFEXPERT folder:
E:\Adrien\yAXM\hfslip\HFEXPERT\APPREPLACEMENT\SFCFILES.DLL
===============================================================================
HFSLIP run time: 5m51s
Camarade_Tux, you sure you didn't remove anything like INF files when running nLite?
That was without nlite.
I think it has something to do with the restart of the installation because on initial try, I have no problem with inf files.
I just confirmed it : it appears only after installation has been "resumed".
I think it has something to do with the restart of the installation because on initial try, I have no problem with inf files.
I just confirmed it : it appears only after installation has been "resumed".
@Camarade_Tux: I just noticed in your hfslip.log file that you include 839643 and DirectX9c. DirectX9c includes 839643. Maybe remove 839643 from your source?
the_guy
the_guy
Your list is incomplete but that shouldn't be an issue.
As the_guy said, remove DirectX90-KB839643-x86-FRA.EXE.
Also get rid of these:
IE6.0sp1-KB918899-Windows-2000-XP-v2-x86-FRA.exe (you have v3)
IE6.0sp1-KB833989-x86-FRA.exe (superseded)
As the_guy said, remove DirectX90-KB839643-x86-FRA.EXE.
Also get rid of these:
IE6.0sp1-KB918899-Windows-2000-XP-v2-x86-FRA.exe (you have v3)
IE6.0sp1-KB833989-x86-FRA.exe (superseded)
There's a problem with XPSP1. Hold on...
I experienced the same WMP10 problem and it isn't related to the problem I posted above. This'll need a bit of work. Also, WU complains about KB883357 and KB839645.
Not ready for XPSP1 yet...
Not ready for XPSP1 yet...
It seems that KB914440 (Network Diagnostics Tool) is not slipstreamed properly.
The file is supposed to appear as %systemroot%\Network Diagnostic\xpnetdiag.exe, but instead, it is placed in %systemroot%\system32 and named as xpnetdg.exe.
The file is supposed to appear as %systemroot%\Network Diagnostic\xpnetdiag.exe, but instead, it is placed in %systemroot%\system32 and named as xpnetdg.exe.
PM me if something is needed.
I can do quick tests but I don't have enough time to visit forums during the week.
I can do quick tests but I don't have enough time to visit forums during the week.
* Have found multiple problems with WMP10 on XPSP1 -- not fixed yet
* BITS update on XPSP1 -- fixed for upcoming version
* KB839645 is a mystery; it's superseded -- need to find good reg hack
* Network Diagnostics Tool for XPSP2 (was this ever supported?) -- fixed for upcoming version
* BITS update on XPSP1 -- fixed for upcoming version
* KB839645 is a mystery; it's superseded -- need to find good reg hack
* Network Diagnostics Tool for XPSP2 (was this ever supported?) -- fixed for upcoming version
@Tomcat: Would this reg hack work for 839645?
the_guy
CODE
[Version]
Signature=$Windows NT$
[DefaultInstall]
Addreg=839645fix
[839645fix]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\ProtocolDefaults","shell",0x10001,0x0
Signature=$Windows NT$
[DefaultInstall]
Addreg=839645fix
[839645fix]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\ProtocolDefaults","shell",0x10001,0x0
the_guy
QUOTE (Tomcat76 @ Oct 8 2006, 07:37 PM)
* Network Diagnostics Tool for XPSP2 (was this ever supported?) -- fixed for upcoming version
It was not officially supported, but you showed how to do that here:
http://www.msfn.org/board/index.php?s=&...st&p=537452
I always added that manually to the script, and it worked without problems. You can now compare that old suggestion with the new support you added to the upcoming version ;-)
Regards,
Tomalak
We're getting somewhere. Most problems with WMP10 on XPSP1 are fixed; remaining:
- playlists don't work (won't fix this)
- window pops up at T-13 to complete installation of WMP10 (normally appears on first run)
@the_guy: thanks; that did it
@Tomalak: that manual trick won't work properly anymore for DOS-based installs with the current test releases when including WMP10 because of the double custsat.dll files. A workaround will be implemented.
I want to test this one more time with XPSP1 and XPSP2 and will release a new version tomorrow at the latest because that's probably the last day you'll be able to check if all hotfixes are slipstreamed properly on XPSP1.
- playlists don't work (won't fix this)
- window pops up at T-13 to complete installation of WMP10 (normally appears on first run)
@the_guy: thanks; that did it
@Tomalak: that manual trick won't work properly anymore for DOS-based installs with the current test releases when including WMP10 because of the double custsat.dll files. A workaround will be implemented.
I want to test this one more time with XPSP1 and XPSP2 and will release a new version tomorrow at the latest because that's probably the last day you'll be able to check if all hotfixes are slipstreamed properly on XPSP1.
@Tomalak/Tomcat, seems I forgot that support for KB914440 was never in the actual script. When I mentioned it briefly in the New updates thread or something, someone said it was supported so I never bothered to check
Thanks.
Thanks.
OK. Check the new version
You still have the WMP10 popup at T-13 for XPSP1 (the one you normally get when starting WMP10 for the first time) but at least the installation isn't broken anymore. At this point, you can still choose between following the wizard or closing it. I'll try to get rid of it in the next few days.
Also, the Documentation Update is finally slipstreamed, completing support for XPSP1. Windows Update should be cool now
You still have the WMP10 popup at T-13 for XPSP1 (the one you normally get when starting WMP10 for the first time) but at least the installation isn't broken anymore. At this point, you can still choose between following the wizard or closing it. I'll try to get rid of it in the next few days.
Also, the Documentation Update is finally slipstreamed, completing support for XPSP1. Windows Update should be cool now
hey Tomcat76, you've been very busy with HFSLIP this past few days. thanks for all your hardwork. very much appreciated!
btw, the latest test release works great for me.. am with XPSP2.
thanks again!
thanks for all your hardwork. very much appreciated!btw, the latest test release works great for me.. am with XPSP2.
thanks again!
I ran into a problem with wmfdist.exe in HF. Never had this trouble before, and by looking at the code it seems that this may be because of the WMP10 changes. During GUI setup, I got this error:
So I made another run without HFAAO, HFCABS, HFEXPERT, HFSVPCPACK, HFSVCPACK_SW or HFCLEANUP and I still got the error. The file, logagent.exe, is in a reducer and that is reflected in the script. I got the same error with and without that reducer.
In addition, on my test runs with HFCLEANUP taken completely out of the picture, I got a new error that I hadn't seen before:
Back to the wmfdist problem, I also tried adding the cabbed file (logagent.ex_) to FIX but that didn't help. Also tried different Compression Types (A and C) as well as test release 6a and 8a but got the same results.
The only fix for this for me is to remove wmfdist.exe. What am I doing wrong?
QUOTE
(Window Title: Advanced INF Install)
Error creating process <"C:\winnt\system32\logagent.exe" /regserver>. Reason: The system cannot find the file specified.
Which comes from line 168 in WMFSDK.inf in wmfdist.exe: Error creating process <"C:\winnt\system32\logagent.exe" /regserver>. Reason: The system cannot find the file specified.
CODE
[RunPost]
"""%11%\logagent.exe""" /RegServer
"""%11%\logagent.exe""" /RegServer
So I made another run without HFAAO, HFCABS, HFEXPERT, HFSVPCPACK, HFSVCPACK_SW or HFCLEANUP and I still got the error. The file, logagent.exe, is in a reducer and that is reflected in the script. I got the same error with and without that reducer.
In addition, on my test runs with HFCLEANUP taken completely out of the picture, I got a new error that I hadn't seen before:
QUOTE
(Window Title: Windows Update)
An error ocurred calling "DllRegisterServer" in "C:\winnt\system32\inetcomm.dll". (HRESULT = 80004005)
But adding HFCLEANUP back fixed that (part of the OE reducer).An error ocurred calling "DllRegisterServer" in "C:\winnt\system32\inetcomm.dll". (HRESULT = 80004005)
Back to the wmfdist problem, I also tried adding the cabbed file (logagent.ex_) to FIX but that didn't help. Also tried different Compression Types (A and C) as well as test release 6a and 8a but got the same results.
The only fix for this for me is to remove wmfdist.exe. What am I doing wrong?
Thanks, TAiN.
It had nothing to do with the recent WMP10 changes.
Windows 2000 copies logagent.exe and laprxy.dll into the Windows Media Player folder by default, but WMP9 and WMP10 expect it in the system32 folder. I worked around this problem when WMP9 is slipstreamed, but forgot that wmfdist.exe also has these files and also expects them in system32.
Fixed now.
It had nothing to do with the recent WMP10 changes.
Windows 2000 copies logagent.exe and laprxy.dll into the Windows Media Player folder by default, but WMP9 and WMP10 expect it in the system32 folder. I worked around this problem when WMP9 is slipstreamed, but forgot that wmfdist.exe also has these files and also expects them in system32.
Fixed now.
Working on the inetcomm.dll problem.
The IE5 section from the Update Rollup's INF isn't taken account of properly. I fixed it in an internal build and am testing it out in a VM right now.
Otherwise, Win2K with IE5 is AOK (WMP9 too).
Malmsteen's Odyssey album is helping me keep up the pace...
The IE5 section from the Update Rollup's INF isn't taken account of properly. I fixed it in an internal build and am testing it out in a VM right now.
Otherwise, Win2K with IE5 is AOK (WMP9 too).
Malmsteen's Odyssey album is helping me keep up the pace...
Hmm... This inetcomm.dll problem is also there with the current final. Would the OE5.5 hotfix be causing this? This needs some thorough testing....
Yup... It's the hotfix. Will see what can be done about it. In the mean time, don't include it... or use IE6, heheh.
Just FYI for those of you wondering "why is he using that old crap anyway?"
I use TommyP's reducers to effectively nuke IE/OE. I do this because FDV does too good of a job and I can't use FDV+Oulook.
But some stuff remains. So using those patches ensures that the leftovers are at the latest patch level, and then the extra stuff gets stripped out by HFCLEANUP.
I use TommyP's reducers to effectively nuke IE/OE. I do this because FDV does too good of a job and I can't use FDV+Oulook.
But some stuff remains. So using those patches ensures that the leftovers are at the latest patch level, and then the extra stuff gets stripped out by HFCLEANUP.
Win2K with IE5 is done. The inetcomm.dll binary from the OE 5.5 cumulative update has a broken registration section (deja vu anyone?)....
HFSLIP (61010a) is letting Windows setup register inetcomm.dll from the Update Rollup (which is OK) and then overwrites the file with the version from the OE 5.5 hotfix. This is the same procedure as for the webvw.dll binary on non-English Win2K sources. All fine with Windows Update.
HFSLIP (61010a) is letting Windows setup register inetcomm.dll from the Update Rollup (which is OK) and then overwrites the file with the version from the OE 5.5 hotfix. This is the same procedure as for the webvw.dll binary on non-English Win2K sources. All fine with Windows Update.
Thanks for your hard work on this, Tomcat76. You did a great job as usual and this is working fine for me now!
WoW! You are making great things here
I'm a bit confused about all new features added and said in this thread. Tomcat76 is the information on HFSLIP website about using all this stuff - HFANSWER.INI and external plugins - right or needs updating?
Sorry I missed a lot
Need some help getting into it again 
I'm a bit confused about all new features added and said in this thread. Tomcat76 is the information on HFSLIP website about using all this stuff - HFANSWER.INI and external plugins - right or needs updating?
Sorry I missed a lot
Need some help getting into it again
Hi Oleg... Nice to see you back!
Hope everything's OK.
The web page is up to date as far as the current final is concerned but it needs modification for the upcoming version. Please refer to the changelog in this thread if you want to use a test release.
Hope everything's OK.
The web page is up to date as far as the current final is concerned but it needs modification for the upcoming version. Please refer to the changelog in this thread if you want to use a test release.
Oleg2 - Welcome back. Hope you are doing OK. Nice to see you back!!!!
Welcome back Oleg.
@Tomcat: 2000/XP no longer need msxml3.msi if 923191 is included (only exception is 2000 SP4 without the Rollup).
the_guy
@Tomcat: 2000/XP no longer need msxml3.msi if 923191 is included (only exception is 2000 SP4 without the Rollup).
the_guy
I'm keeping msxml3.msi on my list for the resource file.
BTW, I suppose it's a mistake from MS to say that KB924191 updates both MSXML2 and MSXML3 because it only contains an updated version of msxml3.dll -- not msxml2.dll.
BTW, I suppose it's a mistake from MS to say that KB924191 updates both MSXML2 and MSXML3 because it only contains an updated version of msxml3.dll -- not msxml2.dll.
Yes, it is a mistake.
The reason I suggested it is that the resource file is the exact same version as the one included in XP SP1/2, as well as the Rollup for 2000.
the_guy
The reason I suggested it is that the resource file is the exact same version as the one included in XP SP1/2, as well as the Rollup for 2000.
the_guy
You are right about the resource file. It's the same version as the one in the 2K rollup. I guess the newer date confused me.
I'm now doing a thorough check of all files and will update my lists accordingly...
I'm now doing a thorough check of all files and will update my lists accordingly...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.