bluebolt

Member
  • Content count

    200
  • Joined

  • Last visited

Community Reputation

17 Good

About bluebolt

  • Rank

Profile Information

  • OS
    Windows 2000 Professional
  • Country

Recent Profile Visitors

184 profile views
  1. I’m sick of Windows 8.x-10, and I don’t even run the meddlesome s***. Sorry to interrupt your XP discussion, but this is important. It's not, by the way.
  2. Thanks kikuk, I’ll keep your solution in mind, I may need it. In the meantime, on the (only) one of seven machines so far that have had this problem, I’ll simply hide those updates for now (to disable the yellow shield), and save this instance for possible later further testing.
  3. While .NET Framework Service Pack 2.0 is listed in Add/Remove Programs, it is not available to uninstall. The manual method discussed here is only for XP SP2: https://support.microsoft.com/en-us/kb/908077
  4. Last time it happened I could uninstall .net 4, then reinstall it, then let Windows Update do its thing--problem solved. Unfortunately this time it’s .net framework 2.0, which I can’t uninstall.
  5. I’m using the yellow shield method, though I’ve tried it with the browser as well (no difference). Last time it happened, I also tried downloading the updates and running them manually. Over the years I’ve often experienced the yellow shield reappearance after running all updates on a machine, but in those instances the yellow shield will subsequently show up only once again in the tray, and when I click it to install it vanishes, never to be seen again.
  6. This month’s .net framework updates have, once again, produced a reboot loop here. Specifically, the five 2.0 updates are installing (along with the others) fine, then the yellow shield reappears, I reinstall the updates, the shield reappears, ad nauseam. KB3123055 KB3127223 KB3135986 KB3142027 KB3163248 This happened in April, but only affected, as I recall, two of ten machines. So far, one of three machines affected by these July updates.
  7. Since these nVidia drivers are modified XP drivers (rather than, say, Vista drivers), I would try max compatibility.
  8. Just out of curiosity, have you tried KernelEx v2.6d? I tried the initial 2.8 version a while back, and it wrecked the OS. Also, when you installed the extended kernel, did you use the maximum compatibility settings (NT5 rather than NT6, and 5.81 rather than 5.82)?
  9. Besides his blog, there are other nVidia driver versions available through BWC’s “Windows Legacy Update” page (step 1: click “manual update” on the left): http://w2k.flxsrv.org/wlu/wluen.htm FYI, when trying blackwingcat’s nVidia drivers, you can extract the ZIP file and locate nv4_dispi.inf open it with Notepad, and use the “Edit / Find” feature to search for the card you’re using (e.g. GTX 560) to confirm compatibility.
  10. Correct, you don’t want to “reinstall” the USB drivers the OS has chosen, because those don’t work--you want to manually direct Device Manager to the other USB drivers. Device Manager will give you a number of choices to try. I think you can get your mouse working, too. It is a frustrating process with multiple steps; expect some trial and error, e.g.: http://www.msfn.org/board/topic/173698-windows-2000-professional-on-the-z97-platform/?do=findComment&comment=1100721 EDIT: I missed your second edit--sounds like you have your mouse working, as well? If so, excellent! You can now move back to a USB keyboard, if you wish.
  11. You are experiencing a problem that has existed for W2k Pro on the last several generations of hardware. I have worked through this on Z77, Z87, Z97 and X99 platforms; the corrective steps vary with the hardware (including the mouse being used). The solution is to use your PS/2 keyboard to enter device manager, and from there to install the USB drivers manually (the necessary drivers are already present on your machine).
  12. The updates do not need to be modified. Instructions for doing what you want to do are, roundabout, here (scroll down to OnePiece Alb post): http://www.ryanvm.net/forum/viewtopic.php?t=6438&postdays=0&postorder=asc&start=3250
  13. I re-tested using 22.0.0.147 (from Chrome Portable Dev) and checking the Flash site, and can confirm that both pepperflash dlls must be replaced in order to achieve update in Chrome portable.
  14. The flash dll is in two places in Chrome Portable: GoogleChromePortable\App\Chrome-bin\49.0.2623.112\PepperFlash GoogleChromePortable\Data\profile\PepperFlash I have been updating both, not sure if the latter is required. EDIT: The Flash site shows that indeed 21.0.0.240 is installed. But when I typed “Chrome://components/” and Enter in URL bar, it showed: pepper_flash - Version: 21.0.0.216 which it arrived at apparently just by reading the name of this folder: GoogleChromePortable\Data\profile\PepperFlash\21.0.0.216 as evidenced by the fact that by merely renaming the folder to 21.0.0.240, the “Chrome://components/” now shows the correct version as well.
  15. File not found