Help - Search - Members - Calendar
Full Version: HFSLIP - Test releases
MSFN Forums > Member Contributed Projects > HFSLIP
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45

   


Google Internet Forums Unattended CD/DVD Guide
Phaneendra Rao
I could not find the download link for HFSLIP. Is it an executable program or some command file. how to use it. I am new to this topic.
Tomcat76
@Yzöwl...
That looks all right to me. The only person that could tell us if XPize can be responsible for this is Kiki because he's using it as well. I'd like to see your HFSLIP.LOG and SYSOC.INF files next, please... smile.gif
Yzöwl
Here you go, including the AU.inf from before!
Kiki Burgh
QUOTE (Phaneendra Rao @ Oct 31 2006, 10:58 PM) *
I could not find the download link for HFSLIP. Is it an executable program or some command file. how to use it. I am new to this topic.
hi! welcome to HFSLIP Phaneendra Rao ... i think TP already answered this Q in this thread ... but just to reiterate ... final versions may be downloaded from the initial page of the thread above OR you may directly get it from the download section of http://hfslip.org ... as for test releases, you may download it from the initial page of this thread
Super-Magician
I haven't been paying much attention to my HFSLIP run window lately, so I just noticed this now.

The CABCOMPACT section, as do many other sections, calls upon UNICAB2 to make the cabinet file. However, that section nulls the MAKECAB output, so the output of the long repacking process is gone too!

Also, I assume you just overlooked this, but I've been *patiently* waiting for your reply regarding this. laugh.gif

QUOTE (Super-Magician @ Oct 27 2006, 07:16 AM) *
What do you think about adding the HFSLIP version to the ISO name or volume label? I'd like to see at a glance the version I used, not just when I created it.
Tomcat76
@Yzöwl

I'm stumped. I really don't know what's going on there. The only thing I can suggest is that you make an HFSLIP run without XPize and the hotfixes that aren't on our lists to find out what's causing this.

QUOTE (Super-Magician @ Nov 2 2006, 12:22 AM) *
However, that section nulls the MAKECAB output, so the output of the long repacking process is gone too!
Ah, OK. I'll change this in the next test smile.gif

QUOTE (Super-Magician @ Oct 27 2006, 07:16 AM) *
What do you think about adding the HFSLIP version to the ISO name or volume label? I'd like to see at a glance the version I used, not just when I created it.
I've been thinking about it. I'm hesitating because I believe the name is quite long already. The intention behind the use of the date and time was to allow people to keep previously created ISO files in the same folder (and to allow HFSLIP to successfully create a new ISO when people forgot to take out the old one) so those have to stay. I'm open to suggestions, but I prefer not to touch the volume label. smile.gif
Yzöwl
Okay, here's some more info on my problem.

I noticed I was getting this error, which I'd been foolishly ignoring!

I traced this to HFSLIPWU.INF somewhere around here
CODE
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","214",0,"%11%\regsvr32 /s """%11%\wuaueng.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","215",0,"%11%\regsvr32 /s """%11%\wups.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","216",0,"%11%\regsvr32 /s """%11%\wups2.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","217",0,"%11%\regsvr32 /s """%11%\wuweb.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","218",0,"%11%\regsvr32 /s """%11%\wuapi.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","219",0,"%11%\regsvr32 /s """%11%\wuaueng1.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","220",0,"%11%\regsvr32 /s """%11%\wucltui.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","221",0,"%11%\regsvr32 /s """%11%\iuctl.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","222",0,"%11%\regsvr32 /s """%11%\muweb.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","223",0,"%11%\regsvr32 /s """%11%\msxml4.dll""""
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZB","224",0,"%11%\regsvr32 /s """%11%\msxml6.dll""""
I loaded up services.msc to once again find no Automatic Updates service. Then I ran the first command from the section I've just posted, (obviously without the unneeded switch, multiple quotes or path)
CODE
rundll32 wuaueng.dll
After a refresh in services.msc the service was now shown.
I ran Windows Update but it failed to work!

When I checked again in services.msc, the service needed starting.

However, when I tried that I got this!

A reboot later and 'all was fine', the service started and WU ran fine.

As a final addition to my woes, WU reported that I needed these
CODE
KB898461
KB892130
IE7
KB918899
KB885836
The second and third are understandable, however the other three are already in my HF folder!
Here they shown in Add or Remove Programs minus IE7 as proof.
Tomcat76
Yzöwl...

When do you get that first error? Is that while running HFSLIP or during installation of Windows? I suppose "root" is your rename of the "Administrator" account but I wonder why it's echoed in the DOS box in that way.

The snippet you posted from HFSLIPWU.INF couldn't have directly caused an "installation error". That part does nothing more than adding entries into the registry, which need to be executed at the next (internal) reboot.

As far as those hotfixes are concerned...

First of all, I find it strange that you have all those entries in Add/Remove Programs. Do you use a custom version of that application?

KB898461--
Do you have spcustom.ref, spmsg.ref, spuninst.ref, spupdsvc.ref, update.ref and updspapi.ref in your updated installation source?

KB918899--
Can't see what could be the problem here at first glance.

KB885836--
Seems that HFSLIPWU.INF didn't get parsed in its entirety, more specifically this line:
HKLM,"SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB885836","Type",0,"Update"
Unless that line was only there to satisfy MBSA. I forgot...
Yzöwl
QUOTE (Tomcat76 @ Nov 2 2006, 08:22 PM) *
When do you get that first error? Is that while running HFSLIP or during installation of Windows? I suppose "root" is your rename of the "Administrator" account but I wonder why it's echoed in the DOS box in that way.
At first logon, i.e runonceex stage
Thats what gave me the headaches too, the console window closes almost immediately the error box is OK'd. Why would the current user name be echoed, but not as the prompt? The cursor is flashing in the line underneath. If I CTRL-C in the console before OKing the error box, I get the 'Do you wish to terminate this batch' message upon returning to the console.
QUOTE (Tomcat76 @ Nov 2 2006, 08:22 PM) *
The snippet you posted from HFSLIPWU.INF couldn't have directly caused an "installation error". That part does nothing more than adding entries into the registry, which need to be executed at the next (internal) reboot.
No I know, all I know is that the registering of one of one or more of the wu*.dlls is not happening.
QUOTE (Tomcat76 @ Nov 2 2006, 08:22 PM) *
As far as those hotfixes are concerned...

First of all, I find it strange that you have all those entries in Add/Remove Programs. Do you use a custom version of that application?
The entries are only added as shown after updating and choosing show updates, none of the HFSLIPped updates are there.
QUOTE (Tomcat76 @ Nov 2 2006, 08:22 PM) *
KB898461--
Do you have spcustom.ref, spmsg.ref, spuninst.ref, spupdsvc.ref, update.ref and updspapi.ref in your updated installation source?
Yes they're all there 'cabbed'.
QUOTE (Tomcat76 @ Nov 2 2006, 08:22 PM) *
KB918899--
Can't see what could be the problem here at first glance.
Me neither…
QUOTE (Tomcat76 @ Nov 2 2006, 08:22 PM) *
KB885836--
Seems that HFSLIPWU.INF didn't get parsed in its entirety, more specifically this line:
HKLM,"SOFTWARE\Microsoft\Updates\Windows XP\SP3\KB885836","Type",0,"Update"
Unless that line was only there to satisfy MBSA. I forgot...
Well that will be due to my error. HFSLIPWU.INF is failing before my WU dlls are registered and [HFSLIPREG] is run, hence the error dialog.
Tomcat76
QUOTE (Yzöwl @ Nov 2 2006, 10:20 PM) *
HFSLIPWU.INF is failing before my WU dlls are registered and [HFSLIPREG] is run, hence the error dialog.
Quite a delayed error report, then. HFSLIPWU.INF is executed somewhere around T-25~19 when SYSOC.INF calls it. That snippet you posted from it is added to the registry at that time. At about T-13, during an internal reboot, those entries are parsed by Windows.
So don't you think it's strange that you only get an error message after first logon? You should've gotten one immediately...

You use the "PROGRAMFILES" feature, right? Was everything copied to the hard disk?
Yzöwl
You know what I mean!

There is nothing wrong with the inf file running, just one or more of the lines in it at runonceex; or something else running at runonceex, stopping those entries from completing.

All I need to do now is find a way of logging the runonceex procedure and possibly whatever batch file is showing when the dialog comes up.

My program files are all copied over and working fine!
Super-Magician
I don't know if this was intended or not, but the date in the ISO name is wrong.

For example, today, it gave me the name XPVOL1_032006_20h27m.iso. Shouldn't it be 110306 or 031106?
Tomcat76
@Yzöwl

In that case, please check that all files listed under the [RegDLL] and [SourceDisksFiles] sections in HFSLIPWU.INF are present on your install share as well as on the hard disk after installation. That's all that could cause HFSLIPWU.INF from being parsed entirely.


@Super-Magician

No, that isn't intentional. Probably your DOS date settings are different from mine. I'll change the code a bit.
Camarade_Tux
I think I have a BSOD at first boot because of a problem with "missing winsrv".

I have some unnecessary HF but it was not a problem before and I changed nothing. I don't have access to my HFSLIP.LOG ATM. Final was no problem, for sure.
I thought someone maybe had an info. confused.gif
Yzöwl
QUOTE (Tomcat76 @ Nov 4 2006, 11:14 AM) *
@Yzöwl

In that case, please check that all files listed under the [RegDLL] and [SourceDisksFiles] sections in HFSLIPWU.INF are present on your install share as well as on the hard disk after installation. That's all that could cause HFSLIPWU.INF from being parsed entirely.
Yes they are, all the files in [PFILESn] appear to have copied over. All the [ROROE] commands work manually after the error too, although I do get this message
MFPLAT.DLL was loaded, but the DllRegisterServer entry point was not found.
This file can not be registered.
I'm as yet to find the cause, none of the [HFSLIPREG] settings are applied though. My only current route is to comment out each of the [ROROE] commands one by one in individual tests to see if it's any of them which are failing, I've already tried with MFPLAT.DLL, but still get the error. I have been holding off on all the other entries because the error says installation not registering.

<Edit>
The only change in that file from the August stable though is the addition of the [PFILESn] stuff from the changes implemented in WMP10 integration, I may therefore start looking at WMP and/or its updates
</Edit>
Tomcat76
According to the DRM10.inf file from the WMP10 package, MFPLAT.dll needs to be registered.

If you get a registration error for that file, one of the hotfixes you use probably contains a corrupt version. This wouldn't be the first time...
Super-Magician
Yay! Thanks for the new version, Tomcat. laugh.gif thumbup.gif

Edit: Is the coding for WMP11 in 61104a finished yet?
Yzöwl
QUOTE (Tomcat76 @ Nov 4 2006, 07:52 PM) *
According to the DRM10.inf file from the WMP10 package, MFPLAT.dll needs to be registered.

If you get a registration error for that file, one of the hotfixes you use probably contains a corrupt version. This wouldn't be the first time...
All of my MD5s were checked and verified with those given on this forum. I just ran all of the commands after the error box was closed and the system up and running. If you say that the file is registerable, and the message I get is that it is not, then it is more likely that
  • You are wrong!
    try the command without the silent switch
  • The problem is as I feared to do with the newer method of WMP integration.
I'll try a run without any WMP stuff tomorrow and see what happens!
RJARRRPCGP
QUOTE (Yzöwl @ Nov 2 2006, 04:02 PM) *
Okay, here's some more info on my problem.

I noticed I was getting this error, which I'd been foolishly ignoring!


I never had that problem before.
That error message was only known to occur under Windows 2000 SP4, using the FDV fileset and HFCLEANUP. That error message was related to MRU list removing utility, which is included with the FDV fileset. I never heard of that before with Windows XP.
Yzöwl
QUOTE (RJARRRPCGP @ Nov 5 2006, 12:05 AM) *
I never had that problem before.
That error message was only known to occur under Windows 2000 SP4, using the FDV fileset and HFCLEANUP. That error message was related to MRU list removing utility, which is included with the FDV fileset. I never heard of that before with Windows XP.
Thanks for the idea, I do have a HFCLEANUP folder containing DBLBINXP.EXT and since I'm running out of ideas, it may be worth a look.
Camarade_Tux
Just to say my problem was my fault : some SP1 updates went into my SP2 HF folders.
Tomcat76
Yzöwl...

Please extract MP10Setup.exe, open DRM10.inf and look at the [regwmp.dlls] section. Then tell me if I'm wrong.

Maybe you misunderstood me. What I was saying is that it isn't the first time MS release a hotfix that contains a broken binary or a binary with a broken registration section. There's "webvw.dll" in localized versions of post-SP4 hotfixes for Win2K and also "inetcomm.dll" from the OE 5.5 cumulative for all languages. There could be more.

@Super-Magician

No, it isn't ready. I just left it in so you can get used to the new size tongue.gif
Yzöwl
Just a quick update on my problem...

The error still shows after removing MP10Setup.exe and WindowsMedia10-KB917734-x86-ENU.exe and adding WindowsMedia9-KB917734-x86-ENU.exe.

<Edit>
In HFSLIPWU.INF, I found...
CODE
1="Windows CD","WIN51",,"I386"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZZ999",999,Cleanup,"CMD.EXE /C RD/Q/S ""%%SystemRoot%%\HFSLIP"""
This is an example of the second line using corrected syntax...
CODE
HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZZ,999,,"CMD.EXE /C RD/Q/S ""%SystemRoot%\HFSLIP"""
I hope this helps!

The syntax of the [SourceDisksNames] section is
QUOTE
disk-ordinal="disk-description",disk-label,disk-serial-number

Identifies and names the disk(s) that contain the source files for file copying and renaming operations. Used along with SourceDisksFiles.

disk-ordinal
A unique number that identifies a source disk. If there is more than one source disk, each must have a unique ordinal.

disk-description
A string or a strings key describing the contents or purpose of the disk. The installer displays this string to the user to identify the disk. The description is enclosed in double-quotation marks.

disk-label
Volume label of the source disk that is set when the source disk is formatted.
This is also where you name the cab file if the files are in a cab.

disk-serial-number
Unused. Value must be 0.
Forcing the volume label onto all users could be difficult for those of us creating and burning our own isos.

Why does yours not follow these rules?
</Edit>
Tomcat76
Yzöwl...

If the error still shows after removing MP10Setup.exe then it's less likely caused by the improved WMP slipstreaming. The only thing else that "passes" that code is wmfdist.exe and wmfdist95.exe.

Concerning the RunOnceEx line...
That line was there even before I started helping TommyP. It was never a problem and it certainly cannot be the reason for the problems you're having only now.

The [SourceDisksNames] section was made just like it's done by others and I read this guide for it.
rajeshjamnadas
QUOTE (dziubek @ Mar 13 2006, 08:52 AM) *
I used HFSLIP_60312-t1.CMD with WIN 2000 & XP

WINDOWS 2000:

1. KB 842773 (WinHTTP 5.1) doesn't integrate.

2. Failure of registration of chosen files: *cpl again (2000 & XP)
-> directx.cpl be active


WINDOWS XP:

3. KB 892130 Windows Genuine Advantage Validation Tool doesn't integrate.

4. KB 887472 (Windows Messenger) doesn't integrate.


----

5. How to download and integrate KB905474 ?


Windows Geniune Advantage Validation Tool is not an hotfix or updates, it is installed pnly after installing windows XP and as WGA talk is restricted v cant talk much about that
but remember it is like an app so u can install after setup completes for that u can use $OEM$ folder and install at the last.

It may work.
Tomcat76
You've resurrected an old post. Both LegitCheckControl.cab and KB905474 are supported by HFSLIP.
Yzöwl
QUOTE (Tomcat76 @ Nov 9 2006, 02:18 PM) *
Yzöwl...

If the error still shows after removing MP10Setup.exe then it's less likely caused by the improved WMP slipstreaming. The only thing else that "passes" that code is wmfdist.exe and wmfdist95.exe.
HFSLIPWU is still used as you said because I am integrating the codecs etc.
Incidentally nullifying the HFSLIPWU.INF does remove my error problem, but solves nothing!
QUOTE (Tomcat76 @ Nov 9 2006, 02:18 PM) *
Concerning the RunOnceEx line...
That line was there even before I started helping TommyP. It was never a problem and it certainly cannot be the reason for the problems you're having only now.
No-one said it was the cause of my problem, it is incorrect, but if you wish to leave it in please do so!
QUOTE (Tomcat76 @ Nov 9 2006, 02:18 PM) *
The [SourceDisksNames] section was made just like it's done by others and I read this guide for it.
Well using that as your example the syntax is still incorrect. It should be
CODE
1="Windows CD",WIN51,,\I386
not
CODE
1="Windows CD","WIN51",,"I386"
Tomcat76
QUOTE (Yzöwl @ Nov 10 2006, 04:05 PM) *
No-one said it was the cause of my problem, it is incorrect, but if you wish to leave it in please do so!
Ho, ho... I never said it was correct. Just thought that you were still speaking of the problem you're struggling with. I'll test your suggestion.

QUOTE (Yzöwl @ Nov 10 2006, 04:05 PM) *
Well using that as your example the syntax is still incorrect. It should be
CODE
1="Windows CD",WIN51,,\I386
not
CODE
1="Windows CD","WIN51",,"I386"
If you scroll down a bit on the page I linked to you'll see that it's done both ways. I opted for the quotes because it's generally "safer" to use them in INF files (with some exceptions). But I'll test this out too.
Yzöwl
The quotes for the tag and path don't matter, it was the leading backslash\ to which I was inferring.
Tomcat76
Yzöwl: I've tested both of your suggestions and they work. They made it into the new final. smile.gif

Hopefully we can get to the bottom of your problem now smile.gif
Camarade_Tux
Btw, does HFSlip handles UAA (888111) slipstreaming ?
clintb
QUOTE (Camarade_Tux @ Nov 12 2006, 03:48 AM) *
Btw, does HFSlip handles UAA (888111) slipstreaming ?

Yes. I've been doing that one for quite a while now. Possibly since the May time frame...
Camarade_Tux
Thanks for the info.
I was really not sure about that one : I couldn't find anywhere that was handled.

smile.gif
Yzöwl
QUOTE (Tomcat76 @ Nov 12 2006, 01:49 AM) *
Yzöwl: I've tested both of your suggestions and they work. They made it into the new final. smile.gif

Hopefully we can get to the bottom of your problem now smile.gif
Using 'the new final' and making a couple of small changes myself, the installation now continues without error, and has automatic updates etc.

Therefore problem solved!

One of the changes I made was a continuation from my last suggestion
CODE
ECHO>>SOURCESS\I386\HFSLIPPF.INF [SourceDisksNames]&ECHO>>ECHO>>SOURCESS\I386\HFSLIPPF.INF 1="PFILES DIR","%CDTAG%",,"I386\PFILES"&ECHO/>>SOURCESS\I386\HFSLIPPF.INF
now says
CODE
ECHO>>SOURCESS\I386\HFSLIPPF.INF [SourceDisksNames]&ECHO>>ECHO>>SOURCESS\I386\HFSLIPPF.INF 1="PFILES DIR","%CDTAG%",,"\I386\PFILES"&ECHO/>>SOURCESS\I386\HFSLIPPF.INF
The other changes, (other than my usual complete re-write of :HFEYzowl) were purely cosmetic.

Usual thanks etc.
Kiki Burgh
QUOTE (Camarade_Tux @ Nov 12 2006, 06:36 PM) *
Thanks for the info.
I was really not sure about that one : I couldn't find anywhere that was handled.

smile.gif
this could serve as your reference Camarade_Tux tongue.gif
QUOTE (Tomcat76 @ Apr 27 2006, 06:23 PM) *
@Kiki: 60427b supports KB888111... smile.gif
Tomcat76
Yzöwl...

ECHO>>ECHO>>... How embarassing... biggrin.gif

Please look for version 1.0.3. It's becoming customary to see a new final the day after, hehe.


I hope I can now focus on IE7 and WMP11... tongue.gif
Super-Magician
QUOTE (Tomcat76 @ Nov 12 2006, 01:48 PM) *
It's becoming customary to see a new final the day after, hehe.
You should slow down there, Tomcat! tongue.gif
Kiki Burgh
QUOTE (Tomcat76 @ Nov 13 2006, 02:48 AM) *
ECHO>>ECHO>>... How embarassing... biggrin.gif

Please look for version 1.0.3. It's becoming customary to see a new final the day after, hehe.


I hope I can now focus on IE7 and WMP11... tongue.gif
he! he! i was just looking at 1.0.2 & then a few minutes after i noticed it's already 1.0.3 ... laugh.gif finalizing integration (?) of ie& & wmp11 would be great ... thanks!
Oleg_II
Tomcat76 welcome.gif
Yzöwl made some changes in Sata/Raid installation section. Could you please include it into the script?
Super-Magician
Hmmm...something happened to the topic's title - it's now Hfslip.

biggrin.gif
retalv
Hi boys...

Test version 1.0.4rc3 of HFSLIP don't register properly .ocx in new version (9.0.28.0) of FlashPlayer for IE (swflash.cab).

Bye
Super-Magician
@retalv, please read further in the forum! laugh.gif

http://www.msfn.org/board/index.php?showtopic=86772

It's already a known issue. smile.gif
retalv
Hahemmm... sorry... blushing.gif

Bye
EmRoD
Wonderfull IE7 is working !!!

BTW -> I can't use a branding.cab file made with IEAK 7 to customise my IE7 install smile.gif
can you help me please ?
or must i put my Install.INS file somewhere (compressed or not)

Thanks a lot

--> Just Put my Install.ins File in the Fix folder and Voila biggrin.gif
Tomcat76
EmRoD

I can make HFSLIP support it, but I don't have IEAK7 so I'll need your help. smile.gif

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.
EmRoD
Hi

IEAK7 is freely downloadable from M$ website

Anyway it generates :BRANDING.CAB

This cab contains :

install.inf
INSTALL.INS
setup.inf

I Just put the INS file from the cab in the fix folder and it worked.

I saw HFSLIP support IE6 Branding.cab for Windows 2000.
Maybe you can add support for XP & IE7
I tried to put the branding.cab file in the HFCABS folder but hflip ignores it smile.gif

if you want me to test things with the cab files, or to copy you my files (cab or infà let me know smile.gif
Tomcat76
BRANDING.CAB supported... smile.gif
EmRoD
Thanks a lot, i'll test it on monday morning @work !!
I'll give you feedback
EmRoD
Branding.cab successfull smile.gif
dziubek
2007 time zone update for Microsoft Windows operating systems
http://support.microsoft.com/kb/928388
http://www.microsoft.com/downloads/details...;DisplayLang=en


"European Union Expansion Font Update" Addon
http://www.ryanvm.net/forum/viewtopic.php?p=40710#40710




Google Internet Forums Unattended CD/DVD Guide

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.