A file is corrupt. SFC / WFP bug.

[Jim Carlock]

If one has a corrupt file on the system. And SFC and WFP are
disfunctional, meaning they don't work, except for the fact that
they copy disfunctional files over functional files...

I NEED a list of files with every update that Microsoft provides.
I also NEED a list of checksums for those files.
We all NEED a way to correct these problems.

What's the suggested method of doing this other than uninstalling
every update and then downloading them all over again and then
reinstalling them ? There has to be an easier way to get valid files
from MICROSOFT. Or at least an error proof manner in which
to get these files.

 

[Kelly]

Sheesh, Jim, is that all you want? ) Thought of applying here in the
meantime:
http://www.microsoft.com/careers/careerpath/marketing/default.mspx

 

[Jim Carlock]

Well, to tell you the truth, I want a lot more. But if I can get
those things I've listed, "you" will be elated.

"We like to make the whole world happy!" I probably should
Trademark that.

"We like to make the whole world happy!"
Trademark May 4, 2004 Jim Carlock / MicroCosmoTalk.

Microsoft already has some information in a database. They
just don't update it and what I've suggested would provide
a logical mannerism which would benefit:

(1) Microsoft
(2) The whole planetary system, including NASA and their
interplanetary vehicles.
(3) Most importantly, you! ;-)

It is relatively simple to list the files and provide that list in a
database. Microsoft already provides a half-hearted attempt:

http://support.microsoft.com/servicedesks/FileVersion/dllinfo.asp

FAULT #1: It is NOT updated on a regular daily basis.
It's months out of date. Someone AT Microsoft is not doing
their job. Most likely there is not a managed approach to
maintaining it (so the failure is that of management).

I have a gdi32.dll on my system that I can not find any
information about. Their database is a couple months out of
date.

I believe this file is a corrupted file on my system. But I don't
see an easy way to figure out where this file comes from. And
I give homage to Microsoft and the good things they've done.
They can make them better though and it won't take too much
time to do it.

Keeping their database up to date is the solution and a benefit
to them, and to you. I dare anyone to disagree. I double-
whammy dare you with fruit in between your toes or step on
your nose.

And providing a link to get the files would be relatively easy
to implement, as all that information is kept in a database that
doesn't get updated regularly. Imagine the benefits to you!
This is another solution to a worldwide problem that Microsoft
can take all the credit for.

It breaks them out of their illogical attempts to hide all files
that are updated though. It ruins their attempts to be secret.
Why do they want to be secret about anything anyways?

I'm only pushing for really beneficial things that Microsoft
CAN DO to make things easier on the rest of the world.

And it CAN be accomplished. It really can. But Microsoft
management must WANT to do it. If they don't want to do
it, then I suggest Microsoft fire their management. It would
be a great benefit to everyone on this planet. Why do folks
think they have to hide things and cover things up ?

And I apologize about being so harsh and if it comes across
being tacky. I am stating obvious failures as I see them. I
could be wrong.

I'm not into marketing. I am no salesperson. I find faulty things
and look for ways to fix and make them better. ;-)

And I really love and enjoy freedom.

--
Jim Carlock


Sheesh, Jim, is that all you want? ) Thought of applying here in the
meantime:
http://www.microsoft.com/careers/careerpath/marketing/default.mspx

 

[Kelly]

I see. )

Ok and now for the record, your tm is:

*"We like to make the whole world happy!"
Trademark May 4, 2004 Jim Carlock / MicroCosmoTalk.

* - And in order to have this done:

I had to double-whammy dare Kelly with fruit in between her toes or step on
her nose.

 

[Jim Carlock]

<g>

If I want to replace my gdi32.dll, how am supposed to do this?
Does Microsoft provide a way to do this other than reinstalling
a service pack update???

What a funny looking nose! ;-) It looks like a full moon.

Your nose: )
The moon:
http://nssdc.gsfc.nasa.gov/imgcat/html/object_page/a11_h_44_6667.html
http://nssdc.gsfc.nasa.gov/imgcat/thumbnail_pages/moon_thumbnails.html

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


I see. )

Ok and now for the record, your tm is:

*"We like to make the whole world happy!"
Trademark May 4, 2004 Jim Carlock / MicroCosmoTalk.

* - And in order to have this done:

I had to double-whammy dare Kelly with fruit in between her toes or step on
her nose.

 

[Kelly]

Depends.....as there are many reasons for the error message. Some bogus
(Norton) and some not (HP/Mystic Video Cards, etc).
http://www.dll-files.com/dllindex/dll-files.shtml?gdi32

 

[Jim Carlock]

:-(

I'm at a loss.

I don't know which file is corrupt. All I know is the PC
has a problem and won't run certain software. Two apps
are crashing and one is a simple VB program with one
line of code in it as well as an imbedded manifest.

I found the update with the new gdi32.dll but that wasn't
the problem. A dependency walker highlights mpr.dll and
indicates:

Warning: At least one module has an unresolved import
due to a missing export function in a delay-load dependent
module.

The following message is given when profiling the module
with Dependency Walker:

Second chance exception 0xC0000005 (Access Violation)
occurred in "ISTOOL.EXE" at address 0x004093E5.

The other app with line of code and a manifest tied in it,
compiles just fine but crashes upon start up outside of the
VB IDE. It runs fine inside the IDE.

Profiling yields the following message highlighted near the end:

GetProcAddress _
(0x71950000 [COMCTL32.DLL], "RegisterClassNameW")
called from "USER32.DLL" at address 0x77D83671 and
returned NULL. Error: The specified procedure could not be
found (127).

Any suggestions would be helpful. And thanks.

 

[Kelly]

You have way too many issues going on here, Jim. As you know User32.dll and
Gdi32.dll are related in the sense of the NT service packs and upgrades. At
this point, on even last week or the week before, I would suggest a 'clean'
install of XP. )

Other than that, I can only assume that getting a copy of User32.dll and
Gdi32.dll from a healthy XP system and copying them into the Winnt\System32
folder _may_ help. Sounds as though you have mismatched versions that
probably stem from an NT SP.

 

[Jim Carlock]

Okay, I did not use the link you supplied. Thanks for the link but
the file was dated 1998 and the file I was questioning (gdi32.dll)
on my system was dated 3/29/2004.

I downloaded the service pack update, which was specifically
labeled XP SP1 for the new (gdi32.dll) file.

That file is not and was not the problem. The more I look at it, it's
looking like comctl32.dll is the problem. The mpr.dll file being
highlighted in dependancy walker is documented and that is not
the problem.

http://www.dependencywalker.com/faq.html

The problem exists ONLY on XP. It doesn't exist on Win2K.
The software runs fine on Win2K. I'm not so sure that it is a
file corruption problem either, being that it could be a VS6 SP6
problem.

I don't know of a way to uninstall VS6, as Microsoft has not
provided a method to do this, so I think I'll work on a batch file
which will delete all the SP6 files.

So far the only files I'm seeing as being stashed in the WFP stash
are the Visual C runtime, oleaut32.dll and possibly a couple other
files, which I don't think I'll need to delete or worry about.

I think I'll talk about this in the following newsgroup and see if I
can get some folks to help out there.

news://microsoft.public.vb.general.discussion

I really really need a way to uninstall SP6. ;-)

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.

You have way too many issues going on here, Jim. As you know
User32.dll and Gdi32.dll are related in the sense of the NT
service packs and upgrades. At this point, on even last week
or the week before, I would suggest a 'clean'
install of XP. )

Other than that, I can only assume that getting a copy of
User32.dll and Gdi32.dll from a healthy XP system and
copying them into the Winnt\System32 folder _may_ help.
Sounds as though you have mismatched versions that probably
stem from an NT SP.

:-(

I'm at a loss.

I don't know which file is corrupt. All I know is the PC
has a problem and won't run certain software. Two apps
are crashing and one is a simple VB program with one
line of code in it as well as an imbedded manifest.

I found the update with the new gdi32.dll but that wasn't
the problem. A dependency walker highlights mpr.dll and
indicates:

Warning: At least one module has an unresolved import
due to a missing export function in a delay-load dependent
module.

The following message is given when profiling the module
with Dependency Walker:

Second chance exception 0xC0000005 (Access Violation)
occurred in "ISTOOL.EXE" at address 0x004093E5.

The other app with line of code and a manifest tied in it,
compiles just fine but crashes upon start up outside of the
VB IDE. It runs fine inside the IDE.

Profiling yields the following message highlighted near the end:

GetProcAddress _
(0x71950000 [COMCTL32.DLL], "RegisterClassNameW")
called from "USER32.DLL" at address 0x77D83671 and
returned NULL. Error: The specified procedure could not be
found (127).

Any suggestions would be helpful. And thanks.

 

[Kelly]

Hi Jim,

Too many issues, Jim! Good luck. )

Okay, I did not use the link you supplied. Thanks for the link but
the file was dated 1998 and the file I was questioning (gdi32.dll)
on my system was dated 3/29/2004.

I downloaded the service pack update, which was specifically
labeled XP SP1 for the new (gdi32.dll) file.

That file is not and was not the problem. The more I look at it, it's
looking like comctl32.dll is the problem. The mpr.dll file being
highlighted in dependancy walker is documented and that is not
the problem.

http://www.dependencywalker.com/faq.html

The problem exists ONLY on XP. It doesn't exist on Win2K.
The software runs fine on Win2K. I'm not so sure that it is a
file corruption problem either, being that it could be a VS6 SP6
problem.

I don't know of a way to uninstall VS6, as Microsoft has not
provided a method to do this, so I think I'll work on a batch file
which will delete all the SP6 files.

So far the only files I'm seeing as being stashed in the WFP stash
are the Visual C runtime, oleaut32.dll and possibly a couple other
files, which I don't think I'll need to delete or worry about.

I think I'll talk about this in the following newsgroup and see if I
can get some folks to help out there.

news://microsoft.public.vb.general.discussion

I really really need a way to uninstall SP6. ;-)

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.

You have way too many issues going on here, Jim. As you know
User32.dll and Gdi32.dll are related in the sense of the NT
service packs and upgrades. At this point, on even last week
or the week before, I would suggest a 'clean'
install of XP. )

Other than that, I can only assume that getting a copy of
User32.dll and Gdi32.dll from a healthy XP system and
copying them into the Winnt\System32 folder _may_ help.
Sounds as though you have mismatched versions that probably
stem from an NT SP.

:-(

I'm at a loss.

I don't know which file is corrupt. All I know is the PC
has a problem and won't run certain software. Two apps
are crashing and one is a simple VB program with one
line of code in it as well as an imbedded manifest.

I found the update with the new gdi32.dll but that wasn't
the problem. A dependency walker highlights mpr.dll and
indicates:

Warning: At least one module has an unresolved import
due to a missing export function in a delay-load dependent
module.

The following message is given when profiling the module
with Dependency Walker:

Second chance exception 0xC0000005 (Access Violation)
occurred in "ISTOOL.EXE" at address 0x004093E5.

The other app with line of code and a manifest tied in it,
compiles just fine but crashes upon start up outside of the
VB IDE. It runs fine inside the IDE.

Profiling yields the following message highlighted near the end:

GetProcAddress _
(0x71950000 [COMCTL32.DLL], "RegisterClassNameW")
called from "USER32.DLL" at address 0x77D83671 and
returned NULL. Error: The specified procedure could not be
found (127).

Any suggestions would be helpful. And thanks.

 

[Jim Carlock]

One issue resolved.

The ISTOOL application that was installed seemed to have been
broken in some manner. It used to work before the XP reinstall
and after the reinstall it wasn't working.

(1) I reinstalled ISTOOL, and that didn't fix it.

(2) I installed a newer version over the ever slightly older version
and that didn't fix it.

(3) I installed the newer version again from a newer download and
that didn't fix it.

(4) I uninstalled it, then reinstalled it and that finally fixed it.

Installation program was checking version numbers and for some
reason it wouldn't reinstall itself if the same version was already
installed. The uninstall worked well and deleted the corrupt file
there and the reinstall then fixed whatever was wrong.

Whew. That one was driving me nuts for a week.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.

:
Hi Jim,

Too many issues, Jim! Good luck. )

--
All the Best,
Kelly

Okay, I did not use the link you supplied. Thanks for the link but
the file was dated 1998 and the file I was questioning (gdi32.dll)
on my system was dated 3/29/2004.

I downloaded the service pack update, which was specifically
labeled XP SP1 for the new (gdi32.dll) file.

That file is not and was not the problem. The more I look at it, it's
looking like comctl32.dll is the problem. The mpr.dll file being
highlighted in dependancy walker is documented and that is not
the problem.

http://www.dependencywalker.com/faq.html

The problem exists ONLY on XP. It doesn't exist on Win2K.
The software runs fine on Win2K. I'm not so sure that it is a
file corruption problem either, being that it could be a VS6 SP6
problem.

I don't know of a way to uninstall VS6, as Microsoft has not
provided a method to do this, so I think I'll work on a batch file
which will delete all the SP6 files.

So far the only files I'm seeing as being stashed in the WFP stash
are the Visual C runtime, oleaut32.dll and possibly a couple other
files, which I don't think I'll need to delete or worry about.

I think I'll talk about this in the following newsgroup and see if I
can get some folks to help out there.

news://microsoft.public.vb.general.discussion

I really really need a way to uninstall SP6. ;-)
--
Jim Carlock

You have way too many issues going on here, Jim. As you know
User32.dll and Gdi32.dll are related in the sense of the NT
service packs and upgrades. At this point, on even last week
or the week before, I would suggest a 'clean'
install of XP. )

Other than that, I can only assume that getting a copy of
User32.dll and Gdi32.dll from a healthy XP system and
copying them into the Winnt\System32 folder _may_ help.
Sounds as though you have mismatched versions that probably
stem from an NT SP.

--
All the Best,
Kelly

:-(

I'm at a loss.

I don't know which file is corrupt. All I know is the PC
has a problem and won't run certain software. Two apps
are crashing and one is a simple VB program with one
line of code in it as well as an imbedded manifest.

I found the update with the new gdi32.dll but that wasn't
the problem. A dependency walker highlights mpr.dll and
indicates:

Warning: At least one module has an unresolved import
due to a missing export function in a delay-load dependent
module.

The following message is given when profiling the module
with Dependency Walker:

Second chance exception 0xC0000005 (Access Violation)
occurred in "ISTOOL.EXE" at address 0x004093E5.

The other app with line of code and a manifest tied in it,
compiles just fine but crashes upon start up outside of the
VB IDE. It runs fine inside the IDE.

Profiling yields the following message highlighted near the end:

GetProcAddress _
(0x71950000 [COMCTL32.DLL], "RegisterClassNameW")
called from "USER32.DLL" at address 0x77D83671 and
returned NULL. Error: The specified procedure could not be
found (127).

Any suggestions would be helpful. And thanks.