Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

jv16 wrote
DasFox wrote

The fact is, this is coming from JV16, otherwise what are we saying now, that under a clean install of XP Pro with only your hardware drivers, XP triggers this effect, if so then there is a bug against JV16 in regards, towards the OS, either way, the problem is still coming from JV16 somewhere.


But if you'll look, you'll see the installer was done and now JV16 is beginning to run for the first time, so it actually looks like the program when it begins it's first run creates it at that point.

Could you repeat the test by running the virtual copy of Windows in Safe Mode?


Ok video now in Safe Mode: (Watch full screen to see it cleaner.)


http://www.mediafire.com/?g1re7d46wnsexlz

This is on Windows 7 x86 Professional and Windows 7 x64 Professional.


I confirm that Sys6925.Config Collection.sys is created by the installation of jv16 PowerTools 2010...on both x64 and x86 Windows 7. Here are the steps to cause it to be created.


1. Fully uninstall jv16 PowerTools 2010. Save nothing during the installation.


2. Do a Search on the C:\ drive and remove ALL folders named jv16 PowerTools 2010.


3. Check to make sure that Sys6925.Config Collection.sys is NOT present at this time.


4. Open Windows Explorer and navigate to AppData\Roaming folder so that you can observe when Sys6925.Config Collection.sys is created.


5. Perform a fresh install of jv16 PowerTools 2010 using the same installer settings as DasFox (current user icon only, no translations, no desktop icon)


6. When the install Wizard reaches the Finish window, you will see that Sys6925.Config Collection.sys is not yet present. As soon as you click on Finish and the Quick Tutorial window opens, Sys6925.Config Collection.sys appears.


If you install a new version of jv16 over the top of an older version, the file is not created....probably because the Quick Tutorial window is not generated.

If you uninstall jv16 and save settings or something else and then re-install jv16, the file is not created....proabably because the Quick Tutorial windows is not generated.


The question is: Is jv16 generating the file or is something like Net Framework or XML generating the file when the Quick Tutorial window is created? I dunno. But DasFox is totally correct that the installation of jv16 causes this file to be created on both Windows 7 x86 and x64 systems.

siliconman01 wrote

The question is: Is jv16 generating the file or is something like Net Framework or XML generating the file when the Quick Tutorial window is created?

I don't think so, because jv16 PowerTools doesn't use the Net framework nor any XML generated GUI.

*** Voided by the poster *** 03

DasFox wrote

Ok video now in Safe Mode: (Watch full screen to see it cleaner.)


http://www.mediafire.com/?g1re7d46wnsexlz

Thank you very much for doing this! I asked you to do it in Safe Mode to ensure there is a minimal number of code running in the background.


I suspect the matter has something to do with the installer of jv16 PowerTools. The installer is created using a third party product called Setup Factory.


We could probably get some idea what is going on, if you could run jv16 PowerTools without the installer. That is, I could send you a zip file with all the files included in the installer, you could execute jv16pt.exe and that would work exactly as you had just installed it to your system. The only exception is that this time you wouldn't have actually run the installer. If the file doesn't show up this time, then it must be the installer that creates the file before it executes jv16 PowerTools after the installation is complete.


Would you be interested in trying this?

*** Voided by the poster *** 04

tullik wrote
I guess jv16 has to ask the supplier of the tutorial if they did this.

The tutorial is made in-house, it's just a regular window with some graphics and text in it. This is getting very strange.

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.
Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

*** Voided by the poster *** 05

*** Voided by the poster *** 06

tullik wrote

The content of all three of the subject files looks like this:


  • 1701=40463

I daresay this fact should narrow your search for a cause a bit. I hope ...

That's interesting. Let me see if I can find something.

*** Voided by the poster *** 07

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

*** Voided by the poster *** 08

*** Voided by the poster *** 09

DasFox wrote

Do you still need me to, or did tullik accomplish this already?

No need, Tullik did this already. But thanks anyway!

Ah, I got it now: These files are relating to the trial system of the PowerTools. In other words, there is no bug, everything works just as designed.


It was a long while back since I have last worked with the trial system so I didn't remember this at first.

*** Voided by the poster *** 10