Compatible with Windows 7

[zer0]

Today, I have noticed that XYplorer's website features a shiny "Compatible with Windows 7" logo from the Windows 7 logo program.

win7compatible.png

As XYplorer is currently not featured on Windows 7 Compatibility Centre, I would like to suggest for it to be added. To do so, could you please let me know the following:

- Has it been tested with a 64-bit version of the logo toolkit?
- If yes, what was the latest XYplorer version to be tested with it?
- Are XYplorer.exe and XYcopy.exe signed with an Authenticode certificate?

Thanks

[admin]

Cool.

- Yep, just did that. Result: PASSED.
- v9.11.0021
- No, this costs a lot of money. Looks like a rip off scheme to me.

[zer0]

- No, this costs a lot of money. Looks like a rip off scheme to me.

I'm intrigued as to how it passed as it's a technical requirement of the logo program to have all executable files (exe, dll, cpl, etc) signed with Authenticode.

[admin]

- No, this costs a lot of money. Looks like a rip off scheme to me.

I'm intrigued as to how it passed as it's a technical requirement of the logo program to have all executable files (exe, dll, cpl, etc) signed with Authenticode.

There was a warning about this, but it still passed ("passed with warning").

[zer0]

There was a warning about this, but it still passed ("passed with warning").

OK, "passed with warning" is still a successful result. Here is what to do next (if you have time):

5. After testing, submit for the Logo
After successful testing (PASS, PASS WITH WARNING) submit the passing results at http://winqual.microsoft.com by uploading the .xml result report. See the submission overview in the downloads section for more information.
6. Sign the Software Logo License Agreement
Once passing results have been submitted, sign the license agreement at https://winqual.microsoft.com. You can then download and begin to use the Logo artwork and will be eligible to receive all the available Logo benefits.

In the meantime, I'll get to work in suggesting XYplorer be added to Win 7 Compatibility Centre

[admin]

There was a warning about this, but it still passed ("passed with warning").

OK, "passed with warning" is still a successful result. Here is what to do next (if you have time):

5. After testing, submit for the Logo
After successful testing (PASS, PASS WITH WARNING) submit the passing results at http://winqual.microsoft.com by uploading the .xml result report. See the submission overview in the downloads section for more information.
6. Sign the Software Logo License Agreement
Once passing results have been submitted, sign the license agreement at https://winqual.microsoft.com. You can then download and begin to use the Logo artwork and will be eligible to receive all the available Logo benefits.

In the meantime, I'll get to work in suggesting XYplorer be added to Win 7 Compatibility Centre

, thanks!

I'll do the submitting with 9.20 (= soon).

[admin]

Long story, short version: Forget it.

I don't have the time to list all the idiocy you meet on the way to get this logo -- here's is some text by another one who gave up:
http://successfulsoftware.net/2009/10/2 ... o-program/

PS: At least I succeeded to be on the Win7 Compatibility list. No idea where this list is to be viewed, but MS emailed me that I'm on it...

[zer0]

...PS: At least I succeeded to be on the Win7 Compatibility list. No idea where this list is to be viewed, but MS emailed me that I'm on it...

I would assume that this is it: http://www.microsoft.com/windows/compat ... fault.aspx But XYplorer isn't on it at the time of writing this

[admin]

...PS: At least I succeeded to be on the Win7 Compatibility list. No idea where this list is to be viewed, but MS emailed me that I'm on it...

I would assume that this is it: http://www.microsoft.com/windows/compat ... fault.aspx But XYplorer isn't on it at the time of writing this

Correct. I tried it again.

[Jibz]

Another nice thing about code signing is that it can improve the startup time because anti-virus software will often assume signed executables are safe. For instance TC (which is signed) is instant on my system, while KIS always takes a look at XYplorer.exe before letting it run.

Of course it is a tradeoff between the benefits and the ~$170 a year the certificate costs .

[zer0]

...while KIS always takes a look at XYplorer.exe before letting it run...

You cannot add XYplorer.exe to a "whitelist" in KIS? I seem to recall it can be marked as a 'trusted application'

[Jibz]

...while KIS always takes a look at XYplorer.exe before letting it run...

You cannot add XYplorer.exe to a "whitelist" in KIS? I seem to recall it can be marked as a 'trusted application'

There are plenty of workarounds of course, they don't really solve the problem though.

The real problem is the next potential user who comes along looking for a file manager might not realize the cause and choose a different one because XY appears to be slow to start.

[admin]

...while KIS always takes a look at XYplorer.exe before letting it run...

You cannot add XYplorer.exe to a "whitelist" in KIS? I seem to recall it can be marked as a 'trusted application'

There are plenty of workarounds of course, they don't really solve the problem though.

The real problem is the next potential user who comes along looking for a file manager might not realize the cause and choose a different one because XY appears to be slow to start.

Good thought.

[zer0]

There are plenty of workarounds of course, they don't really solve the problem though.

The real problem is the next potential user who comes along looking for a file manager might not realize the cause and choose a different one because XY appears to be slow to start.

A problem -- if there is one -- is not with XYplorer, but with software that does the scanning, because it assumes that unsigned executable files *must be* suspicious.

If a potential user believes a product is slow to start, it would be logical/sensible for him/her to enquire as to the potential root cause of it, I would think

[admin]

There are plenty of workarounds of course, they don't really solve the problem though.

The real problem is the next potential user who comes along looking for a file manager might not realize the cause and choose a different one because XY appears to be slow to start.

A problem -- if there is one -- is not with XYplorer, but with software that does the scanning, because it assumes that unsigned executable files *must be* suspicious.

If a potential user believes a product is slow to start, it would be logical/sensible for him/her to enquire as to the potential root cause of it, I would think

Code: Select all

potential user != ideal user