Jump to content

discdude

Member
  • Posts

    12
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by discdude

  1. Ahhh.

    Finally.

    The VM with my rewritten kernel32 comes up with no errors. I have maybe half a dozen more routines to add, and then the question is, how to test it in the community?

    I would just release it with a warning that it is a test version that should only be used in a virtual machine or a secondary system (i.e., not your only computer). The Windows 2000 community is pretty small so (hopefully) you won't get buried with vague bug reports.

  2. I didn't notice it before but VirtualBox needs two more APIs to install properly:

    SETUPAPI.DLL -> SetupSetNonInteractiveMode

    SETUPAPI.DLL -> SetupUninstallOEMInfW

    As I said before, no rush on getting these in but it would be nice to have the ability to run VirtualBox 4.x on Windows 2000. :)

    Again, keep up the great work!

    Did you try BlackWingCat's setupapi.dll? I don't know if it supports those two functions, but it is probably worth a try.

    http://blog.livedoor.jp/blackwingcat/archives/873798.html

  3. I couldn't find any other obvious problems aside from the ones above so I've posted MS11-020 V5. Hopefully it will help...it's working for me, at least, though I'm not running ZoneAlarm.

    WildBill you're the best. MS11-020 V5 solves the blue screen at boot when ZoneAlarm is installed. Everything seems to be working fine now.

  4. I'd need to get my hands on vsdatant.sys to try to see what's going on...I could put it in IDA Pro and see what that instruction is doing. I assume it runs normally without the patch installed?

    Yes, it works normally without the patch installed.

    I attached a copy of vsdatant.sys to this post. If need be, you can also download a copy of ZoneAlarm 7.0.483.000 from: http://download.zonealarm.com/bin/free/1023_zl/zlsSetup_70_483_000_en.exe

    Thanks for your help.

    vsdatant.zip

  5. Just wanted to report my experiences with MS11-011 and MS11-020.

    MS11-011 v6 works pretty well on my system. The only real issue that I've run across is that the drivers for my ATI Theater 750 PCIe TV card will sometimes freeze the computer when booting. Strangely enough, sometimes it will start working after rebooting a couple of times. I guess that is an improvement since the drivers didn't work at all prior to installing MS11-011. Other than that, my computer has been working fine and I'm able to run several applications without BlackWingCat's KDW pack.

    On the other hand, ZoneAlarm 7.0.483.000 does not like MS11-020 at all. It will blue screen right before the password prompt comes up.

    The error message I get is:

    ***STOP: 0x0000001E (0xC0000005, 0xB1720D9F, 0x00000000, 0x00000000) KMODE_EXCEPTION_NOT_HANDLED

    ***ADDRESS B1720D9F base at B16DC000, DateStamp 4874da4c - vsdatant.sys

    vsdatant.sys is part of ZoneAlarm.

  6. 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.

  7. Warning:  This sp rollout sometimes will make you loose your mapped lan file server connections. Much like kbb885250. It might have that one embeded.

    No might about it - it does have KB885250 (aka the bane of my existance).

    KB895900 is supposed to fix what KB885250 broke, but for some unknown reason, Microsoft has yet to make this fix public.

    Maybe it is a scam to get people to pay for $35 tech support calls. I gotta admit, I'm awfully tempted to give MS a call.

×
×
  • Create New...