Tomcat76

I suppose that's because you aren't including IE6. Maybe someone that keeps IE5 can confirm. I always include IE6.

Fixed. Thanks. I came across this problem once before, when I did the slipstreaming section. When you set a setter within a wrapper, it isn't yet "ready to be used" inside that wrapper. Really a stupid limitation of DOS...

Create a folder called HFSLIP in the root of your D: drive Place the HFSLIP program inside it and run it Copy the content of your CD into D:\HFSLIP\SOURCE Place the hotfixes in D:\HFSLIP\HF (etc) Run the HFSLIP program again Those files are for Windows 2000. According to your ERROR_REPORT.TXT file, you were using Windows XP. So which OS are you trying to make a CD for?

cmpnents, DOCS, I386, SUPPORT, VALUEADD, etc. all go in the SOURCE folder. Basically, "SOURCE" is your CD. Don't forget to include all the WIN51 files too. setup.exe and autorun.inf are only used when you initiate the install from Windows (ie, pop in the CD while Windows is running and wait for it to autorun). They are not used when booting the computer with the CD.

I'd like to release a final this weekend if there are no new issues with the latest test release. Nothing was changed in the way hotfixes or addons are handled so it's enough if you let Windows setup get through the initial file copy stage. @dziubek: Please try the latest test release. Hopefully your T-9 problem is resolved.

No. It's sad that the error messages don't provide more info. As far as I can see, it looks like what I'm trying to do can only be done through SYSOC.INF... which requires a lot of INF editing...

A few things were changed in the latest test release (60324c) which may fix the problems you are having. If they don't, I will have to conclude that HFSLIP is not compatible with Symantec Livestate Delivery at this point. I don't have that program so it's difficult for me to pinpoint the cause of the issue(s). I'd still like to have a look at the DRVINDEX.INF and TXTSETUP.SIF files from the SOURCESS folder after running 60324c. Maybe I overlooked something...

IE6 does. I don't know about earlier versions...http://www.w3.org/Style/CSS/Test/CSS1/current/test5526c.htm

That article is spot on. Do click the bottom link when using IE or a browser that uses IE's rendering engine. Since 1999...

Somebody over at the Opera forums made a screenshot of how IE7 handles the Acid2 test: http://my.opera.com/community/forums/topic...=50#post1411559 Funny comment, btw...

Is spx.cab present in the SOURCESS\I386 folder? Could I have your latest DRVINDEX.INF and TXTSETUP.SIF files (SOURCESS\I386)?

IE is a pain in the butt for modern, professional web designers and IE7 brings only marginal changes in the field of post-1998 standards support. Personally, I don't like the interface at all. I prefer "static" and "full customizability", something that's only available with Opera. @FDV: 8303 is a weekly. These are not as rigorously tested as the previews.

@dziubek: You're clearly mixing things. According to your ERROR_REPORT.TXT file, you're using 60322a but that version does not create MPDIR1.TXT. You surely forgot to remove it when you did a test with 60321a-wmp or 60321b-wmp before. Try removing things from the FIX folder. BTW... You got mplayerc.exe in APPREPLACEMENT. I could be wrong, but shouldn't it be named mplayer2.exe? @TAiN: The DX cabs are fully tested.

There's a newer version (60322a-wmp). It uses a whole new approach. It's still untested, though. I really don't have the time ATM...

If only that line needs to be added, try the latest test release (60322a).

That's right... I forgot about that...

It's clear it isn't ready for consumption yet. I've withdrawn it for the moment. MPDIR1.TXT is useless. It's a leftover from an earlier version of the WMP script section but it's not used anymore. I forgot to delete the line that creates the file.

I don't see anything wrong with the DOSNET.INF file. Do you still get copy errors when booting off the CD (ie, do a regular install)? BTW... The "x" in "spx.cab" doesn't stand for a random number; it's an actual "x". When you integrate SP4, SP4.CAB is created in the i386 folder. This package contains newer versions of files in DRIVER.CAB but MS didn't feel like updating DRIVER.CAB for you directly as it may use quite a bit of CPU power to do so. SPX.CAB contains newer versions of files in DRIVER.CAB and SP4.CAB which came with the hotfixes that you include.

I'll keep that in mind...

I think for Windows XP SP2 you should keep the original names of these: WindowsUpdateAgent20.exe LegitCheckControl.cab The other files should be fine as long as they have at least "KB######" in their name. 270~280 hotfixes? Are you sure you aren't using Windows '87? But seriously... I can't imagine you need all those hotfixes and I doubt HFSLIP handles them all. Check in my signature for the hotfixes you need for Windows XP SP2.

START /WAIT should work. I can't see a problem with that. Those link problems are really strange. About a month ago, someone said FDV had the wrong links on his site and I apologized a few messages later for not alerting FDV of this. I can't find that thread anymore, though. And now three times in a row. How many links does FDV have on his site? @FDV: the correct links are in my signature. They were all changed simultaneously a long time ago. I thought you were already aware of that for quite some time but apparantly not. Sorry if I got you confused.

@EmRoD The test release has been updated. There was a problem that may have prevented Windows setup from copying over wmfdist-related files.

@Kramy As far as I know, it is used when the installation is initiated through winnt.exe (floppy disk) or winnt32.exe (installation from within a running Windows). The errors you get when removing DOSNET.INF and doing a regular CD-based install (boot off CD) are probably due to DOSNET.INF being a "protected file". You need to hack some DLLs to shush Windows setup.

It's basically a "CD install" now which allows WMP to install completely (including playlists et al). The current implementation in the 60321a-wmp test release is actually about two weeks old already. The main drives behind this were to narrow down the size of the SOURCESS\I386 folder (as opposed to the SOURCESS\I386 folder now) and to get the background music going again during Windows XP installation. I have a feel that the latter was caused by the missing "control.xml" file. KB911565 didn't have anything to do with it.

I'd think not since it's newer than Windows XP, but try it. You don't need to run HFSLIP again for that; just edit your CMD in SOURCESS\I386\SVCPACK.