Framework\v1.0.3705\mscorwks.dll not a valid image

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Beemer Biker - 27 Feb 2006 19:45 GMT

I get that error message when installing critical service pack for dotnet
1.1

...actually... the update just fails with a general error. If I download
the service pack and run the install then I see that message.

Anyway, I poked around \Windows\Microsoft.NET\Framework\v1.0.3705 and
something does not seem right. I see that file mscorwks.dll and another
file named mscorsvr.dll that is the exact same size down the the byte count.
I did an fc/b compare and both are identical. Strange.

Then I brought up explorer and attempted to get the version # off of them.
None of the dll's I checked the properties of had a version tab property.
They are all dated 1/4/2002

Can I just delete this directory? ie: 1.0.3705?

I went to a thinkpad that also has xp pro sp2, it had that same directory
1.0.3705 but neither of those wks nor svr files were there. The file all
later later dates. Not sure what is going on.

Signature

=======================================================================
Beemer Biker joestateson@grandecom.net
http://TipsForTheComputingImpaired.com
http://ResearchRiders.org Ask about my 99'R1100RT
=======================================================================

Reply to this Message

Dmytro Lapshyn [MVP] - 28 Feb 2006 08:52 GMT

Hi,

The v1.0.3705 folder corresponds to .NET Framework 1.0, not 1.1
For .NET 1.1 files, you should be looking into v1.1.4322

>I get that error message when installing critical service pack for dotnet
> 1.1
[quoted text clipped - 17 lines]
> 1.0.3705 but neither of those wks nor svr files were there. The file all
> later later dates. Not sure what is going on.

Reply to this Message

Beemer Biker - 28 Feb 2006 14:00 GMT

> Hi,
>
> The v1.0.3705 folder corresponds to .NET Framework 1.0, not 1.1
> For .NET 1.1 files, you should be looking into v1.1.4322

Then microsoft's install is using the wrong directory. None of those old
dll's appeared to have been registered and they were exact duplicates byte
for byte with diffeerent named dll's in the same directory. I suspect
whoever handled 1.0 got themselves into dll hell and the new 1.1 guy
programmed installshield (??) to look for any dll of the same name and get
rid of it. That is murphy's best guess.

Anyway I deleted that directory and now I get a differerent error
message..another file in a different directory. Since the system seems
working and I got dotnet 2.0 already, I went to the microsoft update and hid
that 1.1 option so I would not get pestered by it again.

..thanks..

BTW: I assume I dont need 1.1 if I got 2.0? I do have the first version of
Visual Studio.net and assume it can use 2.0? It is on a different computer
so I am not concerned. The computer I got the problem with has Visual Studio
6 with SP6, but AFAIK I am not useing any dot net features.

Signature

Reply to this Message

Dmytro Lapshyn [MVP] - 01 Mar 2006 08:22 GMT

> BTW: I assume I dont need 1.1 if I got 2.0? I do have the first version
> of
[quoted text clipped - 3 lines]
> Studio
> 6 with SP6, but AFAIK I am not useing any dot net features.

If an application targets 1.1, you will need 1.1 to run it. You can probably
trick it to run on 2.0 with assembly version redirects, but nothing can be
guaranteed since 2.0 introduces several breaking changes and is not fully
backwards compatible.

As for Visual Studio versions, the things are as follows:

VS6 (with any SP applied) does not need .NET at all.
VS 2002 needs .NET 1.0
VS 2003 needs .NET 1.1
VS 2005 needs .NET 2.0

>> Hi,
>>
[quoted text clipped - 23 lines]
> Studio
> 6 with SP6, but AFAIK I am not useing any dot net features.

Reply to this Message

Framework\v1.0.3705\mscorwks.dll not a valid image

Free Magazines