Hasta la VISTA

[NewsArchive]

All,

If you have not already made your installations (and applications) Windows 7
compatible, please do it now.

If your installation and/or application is not Win7-aware, your customers
will see a "This program might not have installed correctly"
message every time the setup program or application closes on Windows 7
machines.

"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. 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 7.

We strongly recommend that all customers upgrade to the new version of
SetupBuilder 7.0 to maintain the highest level of support, performance and
reliability. To make your previous SetupBuilder installations Win7-aware,
you only have to open the projects 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]

you've had it baby ;)

Thanks again Friedrich for ALL the tremendous work you did to offer us all the SB7 EXCELLENT tool


Merci

Cordialement - Best regards
Jean-Pierre GUTSATZ

CGF

DMC - Data Management Center
A tool to let you Migrate Import Export Transfer your Data
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" &
"Works with Windows Server 2008"

[NewsArchive]

Hi Jean-Pierre,

> you've had it baby ;)
>
> Thanks again Friedrich for ALL the tremendous work you did to
> offer us all the SB7 EXCELLENT tool

Thanks so much for your kind words ;-)

Friedrich

[NewsArchive]

> All,
>
> If you have not already made your installations (and applications) Windows 7
> compatible, please do it now.

Friedrich,

Yes, I echo JP's thank you as well!

> Thanks again Friedrich for ALL the tremendous work
> you did to offer us all the SB7 EXCELLENT tool

I guess it would be TOO much to expect other software developers to follow
ALL the advice in this message AND use SetupBuilder as well! :-D

I still cringe at some installs built by (well, won't name any)...

David

--
From David Troxell - Product Scope 7.9 - 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/

[NewsArchive]

Hi David,

> Yes, I echo JP's thank you as well!
>
>> Thanks again Friedrich for ALL the tremendous work
>> you did to offer us all the SB7 EXCELLENT tool
>
> I guess it would be TOO much to expect other software developers to follow
> ALL the advice in this message AND use SetupBuilder as well! :-D
>
> I still cringe at some installs built by (well, won't name any)...

<VBG> ;-)

Thank you!!!

Friedrich

[NewsArchive]

Hi Friedrich
I link a manifest (vista aware) into my program file (app). Would this
manifelt have to be upgraded, or should i stop using it and instead manifest
it via SB?

I am still on 6.9.2587 but not for long.

Here are the contents of the manifest:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="Vipilon.vPFaktura"
type="win32" />
<description>Vipilon Faktureringsprogram</description>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="asInvoker"
uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>

Best regards
Viggo Poulsen

[NewsArchive]

Hi Viggo,

> I link a manifest (vista aware) into my program file (app). Would this
> manifelt have to be upgraded, or should i stop using it and instead
> manifest it via SB?

Your manifest is not Win7-aware. I would suggest to use SB7 to embed a Win7
manifest into your app.

Friedrich

--
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]

> Hi Friedrich
> I link a manifest (vista aware) into my program file (app). Would this
> manifelt have to be upgraded, or should i stop using it and instead manifest
> it via SB?
>
> I am still on 6.9.2587 but not for long.

Viggo,

SetupBuilder 7 WILL do everything 6.9.2587 did - PLUS a LOT more! Don't put
it off - JUST start using SB7! :-D

And, as Friedrich suggested, use SB7 to Windows 7 manifest your programs.

David

--
From David Troxell - Product Scope 7.9 - 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/

[NewsArchive]

good advise, will follow :-)

Viggo Poulsen

[NewsArchive]

Hi Friedrich.

I'm on SB7 now and just need to be sure:
I need to add #embed UAC manifest to the script, right ?
If i select Windows 7, will it act as a correct manifest for Windows 7,
Windows Vista And Windows XP ? (i am a little worried about the XP stuff, as
i normally use the manifest to make my apps look good on XP).

Best regards
Viggo Poulsen.

[NewsArchive]

Hi Viggo,

> I'm on SB7 now and just need to be sure:
> I need to add #embed UAC manifest to the script, right ?
> If i select Windows 7, will it act as a correct manifest for Windows 7,
> Windows Vista And Windows XP ? (i am a little worried about the XP stuff,
> as i normally use the manifest to make my apps look good on XP).

Yes, you can use the "#embed UAC manifest..." directive to embed a Windows
7-aware manifest into you application. This manifest is fully backward
compatible (works fine with all previous Windows operating systems).

BTW, make sure your application is NOT already manifested!

Friedrich

--
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]

Hi Friedrich
Thank you for your Very quick answer. It always impresses me.
It all works as i hoped it would.

Best regards
Viggo Poulsen.

[NewsArchive]

> Hi Friedrich.
>
> I'm on SB7 now and just need to be sure:
> I need to add #embed UAC manifest to the script, right ?
> If i select Windows 7, will it act as a correct manifest for Windows 7,
> Windows Vista And Windows XP ?

Viggo,

Friedrich can offer the more technical explanation, but yes, a Windows 7
manifest selection covers Windows 7, Vista AND XP.

If you haven't already (or it's been some time - I update it frequently) -
download the CHM version of the first blog mentioned here for a lot of
significant information on many developer areas including Program Install
Techniques - Code Signing, App Data UAC Safe, etc

Also, Jane Fleming offers a wonderful resource as well at this address:

http://www.beachbunnysoftware.com/webinar/

The order IS important -

UAC manifest - Armadillo protect (optional) - CodeSign EXE IS important!

AND, and TimeStamp your Code Signing as well.

Making App Data UAC (Vista and Windows 7) safe and XP compatible

http://profileexchanges.com/blog/?p=120

* * * * *

Vista, Windows 7 and Clarion 6

C6 IDE appearance and help issues

"You can use the Windows XP version of winhlp32.exe to take full advantage
of the Clarion 6 Help in Vista." (same applies to Windows 7)

http://profileexchanges.com/blog/?p=20

* * * * *

Clarion 6 on Vista and Clarion Version Detection for 3rd Party Products

"The Clarion 6 Vista Installation Fix freeware application makes the
appropriate WIN.INI modifications so 3rd party installations can detect
Clarion 6 on Vista, Windows Server 2008 and Windows 7 machines."

http://profileexchanges.com/blog/?p=47

David

--
From David Troxell - Product Scope 7.9 - 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/

[NewsArchive]

Hi David
I was afraid loosing the XP stuff, so thank you for explaning it.
It is realy a good thing you have done, putting it all together in one
place. Unfurtunately i did all the work Before your excellent blog. In other
word, Jane's e-book and a lot of articles in these news. I'd better download
your latest version to get myself updated.

Best regards
Viggo Poulsen

[NewsArchive]

> Hi David
> I was afraid loosing the XP stuff, so thank you for explaning it.
> It is realy a good thing you have done, putting it all together in one
> place. Unfurtunately i did all the work Before your excellent blog.

Viggo,

Well, the resource has been a real work in progress over time, with many
great sources to draw upon.

Originally, it was focused on Clarion developer needs, but as I examined
the stats more closely - I realized software developers - regardless of
languages or tools used - were showing up in greater numbers

(and had originally when I misinterpreted the amazing early numbers -
thinking it was a new wave of Clarion interest - but the UAC Safe theme
drew the more general crowd)

SO I decided to greatly edit, add, and make it a more effective tool for
Software Developers of any persuasion.

Definitely, Jane has been a leader since early on - and Charles Edmonds of
LANSRAD (among others) was always a very good newsgroup responder - but
with the ProPath tool - opened Vista and Windows 7 to a whole lot more
Clarion developers with proper placement of data in UAC safe locations.

Plus, newsgroup messages scroll quickly, and constant repeating of the same
advice time and again - easier to say - download this! :-D

David

--
From David Troxell - Product Scope 7.9 - 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/

[NewsArchive]

Hi Friedrich

Can I do this for other peoples software namely your fellow countrymens
Teamviewer remote support program?

I've got a customised exe which I ship to provide remote support but it
doesnt come with a manifest file so can I knock one out for this exe and
include it in the installation or would I need to get them to create one?

--
--
Cheers
Richard

[NewsArchive]

Hi Richard,

> Can I do this for other peoples software namely your fellow countrymens
> Teamviewer remote support program?
>
> I've got a customised exe which I ship to provide remote support but it
> doesnt come with a manifest file so can I knock one out for this exe and
> include it in the installation or would I need to get them to create one?

Well, "in theory", yes <g>. SetupBuilder can embed a Win7-aware manifest
into any application that does have a .rsrc (resource) section.

But there are two important open questions:

1. Is it allowed to do it (embedding a manifest will change the binary
contents of the application).

2. The manifest will not only change the "look and feel" but also the way it
works (e.g. virtualization will be disabled). Making an application
UAC-aware is more than just adding a manifest. The application has to
follow the "UAC rules".

Friedrich

--
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]

Hi Friedrich,

> 1. Is it allowed to do it (embedding a manifest will change the binary
> contents of the application).

Would it not be enough to supply a .exe.manifest file or does that trick no
longer work in vista/win7? Haven't used it in years, just wondering. That
way it wouldn't change anything, but the OS _might_ apply the manifest
contents to the application.

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>> 1. Is it allowed to do it (embedding a manifest will change the binary
>> contents of the application).
>
> Would it not be enough to supply a .exe.manifest file or does that trick
> no longer work in vista/win7? Haven't used it in years, just wondering.
> That way it wouldn't change anything, but the OS _might_ apply the
> manifest contents to the application.

It's still allowed to use an external manifest file (for example, for
"hello.exe", the manifest "hello.exe.manifest"). But Microsoft recommends
to embed the manifest.

In the past, some of our customers had problems with external manifest
files -- the manifest file seemed to be ignored. Embedding the manifest
solved the problem. But why? We found out that, in most cases, this
happened after a legacy application was "updated" with an external manifest
to make it UAC-aware. There is some kind of "manifest caching" in Windows
to optimize performance. Reading the (external) manifest information at
application startup slows down the process and so Windows holds manifest
information in a "cache". If you start the application for the first time,
the loader looks for an internal/external menifest. If no manifest is
there, it will NOT look for it if you launch the application for the second
time (because it is too time consuming). So if you add an external
manifest, it's possible that Windows will not recognize it.

The same can happen if you update an external manifest from, say, a
Vista-aware to a Win7-aware version. To optimize performance, Windows reads
the set of meta-information about your application from the cache. As a
result, it's possible that (even if you have a Win7-aware external manifest
now), your application is still a "legacy" Vista application for Windows 7.

You'll never see this behavior with an embedded manifest. I also strongly
suggest to embed the manifest!

Friedrich

--
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]

Hi Friedrich,

> You'll never see this behavior with an embedded manifest. I also strongly
> suggest to embed the manifest!

Absolutely, but the question was if it was allowed since it changed the
binary code. If you try to embed a manifest in a wrapped exe or code signed
exe it's not going to work. Using an external manifest might work - that's
all I'm saying:)

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php