
tommyp
PatronContent Type
Profiles
Forums
Events
Everything posted by tommyp
-
Check out http://www.msfn.org/board/index.php?showtopic=59017&st=50. Perhaps it may help. HFSLIP isn't really geared for a multiboot cd at this point. Also, after running hfslip, any references to sp4 are removed, so it appears you are using a modified txtsetup.sif or dosnet.inf file. If you do that, hfslip won't work.
-
@Yzöwl - I changed a setting on this messageboard's control panel, which ironically turned off the PMs. It's all fixed now. I'm in process of writing up the HFCLEANUP section. What will it do? It will be a file reducer and inf modder. I guess it could be used as an nlite program, but it will need files generated by the computer gurus as I'm not familar with all the installation INFs & files. I'm doing some final testing before I post a new message on the hfcleanup... it will be alpha status since there is lots to do there to reduce the source. So far, I got my sourcess to 160 meg or so with 2k/ie6/dx9/codecs with the new type of hfcleanup. There's some more work I need to do though.
-
Is it possible to rip out the old drivers and use the SP1 drivers instead? Maybe nlite them out?
-
Cool find Crash. Thanks! Seems that the way to slipstream the new media player is to put the dll in the hfexpert\win\system32 and the exe (renamed) in the win\appreplacement folder.
-
Ummm, don't you mean APPREPLACEMENT?
-
If these packs are repacked switchless or switched installers, place them in the right svcpack folder for installation via svcpack. I will only work with microsoft downloaded binaries, so you won't see them slipstreamed by hfslip. Sorry dude.
-
I don't plan on doing XPSP1 stuff, but here's what you have to do. Edit the script as follows. Find this part (it's sort of close to the top). IF "%VERSION%"=="XP" ( SET T1=TommyP's HFSLIP XP/WMP10/WUA20 Hotfix Slipstreamer TITLE %T1% CALL :FOLDERPREP SET PREP=%~dp0 SET SP=SP2 CALL :SLIPSTREAM ) Change the SET SP=SP2 to SET SP=SP1. I really don't support this and I haven't tried it, so you are on your own. If you have success, please post back. Another option is to slipstream the old working driver using the HFEXPERT folder.
-
@nite: Please review these instructions at step 11. You have hotfixes that are named incorrectly.
-
@saugatak - A1 - Yes; A2 - Yes.
-
@Oleg, Please read the new instruction set for the extra files and HFEXPERT. I sent you the advance copy of the instructions yesterday. The new method is more intuitive than previous HFSLIPs.
-
I took a look at the guts of the MDAC installer (the 2.8 one). It's loaded with lots of garbage that defeats the purpose of my lean machine (I rip MDAC out because I don't use it). However, it is possible to install it via svcpack and a cmdline. Perhaps I'll do a little mod to the script so it installs that way. Also, on the mutiboot cd, can you try installing it the old-fashioned way with one OS on the cd and see if it works. I don't want to chase my tail on this issue. Everything works fine on my side, so I'm not sure what I'm missing. Last thing, to check for your updates, can you run the MS Baseline Analyzer? That tells tons more than a visit to the windersupdate site.
-
@pain, thanks for the info. About the windowsrollup. Are you still doing the network installation? Remember, HFSLIP is for a CD installation. With a CD install, all the files are there as are the registry changes. As far as the HFEXPERT thing goes, I don't plan on going to wild with dosnet.inf and HFEXPERT. Dosnet.inf isn't needed for a CD install.
-
Why is it on my side, if I use HFSLIP with FDV's beta set, SYSOC.INF gets processed properly? What am I doing wrong that mine is working?
-
I plan on having two versions of HFEXPERT in the future. One is to just slipstream it along with the source (which works now). With this method, anything placed there will overwrite any existing binaries on a CD. But I also plan on having anther HFEXPERT structure where you place files/folders a different HFEXPERT subfolder. With the latter method, the folders you create will be additonal folders inside the I386 folder, so no binaries will overwrite. There may be some overlap there, but tinkering with txtsetup.sif is pretty limited. Anyway, with the code I presented in the post above, the files cannot be found on the cd. There must be something to put between the commas so the setup can find the files that are nested inside folders inside the i386 folder. I think this could be cool because you would be able to slipstream firefox and rip out IE. A perfect addition to the HFEXPERT hidden utility.
-
Sysoc.inf & txtsetup.sif & dosnet.inf (if it's there) are the only files that HFSLIP alters with FDVs source.
-
If you are working with FDV's set only, HFSLIP is expecting a sysoc.in_ file that is uncompressed. HFSLIP does it's magic, alters the sysoc file and when HFSLIP is complete, it cabs the file and puts it into the sourcess\i386 folder. If you place a CAB'd sysoc.inf file in the FDVFILES folder, HFSLIP will burp and not know what to do with it.
-
You need to see this line in the Components section of your sysoc.inf file (or sysoc.in_ file) after running HFSLIP. Otherwise INF aren't getting run. WinUpdate=Ocgen.dll,OcEntry,HFSLIPWU.INF,HIDE,7
-
If you just drop FDV's sysoc.in_ either cabbed or not into the finalized SOURCESS\I386 folder, you will NOT run any INF files that hfslip generates. I have a suspicion that the the rollup package runs a code to make the IE icon pop up on your desktop. Try adding this into your installation, like in an INF in svcpack. HKLM,"Software\Clients\StartMenuInternet\IEXPLORE.EXE\InstallInfo","HideIconsCommand",0x00020000,"""%11%\rundll32.exe"" ""%11%\shell32.dll"",OCInstall HideIE" or maybe FDV can have a post cleanup in his IE.INF file for me to HFSLIP to parse at the end.
-
I'm running into trouble finalizing Yzöwl's code (with some mods to HFSLIPify it). Can someone help me? Let's say your file/folder structure is this: SOURCESS\I386\FOLDER1 SOURCESS\I386\FOLDER1\FILENAME1.FIL SOURCESS\I386\FOLDER2 SOURCESS\I386\FOLDER2\FILENAME2.FIL What lines does txtsetup.sif need so that it finds the files during the file copy stage? The code below doesn't do it. What am I missing? [WinntDirectories] 1000 = "FOLDER1" 1001 = "FOLDER2" [SourceDisksFiles] FILENAME1.FIL = 1,,,,,,,1000,0,0 FILENAME2.FIL = 1,,,,,,,1001,0,0
-
@nite0859 - Thanks for posting. I'm too lazy to check out the versions. All I have to say is to be careful if quartz.dll and any wmp binaries are in the list. If you try doing additional ones, you may wreak havok on your system. So please be careful. On the flip side, if additional codecs are there, the binaries are registered during installation. Good luck and thanks for supporting HFSLIP.
-
Sorry dude, you are on your own with non-MSFT downloaded packs/cabs. HFSLIP's intent is to not slipstream other people binaries; I like to preserve genuine microsoft binaries. However, if you really want it slipstreamed, please generate a sourcecode and I'll add it to hfslip.
-
@Yzöwl - You da man. That's the coolest thing I've seen. I'm in the middle of integrating it into HFS. I think I like it when files are all crammed into one place. So I modded it a bit so it's all packed into i386. I'll see if there is a need to put it into additional folders in i386 later. I would prefer to have it all packed into one place. Remember, the intent of HFSLIP isn't to make a big source and to slipstream programs. But if the need arises, maybe I'll have to change my tune. Again, thanks Yzöwl, you create the coolest scripts.
-
Do you mean FDV's fileset or HFSLIP? I can answer for the latter: YES.
-
@pnkiller78 - Try swapping the halmacpi.dll from the rollup back into the system32 folder. Test that out. It was a buggy dll that won't make your PC happy, but will make WU happy. Thanks for the scripting, I'll see if it all works, and if it does, I'll incorporate it. Thanks for the help! @dziubek - Are you getting the copy error during the txtmode copy stage? Are you installing from a CD? I just did an english version here on a real box and it works fine. Are you installing anything else to cause this? Check the version number of that dll in the sourcess folder. Google for the version number. Oh and see if it's a QFE type.
-
You need to increment the DIRNUMBER. Put this after your FOR line: SET /A DIRNUMBER=!DIRNUMBER! + 1. If the !'s don't do the trick, try %'s. Tell you what, I really don't want to craft this piece of the puzzle, but if you would like additional files/folder copied over, please generate a "plug-in" for hfslip and I'll incorporate it. As far as the W2K rollup goes. See if this does the trick. Rename the SYSTEM32\Windows Media\Server\NSCM.EXE to NSM.EXE. I thought I found that as a typo the other day and I corrected it, see if that file rename does the trick. Report back. I don't use WU, so I'll need your help with that.