Jump to content

Codecs not installed with HFSLIP 1.6.4


Recommended Posts

Posted
You haven't read the info on IE7 slipstreaming.

After you've fixed those problems, please attach your HFSLIP.LOG, TXTSETUP.SIF (not WINNT.SIF) and SYSOC.IN_ files.

The shown matter was confirmed again.

It was confirmed not to include hotfix of IE6, and to include hotfix of IE7 temporarily removed in the test environment.

It included it again though hotfix of KB928255 was removed in the test environment.

The condition to integrate slipstreams fills the one that the problem occurred.

However, is there a condition that we some overlooked ・・・?


Posted
Do you still have the problem if you remove WINNT.SIF?

Yes, the problem still remains though WINNT.SIF is not included and it Bilded it.

HFSLIP.zip

Posted

What could be an issue is that you don't have an INF file in HFEXPERT\CODECS (or in HFSVCPACK). For some of those codecs, simple registration (what HFSLIPWU.INF does) is not enough.

I'd still like to have a look at your HFSLIPWU.INF file from that last run, though.

Posted
What could be an issue is that you don't have an INF file in HFEXPERT\CODECS (or in HFSVCPACK). For some of those codecs, simple registration (what HFSLIPWU.INF does) is not enough.

I'd still like to have a look at your HFSLIPWU.INF file from that last run, though.

HFSLIPWU.INF at that time is this.

HFSLIPWU.zip

Posted

That file looks to be fine.

I think you should try removing I263_32.drv, ir50_32.qtx and l3codecx.ax. If that doesn't help, it's surely the lack of an INF file in HFEXPERT\CODECS. I can't think of anything else because codecs install fine here.

Posted
That file looks to be fine.

I think you should try removing I263_32.drv, ir50_32.qtx and l3codecx.ax. If that doesn't help, it's surely the lack of an INF file in HFEXPERT\CODECS. I can't think of anything else because codecs install fine here.

These codecs are the one distributed ahead as CODECS.rar in the forum of HFSLIP.

However, I think that the problem is not in a single codec in this.

Because any codec is not built in but all any codecs need not be built in.

Like the RunOnce registry key's being disregarded.

However, I will try having been directed if thought about the possibility.

When the codec is built in with the RunOnceEx registry key, it would be better to verify it having though it doesn't know how to become it though hit on.

This is tried later.

Posted

I have a dumb question, how do you know that the runonce key is not being run? How do you know that the codecs are not being registered? Can you zip and post your sysoc.in_ file?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...