Won't work if I change ENU by FRA. :snif:

Thanks anyway. :/

I used HFSLIP_60417-rc3.CMD
I did not use HFAAO and did not remove *.CAT


In phaze T-13 I have the errors :
"While loading C:\ WINDOWS \ SYSTEM32 \ INETCOMM.DLL stepped out the error. The file can be not installed or damaged".

It is also similarly from :
c:\ THE PROGRAMS FILES \ OUTLOOK EXPRESS \ MSOE.DLL

dziubek

edit
Have I to rename WindowsXP-KB904942-v2-x86-PLK inside HF?

This post has been edited by dziubek: Apr 18 2006, 04:06 PM

[Edited]

Remove the Cumulative MSOE update for XPSP1. You only need the one for SP2. There are a couple of other hotfixes there that are for SP1.

This post has been edited by Tomcat76: Apr 18 2006, 03:36 PM

I used the test version called HFSLIP_60412c.CMD with WINDOWS XP SP2 and all the updates works fine.

Except for the WindowsXP-KB904942-v2-x86-ESN.exe (Spanish language).

The files that this update contains are these:
_sfx_.dll
_sfx_0000._p
_sfx_0001._p
_sfx_0002._p
_sfx_0003._p
_sfx_0004._p
_sfx_0005._p
_sfx_0006._p
_sfx_0007._p
_sfx_0008._p
_sfx_0009._p
_sfx_0010._p
_sfx_0011._p
_sfx_0012._p
_sfx_manifest_
Update/update.ver

This update doens´t seams to work. It´s the problem fixed in the new release (The HFSLIP_60417-rc3.7z)???

All the others updates works fine with the Spanish Version of Windows XP SP2.

Thanks in advance.
Zartrix

The latest version of KB904942-v2 (yes, there's a second version of the second version) is only obtainable from Windows Update or the Windows Update Catalog site. Either download it yourself from the Windows Update Catalog site or use the direct download link in the following thread:

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

I just added the Spanish file.

I used Your list of hotfixes and I cleaned unnecessary hotfixes in HF. Problems don't step out now. Thanks.

dziubek

EDIT:

I again have the problem with framedyn.dll
caused by some ADDONS surely.
Programmes from HFAAO were not installed.. I will execute additional tests and write about my observations.

This post has been edited by dziubek: Apr 19 2006, 11:05 AM

You found it?

The problem with registering components caused damaged SFC > DLL. I apologize this was my fault .

If you have problems with Addons I need your txtsetup.sif as well.

So your problem with Windows Update is fixed?

dziubek...

The "Microsoft Windows Publisher" thing is the Windows Update Agent. If you still get this problem, it means WUA20 doesn't slipstream (properly) into a Polish Windows XP. In that case, download the attached file into the HFSLIP folder and run it (SOURCESS folder must be present). Then ZIP the following files and attach it here:
- WUfiles.txt (generated by the attached file)
- AU.IN_ from SOURCE\I386
- AU.IN_ from SOURCESS\I386
- HFSLIPWU.INF from SOURCESS\I386

getWU.cmd outputs a list of the WUA20 files in the SOURCESS\I386 folder including the creation date.

WU does not work in the order to the end, because it updated files after starting. Was the new version accessible?



"Take the newest software of the extension WINDOWS UPDATE"

I send my txtsetup.sif in the attachment.

You need to remove the addon that contains "AEncoder.cab". Where did you download it from?

I downloaded from here:

http://ryanvm.net/forum/viewtopic.php?p=23237#23237
The update went out today:
"
Silent update to 1.0b
-Changed one line in Entries_AudioEncoders.ini.
"

I also updated several different addons.I will write about the effect by in several hours.

dziubek

I had problem with %maininf% in the textmode:
"Copying the file % maininf % it was not possible"


I again have the problem with framedyn.dll and srclient.dll.
Programmes from HFAAO were not installed...

dziubek

This post has been edited by dziubek: Apr 19 2006, 11:34 PM

hi guys!

pardon for getting off the topic ... but i recall having read here somewhere about some RyanVM remove components (addons) that i could use in HFSLIP to remove some windows components ...

i'd appreciate too if someone can give me tips to remove the ff via HFSCLEANUP way of course:
(1) MSN Explorer
(2) Tour
(3) MSN Messenger
(4) non-Eng languages
(5) non-Eng keyboards

thanks much!

By the look of it, the problem is with one of your addons. Find your Sysoc.inf file (sysoc.in_ compressed in your i386 dir) and check that, see if there are any weird errors in it also. "Slipstreams" such as these you have used arent a very good way to install a program because unless they are written perfectly, one single broken one will stop every single one of them from installing.

Have you tried all these updates in another program such as nLite to make sure its not just a HFSlip problem? What it looks like to me is one of those addon makers didnt specify the %maininf% properly in his entries_whatever.ini. I suppose you could extract all the cab files and search for %maininf% in them to see which ones use it, then check them for errors by hand. Even then, there are obviously more errors in the secondary inf files that are called in your sysoc file since its not installing any of them.

Kiki - There are instructions for HFCLEANUP are here, click on the HFEXPERT link. You are on your own with XP, if you use all of the reducers, your installation may not work. There wasn't any want or need for reducing XP, so I decided not to create reducers for it. BTW, you could always NLITE the sourcess folder to remove things too.

This post has been edited by tommyp: Apr 20 2006, 03:52 AM

Kiki: I believe you were referring to Windows Messenger, not MSN Messenger. There is a difference. MSN Messenger is not installed by Windows Setup.

To prevent Windows Messenger from being installed, you can add an entry to the [Components] section of WINNT.SIF



or you can create the following script and place it in HFSVCPACK.



This post has been edited by Super-Magician: Apr 23 2006, 01:44 PM

Yes. That's because of that odyn1982_AudioUtilities_Addon_v1.0.cab addon.


Concerning your Windows Update problem...
I noticed that wuaucpl.cpl is being updated 13 minutes after the Windows Update files are integrated into the new source by HFSLIP. I suppose XPize is doing that as I can't imagine anything else running 13 minutes after new binaries are integrated.

Do you still have the WindowsUpdate.log file from a test installation of Windows? It is located inside C:\WINDOWS. Don't confuse it with "Windows Update.log":
WindowsUpdate.log = Windows Update
Windows Update.log = Windows Update Catalog
I need the first.

This post has been edited by Tomcat76: Apr 20 2006, 08:45 AM

Would I write email to the author Addon but I do not know what to write so that he improves him ?

This post has been edited by dziubek: Apr 20 2006, 09:59 AM