My Documents

[wesleyw]

A member of the SMT has a very large user area around 24-30gb which we allow not of music or videos just work. The my documents is redirected to n:\ which is there user area. When viewing via N: drive there aren't any problems or at least there does not seem to be any. However when clicking on my documents icon explorer crashes after a few seconds upon displaying the directory. Any ideas?


Wes

[SYNACK]

Got any dodgy codecs on there, even if there are no video files a slightly old xvid codec or similar may be crashing out thanks to it tripping over DEP have had a similar issue a couple of months ago. Could also be a rubbish NIC/NIC driver that gives up when confronted with so many requests in short succession as it grabs all of the details.

[Domino]

Could also be a piece of software that puts an extension into explorer that has trouble over the network.

[wesleyw]

Why would it work when accessing via drive letter and not when going through the my documents link?


Wes

[Domino]

because surely my documents has other connotations as a system folder..?

[Liam_uk]

try veiwing the properties of the folder from the server

[Geoff]

It's probably the UNC path tripping up a buggy explorer extension.

[wesleyw]

How would I go about fixing that Geoff?

Wes

[Geoff]

1. download ShellExView from here
ShellExView - Shell Extension Manager For Windows
2. Disable your shell extensions one by one until the problem goes away
3. Well done you've found the buggy one. Update, remove or replace it.

[dhicks]

When viewing via N: drive there aren't any problems or at least there does not seem to be any. However when clicking on my documents icon explorer crashes after a few seconds upon displaying the directory. Any ideas?

Dodgy auto-start virus - i.e. a virus that distributes itself by installing its own autostart.inf so it gets run when you open a volume. Don't know if opening My Documents starts autorun.inf, but it could well do, and these viruses seem to be badly written enough to get confused and crash should they find themselves at the root of My Documents instead of at the root of a drive as they expected.

Note that simply checking for autorun.inf via explorer won't work as these viruses hide themselves quite well - you'll need to check the PC in question by booting from a CD (Linux boot CD of some sort, or the Windows install CD in repair mode) or check the file area on the server.

--
David Hicks