TestBuild 542 test results for Vista x64

siliconman01

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.

siliconman01

The Flush Cache>Rebuild Cache issue is confirmed as fixed on x64 systems

http://www.macecraft.com/phpBB3/viewtopic.php?p=18400#p18400http://www.macecraft.com/phpBB3/viewtopic.php?p=18400#p18400

siliconman01

The Registry Finder is still broken on x64. It is missing x64 locations and incorrectly showing items in non-existent locations of a x64 addressed registry.

Here is what a Search for PowerChute.exe "found"

HKEY_LOCAL_MACHINE\software\apc\APC PowerChute Personal Edition\2.02.00\AppName : PowerChute.exe

HKEY_LOCAL_MACHINE\software\wow6432node\microsoft\windows\currentversion\installer\userdata\s-1-5-18\components\18cc01d08a2342a4da17b55e012ad803\6ED6842EE2CC0C84DA022C1C24AF6163 : C:\Program Files (x86)\APC\APC PowerChute Personal Edition\PowerChute.exe

HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion\installer\userdata\s-1-5-18\components\18cc01d08a2342a4da17b55e012ad803\6ED6842EE2CC0C84DA022C1C24AF6163 : C:\Program Files (x86)\APC\APC PowerChute Personal Edition\PowerChute.exe

As shown by the attached picture (named NoAPCkey), the first key (HKEY_LOCAL_MACHINE\software\apc\APC PowerChute Personal Edition\2.02.00\AppName : PowerChute.exe) does not exist under HKEY_LOCAL_MACHINE\software

The second key HKEY_LOCAL_MACHINE\software\wow6432node\microsoft\windows\currentversion\installer\userdata\s-1-5-18\components\18cc01d08a2342a4da17b55e012ad803\6ED6842EE2CC0C84DA022C1C24AF6163 : C:\Program Files (x86)\APC\APC PowerChute Personal Edition\PowerChute.exe does not exist as shown below.

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer

Class Name: <NO CLASS>

Last Write Time: 12/11/2008 - 3 AM

Value 0

Name: InstallerLocation

Type: REG_SZ

Data: C:\Windows\SysWOW64\

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\ResolveIOD

Class Name: <NO CLASS>

Last Write Time: 12/11/2008 - 3 AM

Value 0

Name: outlook.exe

Type: REG_DWORD

Data: 0

The third key HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion\installer\userdata\s-1-5-18\components\18cc01d08a2342a4da17b55e012ad803\6ED6842EE2CC0C84DA022C1C24AF6163 : C:\Program Files (x86)\APC\APC PowerChute Personal Edition\PowerChute.exe does appear to be correct.

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\18CC01D08A2342A4DA17B55E012AD803

Class Name: <NO CLASS>

Last Write Time: 2/1/2009 - 6 AM

Value 0

Name: 6ED6842EE2CC0C84DA022C1C24AF6163

Type: REG_SZ

Data: C:\Program Files (x86)\APC\APC PowerChute Personal Edition\PowerChute.exe

The finder did not find PowerChute.exe at the key below.

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC

Class Name: <NO CLASS>

Last Write Time: 2/1/2009 - 6 AM

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC\APC PowerChute Personal Edition

Class Name: <NO CLASS>

Last Write Time: 2/1/2009 - 6 AM

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC\APC PowerChute Personal Edition\2.02.00

Class Name: <NO CLASS>

Last Write Time: 2/1/2009 - 6 AM

Value 0

Name: <NO NAME>

Type: REG_SZ

Data:

Value 1

Name: AppName

Type: REG_SZ

Data: PowerChute.exe

Value 2

Name: InstallPath

Type: REG_SZ

Data: C:\Program Files (x86)\APC\APC PowerChute Personal Edition\

Value 3

Name: ResourceFile

Type: REG_SZ

Data: res.dll

Value 4

Name: Version

Type: REG_SZ

Data: 2.2

Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\APC\APC PowerChute Personal Edition\2.02.00\Dialog

Class Name: <NO CLASS>

Last Write Time: 2/1/2009 - 6 AM

Value 0

Name: ReplaceBatteryWebPage

Type: REG_SZ

Data: http://www.apc.com/tools/upgrade_selector/index.cfm?Localize=true

Value 1

Name: <NO NAME>

Type: REG_SZ

Data:

(remainder of this key's data edited out)

siliconman01

There is a bug in the Registry Cleaner structured list results display. If the major category heading is at the very bottom of the results window, it will not expand when clicking on the + sign. It will expand okay if moved up from the very bottom.

siliconman01

The Registry Cleaner is, for the first time, addressing the registry as a x64 registry....which is GREAT. However, the registry scanner is yielding erratic results from scan to scan. For example, at position 3 of the slider bar will yield 700 items on one scan and then 21 items on another scan. NOTE that I am not letting it do any cleaning/fixing at the moment. Also, items showing in slider bar position 3 may or may not show up in position 4 (aggressive). I am leaving my Advanced Engine Settings at the same settings during scans.

Update: It appears that Registry Cleaner is intermixing 32-bit and x64 access to the registry. On right clicking on various keys that are found, Regedit opens sometimes in x64 mode and other times as a 32-bit registry. Very strange results are occurring in the scan results and with inconsistent results from scan to scan.

siliconman01

The Registy Cleaner finds 650+ keys that it says have incorrect permissions or owner. This list is labeled "IncorrectPermissionsFound" in the attachments. They are EventLabels, BCD0000000, and abelhadigital.com items. I have attached the registry contents for EventLabels, and BCD0000000. In the case of abelhadigital.com, the attached picture shows that this item does not exist where the Registry Cleaner says there is an error. These errors are found in slider bar position 3 and 4 and sometimes in position 2.

I do know that if I let PT 2009 "fix" these supposed errors, it corrupts the registry and the system will not boot under any mode.

siliconman01

Here are the abelhadigital attachments.

siliconman01

The Registry Compactor is fixed and working correctly now for x64 systems.

Reference bug link below:

http://www.macecraft.com/phpBB3/viewtopic.php?p=17593#p17593

That's the extent of my testing with this test version. I am very much encouraged that PT 2009 is getting much closer to being fully x64 compatible. 8) When you need further testing with a new test version, please do not hesitate to post a download link.

drob

Another issue under Vista sp1 x64, registry cleaner seems to freeze t the final analysts stage, scan goes ok, then at the "preforming final analysts" it seems to freeze, the progress bar and the working "star" do not progress.

drob

On further testing it seems the "deep analysts" option is the one causing the problems, un checking it allows the registry cleaner to finish the scan. Juts to make sure its not the process doing its thing, i left the process alone for about 3 hours and still didn't get results.

siliconman01

The aggressive scan yields many, many, many false detections on x64 and that is probably what is causing the freeze, yes. Hopefully this will be fixed in the next test release.

diabolofrais

Hi everyone,

same issue on a 64 bit windows seven OS:

"Failed to gain full read and write access to the system registry! Please verify the security settings of your system. This program cannot perform any registry features (for example the Registry Cleaner) without full registry access!"

Let me know if any information I could provide would help.

drob

Found another issue,

In file tool, choosing- file-add files - doesn't o anything, directories does open the file browser.