tommyp

@Squeeto - As long as your INF file and renamed EXE file are properly working, then if there is an update to your EXE, just place the new and renamed EXE file in the APPREPLACEMENT folder. I do this all the time with WMP Classic.

How was your runonceex done? SVCPACK? OEM cmdlines? Winnt.sif? Where do your installation programs reside?

HFSLIP works on a virgin source.

How did you install the programs last time with your unattend disk? How did you incorporate your runonceex previously? It appears that your system was functional because you were able to post your wu.txt file.

@dirtwarrior - No.

There's three options. If you are not using FDV's fileset. Put the renamed mplayer2.exe in the APPREPLACEMENT folder. Done. If you are using FDV's fileset, put the renamed mplayer2.exe in the appreplacement folder, delete FDV's mplayer2.in_ file, and modify sysoc.inf such that mplayer2.in gets installed. With FDV's mplayer2.inf file, it wants to put the exe file in a folder somewhere else. The last option is to run a commandline on the mplayer2.exe file once installed. You need to do a regaud and regvid switch to register the filetypes. Open mplayer to see the switches in the options. What I typically do is run with a modified mplayer2.inf and run a nice regedit at the svcpack level. All file types are associated for me. My regedit does the "Open With List" option.

TC - HFSLIP already takes care of the WindowsMedia8 fix.

It should not matter, HFSLIP does all it's regtweaks and such a minute before OEM CMDLINES is processed. A few things though.... Be sure to check if it works for your OS (seems like member contributions are geared for XP and 2K is neglected) and test on a VM to verify functionality. I can't see why it wouldn't work though. However, maybe a big however, be sure to run HFSLIP first and then integrate it with WPI using the SOURCESS folder. Report back on your findings. Thanks!

Squeeto - The file should be named mplayer2.exe. If you use NLITE, don't remove wmplayer 6, and don't use any modified mplayer2.inf's either (in other words, delete the mplayer.in_ from FDV's fileset. After that, you should be in businesss. Have fun replacing applications. Also, use the latest HFSLIP if you can. Sorry if I stepped on your toes Oleg2.

@trodes - Here's some help. Search the forums for the answers (it's the search window on top). 95% of the questions you have are already answered. I'll help you in this case. http://www.msfn.org/board/index.php?showtopic=23719&st=0

Help is appreciated if anyone wants to test and help the XPSP1 slipstream. Tomcat and I were testing and ran out of ideas. We are both slipstreaming the latest updates, DX9C and the Windows Update Agent. Please use the January 7,2006 HFSLIP or newer to test and evaluate. TC and TP issues: Quick Launch does not appear IE Shortcuts missing. Only way to run IE is to open Program Files\Internet Explorer and double click the iexplore.exe BITS update not installed (if a commandline is run, then all is fine). TC Issues: GLMDA.IN* file not found error when creating the start menu items. A WUA20 item isn't copied over. TP [non] Issue: MSJava update is being reported. (And I don't want to slipstream a buggy program either). Tomcat and I are unsure if there is a real need for SP1 slipstreaming, so we'll ask the HFSLIP community for their feedback and help.

New version up. Miscellaneous bugfixes, Oleg2 driver slipstream included, XPSP1 tweaks.

Layout.inf isn't touched by hfslip. It's a protected file and will cause problems in you want to retain SFC and not use modified setup dlls. @DmitryKo - When you ran HFSLIP it told you that it's geared for CD installations. Why is this a problem when you were already informed about this? Oh, there are no published methods for slipstreaming IE6 in a W2K source. HFSLIP started it over a year ago. For technical details of the setup process, microsoft has some info. Check out their site.

@trodas - This forum isn't for SFC discussions. If you need answers for SFC, please refer to FDV's site if you are using files in his fileset. If you're not using his SFC files, then google is your friend.

Why not let hfslip do it's job (without any FIX files), run NLITE, then swap files you want at the end? Also, that files to keep list for NLITE is only if you want media to play. If you don't care about media, then you can probably get away with keeping 10% of that list. I'm not sure what your goal is for your installation.

Changing apps is discussed in a thread here. I always thought it was something cool because other slipstreamers don't do this. http://www.msfn.org/board/index.php?showtopic=58362 Have you read FDV's site on sfc? Why not use his files that I mentioned in your other thread on the HFSLIP threads?

Is your SP2.cab corrupted? Can you expand it with winrar? As I mentioned before, installing via CD will give no troubles. Perhaps I sould ask FDV to remove that line from the instructions. What exactly do you mean when you say" But I've also made several Windows 2000 install CDs and upgrades were totally flawless (I started the bootable textmode setup to copy the GUI portion this time, not the WINNT32.exe) Windows XP is currently working fine as well, despite all the installation troubles." Do you mean that you had errors when it installed via a CD? What errors are you seeing when installing by cd? Why so many questions about installing by winnt.exe when the 2nd page of HFSLIP says that it is to be installed by a cd?

A sidenote, if the files you want to replace reside in the driver.cab, HFSLIP will not slipstream those if using the FIX folder. You'll need to that manually. Sorry, it's a limitation of HFSLIP that I really don't want to do.

The HFSLIP slipstream is to be used for a clean installation of windows. It will not work properly with running a winnt.exe command. You must use the HFSLIP install CD to boot the machine, delete your windows partition, and install windows on the "raw" partition of the drive. No winnt.exe commands are needed. The windows setup takes care of all of it.

The files you want copied over because you are not using the FIX folder correctly. The fix folder replaces files that are in the sourcess\i386 folder. For instance, assume that you did not fill your FIX folder and you ran HFSLIP. Your sourcess\i386 folder has a file called notepad.ex_. If you want a different notepad.exe in your installed source, your fix folder should have the notepad.ex_ too. You'll need to do a makecab on the notepad.exe to make it a notepad.ex_. If the filename in the sourcess\i386 was notepad.exe, then the file in your fix folder should be notepad.exe.

Just take one step at a time, slow and steady wins the race.

Sorry, I thought you were doing a 2k cd. Can you re-read the first line of step 3 of this: http://www.vorck.com/hfslip.html. Don't use punctuation marks (rename your folder to hfslipWXPEN). If there is a problem with WMP10, let me know and I'll see what I can do. In the (remote) event I need the windows bloat player 10, I throw the installer into the HF folder. Remember, HFSLIP is geared toward installing via a CD. If you don't run a cd installation, it doesn't work and you will get copy errors and files not found errors.

I see your posts on the nlite board. If you want to disable SFC, download FDV's fileset and extract the sfc.dl_, setupapi.dl_ and sfcfiles.dl_ into the FIX folder. Your SFC will be off and you can delete files at will. You must be warned, if you do that, you cannot run NLITE on the sourcess folder. NLITE doesn't like modified versions of these 3 files anymore. Are those notepad and other files getting copied over to somewhere else? Usually those files are in the system32 folder. Was it like that with the original sp2 build?

Use the HFEXPERT\WIN\SYSTEM32 folder and avoid long file names. This link http://www.vorck.com/hfexpert.html has all the info you want.

Are you doing steps 21 and 22 of this: http://www.vorck.com/hfslip-info.html and doing a clean install? It sounds like you are running a winnt.exe and a series of switches. Do a clean install instead and you won't have errors.