sdfox7

I noticed a few days ago that Adobe was getting close to releasing a new version, because Google Chrome Portable 51 Beta includes it, and while Chrome 51 cannot currently run on XP, it is easy to extract the files and locate the updated pepflashplayer.dll. Chrome 52 Developer already includes Adobe Flash Player 22 (22.0.0.137) Users running Windows XP and Vista should download the updated pepflashplayer.dll (also available here and here) and place it in / save it to the following Chrome PepperFlash folder: C:\Program Files\Google\Chrome\Application\49.0.2623.112\PepperFlash

As CamTron noted above, there were models of D-Link AirPlus that support it, and this YouTube video proves it: WPA2 on Windows 98SE ;) As KippyKip noted above, Windows 98SE works with the Netgear WG111v2 USB but apprently bluescreens. I would think there is some type of configuration issue or it's just a lemon USB there, because it's unlikely Netgear sold a bad product consistently. The Netgear WG111v2 USB 54 was one of the latest Windows 98SE compatible wireless network devices that was released after Windows 98 support was winding down. It is WPA2 compatible, so it would be a good place to start. No guarantees on Windows 98. I bring this up because this model was widely distributed at retailers such as OfficeMax, Staples, WalMart, RadioShack, etc. The latest driver is 4.0.0 and supports all operating systems from Windows 98 through Windows 7: WG111v2 Version 4.0.0 WG111v2 Version 4.00 (supports Win 7) Released: Jun 23, 2010. Supports Windows 7 (32/64 bit) driver version:62.1310.402.2010 Supports Windows Vista (32/64 bit) Win Vista x86/x64 driver version: 6.1308.1226.2007(WHQL certified, Works with Windows Vista) Win 2000/XP/XP-x64 driver version: 5.1308.1226.2007 (WHQL certified) Win 98SE/Me driver version: 5.1308.1226.2007 Utility version: 1.0.0.185 http://www.netgear.com/support/product/WG111v2.aspx?cid=gwmng#Software%20Version%204.0.0%20for%20Windows Direct Download: http://www.downloads.netgear.com/files/GDC/WG111V2/WG111v2%20Software%20Version%204.0.0.zip (you can access this file in the future by simply pasting the link in the WayBack Machine aka Internet Archive: http://archive.org)

By spoofing the browser and manually extracting the updated Flash Player ( pepflashplayer.dll ) from Chrome Portable, it is possible to keep Chrome 49 going for a while. I've already showed above how to spoof the browser with the current version number. To keep flash up to date: when Google announces a new version of Chrome, I simply download the Chrome Portable version and manually extract pepflashplayer.dll. I then copy it to the Chrome directory C:\Program Files\Google\Chrome\Application\49.0.2623.112\PepperFlash Web standards generally haven't changed all that much, so for now this solution could work for many years. Of course, there's always Firefox, SlimJet, Opera 36.x, Pale Moon, etc. In Portable Chrome 51 Beta, Flash Player 21.0.0.240 is already available:

I am pleased to announce that I have finally gotten WPA2 working on Windows 2000, thanks to all of your input. You simply need to install a compatible adapter with Windows 2000 driver (mine is a RTL 8188/8192 802.11n), then install Boingo wireless client, which appears to be the only client that supports WPA2 under Windows 2000! I tested it on my Pentium 3 laptop and had no issues connecting! http://web.archive.org/web/20070407064532/http://www.boingo.com/download_windows.html click th e box and then Begin Download!

For now I am simply spoofing the browser to emulate Chrome 50. Many websites block old browsers for no legitimate reasons, so I used Chrome's built in developer tools to manipulate the string from Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 to Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 I'm "running Chrome 50 on Windows XP!"

ATI/AMD Catalyst 14.4 covers a large range of desktop hardware for Windows XP. It was released in April 2014 and appears to be the most recent package for the XP operating system. This is probably a good package to start with if looking to backport XP compatibility. Features: http://support.amd.com/en-us/download/desktop?os=Windows%20XP%20-%20Professional/Home&RenderOnServer=true Supported products: http://support.amd.com/en-us/download/desktop?os=Windows%20XP%20-%20Professional/Home&RenderOnServer=true#2

In XP and Internet Explorer 6.0 SP3, I go to Tools --> Internet Options --> Content Tab --> Certificates

Dave, here is a perfect example of why TLS tends to work better than SSL: My school uses Office 365 for web based email. With SSL enabled (IE 6.0 default) I cannot even load the page; with SSL 2.0 and 3.0 disabled but TLS enabled, I can load it no problem:

The following link explains how to force Google to load in non-SSL mode. I'm not sure if it possible to load Advanced Search in non-SSL mode. How force Chrome to use google.com search engine without https The resulting webpage is indeed non-https: http://www.google.com/webhp?nord=1

The only way to load Google on IE 6.0 is to use at least XP with SP3, or on older systems to install an old version of IE, such as 5.5 or lower, which include SSL 2.0, not SSL 3.0. By installing an old version, it forces Google to serve a non-SSL page. My NT 4.0 system loads Google in IE 5.0 with no problem. SSL worked on the IE 6.0 until POODLE hit; then webmasters started removing support for ("blocking") SSL 3.0. SSL 2.0 is unaffected. https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility

It appears that the error, at least on Vista and Server 2008, is that (https://support.microsoft.com/en-us/kb/942959) "By default, when you start or reset PCI Express bridge devices, the initial values of the limit register for the bridge resource window are less than the initial values of the base register for the bridge resource window. Windows Vista and Windows Server 2008 interpret this behavior as an indication that the bridge resource window is disabled. and Additionally, Windows Vista and Windows Server 2008 do not generate any bridge resource window requirements for the PCI Express bridge device. Therefore, any PCI Express bridge device that requires resources from the bridge resource window will fail enumeration. In this situation, a Code 12 error is generated." There are workarounds, but I don't know if they would work on Windows 2000, or even XP.

Many companies continue to pay for extended custom support on XP and Server 2003. Continuing definitions may have been part of the deal. The other possibility is that keeping the updating mechanism and infrastructure intact is a trivial thing to do. Both of my hypothetical answers are purely speculative, but seem reasonable.

I have noticed that Windows 2000 requires the Update Rollup in order to avoid Bad Pool Caller 0x000000C2 errors, particularly while running web browsers such as Firefox and Opera. For example, opening washingtonpost.com on Windows 2000 SP4 without the rollup will result in a BSOD and system reboot. I have an related question, but believe starting a separate thread is unnecessary: Do you know if any of your tools/unofficial service packs can enable Windows 2000 to use WPA2? Windows XP SP2 simply requires KB893357 installed. Is there a way to port this to Windows 2000? Windows 2000 is still a fantastic and useful system, but I am limited to using it only on my home and free public hotspots, because I am unable to get it working on a laptop with WPA2.

You may find my archived AOL for Mac OS X useful. AOL has a built in client, and you should be able to sign in for free using a TCP/IP connection: http://sdfox7.com/macppc/AOL_for_Mac_OS_X.dmg It has been years since I've used that program on a PowerPC Mac, and I do not recall what version of the program it is. It's probably 10-15 years old.

July 14, 2015 (7/14/2015) is the same date that Windows Server 2003 went end of life (EOL). Windows Server 2003 shared XP's code base. It appears Microsoft made the EOL for Security Essentials coincide with Server 2003's EOL.

I moved my domain to Hostgator in 2011. I don't recall my registrar immediately prior, but in the earlier years I was using AOL Hometown (members.aol.com/sdfox7) which has since been shut down for several years. With HostGator I have never had any uptime issues and have 100% availability anytime I accessed my site. No advertising. If you are interested, I could probably add your .tk domain to my account. I already pay for the hosting package, so it's simply a matter of the $15 annual renewal.

The AMD Athlon 3200+ was released in May 2003, just after the March 2003 launch of my laptop, the ThinkPad T40, which was IBM's flagship and came equipped with the then-new Pentium M. At that time, the Pentium M was the flagship of the Intel mobile line, and likely the best laptop processor you could probably have at the time. Compared to the Pentium M, the Athlon 3200+ was missing SSE2 instruction and only had half the L2 cache of the Banias Pentium M; Dothan had not yet been released, until September 2003. It appears that AMD has been consistently late to the game with forward-thinking/future-proof technology. At least it's been this way in the past.

I am not concerned about Chrome 49 being the last version for XP. We all know the rapid-release cycles have become ridiculous, and at this point next year there will be Chrome version 2,017. The functionality of many old browsers is still quite good. As this thread focuses on Chrome, any version that supports HTML5 should perform reasonably well, which probably includes any version of Chrome >30. Keep in mind that Chrome 34.0.1847 is the final version for non-SSE2 processors (Pentium III, Pentium II, etc). All later versions require Pentium 4 or newer, which contain SSE2 instructions. Not to mention that you may be quite limited on today's web with such an old machine, depending on your desires. There are many fantastic alternatives to Chrome (like Firefox), and worst case scenario, you could simply spoof the Chrome agent to make it report Chrome 50 (5x). Many websites block you only because of your user agent, not because of any inherent flaw or limitation of the browser.

The archived Chromium versions are officially stored here, however, they are not stored in any form of common rhyme or reason. It took me quite a while when I finally found the last SSE-compatible version of Chromium 34 here. You can get the archived versions more easily here: https://chocolatey.org/packages/chromium Specifically, 49.0.2598.0 is here. Chromium continuous build is no longer updated.

I was thinking you might have more luck using Windows Server 2008 R2, based on Windows 7. Windows Server 2012 is based on Windows 8.x and may be too new with multiple incompatibilities, other than those you have posted here.

Java has been updated to Java 8 Update 92: http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html http://www.oracle.com/technetwork/java/javase/2col/8u92-bugfixes-2949473.html

I missed this post at the time, but then realized that someone on Ars Technica also cited this as a good browser based on Chromium. It apparently syncs all Chrome settings while continuing XP and Vista support. http://arstechnica.com/gadgets/2016/04/chrome-50-ends-support-for-windows-xp-os-x-10-6-other-old-versions/?comments=1&post=31026417#comment-31026417

When opened with Hex Editor, there are clearly differences between the Chrome 49 and 50 installers. I still believe there are artificial limitations placed here. How do I find the value that is calling GetThreadId and remove this API call? Top windows is Chrome 49 installer, bottom window is Chrome 50 installer.

I understand this. What I intended to say is that previously, all versions of Internet Explorer for a platform were supported until the platform itself lost support. Now, Microsoft has changed policy so that only the latest version of Internet Explorer on a platform is supported. Internet Explorer 5.0 received support until 2010 because Windows 2000 was still supported until then, and Internet Explorer 6.0 received support until Windows XP reached end of life in 2014. Now, Windows Vista is still supported, but Internet Explorer 7.0 and 8.0 are not supported on the platform; they would have under the previous policy. The situation is the same with Windows 7, which shipped with IE8 and can run IE9 and IE 10, but none of those browsers are supported any longer. I am not including non-consumer versions such as POS.