PDA

View Full Version : FAQ: Program Assistant Compatibility (PCA) and Windows 7



NewsArchive
08-08-2009, 01:59 PM
Quite a few users are already running Windows 7 RTM. If your installation
and/or application is not Win7-aware, your Windows 7 customers will see a
"This program might not have installed correctly" message every time the
setup program or application closes.

"Program Assistant Compatibility" (PCA) is a Windows component that tries to
help older applications work on new versions of Windows. In Windows Vista,
PCA looked for the presence of a manifest in an .exe that set the
"RequiredExecutionLevel". If found, the PCA assumed that the executable was
built to target Windows Vista, and that it was tested on Vista. If not, and
the executable was detected as an installer, PCA would check the "Add/Remove
Programs" list to see if the installation succeeded. If no "Add/Remove
Programs" entry was made, PCA would offer to re-run the .exe in Windows XP
SP2 compatibility mode.

For Windows 7, PCA no longer looks at the RequiredExecutionLevel setting.
It uses the new Compatibility section of the manifest to identify
executables built for Windows 7.

Please note that you need (at least) SetupBuilder 6.9 -- Build 2581 (April
29, 2009) or the new SetupBuilder 7.0 (Gold) to compile Win7-aware
installations. But you need SetupBuilder 7.0 (Gold) to make your own
application files Win7-aware by using the enhanced "#embed UAC manifest..."
compiler directive.

If both your installation and application files are Win7-aware, they can run
without causing a PCA mitigation on both Vista and Windows 7 (and Server
2008).

We strongly recommend that all customers upgrade to the new version of
SetupBuilder 7.0 as soon as possible to maintain the highest level of
support, performance and reliability.

To make your previous SetupBuilder installations Win7-aware, you only have
to open the project in SB7 and recompile. That's it.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

NewsArchive
08-10-2009, 03:00 AM
> Quite a few users are already running Windows 7 RTM. If your installation
> and/or application is not Win7-aware, your Windows 7 customers will see a
> "This program might not have installed correctly" message every time the
> setup program or application closes.

Friedrich,

Thanks for this FAQ - as soon as MSDN subscribers could retrieve Windows 7
RTM on August 6 - I downloaded and installed clean installs of x64 and x86
versions - and began in earnest to rebuild a Windows 7 x86 Virtual Machine
particularly for Clarion 6 development.

Having to reinstall quite a few development tools AND knowing that I had to
use troubleshooter compatibility for some of those tools BECAUSE they did
NOT have SetupBuilder Windows 7 compatible install - SURE made those
installs STICK out like a SORE Thumb!

> To make your previous SetupBuilder installations Win7-aware, you only have
> to open the project in SB7 and recompile. That's it.

OK, that is true MOSTLY! :-D

Of course, for those of us that DO use SetupBulder to UAC manifest our
programs, dlls, -

the #embed UAC manifest compiler directive WILL initially display -
Compatibility Information - None when we load a previous SB project in the
latest SB7, and of course, we need to change that to Windows 7 as
illustrated in the attached screen shot.

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/


--------------------------------------------------------------------------------