nickdu
2007-09-06 20:46:02 UTC
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?
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
***@community.nospam
remove "nospam" change community. to msn.com
Thanks,
Nick
***@community.nospam
remove "nospam" change community. to msn.com