Private test build 569 released (and now finally 580)

redseujac

Another question for the developer:

(sorry I post this question here, but I would not create a new thread elsewhere in the PowerTools 2009 section)

*.txt-files, *.log-files, *.dat-files, etc. are all analyzed as XML-type files

*.pdf-files, *.xbin-files are analyzed as PAS-files

*.lng-files are analyzed as CPP-files

1) Is the analysis result for those files correct?

2) What is the meaning of the abbreviations PAS and CPP?

3) Where can the user find the meaning of all such abbreviations indicated by the File Analyzer file type results?

tullik

Those 1, 2, 3, 4 pop-ups reported by drob for the File Tool are also happening with other tools.

For example, the Add button in the Directory Finder gets them. :(

*** After you "OK" 1 and 2, "Browse for folders" appears.

*** After you select a folder and click "OK," 3 and 4 appear.

redseujac

Very annoying those pop-ups!

IMHO the developer should fix that issue anyway, especially because it was inexistent in build 552.

If he can't without undoing the/some program improvements for 64-bit, then I insist once again to create 2 separate programs: one for 32-bit and another for 64-bit, even if that gives mork work and testing.

I find it can't be true that the users with 32-bit systems should bear the bad consequences / bugs /issues of "improvements" for the 64-bit OS, while before and/or without those "improvements" the program for 32-bit had not those problems / bugs /issues.

myers6mm

I mentioned the same thing back in Feb about 2 separate installers one for 32Bit and one for 64Bit. I never did see any response to it?

jv16

redseujac wrote

That issue did NOT exist in build 552!

So, is it possible that working on 64-bit improvement has "messed up" well working 32-bit (again)?

That issue can and should be fixed (at least for 32-bit OS)...

Or is it an incompatibility PT/64-bit for that feature in 32-bit also? I mean: do the improvements made in PT for 64-bit OS always cause the reported issue in File Tools (also in 32-bit systems) and that issue cannot be fixed without undoing the 64-bit improvements/fixes?

The message boxes are simply debug code that will be removed before the final release.

jv16

myers6mm wrote
I mentioned the same thing back in Feb about 2 separate installers one for 32Bit and one for 64Bit. I never did see any response to it?

There is no need for two installers because there is no two versions of the program for 32/64 OS'es either. Nor would there be any point to do so, because there is very little difference in the program when it runs under 32 bit Windows and 64 bit.

redseujac

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

redseujac wrote
jv16 wrote...The message boxes are simply debug code that will be removed before the final release.

Well well, that's all?

I thought you wrote there was an incompatibility PT/64-bit? I must have dreamed... But NO, I didn't:

Yes, the fact that the directory browsing feature does not work under 64 bit Windows is the one last compatibility issue. The fact that the latest test build shows message boxes with numbers is a matter debug code.

jv16

redseujac wrote
Boofo wroteSo, the "Open With..." bug is gonna be put on the back burner again??? This is what frustrates me,that they will release a partially working program and consider that a job-well-done.

No, I think the programer should fix that issue (if has the time) before releasing the next update, because he will be out of office quite some time shortly.

Maybe it's not that difficult, because in previous versions those features worked as far as I remember (I mean for Win XP naturally).

The issue is now fixed, thank you for reporting and reminding!

boofo

Does that mean the "Search menu" is fixed also?

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.

boofo

Great! Are you gonna let us test it then to make sure it works on all the systems it was having problems on?

feck

Are these safe to delete?

siliconman01

feck,

You are not scanning in Aggressive mode, are you? If so, you should not be. Move the slider bar to the 2nd position down which is the default mode.

feck

Hi,

I've always sworn by the 3rd and 4th levels of aggression :. It's only since 577 that this extra batch of errors have been given.

siliconman01

Well, the 2nd and 3rd position are most likely safe to "Fix". The 4th position is a "you better have a good system backup ready just in case" level.

Why don't you "Fix" at level 2, reboot and see if all is okay. Then do level 3 and check again.

I'm not sure about the ones with wrong permissions. Can you export these keys and then attach them back here for a look/see?

redseujac

Well, as the program indicates it, in any case the 4th level is at the own risk of the user ("use only for testing purposes"). So you should know yourself if those entries are safe to delete.

When you take risks, and something goes wrong, then don't blame the program or the forum users :

Anyway you have always the backups you could restore if necessary. I suppose you always let the program create backups?

feck

Can you export these keys and then attach them back here for a look/see?

I was about to do that for you, but now I'm pretty sure I should leave it be, it's major settings for all my 32bit software.

The exported Wow6432Node directory is 26MB : .

26MB / 67,000 = 388 bytes, feasibly the average size of one exported key. In other words, I think every single key was reported.

siliconman01

Are you running with your user account that has full admin privileges? If not, please try that and see if it reports the same keys. It is very odd that it is detecting the wrong owner or incorrect permissions.

jv16

Boofo wrote
Great! Are you gonna let us test it then to make sure it works on all the systems it was having problems on?

Yes, of course. I would have released the next version for testing but a new version of the list component had a bug and I need to wait for my collegue to fix it. The next version should be released for testing later today.

« Previous Page Next Page »