12 replies to this topic

[Erik Ramey]

Just updated the W2K with a new version today. I don't have the ability to increment the Version number so just keep a look out for these posts

Changelog:

Implemented zip compression for AP modules
Added NonCritical modules
Removed KB895181 from Critical (Already present in NonCritical)

[Cyrus]

Don't forget to change the version from 1.1 to 1.2 (you haven't as of this post).

[Erik Ramey]

Cyrus, on Nov 25 2007, 10:42 PM, said:

Don't forget to change the version from 1.1 to 1.2 (you haven't as of this post).

Well, I did mention that I don't have the ability to update the versioning

[Cyrus]

lol, so I'm not paying attention today...........

[Erik Ramey]

New Script Deployed for Windows W2K

Changelog

Added Components to APUP
Updated Detection for Roots Update Module

[Erik Ramey]

Another New Script Deployed for Windows W2K

Changelog

Updated Multiple Modules - Compatibility with Win XP Modules

[Cyrus]

Aside from the file verification error, I had no issues with the new script, so congrats!

[Erik Ramey]

Another update today:

Removed KB820888 - Replaced by KB891861 W2K Rollup
Removed KB822831 - Replaced by KB891861 W2K Rollup
Removed KB883935 - Replaced by KB891861 W2K Rollup
Added KB908506 - Unable to print over network after (KB896423)

[Rudy]

Hi Everybody,

I've tested the latest W2K ENU script - version 1.2 beta (26 November 2007), downloaded without any errors. I think this version can be marked as stable.

Edited by Rudy, 03 December 2007 - 05:32 AM.

[Cyrus]

The latest version (as of late on December 12) gave a file verification error. However, on subsequent runs it gives no errors and the log shows no checksum problems. Any idea what could be causing this erratic behavior?

[James]

Quote

Any idea what could be causing this erratic behavior?

One possibility is that there is a typo in the latest autopatcher_2k_enu_nov07.script

In the middle is:

DownloadTo=autopatcher:\modules\Components\windows_components_2k_x86_enu.zip
ExpectedSize=185569
ExpectedHash=F53410C73D5E908595702E13C95A828D

There is an extra 5 , ie the true size is 18569 (18 k not 185 k). The MD5 hash is correct. Could this be the cause?
--
James

[Erik Ramey]

Good catch. That was the culprit. Updated

[Cyrus]

Great, that fixed it!