Mark,
Thank you for the nice links. Spent 2 hours noodling at AStebner's page.
I'll go back again for more research after I get some home chores
done...... :)
Later this afternoon I'll go play with the client machine some more.
Nice to know that I am not alone with dot-net issues (even if it is my
1st; and, on a fresh install?) I do so wish this was less confusing,
but I am getting use to it.
LOL!
Best,
Duncan
On 08/24/2010 19:53, Mark Dodge wrote:
http://blogs.msdn.com/b/astebner/archive/2005/04/08/406671.aspx
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_
cleanup_tool.zip
Go to the first link, the second link is the tool.
Mark Dodge
MD Computers
Houston, TX
-----Original Message-----
From: hardware-boun...@hardwaregroup.com
[mailto:hardware-boun...@hardwaregroup.com] On Behalf Of Mark Dodge
Sent: Tuesday, August 24, 2010 6:34 PM
To: hardware@hardwaregroup.com
Subject: Re: [H] MS dot-NET
As I said in a different thread there is a way to remove ALL .net stuff and
start fresh, without something that requires it from 2.o forward. I will
look for the specifics and post it.
Mark Dodge
MD Computers
Houston, TX
-----Original Message-----
From: hardware-boun...@hardwaregroup.com
[mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DSinc
Sent: Tuesday, August 24, 2010 4:42 PM
To: hardware@hardwaregroup.com
Subject: Re: [H] MS dot-NET
Mark,
I'd like to start as suggested. MS no longer lists their 'compendium'
KB for v2.0. I am still doing reverse research to maybe find it.
Conflicting MS docs indicate the dot-net will NOT install UNLESS there is an
app previously installed the requires dot-net. OK. Now, I have to dig thru
5 other clients to find which app requires dot-net? Way too much fun.
Good news: the old client is back up and running w/o BSODs and other odd
crashes. This post suspect pata hd, suspect kbd, and, confirmed sagged psu.
This dot-net business may just get down-graded to "future noise."
Best,
Duncan
On 08/24/2010 16:57, Mark Dodge wrote:
Yes start with 2.0,, NOT 2.0 sp1
Mark Dodge
MD Computers
Houston, TX
-----Original Message-----
From: hardware-boun...@hardwaregroup.com
[mailto:hardware-boun...@hardwaregroup.com] On Behalf Of Bobby Heid
Sent: Friday, August 06, 2010 9:55 PM
To: hardware@hardwaregroup.com
Subject: Re: [H] MS dot-NET
I love .Net! The positives are that it allows you to do so much with
so little code.
As for a rebuild, I usually put 2.0, 3.0, 3.5, and 4.0. Not a lot of
stuff uses 1.1 that I have come across. Windows update will put all
of those on, I think.
Bobby
-----Original Message-----
From: hardware-boun...@hardwaregroup.com
[mailto:hardware-boun...@hardwaregroup.com] On Behalf Of DSinc
Sent: Friday, August 06, 2010 9:16 PM
To: Hardware Group
Subject: [H] MS dot-NET
Some months back our collective convinced me that MS DOT-NET was
painless and may be beneficial in the future.
OK. I bit. I run it on 3 clients. It is here. It runs (I hope?). Still
do not see any positive or negative
effect......................until...........
I rebuild a machine from scratch.
I have DOt-NET v3.5 sp1 on running clients.
I tried the optional v4 DOT-NET during last month's updates. It
bombed/failed.
Fine. I can stay at 3.5sp1.
I've read to being blind about DOT-NET. Yes, I have mostly RTFM!
On a new install should I optionally install the OLD v1.1 DOT-NET base
to start the game again????
Then I will just let MS Update do what MS Update does......... :)
Best, Duncan
