Hello,

Recently I have been getting the following error when starting up a
couple programs and when I installed a program once (after the fact) as
well. Here is the error:

"The procedure entry point symbol could not be located in the dynamic
link library SHELL32.dll"

Any idea as to of what could be causing this, but most importantly how
to fix it? Any help would be greatly appreciated. Thank you.


--
Galskygge

Hi,

Verify the system file set. Click start and type CMD, then right click the
start menu entry and choose 'run as administrator'. Click continue at the
UAC prompt. From the command line, run:

sfc /scannow

There may be .log errors, do not concern yourself with them. Once this
process has run through, close the command prompt and see if there are still
issues with those programs. If so, check that they are actually compatible
with Windows Vista.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Galskygge" wrote in message
...

Hello,

Recently I have been getting the following error when starting up a
couple programs and when I installed a program once (after the fact) as
well. Here is the error:

"The procedure entry point symbol could not be located in the dynamic
link library SHELL32.dll"

Any idea as to of what could be causing this, but most importantly how
to fix it? Any help would be greatly appreciated. Thank you.


--
Galskygge

Galskygge;926645 Wrote:
Hello,

Recently I have been getting the following error when starting up a
couple programs and when I installed a program once (after the fact) as
well. Here is the error:

"The procedure entry point symbol could not be located in the dynamic
link library SHELL32.dll"

Any idea as to of what could be causing this, but most importantly how
to fix it? Any help would be greatly appreciated. Thank you.

It could be any application that wants to call a function in
Shell32.dll
When you get the error try to narrow down the program. If it happens
with
more than one program it could be that the dll is corrupt. Or it could
be that the program that is trying to call the function in the .dll has
a typo and the function name is misspelled, or the address got
overwritten. It's impossible to say until you know which apps trigger
the error.

Where it mentions the symbol not being there it's a possibility that
the program was developed against a debug version of the OS with
symbolic info. You may have mistakenly gotten the debug version of the
program instead of the release version.
Again, see if you can look for a program that is hung while the error
dialog is showing.


--
MilesAhead

"How come we don't know the I.Q. of the guy who invented the test?"

For definite I can say that it happens whenever I open up Trillian,
IZarc, and when I installed a couple of things recently. I've had
Trillian and IZarc on my comp for a year or less before I started
getting this error. It couple be possible that the dll is corrupt then.
I had my suspicions about that but wasn't really sure to be honest. Is
it possible to download the dll or do I actually have wipe my hard drive
out and reformat windows? I pray that the second option doesn't have to
be the answer. Thank you for your response/help, by the way!


--
Galskygge

Galskygge;928169 Wrote:
For definite I can say that it happens whenever I open up Trillian,
IZarc, and when I installed a couple of things recently. I've had
Trillian and IZarc on my comp for a year or less before I started
getting this error. It couple be possible that the dll is corrupt then.
I had my suspicions about that but wasn't really sure to be honest. Is
it possible to download the dll or do I actually have wipe my hard drive
out and reformat windows? I pray that the second option doesn't have to
be the answer. Thank you for your response/help, by the way!

You might try this 'System File Check Tool'
(http://www.vistax64.com/software-too...heck-tool.html)

My Vista PC is preinstalled so I'm not sure what Vista does if you put
the install CD/DVD in and do a Repair. I would try that file check
thing first. It's from Vista Forums so I doubt it's anything nasty. If
you have the Vista install CD/DVD then you might google on Vista Repair
and see if you can get details on what files it replaces. Maybe on MS
site there's a list.


--
MilesAhead

"How come we don't know the I.Q. of the guy who invented the test?"

I have Vista preinstalled as well. There's a way to reformat/repair even
with it preinstalled. I was just hoping to bypass using any of that to
make sure I don't lose anything on my comp most definitely. I went ahead
and downloaded the System File Check Tool, so wish me luck. Thanks for
your help!


--
Galskygge

Well, I tried the System File Check Tool, and so far no luck. I'm off to
find a program to attempt to fix this problem now.


--
Galskygge

Galskygge;931312 Wrote:
Well, I tried the System File Check Tool, and so far no luck. I'm off to
find a program to attempt to fix this problem now.

The other thing you can try is make it give the error again. If it
gives an error code or an address, search on it. The error code will
usually look like "0xC0000xxx" where the x's are digits and the address
is usually 4 digits a colon and 8 digits like 0100:00400010 or
something. Usually bug reports have the error code and/or address where
it crapped out to facilitate searches.


--
MilesAhead

"How come we don't know the I.Q. of the guy who invented the test?"

I tried what you said but for whatever reason there wasn't any sort of
an error code at all. I grabbed a screen shot of the error incase it
helps. Hopefully I uploaded it to this thread correctly.


+-------------------------------------------------------------------+
|Filename: error.jpg |
|Download: http://www.vistax64.com/attachment.p...achmentid=9266 |
+-------------------------------------------------------------------+

--
Galskygge

Galskygge;931742 Wrote:
I tried what you said but for whatever reason there wasn't any sort of
an error code at all. I grabbed a screen shot of the error incase it
helps. Hopefully I uploaded it to this thread correctly.

According to the error dialog it's looking for a symbol or function
named "_b"
I don't think it likely MS chose such a short name for a function so I
have to think some memory is getting overwritten. For example if the
program uses a variable stored on the Stack, as in declared locally in a
procedure or function, it may have used the variable without
initializing it, or it may be a variable that can be set from outsite
and it wasn't declared as volatile or something like that. IOW, it's
either a programming error or buffer overrun type problem most likely.
If you have a variable for text that allows 32 bytes of space and right
after that you have another variable, if somebody puts 40 bytes into the
first variable, it overwrites the 2nd. You get garbage. You should
probably post a bug report with the software developer/company.


--
MilesAhead

"How come we don't know the I.Q. of the guy who invented the test?"