• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
WildBill

PE Tool for creating patches

695 posts in this topic

WildBill,

I've been having some problems with my computer and don't have access to my 2K system at the moment :(

I'll try to test your patch as soon as possible.

0

Share this post


Link to post
Share on other sites

I've just tested it but still no difference unfortunately :(

0

Share this post


Link to post
Share on other sites

I've found one more mistake on britols' page and this one I'd call critical.

2511455 is said to supersede 980232 but it does not because there's no rdbss.sys in it. If you slipstream 2511455 and don't include 980232 at the same time, you'll get a BSOD during Windows setup.

I prepared a fixed version where I added the rdbss.sys from 980232:

Windows2000-UU-KBz2511455-v2-x86-Global.exe

0

Share this post


Link to post
Share on other sites

Thanks tomasz86.

Aside from rdbss.sys, did you add anything else to 2511455?

If not, I guess it's OK to continue using 980232 together with the existing 2511455 by WildBill. Is that right?

0

Share this post


Link to post
Share on other sites

No, the only thing I added was rdbss.sys :) It's different in case of 2479628 & 2079403 where changes are related strictly to the registry.

Of course you can use both 980232 & 2511455. It's just (in my opinion) that the fewer updates, the better ;)

0

Share this post


Link to post
Share on other sites
the fewer updates, the better

Sure, but that's not the only consideration.

Thanks tomasz86.

Edited by bristols
0

Share this post


Link to post
Share on other sites

I've removed KB908536.

Uxtheme.dll seems to cause problems with .NET Framework based applications. I tried both versions - one from OldCigarette and the other one from BlackWingCat but unfortunately it's always the same. There's an error when trying to launch .NET based programs.

0

Share this post


Link to post
Share on other sites

I added two updates:

Windows2000-UU-MSRDP7-x86-ENU.exe <- MS Remote Desktop 7.0 (quite experimental but works)

Windows2000-UU-WIC-x86-Global.exe <- Windows Imaging Component (WIC)

Both of them rely on DLLs coming from either BlackWingCat's KDW or directly from Windows XP.

I'd also like to add one important information. Starting from this moment I'm going to test updates only in a system with (at least) BlackWingCat's kernel v5 installed. They may work without the kernel but don't have to. I'm sorry to say it but I just haven't got the time to test them in a configuration without unofficial kernel installed :(

The kernel is also required for applications written in Visual Studio 2010 so I think using it is just inevitable.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

I added:

OnePiece_Microsoft.NET_Framework_v3.5.30729.3644.4_True_AddOn_ENU_W2K.7z

This is modified version of OnePiece's .NET 3.5 True AddOn for XP/2K3. I fixed the dependencies to make it work smoothly in Windows 2000. The files used to fix them come either from BlackWingCat's KDW or directly from Windows XP. You must install OnePiece's .NET 2.0 True AddOn together with one!! When slipstreaming in HFSLIP, both of them should go to HFAAO folder.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

WildBill,

As a long-time lurker to this thread, I am amazed at your dedication to fixing bugs and extending the usefulness of Windows 2000.

Regarding KB2393802, I was wondering if it might be better to release two versions of this patch - one with bootskin support and one without. That way, people who run into problems (like tomasz86) can simply use the version without bootskin support.

I must admit that I've been too chicken to install KB2393802 on my computer even though I might finally get my ATI TV Wonder 750 working since you added KeAcquireInterruptSpinLock and KeReleaseInterruptSpinLock support. I think the only other XP-only command the driver uses is RtlGetVersion (maybe I can hex edit it to use GetVersionEX).

Thanks for your great work.

0

Share this post


Link to post
Share on other sites

The thought has crossed my mind, though I'd still like to try a little more to fix it once and for all. I've been out of action with a virus for the past week, hence the lack of updates (and I still have it :( -- physical virus, not a computer one). The time has allowed me to think about where tomasz's problem might be coming from. I put together this update which leaves everthing in place but circumvents loading bootskin settings:

Windows2000-KB2393802-v1-early-c5l-x86-ENU.exe

Edited by WildBill
0

Share this post


Link to post
Share on other sites

Unfortunately it still doesn't work :( It dies around 80%.

0

Share this post


Link to post
Share on other sites

Unfortunately I can't recreate the problem so I'm trying to find it by eliminating potential causes. Here is another one that (1) removes the call to load the image from the registry, (2) removes the call to load the image from disk, and (3) puts in a small fix when setting up the image palette.

Windows2000-KB2393802-v1-early-c5m-x86-ENU.exe

Edited by WildBill
0

Share this post


Link to post
Share on other sites

No difference with c5m :(

0

Share this post


Link to post
Share on other sites

Ugh. Here's another that fixes a bug in parsing "NOGUIBOOT" and clears direction flags when messing with the palette (if they weren't already cleared that would be a big problem).

Windows2000-KB2393802-v1-early-c5n-x86-ENU.exe

It's still the same :}

0

Share this post


Link to post
Share on other sites

(sigh)

I went through all of the bootskin code and revamped how I deal with the stack -- except for two particular routinea, this one takes a minimally-invasive approach instead of saving everything in sight.

Windows2000-KB2393802-v1-early-c5o-x86-ENU.exe

Edited by WildBill
0

Share this post


Link to post
Share on other sites

No positive effect unfortunately :(

So it's the bootskin support that causes all these problems right? The last version that worked was the one with no bootskin support implemented yet. Is it correct?

It's just a wild guess but maybe there's something different with Win2k Pro and Server in this field? On the other hand, it runs fine under a VM so it's unlikely...

0

Share this post


Link to post
Share on other sites

Sorry, I think I lost myself by reading this thread too little. And many other may be feeling like I do. Are you positive the problem is caused by the bootskin code added?

0

Share this post


Link to post
Share on other sites

It happens when I enable all of the bootskin support, but the problem has been tracking down the exact cause.

For this test, I went all the way back to c5c since that was the last one that worked (it didn't have the bootskin code hooked in). This one hooks just one tiny piece in (actually just a helper routine, not really bootskin related). Maybe I can connect the bootskin stuff one tiny piece at a time until it fails. For now, I'm only going to update ntkrnlmp.exe since that's the one that tomasz uses.

Windows2000-KB2393802-v1-early-c5c2-x86-ENU.exe

Edited by WildBill
0

Share this post


Link to post
Share on other sites

It works :)

By the way, just to add something positive...

Word 2007 works "out of the box" with your kernel installed (Excel & PowerPoint 2007 work with BWC kernel v5 too but Word doesn't).

59JnMs.png

and I've been trying to do something with IE7 but it doesn't look very well yet.

MArvis.png

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

It works :)

Wow! Makes me tempted to buy a copy of O2k7...I'm still using O2k.

I also want to try Office 2010 too but I can't get the thing install here. It's a trial version but I don't think the installer of the proper one is different... so I'll probably have to install it in other 'supported' system and copy files to Win2k manually.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.