These versions are test builds and are pretty much stable. As usual, use them at your own risk.

A new final was released on November 9, 2009. If you were referred to this thread prior to November 9, please get the final from the main thread.

HFSLIP home page

*********************************************************
I hope tomcat76 doesn't mind me [tommyp] editting this post to add in a beta test build. See attachment for beta testing in preparation for the next final. Bugfixes:


There are no betas at the current time.



*********************************************************

You can help by checking if the binary removal files (2000SP4.EXT, XPSP1.EXT and XPSP2.EXT) cover everything. Download dumpdupes.cmd and place it in the main HFSLIP folder (alongside the normal HFSLIP executable). Run this tool AFTER you ran HFSLIP (it namely requires a SOURCE and a SOURCESS folder to compare). If there are any duplicate binaries that can be removed, a file called EXCLUDE.TXT will be created. Let me know if it contains additional files to those that already exist in the current removal files. This program can be used to check Windows 2000, XP and 2003 sources.
Dumpdupes.cmd has one limitation: it only checks for duplicates in the current sources. This tool would have to be run again whenever new hotfixes arrive in order to ensure the list is up to date. I'll probably make another tool that outputs a full list of any driver binary that isn't supposed to be loose in I386 once I evaluated the pros and cons of both.[attachment=25420:hfslip_beta_Mar30.zip]

This post has been edited by tommyp: Nov 9 2009, 06:57 PM

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

This post has been edited by fdv: Apr 10 2006, 06:11 PM

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.

This post has been edited by Super-Magician: Apr 10 2006, 06:41 PM

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

This post has been edited by dziubek: Apr 10 2006, 08:19 PM

@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

This post has been edited by dziubek: Apr 10 2006, 10:25 PM

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!

This post has been edited by Kiki Burgh: Apr 11 2006, 12:17 AM

@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!

This post has been edited by Kiki Burgh: Apr 11 2006, 12:18 AM

Thanks fdv.

I'd like to make Windows not check the list.
From here : http://www.d--b.webpark.pl/dreampackpl_en.htm , I need this method:

Do you know of any patcher that uses only this method ?

Hi

SFCFILES.DL_]

Error from T -9 stepped out by file SFCFILES.DL_. I deleted his from FIX.
I use file sfc_os .dl_ only now.

dziubek

It's already added, dziubek. In the script, Tomcat wrote

The /I switch results in a case insensitive comparison. So "y" should work as well as "Y".


Not sure if someone answered your question yet, but to remove the CAT files, you need the modified SFC*.DLL in FIX (of course, use the correct one for your OS). After the multiboot path screen, the script will ask you whether to remove the catalogs.

This post has been edited by Super-Magician: Apr 11 2006, 07:17 AM

@Kiki Burgh - Ohhh, I see. We just had a filename mixup. You had "sfc_files.dll ... is not quite well compatible with winXP" but you meant SFC.DLL, not SFCFILES.
SFC.DLL without the word "files" in it is, in fact, for Windows 2000 only, as TP directs. SFCFILES is, after all, only just a list. So nothing to see here

@Camarade_Tux - Damian advocates just SFCFILES replacement. I have corresponded with him in the past and what he is referring to is only SFCFILES being emptied out. Note he says "So WFP is on" in paragraph 3. So, to have WFP off, use a modified SFC.DLL or SFC_OS.DLL and to avoid the OS loading up a list of protected files use also an empty SFCFILES.DLL. In other words, see my post above called the "overkill" method.

@Everybody
Anyway, everybody make sure you've added yourself to the HFSLIP world map.

This post has been edited by fdv: Apr 11 2006, 09:08 AM

@Super-Magician

thanks for explanation




@fdv
When I used file sfcfiles.dl_ I had problem in T9 .
It sufficed to alter the name of file on sfc.dl_ problem would pass

This post has been edited by dziubek: Apr 11 2006, 06:07 PM

@Tomcat (or anyone),

Do you know if any of the hotfixes released today supersede ones previously released?

KB912812 (IE)
KB911562
KB908531
KB911567 (OE)

Also - are you going to be updating your update lists?

This post has been edited by Super-Magician: Apr 16 2006, 08:03 AM

The 912812 update supersedes 905915 and 910620 (IE 5.01SP4 only).

The 911567 update supersedes 823353, 887797, and 897715 on 2000 and XP SP1, and 887797 and 900930 on XP SP2.

the other 2 don't replace any updates to my knowledge.

the_guy

@fdv - Can you shed some light on setupapi.dl_? Are these different for all the OSs?

With the latest round of hotfixes, there are some additional files that msft is putting on our systems. One is for the kb908531 update. Why are they forcing additional files on our systems now? Please stand by, I'm sure TC already figured out what's missing, but I sent him some tips on fixing up the script for this. Anyway, the fixes I had were for 2k only. I didn't test for XP.

thanks for these!
pardon me for the confusion ...

may i just know though where i could get the SFC*.DLL that would be compatible with my XPSP2 OS?
would there be anything else that i need to do other than this ... any editing for example?

This post has been edited by Kiki Burgh: Apr 11 2006, 08:58 PM

From a different thread... SFC_OS.DLL

No editing is required. Just drop the file into FIX.


not much other than the DLLs are indeed different. the edits to them are pretty much the same. i was never good with assembly. oleg clued me in to where the edits are, passed on from x-pert. he could tell us more of whats going on.

<shines the secret x-pert signal into the sky>

This post has been edited by fdv: Apr 11 2006, 09:31 PM