• Beta testing

  • jv16 PowerTools 2010 Beta6 released! (Latest build: 938)

jv16 wrote
Leonardo wroteRunning XP-Prof SP3 with jv16PT-beta6-v927:


1. Resizing of the PT16 windows is still not remembered, this was already the case in beta2, beta3 and beta4:

-- Resizing the window right side border line is always lost (the right side border line seems to return to a fixed default position)

Resizing of the bottom border line is not remembered in a few cases.

Can anyone else reproduce this issue?

ADDED COMMENT based on aditional tests:

Resizing the window right side border line is always lost if I enlarge beyond ~75% of the full screen width of my 15" laptop screen.

In that case the right side border line is not remembered and returns to a fixed default position at ~75% of the screen width.

If the resizing of the window right side border line is limited to LESS than ~75% of the full screen width, the resizing is remembered!!

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.

Leonardo wrote

ADDED COMMENT based on aditional tests:

Resizing the window right side border line is always lost if I enlarge beyond ~75% of the full screen width of my 15" laptop screen.

In that case the right side border line is not remembered and returns to a fixed default position at ~75% of the screen width.

If the resizing of the window right side border line is limited to LESS than ~75% of the full screen width, the resizing is remembered!!

What screen resolution are you using?

jv16 wrote
Leonardo wrote

ADDED COMMENT based on aditional tests:

Resizing the window right side border line is always lost if I enlarge beyond ~75% of the full screen width of my 15" laptop screen.

In that case the right side border line is not remembered and returns to a fixed default position at ~75% of the screen width.

If the resizing of the window right side border line is limited to LESS than ~75% of the full screen width, the resizing is remembered!!

What screen resolution are you using?

Screen reolutionis set at maximum(=default) is 1400x1050, with an ATI mobility Radeon X1400 graphic card


ADDED COMMENT:

See the attached .zip file for a small test on resizing the beta6 Main window.

NOTHING of the main window resizing is 'remembered' after stopping/starting of jv16PT-beta6. In jv16PT-beta4 the resizing of the main window IS REMEMBERED.

jv16 wrote
Leonardo wroteRunning XP-Prof SP3 with jv16PT-beta6-v927:


1. Resizing of the PT16 windows is still not remembered, this was already the case in beta2, beta3 and beta4:

-- Resizing the window right side border line is always lost (the right side border line seems to return to a fixed default position)

Resizing of the bottom border line is not remembered in a few cases.

Can anyone else reproduce this issue?

XP-Home / SP3

Well indeed, the main window and the Settings window are not remembered.

Meanwhile the main window keeps the resizing for the same session, the Settings window even does not when closing and reopening in the same session.

As far I could see all other windows are fine.

Jean-Paul

Leonardo wrote

ADDED COMMENT based on aditional tests:

Resizing the window right side border line is always lost if I enlarge beyond ~75% of the full screen width of my 15" laptop screen.

In that case the right side border line is not remembered and returns to a fixed default position at ~75% of the screen width.

If the resizing of the window right side border line is limited to LESS than ~75% of the full screen width, the resizing is remembered!!

This issue should now be fixed, thank you for reporting! (And thanks for your patience).

jv16 wrote
Leonardo wrote

ADDED COMMENT based on aditional tests:

Resizing the window right side border line is always lost if I enlarge beyond ~75% of the full screen width of my 15" laptop screen.

In that case the right side border line is not remembered and returns to a fixed default position at ~75% of the screen width.

If the resizing of the window right side border line is limited to LESS than ~75% of the full screen width, the resizing is remembered!!

This issue should now be fixed, thank you for reporting! (And thanks for your patience).

Thank you. If you want it tested before the next release, let me know.

Build 931 released:

http://www.macecraft.com/downloads/betas/jv16PT2010_Beta6_b931.exe


Here is the Change Log:

Issues Fixed (since the original Beta6 release)




Known issue fixed: Anti-Malware feature is not yet ready for testing.


Note: If you want to test the Anti-Malware feature and make sure it can detect something, you can use the test file from http://www.eicar.org/anti_virus_test_file.htm




Issues Reported (numbers continue from previous version)


(none)



Issues Reported (new numbers)


1. Unit Test feature reports errors relating to "TestRNG"


2. Unit Test feature reports errors relating to "TestTBackupManager"


3. File Recovery can show an errir message: "The following information must be provided in order to start: At least one search argument, you can use Files to find, Search by size and/or Search by date tabs." - there is no Search by date tab.


4. System Cleaner tool's window doesn't have a tool caption, nor does the tool exist in English.lng at all


5. The size and position of some or all tool windows are not correctly remembered.



Issues Not Reported AFAIK


1. If a new version of the program is available, and you start Help > Check for updates right after starting the program, you might see a message "You are currently using version "{1}". A newer version "{2}" is available. Would you like to get more information about the new version?". If you click Yes, the already opened Check for Updates windows will close, start again and check again for a new version. The second time the popup does not occur.


2. The Check for Updates window lacks its icon.


3. File Tool's File Analyzer feature doesn't look right, all the text captions are wrong and do not originate from the English.lng



Improvements Done


1. Improved the Check for Updates window content handling.


2. It's now possible to send messages over the Internet to the Main Window of PowerTools, without the need of user clicking to Help > Check for Updates.


3. Increased the size of the Unit Testing Tool's window.


4. Clicking Abort now closes most of the tool windows - there is no need to show an empty list of results to the user if the user has clicked Abort.

Not a word about the problems with Registry Copmactor in Windows 7 x64 reported by myself and others (e.g. Siliconman) :


Are those problems fixed in this new beta6 build? I guess they aren't because I can't read anything about it...

Running build 931 on Windows 7 x64 Home Premium.


Setup ran very fast with no problems.

Performing Initial Setup completed in a very fast 83 seconds.

Registry Scan at default settings completed in 39 seconds.


Just came across one thing that doesn't seem right but it could be me misreading it. After running Registry Cleaner in aggresive mode there are a number of SySWOW64 entries that if opened in regedit don't seem to be the same as what PT results is showing.


For instance in PT results I get:-



@="C:\\Windows\\SysWOW64\\wpcumi.dll"


If I right click this entry and open in regedit I see this:-



@="C:\\Windows\\System32\\wpcumi.dll"

"ThreadingModel"="Apartment"


Is this ok and I'm misunderstanding what I'm seeing or is something incorrect?

DooGie wrote

Is this ok and I'm misunderstanding what I'm seeing or is something incorrect?

This is OK, it's again to do with the fact that PowerTools is a 32 bit application and RegEdit is a 64 bit application. They have a bit different view of the computer, including the registry and the file system.


This is the reason why it took so long for us to come up with a fully 64 bit compatible version of PowerTools - it's rather tricky to do 100% correctly.

After testing this newest build, I can assure the earlier reported issues with Registry Compactor in Windows 7 x64 persist.

I saw nothing at all during reboot concerning the compacting process.

-------------

Edit:

file Compactoutput.dat does not exist

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.

redseujac wrote
After testing this newest build, I can assure the earlier reported issues with Registry Compactor in Windows 7 x64 persist.

I saw nothing at all during reboot concerning the compacting process.

This issue hasn't been addressed yet, I'm afraid.

I just ran File Cleaner at the default setting. It scanned then popped up this message.


jv16 PowerTools AssertEx Log

11.05.2010 16

- AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry"


The list of found entries appeared to be ok however. I closed PT and then restarted it and ran File Cleaner again but this time didn't get the message.

After a reboot of the PC I again ran File Cleaner and the message appeared once more.

PT 2010. 931

Running a Unit Test I had a crash in RegistryDataAnalyzer - at about 75 % of the whole Test.

So here comes the Debug-Logs.

Jean-Paul

Windows XP Home SP3


This version (931) does stop working (does not crash the computer) when I clean the register. The last version (927) did work great. When I create a .dat file nothing is added to the file when the program stops.

Windows 7 x86 Professional, Build 931


The Registry Cleaner crashes promptly.

jouni,


Does the Debug>Unit Test actually run to completion error free on your inhouse Windows 7 x64 computer or Windows 7 x86 computer? Is this a futile exercise for us beta testers to attempt to run the Unit Test at this point in Beta testing?

Running XP-Prof SP3 with jv16PT-2010-beta6-b931:


1. jv16PT window resizing problems are gone for the major part (but not fully). I can live with it as it is now.

2. Trying to run Registry Cleaning 5 times ended up in 1 actual run, 1 access violation and 3 times the program frooze.


Shown message from windows error reporting:

AppName: jv16pt.exe AppVer: 2.0.0.931 ModName: kernel32.dll

ModVer: 5.1.2600.5781 Offset: 00012afb


See the attached .zip file for the bug reports on the freeze situation!

Registry Cleaner promptly freezes for me (Windows7-32bit).

PT931 Registry Cleaner promptly freezes for me

V.2.0.0.931 on an x86 Windows 7 notebook


My initial setup produced a SysCache.dat containing only the string RGCF , or (hex=5247 4346 0100 0000 0000 0000).


Is that a matter of concern?

tullik wrote
V.2.0.0.931 on an x86 Windows 7 notebook


My initial setup produced a SysCache.dat containing only the string RGCF , or (hex=5247 4346 0100 0000 0000 0000).


Is that a matter of concern?

Confirmed for Win-XP-Pro-SP3 and V.2.0.0.931

siliconman01 wrote
jouni,


Does the Debug>Unit Test actually run to completion error free on your inhouse Windows 7 x64 computer or Windows 7 x86 computer? Is this a futile exercise for us beta testers to attempt to run the Unit Test at this point in Beta testing?

The Unit Testing Tool runs without any errors in my 64 bit Windows 7.

Dermot7 wrote
Registry Cleaner promptly freezes for me (Windows7-32bit).

thmck wrote
PT931 Registry Cleaner promptly freezes for me


None of these Debug Logs show you actually starting the Registry Cleaner, could you please send a Debug Log that does? Please follow the instructions from the first post under "How to create a Debug Log" > "If the problem causes PowerTools to crash:".

tullik wrote
V.2.0.0.931 on an x86 Windows 7 notebook


My initial setup produced a SysCache.dat containing only the string RGCF , or (hex=5247 4346 0100 0000 0000 0000).


Is that a matter of concern?

Confirmed. Seems like a bug in the Initial Setup, I'll see what I can do.


In the mean time, I'll be adding a new test to the Unit Testing Tool called Self Test that checks whether all the files in PowerTools' installation directory are correct and in order. Such feature would have allowed me to detect this problem before the release of this beta build.

jv16 wrote
Dermot7 wroteRegistry Cleaner promptly freezes for me (Windows7-32bit).

thmck wrote
PT931 Registry Cleaner promptly freezes for me


None of these Debug Logs show you actually starting the Registry Cleaner, could you please send a Debug Log that does? Please follow the instructions from the first post under "How to create a Debug Log" > "If the problem causes PowerTools to crash:".

Do the Debug and BugReport logs I posted for Windows 7 x86 Professional registry cleaner's crash provide the necessary info?

siliconman01 wrote

Do the Debug and BugReport logs I posted for Windows 7 x86 Professional registry cleaner's crash provide the necessary info?

They do show the Registry Cleaner crashed, but more bug reports from other users would help me to solve the problem faster.

tullik wrote
V.2.0.0.931 on an x86 Windows 7 notebook


My initial setup produced a SysCache.dat containing only the string RGCF , or (hex=5247 4346 0100 0000 0000 0000).


Is that a matter of concern?

With that SysCache.dat, Registry Cleaner freezes immediately.

*No scan freeze.PNGBad SysCache.zip

Using the SysCache.dat generated by v 2.0.0.927, the tool ends normally.

tullik wrote
tullik wroteV.2.0.0.931 on an x86 Windows 7 notebook


My initial setup produced a SysCache.dat containing only the string RGCF , or (hex=5247 4346 0100 0000 0000 0000).


Is that a matter of concern?

With that SysCache.dat, Registry Cleaner freezes immediately.

*No scan freeze.PNGBad SysCache.zip

Using the SysCache.dat generated by v 2.0.0.927, the tool ends normally.

That's what I thought. Although, the tool does work perfectly with my test environments, even with the corrupted SysCache.


Could you try one more thing? Run the Registry Cleaner using the Reference Mode. In that mode the SysCache is not used. Does that work?

jv16 wrote
... That's what I thought. Although, the tool does work perfectly with my test environments, even with the corrupted SysCache.


Could you try one more thing? Run the Registry Cleaner using the Reference Mode. In that mode the SysCache is not used. Does that work?

No.

*Bad SysCache w refmode.zip

DooGie wrote
I just ran File Cleaner at the default setting. It scanned then popped up this message.


jv16 PowerTools AssertEx Log

11.05.2010 16

- AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry"


The list of found entries appeared to be ok however. I closed PT and then restarted it and ran File Cleaner again but this time didn't get the message.

After a reboot of the PC I again ran File Cleaner and the message appeared once more.

I added some more debug code. Could you try this again with the next released build and let me know of the error message then?

An updated build released:

http://www.macecraft.com/downloads/betas/jv16PT2010_Beta6_b932.exe


This build fixes the problem of the SysCache.dat not being correctly created, and thus it should also fix the Registry Cleaner not running properly. The latter fix is not confirmed, as the problem didn't occur in any of my test environments.


Here is the full Change Log:

Issues Fixed (since the original Beta6 release)




Known issue fixed: Anti-Malware feature is not yet ready for testing.


Note: If you want to test the Anti-Malware feature and make sure it can detect something, you can use the test file from http://www.eicar.org/anti_virus_test_file.htm




Issues Reported (numbers continue from previous version)


(none)



Issues Reported (new numbers)


1. Unit Test feature reports errors relating to "TestRNG"


2. Unit Test feature reports errors relating to "TestTBackupManager"


3. File Recovery can show an errir message: "The following information must be provided in order to start: At least one search argument, you can use Files to find, Search by size and/or Search by date tabs." - there is no Search by date tab.


4. System Cleaner tool's window doesn't have a tool caption, nor does the tool exist in English.lng at all


5. The size and position of some or all tool windows are not correctly remembered.


6. Initial Setup creates an empty SysCache.dat file


7. Registry Cleaner does not run (probably related to issue number 6).



Issues Not Reported AFAIK


1. If a new version of the program is available, and you start Help > Check for updates right after starting the program, you might see a message "You are currently using version "{1}". A newer version "{2}" is available. Would you like to get more information about the new version?". If you click Yes, the already opened Check for Updates windows will close, start again and check again for a new version. The second time the popup does not occur.


2. The Check for Updates window lacks its icon.


3. File Tool's File Analyzer feature doesn't look right, all the text captions are wrong and do not originate from the English.lng




Improvements Done


1. Improved the Check for Updates window content handling.


2. It's now possible to send messages over the Internet to the Main Window of PowerTools, without the need of user clicking to Help > Check for Updates.


3. Increased the size of the Unit Testing Tool's window.


4. Clicking Abort now closes most of the tool windows - there is no need to show an empty list of results to the user if the user has clicked Abort.


5. Improved the detection of incorrect / corrupted translation file.


6. The program now saves a separate Debug Log of the first run, in order to catch any possible bugs that occur during the Initial Setup.


7. Added debug code in order to better track any "AssertEx Failed!" error messages.


8. Added more debug to better detect problems with FileCache and SysCache creation and loading.


9. Added a SelfTest feature to the Unit Testing Tool, it will detect any missing or corrupted files from PowerTools' installation directory.

Build 931. Unit Testing Tool runs with errors on Win7 64bit. debug log attached.


Dick

jv16 wrote
An updated build released:

http://www.macecraft.com/downloads/betas/jv16PT2010_Beta6_b932.exe


This build fixes the problem of the SysCache.dat not being correctly created, and thus it should also fix the Registry Cleaner not running properly.

The latter fix is not confirmed, as the problem didn't occur in any of my test environments.

In XP-Pro-SP3 with beta6-v932 Registry Cleaner is working again as expected!

rcprins wrote
Build 931. Unit Testing Tool runs with errors on Win7 64bit. debug log attached.


Dick

I'm afraid the Debug Log does not show that you have even run the Unit Testing Tool. Please see the first post of this thread for instructions how to create a Debug Log.

jv16 wrote
DooGie wroteI just ran File Cleaner at the default setting. It scanned then popped up this message.


jv16 PowerTools AssertEx Log

11.05.2010 16

- AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry"


The list of found entries appeared to be ok however. I closed PT and then restarted it and ran File Cleaner again but this time didn't get the message.

After a reboot of the PC I again ran File Cleaner and the message appeared once more.

I added some more debug code. Could you try this again with the next released build and let me know of the error message then?


Right Jouni, running File Cleaner on build 932 Windows 7 x64 I get this error message.


jv16 PowerTools AssertEx Log

12.05.2010 15

- AssertEx1 (RS) FAILED! Desc="TDebugLog.AddLogEntry, Entry="Start: Procedure TFileViewForm.OnGetInfo(Sender: TObject; FileInfo : TFileInfo; PossibleIndex : Integer);""

Leonardo wrote

In XP-Pro-SP3 with beta6-v932 Registry Cleaner is working again as expected!

That is good news! Does the Unit Testing Tool also run without any errors?

jv16 wrote
Leonardo wrote

In XP-Pro-SP3 with beta6-v932 Registry Cleaner is working again as expected!

That is good news! Does the Unit Testing Tool also run without any errors?

Within a few hours I will run the Unit test (with erased debug files at starting point) and will let you know.