Yes, remove the diagnostic part. The dosnet file is pretty much empty. Take a look.

OK... 18f adds the lines into txtsetup.sif and dosnet.inf.

I had issues with E but I am now testing F...

Which issues? 18f only adds two lines into txtsetup.sif and two more lines into dosnet.inf so it won't make a difference.

18E + HFCLEANUP = missing NT5.CAT
Reloading my HFCLEANUP from scratch in case I put one of those HFCLEANUP addons in there and forgot about it. Those things give me nothing but trouble!

But the HFEXPERT/WIN thing seems fixed. Thanks for all the help

That *may* have been fixed in 18f.

You know... It's strange that you never experienced this problem before, but OK... We're working with Altair Basic here...

318F w/hfcleanup+hfexpert -->txtsetup dosnet still needs work, the file begins with the files added by hfcleanup. I'm assuming that there is no dosnet file in the sourcess\i386 folder prior to hfcleanup starting. Dosnet is not used for cd installs, so it doesn't really bother me.

I'm slowly beginning to run out of ideas, hehe.

18g does something (or rather doesn't do something) which I wanted to avoid. But if this fixes the problem with dosnet.inf I don't have a choice...

It looks like we are back on track

Now back to that CPL issue we were working on....

In HFEXPERT/WIN/SYSTEM32 I have:
and in SOURCESS after HFSLIP_60318f-expert I get:
But on my installed VMWare system I end up with:

The .CPL is getting copied over as the CPI and the CPL. The real CPI is gone.
Would you guys like to address this? If not, I can try to turn this into an addon (which I was considering anyway) and go around the problem.

TC, Sorry about the dosnet thing. It was my error, I was removing that file with hfcleanup. Can you add this into the lower part of the hfcleanup section? (not a critical change at this point because you can't do a dos install with an hfcleanup'd source).
FROM THIS ECHO>>SOURCESS\I386\DOSNET.INF d1,%%I
TO THIS IF EXIST SOURCESS\I386\DOSNET.INF ECHO>>SOURCESS\I386\DOSNET.INF d1,%%I

I just have to test the HFSLIP easter egg out to see if all is OK.

TC - 318G - verified the following: hfcleanup/hfexpert and hfslip easter egg. Both are good. I have to verify with a HFDRV set.

Tain/TC - I think this will help. There is a txtsetup.sif command to say that the file that is on the CD isn't compressed. Check this out. http://gosh.msfnhosting.com/txtsetup.htm Look at the _X part. I think (or hope?) this is relatively easy to incorporate into the script. This was lifted out of the 2k txtsetup.sif
autochk.exe = 2,,,,,,_x,2,0,0
The file is uncompressed, the _x tells the installer that the file is uncompressed. Hope this helps....

Good find! Gosh put out some great info...too bad he is MIA. Speaking of MIA...FDV and Oleg are sorely missed :/
And what about C&B, saugatak, Dirtwarrrior, and Bilou? Did we scare them away?

FDV is here once in a while. But the rest are indeed MIA.

If dosnet.inf wasn't an issue then 18f would've worked the same as 18g. I'll base the next tests on 18f then.

CPI/CPL...
You know... A while ago I changed the code to leave both CPI and CPL files extracted. But then I figured it would be better to compress one of the two again and I picked CPL... for these reasons:
1) There's no point in keeping both uncompressed
2) I believe all MS *.CP_ files are CPL files so it's better to overwrite them instead of creating duplicates (eg whatever.cp_ and whatever.cpl)

But apparantly Windows setup is too stupid to see the difference between myuninst.cp_ and myuninst.cpi...

I see two options:

1) Extract all *.CP_ files (even those from the source) and leave them like that

2) Try what Tommy suggests with the _x thing in txtsetup.sif (this I can't do in HFAAO)

Option 2 sounds more prudent to me.
Is it even an issue with HFAAO? I didn't think that they were processed until later...

HFAAO is parsed before the source gets copied. You can try a few CPL addons if you like just to see if a fix is needed there as well. But, as said, it's too complicated to do the _x fix for addons.

Version 18h debuts the _x fix for CPI files in HFEXPERT\WIN\SYSTEM32.


Edit: it shouldn't be an issue for addons; CPL and CPI files are named differently so there's nothing for Windows setup to get confused with.

Woohoo!

60318H-expert slipstreamed great with HFEXPERT/WIN/* and HFCLEANUP...and even the control panel additions work! /SYSTEM32 and HFAAO control panel files are all working properly now.

You guys RULE!

Glad we could fix this within 24 hours, hahaha!

Well, its been about 18 hours since I cried about anything so how about another feature suggestion?

I've noticed a few things happen when users have trouble. They/we:
-Don't post an error_report
-Put the text of error_report into their post
-Need to add another file that is requested by the devs

Maybe it would be easier if HFSLIP output an ERROR_REPORT.ZIP (or CAB) that contained:And maybe even:But that may make a large zip. DRVINDEX isn't too bad, but TXTSETUP.SIF tends to be quite large even though text files compress well.

Anyway, this takes a few steps out of the user's hand and they can "just attach the zip."

Gosh was a she, BTW. To be sorta sexist (maybe?), female contributors on MSFN are rare to be sure. The only other one we have now and again is Wendy (OS2FAN2).
I'm around now and again as Super-Magician notes, but in a technical thread like this you've gotta remember that this is script-heavy, new-feature testing stuff, which is rare for me to participate in anyway... I have cruised Oleg_II's site and have not heard from him since like February. He appears quite gone to me, unfortunately. I hope he resurfaces.
I have been busy mostly with Windows 2003. Many of my test installs just die right after filecopy. I have had the modded setupapi for a while but I see I should have released instructions on it, so I have written them finally.
Ok, I'm gonna go back to plugging away again.

Random: I recommend the DVD "Primer" to you all. It's a great techie film about the head games that happen between two engineers when they accidentally create a time machine (it's not cheesy like Back to the Future or anything, it's really good!)

Always good to hear from you, FDV

Its funny how most Americans are naturally sexist; we usually bias towards males. I was in class the other night and my instructor, a PHD-seeking female, kept referring to third parties with male pronouns.

OlegII has a site? URL please? From his profile:

I'm glad to hear that you are making progress on 2k3. I, for one, will be clamoring for it in a year or so whenever some killer-app comes out that won't run on 2k.

Oleg_II's site is here: http://kitaist.com/

about future apps for windows. maybe this is too much speculation... but i read (and i do not have the url handy) that Win FX is just add-on to Vista, and so is Framework... meaning no part of Vista is written natively in Framework or Win FX. anyone know if this is true? if so, it would mean that most apps will probably continue to be written in the same nt 5.1 API as 2003 and xp apps, right?

For those using the test builds...
A problem was introduced yesterday that prevents subdirectories of HFEXPERT\WIN\SYSTEM32 (eg, DRIVERS) from being processed. That's fixed in 60319a.

Doh! In Russky. This version says it is a commerce site.

Wikipedia says that WinFX is integral. Perhaps you are referring to WinFS, which was to be integral but was recently dropped. I heard that it will be an addon.

processed = copied over, right? No other processing (like CODECS)?

Just so we're on the same level...

HFEXPERT\CODECS = copied over; txtsetup.sif & dosnet.inf updated; all files except exe and cpl registered

HFEXPERT\WIN = copied over; txtsetup.sif & dosnet.inf updated

HFEXPERT\APPREPLACEMENT = copied over


I'm gonna add *.CPI to the list of files not to be registered in the HFEXPERT\CODECS section just in case people still put those files in there.

fdv, your page on HFSLIP for XP/2003 now says "updated on March 20, 2005", but it is 2006 .

By the way, what did you update on that page?

Yeah, my last post was still vague

How about this for even more fidelity:HFEXPERT\WIN\ is the only one that will use subfolders, right?

@Super-Magician: He finally changed "Windows Server 2002" to "Windows Server 2003"...

@TAiN: Right now, yes. I was thinking of asking TommyP to allow subfolders in APPREPLACEMENT.

Hmmm...how would that be used? Where would the folders go? 'program files'?

Haha... I wish...

No. Currently, files in APPREPLACEMENT are copied over into I386. I guess it could be expanded to allow replacing files in subfolders of the I386 folder (though I can't think of a practical use for that).

thanks for the alert, boy did that look foolish. i updated instructions for modifying 2003's SETUPAPI.DLL as well as a note about HFAAO.


? i don't know what this means

FDV: Do you think you could change the link to Tomcat's XP page to http://users.telenet.be/tc76/winup/_winxp.html? Right now, you have to click twice to reach it.

[question removed; script for removing Windows Messenger reposted below]

-- Super-Magician

Windows messenger in 2000? Nope, it's not part of 2000. Windows messenger is bloatware/worthlessware (if there is such a word) that comes prebundled with xp and newer.

Oh, OK then. Didn't realize that. Time to scrap that idea !

Of course, that's why I'm removing it .

Hmmm...this thread seems to be getting quite long ...

-- Super-Magician

I'd rather call it backdoor.MS.msmsgs

I'll take a look at Windows Messenger and if it doesn't take too much time to implement I'll ask TommyP for permission. But don't keep your hopes up...

@fdv: It was a joke inspired by the fact you got a date wrong. Sorry if it didn't come across like that.

Haha

OK, great . I accidentally removed the CMD file from my previous message, so I'll repost it here:


-- Super-Magician

There are three options that I see for this.

1. Create an INF file and throw it into the HFSVPK folder.
2. Create a CMD file and throw it into the HFSVPK folder.
3. Why not craft a hfcleanup file to not let it install at all? .... cough cough cough the reducer is already created and available cough cough cough. I hate colds!

Congratulations, tommyp! You're now a "Friend of MSFN" as indicated by your avatar, and you've reached 700 posts...yay!

Anyway, what I used was a CMD file, which I put in HFSVPK. I don't know much about INF files and HFCLEANUP, but maybe option 1 or 3 is easier?

-- Super-Magician

Oh, you wanted it removed...

You shouldn't edit posts, you know...

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.

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

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?