Because I DO think its important, I wanted to distill some points from another thread into a single post, and provide my thoughts. I am not trying to stir things up, nor beat a dead horse:
Quoted from Synetech:
“I recently tried out the latest versions of SlySoft’s apps and have noticed some unusual behavior…There is a new file…The ElbyCDIO service creates then accesses it every ten seconds in a seemingly infinite loop!..you could always stop the ElbyCDIO service and note that the polling stops, then run it again and note that it starts polling again”
Quoted from ArcCoyote:
“…it is in fact checked 10 seconds by the ElbyCDIO driver and is part of the trial period enforcement…I found this thread after discovering this behavior myself and posted to confirm this behavior was expected…”
Quoted from alan1476:
“…by the way it stops checking after your key has been verified after the trial period has ended…”
Quoted from Synetech:
“…I’m not sure what you mean; are you saying that it stops if you enter a key after the trial ends? What if you enter it before? Does it delete the file?..”
Quoted from alan1476:
“Noone can verify your finding because they do not exist…Now after 4 years this one user has found something that noone else can find…”
Quoted from Synetech:
“…it was confirmed that it has started with a recent version…it would not have been brought up in the ‘past 4 years’.”
Quoted from profcolli:
INSERT list of links referencing other programs (including Windows Update, and Windows indexing) exibiting similar activities
So, what’s to complain about? After 21 days you pay for it and it stops, or you uninstall it and it stops. Just like a thousand other programs…"
Quoted from NeoTrin2000:
“We know (or based on profcolli’s findings we are almost sure) this behavior is caused by Windows Indexing Services…”
Quoted from Synetech:
“For the record, I don’t use the Windows Indexing Service…”
Quoted from NeoTrin2000:
“…but are you 100% sure it’s disabled?”
Quoted from Synetech:
“Of course…”
Quoted from profcolli:
“…Elbycdio does a FASTIO_QUERY_STANDARD_INFO as part of its design to check whether drive access is required?”
Quoted from Synetech:
“…why was it added recently? …Was it part of a new protection defeat?”
Quoted from Seabrawk:
“Should he have not brought it to anyone’s attention (on this site) and simply uninstalled it?”
Quoted from alan1476:
“…He cant get an answer to something that does not exist. CloneDVD2 has not been updated for months…it only happening to 1 person, and I doubt that CloneCDhas anything to do with it, the program has not been updated recently…I use this program since it was released in 2002 and it never exibited this behavior. So there you have 1 user with a problem.”
I would first like to point out that I have run my own tests and have verified that what Synetech has asserted from the beginning is true: Windows indexing disabled, the temp file in the c:\Windows directory is accessed every ten seconds.
As pointed out by profcolli, the process of checking a file every ‘n’ seconds, is a process used by various applications, for various reasons. In the case of the Windows indexing service, I would imagine it is a result of attempting to index certain files and is therefore “expected”. It is in those cases where it is unexpected that some poeple have expressed distaste for this sort of behavior (such is the case for the Elby products, as well as the Gemini product linked by profcolli).
As quoted by alan1476, and ArcCoyote this may be some sort of hidden trial period enforcement, although I am not sure that much effort went into reseraching this assertion. It appears profcolli has provided a better explanation from a more informed source, which is that it was “part of its design to check whether drive access is required…”
This, however, would mean that the file would continue to be polled for eternity, as long as the software is installed on the machine, regardless of the registration status (this is untested), and begs the question “How did they do it before?”
In either scenario, I am unsure if I want many applications on my machine with this type of behavior, but to each their own. I just figured that some people may still be interested in this, and thought that the original thread was prematurely closed.