Super-Magician

Actually, you are wrong. The RTM version could be anywhere from the 57xx series to the 59xx series. However, the build number of the final release will be MANUALLY changed to build 6000. So, technically, the RTM build number is 6000. In case anyone is still wondering, build 5717 is part of the RTM fork and was released recently to TAP testers. TAP will receive weekly builds until Vista is finalized. Despite reports, build 5717 will NOT be released to Connect. Nevertheless, TechBeta testers will still continue receive various builds. Vista, at this point, is expected to be finalized on October 25. However, this date is likely to change based on Microsoft's often unpredictable delays.

@glentium, is that for XP or 2000 or what?

I suppose that Microsoft just updated the readme file for the program. I downloaded my copy of the file back in April so it doesn't appear to have been updated at all.

Thanks.

List updated for new hotfixes. Please see changelog for more details. Enjoy !

List updated for new hotfixes. See changelog for more details. Enjoy !

Hmmm...can't find KB920883 on Microsoft's site. Oh, well. Thanks for the list!!

@muiz, I would recommend you read this .

The final version of WMP11 should be released on September 14th, and I'm sure we'll need support for it soon .

@rgoff, your WINNT.SIF file is definitely the culprit! It appears you are using the file provided by FDV on his site. Remove it from your FIX folder and everything should be fine . Good luck !

Would you please go to the forum to which I linked above? This is the HFSLIP forum. Your issue has nothing to do with this program.

Yes, I think this would be more appropriate.

As far as I know, Star Man, you cannot set on which drive Windows should install through unattend.txt or WINNT.SIF. You can only set whether Setup repartitions your hard drive structure or automatically selects a partition on which to install. However, if your D: is blank, Windows should pick that partition if you insert the following lines into the [unattended] section of your unattended setup file. Repartition=No FileSystem=* If you need further help, I would recommend you direct your question to the following forum as this is not the forum for unattended install issues: http://www.msfn.org/board/index.php?showforum=70

*gentle bump*

*gentle bump*

So, what are we deciding? Changing the actual version number of HFSLIP to something like "HFSLIP 1.9"? Or just modifying the topic?

Wow, that was a quick reply!! I'd prefer the PDF.

I think this would be a good idea .

cdburn will not burn DVD. To do that, you must use dvdburn, which is a separate file.

Updated KB918899 to v2.

HFSLIP takes about 20 minutes to run on my (relatively-slower-than-some) computer (2.4GHz + 1GB RAM). Therefore, I am not saying that Yzöwl (or you for that matter) is/are wrong. I am simply stating that HFSLIP does take a long time for some people.In agreement with what you said, I am not too supportive of this idea. I am just happy that my computer doesn't take very long (and is not bogged down by spyware and junkware...I think ) .

I am sorry that you have taken my statement to be an assumption. I based it on what I saw in many HFSLIP.LOG files that have been posted across this forum over the past few months or so. There are some computers that take about 20 minutes to run HFSLIP (similar to my box) and others that take as much as 58 minutes. Yours by far takes the shortest amount of time (~6 minutes).I hope that you don't assume that what people say are assumptions.

For people with slower computers (that is, people who don't have your computer), HFSLIP can take anywhere from 15 minutes to even an hour long to run.

If you have enough hard disk space, Killgore, you should just make more than one HFSLIP folder.

It's not as simple as just replacing all instances of SOURCE and SOURCESS. Tomcat needs to add additional commands. The bloat I'm talking about is this: A few months ago, Tomcat introduced support for a custom location of EXPAND.EXE. He then replaced all instances of EXPAND or EXPAND.EXE in the script with the variable %XPAND%. However, TommyP, the author, objected to this as it unnecessarily increased the script's size and this feature was removed. You are the only such user (as far as I can tell) who has requested such a feature. If additional users support it, Tomcat may add it.