Re: A file is corrupt. SFC / WFP bug.
From: Jim Carlock (anonymous_at_127.0.0.1)
Date: 05/09/04
- Next message: CS: "Re: Back UP"
- Previous message: P. Jayant: "Does deleting suspected spyware files damage the Operating System?"
- In reply to: Kelly: "Re: A file is corrupt. SFC / WFP bug."
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 8 May 2004 23:27:51 -0400
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. "Kelly" wrote: Hi Jim, Too many issues, Jim! Good luck. :o) -- All the Best, Kelly "Jim Carlock" wrote: > 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 > > "Kelly" wrote: >> 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. :o) >> >> 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 > > "Jim Carlock" wrote: >> :-( >> >> 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
- Next message: CS: "Re: Back UP"
- Previous message: P. Jayant: "Does deleting suspected spyware files damage the Operating System?"
- In reply to: Kelly: "Re: A file is corrupt. SFC / WFP bug."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
