• Content count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About AnX

  • Rank
    Fighting for the right to OS since 2010
  • Birthday

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

1,081 profile views
  1. I have a feeling this would be more appropriate on the XP forum, but regardless, it had to do with it popping up some strange storage related errors. Even updating AHCI drivers did nothing. I'll install XP again as a secondary OS and see if I can get it working the next time around.
  2. I was starting to like Windows 10. But some caveats have caused me to go back to Windows 7. 1. For some reason, when I go to open my folder with all my documents, Explorer would crash. 2. Windows 10's updating system was horrible. Because my Internet is limited, I need more control on how Windows 10 downloads its updates. But when I go to do that, it decides to just sit there and use up 30% of my CPU doing nothing. 3. Who knows how much data was being siphoned out... however I haven't really recorded any significant signs of that happening. 4. Compatibility with older programs is quite subpar. Anyway, that's just me. I'm pretty sure Windows 10 has been working for many others, but I'm gonna wait longer. 'Till then, 7 is a solid OS.
  3. Thanks for the heads up, BWC. It's really a shame how MS let Windows 2000 to die off. The fact that they claimed 2000 had an issue which was fixed just so they could sell more copies of server 2003 is downright misleading. Furthermore, I'm relived that Windows 2000 supports high cache CPUs, as I run it on an FX-8320 box because of my 26 year old compiler that hates modern OSes (and virtual machines). I would run XP, but XP simply produced issues of all sorts on that machine for whatever reason. Also, I must clarify that the BSOD only happened while installing a sketchy HPET driver. My simple solution is to simply disable the device altogether, and Windows 2000 runs solid as a rock. Additionally, my AFD.SYS is version 7204, the fixed version.
  4. You'll be able to run Windows 10 x64 on your machine just fine. These are the drivers needed for your graphics unit.
  5. The issue with Win2k's MPS HAL is well documented, and typically happens in the following scenarios: -Certain BIOSes (such as "insydeH2O") -Conflicts with the Serial/Parallel port (this was documented by bluebolt and could actually fix your problem, if you have a way to disable those ports) It's unknown why Win2k (and NT4)'s MPS kernels do this, however you gotta understand that they were built for multi processor systems years ago. Perhaps a change in how Windows XP recognizes processors is what fixed the issue for that OS. Nonetheless, Win2k does end up supporting most MPS/Multi-core systems, provided that they are either desktops (custom built ones in the case of modern units), or laptops prior to 2008 (some 2011-2012 ones support Win2k, but it varies). Even though it's probably too late to ask, I'd love to see a fix up of the Win2k MPS HAL to repair these issues, and possibly even bring in proper HyperThreading support. It's a long shot and likely not even worth it for this OS, but it would be interesting to see the result.
  6. I was browsing the web, and came across an article which points to a flaw under Win2k that could cause it to BSOD with the 1E error "under a processor that is very fast or with a large L3 cache". So, I was wondering if anyone over here has actually experienced this anomaly with Win2k. I will admit that I got some KMODE_EXCEPTION_NOT_HANDLED errors on my FX-8320 when I tried to install an HPET driver, but without it, Win2k runs solid there.
  7. I just used the latest one made by blackwingcat. Works fine.
  8. Any chance of getting GTA V running on XP x64 edition with this? According to Dependency Walker, GTA5.exe needs kernel32 WerSetFlags and GetSystemDefaultLocaleName GTAVLauncher.exe and PlayGTAV.exe need kernel32 QueryFullProcessImageNameW , GetTickCount64 and GetUserDefaultLocaleName and shell32 SHGetKnownFolderPath Some DLL files such as IESHIMS.DLL and WER.DLL are also needed.
  9. Firefox crashes if I use it with Extended Kernel v.2.8d. 2.6d is the last version that worked flawlessly for me.
  10. No, nVidia still makes GeForce cards. ASUS is just a (very vocal) nVidia partner, which may be the reason you made such an assumption.
  11. I haven't had any issues with Windows 7 x64 vs the x86 version, but i do know that the former has better support for newer and more powerful hardware, so that's what I use.
  12. You could put in a lower power CPU along with an SSD into that PC, which should result in lower power draw. I say its worth a try.
  13. Nope, the one you put up for download recently on RyanVM.
  14. Dibya, attempting to slipstream your addon in with Windows XP SP4 causes this BSoD This was done in VMware workstation 12. Any solution?
  15. Problem when slipstreamed with Dibya's Windows XP 4GB RAM limit breaker. In VMware, install seems to go fine, then come across a peculiar BSoD I really want to slipstream his addon as it cannot be installed after setup. Any way to fix this?