jv16 PowerTools 2011 Beta4 released

leonardo

XP-SP3 with v2.0.0.993 (beta4):

An Access Violation occured at the closure of the Startup Manager window.

This does not happen every time, only occasionally!

tullik

Many of the bugs I'm tracking are fixed in v.2.0.0.993. Look here: http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4300&p=27175#p27175

These rather interesting bugs are still present:

Prior Beta issues still present in Beta 4.

In Startup Manager, Tag Editor places unwanted tags on lines not selected. Still happens in v.2.0.0.993. Awaiting developer response.

Startup Manager line tags do not show when you start the tool again. Still happens in v.2.0.0.993. Awaiting developer response.

Backup Tool list: you lose your column width changes when you sort a column. This also happens sometimes in the lists of some other tools. Still happens in v.2.0.0.992. May be fixed in Beta 4. Still happens in v.2.0.0.993 for columns resized by double clicking). Awaiting developer response.

When run from the Automation Tool, an aborted System Cleaner task gets an incorrect message. Still happens in v.2.0.0.993. Awaiting developer response.

Startup Manager: when disabling a task, the ...\MSConfig\startupreg\... key created is missing a necessary entry name and value. Still happens in v.2.0.0.993. Awaiting developer response.

Here are some new ones (the third and sixth items are related to the third and fifth items in the "still present" list above):

New issues noticed in Beta 4.

Initial Setup does not back up HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.

Initial Setup does not back up HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run.

Backup Tool does not remember resizing of columns done by double clicking. It does remember resizing done by dragging. Some other tool lists are also affected.

C&FMC "All done!" count can be wrong when removing empty directories.

Startup Manager "Open in RegEdit" does not work for HKLM Run items. It works for HKLM Wow6432Node Run and HKCU Run items.

Startup Manager: Enable for a selected disabled task gets an "Internal error ERM-1" pop-up. Only happens if Startup Manager did the disable. Does not happen if disable was done by msconfig before starting the Startup Manager.

leonardo

tullik wrote

New issues noticed in Beta 4.

Backup Tool does not remember resizing of columns done by double clicking. It does remember resizing done by dragging. Some other tool lists are also affected.

Confirmed for XP-SP3, with the additional remark that column resizing done thru double clicking does not always give the correct column width.

tullik wrote

New issues noticed in Beta 4.

Startup Manager: Enable for a selected disabled task gets an "Internal error ERM-1" pop-up. Only happens if Startup Manager did the disable.

Does not happen if disable was done by msconfig before starting the Startup Manager.

In XP-SP3 enable/disable thru Startup Manager works OK, without the pop up of the "Internal error ERM-1".

tullik

Just noticed this discrepancy:

Startup Manager: an "Old" tag is placed on all 22 lines of a list. However, "TagSystem.dat" only has 17 line tags after the operation. Awaiting developer response.

Details:

width=331 height=330 1=Bug 2=Delete this 3=msconfig yes 4=Old 5=Same as PT2010? 6=Save this 7=Tag entry test ... 8=Test data 9=updated? 06176cc43baa1e19ec0dadeacecf00b2483a567e=4 2614607434d496264e8fcaa3d19ff23c6a7410f7=4 2e968d0fffbcea3d5166907b7fa0c7461940985f=4 3cc354ce63a72d7eaac97342e7d1891fc37d1f6e=4 3e3a5a38260b72b4b5a5ede91f854dc40a0be733=4 3e7e5a623e2978a2f0fdf023c07877eabaae66a6=4 42e14d3eb022f3c1eb653ead42a2c3d02af13628=4 483d0cb639a3d907d96c8d2f10898933d63677ed=4 5ef8b2be0be4dce31318f04d8b91bad54752d566=4 66cd311b0ae47443dd9c2685119acc6a67dc4ce9=4 7e2b0966e46e68372fec6f68f5c931296739bd66=4 81428d4fa02ce7ed3d5ca82d42d473a2628d00ed=4 8ffade83bdd424236f9d3e06c8add86582df4b34=4 c6da4cae9f032b39a8618bfe4870417a2af7fd7d=4 ce1fd2d6d17d0a72c0258e511d1ebd9827e7ccc5=4 e94af4585f8a7d83b2495e17a7d71ebe207c0b38=4
f96ba5e593c66e6eaa0bd1ee426c9b4274e01d6a=4

jv16PT_debuglog.zip

01-06-2011_22-22-28.jpg

tullik

Could these be related?

In Startup Manager, Tag Editor places unwanted tags on lines not selected. Still happens in v.2.0.0.993. Awaiting developer response.

Startup Manager: an "Old" tag is placed on all 22 lines of a list. However, "TagSystem.dat" only has 17 line tags after the operation. Awaiting developer response.

jv16

tullik wrote
Version 2.0.0.993 with x64 Windows 7

Startup Manager "Open in RegEdit" does not work for HKLM Run items.

Can someone confirm? It works with me.

siliconman01

I put a Test string in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and then did a "Open in Regedit". Instead of opening to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, it opens to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run.

leonardo

jv16 wrote
tullik wroteVersion 2.0.0.993 with x64 Windows 7

Startup Manager "Open in RegEdit" does not work for HKLM Run items.

Can someone confirm? It works with me.

Seems to work OK in XP-SP3. But temporarily I have no access to my W7 x86 notebook!

XP_beta4_StartupMgr_Regedit HKLM.jpg

siliconman01

HKLM\........ "Open in Regedit" works fine on Win 7 x86.

jv16

tullik wrote

Enable no longer wipes out the entire HKLM Wow6432Node Run key. Now it gets an "Internal error ERM-1" pop-up.

This happens if you try to Disable an item previously enabled in the same Startup Manager session, right? This issue is now fixed.

tullik wrote

Startup Manager: the entire content of the HKCU Run key disappeared when I clicked Enable for a selected HKCU disabled task. Still happens in v.2.0.0.992. Fixed in v.2.0.0.993.

This Enable gets the same pop-up.

Also now fixed.

tullik wrote

In both cases, only the selected task is removed from the applicable RUN key. However, msconfig does not know what the Startup Manager did.

That is due to this bug:

Startup Manager: when disabling a task, the ...\MSConfig\startupreg\... key created is missing a necessary entry name and value. Still happens in v.2.0.0.993. Awaiting developer response.

Details are here: http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=4296&p=27126&hilit=startupreg#p27126

I didn't quite understand, what key or entry doesn't Startup Manager create when disabling a task?

tullik

jv16 wrote
tullik wroteVersion 2.0.0.993 with x64 Windows 7

Startup Manager "Open in RegEdit" does not work for HKLM Run items.

Can someone confirm? It works with me.

A specific example from my Startup Manager list:

"C:\Program Files (x86)\Lexmark Pro200-S500 Series\ezprint.exe" is loaded from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

"Open in RegEdit" for the line opens at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run (same as siliconman01's test; must be an x64 only bug).

Another symptom:

*** Successful opens highlight the entry name in the RegEdit window's right pane.

*** The unsuccessful ones not only open at the wrong Run key, but also "beep."

tullik

jv16 wrote
tullik wrote

Enable no longer wipes out the entire HKLM Wow6432Node Run key. Now it gets an "Internal error ERM-1" pop-up.

This happens if you try to Disable an item previously enabled in the same Startup Manager session, right? This issue is now fixed.

Right. A test just done shows that Startup Manager happily enables an item it disabled in a previous session.

However, msconfig is not aware that the item was disabled. It only knows that it is not there anymore.

jv16

tullik wrote
jv16 wroteImprovement: When the program is started for the first time it automatically creates a backup of a critical parts of the registry, these backups can be restored from the Tools menu of the Backup Tool. Starting with this build, a backup of all the \Run keys is also automatically created.

__SystemRecovery3__ backs up this:

But not this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

It should back up both.

Issue confirmed and fixed. Thank you for reporting!

tullik wrote

Edit: It should also back up HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run.

Agreed, this will be included to the next build.

tullik

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.

tullik

@ jv16

Will the next build be Beta 5 or Beta 4.1? :|

jv16

siliconman01 wrote
I am pleased to see the Startup Manager loads much, much quicker on both Win 7 x64 and x86. There is, however, a bug in the Startup Manager on 64-bit systems. The Startup Manager finds the RUN keys correctly. But if the started program is a pure 64-bit program loading from C:\Program Files, jv16 does not show that the program is running. See the pic enclosed.

Confirmed and fixed, thank you for reporting!

jv16

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

tullik wrote

If the item is missing, msconfig does not recognize that the item was disabled. It only knows it is not there. Therefore, the item can only be enabled using Startup Manager. That falls short of this Release Notes statement:

This issue is now fixed, thank you for reporting!

jv16

Leonardo wrote
XP-SP3 with jv16PT-2011-Beta4:

A search with 'File Finder' produced a small list of only 20 items.

During the build-up of this short list some intense flickering occured for less than a second.

After the build-up of the list was finished, the screen shows a 'flickering' once every 5 seconds, up till the closing of 'File Finder''. (after ~12 minutes!)

EDITED:

I ran a search with 'File Finder' to produce a large list of 904 entries.

After the build-up of this large list was finished, surprisingly the screen did not show 'flickering' once every 5 seconds, as it does for the small 20 item list.

I tested this a few times with the same results!

The same is true for 'Directory Finder'!

The issue is now fixed, thank you for reporting! This problem was caused by the timer that checks every 5 seconds that all items in the list really exist (e.g. the files listed in the File Tool's result list are valid). The check can now detect whether the contents of the list has been changed and if it hasn't, the check is skipped.

The reason why the flickering doesn't occur with lists of hundreds of items is simply because the checks are not performed due to performance reasons for lists that have more than 200 items.

jv16

Change Log so far:

Bug fix: Running the Start Menu Fixer many times in a row causes duplicate items to show up in the list of results.


Bug fix: "Never Show Again" does not work on empty folders in Clean and Fix.  It does not store these in SuperEasyFixIgnoreList.dat; thereby, they are always detected.
Bug fix: Using Enable and Disable many times in a row in Startup Manager produces "Internal error ERM-1"
Bug fix: Backups created during Initial Setup only backup the 32 bit view of the registry.
Bug fix: In Startup Manager, if a program is a pure 64-bit program loading from C:\Program Files, jv16 does not show that the program is running.
Bug fix: Items disabled with the Startup Manager do not always show up in Msconfig.
Bug fix: In File Tool and Directory Tool, after the build-up of the list was finished, the screen shows flickering once every 5 seconds.

Improvement: Improved the safety of Start Menu Fixer in regard of detecting empty folders.
Improvement: Backups created during the Initial Setup now also backup HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

« Previous Page Next Page »