M
Marvin L. Zinn
I have a new problem with an HP Pavilion running XP
home which I no doubt caused somehow.
Here is what I did:
I was trying to write a folder to a CD. The first
step the program takes when I select the folder and
"Send to Drive D" (or something like that) is
apparently to copy the files into a buffer area from
which I select "Write to CD". In this buffer area, I
noted some files which I really did not want to
include, so I began to delete them. When I came to a
file labeled "lbrdll.doc" (not sure the exact name) I
noticed that in spite of the ".doc" suffix, it had a
command prompt icon. Since this was a folder containing
mail downloads, I considered it could be a virus and
tried to delete it. It would not delete, so I went to
properties to try to find out why. Somewhere in
properties/advanced I did something that made the CD-RW
window close, and everything on the computer became
extremely slow.
Next I powered down the computer (after being
unable to do anything else for about ten minutes). It
came up very slow, but I waited perhaps an hour until I
could get into the original folder where this file
resided and did a virus check on the entire folder with
Mcafee, just updated last night. No virus was found,
and I deleted the file from there with no problem.
I restarted again, and response is still very slow,
but improves over time to perhaps 25% of normal speed.
Task manager shows normal cpu usage (0-10% most of the
time, but sometimes spiking to 100%, system idle runs
about 30-70%, and during startup the only significant
task time is for svchost.exe. BOTH TIMES I RESTARTED,
XP FOUND IT NECESSARY TO INCREASE THE PAGEFILE SIZE.
The first time it went to about 1340MB, and the second
time to 943MB.
There have been other errors and symptoms which
unfortunately I did not write down. Basically after the
system has been up for 30 minutes or so, everything
seems almost normal, only slower.
I hope someone can give me some direction to
getting my computer back to normal without losing any
recent work.
Thanx,
Marvin L. Zinn
(e-mail address removed)
Using Virtual Access
Windows 2000 build 2600
home which I no doubt caused somehow.
Here is what I did:
I was trying to write a folder to a CD. The first
step the program takes when I select the folder and
"Send to Drive D" (or something like that) is
apparently to copy the files into a buffer area from
which I select "Write to CD". In this buffer area, I
noted some files which I really did not want to
include, so I began to delete them. When I came to a
file labeled "lbrdll.doc" (not sure the exact name) I
noticed that in spite of the ".doc" suffix, it had a
command prompt icon. Since this was a folder containing
mail downloads, I considered it could be a virus and
tried to delete it. It would not delete, so I went to
properties to try to find out why. Somewhere in
properties/advanced I did something that made the CD-RW
window close, and everything on the computer became
extremely slow.
Next I powered down the computer (after being
unable to do anything else for about ten minutes). It
came up very slow, but I waited perhaps an hour until I
could get into the original folder where this file
resided and did a virus check on the entire folder with
Mcafee, just updated last night. No virus was found,
and I deleted the file from there with no problem.
I restarted again, and response is still very slow,
but improves over time to perhaps 25% of normal speed.
Task manager shows normal cpu usage (0-10% most of the
time, but sometimes spiking to 100%, system idle runs
about 30-70%, and during startup the only significant
task time is for svchost.exe. BOTH TIMES I RESTARTED,
XP FOUND IT NECESSARY TO INCREASE THE PAGEFILE SIZE.
The first time it went to about 1340MB, and the second
time to 943MB.
There have been other errors and symptoms which
unfortunately I did not write down. Basically after the
system has been up for 30 minutes or so, everything
seems almost normal, only slower.
I hope someone can give me some direction to
getting my computer back to normal without losing any
recent work.
Thanx,
Marvin L. Zinn
(e-mail address removed)
Using Virtual Access
Windows 2000 build 2600