made any progress?
Pete
> From: peterhul...@hotmail.com
> To: wix-users@lists.sourceforge.net
> Date: Sat, 14 Jan 2012 08:51:16 +
> Subject: Re: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
>
>
> I've
I've used an old (2004?) version of InstallShield and it generated a setup.exe
and the msi separately. I'm assuming that setup.exe is their bootstrapper and
was well-known enough to go onto the AV makers white-lists. When burn is
released hopefully its engine could also be white-listed, assumin
-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday, January 13, 2012 12:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
Burn is a little different because it is designed to recover from power
Burn is a little different because it is designed to recover from power
failures and unexpected reboots. To do that it writes to the RunOnce
registry key up front.
Other bootstrappers/chainers may not write to RunOnce except when a force
reboot is required in the middle of the chain. Then the
boot
On Fri, Jan 13, 2012 at 7:48 AM, Peter Hull wrote:
>
> > Date: Thu, 12 Jan 2012 20:56:15 +0100
> > From: n...@panorama9.com
> > > I would start by digitally signing your burn bundle.
> >
> >
> > The bundle is already signed with a Thawte code signing certificate
> The reported file name looks mor
> Date: Thu, 12 Jan 2012 20:56:15 +0100
> From: n...@panorama9.com
> > I would start by digitally signing your burn bundle.
>
>
> The bundle is already signed with a Thawte code signing certificate
The reported file name looks more like it's the extracted engine than your
bundle itself. Have you
be a way to turn
the "Malware detection feature"
>
> -Original Message-
> From: NIkolaj Steensgaard [mailto:n...@panorama9.com]
> Sent: Thursday, January 12, 2012 3:37 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Reopen Burn t
neral discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Reopen Burn triggers virus checker - ID:
3431068
On 01/12/2012 09:46 AM, Peter Hull wrote:
>> From: r...@robmensching.com
>> We'll need to teach this anti-virus program about Burn. Fortunately
big
>>
On 01/12/2012 09:46 AM, Peter Hull wrote:
>> From: r...@robmensching.com
>> We'll need to teach this anti-virus program about Burn. Fortunately big
>> programs, like Visual Studio, are using Burn and if it kills them I hope we
>> can muster some change.
> So are you saying we need to raise this as
> From: r...@robmensching.com
> We'll need to teach this anti-virus program about Burn. Fortunately big
> programs, like Visual Studio, are using Burn and if it kills them I hope we
> can muster some change.
So are you saying we need to raise this as an issue with Trend Micro? Is the
program tha
gt; >> Date: Wed, 11 Jan 2012 12:16:37 +0100
> >> From: n...@panorama9.com
> >> To: wix-users@lists.sourceforge.net
> >> Subject: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
> >>
> >> We have built a EXE with Wix 3
d, 11 Jan 2012 12:16:37 +0100
>> From: n...@panorama9.com
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] Reopen Burn triggers virus checker - ID: 3431068
>>
>> We have built a EXE with Wix 3.6 beta which are detected by Trend Micro
>> as "Malwa
sers
)
I'm glad someone else has seen this problem, especially as you have more
control over your environment than I do!
Peter
> Date: Wed, 11 Jan 2012 12:16:37 +0100
> From: n...@panorama9.com
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Reopen Burn trigge
We have built a EXE with Wix 3.6 beta which are detected by Trend Micro
as "Malware behavior" and
we are looking for the reason for this.
This is the log entry from Trend Micro
We have built a EXE with Wix 3.6 beta which are detected by Trend Micro
as "Malware behavior" and
we are looking for the reason for this.
This is the log entry from Trend Micro
15 matches
Mail list logo
