Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • September 01, 2015, 07:22:33 PM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: DC and dotNet  (Read 3381 times)

oblivion

  • Supporting Member
  • Joined in 2010
  • **
  • Posts: 386
    • View Profile
    • Donate to Member
DC and dotNet
« on: November 02, 2011, 03:14:09 PM »
Since installing the recent dotNet security patches, my poor netbook's been beside itself.

First, Windows lost its activation, and I had to redo it.

Next, ALL my DC software stopped working. CHS, FARR and LaunchBar Commander, and even DCUpdate won't run.

I hate Microsoft sometimes.

Anyone have any helpful ideas? (Win7 Starter, patched up to date -- unfortunately!)

-- bests, Tim

...this space unintentionally left blank.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 34,976
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Donate to Member
Re: DC and dotNet
« Reply #1 on: November 02, 2011, 03:18:15 PM »
I dont know why any of the DC software should stop running -- none of them use dotNet.

oblivion

  • Supporting Member
  • Joined in 2010
  • **
  • Posts: 386
    • View Profile
    • Donate to Member
Re: DC and dotNet
« Reply #2 on: November 02, 2011, 04:23:11 PM »
I dont know why any of the DC software should stop running -- none of them use dotNet.
No, I know. But the dotNet security patches are almost always a complete  :down: to install without impacting lots of other stuff. Last time I did them without thinking, lots of stuff -- including DC software -- broke so I just ran a system restore and hid the updates. After the event I discovered Susan Bradley's PatchWatch recommending not doing them for pretty much those reasons... and then I find that she's now saying the October 13 .net4 patches can't really be skipped.

Here's the link.

So I bit the bullet. And my teeth now hurt quite a bit, if you see what I mean.

I'd sort of hoped that someone here might have had a similar experience and have some idea of which bit of Windows I can chuck rocks at to make everything work properly again.

I'll let you know if I work out how to fix it. I haven't yet braved the system logs, so that's my next stop.  :'(

...and a quick first look suggests a common problem: ntdll.dll is what Windows says is falling in a heap.
-- bests, Tim

...this space unintentionally left blank.
« Last Edit: November 02, 2011, 04:27:56 PM by oblivion, Reason: addendum »

Renegade

  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 12,787
  • Tell me something you don't know...
    • View Profile
    • Renegade Minds
    • Donate to Member
Re: DC and dotNet
« Reply #3 on: November 02, 2011, 06:29:08 PM »
Have a read here:

http://blogs.msdn.co...06/05/30/611355.aspx

It might help... YMMV.
Slow Down Music - Where I commit thought crimes...

Freedom is the right to be wrong, not the right to do wrong. - John Diefenbaker

oblivion

  • Supporting Member
  • Joined in 2010
  • **
  • Posts: 386
    • View Profile
    • Donate to Member
Re: DC and dotNet
« Reply #4 on: November 02, 2011, 06:46:59 PM »
It might help... YMMV.
It might -- thanks!  :Thmbsup:

I've been struggling with the thing all evening and am getting nowhere fast; the link you posted suggests (from the last page) that if I rip out everything that's not intrinsic to the OS then try installing .Net framework 4 on its own, it might do the trick. I'll give it a go -- but for the time being, as tomorrow's already booked for Christmas shopping  :( I'll boot it into ubuntu and go back to Microsoft-bashing on Friday.  :)
-- bests, Tim

...this space unintentionally left blank.