[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.

[Yzöwl]

Tomcat76, on Nov 4 2006, 11:14 AM, said:

@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.

Edit: Is the coding for WMP11 in 61104a finished yet?

This post has been edited by Super-Magician: 04 November 2006 - 03:32 PM

[Yzöwl]

Tomcat76, on Nov 4 2006, 07:52 PM, said:

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]

Yzöwl, on Nov 2 2006, 04:02 PM, said:

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]

RJARRRPCGP, on Nov 5 2006, 12:05 AM, said:

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

[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...

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

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]

dziubek, on Mar 13 2006, 08:52 AM, said:

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]

Tomcat76, on Nov 9 2006, 02:18 PM, said:

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!

Tomcat76, on Nov 9 2006, 02:18 PM, said:

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!

Tomcat76, on Nov 9 2006, 02:18 PM, said:

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

1="Windows CD",WIN51,,\I386

not

1="Windows CD","WIN51",,"I386"

[Tomcat76]

Yzöwl, on Nov 10 2006, 04:05 PM, said:

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.

Yzöwl, on Nov 10 2006, 04:05 PM, said:

Well using that as your example the syntax is still incorrect. It should be

1="Windows CD",WIN51,,\I386

not

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.

Hopefully we can get to the bottom of your problem now