InstallAware

You can write any additional fields you like (including, size) using Write Registry.

This is what Microsoft said about the issue after they looked at our MSI and registry settings:

I have received an update from the Product team. The issue was possibly because of the system component(ARPSYSTEMCOMPONENT) value being set to 1 by the Tajima DGML by Pulse 2009 application.

So, as a workaround, I would suggest you NOT to set the SystemComponent=1 value in the ARP registry entry

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\{A4C53FEC-3727-49F5-8B9B-7176FC4C82EA} for Tajima DGML by Pulse 2009 for submission .

Hope above clarifies. However, please let me know if you have any questions on this and also if this works.

Now, is this registry setting set by us or by IA?

...Matt

InstallAware sets this registry entry to ensure that InstallAware's bootstrapper runs during uninstallation, and not just a generic MSI uninstall.

If this is the problem, it means you are looking at the wrong part of the registry. Look at the additional part that InstallAware writes which does refer to the bootstrapper and will contain everything you need.

Michael,

I think it's obvious that Microsoft is having issue with something IA is doing in the install. It's also obvious that IA has reasons for doing what it's doing.

I'd recommend that the IA development team communicate directly with Microsoft on this issue, rather than using me as a middle man. I think communication would be more clear and efficient.

I am sure that I won't be the last one to have issues submitting to the logo program. So whether it's Microsoft or IA which needs to make changes, it's probably best if the two of you discuss the matter directly.

BTW, have you guys been able to successfully submit a test installation of your own to Microsoft's "Compatible with Windows 7" program?

...Matt

Hi Matt,

I'm sorry you're having troubles with Microsoft...

Unfortunately we cannot communicate on your behalf. We have thousands of customers and we cannot act as their representatives with Microsoft

Unfortunately, Microsoft/Lionbridge hire amateurs for logo testing/validation. However you will find that they are easily educated. In my previous post, I told you that they are checking the wrong registry key - they are looking at the key which is suppressed. Just tell them to look at the key which is not suppressed.

I sure wish they were easier to work with, but I can assure you this isn't the first time a customer is running into issues (and won't be the last) - the problem is not with InstallAware or your installer but the lack of communication/knowledge with your testers.

Best of luck!

Michael,

I will forward your comments to Microsoft.

However, has IA tried submitting an installer of it's own to the Windows 7 logo site?

...Matt

No, we are not pursuing logo certification, and we never have with any version of InstallAware. Logo certification makes more sense for consumer products, rather than development tools.

I meant has IA submitted any installer that the IA product produced (as a test) to ensure that it's working ok with the Windows 7 logo site?

...Matt

My installers has all passed the Works with Windows 7 Test, but only after I got my installer to write the two extra registry attributes.

I've also tried to test an installer that is generated from IA with everything set to the default settings, and this will not pass the certification. As the guys that are running the site where everything is submitted requires you to have the Version set before you can go ahead and submit the generated report.

I would think that it would be in IA's best interest to by default generate installers that will pass this certification. Specially since it's, from where I'm standing, a very simple fix to do.

Actually, the version fields are optional and do not fail the test (see related thread in forum). If your product is being declined because of this, it is a tester error.

However, you will be pleased to know that InstallAware 9.04 does record version fields automatically to ensure a smoother ride for certification.

Awesome


[StartRant]
Even though the test toolkit says it's not required to have those field, here's a quote from the winqual support guys:

However the version information is also required for the successful completion of the submission, if it is missing then Winqual will not accept the submission.

So while it's seemingly not required, it is required if you want to actually submit the report that was generated with the test tool.

I wrote back asking why this was a requirement on the site while it's clearly marked as just a warning and not required by the test tool. I then got this response:

It is required.

[/EndRant]

On a related note for anyone trying to submit their report, note that you can't use special character is the Product Description box (ie. & ') it will let you continue to the end of the sequence and then when you click finish throw and error stating that there is something wrong with the site, please try again later.

And again that sounds very good Michael Nesmith. Will Display Version and Estimated Size be added as well ?

Display Version is already there, you may manually record size.

I just ran into this issue with IA 9 and the final (October 2009) release of the Windows 7 Logo Toolkit while dealing with my 32-bit application.

The problem is that IA 9 does not create the MajorVersion and MinorVersion registry values under:

For 64-bit OS:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\MY-PROGRAM

For 32-bit OS:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MY-PROGRAM

If the MajorVersion and MinorVersion registry values are not found by the toolkit then you are unable to submit your results to Microsoft. It is not a matter of "Pass with Warnings", you simply cannot submit.

I was able to work around the problem by having my install script create the needed MajorVersion and MinorVersion registry values.

But it would be good if IA did this itself.

Actually, the latest build of InstallAware has been recording these properties for a while now (since July of last year).

I should also advise that we have followed Microsoft's published rules for logo validation and their third party tool seems to check for some unpublished additional keys.

Perhaps I should have been a bit more clear.

IA 9.06 SP1 creates two sets of keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\.

One key is the GUID associated with the product. The other key is equivalent to $TITLE$ in the IA script.

IA 9 does create the needed MajorVersion and MinorVersion values under the GUID key.

It DOES NOT create them under the $TITLE$ key, and that's where the problem occurs because the Logo Toolkit is unhappy if it cannot find those values.