Tomcat76

The file you put in HFEXPERT\WIN\SYSTEM32\DRIVERS.

No, it just means the script fails to merge the two programs together properly. Try MC2 (v060616b) but DON'T merge the installers. What happens if you install DNF11.EXE and DNF20.EXE by hand? Does it work like that?

OK. I pretty much have an idea of how far you could go. I'll update the script so it deletes the TEMP folder in such case. But before we go any further... What's the name of the file? I hope it doesn't have an exclamation mark in it...

The "MAKENOISO" feature was introduced in 13a and your suggestion (Super-Magician's suggestion, actually) was implemented in 13b... So no need to implement it again...

Hi Mystek. I checked the HFEXPERT code from bottom to top (and then from top to bottom which made a lot more sense ). It looks like there are two problems, one of which I just fixed (see test release 60616b): 1) for some reason, the section that deals with subdirectories of HFEXPERT\WIN\SYSTEM32 fails in your case 2) HFSLIP didn't provide a safety net for when files are detected in HFEXPERT but none were processed (causing your broken TXTSETUP.SIF file) I'm sure that if you try the latest test release, TXTSETUP.SIF will remain in tact but the files in DRIVERS are ignored. Is that correct?

Huh, what? I've never seen this before....

The latest test releases no longer support dotnet2.exe in HF. That functionality was removed because of several reasons. You should try to make it all work from HFSVCPACK. We seem to be getting closer. It appears that you no longer get an error message when trying to install one of the output files. That's good. Now we need to figure out why .NET 2.0 doesn't install. Please download the latest version of MC2 (060616b); it allows you to merge .NET 1.1 and .NET 2.0 into one installer (that's six files in one) and you save about 5.2MB.

Whoops... It just occured to me that I'm mixing you up with someone else... There is no "other thread" from you and I didn't ask you to try MC2 before... Looks like I'm the one who needs some sleep, hehe...

HFSLIP just copies the files from HFSVCPACK into SOURCESS\I386\SVCPACK and echoes the executable names into SVCPACK.INF alphabetically. So if the order is important change the name(s) and you're good to go. Looking at your other thread, you're already doing that.

Is this built into the 060616a?HFSLIP has always supported silent installers from HFSVCPACK (formerly HFSVPK).BTW... I just updated MultiCompiler 2. If both .NET 1.1 and .NET 2.0 are detected, it asks you whether you want to merge it all into one file...

If you go to WINNT\Microsoft.NET\Framework or WINDOWS\Microsoft.NET\Framework, do you see a subfolder called v1.1.4322 or just v2.0.50727? Don't mind the folder for 1.0... I already suspected that the order might be playing a role so removed the extra .NET 2.0 handling from the latest releases again. For that work, HFSLIP would have to take into account the inclusion of .NET 1.1 too which means a heck of a lot more code (to exclude it from being parsed by other sections, etc). Here's two options for you (all from HFSVCPACK)... Option 1: 1DOTNET1.EXE (your silent .NET 1.1 installer) 2DOTNET1SP1.EXE (your silent .NET 1.1 SP1 installer) 3DOTNET1up.EXE (your silent KB886903 installer) 4DOTNET1lng.EXE (your silent .NET 1.1 langpack) 5DOTNET2.EXE (Aserone's silent .NET 2.0 installer) 6DOTNET2lng.EXE (your silent .NET 2.0 langpack) Option 2: DOTNET11.EXE (silent .NET 1.1 installer including SP1, KB886903 and langpack) DOTNET20.EXE (silent .NET 2.0 installer including langpack + hack for installation at T-13) You can make these two installers with the "beta" of MultiCompiler 2. Have you tried it already?

I think that might be a problem. But it worked for me on Win2K...

It is time to revive this project. The second version of MultiCompiler is in the making. Download current build: MC2-060617b.7z The MC2 project was discontinued for the time being.

Hi. Welcome to the forums. Here's something you can try. Johnathan Howell made this great utility called iexplore.exe which you can put in Program Files\Internet Explorer. When first run, it asks you for the path to your preferred web browser. From then onwards, any calls to iexplore.exe will be redirected to your browser of choice. You can reset this behavior at any time by deleting a registry key. Download the program here. It's the MSFN thread where Johnathan announced the application. The information in the first post is a bit dated so do scroll down if you're interested in learning more about it. If this proves to solve your Quicken problem, someone with more knowledge about the FDV fileset than me will help you with the integration of that file into HFSLIP. Good luck...

Don't know... You experienced DST or something? It's probably the Service Pack... BTW... Did you install that .NET 2.0 build or not?

The only difference between the main installers (.NET 1.1, SP1 & KB886903) is that the localized versions have the installation wizard in your language. The actual program files of the localized versions are still in English (which is why you need a lang pack). So whether you install this: English .NET 1.1 + English SP1 + English KB886903 + langpack.exe or this: Spanish .NET 1.1 + Spanish SP1 + Spanish KB886903 + langpack.exe ...the end result is completely identical.

+1

That was ditched 9 minutes before you wrote your post, I'm afraid. I might consider putting the functionality back if it's really necessary but only in the HFSPLUG1.CMD file.

Use RVM's .NET 1.1 installer and Aserone's .NET 2.0 installer; they go in HFSVCPACK. HFSLIP supports the integration of Shockwave Flash (for XP: read the 60528 changelog; for other OS versions, see the Test releases thread) and there is a silent installer floating around here somewhere for Shockwave for Director which can be put in HFSVCPACK. You probably lose a fraction of a second while HFSLIP determines if your source needs to be patched or not. But HFSLIP does this check anyway so it wouldn't make a difference to leave it out.

The name doesn't matter. I use RVM's installer renamed to DNF11.exe.

You never answered my question: when you are trying to get both .NET 1.1 and .NET 2.0 in, where exactly are you placing your .NET 1.1 files and where exactly are you placing your .NET 2.0 files? Anyway... I'm making a newer version of the MultiCompiler script. It already supports .NET 1.1 and .NET 2.0 (including updates, language packs and reg hacks). I suggest you try it because the .NET 1.1 section has been thoroughly revised. You can rename the output files to whatever you want and place them in the HFSVCPACK folder (then run HFSLIP). MC2

It is supposed to be. I haven't actually tried all languages but English, Dutch & French work fine.Do you have .NET 1.1 installed on the system you're running MultiCompiler from? Are you logged on to an account with admin rights?

You do have 7za.exe and StartX.exe in the MultiCompiler working folder, right? Anyway, it's not so important. I was just trying to make it easier for you (one file for .NET 1.1 in HFSVCPACK). Just for clarification... If you keep using your own files: - your .NET 1.1 files should be in HFSVCPACK - the RVM .NET 2.0 installer should be in HF

HFSLIP test version 60614d adds these extra [FileFlags] entries into TXTSETUP.SIF for WinXP.

A new final is in the works. At this point, I don't intend to add more functionality except maybe a [FileFlags] section for Windows 2000. To be checked: - all new hotfixes should be supported on Win2K SP4, WinXP SP1, WinXP SP2 and Win2K3 SP1 - KB911562 for MDAC 2.8 SP1 - Win2K .ART extension support - USP5 Any volunteers?