Firewall Exceptions and Windows 64bit causes install to fail?

[NewsArchive]

Testing my install on windows 7 Enterprise, 64 bit.
I get "MyProgram Installer has stopped working. A problem caused the
program to stop working correctly. Windows will close the program and
notify you if a solution is available."

I used messages to figure out where it was dying, and discovered it is while
entering the first firewall exception.
Add Firewall Exception(Application) "%_SB_INSTALLDIR%\myprog.exe" --
Friendly Name: "MyProgram"

any ideas what could cause this?
I don't even know where to start. All this was working fine before (on 32
bit)

Help me Friedrich-Wan Kenobi! you're my only hope!

Glenn Paschal

[NewsArchive]

Hi Glenn,

> Testing my install on windows 7 Enterprise, 64 bit.
> I get "MyProgram Installer has stopped working. A problem caused the
> program to stop working correctly. Windows will close the program and
> notify you if a solution is available."
>
> I used messages to figure out where it was dying, and discovered it is
> while entering the first firewall exception.
> Add Firewall Exception(Application) "%_SB_INSTALLDIR%\myprog.exe" --
> Friendly Name: "MyProgram"
>
> any ideas what could cause this?
> I don't even know where to start. All this was working fine before (on 32
> bit)
>
> Help me Friedrich-Wan Kenobi! you're my only hope!

I have developed and uploaded a demo (source + binary).

http://www.lindersoft.com/projects/FirewallExceptionDemo.zip

Tested on three different Win7 Ultimate 64-bit machines. Worked without any
problem (see attached screenshot).

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]

ok, being a little absent minded... it was NOT the exceptions that was
failing...
brain must have been a little fried on Friday. Will start new thread.
My apologies.
(Thanks for the example, tho)

Glenn Paschal

[NewsArchive]

In case the message went out before I caught it, please ignore my message
that "firewall is working" still testing.
brain was ok on Friday, just not working today <g>
I think I need to be rebooted.
Memory overflow.
Bad memory read at 0000:0000.
I need coffee.

Glenn Paschal

[NewsArchive]

Friedrich, you are right, your demo works fine. I even recompiled it on my
development machine, and it works great on 7-64bit. But, Mine is absolutely
no different. So, what am I missing? Only difference I could see is that
in mine, "MyProgram" was actually "TCS Front Counter" (note the spaces), so
I tried it without spaces, still dying at the same spot. and now, when I
recompile, SB7 crashes after "Adding Digital Certificate". I get the
following:

Problem signature:
Problem Event Name: APPCRASH
Application Name: sb7.exe
Application Version: 7.0.2762.0
Application Timestamp: 4ae7193f
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdadb
Exception Code: c0000005
Exception Offset: 000560d9
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Is it possible that something is corrupted? have you seen this before?

Glenn Paschal

[NewsArchive]

Ok, SB7 crash seems to be fixed. Rebooting the system and the problem went
away.
However, still having the install crash on the firewall entry.
I've tried everything I can think of.
Any ideas would be greatly appreciated.
Thanks,
-Glenn.

[NewsArchive]

Glenn,

> However, still having the install crash on the firewall entry.
> I've tried everything I can think of.
> Any ideas would be greatly appreciated.

Unfortunately, I have no idea, sorry. I have tested it again on another
Win7 Ultimate 64-bit machine. This time, I changed the application name to
"TCS Front Counter". It created the Firewall Exception without any problem
(see attached screenshot).

Friedrich

[NewsArchive]

I'm going to copy my install to a test.sb7, and start ripping stuff out
until it either works, or I have something small I can send you. Perhaps it
is a combination of things I am missing... maybe something to do with code
signing... who knows... will get back to you.

Thanks!
-Glenn.

[NewsArchive]

Ok.... hmm.... weird... didn't expect to have something this quick...
open TirePowerClient.sb7 (the SB7 that has the firewall problems...)
save as FireWallTest.sb7
change exe name to FireWallTest.exe
Compile SB7
Move to Win7-64bit machine, and test install.
Worked... no errors.

Opened FireWallTest.sb7, save as TirePowerClient.sb7 (overwriting)
change exe name to TirePowerClient.exe
Compile SB7, move to Win7-64bit machine and test...
Worked... no errors.

Now, I feel like I'm in some black-n-white twilight zone show... (Is Rod
Sterling hiding behind that door?)
What ever it was, it's fixed now.
Thanks Friedrich, for bearing with me.
-Glenn.

[NewsArchive]

> Now, I feel like I'm in some black-n-white twilight zone show... (Is Rod
> Sterling hiding behind that door?)
> What ever it was, it's fixed now.
> Thanks Friedrich, for bearing with me.

<VBG> :) Thanks for the updare.

Friedrich

[NewsArchive]

I double-dog updare ya<g>

Jeff Slarve

[NewsArchive]

>
>I double-dog updare ya<g>
>

<BG>. Fat fingers...

Friedrich

[NewsArchive]

"Serling" <g>

jane

[NewsArchive]

oui...

I can't even make stupid comments with out getting stupid comments! <g>

next time I is jes gonna type it jes like'ns I seys it.
ser, whit ya thunk `bout them apples?

Glenn Paschal

[NewsArchive]

That can be painful during nasal mining <g>

--
Russell B. Eggen
www.radfusion.com
Clarion developers: www.radfusion.com/devs.htm

[NewsArchive]

Ok, my firewall bug is back again. (gees)

I went thru the exact same steps I did before that "fixed" it, but no luck
this time.
Also, I noticed some more odd behavior.

As a result of my save-as's and recompiles, I ended up with 2 identical
files: TirePowerClient.exe, and FireWallTest.exe.
FireWallTest.exe installs fine (actually installs TirePower Client).
TirePowerClient.exe fails at the firewall update.
Rename TirePowerClient.exe to TirePowerClient_BAK.exe,
Rename FireWallTest.exe to TirePowerClient.exe, and rerun this file.
It fails at the firewall update.
Rerun TirePowerClient_BAK.exe (the original TPC.exe that was failing), and
it works fine.

Through several tests with the two files, I found it doesn't matter what the
name is, it will run, as long as the name ISN'T TirePowerClient.exe. Is
Win7 putting something in the registry or saving some information that could
be causing the firewall update to fail?

(hair coming out in clumps at this point!)

Thanks to ANYONE who figures this one out, as well as a free lunch on me. (I
hope you like McDonalds? <G>)

Glenn Paschal

[NewsArchive]

Glenn,

> Through several tests with the two files, I found it doesn't matter what
> the name is, it will run, as long as the name ISN'T TirePowerClient.exe.
> Is Win7 putting something in the registry or saving some information that
> could be causing the firewall update to fail?

Just for fun: what happens if you temporarily disable your
antivirus/antispyware security product and run TirePowerClient.exe?

>
> (hair coming out in clumps at this point!)
>

<BG>

Friedrich

[NewsArchive]

Well, my test machine does not have any antivirus or antispyware. It is
there for the purpose of MS Logo Verification.
Win7 is the only thing on the box.

However, on a hunch, I uninstalled my client, went into the registry and
searched for "TirePowerClient".
There were about a dozen entries (most of which were "recents" and
"pathing", but not all).
I deleted all of them, and now the install works flawlessly.

I wish I had made a list of them.

Glenn Paschal

[NewsArchive]

Hi Glenn,

> However, on a hunch, I uninstalled my client, went into the registry and
> searched for "TirePowerClient".
> There were about a dozen entries (most of which were "recents" and
> "pathing", but not all).
> I deleted all of them, and now the install works flawlessly.
>
> I wish I had made a list of them.

That's very interesting. Thanks for the information!

Friedrich

[NewsArchive]

Well, the problem came back again, on the same file.
Cleaning out the registry didn't fix it, and now renaming it doesn't fix it.
I am beginning to suspect it has something to do with the Windows 7 Logo
Certification routine that is running around the install. I wonder if
anyone else has tried the W7Logo stuff...

Glenn Paschal

[NewsArchive]

Glenn,

> Well, the problem came back again, on the same file.
> Cleaning out the registry didn't fix it, and now renaming it doesn't fix
> it.
> I am beginning to suspect it has something to do with the Windows 7 Logo
> Certification routine that is running around the install. I wonder if
> anyone else has tried the W7Logo stuff...

Aha, okay. You did not mention that you are running the Win7 Software Logo
Toolkit when this happens. It is very well possible (99.99%) that this is
caused by the toolkit itself.

Friedrich