41 replies to this topic

[JRosenfeld]

Fine here. No errors.

[Erik Ramey]

 Cyrus, on Dec 13 2007, 02:46 PM, said:

Not on my computers, they (I tested it on several) still get the same MD5 error as before.

What are the MD5's of the files that are reporting errors?

[StanTheMan]

 Erik Ramey, on Dec 14 2007, 01:51 AM, said:

What are the MD5's of the files that are reporting errors?

Yip, i am also still getting the file verification error:

Looking for file C:\apup\modules\Components\__dotnet\dotnet3.5_enu.apm
MD5 Hashes do NOT match. Expecting 89205a7b98b191a1d46c21ca5d20cfc9, but found 19bfd0c211fd85be41bdcab0910c3aae!!!

[Erik Ramey]

Okay, I see what happened. I accidently added to MD5's when I last corrected it. Fixed

Thanks Stan!

[StanTheMan]

 Erik Ramey, on Dec 14 2007, 07:53 AM, said:

Okay, I see what happened. I accidently added to MD5's when I last corrected it. Fixed

Thanks Stan!

Thanks Erik!

I still have the same error, but i'll wait a while and try it again later, maybe the incorrect script is still being
cached somewhere on my side.

Thanks.

[Erik Ramey]

Quite odd... I just tested with the old script that was incorrect which APUP didn't delete. Once I deleted it manually, the newest one was download. I then copied the bad one back and this time APUP deleted like it was suppose to.

Check this for me Stan:
The bad one contains this below in the modules portion of the script:
DetectFile=autopatcher:\modules\Components\__dotnet\dotnet3.5_enu.apm
DetectHash=19BFD0C211FD85BE41BDCAB0910C3AAE
DetectHash=89205a7b98b191a1d46c21ca5d20cfc9

While the good one has only this:
DetectFile=autopatcher:\modules\Components\__dotnet\dotnet3.5_enu.apm
DetectHash=19BFD0C211FD85BE41BDCAB0910C3AAE

Do you still have the bad version of the script?

[StanTheMan]

 Erik Ramey, on Dec 14 2007, 08:12 AM, said:

Quite odd... I just tested with the old script that was incorrect which APUP didn't delete. Once I deleted it manually, the newest one was download. I then copied the bad one back and this time APUP deleted like it was suppose to.

Check this for me Stan:
The bad one contains this below in the modules portion of the script:
DetectFile=autopatcher:\modules\Components\__dotnet\dotnet3.5_enu.apm
DetectHash=19BFD0C211FD85BE41BDCAB0910C3AAE
DetectHash=89205a7b98b191a1d46c21ca5d20cfc9

While the good one has only this:
DetectFile=autopatcher:\modules\Components\__dotnet\dotnet3.5_enu.apm
DetectHash=19BFD0C211FD85BE41BDCAB0910C3AAE

Do you still have the bad version of the script?

Hi again Erik,
Sorry i have been out all day.

Ok here is a clean copy of the problem log:

DetectFile=autopatcher:\modules\Components\__dotnet\dotnet3.5_enu.apm
DetectHash=19BFD0C211FD85BE41BDCAB0910C3AAE
DetectHash=89205a7b98b191a1d46c21ca5d20cfc9

Notice it still has two copies of the Hashes!

Very strange as i deleted ALL the scripts and reran apup only selecting "Dotnet Add on pack for Windows"
And then it gives me that file verification error!

Strange?

Stan

[sh1leshk4]

Yes...it's strange indeed...since I just downloaded the .NET add-on and everything went fine.
Is it probably because you're (somehow) connected to a proxy that caches downloads?

Edited by sh1leshk4, 14 December 2007 - 02:06 PM.

[StanTheMan]

 sh1leshk4, on Dec 14 2007, 04:06 PM, said:

Yes...it's strange indeed...since I just downloaded the .NET add-on and everything went fine.
Is it probably because you're (somehow) connected to a proxy that caches downloads?

Well thats what i was thinking

But i have a direct dsl connection to the internet ??

Strange?

I dont even think deleting all the dotnet files and re downloading them will help?

Stan.

[sh1leshk4]

Mmm...I think it's the downloaded script file that has the problem, not the downloaded .NET file.
Try deleting all .list and .script files in your AP folder first.

[StanTheMan]

 sh1leshk4, on Dec 14 2007, 05:25 PM, said:

Mmm...I think it's the downloaded script file that has the problem, not the downloaded .NET file.
Try deleting all .list and .script files in your AP folder first.

Allready tried that a few times!
Its still bringing down the wrong file.
I'll try again later!

Thanks,

Stan

[Cyrus]

It worked fine for me this time.

[StanTheMan]

Yip! worked fine for me now too

Must be a cache problem of some sorts.

Thanks guys!

Stan.

[BrainDedd]

Any chance of changing Dotnet 2.0 SP1 to show for windows xp as well, since it's there and all.

[Erik Ramey]

 BrainDedd, on Jan 10 2008, 05:32 AM, said:

Any chance of changing Dotnet 2.0 SP1 to show for windows xp as well, since it's there and all.

Dotnet 2.0 SP1 isn't required for Windows XP since Dotnet 3.5 already includes this.

[BrainDedd]

OK I just figured for people like me that don't have or want dotnet 3.0+ on since there's nothing out there that really uses it, that having it as an option was maybe a good idea.

[James]

 BrainDedd, on Jan 12 2008, 10:21 AM, said:

OK I just figured for people like me that don't have or want dotnet 3.0+ on...

That would include me, too...
--
James

[DesertJerry]

Will the update include: ParallelExtensionsToNetFramework35_Dec07CTP.msi

and/or PowerToysForNETCompactFramework35.msi

Just wondering?

[Erik Ramey]

@'DesertJerry - Honestly I haven't looked into this. Is this something that the average user will need? Well.. the average person that uses dotnet will need...

[sh1leshk4]

I don't think it should be included.
The .NET pack is supposed to make any .NET apps work, not to help the average user to create one.

Just my $0.02. =)