[Super-Magician]

Quote

- more flexible ISO naming with new variable (1)

Thanks for this new feature!

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.

This post has been edited by Super-Magician: 27 October 2006 - 06:17 AM

[Yzöwl]

Error dialog - 61027a, any ideas?

TIA

<Edit>
Is this relevant?
60810  - /Q /C /T:"%PREP%WORK\MSXML"
61027a - /QUIET /X:"%PREP%WORK\MSXML"

\SOURCESS\I386
    MSXML.DL_   - msxml.dll
    MSXML2.DL_  - msxml2.dll
    MSXML2R.DL_ - msxml2r.dll
    MSXML3.DL_  - msxml3.dll
    MSXML3R.DL_ - msxml3r.dll
    msxml4.ca_  - msxml4.cab
    msxml6.dl_  - msxml6.dll
    msxml6r.dl_ - msxml6r.dll
    MSXMLR.DL_  - msxmlr.dll
</Edit>

<Edit2>
I have tried to use Windows Update, to check my system but have a major problem!

I do not have an Automatic Updates service, what gives?

Even the Automatic Updates cpl, which exists is completely greyed out!
</Edit2>

This post has been edited by Yzöwl: 29 October 2006 - 12:52 PM

[Super-Magician]

Also, where's 61027b?

[Tomcat76]

Yzöwl, on Oct 29 2006, 03:33 PM, said:

Error dialog - 61027a, any ideas?

Yes. Please read the changelog for HFSLIP 1.0.

Super-Magician, on Oct 29 2006, 03:37 PM, said:

Also, where's 61027b?

You naughty boy...

[Super-Magician]

Tomcat76, on Oct 29 2006, 04:29 PM, said:

You naughty boy...

Now, here's a reminder for you to check my post above.

[Yzöwl]

Tomcat76, on Oct 29 2006, 09:29 PM, said:

Yzöwl, on Oct 29 2006, 03:33 PM, said:

Error dialog - 61027a, any ideas?

Yes. Please read the changelog for HFSLIP 1.0.

Yep, that's sorted the dialog.

It would have been better, had you updated your updates page on this forum, I didn't know that those files were updated. The changelog isn't an obvious enough method to start informing people that files are no longer supported.

What about the Automatic Updates? They still do not have a service etc.

[Super-Magician]

@Yzöwl, it's remotely possible that the bad MSXML updates did something with the Automatic Updates service. Try it again?

[Yzöwl]

I did, before I reposted.

The HFSLIP run went perfectly as did the installation. All I did after install was check in services.msc to once again find no Automatic updates service.

And before anyone stupidly asks, I dont use addons, remove files, do service 'tweaks' etc. just a few IE and cmd shell tweaks and integrate XPize, (v4.51 not the current Beta).

<Edit>
One thing though, which as an afterthought may be relevant, using XPize 4.5, my hfslip took around 17½ mins whereas useing 4.51 only takes 13½ mins. The XPize version may or may not be relevant, however it is likely that the lost 4 minutes is!
</Edit>

This post has been edited by Yzöwl: 29 October 2006 - 10:39 PM

[Tomcat76]

@Yzöwl...

It's a bit difficult for me to diagnose the problem without being able to duplicate it. Can you please post the content of the "new" AU.INF here?

[Yzöwl]

Here you go!

 
; Installation of AutoUpdate Service
; Copyright Microsoft ® 2003
[Version]
Signature="$Windows NT$"
ClassGUID={00000000-0000-0000-0000-000000000000}
LayoutFile=layout.inf
[DestinationDirs]
AUCopyFilesSys	= 11
AUDelSysFiles = 11 ; system directory
AUDelRootFiles = 25 ; windows directory
AUDelInfFiles = 17
CUNDelSysFiles  = 11     ; LDID_SYS
CUNDelInfFiles  = 17     ; LDID_INF
CUNDelTaskFile  = 10, Tasks ;LDID_WIN
[DefaultInstall]
DelFiles	= AUDelSysFiles, AUDelRootFiles, AUDelInfFiles, CUNDelSysFiles, CUNDelInfFiles, CUNDelTaskFile
DelReg		= DelAUKeys, DelCUNKeys, DelW2kAUKeys, DelOtherKeys
AddReg          = AddRegControlPanelCategory, AddRegKillBit
CopyFiles	= AUCopyFilesSys
RegisterDLLs	= AU_dlls
[AUCopyFilesSys]
[AU_dlls]
[AUDelSysFiles]
[AUDelRootFiles]
[AUDelInfFiles]
[CUNDelSysFiles]
[CUNDelInfFiles]
[CUNDelTaskFile]
[DelAUKeys]
;wuv3is
;wuauboot
;wuauclt
;wuaucpl
;auhook
;wuaures
;wuaupd
[DelCUNKeys]
[DelW2kAUKeys]
[DelOtherKeys]
; Service Startup Key
; old IUpdate 
; wuv3is.dll    
; wupdinfo.dll		
;iuctl.dll
[AddRegKillBit]
;AddRegKillBit WUV3IS
[AddRegControlPanelCategory]
[Strings]
;Non-Localizable
;Localizable
;needs to be localized exactly as the task scheduler job created by CUN
WUCUN_TS_JOBFILE = "windows critical update notification.job" 

Anything else, just let me know!

Thanks.

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

[Yzöwl]

Here you go, including the AU.inf from before!

Attached File(s)

•  files.rar (6.71K)
  Number of downloads: 10

[Kiki Burgh]

Phaneendra Rao, on Oct 31 2006, 10:58 PM, said:

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

This post has been edited by Kiki Burgh: 31 October 2006 - 12:34 PM

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

Super-Magician, on Oct 27 2006, 07:16 AM, said:

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.

Super-Magician, on Nov 2 2006, 12:22 AM, said:

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

Super-Magician, on Oct 27 2006, 07:16 AM, said:

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.

[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

 
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)

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

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]

Tomcat76, on Nov 2 2006, 08:22 PM, said:

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.

Tomcat76, on Nov 2 2006, 08:22 PM, said:

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.

Tomcat76, on Nov 2 2006, 08:22 PM, said:

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.

Tomcat76, on Nov 2 2006, 08:22 PM, said:

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

Tomcat76, on Nov 2 2006, 08:22 PM, said:

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

Me neither…

Tomcat76, on Nov 2 2006, 08:22 PM, said:

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]

Yzöwl, on Nov 2 2006, 10:20 PM, said:

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?