Hanzie wrote
Now and then I get an Access Violation.

Powertools 2010 is the only programm giving problems on my pc

I hope they will troubleshoot this bug soon.

I only start Powertools 2010, use the regcleaner and click fix ... nothing more nothing less.

Bugfree sw does not exist (yet)!

Please Create a (.zip) Debug log and sent it to http://www.macecraft.com/bugtracker/


How to Create a Debug log of a specific problem, please follow these simple steps:

1. Start PowerTools

2. Press down keyboard keys Ctrl and Shift, release.

3. A menu called "Debug" is now visible in the main menu of the main window, select "Enable Debug Mode" under it.

4. Close PowerTools.

5. Start PowerTools.

6. Perform any action you wish to be saved to the Debug Log. For example, if you are experiencing a problem of the Registry Cleaner not fixing all found errors, run the Registry Cleaner and use the Fix button untill you see the problem again.

7. Close PowerTools. The Debug Log files are saved to your desktop and are called "jv16PT_debuglog.html"

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.

So I'm not the only one then. jv16 PowerTools 2010 seems to crash left and right here. On different computers even. So it's not a system-specific thing.

I hope you're able to bugfix it.

jv16.jpg

Could you tjukken and Hanzie please follow Leonardo's instructions and create a Debug Log of the problem? It's very difficult to fix the issue without it.

tjukken wrote
So I'm not the only one then. jv16 PowerTools 2010 seems to crash left and right here. On different computers even. So it's not a system-specific thing.

I hope you're able to bugfix it.

jv16.jpg

Good morning,

Got the same problem here...

mallet wrote
tjukken wroteSo I'm not the only one then. jv16 PowerTools 2010 seems to crash left and right here. On different computers even. So it's not a system-specific thing.

I hope you're able to bugfix it.

jv16.jpg

Good morning,

Got the same problem here...

For fixing this issues: Please sent the Debug log to Bugtracker.

See higher up in this forum/track for "How to make a Debug Log"

Leonardo wrote

For fixing this issues: Please sent the Debug log to Bugtracker.

See higher up in this forum/track for "How to make a Debug Log"

Do you also want to include instructions for zipping and sending in BugReport.txt from C:\Program Files\jv16 PowerTools 2010 along with the DebugLog.html submittal ?

siliconman01 wrote
Leonardo wrote

For fixing this issues: Please sent the Debug log to Bugtracker.

See higher up in this forum/track for "How to make a Debug Log"

Do you also want to include instructions for zipping and sending in BugReport.txt from C:\Program Files\jv16 PowerTools 2010 along with the DebugLog.html submittal ?

Siliconman01, Yes I certainly would.


Everything what makes the debug process easier and faster.

Perhaps the developer could add "How to make and sent a Debug log + Bug report" as the first threat in this jv16 Power Tools 2010 Macecraft Software Products forum . As is done in the 'Beta testing' threat in forum topic 'Development'.


I get the feeling that for several of the early users of the new jv16PT-2010-2.0.0.961 the 'threshold' to Bugtracker is high for sending Debug log.html + indeed Bugreport.txt. People tend to rely on others to send in the same or similar Debug logs.

jv16 wrote
Could you tjukken and Hanzie please follow Leonardo's instructions and create a Debug Log of the problem? It's very difficult to fix the issue without it.

OK, I took the chance, and have now uploaded the debug log after jv16 crashed. I'll see if I can replicate the other bug on my other machine.

Hanzie wrote
Now and then I get an Access Violation.

Add another PT 2010 user to the access violation/jv16pt.exe "An error occurred in the application" list.

This started right after I uninstalled jv16 Powertools 2009 and installed jv16 Powertools 2010 v2.0.0.961.

At first I thought it might be a conflict with my Avira Antivirus, so I uninstalled v 2.0.0.961, added it to my Avira's guard exception list, and reinstalled v 2.0.0.961. The problem continued. I get the error window upon starting, and whenever I select most of the features.


It looks like it's back to the 2009 version until the bug is resolved.

Registrology wrote
Hanzie wroteNow and then I get an Access Violation.

Add another PT 2010 user to the access violation/jv16pt.exe "An error occurred in the application" list.

This started right after I uninstalled jv16 Powertools 2009 and installed jv16 Powertools 2010 v2.0.0.961.

At first I thought it might be a conflict with my Avira Antivirus, so I uninstalled v 2.0.0.961, added it to my Avira's guard exception list, and reinstalled v 2.0.0.961. The problem continued. I get the error window upon starting, and whenever I select most of the features.


It looks like it's back to the 2009 version until the bug is resolved.

But, if nobody sends the Debug log.html and Bugreport.txt to BugTracker (and rely on others doing so), it can take quite a while to fix these annoying issues!

Seriously, if Macecraft wants the bug info, they shouldn't make people jump through hoops to give it to to them.


They obviously are able to generate the bug info when debug mode is on. So, why can't Powertools simply check a folder for bug reports, and upload the data to them? Before sending, a popup could ask the user the questions he now has to fill out in the bugtracker. Then a send button. This isn't rocket science.

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.
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.

tjukken wrote
Seriously, if Macecraft wants the bug info, they shouldn't make people jump through hoops to give it to to them.


They obviously are able to generate the bug info when debug mode is on. So, why can't Powertools simply check a folder for bug reports, and upload the data to them? Before sending, a popup could ask the user the questions he now has to fill out in the bugtracker. Then a send button. This isn't rocket science.

With such system we might not get any contact details for the user that is reporting the issue in the case we would need to contact the user for more information. Also, building such system would take time and money, both of which would be away from the development of the actual product itself.


And to be perfectly honest with you, if an user doesn't want to take the time and effort to fill out the Bug Tracker's form and use it to upload two files, the user is most likely not willing to take any time in helping us to solve the issue to begin with. Just sending over the debug data doesn't always help, sometimes we might need to ask the user to try something else.

jv16 wrote
tjukken wroteSeriously, if Macecraft wants the bug info, they shouldn't make people jump through hoops to give it to to them.


They obviously are able to generate the bug info when debug mode is on. So, why can't Powertools simply check a folder for bug reports, and upload the data to them? Before sending, a popup could ask the user the questions he now has to fill out in the bugtracker. Then a send button. This isn't rocket science.

With such system we might not get any contact details for the user that is reporting the issue in the case we would need to contact the user for more information. Also, building such system would take time and money, both of which would be away from the development of the actual product itself.


And to be perfectly honest with you, if an user doesn't want to take the time and effort to fill out the Bug Tracker's form and use it to upload two files, the user is most likely not willing to take any time in helping us to solve the issue to begin with. Just sending over the debug data doesn't always help, sometimes we might need to ask the user to try something else.

The popup box would have an input field for contact details. Sure, it does take time and money, but wouldn't it be helpful in squashing bugs, by making it easier for users to give you the info? The time you use for bugfixing right now, could become much less with such a system, as you suddenly would have lots more info to go on.


I do use the bugtracker myself, so it's not that I need this system. I will use it whenever I encounter a bug. But I really think more users would take the time to help, if you made it easier, and a more visible process, for them. People are inherently lazy, so using a bugtracker may seem like too much work, even if it's not.