Tiny Personal Firewall 64 Conundrum

Soon after a clean install of XP64 on a homebuilt Athlon 64 3000+/MSI
K8N Neo2 Platinum machine, I installed Tiny Personal Firewall 64.

Now I have a strange problem and posts to the tinysoftware.com forums
are pretty sparse, so I thought I'd ask here.

Tiny worked fine over the past week or so but yesterday, when I tried
to bring up the menu from the system tray icon, I got an installation
(!!) dialog instead stating that files were being prepared for
installation of the Tiny personal firewall. Of course, I clicked
cancel and after a delay, the dialog disappeared. Odd, thought I.

So, I decided to reboot in case something had fouled up during the
last reboot. Same behavior.

OK, so I'll uninstall Tiny and reinstall it. Pop up Add/Remove
Programs and begin the Tiny uninstall. The process starts fine but
then hangs saying that a Windows installer file necessary for this
*installation* is missing. Contact Microsoft. Huh?

Only option is to cancel the uninstallation. Check the Tiny dir and
most files are gone and the icon is gone from the system tray as well.
So it appears to be (mostly) gone. Tried a new installation, but that
failed with the same error. Checked the task mgr. Process List and
removed what appeared to be a couple of errant msiexec processes.
Rebooted, tried uninstall and install again with the same error.

So, I'm at an impass now. Only thing I haven't done is try to expunge
all references to Tiny from the Registry, but I'm uncertain if that's
what would be causing these problems.

One other oddity, I decided that if Tiny wasn't working I'd better at
minimum turn on the XP64 firewall so went to do that and found that it
had been turned on at some point. I am certain that I had turned it
off before installing Tiny and did not turn it on again at any point.
Why or how it was enabled, I don't know.

I'll understand if no one has any ideas because this behavior is
unlike any I've experienced with previous flavors of Windows. It's
just downright weird.

_jd
j e d @ comcast.net

David
Mon Jun 06 17:19:00 CDT 2005

Jason Durbin<jedurbin@example.com.invalid> wrote in:

> So, I'm at an impass now. Only thing I haven't done is try to expunge
> all references to Tiny from the Registry, but I'm uncertain if that's
> what would be causing these problems.

I think that would be a good next move, search for files that belong to Tiny
particularly .dll files, then search the registry for any references and
delete them.

Then try to install it again.

> One other oddity, I decided that if Tiny wasn't working I'd better at
> minimum turn on the XP64 firewall so went to do that and found that it
> had been turned on at some point. I am certain that I had turned it
> off before installing Tiny and did not turn it on again at any point.
> Why or how it was enabled, I don't know.

?? Odd, try turning it off and then reboot and see if it stays off.


--
David R. Norton MVP
<d_r_norton@yahoo.com>

Jed
Mon Jun 06 19:38:24 CDT 2005

On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
<d_r_nortonNO@SPAMyahoo.com> wrote:

>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>
>> So, I'm at an impass now. Only thing I haven't done is try to expunge
>> all references to Tiny from the Registry, but I'm uncertain if that's
>> what would be causing these problems.
>
>I think that would be a good next move, search for files that belong to Tiny
>particularly .dll files, then search the registry for any references and
>delete them.
>
>Then try to install it again.

Thanks for the confirmation. I'll try that tomorrow and report the
results.

_jd
j e d @ comcast.net

Jason
Tue Jun 07 05:54:13 CDT 2005

On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
<d_r_nortonNO@SPAMyahoo.com> wrote:

>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>
>> So, I'm at an impass now. Only thing I haven't done is try to expunge
>> all references to Tiny from the Registry, but I'm uncertain if that's
>> what would be causing these problems.
>
>I think that would be a good next move, search for files that belong to Tiny
>particularly .dll files, then search the registry for any references and
>delete them.
>
>Then try to install it again.

Yep. That worked. Just like all these security apps, Tiny left
droppings all over the Registry as well as sharing some naming
conventions with other apps, namely NOD32's amon.exe some system
files, so special care is needed when cleaning out the Registry. Thank
goodness for System Restore.

Still don't understand what caused the original corruption of the
System Tray icon menu -- I've seen no one else mention a similar
problem. Perhaps the Tiny folk will come up with an answer eventually.

_jd
j e d @ comcast.net

John
Tue Jun 07 07:21:04 CDT 2005

Glad to hear that System Restore worked for you. It destroyed my system
requiring a complete re-install
Hopefully if I have another bad program install it will actually help.


"Jason Durbin" <jedurbin@example.com.invalid> wrote in message
news:truaa11ftrtkmu797fu5qs7fk5306m0pae@4ax.com...
> On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
> <d_r_nortonNO@SPAMyahoo.com> wrote:
>
>>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>>
>>> So, I'm at an impass now. Only thing I haven't done is try to expunge
>>> all references to Tiny from the Registry, but I'm uncertain if that's
>>> what would be causing these problems.
>>
>>I think that would be a good next move, search for files that belong to
>>Tiny
>>particularly .dll files, then search the registry for any references and
>>delete them.
>>
>>Then try to install it again.
>
> Yep. That worked. Just like all these security apps, Tiny left
> droppings all over the Registry as well as sharing some naming
> conventions with other apps, namely NOD32's amon.exe some system
> files, so special care is needed when cleaning out the Registry. Thank
> goodness for System Restore.
>
> Still don't understand what caused the original corruption of the
> System Tray icon menu -- I've seen no one else mention a similar
> problem. Perhaps the Tiny folk will come up with an answer eventually.
>
> _jd
> j e d @ comcast.net
>

Jason
Tue Jun 07 07:38:43 CDT 2005

On Tue, 7 Jun 2005 05:21:04 -0700, "John Barnes" <jbfoofy@email.net>
wrote:

>"Jason Durbin" <jedurbin@example.com.invalid> wrote in message
>news:truaa11ftrtkmu797fu5qs7fk5306m0pae@4ax.com...
>> On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
>> <d_r_nortonNO@SPAMyahoo.com> wrote:
>>
>>>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>>>
>>>> So, I'm at an impass now. Only thing I haven't done is try to expunge
>>>> all references to Tiny from the Registry, but I'm uncertain if that's
>>>> what would be causing these problems.
>>>
>>>I think that would be a good next move, search for files that belong to
>>>Tiny
>>>particularly .dll files, then search the registry for any references and
>>>delete them.
>>>
>>>Then try to install it again.
>>
>> Yep. That worked. Just like all these security apps, Tiny left
>> droppings all over the Registry as well as sharing some naming
>> conventions with other apps, namely NOD32's amon.exe some system
>> files, so special care is needed when cleaning out the Registry. Thank
>> goodness for System Restore.
>>
>> Still don't understand what caused the original corruption of the
>> System Tray icon menu -- I've seen no one else mention a similar
>> problem. Perhaps the Tiny folk will come up with an answer eventually.

>Glad to hear that System Restore worked for you. It destroyed my system
>requiring a complete re-install
>Hopefully if I have another bad program install it will actually help.

Worked like a charm. Created a restore point before messing with the
Registry. Got a blue screen on reboot after getting a bit
trigger-happy while deleting all the Tiny entries left behind and
apparently deleting a required system file. Powered down, then up and
was given the option to restore from a Restore Point. Worked just as
advertised, didn't even lose the deletions of Tiny from the Registry,
it just replaced the mis-deleted system file.

Sorry you had a bad time with System Restore, perhaps it was
situational and not an inherent flaw with x64 System Restore.

-jd
j e d @ comcast.net

John
Tue Jun 07 08:17:47 CDT 2005

Thanks. Seems like it was situational but it deleted all my network
connections and several programs would not complete loading. For now I will
make a Ghost backup and a restore point until I have a successful restore.
I didn't have to use system restore in x86 very often in 3 1/2 years but the
4-5 times it worked like advertised. This one sure didn't.


"Jason Durbin" <jedurbin@example.com.invalid> wrote in message
news:qs4ba1h8hk181t7bvrba7bc64887efpo6e@4ax.com...
> On Tue, 7 Jun 2005 05:21:04 -0700, "John Barnes" <jbfoofy@email.net>
> wrote:
>
>>"Jason Durbin" <jedurbin@example.com.invalid> wrote in message
>>news:truaa11ftrtkmu797fu5qs7fk5306m0pae@4ax.com...
>>> On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
>>> <d_r_nortonNO@SPAMyahoo.com> wrote:
>>>
>>>>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>>>>
>>>>> So, I'm at an impass now. Only thing I haven't done is try to expunge
>>>>> all references to Tiny from the Registry, but I'm uncertain if that's
>>>>> what would be causing these problems.
>>>>
>>>>I think that would be a good next move, search for files that belong to
>>>>Tiny
>>>>particularly .dll files, then search the registry for any references and
>>>>delete them.
>>>>
>>>>Then try to install it again.
>>>
>>> Yep. That worked. Just like all these security apps, Tiny left
>>> droppings all over the Registry as well as sharing some naming
>>> conventions with other apps, namely NOD32's amon.exe some system
>>> files, so special care is needed when cleaning out the Registry. Thank
>>> goodness for System Restore.
>>>
>>> Still don't understand what caused the original corruption of the
>>> System Tray icon menu -- I've seen no one else mention a similar
>>> problem. Perhaps the Tiny folk will come up with an answer eventually.
>
>>Glad to hear that System Restore worked for you. It destroyed my system
>>requiring a complete re-install
>>Hopefully if I have another bad program install it will actually help.
>
> Worked like a charm. Created a restore point before messing with the
> Registry. Got a blue screen on reboot after getting a bit
> trigger-happy while deleting all the Tiny entries left behind and
> apparently deleting a required system file. Powered down, then up and
> was given the option to restore from a Restore Point. Worked just as
> advertised, didn't even lose the deletions of Tiny from the Registry,
> it just replaced the mis-deleted system file.
>
> Sorry you had a bad time with System Restore, perhaps it was
> situational and not an inherent flaw with x64 System Restore.
>
> -jd
> j e d @ comcast.net
>

Christian
Tue Jun 07 10:09:48 CDT 2005

John Barnes <jbfoofy@email.net> wrote:
> Glad to hear that System Restore worked for you. It destroyed my
> system requiring a complete re-install
> Hopefully if I have another bad program install it will actually help.
>
As a beta tester for years now, I'm using system restore since winME.
Never ever had any problem at all with this function, it saved my life a few
times....
Of course, computing is not an exact science...

Cheers

--
Christian Hougardy (MS XP MVP)
Johannesburg - South Africa
http://msmvps.com/xpditif

Andre
Tue Jun 07 13:24:02 CDT 2005

I think System Restore only protects files created, not adjusting system
settings, since you could have done something to your PC when setting up a
network connection that could have caused your PC to malfunction.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

"John Barnes" <jbfoofy@email.net> wrote in message
news:OhdKVN2aFHA.760@TK2MSFTNGP10.phx.gbl...
> Thanks. Seems like it was situational but it deleted all my network
> connections and several programs would not complete loading. For now I
> will make a Ghost backup and a restore point until I have a successful
> restore. I didn't have to use system restore in x86 very often in 3 1/2
> years but the 4-5 times it worked like advertised. This one sure didn't.
>
>
> "Jason Durbin" <jedurbin@example.com.invalid> wrote in message
> news:qs4ba1h8hk181t7bvrba7bc64887efpo6e@4ax.com...
>> On Tue, 7 Jun 2005 05:21:04 -0700, "John Barnes" <jbfoofy@email.net>
>> wrote:
>>
>>>"Jason Durbin" <jedurbin@example.com.invalid> wrote in message
>>>news:truaa11ftrtkmu797fu5qs7fk5306m0pae@4ax.com...
>>>> On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
>>>> <d_r_nortonNO@SPAMyahoo.com> wrote:
>>>>
>>>>>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>>>>>
>>>>>> So, I'm at an impass now. Only thing I haven't done is try to expunge
>>>>>> all references to Tiny from the Registry, but I'm uncertain if that's
>>>>>> what would be causing these problems.
>>>>>
>>>>>I think that would be a good next move, search for files that belong to
>>>>>Tiny
>>>>>particularly .dll files, then search the registry for any references
>>>>>and
>>>>>delete them.
>>>>>
>>>>>Then try to install it again.
>>>>
>>>> Yep. That worked. Just like all these security apps, Tiny left
>>>> droppings all over the Registry as well as sharing some naming
>>>> conventions with other apps, namely NOD32's amon.exe some system
>>>> files, so special care is needed when cleaning out the Registry. Thank
>>>> goodness for System Restore.
>>>>
>>>> Still don't understand what caused the original corruption of the
>>>> System Tray icon menu -- I've seen no one else mention a similar
>>>> problem. Perhaps the Tiny folk will come up with an answer eventually.
>>
>>>Glad to hear that System Restore worked for you. It destroyed my system
>>>requiring a complete re-install
>>>Hopefully if I have another bad program install it will actually help.
>>
>> Worked like a charm. Created a restore point before messing with the
>> Registry. Got a blue screen on reboot after getting a bit
>> trigger-happy while deleting all the Tiny entries left behind and
>> apparently deleting a required system file. Powered down, then up and
>> was given the option to restore from a Restore Point. Worked just as
>> advertised, didn't even lose the deletions of Tiny from the Registry,
>> it just replaced the mis-deleted system file.
>>
>> Sorry you had a bad time with System Restore, perhaps it was
>> situational and not an inherent flaw with x64 System Restore.
>>
>> -jd
>> j e d @ comcast.net
>>
>
>

John
Tue Jun 07 13:44:18 CDT 2005

The only network connection I set up was a dial up connection. Worked
perfectly before the restore
There were 2 1394 connections and 2 network connections and 1 bridge setup
by the install program and never touched. No network connected.
All items were gone after restore. The Network Connections folder on the
start menu showed empty when hovered over.

I also tried to run 2 programs with shortcuts on the desktop and neither got
beyond the flash screen before freezing.

Just my experience. Glad others have had it work. I had a Ghost image 5
days earlier so I didn't loose too much. Just makes me more cautious.


"Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
news:e8j6Z44aFHA.580@TK2MSFTNGP15.phx.gbl...
>I think System Restore only protects files created, not adjusting system
>settings, since you could have done something to your PC when setting up a
>network connection that could have caused your PC to malfunction.
> --
> Andre
> Extended64 | http://www.extended64.com
> Blog | http://www.extended64.com/blogs/andre
> http://spaces.msn.com/members/adacosta
> FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
>
> "John Barnes" <jbfoofy@email.net> wrote in message
> news:OhdKVN2aFHA.760@TK2MSFTNGP10.phx.gbl...
>> Thanks. Seems like it was situational but it deleted all my network
>> connections and several programs would not complete loading. For now I
>> will make a Ghost backup and a restore point until I have a successful
>> restore. I didn't have to use system restore in x86 very often in 3 1/2
>> years but the 4-5 times it worked like advertised. This one sure didn't.
>>
>>
>> "Jason Durbin" <jedurbin@example.com.invalid> wrote in message
>> news:qs4ba1h8hk181t7bvrba7bc64887efpo6e@4ax.com...
>>> On Tue, 7 Jun 2005 05:21:04 -0700, "John Barnes" <jbfoofy@email.net>
>>> wrote:
>>>
>>>>"Jason Durbin" <jedurbin@example.com.invalid> wrote in message
>>>>news:truaa11ftrtkmu797fu5qs7fk5306m0pae@4ax.com...
>>>>> On Mon, 06 Jun 2005 15:19:00 -0700, "David R. Norton MVP"
>>>>> <d_r_nortonNO@SPAMyahoo.com> wrote:
>>>>>
>>>>>>Jason Durbin<jedurbin@example.com.invalid> wrote in:
>>>>>>
>>>>>>> So, I'm at an impass now. Only thing I haven't done is try to
>>>>>>> expunge
>>>>>>> all references to Tiny from the Registry, but I'm uncertain if
>>>>>>> that's
>>>>>>> what would be causing these problems.
>>>>>>
>>>>>>I think that would be a good next move, search for files that belong
>>>>>>to
>>>>>>Tiny
>>>>>>particularly .dll files, then search the registry for any references
>>>>>>and
>>>>>>delete them.
>>>>>>
>>>>>>Then try to install it again.
>>>>>
>>>>> Yep. That worked. Just like all these security apps, Tiny left
>>>>> droppings all over the Registry as well as sharing some naming
>>>>> conventions with other apps, namely NOD32's amon.exe some system
>>>>> files, so special care is needed when cleaning out the Registry. Thank
>>>>> goodness for System Restore.
>>>>>
>>>>> Still don't understand what caused the original corruption of the
>>>>> System Tray icon menu -- I've seen no one else mention a similar
>>>>> problem. Perhaps the Tiny folk will come up with an answer eventually.
>>>
>>>>Glad to hear that System Restore worked for you. It destroyed my system
>>>>requiring a complete re-install
>>>>Hopefully if I have another bad program install it will actually help.
>>>
>>> Worked like a charm. Created a restore point before messing with the
>>> Registry. Got a blue screen on reboot after getting a bit
>>> trigger-happy while deleting all the Tiny entries left behind and
>>> apparently deleting a required system file. Powered down, then up and
>>> was given the option to restore from a Restore Point. Worked just as
>>> advertised, didn't even lose the deletions of Tiny from the Registry,
>>> it just replaced the mis-deleted system file.
>>>
>>> Sorry you had a bad time with System Restore, perhaps it was
>>> situational and not an inherent flaw with x64 System Restore.
>>>
>>> -jd
>>> j e d @ comcast.net
>>>
>>
>>
>
>