sdfox7

This is a long thread. Am I missing something? I installed the install_flash_player ppapi.exe and got confirmation that it was installed, but when I go to the Adobe test page (http://www.adobe.com/software/flash/about/), it is still showing the original 21.0.0.213 that installs with 49.0.2623.112. The Flash plugin for Internet Explorer and Firefox install without any issues.

I suspect that this is actually not limited to IE 8, but old versions of IE in general. On Windows 7 Enterprise with IE 9.0.46, I did a quick search for IE 9 compatibility mode: https://support.microsoft.com/en-us/kb/2536204#!%2Fen-us The link loads correctly in Chrome, but not in IE 9. I think that Microsoft has begun blocking all old browsers, in conjunction with its decision to drop old browser support on 1/12/16. I should note that the CT State University System has decided to stick with IE 9 instead of 11- I assume IE 11 loads these sites without a problem since that is Microsoft's latest version. The system also added Chrome to installed programs last fall, so it's possible they kept IE 9.0 around for compatibility reasons.

Dave Have you tried restoring IE to its default settings? I do know for a fact that Frame worked well with IE 6 on many websites just a couple of years ago. I find it hard to believe that web developers would have removed the code this quickly. http://answers.microsoft.com/en-us/ie/forum/ie8-windows_other/no-error-code-the-webpage-cannot-be-displayed-most/64bde1cb-3dad-447e-9d39-022070f88cd3

Yes, Windows ME shipped with IE 5.5. The latest version was IE 6.0 SP1.

I forgot to address your VLC issues in my post. In my own experience, VLC 0.8.6a through 0.8.6d were the only versions I could get working trouble free on Windows 95 and NT 4.0. The newer 0.8.6x versions gave me problems (e through h). A major problem with NT 4.0 is that there are no newer versions of DirectX versions available unless you resort to unofficial versions. This may be causing you problems that I never experienced with Windows 95. Windows 95 supported USB (to a degree) and DirectX all the way to version 8 (DX80ENG.EXE). It also supported the latest versions of Windows Media Player, and AOL, 7.0 (SETUP9X.EXE), at a time when AOL ruled the world. These, among other reasons, made it a more desirable system for home users, even if it was a little less stable than NT.

Can either of you try installing Google Chrome Frame, and let me know if that fixes the issue for you? I have had great luck using old versions of IE with Frame installed. I am currently on a Windows 7 Enterprise system at school and cannot check at the moment. http://dl.google.com/chrome/install/GoogleChromeframeStandaloneEnterprise.msi (if that link fails for some reason try http://sdfox7.com/xp/sp3/GoogleChromeframeStandaloneEnterprise.msi )

http://nt4ref.zcm.com.au/usb.htm Firefox 2.x is still a bit more useful than IE 6, the final 2.0.0.20 release is 7 years newer.

The wireless card likely isn't working because 1) the Intel 2200 with the D610 is too new- you need the 2100 which has NT 4.0 driver support. You may find it on eBay (http://www.ebay.com/sch/Internal-Network-Cards/20318/i.html?_from=R40&_nkw=intel+2100) My ThinkPad T40 had the same network card, the drivers for NT 4.0 are here: http://sdfox7.com/ibm/t40/t40_nt40/wireless/inwi1tnt.exe You also need PCMCIA support. NT 4.0 has rudimentary support for PCMCIA. You will want to install CardWare (http://sdfox7.com/nt40/CARDWARE.ZIP). When you install, select "Unknown PCIC laptop". After installing the wireless driver, you need to install TCP/IP networking. This must be done after installing the card driver because networking will be looking for the card to configure it. Here is a good article from 1997 explaining the networking process on NT 4.0: http://www.windowsnetworking.com/articles-tutorials/windows-nt/nt4netin.html For Internet Explorer 6.0 Service Pack 1 for NT 4.0, I have it here: http://sdfox7.com/ie/win32/IE6SP1NT.ZIP I had some old notes here for setting up NT 4.0 on an old Gateway Solo 9300: http://sdfox7.com/solo9300/winnt/wifi.txt You'll want to install the "updated" common controls (50COMUPD.EXE) and libraries update (SPEU.EXE). Both of these are nearly 20 years old but you'll still need them for the wireless configuration operation. Once you install IE6, you will find it too old and useless. I would install Firefox. More info here, I wrote it for Windows 95, but the same info applies to NT 4.0: How to run Mozilla Firefox 2.0 on Windows 95

I tried loading https://www.microsoft.com/en-us/download/windows-media-player-details.aspx and it failed with IE 8. However, changing "https" to "http" allowed the page to load in IE 8.

Seems like a bunch of hoops to jump through, when Adobe/Google should simply write the code correctly. Non-technical people will be stuck on 22x209 unless the problem is fixed in the future.

Installing the above file did not change the installed version on my system. As I quoted above, Google has detected an incompatibility with the PPAPI Flash 23 and Chrome 49 and has blocked distribution. https://productforums.google.com/d/msg/chrome/Wxv-K1nnztk/dtd6xkzHAgAJ

It's important to note that while Windows ME came out after both Windows 98SE and 2000, it is still based on the older Windows 9x model. Most software I ever came across would run on Windows 95/98/ME. (with the exception of Internet Explorer 6, which excluded 95) I think the support issue came down to the fact that ME was like Vista, it was released quickly, and killed off by Windows XP less than a year later. There was no time for it to gain market share, that could have compelled vendors to support it longer. The system requirements included a 150MHz processor, what a joke. In fact, I didn't enjoy running Windows 95 on anything less than a Pentium II or newer with 64MB RAM.

Windows XP is still a relatively up to date system, despite what Microsoft and tech pundits would have you believe. I can still update/backup my iPhone 6S with iTunes 12, although I typically do it over WiFi. Security experts will tell you that XP is no longer secure because it is not being patched, which is true to SOME degree. However, the way I see it, it is no worse than using Windows 7/8/10 with unknown vulnerabilities that have not yet been patched. Also, Windows 7/8/10, with market share that is much larger than XP, will be a bigger target. Microsoft will always be one step behind, playing whack-a-mole to fix vulnerabilities in its software. It is reactive, not proactive. Don't forget that Windows 7/8/10 will have vulnerabilities that don't affect XP since the code continues to change and does not exist in the XP operating system. This has already occured with Windows 95 and 98; the DOS-based systems are "incompatible" with the viruses that affect NT systems! Firefox support will continue to receive updates through mid-2018 with Firefox 53 ESR, and Opera 36 is still being patched for the time being. For the average user that browses the web and does office work, the system still gets the job done.

Update: Adobe Flash Player has been updated to 23.0.0.185 on October 11, 2016. You can read the security bulletin here: https://helpx.adobe.com/security/products/flash-player/apsb16-32.html The Internet Explorer ActiveX plugin is available here: http://fpdownload.adobe.com/get/flashplayer/pdc/23.0.0.185/install_flash_player_ax.exe The NPAPI for Firefox is available here: http://fpdownload.adobe.com/get/flashplayer/pdc/23.0.0.185/install_flash_player.exe Please note: The Internet Explorer plugin only appears to function under Internet Explorer Compatibility Mode. When I tested under regular browsing mode in Internet Explorer 8, the plugin did not execute.

If you are running Server 2003, is it the 32-bit version, or 64-bit version? The official driver for XP 64 bit and Server 2003 64 bit is here: http://www.geforce.com/drivers/results/105041 The official driver for XP 32 bit and Server 2003 32 bit is here: http://www.geforce.com/drivers/results/105040 (there is no Server 2003 32-bit driver)

Just an update: M-Vargas, STAFF at Adobe, says the bug has been assigned to a developer. As the ActiveX and NPAPI control still work, the recommendation is to use Firefox with the NPAPI control, or Internet Explorer with the ActiveX control. Adobe has not dropped support for XP, so it is not an XP problem. Since the bug has been assigned to a developer at Adobe, it appears that Adobe supplies the pepflashplayer.dll to Google? You can continue to get the 22.0.0.209 from my FTP. Re: Flash PPAPI plugin 23.0.0.162 doesn't work in Opera and Chromium

What I find interesting is that many of these developers claim they need to strip the legacy code, all in the name of keeping install package sizes at a "manageable" size. It's an ironic argument because, if anything, new programs just keep increasing! The XP code in these programs likely adds a negligible/trivial amount to the size of these programs. None of these programmers are going to reduce their program size from 11,000 to 1,000 lines just by removing XP code. Granted, that article is years old, but it is relevant in terms of efficiency. Over the last several years, I have watched Microsoft Office and Adobe Reader grow to monstrous sizes without any discernible (in my eyes) increase or improvement in performance. Microsoft, and others, do not understand the following concept: by removing compatibility in newer products, it keeps people on older products with the compatibility!

Firefox is open source software, so I'm sure there will be someone that ports 53+ to XP and Vista. This is what we saw with TenFourFox; when Firefox dropped support for PowerPC Mac's, someone created a branch.

According to this thread, MSE was designed for use strictly on consumer OS such as Windows XP, Vista and 7. That being said, people have succeeded in installing the XP version on Server 2003. "Technically" it can be installed but is unsupported. Since XP 64 is based on Server 2003, it would probably work. However, you'd probably need the final XP version 4.4.304, and I think you'd be stuck with the 32-bit executable because Microsoft never provided an XP 64 executable. I am providing the Internet Archive's link for the 4.4.304 version from November 21, 2013. I hope this is helpful; as far as the current Vista/7 version, you'd have to actually try it; I don't have a Server 2003 setup handy to test the Vista/7 executable.

For future reference, for newer machines I always usually had to install the "Microsoft Universal Audio Architecture (UAA) Bus Driver for High Definition Audio" because XP does not include this. HP's version can be found here. It probably doesn't matter if you use the driver on a non-HP machine. http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_45958_1

Just to let you know, the Windows 95/NT Windows Update was taken offline over five years ago. The original page was http://windowsupdate.microsoft.com/Static_w95/V31site/default.htm If you are running plain NT 4.0, you can access the updates here: ftp://ftp.uni-rostock.de/pub/tools/microsoft/ServicePacks/NT40/us/

This page has updates. If you are using Chrome the page may fail to load correctly or display an empty directory. In that case, use Internet Explorer or try Firefox. ftp://ftp.uni-rostock.de/pub/tools/microsoft/ServicePacks/NT40TSE/us/

Please see my post here from May 10, I succeeded in getting WPA2 to work on Windows 2000. Most access points including the Apple iPhone only provide WPA2 signal because it is more secure. WEP is obsolete and many points do not provide this access anymore.

I wouldn't worry too much about this. It's important to note the wording "support", which is quite different than "won't work". After all, we have had ways of running unsupported versions of Firefox on Windows 95 (only 1.x was officially supported) and 2000 (was dropped at 12, but it is possible to run later versions). How to run Mozilla Firefox 2.0 on Windows 95 Firefox 13+ in Windows 2000 (forums are currently offline for maintenance, so I have posted the cached version- the original link is http://forums.mozillazine.org/viewtopic.php?t=2482475)

Just wanted to note that on Google Groups, Anthony Laforge has posted that Chrome 49 is being blocked from further Flash updates due to an "incompatibility": https://productforums.google.com/d/msg/chrome/Wxv-K1nnztk/dtd6xkzHAgAJ I'm not really sure he means. The ActiveX and Firefox/Opera plugins of Flash 23 work correctly, so I'm not sure what would keep the PepperFlash version from working.