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

But at least tommyp understood...I think.

I do know though that that line you got there is not enough. There are two things to be uninstalled but I can't remember what the other one was. I used to make silent installs a couple of months back and I was removing Windows Messenger from Windows XP right before installing MSN Messenger 7.5 in one of the packages but since I couldn't find a way to shush Windows Update I decided to drop it... and now I can't find it back. It was for the second Windows Messenger entry in Add/Remove Programs.

I looked a bit closer. Here's more options to getting rid of messenger... (continued numbering from before)

4. Edit sysoc.inf (you need to repack it when you're done) and remove the line that says "msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,hide,7".
5. Create a winnt.sif and add this to your [Components] section : Msmsgs=Off

Wow. I'm a friend now. Cool. It's funny seeing some posters on the forum that post gibberish & have over 2000 counts. I get a kick out of when someone asks a question, and they would reply saying that they don't know. HAHAHA.

Tomcat76: My script works fine, but what's the thing in Add/Remove Programs you're talking about?

tommyp: Option 4 sounds OK to me, but I wish there would be an automated way of doing that. I tried Option 5 once, but that was with my *corrupted* WINNT.SIF file (it said "[Componants]" instead), and I never tried it again.

This post has been edited by Super-Magician: Mar 20 2006, 05:25 PM

On Windows XP, when you remove all instances of "HIDE" from sysoc.inf, you'll see two references to Windows Messenger in Add/Remove Programs. They both need to be uninstalled to get fully rid of Windows Messenger. I think the second inf is called ims.inf but don't take my word for it. I need to investigate this again just like I did a couple of months ago.

What about the thing in Add/Remove Windows Components?

I need a rest...

That's what I meant to refer to...

I used to use the winnt.sif method before nlite. It worked great, even if I had the messenger slipstreamed into the sourcess.

My script only appears to work in Windows XP. When I place the script in SVCPACK ('MSMSGS.CMD') for a 2003 installation, I get an 'Advanced INF Install' error at T-13 again, just like for 2000.



-- Super-Magician

This post has been edited by Super-Magician: Mar 21 2006, 01:07 PM

When you say "just like for Windows 2000", I assume you tried it with a different CMD since Windows Messenger isn't part of Windows 2000.

For Windows 2000, you need to provide the full path to advpack.dll:

%windir%\system32\advpack.dll


But it should work without path for Windows 2003... Or am I wrong?

Oops, I forgot about that .

When I didn't provide the full path, that Advanced INF Install error occurred. Does that mean I do need it for Windows 2003? It worked fine without on XP.

This post has been edited by Super-Magician: Mar 21 2006, 02:17 PM

I'd think not since it's newer than Windows XP, but try it. You don't need to run HFSLIP again for that; just edit your CMD in SOURCESS\I386\SVCPACK.

This post has been edited by Tomcat76: Mar 21 2006, 03:22 PM

You mean try installing with the full path in the CMD? OK, will report back.

With CMD files that are processed during setup, it is good practice to specify the full path to the files you are working to. Using system variables also helps. To get an idea of what variables are available open a cmd window and type in SET.

@FDV,

You could do the same to the link on your 2K SP5 page. http://users.telenet.be/tc76/winup/_win2k.html

But, thanks for updating the link on your XP page.

@Tomcat76,

Does it matter that I put 'START /WAIT' at the beginning of the main line in my script? I won't be able to test my 2003 install with the modded CMD until maybe Thursday.

This post has been edited by Super-Magician: Mar 21 2006, 07:29 PM

START /WAIT should work. I can't see a problem with that.

Those link problems are really strange. About a month ago, someone said FDV had the wrong links on his site and I apologized a few messages later for not alerting FDV of this. I can't find that thread anymore, though. And now three times in a row. How many links does FDV have on his site?

@FDV: the correct links are in my signature. They were all changed simultaneously a long time ago. I thought you were already aware of that for quite some time but apparantly not. Sorry if I got you confused.

That someone was me actually . After you *apologized*, I thought that FDV had seen my message. But the links were never changed (until now). When I posted that original message in the other thread, browsing to the links on your old server would turn up an error message (page not found). Now I see you have the redirect link on the page.

Maybe you should have the pages redirect automatically to the new links. That way, it'll be easier. FDV only has two links to your update pages - one on the XP/2003 page (for XP only; he has Bilou's link for 2003) and one on the 2000 page.

-- Super-Magician

This post has been edited by Super-Magician: Mar 21 2006, 08:32 PM

in any case it's always best to pm me

I'll keep that in mind...

Hello
1. I have big problem. My setup stops in 9 minute near end of installation.
In spite it removal the content of catalogs: HFSVPK and HFAAO. Problem steps out from several version hfslip, but I had not time about this to write :>

2. After generating folder SOURCESS creates file MPDIR1.TXT with content : wpdmtp.inf