ie6sp1 : Repair Function Blocked - Anyone know of a fix?

[den]

Robert,

Thanks for this. Alas, changing switch order hasn't resolved it -
just get a slightly different error message <<DllInstall in
digest.dll failed. Return code was 0xc0000005>> [unable to locate
with Dependency Walker]. Btw "/I" was a typo!

Now where have we seen that before?

Are you ready now to try those suggestions I made then? <eg>


Robert
---

Is there a way one can pinpoint the Entry Point/export
DllRegister/DllUnregister problem and then fix it? Does software
exist that can do the job for novices like me?

Thanks again for your help and patience.

All the best,
Denis

Robert,

Thanks for this.

<<Are you ready now to try those suggestions I made then?>>

Yes please - and thanks for your patience too. I had a strong hunch I may
have missed something. The problem with being a novice - and only having
partial knowledge - is that it can be extremely difficult to spot
significance and exceptionally easy to overlook it.

I imagine you are probably aware of the key limitation and paradox of
knowledge development technology. The quality of any knowledge development
technology is ultimately only ever as good as the quality of questions from
the end-user. This in turn depends as much on the end-user's knowledge of
what they do not know as on what they do know. So we are making great
strides with knowledge development technology on the one hand ... whilst, on
the other, the chasm widens in developing the kind of thinking needed in
order for people to be capable of using it. It's an interesting dilemma.

That aside, I think I have probably learnt enough from my mistakes to now
recognise and understand the steps I previously missed.

Once again, very many thanks for all your help.

All the best,
Denis

 

[den]

Robert,

Thanks for this. Alas, changing switch order hasn't resolved it -
just get a slightly different error message <<DllInstall in
digest.dll failed. Return code was 0xc0000005>> [unable to locate
with Dependency Walker]. Btw "/I" was a typo!

Now where have we seen that before?

Are you ready now to try those suggestions I made then? <eg>


Robert
---

Is there a way one can pinpoint the Entry Point/export
DllRegister/DllUnregister problem and then fix it? Does software
exist that can do the job for novices like me?

Thanks again for your help and patience.

All the best,
Denis

Robert,

It occurs my response to your message may have been misleading.

<<Are you ready now to try those suggestions I made then?>>

Yes, I would welcome that and would very much appreciate it if you could run
through the steps again, so I can spot what it is I've been missing.

<<That aside, I think I have probably learnt enough from my mistakes to now
recognise and understand the steps I previously missed.>>

This remark wasn't intended as a rejection of your kind offer. What I was
trying to say was - once able to see the full set of steps - I should now be
much better placed to recognise what it is I have been missing.

I do hope you did not think I was being dismissive - especially with all the
considerable help that you have already given. Once again, many thanks for
all your advice.

Denis

 

[Robert Aldwinckle]

Robert,

Thanks for this. Alas, changing switch order hasn't resolved it -
just get a slightly different error message <<DllInstall in
digest.dll failed. Return code was 0xc0000005>> [unable to locate
with Dependency Walker]. Btw "/I" was a typo!

Now where have we seen that before?

Are you ready now to try those suggestions I made then? <eg>


Robert
---

Is there a way one can pinpoint the Entry Point/export
DllRegister/DllUnregister problem and then fix it? Does software
exist that can do the job for novices like me?

Thanks again for your help and patience.

All the best,
Denis

Robert,

It occurs my response to your message may have been misleading.

<<Are you ready now to try those suggestions I made then?>>

Yes, I would welcome that and would very much appreciate it if you could run
through the steps again, so I can spot what it is I've been missing.

<<That aside, I think I have probably learnt enough from my mistakes to now
recognise and understand the steps I previously missed.>>

This remark wasn't intended as a rejection of your kind offer. What I was
trying to say was - once able to see the full set of steps - I should now be
much better placed to recognise what it is I have been missing.

I do hope you did not think I was being dismissive - especially with all the
considerable help that you have already given. Once again, many thanks for
all your advice.

Actually I thought it meant you were going to take a stab at rereading
the suggestions I had previously made that you hadn't acted on yet.

The most important one was to see if drwatson can be made to give
you more information about that crash. You need to know more about
what is going on there I think.

Subject: Re: ie6sp1 : Repair Function Blocked - Anyone know of a fix?
Date: Fri, 16 Jul 2004 08:45:58 -0400


Good luck

Robert
---

 

[den]

...
Robert,

Thanks for this. Alas, changing switch order hasn't resolved it -
just get a slightly different error message <<DllInstall in
digest.dll failed. Return code was 0xc0000005>> [unable to locate
with Dependency Walker]. Btw "/I" was a typo!


Now where have we seen that before?

Are you ready now to try those suggestions I made then? <eg>


Robert
---



Is there a way one can pinpoint the Entry Point/export
DllRegister/DllUnregister problem and then fix it? Does software
exist that can do the job for novices like me?

Thanks again for your help and patience.

All the best,
Denis

Robert,

It occurs my response to your message may have been misleading.

<<Are you ready now to try those suggestions I made then?>>

Yes, I would welcome that and would very much appreciate it if you
could run through the steps again, so I can spot what it is I've
been missing.

<<That aside, I think I have probably learnt enough from my mistakes
to now recognise and understand the steps I previously missed.>>

This remark wasn't intended as a rejection of your kind offer.
What I was trying to say was - once able to see the full set of
steps - I should now be much better placed to recognise what it is I
have been missing.

I do hope you did not think I was being dismissive - especially with
all the considerable help that you have already given. Once again,
many thanks for all your advice.

Actually I thought it meant you were going to take a stab at rereading
the suggestions I had previously made that you hadn't acted on yet.

The most important one was to see if drwatson can be made to give
you more information about that crash. You need to know more about
what is going on there I think.

Subject: Re: ie6sp1 : Repair Function Blocked - Anyone know of a fix?
Date: Fri, 16 Jul 2004 08:45:58 -0400


Good luck

Robert
---

Robert,

Very many thanks for this. I have been over it again with a tooth comb and
as far as I can see haven't missed anything and nothing has changed. Some
of the information was acquired by slightly different methods but the
objectives and outcomes remained the same.

a) Prospective Ram Problem in a dependent module.

- Nothing showed under Dr Watson
- <<Return Code 0cx0000005>> didn't figure as a page fault (it looks very
similar to the references given to entry points in Dependency Walker, though
I have run through the various dependencies and been unable to locate it.)
- Have run extensive tests via a RAM diagnostic software programme -
including multiple pass burn in tests etc - and no problems showed.

b) Checking File Validity

- Carried out tests you suggested using software that outputs to Excel,
instead, to assist analysis
- In addition, created a baseline database from Fixie.inf/Dll Help

Conclusion:

Everything seems to point to a problem with the DllInstall function with
digest.dll. This is due to there being no entry point for DllRegisterServer.
The key information I am still seem unable to obtain is how to edit and fix
such a problem. Everything seems to point to this being done using C++.
However, << Frankly I don't see any advantage to using it [C++] over
regsvr32.exe>> implies that you know a method that does not require C++
programming skills?

If this is the case, I would very much appreciate it if you could share this
information. You have have been extremely helpful in enabling me to
identify the problem. It would be brilliant if you also happen to have
information on the tools with which to fix it. Whatever the case, thank you
very much indeed for all your valuable help.

Denis

 

[Robert Aldwinckle]

....

a) Prospective Ram Problem in a dependent module.

- Nothing showed under Dr Watson
- <<Return Code 0cx0000005>> didn't figure as a page fault (it looks very
similar to the references given to entry points in Dependency Walker, though
I have run through the various dependencies and been unable to locate it.)
- Have run extensive tests via a RAM diagnostic software programme -
including multiple pass burn in tests etc - and no problems showed.

That sounds good. I still think that that 0xc0000005 represents a page
fault though. It may have been trapped so Dr Watson wasn't called.
An example of what the code might have been to have caused such a thing
is: assuming the existence of a pointer and then trying to use it without testing
somehow for its validity. The code fortunately protected itself from crashing
the program completely but hasn't left sufficient diagnostics about the
error/recovery situation to allow you to figure out what needs to be repaired.
That is why we need to trace the flow up to the crash.

Unfortunately I have never used your OS or its Dr Watson so I can only go
by analogy from previous experience with Dr Watson under Windows 3.1. ;o
There IIRC there was a way to increase the sensitivity to page faults
and even report all of them. I think it involved editing an .ini file.
Does the offline help give you any clues about how you could do something
like that? BTW I'm only suggesting Dr Watson because I know that
it is a standard tool. If you have something like Visual Studio you
could use its debugger instead.


There is the still the other alternative that I suggested: using FileMon
to get a list of .dlls accessed when the regsvr32 /i /n digest.dll runs
on both systems. It wouldn't be as reliable a list as a Stack Back Trace
from a dump would be but you would undoubtedly have different
lists from both systems and thus have something new to look at.

Hmm... apparently I have a digest.dll on my system too,
undoubtedly not the same but perhaps similar enough.
Anyway, start FileMon; press Ctrl-L to set the filters.
I used Include: regsvr32*dll Highlight: digest.dll
Then Run... regsvr32 /i /n digest.dll
Stop the trace when you get the prompt that regsvr32
was successful (for the good case) and when you get
whatever the symptom you get for the bad case.

Look after the highlighted lines (i.e. after digest.dll entries)
FWIW I see: rpcss.dll, security.dll, SECUR32.dll after them.
There's more of course but I think that they will be for when the
prompt was being generated.

Even if you don't do the FileMon traces and comparisons
yourself it could be worthwhile to compare the properties
of those three modules on both systems and perhaps
replace them.


Good luck

Robert
---

 

[den]

...

That sounds good. I still think that that 0xc0000005 represents a
page
fault though. It may have been trapped so Dr Watson wasn't called.
An example of what the code might have been to have caused such a
thing
is: assuming the existence of a pointer and then trying to use it
without testing somehow for its validity. The code fortunately
protected itself from crashing the program completely but hasn't left
sufficient diagnostics about the error/recovery situation to allow
you to figure out what needs to be repaired. That is why we need to
trace the flow up to the crash.

Unfortunately I have never used your OS or its Dr Watson so I can
only go
by analogy from previous experience with Dr Watson under Windows
3.1. ;o
There IIRC there was a way to increase the sensitivity to page
faults
and even report all of them. I think it involved editing an .ini
file.
Does the offline help give you any clues about how you could do
something
like that? BTW I'm only suggesting Dr Watson because I know that
it is a standard tool. If you have something like Visual Studio
you
could use its debugger instead.


There is the still the other alternative that I suggested: using
FileMon
to get a list of .dlls accessed when the regsvr32 /i /n
digest.dll runs
on both systems. It wouldn't be as reliable a list as a Stack Back
Trace
from a dump would be but you would undoubtedly have different
lists from both systems and thus have something new to look at.

Hmm... apparently I have a digest.dll on my system too,
undoubtedly not the same but perhaps similar enough.
Anyway, start FileMon; press Ctrl-L to set the filters.
I used Include: regsvr32*dll Highlight: digest.dll
Then Run... regsvr32 /i /n digest.dll
Stop the trace when you get the prompt that regsvr32
was successful (for the good case) and when you get
whatever the symptom you get for the bad case.

Look after the highlighted lines (i.e. after digest.dll entries)
FWIW I see: rpcss.dll, security.dll, SECUR32.dll after them.
There's more of course but I think that they will be for when the
prompt was being generated.

Even if you don't do the FileMon traces and comparisons
yourself it could be worthwhile to compare the properties
of those three modules on both systems and perhaps
replace them.


Good luck

Robert
---

Robert,

Very many thanks - plenty of food for thought. Am about to take a short
break and so will report back later. Btw Filemon only revealed one
discrepancy:

Regsvr32: FFE9D77FF Attributes c:\windows\system\regsvr32.exe.local Not
Found

Checked properties. None ticked. Selected Archive. Ran Regsvr32 again - no
change to either DllInstall error message or to Not Found message in
Filemon.

Will be in touch after the break and once again, thanks for all your help.

Denis

 

[den]

...

That sounds good. I still think that that 0xc0000005 represents a
page
fault though. It may have been trapped so Dr Watson wasn't called.
An example of what the code might have been to have caused such a
thing
is: assuming the existence of a pointer and then trying to use it
without testing somehow for its validity. The code fortunately
protected itself from crashing the program completely but hasn't left
sufficient diagnostics about the error/recovery situation to allow
you to figure out what needs to be repaired. That is why we need to
trace the flow up to the crash.

Unfortunately I have never used your OS or its Dr Watson so I can
only go
by analogy from previous experience with Dr Watson under Windows
3.1. ;o
There IIRC there was a way to increase the sensitivity to page
faults
and even report all of them. I think it involved editing an .ini
file.
Does the offline help give you any clues about how you could do
something
like that? BTW I'm only suggesting Dr Watson because I know that
it is a standard tool. If you have something like Visual Studio
you
could use its debugger instead.


There is the still the other alternative that I suggested: using
FileMon
to get a list of .dlls accessed when the regsvr32 /i /n
digest.dll runs
on both systems. It wouldn't be as reliable a list as a Stack Back
Trace
from a dump would be but you would undoubtedly have different
lists from both systems and thus have something new to look at.

Hmm... apparently I have a digest.dll on my system too,
undoubtedly not the same but perhaps similar enough.
Anyway, start FileMon; press Ctrl-L to set the filters.
I used Include: regsvr32*dll Highlight: digest.dll
Then Run... regsvr32 /i /n digest.dll
Stop the trace when you get the prompt that regsvr32
was successful (for the good case) and when you get
whatever the symptom you get for the bad case.

Look after the highlighted lines (i.e. after digest.dll entries)
FWIW I see: rpcss.dll, security.dll, SECUR32.dll after them.
There's more of course but I think that they will be for when the
prompt was being generated.

Even if you don't do the FileMon traces and comparisons
yourself it could be worthwhile to compare the properties
of those three modules on both systems and perhaps
replace them.


Good luck

Robert
---

Robert,

Just to let you know a clean install W98SE/ie6sp1 finally did the trick and
to thank you for all your help.

Very best wishes,

Denis