Leaderboard

Introduction: Here, you will find a list of AMD/Intel CPUs/chipsets and Intel/NVIDIA/AMD GPUs which support Microsoft® Windows Vista™. If you have any additions that aren't currently listed, feel free to reply with them and they will be added as soon as possible. Supported CPUs: Intel (Desktop/Server): Note: Windows Vista has been known to work with Pentium III and even some Pentium II processors, however this configuration is extremely suboptimal and the OS is practically unusable on these processors, so using at least a Pentium 4 (Prescott), plus installing Windows Vista Service Pack 2 is recommended for acceptable performance. Intel Pentium 4 (Prescott, 2004-2005) *x64 is only supported from the Pentium 4 505 Processor and newer Intel Pentium 4 Extreme Edition (Prescott, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Northwood, 2003-2004) *x86 only Intel Pentium 4 HT (Prescott, 2004-2005) *x64 is only supported by F-series, 5x1, 517, 524 and few OEM models in E-series (SL7QB, SL7Q8) Intel Pentium 4 HT (Prescott 2M, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Cedar Mill, 2006) *Supports both x86 and x64 Intel Pentium D & Pentium Extreme Edition, all models Intel Celeron, all Netburst-based models (Williamette & Northwood-128, 2002-2003) *x86 only Intel Celeron D (Prescott, 2004-2005) *x64 only supported by 3x1, 3x6, 355 models Intel Celeron D (Cedar Mill, 2006-2007) *Supports both x86 and x64 Intel Celeron *all Core-based and newer models up to Ivy Bridge based Celerons; Braswell/Haswell and later do not properly work with Vista. Intel Core 2 Duo, all models Intel Core 2 Extreme, all models Intel Core 2 Quad, all models Intel Pentium up to Sandy/Ivy Bridge G series processors; Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Xeon 1.4 "Foster" - Intel Xeon 3.2 "Gallatin" *x86 only Intel Xeon, all models from 2.8 "Nocona" to 3rd generation Ivy Bridge Xeon processors; Haswell and later do not properly work with Vista. Intel (Mobile): Intel Pentium M, all models *86 only Intel Pentium 4-M, all models *x86 only Mobile Pentium 4, all models *x86 only Mobile Pentium 4 HT, all models *x86 only Intel Atom *all models up to Bonnell microarchitecture (2012); Silvermont (2014) and later may not properly work with Vista (not yet tested). Intel Core Solo, all models Intel Core Duo, all models Intel Core 2 Solo, all models Intel Core 2 Duo, all models Intel Core 2 Quad, all models Intel Core 2 Extreme, all models Intel Pentium up to Sandy/Ivy Bridge mobile processors, Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. AMD (Desktop/Server): AMD Athlon 800 - Athlon 1000 (Pluto/Orion, 2000) *x86 only AMD Athlon 800 - Athlon 1400C (Thunderbird, 2000-2001) *x86 only AMD Duron 800 or later (2000-2003) *x86 only AMD Athlon XP, all models (2001-2003) *x86 only AMD Athlon 64, all models AMD Athlon 64 X2, all models (X2 & K10) AMD Phenom, all models AMD Opteron, all models AMD Sempron (Palermo, Socket 754; July/August 2005) *x64 only supported by all models with an OPN ending in BX and CV) AMD Sempron (Palermo, Socket 939; October 2005) *x64 only supported by all models with an OPN ending in BW AMD Sempron "Manilla" or later, all models AMD FX (Bulldozer Family), all models AMD Ryzen (all Summit Ridge models; Raven Ridge has yet to be tested) AMD (Mobile): AMD Mobile Sempron, all models (2003-2006) *x86 only AMD Mobile Athlon 64, all models (2004-2005) AMD Turion 64, all models (2005) AMD Kite Platform - AMD Carrizo Platform, all CPUs & APUs (2006-2015); Bristol Ridge (2016) may work but has yet to be tested. Supported GPUs: Intel GPUs: Intel 915GM/GMS will work with Windows Vista by using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. Intel GMA 950 (Desktop: 945GC, 945GZ, 945G; Mobile: 945 Family) or newer, last Intel GPU to support Vista is Intel HD 4000 series (Ivy Bridge; Desktop and Mobile). Download Intel HD 4000 Graphics Drivers for Vista: 32 bit - 64 bit ATI/AMD GPUs: ATI Radeon 9250 and all later GPUs released prior to the 9500 will work with Vista using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. ATI Radeon 9500 or later; last AMD GPU to support Vista is AMD RX 300 series; drivers are coming soon. The first official version of ATI Catalyst to support Vista is version 7.1. The last official version of AMD Catalyst to support Vista is version 13.12 (Download: 32 bit 64 bit). However, newer versions up to 15.6 Beta for Windows 7 can be modified to work on Vista. View this thread for more details. NVIDIA GPUs: NVIDIA GeForce FX 5100 and later NVIDIA GeForce 8 series to GeForce 300 series; download recommended driver here: 32 bit 64 bit NVIDIA GeForce 400 series and later; last NVIDIA GPU to officially support Vista was the GTX 980 along with driver version 365.19. Download here: 32 bit 64 bit - Note: Vista 3D Vision support was dropped around version 310.00. The GTX 1060, 1070, and 1080 can also be made to work with Vista, as driver versions up to 372.70 work with Vista, albeit not officially supported by NVIDIA. Download here: 32 bit 64 bit - Note: DirectX applications aren't properly utilized by these drivers under Windows Vista, so this will cause a bottleneck in performance over using the GTX 980 or older, where the 365.19 drivers (more optimized for Vista as they're officially supported) can be used. Final Apple Mac Computers to support Vista via Boot Camp: iMac; all Late-2009 models Macbook Air; all Mid-2009 models (32-bit only) Macbook and Macbook Pro; all Mid-2010 models Mac Mini; Mid-2010 (This is the only Mac Mini to support Windows Vista 64-bit; earlier models are 32-bit only.) Mac Pro; Mid-2010 Miscellaneous Hardware: Looking for an Xbox One Controller driver for Windows Vista? View this thread for download + how to install (HUGE THANKS TO @GTAGAME for this.) Download Elgato HD 60 S Capture Card drivers here - to install, extract the exe with 7-ZIP and manually install the drivers in Device Manager (thanks again to GTAGAME for pointing this out).

I installed the Windows XP Professional x64 operating system on a Samsung 970 Pro NVME SSD drive using an ASRock X99 Extreme4 motherboard. Really easy the second time. Download Kai Schtrom's driver here: https://sourceforge.net/projects/nvme-for-windows-2003-server/files/ Download KB932755 here: https://www.microsoft.com/en-us/download/details.aspx?id=11619 Download AOMEI Backupper Standard here: https://www.aomeitech.com/download.html Use diskpart in Windows 7 x64 to create the aligned partition on, and format, the NVMe drive (the Windows 7 OS must have an NVMe driver installed, or diskpart will not be able to see the NVMe drive). Use Device Manager in XP x64 to install Schtrom's driver, which makes the NVMe SSD available as a storage drive -- and the XP x64 operating system as such now includes the NVMe driver. Run the storport hotfix. Use AOMEI Backupper to clone the XP x64 disk to the NVMe disk (remember to align the partition). Reboot into the BIOS and set the NVMe drive to boot first. I don't know whether Kai Schtrom had Windows XP 64-bit in mind when he wrote his driver, but for those of you running that OS it does present the potential for significant performance improvement, to say the least.

The following code from Sky's e-mails uses Web Open Font Format (woff file), which is only supported as of IE9 and ensures long loading times. <style type="text/css">@import "//helpforum.sky.com/html/assets/toolkit.css";@font-face{font-family: "Sky Text"; src: url("//www.sky.com/assets/fonts/sky-regular.woff") format("woff")}@font-face{font-family: "Sky Text"; src: url("//www.sky.com/assets/fonts/sky-medium.woff") format("woff"); font-weight: bold}html, body, #MessageContainer{font-family: 'Sky Text', Arial;margin: 0;padding: 0;box-sizing: border-box;filter: progid: DXImageTransform.Microsoft.gradient(startColorstr="#c9c7d1", endColorstLOGNULL NowTransReader::ReadIt() JJFileMT::Truncate(122991) r="#fefefe", GradientType=1);background-image: -webkit-linear-gradient(left, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);background-image: -moz-linear-gradient(left, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);background-image: -o-linear-gradient(left, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);background-image: linear-gradient(to right, #c9c7d1 0%, #e5e5ea 6%, #fefefe 20%, #fefefe 80%, #e5e5ea 94%, #c9c7d1 100%);}.header-row{padding: 10px; -webkit-box-shadow: 0 1px 10px 0 rgba(0, 0, 0, 0.2); -moz-box-shadow: 0 1px 10px 0 rgba(0, 0, 0, 0.2);box-shadow: 0 1px 10px 0 rgba(0, 0, 0, .2);background-color: #fff;}<!--if[mso]>.footer-links table{float: left; width: auto !important;}<![end if]-->.footer-links table{float: left; width: auto !important;}.footer-links a:link, .footer-links a:visited, .footer-links a:active, .footer-links a:hover{font-size: 18px;} For e-mail programs such as Outlook Express and Windows Live Mail, where the Microsoft Viewer (IE) is used for viewing e-mails, the reloading of fonts can be prevented. At Eudora, I do not have this option, a suitable plugin for Eudora could provide a remedy, similar to an ad blocker where the code for reloading Web Open Font Format is removed. With the internal viewer of Eudora (HTML mails have problems with the reloading of pictures etc. with encrypted web server) there is no possibility to take over the proxy settings from the system (no use of HTTPSProxy possible), therefore the detour over the Microsoft Viewer (IE).

IMO, no. Eudora is one of the best (if not the very best) stand-alone e-mail client ever. So, now that we have a diagnostic of the problem, at last, it seems proper to pursue the actual solution in the same thread. Me, too. But if @jumper is willing to try and create a standalone wrapper library to be dropped in Eudora's folder (even if some local executables will have to be hexedited to redirect some calls to the wrapper) he sure has the expertise to do so. I think we should go for it.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190209-95988d7-uxp-4adc40988-xpmod.7z Browser-only Suite Win32 (removed due to request) source patch (excluding UXP): (removed due to request) Official repo changes since my last build: - [PLATFORM] Update commit pointer (0358bd0) - [PLATFORM] Update commit pointer (3903a16) - [INSPECTOR] Use main toolbar background for modern theme (11dc15b) - [PLATFORM] Update commit pointer (68c6dd6) - [ABPRIME] Change menu order for Navigator (adebcea) - [PLATFORM] Update commit pointer (0cb0749) - [PLATFORM] Update commit pointer (e55019d) - [MAIL] Update proxy prefpane for changes in https://github.com/MoonchildProductions/UXP/commit/6567bb631a78033b6b4cc32bc93e07d837652276 (95988d7) For UXP changes please see above.

Thank you. Many years ago I began archiving MS-DOS, Windows 3.1, and Windows 95 resources that in my opinion were increasingly becoming endangered but that were of historical significance. I eventually uploaded these online in 2011 as many of these resources are extremely rare and cannot be replaced. Having this stuff backed up with server redundancies and failover is a safer method of preservation. Some of the original links online for this softwareare dead (even with the wayBack Machine) which is where my site comes into play. I didn't want my physical media to be the only source, particularly since physical media tends to degrade over time. That gradually grew into numerous directories for NT 4.0, 98, 2000, and XP. I generally skipped ME and Vista as I was not fond of either OS. I think that people should have complete unfettered freedom to use the software they know and love. If it does the job it was intended to do, it's not obsolete. I don't think people should be forced along by "planned obsolescence" or by corporations whose interest is to make money.

Been a while since I posted one of these, but anyway here it is... SUMMARY OF CHANGES TO THE LIST FOR FEBRUARY 1, 2019: Added MailNews by roytam1 to "E-mail Clients" section. Removed Dropbox from "Cloud Storage Clients" section, as new versions of the software will no longer install in Windows Vista and older versions will no longer connect to the Dropbox service from my testing. Added Steam (Jan 4, 2019) build as the last version for Windows Vista, along with information on how to prevent the software from automatically updating (resulting in Vista compatibility loss). Added AssaultCube to "Games" -> "Active Development" section. Added EditPad Lite to "System File Viewers/Editors" section. Hope all the XP/Vista users have continued to make use of my list. Sorry about not being too active lately.

Remember that spoofing only will cause the site to make available code specific to the browser you are identifying as. It all depends on how the site is written. Identifying as another browser or application does not magically give your browser the ability to do the things the other software is capable of. If they are adding some code that doesn't work in older versions of Firefox, even if they don't put in a version checker, the page may not work properly because your version can't execute the code. As noted, it is impossible to tell what the results will be until that site updates their site, only then would you know if changing your user agent will make the page work or not.

Hmmm. Let me see. Under Windows everyone uses Chrome or Chorome/Chromium engine based browser. (exception made for those insisting on using Mozilla Firefox, all in all a small amount of people [1]). Noone uses Edge. Whatever undocumented features of Edge (if any ) *somehow* facilitating MS operations is lost. The whole plan on world domination and stuff through the Windows 10 pushing is likely failing (besides the total defeat on phones) because even those that for one reason or the other are using Windows 10 ar not using Edge and nowadays a large part of the time spent on a computer is through its browser. Idea , let's make a new browser similar to or nearly identical to Chrome (possibly while keeping the same *whatever* undocumented features we like to have). Wait, this would mean actually writing lots of code, why not using the actual same engine as Chrome? jaclaz [1] and with the exception of a few old dinosaurs like yours truly that still use good ol' browsers (with some limitations).

I inadvertently found out that Internet Explorer 9 is again, as of late, able to play back youtube videos, so it appears Google (the owner of youtube) have patched their scripts to cater to IE9; this surely comes as a (nice ) surprise, but the reason behind such a move seems inexplicable to me... Perhaps was to support WS 2008 SP2 (officially supported until Jan 2020), on which IE9 is the only version of the native Microsoft browser to run, but I'm not convinced... For whatever reason, youtube now has been restored to its previous state in IE9, serving standalone MP4 encodes over HTML5 (usually only in 360p quality variant - some videos with more relaxed copyright also come with an additional (HD) 720p variant). As before, there's no way to go full screen: The MP4 decoding relies on system h.264/aac decoders (Windows Media Foundation), which means you need installed both SP2 + Platform Update Supplement for Vista... OT: Notice in the top blue ribbon how Google are eager to push their own (spyware of a) browser, even on a currently unsupported platform (i.e. Vista)...

Ever heard of fcwin2k? Then again, there are other ways, too...

IE9 (32-bit) on Vista SP2 Home Premium 32-bit here The youtube.com/html5 test is correct when it comes to IE9 on Vista (no VP8 support here): IE9 has no support for MSE; after Google ceased supporting Adobe Flash Player (all 3 variants of it, i.e. activeX, NPAPI, PPAPI) on youtube, the only thing left for IE9 to handle was progressive download of mp4 files (encoded in h264/aac) over HTML5, and I recollect the limitation of not being able to go Fullscreen on the embedded player (a message about unsupported browser was displayed ) ... It was at the start of summer that I accidentally noticed yt was unplayable on IE9, as I'm hardly using IE9 for anything this day and age... I did not lament the loss of yt on IE9, in any case it had been an unsupported browser many moons ago already... But it was this thread that made me want to investigate things... So: Well, youtube claim they don't officially support any IE version anymore, yet tests show that IE10/IE11 still work, while (obviously) previous versions don't... Loading Introducing iPhone XS, iPhone XS Max, and iPhone XR in IE9 (after you declined to upgrade your browser, that is...), you get the empty embedded player, as per OP: For troubleshooting, open IE9's developer tools (F12) and load (browser) Console; refresh youtube page: To load their embedded player, yt use, among other things, a JS script named base.js; URI for my locale is: https://www.youtube.com/yts/jsbin/player-vflkUTZn2/el_GR/base.js That script uses in 19 instances the window.matchMedia code snippet; a Google search on matchMedia yields the following two results (among others): https://developer.mozilla.org/en-US/docs/Web/API/Window/matchMedia#Browser_compatibility https://caniuse.com/#feat=matchmedia where one can see that the needed API was introduced only in IE10+, i.e. IE9 does not understand window.matchMedia and chokes, failing to load the HTML5 youtube player: Mozilla Firefox, OTOH, supports the function from an early version 6 - and Chrome from version 9... Not strange anymore, is it?