The later released Windows Virtual PC, made for XP-Mode on Windows 7, did require hardware-virtualization. Windows 3.1 wanted it though, to get Win32s going. It had AMD-V, but the VM software didn't require it at the time. My father had an Athlon 64 X2, I vaguely remember. Roughly about the time, I had a PC with a VIA C7-D that ran MS Virtual PC 2007 just fine.Īnd VMWare Player/Virtualbox, I remember.īefore that, I was using a Pentium IV with Hyper-Threading, but no AMD-V/Intel V (Vanderpool) support in silicone. □♂️īut back in 2008 and before, I ran various virtualizers on XP 32-Bit. Um, Windows 11 needs TPM 2 and in turn indirectly those virtualization-extensions, I guess. Most xp machines don't have CPUs with virtualization extensions. Up to Windows 10 should work, after that, 32-Bit PC support got canned (finally □). So you can export all your bookmarks of Palemoon etc and import it in a virtualized Firefox on Linux, ArcaOS or modern Windows. If you're still using XP as your main OS, please consider using a virtualized Linux (CoLinux/AndLinux etc) or a VM.īoth Virtual PC 2007 and older versions of VirtualBox/VMware can still run under Windows XP. And the Mac fans are kinda jealous about that (- Thenfourfox). Let's see it positive, XP outlived both Mac OS X 10.4 'Tiger' and Mac OS X 10.6 'Snow Leopard'. So you see, 32-Bit computing was on its knees already, before Windows XP went EOL in 2014. The compiling had to be done on a real Windows 2000 at the time. In fact, the news said the Windows 2000 system was almost falling apart from the stellar memory consumption.Īnd no, a 64-Bit of Windows edition couldn't be used for some reason. The web simply has become too bloated and 32-Bit editions were hard to compile to in ~2010 already.Īs far as I remember from the news back then, a Windows 2000 machine used for compilation had to use all kind of tricks to get Firefox 32-Bit compiled. Seriously guys, the time for XP compatible browsers is over.
0 Comments
Leave a Reply. |