(Top posting to save people the need to plow through a lot of
stuff)
Thank you, Sietse.
I appreciate your explanation. I'm not certain that Sygate is
causing the HD "blips." I only know that the activity began
right after I put it onto my system.
I have two process display utilitites right now. However, the
program that you described sounds cool in that it displays action
involving the hard drive.
Thanks again.
Richard
in message | Richard Steinfeld wrote:
| > Sietse Fliege wrote:
|
| >> FileMon from
www.sysinternals.com may be of help here.
| >
| > Thanks. Would you please explain and point the way toward
what
| > you think we may find of use. Tell us why.
|
| We? Us? Is that a royal plural? (Don't know the English
phrase).
|
| First: I have no experience with Sygate.
| Now, let me quote a bit more of what you said:
|
| > Immediately after I installed Sygate this last time, I have
| > noticed a steady use of my hard disk at an almost rhythmic
rate.
|
| You seem to be sure that this new hard disk activity is caused
by Sygate
| and you therefor plan to reinstall it.
| However, there is always a chance that it's just a coincidence.
| Something else might (however unexpectedly) be the cause.
| These coincidences do happen and reinstalling Sygate therefor
just might
| be a little drastic.
| Installing FileMon means merely installing a simple executable
and
| adding one registry key. FileMon also might come in handy in
other
| occasions, anyway.
| You would only have to run it a relatively short time to check
out which
| process is accessing which file(s).
|
| > The HD usage is so brief that the "HD in use" LED isn't
visible.
| > But I hear the head motor for an instant.
| > I see no indication that anything is engaged in the system to
| > cause this. On Sygate's web site, there was a FAQ answer that
| > mentioned something about unusual system activity that can be
| > caused by a "dirty" installation of the program: in other
words,
| > an installation on a computer that's already got programs and
| > TSRs in memory at the time of installation.
|
| What if it turns out that Sygate indeed is the cause?
|
| Someone recently posted this:
| "The hard drive LED indicates that my p2p program, WinMX 3.31,
keeps
| accessing the hard drive every 14 or 29 seconds, while no
transfer (or
| any other activity) is underway, until I close WinMX."
| He was a bit worried, but running FileMon learned him that
WinMX was
| writing to its settings file.
| That reassured him enough that nothing ontowards was happening.
|
| The activity you see might be comparable and not too unusual.
| It might be different from the "unusual system activity"
described in
| the FAQ. (Hard for me to gauge anyway.)
|
| And in the probably more likely event that the FAQ answer
applies, it
| might still be useful to see what files are accessed, before
you
| reinstall and solve the issue.
|
| HTH
|
| --
| Cheers,
| Sietse Fliege
|