 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Just off the top of my head:
> - Files that share the name, but not the path, of a system file are common
> indicators of malware.
> - The original file in 'system32' is protected against unauthorised
> changes (though less so in WinXP if you are using an administrator
> account).
> - The original file in 'system32' is affected by system updates.
> - You are treating a symptom, not the cause.
Good point about the auto-updates, maybe I'll make it automatically copy the
shell32.dll from system32 into windows each time I boot to make sure any
updates are reflected.
> Try searching for it in AutoRuns (from SysInternals). If it does not show
> up there, try searching for it in the registry.
>
> Also keep in mind that it might not be registered as
> "windows\shell32.dll". It could be "%WINDIR%\shell32.dll",
> "%SYSTEMROOT%\shell32.dll" or some other variant.
Nothing showed up, every shell32.dll was referenced in the system32 folder.
I don't know what else to try, but at least I have my computer back working
at a normal speed, even if it is a bit of a hacky temporary fix.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 09 Mar 2010 10:51:28 +0100, scott <sco### [at] scott com> wrote:
>
> Good point about the auto-updates, maybe I'll make it automatically copy
> the shell32.dll from system32 into windows each time I boot to make sure
> any updates are reflected.
That may be difficult if the DLL is actually being loaded by explorer.exe.
> Nothing showed up, every shell32.dll was referenced in the system32
> folder. I don't know what else to try, but at least I have my computer
> back working at a normal speed, even if it is a bit of a hacky temporary
> fix.
Grasping for straws here, but check that "Windows\system32" comes before
"Windows" in your %PATH%.
It could also be caused by a crappy shell extension with an import table
entry for "windows\shell32.dll". That would be a little more tedious to
track down, though you could come a long way by simply disabling all
non-essential extensions with ShellExView.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
> I bet there's some core code that is still from Windows 1 :-)
No. Vista added the ability to cancel an outstanding IO request that was
hanging. XP doesn't have that, so you get a timeout. Known problem fixed
years ago.
> Don't remember the last machine I used with an "A" drive, but the same
> happens with CDs and DVDs that it can't read properly.
That in part is a kernel/driver problem, since it actually *does* hang the
whole machine to a large extent.
> As I said, if I unmap the drives the problem goes away. Issue is that I
> don't want to have to remap them everytime I connect to the network
> they're on!
Shell scripts to the rescue?
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Phil Cook v2 wrote:
> The only other thing I can think of off the top of my head is UPnP
SSDP *is* UPnP.
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
|
| |
| |
|
|
From: Phil Cook v2
Subject: Re: Network devices hanging explorer
Date: 10 Mar 2010 04:21:27
Message: <op.u9chmarjmn4jds@phils>
|
|
|
| |
| |
|
|
And lo On Tue, 09 Mar 2010 22:21:04 -0000, Darren New <dne### [at] sanrrcom>
did spake thusly:
> Phil Cook v2 wrote:
>> The only other thing I can think of off the top of my head is UPnP
>
> SSDP *is* UPnP.
I thought SSDP was what found UPnP devices; so it might freeze because
it's looking or it might freeze because it's trying to interface with it.
But yes turning off SSDP should turn off UPnP too.
--
Phil Cook
--
I once tried to be apathetic, but I just couldn't be bothered
http://flipc.blogspot.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Phil Cook v2 wrote:
> And lo On Tue, 09 Mar 2010 22:21:04 -0000, Darren New <dne### [at] sanrrcom>
> did spake thusly:
>
>> Phil Cook v2 wrote:
>>> The only other thing I can think of off the top of my head is UPnP
>>
>> SSDP *is* UPnP.
>
> I thought SSDP was what found UPnP devices;
SSDP is part of uPnP, yes. It's the equivalent of WINS for netbios, tracking
the announcements.
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
they are right after all. Let's all just hang IE... ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Try using ShellExView to see if there is a misconfigured shell extension,
> or a remnant of some malware.
LOL, my AV software has flagged this as a "hacking tool" :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
>> Try using ShellExView to see if there is a misconfigured shell
>> extension, or a remnant of some malware.
>
> LOL, my AV software has flagged this as a "hacking tool" :-)
According to SecuROM (or whatever it's called), Process Explorer is a
"cracker tool", and having it installed prevents Crysis from running.
Post a reply to this message
|
|
| |
| |
|
|
From: Nicolas Alvarez
Subject: Re: Network devices hanging explorer
Date: 20 Mar 2010 17:52:14
Message: <4ba5438e@news.povray.org>
|
|
|
| |
| |
|
|
scott wrote:
>> Try using ShellExView to see if there is a misconfigured shell extension,
>> or a remnant of some malware.
>
> LOL, my AV software has flagged this as a "hacking tool" :-)
My AV used to complain about a Windows port of netcat -.-
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
