visual studio .net documentation: I was trying to load the MSDN Library April 2007. I put the disk in my DVD
drive (IBM Thinkpad T43p) and nothing happened. I then opened a console
window and tried dir'ing the D: drive, that hung. The machine afterwards was
unusable. I rebooted and tried again. I simply put the MSDN Library disk in
my drive and closed it. That of course executed the AutoRun (I guess) and
nothing happened. I noticed that a svchost.exe process had the CPU pegged.
I called IBM and told them that I thought something was wrong with my DVD
drive and they sent me a new one. That didn't fix the problem.

I did some searching on the net and it appears others are having similar
trouble
(https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134404&SiteID=1). I
tried the suggestion in the post and I was able to install MSDN so I guess
the problem has something to do with the services that are running. Having
MSDN installed doesn't mean I got past the problem. The CPU is pegged still
each time the MSDN disk is inserted into the DVD drive or when you attempt to
access the D: drive when the MSDN disk is in the drive. The svchost process
that has the CPU pegged is the one that's running the netsvcs services.

Does anyone know how to fix this problem?
--
Thanks,
Nick

nicknospamdu@community.nospam

Hello Nick,

Based on my experience, such hang issue may be related to your Operate
System Environment (Antivirus, or Services).
I'm afraid to say it is hard to troubleshooting such issue in Newsgroup.

General idea is that you may try to run this MSDN Library Disk on other
machine. Does the issue only occur on your current system?

Another idea is that you may press and hold the SHIFT Key when inserting
MSDN library Disk into DVD drive.This trick will disable the feature that
allows DVD room to Run Automatically.

http://support.microsoft.com/kb/126025/en-us
[How to Disable the Feature That Allows CD-ROMs and Audio CDs to Run
Automatically]

Hope this helps.
Best regards,

Wen Yuan
Microsoft Online Community Support
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks. I'm pretty sure that it is related to the services running since the
problem went away when I tried the suggestion in the post I included which
basically starts the OS in some sort of safe mode. Your suggestion of
holding down the shift key while inserting the DVD will most likely solve the
problem where the CPU pegs when I insert the disk, though accessing the disk
afterwards also appears to peg the CPU so doing a dir or maybe even the MSDN
GUI accessing the content will peg the CPU.

What I would like to do is to reconfigure, temporarily, each of the services
in that one svchost.exe that's pegging the CPU such that each service runs in
its own svchost process. This will narrow in on the service which is causing
the issue. I attempted to use WinDbg to determine which component is causing
the problem but the system is so unusable at this point I can't create a hang
dump or use perfmon to determine which thread in the process is consuming the
CPU.
--
Thanks,
Nick

nicknospamdu@community.nospam
remove "nospam" change community. to msn.com


[quoted text, click to view]