Tomcat76

Just wondering... You didn't list the BIN file, so is there an installation CD in your CD drive?

IE7's iernonce.dll breaks RunOnceEx? I'd doubt that because Windows Update would've complained in that case. All the hotfix INF files are installed through RunOnceEx... Can the IE6 version be renamed or should its name remain the same?

RC6 still defaults to DVDBURN.EXE, but it no longer sets the wrong switch if CDBURN.EXE is present as well.

Nice

There's a simpler solution: Note that this feature only works with merging options A, B and C.

BRANDING.CAB supported...

Maybe Oleg can help with that. HFSLIP puts INF files in the I386 folder (to be copied into WINDOWS\INF during Windows setup) and puts other files in DRIVER.CAB. Those were the instructions I was given... What you could try is to uncompress all files. That's all I can come up with. To answer your other question... Snippet from "the web site": Note that this only works with merging options A, B and C. Sorry if that isn't clear enough...

Just an FYI... The next version of HFSLIP will have the IE7 code "unlocked" for Server 2003, but it should not be used for that OS yet. During Windows setup, you'll get error dialogs every time rundll32.exe, regsvr32.exe, etc. are accessed; they basically say that you don't have permission to access those files. I don't know if there are any other problems because after clicking OK about 50 times I gave up... The Server 2003 version of IE7 hasn't been updated in November like the one for XP. Maybe that's the reason.

EmRoD I can make HFSLIP support it, but I don't have IEAK7 so I'll need your help. Are there any INF files alongside INSTALL.INS? If so, do you see install.inf and setup.inf? If there are other INFs besides install.inf and setup.inf, can you paste here what's specified under the [DefaultInstall] sections? This should be the same for every file so only copy this once.

dvdburn.exe But it will set the wrong switch if you didn't specify CDBURNSW2. It's maybe better to default to cdburn.exe...

HFSLIP 1.0.4rc5 supports the following variables for CD burning: NOBURNISO= CDBURNAPP= CDBURNSW1= CDBURNSW2= HFSLIP uses the following command to burn the ISO: %CDBURNAPP% %CDBURNSW1% "%TEMPISO%" %CDBURNSW2% TEMPISO is an HFSLIP internal name for the ISO it has created. You can clearly see the difference between the CDBURNSW1 and CDBURNSW2 variables. Unless cdburn.exe or dvdburn.exe is used, CDBURNAPP should contain the executable name of the burning program of your choice, including the path. If there are spaces in the path, it should be quoted. If CDBURNAPP is not defined, HFSLIP looks in the HFTOOLS folder for either cdburn.exe or dvdburn.exe. When using cdburn.exe or dvdburn.exe, you must specify at least the drive letter in the CDBURNSW1 variable, and HFSLIP defaults to CDBURNSW2=-max if CDBURNSW2 is not defined. The purpose of NOBURNISO should be pretty straightforward, I think... Here's a few examples: ImgBurn.exe: NOBURNISO= CDBURNAPP="%PROGRAMFILES%\ImgBurn\ImgBurn.exe" CDBURNSW1=/MODE ISOWRITE /SRC CDBURNSW2=/DEST E: /START /COPIES 1 /ERASE /OVERWRITE YES /CLOSESUCCESS /WAITFORMEDIA cdburn.exe (in HFTOOLS): NOBURNISO= CDBURNAPP= CDBURNSW1=E: CDBURNSW2= cdburn.exe (in HFTOOLS) with erase: NOBURNISO= CDBURNAPP= CDBURNSW1=E: -erase CDBURNSW2= dvdburn.exe (in HFTOOLS): NOBURNISO= CDBURNAPP= CDBURNSW1=E: CDBURNSW2= dvdburn.exe (in HFTOOLS) with erase: NOBURNISO= CDBURNAPP= CDBURNSW1=E: CDBURNSW2=/Erase

Actually, it's still not perfect. I still need to use the original iesetup.dll (IE6) in the early stages of Windows setup so you won't see an error. The new version of iesetup.dll is copied at T-13.

Fixed in 1.0.4rc5...

Fixed in 1.0.4rc5...

Thanks for that. The new opuc.dll has a bad header. I'll let HFSLIP run MODIFYPE on it. You can expect a new version soon (with several other updates)...

And sooner than you think...

It looks like they fixed most of the problems with this re-release. You can expect HFSLIP to support IE7 soon

Looks like the "shouting filter" is in effect again. Our program is called HFSLIP and it's referred to like that in several thread titles on our forum, but editing the main post of such a thread causes the title to display "Hfslip" afterwards. The only way I can get it back to showing "HFSLIP" is by using the "click and hold" edit feature. But I really don't feel like doing this every time I edit the main posts of such topics... "Msfn, our forum host... and be sure to try out their Bb Code..." Edit... Looking at how the board messed up the title of this post, it should be: "Msfn, Our Forum Host... And Be Sure To Try Out Their Bb Code..." I'm writing for an American news paper... Yay...

Heheh. Beat you to it...

HFANSWER.INI. That's where you can define your custom settings. You can read up on HFANSWER.INI here.

Yes, and so did the XML4 and XML6 updates from October

You'll get an OCX registration error during Windows setup when the new Flash 9 (Flash9b) from November 9, 2006 was slipstreamed, though Flash still works. I'm currently investigating why this happens...

I advised to remove the standalone msxml3.msi. You should use the KB924191 hotfix for MSXML3 for your OS. MSXML3 - KB924191 MSXML4 - KB927978 MSXML6 - KB927977

OK... It's done. Version 1.0.4rc2. Thanks, Yzöwl...

Multiple STORAGE*.INI files are supported since version 61014c... That's about a month already... I'll check out the other suggestions...