[Gurgelmeyer]

In theory a lot like that. My thought is, that each and every file should be stored only once - no matter how often it appears, no matter under which names, no matter how many different ways it is compressed, no matter if it's (recursively) embedded in MSI streams or other cabinets. It's perfectly simple - it could even be expanded to handle more than just the MSCF formats. The only difference to the end user would be that (s)he would have to download an EXE file instead of a ZIP file.

Best regards
Gurgelmeyer

[Dels]

or maybe we could ask someone in AutoPacther 2K project how they did it

please don't mind, this only a "cruel" joke

[vci]

great work gurgelmeyer!

i think this release and 5.2 will be the best versions (dont need extreme edition at all ...)

[erpdude8]

Hi Gurgelmeyer. sorry I wasnt able to follow up my old topic about the FP2k KB838018 hotfix. I was busy in the other side of the MSFN forums site.

wonder if the KB139071 OLE automation hotfix is or will be included in your unofficial Win2k SP5 pack.
Files are build 4528; replaces the previous 4526 build from KB886765. MS KB article 139071:
http://support.microsoft.com/kb/139071

I have this Win2k hotfix. someone sent it to me. let me know if you need it.

This post has been edited by erpdude8: 02 May 2006 - 05:32 PM

[-I-]

btw. G from around next week or so i got myself a (powerhouse)
> (dualcore 1,8ghz cpu) with 2gb of ram...
so if for any reason you nead any cpu-time for building it or compressing it.. just ask...

[Gurgelmeyer]

erpdude8, on May 2 2006, 05:29 PM, said:

Hi Gurgelmeyer. sorry I wasnt able to follow up my old topic about the FP2k KB838018 hotfix. I was busy in the other side of the MSFN forums site.

It is included in the 5.1.2195.21 release.

Quote

wonder if the KB139071 OLE automation hotfix is or will be included in your unofficial Win2k SP5 pack.
Files are build 4528; replaces the previous 4526 build from KB886765. MS KB article 139071:
http://support.microsoft.com/kb/139071

I have this Win2k hotfix. someone sent it to me. let me know if you need it.

That is not included - yes, I need it

/G

PS - @-I- - Cool - I might need some compression stats later on

[erpdude8]

Gurgelmeyer, on May 7 2006, 05:31 PM, said:

Quote

wonder if the KB139071 OLE automation hotfix is or will be included in your unofficial Win2k SP5 pack.
Files are build 4528; replaces the previous 4526 build from KB886765. MS KB article 139071:
http://support.microsoft.com/kb/139071

I have this Win2k hotfix. someone sent it to me. let me know if you need it.

That is not included - yes, I need it

/G

PS - @-I- - Cool - I might need some compression stats later on

I have sent the KB139071 win2k hotfix to MDGx and it's mentioned on his web site. you can get it here directly:
http://www.mdgx.com/files/2K139071.EXE

I havent been able to use my email for several days since my brother and I paid for a high speed DSL internet connection last week.

[-I-]

just send me a PM and we'll set something up (havn't got the darn thing yet though, (thay said i should expact it this week),

by the way: as soon as i have in ill add the specs to a siggy (with a link to som pick LOL (benchmark-scores included ofcaurse)

[Inki]

My thanks to Gurgelmeyer for this great contribution.

I did notice that update KB832414 for MSXML 2.5 (msxml.dll 8.0.7002.0) is not included.

I am not sure how useful or necessary this update is if later versions of MSXML are also installed. Nor am I certain how this update plays together with current updates of Internet Expolorer, or if it has somehow been made obsolete.

KB832414 has been totally changed from its original appearance. It no longer has a download link to this update but points on to KB887606 which only covers later versions of MSXML.

Anyway, the download link for this update can still be found at MDGx's site on the page for Internet Explorer.

P.S. Edited addition (made after the following post by -I-):
I just noticed that my laptop at work, which has XPSP2 installed by IT people, and where I do not have admin rights, also has the updated msxml.dll file among others. So I guess that at least it probably is not harmful.

This post has been edited by Inki: 10 May 2006 - 09:48 AM

[-I-]

if im not mistaken its an outdated patch. (and outdated xml version, SP5 should use a newer version i believe,

But to be sure id have to check...

[erpdude8]

Inki, on May 9 2006, 02:19 AM, said:

I did notice that update KB832414 for MSXML 2.5 (msxml.dll 8.0.7002.0) is not included.

The KB832414 update for MSXML 2.5 is obsolete, Inki and XML 2.5 is buggy. Anyway, KB832414 is replaced by KB887606. Upgrade to MSXML 2.6 which fixes problems with XML 2.5 and then apply the KB887606 update for XML 2.6.

MSXML.DLL version 8.0.7002 is included in Windows XP SP2 and Windows Server 2003 SP1.

This post has been edited by erpdude8: 15 May 2006 - 04:50 PM

[erpdude8]

Inki, on May 9 2006, 02:19 AM, said:

KB832414 has been totally changed from its original appearance. It no longer has a download link to this update but points on to KB887606 which only covers later versions of MSXML.

Here's the Microsoft Download Center link to MSXML 2.5 KB832414 hotfix (which still works):
http://www.microsoft.com/downloads/details...&DisplayLang=en

[Inki]

Thank you for your information on KB832414.

The question I had in mind but failed to spell out is: Since W2k contains MSXML 2.5/msxml.dll by default, is it better to
- leave it as it is, or
- upgrade it to the latest version 8.0.7002 with KB832414?

My uninformed guess is that with later versions of MSXML (2.6/msxml2.dll, 3.0/msxml3.dll, etc.) installed it probably does not matter very much. Like erpdude8 said above, later versions fix problems with 2.5, and I guess they take care of most of the business anyway. (I do have them on my system.)

Still, based on what I have understood I would choose to also upgrade the msxml.dll file, because:
- New versions of MSXML after 2.5 do not replace files for older versions, there may be some parallel functioning (?)
- One would (naïvely, perhaps) expect the newer msxml.dll file to be less buggy, just in case if it might be used.
- Microsoft in its grand wisdom has decided to include the upgraded msxml.dll file in XPSP2 and 2003SP1.
- It satisfies my personal desire for completeness .

So you can also read my post as a humble between-the-lines suggestion that maybe there might be a case for including KB832414 for MSXML 2.5 in the Unofficial Service Pack. Of course, this might be a bad idea, but I would not know, as my reasoning is no better informed than what you can read above .

This post has been edited by Inki: 25 May 2006 - 08:51 AM

[dosworld]

quick question out to everyone, suppose one wanted to slimstream the hotfix for the new kernel driver (included in the update rollup package) how would one do so?

[Gurgelmeyer]

Just a quick update:

KB832414 - added
KB909363 - added
KB139071 - added
KB885912 - added
KB912196 - added

No new downloads just yet.

Best regards
Gurgelmeyer

[the_guy]

@ Gurgelmeyer:

I also sent you the 897711 and 898465 updates for Windows 2000 to your gmail account.

the_guy

[rjdohnert]

I only have a CD where I had integrated SP4 using Nlite. I want to add USP 5.1. Can I do that or do I need to still have a virgin Windows 2k CD? Also is there anyway to edit the registry in Nlite so I can load progman or another shell as my default desktop?

[Electrician]

rjdohnert, on Jun 1 2006, 06:01 PM, said:

I only have a CD where I had integrated SP4 using Nlite. I want to add USP 5.1. Can I do that or do I need to still have a virgin Windows 2k CD? Also is there anyway to edit the registry in Nlite so I can load progman or another shell as my default desktop?

I tried to Nlite an Nlited source and ttried to slipstream from an Nlited source - they both failed to
make anything useable. Never tried to USP an Nlited source.

As for changing shells.. example: single user change
[HKEY_CURRENT_USER\Software\WinShellEx]
"Default"="GeoShell"

[HKEY_CURRENT_USER\Software\WinShellEx\GeoShell]
"Start"="c:\\geotest\\GeoShell.exe"

For all users:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Shell"="LiteStep.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"Shell"="c:\\litestep\\LiteStep.exe"

etc etc. exact steps will be explained in docs for your new shell.

[-I-]

you should do that from $oem$\cmdlines.txt
just start a batch file and reg merge tweaks.reg or regedit /s regtweaks.reg

but id recomand doing it asap in your install and dont wait for runonceEx and the shell is than alread loaded (partly)

[rcll]

will there be an updated release with the june patches?