hi!
you may try looking into this if it would be any help ...
http://www.vorck.com/hfexpert.html

APPREPLACEMENT: Create a folder in HFEXPERT called APPREPLACEMENT. Place a renamed EXE file that is part of Windows.
Example 1 - SysInternal's Process Explorer, Renamed to TSKMGR.EXE
Example 2 - Media Player Classic, renamed to MPLAYER2.EXE

if i'm not mistaken mplayer.exe is for the classic media player that was in use in the DOS-based OS while mplayer2.exe is for the newer one that are in use in the NT-based OS ... ver diff

oops ... sorry for the late post ...
the page i'm in was not refreshed

Could You add new capabilities to already gigantic possibilities HFSLIP about next :


* If I have turned off WFP (hacked sfc_os.dll) I would like to have the possibility automatic the removing the files of CAT in catalog SVCPACK and file svcpack.inf


** It addition support for r XPize - Creating a XPized Windows ISO
Is compatible with nLite's hotfix integration.
http://xpero.msfn.org/?page=home



*** The integration the KB 905474 with source of installation


In advance thanks for considering suggestion

dziubek

Why do you want to remove the catalog files? They are required for Windows Update to think that the hotfixes are installed.

KB905474 cannot be integrated/slipstreamed because there is nothing to download. The KB article is just a informational page describing the Windows Genuine Advantage Notifications application. The application is installed/executed when Windows Genuine Advantage fails to validate a copy of Windows.

Although according to the KB article you can uninstall KB905474, I do not think you can slipstream it.

Also, why would you slipstream it in the first place? Does Windows Update/Automatic Updates ask you to install it? Isn't the application just a nuisance if it keeps popping up to say your Windows isn't genuine?

@dziubek...

What's that install prompt you're getting when going to the Windows Update site? What are you being asked to install?

I don't really understand your problem with My Documents. When you install on a VM, does Windows think your documents are located in C:\My Documents?

It's to be called "mplayer2.exe", yes. Appreplacement replaces files in I386 and the file you want to replace is called "mplayer2.ex_".

I've taken a look at the XPize program but I fail to see how nLite is being told which switches you want to use. Also, does this work from SVCPACK?


@Kiki

Try mplay32 from Run. That's not "the DOS player" but WMP 5.0.


It would be more of a nuisance if it flashed "Thank you for using a genuine copy of Microsoft Windows!" once in a while...

MBSA2 does not complain if they are removed and it uses the same engine as WU.

I believe MBSA is actually *downloading* the signatures before checking the files.

I'll check asap (maybe Saturday) but I don't think it does.

Windows File Protection prevents the replacement of protected system files such as .sys, .dll, .ocx, .ttf, .fon, and .exe files. Windows File Protection runs in the background and protects all files installed by the Windows Setup program.
Windows File Protection detects attempts by other programs to replace or move a protected system file.
WU only checks for the reg entries and the file versions, so its no problem,but QFECHECk will say you you have to reinstall the most of the hotfixes.
Windows update scans for file versions. Not the cat files so windows update will still recognize the fact that Windows has been updated.
CAT files are used to register the files with Windows File Protection, so it knows they're valid and doesn't try to replace them.When I delete cat file from hotfix .All files from this hotfix will appear to be unsigned and won't be protected by Windows File Protection.If you disable sfc you dont need the cat files.
According to me after removal the files of CAT the installation runs more considerably quickly.

http://www.ryanvm.net/forum/viewtopic.php?t=553

dziubek

hi!
what i meant by this was that basically this media player is the one present with the lower OS vers (i.e., Win98 & the like)
my apologies if it sent the wrong msg

as for removing the cat files, i agree that this actually hastens the installation process as i used to experience being stuck at 39 mins without any progress (for long hours) ... which was kinda apparent when i used nLite to slipstream multitude of hotfixes ... if i may quote:


and i think tomcat76 would try to look into the possibility of adding the capability to do so via HFSLIP, right?

thanks!

@Kiki: You didn't send the wrong message. I was just mentioning it as an aside.


407b is out. Support for XPize plus optional removal of CAT files if sfc.dl_ or sfc_os.dl_ are detected in FIX.

WOW , I get for tests :-) Great respect for your support.

dziubek

I have read that there were some issues with xpize with media player compatibility. They may be fixed, but I just wanted to caution the users. If there are any issues with xpize, please report them to the proper forum. TC - Please state this when updating the main page when the beta gets out of beta phase.

On a sidenote, I tested xpize on 2k. It seems to work. Not sure if there are any issues yet. It's funny seeing an XP boot up screen on a 2k box.

Just an FYI... XPize is not slipstreamed. I asked for more info on this a couple of posts back but nobody got back on that. It is merely being installed through SVCPACK.

According to me You should contact Xpero yourself to get the necessary detailed information for You
http://xpero.msfn.org/?page=contact
http://www.msfn.org/board/index.php?showuser=26650

or on forum?
http://www.msfn.org/board/index.php?showforum=112

dziubek

Updated.

XPize**.exe in HF folder ==> slipstreamed
XPize**.exe in HF folder + answer file in HFTOOLS folder ==> silent svcpack install

Note that you'll probably need a modded sfc.dll or sfc_os.dll file if it's going to be slipstreamed. I'll add a check for the presence of these files in the next version.


Edit: Done.

You're incredible. :

Funny... My imaginary wife tells me the same thing...

TC your're so proactive in incorporating suggestions like the removal of CAT files!
this is great!

i'd like to learn though how to use, edit & implement sfc.dl_ or sfc_os.dl_ in the FIX folder ... as i've yet to confirm that it's presence is probably causing some issues for me (just like the ones i posted in the thread: HFSLIP, The 2K/XP/2K3 slipstreamer

thanks much!

test 1:
*The files of CAT don't delete y when I choose Y
*Xpize doesn'tt swap files

When I start Creating ISO by Xpize using SOURCESS all by hand it acts correctly.

in atest2:
I changed in FIX the name of files on small letters

*The removing the files of CAT doesn't act
*Xpize doesn'tt swap files

dziubek

p.s
In attachment I added the list of files overwritten by Xpize

Since HFSlip successfully slipstream service packs, wouldn't it be logic that it creates the corresponding folder on startup ?

Thanks.

dziubek - I found some coding probs and alerted TC about the fixes. There were about a half dozen or so. Please give a bit for TC to incorporate them.

Camarade_Tux - Good point about the extra folder creation on initial startup. All my source folders have the latest SP level so I never really bothered to think about it.

@dziubek -- Try the new version.

@Camarade_Tux/TommyP -- What folder?

TC, the HFSPACK folder.

Done.

cool.

Thanks.


Someone told me HFSlip didn't simply use /integrate. What else does it do ?

Camarade_Tux: Look at the script !

Can't really elaborate on exactly what it does. Ask TommyP !

I always forget hfslip is open.
Reading the source right now.

I found nothing special. :/
Except that the source is nearly 2000 lines long.

HFSLIP extracts the files in Type 1 and Type 2 hotfixes to a folder in the directory called "TEMP". It then deletes the tons of junk files and copies the necessary files to its WORK directory. Later on, when HFSLIP says "Total Slipstreaming" in the title, each file is compressed using MAKECAB and copied to SOURCESS. If you open the WORK directory while HFSLIP is in its early stages (extracting hotfixes, slipstreaming, etc.), you'll see many folders. Although in most cases most of the folders are empty, in (I think) I386E you will find the new files (from the hotfixes). If you choose compression options A-C, after HFSLIP copies the files from the SP*.CAB file, and before it CABs the DRIVER.CAB file, you'll see HFSLIP copy certain binary files to the DRIVER directory.

Just a brief, technical description . For a more basic description, see TommyP's post below.

HFSLIP does two things. First , it slipstreams the latest binaries to the sourcess folder and second it creates INFs files on the fly depending on what you are slipstreaming. A few months back before MSFT started adding files to your OS, the WU issues were mainly registry related. We got that part figured out. Now, the problems that generally arise are when MSFT *adds* additional files. But I think TC and I have a hold on that now. On the flip side, if you are trying to slipstream garbage, then you'll get garbage. Garbage in=garbage out.

@Camarade_Tux -- If size really matters, check the latest...

Now I need to lie down for a while... I'm not gonna explain what I did with those lines...



Thanks to TommyP, btw... He gets the credit for the last couple of updates...

I'm not using any file replacement, only updates. Then I use nLite and patches uxtheme and sfc_os.
Do you think latest version will result in smaller iso ?


@Super-Magician, tommyp thanks for the explanations.


Also I've seen a modified sfc_files.dll on vorck.com
It disables sfc by providing an empty list of protected files.
Who has tried it ?

That update is about the length of the HFSLIP source. It should be nearly 1990 lines now...

The sfc.dl_ on fdv's site is for 2k and I use that file all the time with 2k. It *may* work with xp, but you'll have to rename it to sfc_os.dl_, xp uses a different filename. I haven't tried it though.

In fact, I was thinking about that:



Tomcat, OK
btw I'll make a new iso on Wednesday.

@Tomcat76

More possible changes:

1. Update startup screens in HFSLIP with relevant new info. By this, I mean for newly added changes/updates. For example, the file and folder format list (third screen) should have HFSPACK listed in it.

2. Rename HFSVPK (and ultimately HFSVPK_SW) to something that doesn't have people confuse it with HFSPACK when they want to slipstream a service pack. The two names are very similar, and are indeed if spelled out.

3. Possibly permanently rename the ERROR_REPORT to HFSLIP, like it is in SOURCESS. But only if you see a need and if other people support this. If you do so, however, you would need to change the documentation.
*I guess this will happen eventually, but for now, we can just let it be.

I used HFSLIP_60409a.CMD.

* The files of CAT were removed
* Xpize overwrite files correctly

HFSLIP doesn't create ISO because error appears:
"
CDIMAGE 2.47 CD-ROM and DVD-ROM Premastering Util
Copyright © Microsoft, 1993-2000. All rights r
For Microsoft internal use only.


ERROR: Could not open boot sector file "HFTOOLS\"
Error 3

Your ISO is here: D:\HFSLIP\WINLite.ISO
"


thanks

dziubek

@dziubek...
Whoops... I created a variable called BBIN but I was referring to it as BBBIN later on...



HFSVPK and HFSVPK_SW are now called HFSVCPACK and HFSVCPACK_SW respectively. Should HFSPACK be renamed too?

How does HFSLIP.LOG sound instead of ERROR_REPORT.TXT?

Small request: please make a summarization post for clarity once all of these changes are implemented.

Of course. But it might take a while. It looks like the WMP Classic skin still doesn't copy over properly and I want to tackle this before a new final is released.

Thanks for implementing my requests. HFSLIP.LOG sounds great. However, the names "HFSVCPACK" and "HFSVCPACK_SW" sound a bit too lengthy. Now that I think about it, I think the original names were fine. How about renaming HFSPACK to something?

Edit: By the way, not to be annoying or anything, make sure you first get tommyp's approval for changing the names of the folders. FDV's site and your update pages would also need to be revised if they do get in.

Approval already given for the hfsvcpack. Don't worry if they are too lengthy. For us old timers that have been using hfslip since it's inception, the script will automagically change the foldernames to this new scheme.

Standing by for documentation changes.

On a different subject... SFCFILES.DLL by the way works on ALL versions of Windows, just to clear that up. SFC.DLL and SFC_OS.DLL are different matters entirely. You can use SFCFILES.DLL and no other modified binaries and SFC will be disabled. To recap, for the confused

To shut Windows File Protection off:
Use a modified SFC.DLL in Windows 2000
Use a modified SFC_OS.DLL in Windows XP and Windows 2003
No need for a modified SFCFILES.DLL

To disable Windows File Protection causing it to check an empty list:
Use a modified SFCFILES.DLL in ANY version of Windows
No need for a modified SFC*.DLL

For complete overkill, so that Windows File Protection is shut off AND has an empty list which it doesn't even check:
Use a modified SFC.DLL in Windows 2000
Use a modified SFC_OS.DLL in Windows XP and Windows 2003
AND Use a modified SFCFILES.DLL in ANY version of Windows

So, are we just about ready for another final ?

But don't forget - tomorrow's Patch Tuesday ! Another round of hotfix troubleshooting coming up !

I will test this version. I don't think you should release another final until we make sure the five new hotfixes don't clash with HFSLIP.

sfc_files.dll on vorck.com is not quite well compatible with winXP ...
this is what i'd actually report to tommyp & Tomcat76 in a different thread ...

I use for winXP this file:
http://addons.ryanvm.net/ryanvm/RVMAddonsSFC_1.0.cab
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=
dziubek

@FDV: You provide us with tons of info for disabling WFP, but I've never seen a compelling reason to do so. Does WFP involve a lot of system overhead?

@ Tomcat76

1. Can you add except acceptance the Y also the y by choice the removal of files of CAT ?

2. Can You be able to add for driverpacks (BTS drivers) support?
http://www.driverpacks.net/

P.S I use HFSLIP_60410a.CMD.
ISO creates now correctly
dziubek

hi dziubek!
this is what i've used likewise to come up with successful builds ...
i remember seeing your msg before about being stuck at T-9 & i suppose you used the same file too ... & perhaps resolved it by using the file from RyanVM ?

btw, would this cat removal an option that the new test release already shows? i mean, i did not see it using the test release cmd ... how can this be done?

thanks!

@tain
someone will pounce on me for this, but here goes.
i encourage people to really think about doing this... i turn it back on after i install. i am SO tired of installing apps and having them replace my dlls. i also do installs on systems other than my own (yeah, they're licensed, calm down you panicky types). the last thing i need is trying to troubleshoot someone's pc because some stupid game made for windows 95 replaced their ole32.dll when they installed it.

wfp is noticeable during the setup phase. each file that gets installed gets checked. switch WFP off and setup can really fly. i keep unmodified copies on the installed CD as "SFC.DLL.OLD" and etc. when i want to turn sfc back on, i do a switch by booting into safe mode or using bartpe.

@Kiki Burgh

well, i'm the guy who hosts the dll and source. i need to know what not quite means here. i'd love to see a link to that thread so i can see what the problems are.

hi fdv!
i meant no disrespect sir in fact, i have been waiting for you to comment on this too ...
i just found out about my issues when i took out those files that i downloaded from your site ... apparently, it's more for 2K than XP as explained:



btw, the sticky thread is here: http://www.msfn.org/board/index.php?showtopic=57659&st=150

it's great to hear from you!