Of course, this manner of possibly giving information to the person best suited to provide a resolution and information is likely frowned upon based on previous posts I see here so we could provide back-and-forth middle-man communication if that is preferred at that time.
It is for the various reasons I've made clear from the outset.
I haven't needed support not being the least.
And just to emphasise how unreasonable I've been have a look at my first post in this thread.
and again for anybodies information that is interested, as I'm well past caring.
Other readers can draw their own conclusions given these facts.
1/ These specific files are disguised with system like names and extensions.
2/ They are stored in locations which could render a system vunerable by needing write access in system folders.
3/ They are nothing to do with the authorization manager at all as previously implied by the representative here. They are there if it is installed or not.
4/ They are not limited to this particular product, indeed at least Sampletank will create them so they are part of a scheme that IK employs, whatever that scheme's intent is does remain unclear.
5/ The files will re-appear if deleted by the user even if that user is the system administrator. (Malware)
6/ They are in fact data files which have no bearing on the actual working functionality of the product other than it will dig it's heels in if the product isn't given read/write access to them.
7/ The IK representative here is clearly touchy about the subject and unwilling to clarify their existence any further let alone their function.
8/ The IK uninstaller does not remove them although provided you no longer have any IK products installed you can subsequently remove them manually without them re-appearing.
Here is the list of those specific files again.
Windows\msocreg32.dat
Windows\System32(SysWOW64 on a 64 bit OS)\msvcsv60.dll
Windows\System32(SysWOW64 on a 64 bit OS)\w3data.vss
ProgramData\autobk.inc
AppData\Roaming\msregsvv.dll
Two of these files are named with a .dll extension which is normally given to a dynamic linked library. They are not .dll's in any recognized form they are data files.
One has an .inc extension which is normally used as an 'include' extension for higher level language code intended to be compiled into machine code.
.vss is a Microsoft reserved extension used for the system virtual shadow service.
.dat is an acceptable extension for a data file which is what all these are but note that the msocreg32 file name is intended to look like a bona fide OS file which it is not.
Now all this stuff may be innocuous and part of a naive copy protection scheme but either unawareness or reluctance shown here by the company representative leading any anything but a clear explanation leads me to think...
...If it looks like a duck, talks like a duck, then it probably is..............
Frankly you can all discuss among yourselves whether I am right or wrong about any of the above, you can even confirm it on your own machines, but I've seen enough I'm out!
I'm sorry if any of that seems in veiled or cryptic language to you Smokey but it's as clear as I can make it.
post edited by Jonbouy - 2012/03/11 15:48:22