«

All seems to have went well, both on XP & 7. Maybe with all the
upcoming competition, Billy Bob is starting to do a better job. ? <g>
--
Old Gringo
Just West Of Nowhere
Enjoy Life And Live It To Its Fullest
http://www.NuBoy-Industries.com

OldGringo38 <> wrote in
news:hb4ogb$m56$:

> All seems to have went well, both on XP & 7. Maybe with all the
> upcoming competition, Billy Bob is starting to do a better job. ? <g>

It's still almost the "every second one" rule: dos 4, dos 6, Millenium,
Vista. If it was an automaker they'd be called citroen or lada.

--
(setq (chuck nil) car(chuck) )

OldGringo38 wrote:
> All seems to have went well, both on XP & 7. Maybe with all the
> upcoming competition, Billy Bob is starting to do a better job. ? <g>

On my Win2000Pro machine, two of the .Net Framework 2.0 Service Pack 1
updates keep wanting to install even though they are already installed.
KB953300 and KB971110.
Anyone else having this issue?
Buffalo

On Wed, 14 Oct 2009 09:50:54 -0500, OldGringo38 <>
wrote:

>All seems to have went well, both on XP & 7. Maybe with all the
>upcoming competition, Billy Bob is starting to do a better job. ? <g>

I still can't get my Bluetooth adaptor to work right on Win7 x64. I wish
those drivers would appear on the updates.

On Wed, 14 Oct 2009 11:13:46 -0600, "Buffalo"
<> wrote:

>
>
>OldGringo38 wrote:
>> All seems to have went well, both on XP & 7. Maybe with all the
>> upcoming competition, Billy Bob is starting to do a better job. ? <g>
>
>On my Win2000Pro machine, two of the .Net Framework 2.0 Service Pack 1
>updates keep wanting to install even though they are already installed.
>KB953300 and KB971110.
>Anyone else having this issue?
>Buffalo
>


I had that problem a few weeks back. I ended up using the
MSI cleanup tool from MS along with their reset.cmd tool to
reset the machine permission to their default state. Ran
the update again with no problem. Reset permissions as
required. Today's update went smoothly.

Lugnut

"Buffalo" <> wrote:

>
>
>OldGringo38 wrote:
>> All seems to have went well, both on XP & 7. Maybe with all the
>> upcoming competition, Billy Bob is starting to do a better job. ? <g>

>On my Win2000Pro machine, two of the .Net Framework 2.0 Service Pack 1
>updates keep wanting to install even though they are already installed.
>KB953300 and KB971110.
>Anyone else having this issue?

I have the autoupdates service disabled, just now my firewall asked if
C:\Temp\ProgramUpdaterMain.exe could run
1) nothing gets installed by me running from the temp dir.

I check the file out and it's a windows update - the fact it got past
my firewall Comodo is of concern.

While it could be for a few things this was kinda stood out.

Windows Installer
0000A2C8: 4837483174987348g.
0000A30E: \sseun.
0000A328: MAINPROG:
0000A340: REQUIRESELEVATEDADMIN:
0000A378: MISCELLANEOUS>
0000A39E: \sseintupdret.
0000A3CE: <ARGUMENTS>
0000A3EA: <NAME>
0000A3FC: REQUIRED
0000A414: PREREQ
0000A42C: (Required for
0000A454: DOTNET
0000A46A: .NET Framework
0000A49C: (Prerequisite for .NET Framework)
0000A4E6: \SSEIUBSreturn.
0000A51C: OpenProgram
0000A56A: MSIExecute

--

How soon people forget
http://imgur.com/CVkCC.png

wrote:

> "Buffalo" <> wrote:
>
>>
>>
>>OldGringo38 wrote:
>>> All seems to have went well, both on XP & 7. Maybe with all the
>>> upcoming competition, Billy Bob is starting to do a better job. ? <g>
>
>>On my Win2000Pro machine, two of the .Net Framework 2.0 Service Pack 1
>>updates keep wanting to install even though they are already installed.
>>KB953300 and KB971110.
>>Anyone else having this issue?
>
>I have the autoupdates service disabled, just now my firewall asked if
>C:\Temp\ProgramUpdaterMain.exe could run
>1) nothing gets installed by me running from the temp dir.
>
>I check the file out and it's a windows update - the fact it got past
>my firewall Comodo is of concern.
>
>While it could be for a few things this was kinda stood out.

>0000A42C: (Required for
>0000A454: DOTNET
>0000A46A: .NET Framework
>0000A49C: (Prerequisite for .NET Framework)
>0000A4E6: \SSEIUBSreturn.
>0000A51C: OpenProgram
>0000A56A: MSIExecute

I found I had three .exe files or updates, understand I've never had
the autoupdates service running on any version of windows. The
majority of them are to fix holes in I.E. and I don't use that
program, this is the first time any updates have made it my way, So
I'm not used to reading them.

I dropped ZoneAlarm to give Comodo a try and it allowed the files to
show up, as MS is treated as a trusted site and allowed two way
access. *this with autoupdates disabled*.

One file is the autoupdater itself (ProgramUpdaterMain.exe), both
mention Chris.Long, this is his program http://www.ssesetup.com/ and
the update (SSEInternetUpdaterX.exe), SSE Setup Internet Update Module
(Main Process) It requires:
..NET framework download ability if user doesn't have

That's what the code in the last post ment - if you don't have .Net,
it's going to get/install it for you.

I just can't find the entry in the registry - to turn it off if you
already .net and it keeps trying to install it.

The other: Roboex32.exe
0000195E: FileDescription
00001980: RoboHELP Extensions for WinHelp
00001C58: WinHelp 2000: the next generation of WinHelp.

Is just a help file program.

Posted this as I insinuated in the last post that the update installed
..Net, which is correct with the right conditions (you don't have it)
but it's not what it's suppose to do.

--

This guy paints himself... no trick photography ... no photoshop ...he just paints himself... (v1kram.posterous.com)

http://v1kram.posterous.com/liu-boli...nvisible-man/?

Buffalo wrote:
> OldGringo38 wrote:
>> All seems to have went well, both on XP & 7. Maybe with all the
>> upcoming competition, Billy Bob is starting to do a better job. ? <g>
>
> On my Win2000Pro machine, two of the .Net Framework 2.0 Service Pack 1
> updates keep wanting to install even though they are already
> installed. KB953300 and KB971110.
> Anyone else having this issue?
> Buffalo
Well, I got it fixed.
I used the MS Net Framework uninstaller 'cleanup_tool.exe' (which I got from
MS support) and uninstalled all NET versions, rebooted and then used MS
updates to install whatever it said I should. Now it is fine.
Anyhow, the secret was in using the above mentioned uninstall tool,
rebooting and then using MS Updates.
Buffalo