Windows Vista 64 bit and intel quadcore

jürgen

I have just succesfully installed jv16 Powertools (Version 1.7.0.416) in a fresh windows vista 64bit Business installation and this worked without problems. But the registry cleaner took a very long time and reported finally more then 30000 errors to fix. I didn´t apply this because I was wondering about this huge value.

Is it probably a bug in this 32bit version and it does not work under 64bit vista? Is there a new version of jv16 for 64bit available?

Regards

Jürgen

[deleted]

In the system requirements it is said that software works on any computer running Windows 98, 98 SE, ME, NT, 2000, XP or Vista operating system (only the normal 32b versions, not the x64 ones). So the software is not compatible with 64b version.

jv16

A 64 bit compatible version is already in testing, it should be released shortly, hopefully in next week.

blackdex

Nice to hear :).

I Havent been using PT alot lately because of no 64Bit version.

And being on 64Bit OS Only the last view months.

ostrichs

any news on 64 bit?

jv16

Latest released version of PT works on some 64 bit Vista systems but not on all. We are hoping to have a full compatibility for the next released version due to be out within two weeks.

sangwooksohn

>>jv16

I've downloaded and tested the latest version (build 422) on my WinVista x64 system, but RegCleaner still didn't finishi scanning.

Follwing is my quick system info:

2x ADM Opteron 280 w/ 4x 1GB ECC DDR DIMM on nForce4 Professional 2200+2050 chipset mobo.

jv16

How long did you run it before you hit the Abort button? Could you try to run the Registry Cleaner but with only the first scan module (File Reference Scan) checked?

sangwooksohn

>>jv16,

It took approximately 5 minutes until I decided to abort the process. (RegCleaner was ran in "Aggressive" mode)

And as for running RegCleaner with only "File Reference Scan" checked, I didn't encounter any problem. RegCleaner did finish running the scanning.

---edit---

I did test RegCleaner on my system with each one of scan modules checked at a time, and found that "Left-over software data scan" is the one that just wouldn't finish.

jv16

sangwooksohn wrote
>>jv16,

It took approximately 5 minutes until I decided to abort the process. (RegCleaner was ran in "Aggressive" mode)

And as for running RegCleaner with only "File Reference Scan" checked, I didn't encounter any problem. RegCleaner did finish running the scanning.

---edit---

I did test RegCleaner on my system with each one of scan modules checked at a time, and found that "Left-over software data scan" is the one that just wouldn't finish.

Thank you very much! This is just the information I needed. Before, it was the File Reference Scan that cause the problems, now I can see that the problem in that is now fixed. Now, let me take a look at the Left-over Software Data scan...

hamed206

jv16 wrote
sangwooksohn wrote>>jv16,

It took approximately 5 minutes until I decided to abort the process. (RegCleaner was ran in "Aggressive" mode)

And as for running RegCleaner with only "File Reference Scan" checked, I didn't encounter any problem. RegCleaner did finish running the scanning.

---edit---

I did test RegCleaner on my system with each one of scan modules checked at a time, and found that "Left-over software data scan" is the one that just wouldn't finish.

Thank you very much! This is just the information I needed. Before, it was the File Reference Scan that cause the problems, now I can see that the problem in that is now fixed. Now, let me take a look at the Left-over Software Data scan...

I have Vista x64 Ultimate,yes the problem with the file reference scan has gone...and I have tested all scan modules but found the problem with two modules!,obsolete software scan & left-over software data scan.

The regcleaner with these two modules never stop!!!!

Thanks you.

shawn-m

I can confirm the above findings on my AMD system; v.422 Registry Cleaner successfully completes scanning when both "Obsolete software scan" and "Left-over software data scan" modules are not active.

If helpful, here are some system specs (not sure if I've included everything necessary):

- Windows Vista-64 Ultimate

- Asus LiN64-SLI WS mother board

- AMD Athlon 64 FX-74 (3 GHz, quad-core)

- OCZ DDR RAM (6 GB)

clyde

I found that I only had to disable Obsolete Software Scan in order for the registry scan to finish. It only made it slightly faster if I also disabled the Left-over software scan.

I'm running Windows Vista 64 Ultimate on an Intel Q6600 quad core CPU with a Gigabyte GA-P35-DS3 motherboard.

hamed206

I have Vista Ultimate 64 bit and pentium 4 3.2GHZ,3GB ram...I still can confirm that the problem is with the two modules: obsolete software scan & left-over software data scan.

runfox

clyde wrote
I found that I only had to disable Obsolete Software Scan in order for the registry scan to finish. It only made it slightly faster if I also disabled the Left-over software scan.

I'm running Windows Vista 64 Ultimate on an Intel Q6600 quad core CPU with a Gigabyte GA-P35-DS3 motherboard.

same for me

jv16

This issue should be finally fixed in the next released version which is to be released within one week. The release is most likely the last update for PT 2007 so I really hope to finally nail this bug.

majordisaster

jv16 wrote
This issue should be finally fixed in the next released version which is to be released within one week. The release is most likely the last update for PT 2007 so I really hope to finally nail this bug.

Is this issue fix for Vista x64 users? thanks