Tomcat76

Heh... I figured the change applied to all extensions so I didn't try a different one. Thanks-- it works. Too bad there's no global hack (doesn't work from HKLM or HKU) but I can live with that.

That's besides the point. As said, the codecs aren't the issue. Besides, I don't need big codec packages when it all works fine with just a handful of files. I use CoreAAC.ax coupled with MP4Splitter.ax to play M4A and AAC files. FFDshow also slows down the mouse movement when the config panel is open. @boooggy: Any idea what I need to enter into the registry (and where)? This is what I use to associate the files with WMP9, so what do I need more? HKCR,".aac",,,"aacfile" HKCR,".aac","Content Type",,"audio/mp4" HKCR,"aacfile",,,"MPEG4 AAC Audio File" HKCR,"aacfile","EditFlags",1,00,00,01,00 HKCR,"aacfile\DefaultIcon",,,"quartz.dll,-203" HKCR,"aacfile\shell",,,"play" HKCR,"aacfile\shell\play",,,"&Play" HKCR,"aacfile\shell\play\command",,0x00020000,"""%programfiles%\Windows Media Player\wmplayer.exe"" /Play ""%L""" HKCR,".m4a",,,"m4afile" HKCR,".m4a","Content Type",,"audio/mp4" HKCR,"m4afile",,,"MPEG4 Audio File" HKCR,"m4afile","EditFlags",1,00,00,01,00 HKCR,"m4afile\DefaultIcon",,,"quartz.dll,-203" HKCR,"m4afile\shell",,,"play" HKCR,"m4afile\shell\play",,,"&Play" HKCR,"m4afile\shell\play\command",,0x00020000,"""%programfiles%\Windows Media Player\wmplayer.exe"" /Play ""%L"""

Alright. Could I have the TXTSETUP.SIF and HFSLIPWU.INF from SOURCESS\I386 then? I want to double check that the HFSLPxxx.INF files (which contain additional registry stuff for hotfixes) are processed during installation and that there's nothing in HFSLIPWU.INF that causes it to close inadvertently.

I noticed recently that ReClock cuts off the beginning of quite a few of the media files I got. Today I finally figured out the cause. The pre-buffer is set to 500ms by default but media files are muted for that extend of time during playback. A lot of the media files on my computer have a "lead-in silence" of only 128ms (approx.) so that explains the borked up sound at startup. I fixed it for me by lowering the pre-buffer to 126ms (and setting the max PCM latency to 100%).

What would happen if I only added a few selected ones, like .M4A and .AAC? Would it then at least stop complaining about these?

DOS-initiated installs and upgrades are not supported. These are the show stoppers but there may be more: - DirectX9 - Package Installer There might be a way to fix the Package Installer problem but DirectX is a real PITA.

I don't think HFSLIP handles the DRM update (WindowsMedia-KB891122-x86-NLD.exe) as is. If you wanted the newer MP9/10 codecs, you need to extract wmfdist95.exe from it using an advanced compression program like WinRAR or 7-zip. Other than that I don't see anything out of the ordinary except that you're using an old version of HFSLIP. Try the latest test release (60330a) from the other thread and remove the DRM update (and add wmfdist95.exe into HF if that's what you intended to do). After installation, set up the AU service to only download new hotfixes. If many are downloaded, go to the Windows Update site (or an alternative download site) and see what it says there.

Thanks for replying. Well... That's not what happened. I wrote inside the first post what title I typed. It wasn't all caps.

No, it's not silly, but those hotfixes are not freely available. You need to call MS to get these and I don't think anyone here would do that just to see if they work with HFSLIP. Make your CD with what's supported first. If it works, add in those additional hotfixes and check again. If you come up with a list of "kbwinxpsp3fix" hotfixes which don't work with HFSLIP you can post it in a separate thread for the community.

2nd file copy? Are you installing by booting off the CD?

I noticed in some of the subforums here that titles are being edited. Many words get a capitalized first character and typing "WMP" is not possible (it's edited to "Wmp"). Is this a board feature? Edit: The title of this thread is supposed to be "Titles are sometimes being edited by forum software". A clear example...

I associated m4a files with WMP 6.4 on Win2K and it's working fine. Now I did the same thing on XP but I got this annoying warning message. Here's what happens (on XP)... I double-click the m4a file and WMP9 opens. Instead of playing the file, I get an error telling me that the extension is unsupported but that it may be able to play it back anyway. Below that is a checkbox with a description that I don't quite remember anymore but it comes down to "Don't ask me again". Clicking OK/Yes kills the error dialog and the m4a file starts to play. The second time around, I checked that checkbox and clicked OK/Yes. That was actually a stupid move... I should've used Advanced Registry Tracer or a similar program to take a snapshot of the registry before doing so and once again afterwards. Now I don't know what the reg hack is (if there is one) to get rid of this useless warning. I searched on WinGuides and also the Internet but couldn't find anything relevant thus far. Every result deals with people not installing the appropriate codecs (or not knowing they need additional codecs) but that's not the issue here. What would actually be better is a way to tell WMP9/10 which additional file types it shouldn't warn about but I couldn't find info on that either...

No problem. Glad you got things sorted out...

What does Windows Update say? MSICabExtract.exe is not used by HFSLIP for the msxml.msi and msxml6.msi files since March 1st. I never mentioned that...

Well... KB901190 (Vulnerability in Korean IME) didn't slipstream (which I'll investigate) but for the rest everything's fine on the computer I installed XP SP2 Dutch on two days ago. Your ERROR_REPORT.TXT might help...

You probably meant spupdsvc.exe. Those two files are taken from KB898461 (the package installer). Can I also have a look at your txtsetup.sif file?

I once had mistakes on the partition I ran HFSLIP on. I got copy errors during installs and on different computers. A CHKDSK on the drive showed the problems and fixed them (some of the "damaged" files resided in the SOURCE folder). Then I deleted the SOURCE folder and copied the files from CD again. The problem was gone. I only changed the handling of SPX.CAB in those spx test releases. "wind_w.chm" isn't part of SPX.CAB so a copy problem with this file couldn't have been introduced with those releases.

I built a complete Dutch XP CD with HFSLIP two days ago and installed it on a computer but I haven't connected it to the Internet yet. I'll test this in a while...

When do you get these copy errors? Do you have spmsg.dl_ and spupgsvc.ex_ in your SOURCESS\I386 folder?

Test releases: http://www.msfn.org/board/index.php?showtopic=69809

For a few days now, I noticed in some posts that quotes are not properly quoted. I just experienced this in one of my own posts. Any idea why this is happening and if there's something I can do to fix it? Edit: Never mind. I had 6 quotes in my post and one of them had an ending URL tag instead of an ending QUOTE tag. Strange that this breaks all 6 quotes. Oh well....

Please note the difference: HFSPACK and HFSVPK. The first folder is for the Service Pack file and the second folder is for switchless installers. According to your latest ERROR_REPORT.TXT, you placed the Service Pack in the folder intended for switchless installers. You have to move the Service Pack into HFSPACK. RyanVM's .NET 1.1 will work (put it in HFSVPK <-- note the name!) but RyanVM's .NET 2.0 only works from GUIRunOnce which HFSLIP doesn't support. Some people had success with Zxian's .NET 2.0 installer (this would go in HFSVPK too). It's important that every file that originally had "Windows" in its name still has "Windows" in its name. Also, for some hotfixes, "KB######" is required. There is no way right now (except for manually deleting the CAT files and editing SVCPACK.INF), but wait with that for now. You should first try to work with HFSLIP the way it was designed to be used. Hotfixes which were never listed on the hotfix pages on this forum were never tested so problems may arise. I strongly suggest you use the hotfix pages on this forum as a guide for now until everything works. After that, you can start adding back the additional hotfixes. It is possible through the HFCLEANUP feature but someone else here will have to tell you what to do. I'm not that familiar with it.Here's what I suggest you do (if you haven't done so yet): 1) Download the latest test release (60328c) and extract the HFSLIP_60328c CMD file into your HFSLIP folder 2) Move the Service Pack file from HFSVPK into HFSPACK 3) Move away (for now) all the hotfixes which are not listed on the hotfix pages here 4) Move away the winnt.sif file After that, run HFSLIP (60328c) and make your CD (don't use nLite or anything else). Install Windows and see how far you get.

Did you put blackbox.exe inside HFEXPERT\WIN\blackbox?

A couple of remarks... 1) If you want to let HFSLIP slipstream the Service Pack, you need to create a folder called HFSPACK inside HFSLIP and place the SP file (Network Install version) in there. Not in HFSVPK. 2) Addons don't go in the HFSVPK folder. They go in HFAAO which you also need to create yourself. 3) Where are you getting this "DOTNETFX.EXE" from? HFSLIP doesn't support the one from Microsoft. If it's a silent switchless installer for .NET 1.1, it should be moved in HFSVPK. Kiki is using a winnt.sif file...

You know... I changed one specific thing in each of those spx releases and they couldn't have caused this new problem. Are you using CDIMAGE.EXE or MKISOFS.EXE? If the latter, is it a release that needs CYGWIN1.DLL? Other than that, I'd say try a CHKDSK /R on the drive you're using for HFSLIP.