Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Popular Content

Showing content with the highest reputation since 09/21/2017 in all areas

  1. 7 points
    So new build and new thread. Latest build is here: Binaries are moved to here: (I'm lazy to edit all previous posts) https://o.rthost.cf/palemoon/?sort=date&order=desc FAQ: Q: Can't play H264 clips? A: Download following packages for your browser edition(32bit/64bit) and extract DLLs to same place as palemoon.exe lives. 32bit LAV dlls are in separated package (extracted from K-Lite codec pack 13.5.5) https://o.rthost.cf/palemoon/lav.7z 64bit LAV dlls are in separated package (LAV Filters 64bit 0.70.2) https://o.rthost.cf/palemoon/lav64.7z Q: VP9 Support? A: VP9 works if async MSE option is unchecked in options. Q: Extensions/Themes not working after updating binaries. A: If you encounter extensions not show icon, clicking options button of extension causing browser unresponsive, etc. please try following actions: 1.a Killing palemoon.exe process 1.b Copy whole extensions folder out of profile folder (to somewhere else for example, desktop) 1.c Restart browser without restoring previous sessions 1.d Goto about:addons page 1.e Drop XPI files from the copied-out extensions folder to about:addonss page One-by-One. 1.f After all XPI files are dropped and installed/updated, restart browser Q: Virus detected? A: Tell your anti-virus program to exclude palemoon.exe and/or plugin-container.exe. Some anti-virus heuristic engines (for example symantec's sonar engine) is too sensitive to palemoon.exe/plugin-container.exe network activities. Q: Where's your patches for compiling my own? A: Please visit the link above "FAQ:". Latest source patch files are named "sources_patches_YYYYMMDD.7z" in that page. ----original post message belows---- Today's build with portable LAV libraries. Place LAV dlls (av*.dll) in same place as palemoon.exe lives. Official repo changes since my last build: -Clobber for Brotli/WOFF2 update -Fix some comments (no code change) -Enable Brotli content-encoding by default (https only). -Pull woff2 upstream update. -Update Brotli decompressor. My changes since my last build: - Upgrade Mozilla NSPR and NSS to 4.16 and 3.22 for (hopefully) faster AES operations 32bit: https://o.rthost.cf/palemoon/palemoon-27.6.0a1.win32-git-20171002_2-e68ab5b3d-xpmod.7z 64bit: https://o.rthost.cf/palemoon/palemoon-27.6.0a1.win64-git-20171002_2-e68ab5b3d-xpmod.7z
  2. 5 points
    Don't afraid. It was just an ironic note, because of users asking the same things over and over again and they still expect some answer although it has been covered milliontimes.
  3. 5 points
    Introduction: As the title implies, this post serves as a guide for anyone potentially seeking to install and use Vista on the Intel Ivy Bridge platform. I felt there was a need to create this guide, because although getting full driver support for Vista under Ivy Bridge IS possible, it requires you to use certain motherboard(s) from the Sandy Bridge era to get USB 3.0 driver support for Vista. Intel HD 4000 Graphics drivers are also not so easy to obtain for Vista, so a link to them has been provided below. Choosing the right motherboard: With Ivy Bridge, Intel dropped Windows Vista (and XP) support from its USB 3.0 drivers, rendering XP/Vista support for the Ivy chipset incomplete. To work around this, you will need to find a motherboard from the Sandy Bridge era that supports Sandy AND Ivy Bridge CPUs. Almost all Sandy Bridge motherboards, except those with the Q65, Q67 or B65 chipsets, will support Ivy Bridge CPUs through a BIOS upgrade. A notable example of such a motherboard is the Asus P8Z68-V LX. This motherboard in particular has Asmedia USB 3.0 controllers, and Asmedia has excellent driver support for Windows Vista. Gigabyte also offers a number of boards that include third-party USB 3.0 chipsets, which support Vista. Be aware that you might have to purchase (or borrow from a friend/relative) a Sandy Bridge CPU to boot up your system for the first time if you are building from scratch, as the original BIOS version for these boards does not support the use of Ivy Bridge CPUs and will not allow you to boot the machine with an Ivy Bridge CPU without first updating your BIOS. For Ivy Bridge-E processors, the X79 chipset is fully supported on Windows Vista and you may choose any motherboard you like (the BIOS update situation still applies). If you do not care about or need USB 3.0, then you may choose any Ivy Bridge motherboard you like. Chipset drivers for Ivy Bridge do support Vista and can be downloaded here. I personally use the ASUS P8B75-M motherboard with Windows Vista Ultimate, and I find it to work well (Vista simply uses its generic USB 2.0 drivers for the USB 3.0 ports). Finding Intel HD 4000 Graphics drivers: You can download Intel HD 4000 Graphics drivers for Vista here. For some reason, Intel decided initially to not support Windows Vista with its HD 4000 graphics chipsets. However, it appears that they later decided to add in Windows Vista support, evidently via backporting Windows 7 drivers, since this installer claims that the drivers are for Windows 7 but doesn't mention Vista specifically. Despite this, the drivers work just fine in Windows Vista. I have studied the driver setup information (.inf) files and found that both desktop and mobile HD 4000 graphics chipsets are supported, so this driver should be able to be used with any Ivy Bridge graphics chipset under Windows Vista. That's it! No additional special steps are required, and you may install and use Vista normally with full driver support on the Ivy Bridge platform (arguably the best platform for XP/Vista). I hope this guide helped you!
  4. 4 points
    Of course there was an update to Windows XP, KB4042723 (wzcsvc.dll). According to my manufacturer of the router, this is not affected with the current firmware, best at your router manufacturer inquire / inform. Today, there was another update (KB4019276 download / info) for Windows XP to support TLS 1.1 and TLS 1.2 (client - server / IIS).
  5. 4 points
    Anyway I built my own palemoon-27.4.2 with patches in #1 and replaced GetTickCount64() with dynamic loading NtQueryPerformanceCounter() like One-Core-Api does (with --disable-skia and bundled New Moon branding, nothing else changed) http://o.rthost.cf/gpc/files1.rt/palemoon-27.4.2-unofficial-xp.7z
  6. 3 points
    New build which is working in Win95 OSR2! http://o.rthost.cf/gpc/files1.rt/rzbrowser-tls12-20171008.7z Updated files are available here: https://github.com/rn10950/RetroZilla/issues/7#issuecomment-334985097
  7. 3 points
    Hey guys! I'm proud to announce my first colaboration for the old software and hardware community. I'm developing a chat website and now, people who use old OS are able to chat too. This is just the first version, so bugs can be found. Download link: https://www.papinho.com/ProgramaLegado.exe It's simple, but I plan to improve it. I am using Delphi 7 to develope it, running on Windows NT 4. Limitations: - Not possible to select room yet, by default you enter on a room caled "Legacy Software and Hardware"; - Portuguese Brazil only interface; - Several features still not available (like send voice messages, files, images, youtube videos, webcam chat) - these are already working on website: https://www.papinho.com/index.php?Idioma=en-US; I plan to fix all these limitations and if someone want to collaborate, I will be happy : - ) Please, test it on old OS, and give me feedback [on which one it work or fail]. To enter, just type your nickname at "Apelido" and press "Entrar".
  8. 3 points
    It's not identical with the SP3 version. Only the version is the same, content is different (PE binary code). Additionally, the msinfo32.exe is only the launcher, not the real system information - latter is the msinfo.dll, which serves as a module for the Windows Help Center Service. If you start msinfo32.exe, the small process simply quits after launching the system information. However, in WS2008 the msinfo32.exe contains the real code (see size on support site) and probably that's the reason why MS "updated" the exe accidently in xpe instead of the dll, too - and then corrected the update package on August.
  9. 3 points
    I don't think it was really all that "right",,, There are things I can name that are better in other versions. It's just that Windows 8 had a fundamental UI flaw and WIndows 10 is so "wrong" that nobody wants it on its own merits. One of the prime reasons for getting Windows 10 runs along the lines of "my computer died and the new one came with Win 10". Only a few of us geeks have felt the good in Darth Win8er and managed to turn it back to the good side of the force. People generally don't want to have to be degreed in computer science and work that hard to make their OS acceptable for use. -Noel
  10. 3 points
    I'd say it means you're not trying to actually do anything useful with those systems. I think that's the only way Windows 10 continues to hang together - when it's only tasked with updating itself. -Noel
  11. 2 points
    Yeah. So use USP10.DLL for GlyphIndex retrieving. The gfx drawing is still need more work.
  12. 2 points
    Update; Version 3.01 is now ready. Check out the blog post for details; https://hjtsoft.blogspot.co.uk/2017/10/unofficial-windows-millenium-edition.html
  13. 2 points
    Newest JRE have been released moments ago: 8u151/152.
  14. 2 points
    An LBA entry in the MBR (or in a EMBR) is made of two fields, each 32 bit in size: 1) "Start Address" or "Sectors Before" i.e. how many sectors are BEFORE the beginning of the partition described in the entry 2) "Size" or "Sectors in partition". i.e. how many sectors (starting from the address in the field above) are contained in the partition. So at the very most you can have is: 1) One entry where the "Start Address"+"Size"<2^32-1 (this can be also multiple partitions as long as the sum of the last "Start Address"+"Size" remains within the 2^32-1 limit. 2) Given that the #1 is actually <2^32-1 ONLY a single primary partition with a maximum extent of 2^32-1 sectors. If you prefer, you can have one (and only one) partition crossing the 2^32-1 "border". Since you need some "hidden sectors" before the first partition (at the very minimum 1, the MBR), the most you can have theoretically is: Entry #1 -> "Start Address" = 1 and "Size"= (2^32-1-1)=4,294,967,294 these will be in hex respectively 0x00000001 and 0xFFFFFFFE and 0x00000001+0xFFFFFFFE=0xFFFFFFFF=4,294,967,295, i.e. (2^32-1) Entry #2 -> "Start Address" =(2^32-1)=4,294,967,295 "and "Size"=4,294,967,295 these will be both in hex 0xFFFFFFFF In practice you need to align the partitions using more "hidden sectors" which are typically 63 (traditional value, aligned to disk geometry) or 2048 (new value since Vista, aligned to 4Kb, actually more than advised, strongly suggested on 512e disks) so you can have at the most: Entry #1 -> "Start Address" = 2048 and "Size"= (2^32-1-2048-7)=4,294,965,240 (i.e. a number divisible by 8), these will be in hex respectively 0x00000800 and 0xFFFFF7F8 and 0x00000800+0xFFFFF7F8=0xFFFFFFF8=4,294,967,288 (<4,294,967,295) Entry #2 -> "Start Address" =4,294,967,288 "and "Size"=4,294,967,295 these will be in hex respectively 0xFFFFFFF8 and 0xFFFFFFFF There is simply no more address space to write bigger numbers. The 128 Gb limit you mention is an altogether different issue. The LBA data in the MBR has always been 32 bit in size, but the actual hard disk standards (ATA) had only 28 bit resolution (early drivers , i,e, 2k until Service Pack 3 if I remember correctly and XP until SP1 followed the standard) with ATA 6 the resolution was increased to 48 bit (i.e. more than the amount that can be stored in the physical space available in the MBR). The 48 bit in itself allows accessing 2^48-1=281,474,976,710,655 sectors, i.e., with "normal" 512 bytes sector 128 Pb. If you prefer, before the ATA transmitted only partially the data available, now it can trasmit more data than what exists. Now any *normal* OS manufacturer would have found a way to extend the MBR scheme finding a way to use some otherwise unused 4*2 bytes *anywhere* in the MBR as "high address" (and BTW also a 40 bit extension, needing only one additional byte per entry would have made accessible 512 Tb that would have been more than enough for several years), but the good MS guys (strongly pushed by the good Intel guys I believe) decided that it was too d@mn simple and went for the stupid GPT scheme (which is the typical exampe of an overcomplicated scheme designed by a commission). Still, there is nothing preventing adding GPT compatibility to an existing OS such as XP, but a number of drivers (and possibly a number of disk related tools need to be rewritten (from scratch since most are not open source). Most probably the next candidate would be a port of ReactOS drivers, when and if that OS will have GPT support, and by that time most probably it would make more sense to use directly ReactOS instead of XP. jaclaz
  15. 2 points
    Some text is shown now. Maybe I have to use this instead of using stub. https://github.com/LayoutFarm/Typography/wiki/How-To-Translate-Unicode-Character-Codes-to-TrueType-Glyph-Indices-in-Windows-95
  16. 2 points
    I personally think we should start working on an "extended kernel" for Windows 7, just like how blackwingcat made one for Windows 2000, which can port Windows 10 functions and the like. It won't be long until manufacturers/devs succumb to the will of MS, and prevent older OSes from working on newer hardware and software.
  17. 2 points
    IMHO there is a big difference between Windows ME and Vista. As a matter of fact Windows ME is - as you say - very similar to 98 SE (with actually a few betterings "under the hood"). The issue was that it removed (or made difficult) to an audience coming from 9x a large part of their experience (MS-DOS in real mode) while introducing quite a few incompatibilities (particularly with DOS based programs, but not only), and the betterings were not easily detectable to the end user. As a matter of fact, the "best" system is most probably a 98SE2ME: http://www.mdgx.com/9s2m/ http://www.mdgx.com/98-5.htm#KRM9S Of course XP (particularly the XP Home pre-installed on laptops) killed it (while providing - on the very limited hardware on which it was installed - a poor experience to the user anyway). Vista is a different case, it actually sucked, and it sucked big initially. A number of (senseless) changes were introduced on the otherwise perfectly working NT derived XP, and it was delivered in a severely immature stage, while no or very little documentation was provided. Besides (the same) issues with low-powered entry-level systems where it came pre-installed, the real deal breaker was that it was widely publicized as the "new better" OS (understandably from MS point of view) without highlighting how the hardware requirements were extremely higher than what XP ran on. The net result was that everyone that had XP running tried it (either on the same old hardware where they had XP running just fine or as a pre-installed OS on low-low power notebooks/netbooks) and the result was of an extremely slow OS (additionally with a lot of issues with permissions, network and drivers). It was doomed, everyone that could remained on XP, at least at the times of "gold" and - later - "SP1" (which only partially fixed the issues) came out. The actual working version of Vista (from a certain point of view even better than 7) was SP2 which simply came too late and was "killed" by MS itself and by the release of 7. The latter was also IMHO greatly facilitated by the progresses of the hardware in the meantime, an entry level system in 2009 was far more powerful than an entry level system in 2006 or 2007, and this is one of the reasons why 7 (which I like to call Vista SP3) actually had so much success. BOTH Vista and 7 are resources hogs (when compared to XP or even better 2K) what made the difference was the sheer power/speed beneath. jaclaz
  18. 2 points
    Okay Final version 3.8.8 is online. Fixing a few bugs that were left in the last Beta.
  19. 2 points
    Update for root certificates: Delete: CN = Sonera Class1 CA O = Sonera C = FI New: OU = AC RAIZ FNMT-RCM O = FNMT-RCM C = ES SN:5d 93 8d 30 67 36 c8 06 1d 1a c7 54 84 69 07 CN = GTS Root R1 O = Google Trust Services LLC C = US CN = GTS Root R2 O = Google Trust Services LLC C = US CN = Halcom Root Certificate Authority = VATSI-43353126 O = Halcom d.d. C = SI CN = Netrust Root CA 2 OU = Netrust Certificate Authority O = Netrust Pte Ltd C = SG CN = SSC GDL CA Root A OU = CA ROOT Services O = Skaitmeninio sertifikavimo centras C = LT CN = SSC GDL CA VS Root OU = VS ROOT Services O = Skaitmeninio sertifikavimo centras C = LT CN = SSL.com EV Root Certification Authority RSA R2 O = SSL Corporation L = Houston S = Texas C = US Those using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.
  20. 2 points
    One step away from the Abyss. I have a working Hard Disk AHCI Driver. Unfortunately, I do not have the Optical Drive Code working yet.
  21. 2 points
    Direct links to the October 2017 updates: POSReady 2009 (English only), IE8 (English only), .NET Framework 2.0 SP2 (international) and .NET Framework 4 (international), Office 2007 compatibility pack (international) and Word 2007 (international). http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/09/windowsxp-kb4041995-x86-embedded-enu_acee429ab4e7445545ac73a97f390628e647c1cf.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/09/windowsxp-kb4042007-x86-embedded-enu_91da0ec0a97369c4723348583667f6b1602330d2.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/09/windowsxp-kb4042067-x86-embedded-enu_b09bab2b749c62c40dac8de0f7ac6e483faeb74b.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/09/windowsxp-kb4042120-x86-embedded-enu_5bfd7225d96606fe963ade3234d40dd91171d03f.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/09/windowsxp-kb4042121-x86-embedded-enu_65002fb4dca0f5a66ea065087a5fe489756610bd.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/09/windowsxp-kb4042122-x86-embedded-enu_9a490eca0c895cc02405f1914beb655e26d09d32.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/09/windowsxp-kb4042723-x86-embedded-enu_8576b400225ed341b99d8b68d27b1cf3442ae85d.exe http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/09/ie8-windowsxp-kb4040685-x86-embedded-enu_626c47bd53c0814a664cebd80e6c643bc3866707.exe http://download.windowsupdate.com/c/csa/csa/secu/2017/09/NDP20SP2-KB4040968-x86_627A7D41E164C26280B1DB64FEFBBA23C754EBC4.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/09/NDP40-KB4040962-x86_976F8849C17DE7A0CAB333C0081E9858A6407A85.exe http://download.microsoft.com/download/3/0/3/303F463C-8141-42D1-9DCD-278AB1576537/wordconv2007-kb3213647-fullfile-x86-glb.exe http://download.microsoft.com/download/D/9/C/D9CC0E10-4B94-44FD-93BA-6DCE1E8F332F/word2007-kb3213648-fullfile-x86-glb.exe
  22. 2 points
    Well since we are still in the BMW motorcycle field, let's not forget how still today the boxer engine (and shaft drive) used on the series R models is essentially derived from the one designed in the 1930 and 1940's, which should be a good enough example that when you have something well designed and working correctly, you only refine it. Now MS had a perfect product: Windows NT designed (mainly) by Dave Cutler : https://en.wikipedia.org/wiki/Dave_Cutler that worked just fine since day one and was improved over the years until they managed to ruin it almost completely with Windows 10. jaclaz
  23. 2 points
    2008WindowsVista I support your effort to keep these drivers alive. As you know Intel has a convoluted database that is hard to search for the drivers or they intentionally deprecate it and remove older versions (to save space) and only leave newer versions killing off support for older ones. I think these drivers are hidden from Z77 chipsets on the Intel website but should work. If not I'll back port them when I get a chance. I decided to help back up the Vista Drivers for integrated Intel HD Graphics for (Sandy Bridge / Ivy Bridge) Chipsets Z68 / Z77. Backup of the download page works although the download links are destroyed by Intel so I found a way to directly link them as long as WayBackMachine exists these files will never be lost. Archived for information purposes only and you can't directly download the files through this archive page. http://web.archive.org/web/20171008141948/https://downloadcenter.intel.com/download/20758/Graphics-Intel-HD-Graphics-Driver-for-Windows-Vista Vista 32-Bit Intel HD Graphics Drivers direct link to download file. http://web.archive.org/web/20171008142049/https://downloadmirror.intel.com/20758/a08/GFX_Win7_32_8.15.10.2761.exe Vista 64-Bit Intel HD Graphics Drivers direct link to download file. http://web.archive.org/web/20171008142245/https://downloadmirror.intel.com/20758/a08/GFX_Win7_64_8.15.10.2761.exe Now I haven't tested these recently but I seem to recall using Vista 64-bit Intel HD Graphic drivers on my Z68 and Z77 systems back in the 2012 time frame. The final test is did they retain the Windows 7 HDCP so even Vista can play Blu-ray movies properly or if this was just a basic graphics drivers. I'll have to test these later to see if they work but these new download links will ensure they will never be deleted even if Intel secretly removes them one day from their own server. I suggested people archive the two Vista 32/64 Bit direct download links as a bookmark in case MSFN goes down you can still find them. Readme file: http://web.archive.org/web/20171008143938/https://downloadmirror.intel.com/20758/eng/GFX_8.15.10.2761_readme.txt
  24. 2 points
    Good question, burd. You see, superfetch preallocates some applications you use most frequently into RAM. This results in faster performance (since RAM can be accessed instantly, whereas on the hard drive the data must be "read" first). With SSDs, superfetch is useless because SSDs are instant and have no moving parts unlike standard HDDs, so it takes almost no time to read the data to launch the application(s) you want to open and ends up being about the same speed as RAM. So it saves memory to turn it off. In Windows Vista, superfetch was much more aggressive with RAM compared to Windows 7, where superfetch was greatly toned down. Vista's algorithm was just not practical for systems with less than 2 GB of RAM, but on systems with more RAM than that, it was fine (at least until modern applications started to use more RAM... now you'd probably need even more than 2 GB, optimally). 7's algorithm works almost the same, but I suppose it doesn't preallocate as many applications into RAM so it doesn't use as much memory. That's great for low-end hardware but could cause a slight performance decrease coming from Vista on systems with more RAM, if you use several different applications. I doubt it's all that noticeable, though.
  25. 2 points
    I'd have to disagree in regards to DWM, at least somewhat. Vista's window animations are much smoother than those of Windows 7 (7's are quite choppy; Vista's are buttery smooth). The only difference I can find is that Vista uses Direct3D 9 to render its window animations whereas Windows 7 uses Direct3D 11, so maybe this caused a decrease in performance? Whatever the issue is, it doesn't exist in Windows 8.x (one of the many things I like about 8.x over 7); animations there are buttery smooth once again. As for the other issues you mentioned, they're also applicable to Windows 7 but the biggest difference is that Windows 7 at least is provided drivers for most modern hardware, whereas Vista is not. It largely depends on your needs, and if you need those things you're better off using Windows 8.1 anyway imo.
  26. 2 points
    You're not understanding my point at all. The issue I'm describing has NOTHING to do with graphics cards. There. That's it. Nail on the head. The problem is isolated to Haswell and all of its successors. If you run Vista on the Haswell platform, you'll experience this error at some point. Doesn't matter what video card you use, what onboard devices are enabled or disabled, or how you install Vista. Those have absolutely no effect. Do forgive me, but I LOL'd when I saw that. You don't need to use a card from 2011 for Vista. The GTX 980 supports Windows Vista just fine, and you can even use the GTX 1080 with Vista thanks to unofficial drivers (you can find them on my Last versions of software for Vista list). AMD's driver support for Vista is far worse compared with NVIDIA (15.6 beta is the last version of the AMD Catalyst drivers that works with Vista which is long obsolete and limits you to AMD GPUs released prior to June 2015). 98SE, I invite you to read more about Vista on my Last versions of software for Windows Vista and Windows Server 2008 list. You'll find a ton of information there about the current state of Vista's third party software & driver compatibility, and it is updated almost daily so the information there is all accurate and up to date.
  27. 2 points
    SUMMARY OF CHANGES TO THE LIST FOR OCTOBER 5, 2017: Added mpv v0.25.0 to "Multimedia" section as the last version of the software to support Vista. Added download links to Epic Browser 58, Google Chrome 50, Opera 37, Firefox 53, and Waterfox 53.0.3. Overhauled "Intel chipset & graphics" section, containing new information about Ivy Bridge compatibility with Vista and a link explaining the problems with Vista on Haswell (and later platforms) in greater detail. Added Passmark PerformanceTest to (ONG) "Benchmarking and system stress-testing software" section.
  28. 2 points
    Thank you for another very detailed and informative post, VistaLover. I share your sentiment and can't stand when developers use the end of extended support as an excuse to justify dropping support for an OS with their own product. If they really cared about EOL, why did they support XP until November 2015, and why did they not (intentionally) drop support for Vista until now? Sounds awfully fishy to me. Regardless, I will add mpv 0.25.0 to the list.
  29. 2 points
    @dencorso @jumper I stand corrected. I think I might have been thinking of MMX support, which was first seen with the later 1996 Pentiums. So, I think this means that Firefox 3.6.28 was the final version for the Pentium and Pentium II: (https://web.archive.org/web/20120525091229/http://www.mozilla.org/en-US/firefox/3.6/system-requirements/)
  30. 2 points
    Well of course Vista will "work" on Coffee lake, just as it did with Haswell, Skylake, and so on. But the problem is finding proper drivers for Vista to communicate with the hardware. The Asmedia components might work on Vista with the board that you mentioned (AsRock Z370 Tai Chi), but there's another huge problem with Vista when coupled with Haswell (and newer) platforms, which I'm about to go into now: Vista was very unstable for me when trying to use it on my Haswell hardware (ASUS H97-M board, Core i5 4460). Half the time, the OS wouldn't boot without an error popping up on the screen just before the startup orb animation appears that contained the following information: "The interactive logon process initialization has failed. Please consult the event log for more details." Upon closing the error, sometimes the machine would hang on a black screen or it would boot to a semi-usable desktop. If the latter occurred, many services failed to start and I was forced to reboot the machine to get them to start correctly, provided the machine even decided to boot properly on the next boot attempt (again, maybe 5 out of 10 times the OS would boot properly, but otherwise it would either display the aforementioned error or random services would fail to start, leaving the OS in an unusable state). I even installed Intel's own chipset drivers for XP/Vista for Haswell, and doing so had no effect: the error simply persisted. Other users of Haswell/Skylake coupled with Vista (such as @11ryanc, @burd, and @dork) had the exact same problems with different Haswell/Skylake boards and CPUs than what I was using, so I know the problem wasn't caused through any fault of my own - Vista just simply doesn't work properly with any Intel platform after Ivy Bridge. I don't know why this is the case (even Windows XP at least successfully boots consistently on Haswell), but the fact of the matter is that it's more than likely to remain unfixed for the foreseeable future. If you're more technically inclined to fix or have the patience to deal with those issues, more power to you. But most people aren't going to have the patience or know-how when it comes to these errors and will simply opt to use Windows 7/8.x/10 instead (which is what I was forced to do until I went with Ivy Bridge). Since this issue has carried on through Haswell/Broadwell, Skylake, and Kaby Lake, it's pretty safe to assume that Coffee Lake will have the same problem. Just know that if you're buying Coffee Lake to run Vista, you're running the risk of either being forced to use Win7+ against your will, having to deal with the mess of problems I just mentioned, or having to return the hardware and just embrace Sandy/Ivy Bridge. I'll be flabbergasted if this problem somehow doesn't occur with Coffee Lake, but I really don't see that happening. Just don't get too hopeful.
  31. 2 points
    I am sorry to report that yet another application moves out of Vista support mpv is a CLI media player, a recent fork of MPlayer (itself a fork of mplayer2); while it is mostly known/used on non-Windows OSes, it does support Windows too codewise and win32/win64 executables (mpv.exe) can be compiled via, e.g., MSYS2 native Windows compiler (but, sadly, MSYS2 now requires Win7+ and preferably the x64 architecture ). Power Windows users may be already familiar with mpv when using it with other CLI applications like the stream-downloaders livestreamer (now defunct), its maintained fork streamlink and youtube-dl; but perhaps others may know mpv as the media engine driving the front-end SMPlayer (this can also use the original MPlayer under the hood, but from experience has worse performance compared to using mpv). The mpv devs have made it clear from the start of the fork (ca. 2012) that they'll be dropping support for very old systems... Windows XP was accidentally dropped in November 2015, but then the devs decided to do nothing to restore its support. Most unfortunately, we're now seeing a repeat of that with regards to Windows Vista; you can read about it in this GitHub issue . Though the breakage was indeed unintentional, there'll be no effort spent by the devs towards restoring Vista support As you'd expect in such cases, the same ol' "Microsoft’s extended support has ended" mantra was recited but, in all fairness, the dev did acknowledge that as The justification of "Vista not registering in my download statistics: https://mpv.srsfckn.biz/stats.html" I found quite lame, TBH; what it all comes down to is While he obviously could, the main dev providing the Windows executables said The only options offered by the devs to Vista users (cross compile in a Linux VM or install Linux in the Vista machine and dual-boot) are far from realistic for most Vista users on old-ish hardware, not to mention the huge learning curve required to master Linux at first and the cross-compiler itself after that... So, on the Windows builds page the very last Vista compatible binary is the one marked as 2017-04-23, which is in fact mpv-v0.25.0: https://mpv.srsfckn.biz/mpv-i686-20170423.7z https://mpv.srsfckn.biz/mpv-x86_64-20170423.7z versions 0.26+ will simply not run on Vista; to be exact, this is only valid for the pre-compiled binaries offered by the main dev in his repo; in theory, code newer than v0.25 could be compiled with modifications to the crypto lib used so as to restore Vista support; I, for one, don't possess neither the hardware nor the know-how to even attempt such a task...
  32. 2 points
    I am way cooler. I decommissioned only recently (march or april this year) a couple of machines, running respectively NT 4.00 and Windows 2K that worked just fine for the parts of the Internet that were needed. Both ran 24/7 for the last 14 years or so without issues of any kind (only replaced some power supplies and some disks). In the good ol' times we used to call this "work", it involved no access to social sites, no messaging, no lolcats, no videos, you get the idea . jaclaz
  33. 2 points
    New Build! If you encounter extensions not show icon, clicking options button of extension causing browser unresponsive, etc. please try following actions: 1.a Killing palemoon.exe 1.b Copy whole extensions folder out of profile folder (to somewhere else for example, desktop) 1.c Restart browser without restoring previous sessions 1.d Goto about:addons page 1.e Drop XPI files from the copied-out extensions folder to about:addonss page One-by-One. 1.f After all XPI files are dropped and installed/updated, restart browser Official repo changes since my last build: - Focus the address bar if opened content in a new window is blank. (babcb02) - Fix preprocessor build warnings (7fa18a4) - Merge pull request #1389 from JustOff/PR_pp_warnings (9219747) - Fix MSVC LNK4217 warning in hunspell (c7e04ff) - Merge pull request #1390 from JustOff/PR_hunspell_LNK4217 (884093a) - Tweak the Windows 10 styling of the default theme. (8416a01) - Fix warnings from MakeNSIS (91268a6) - Merge pull request #1392 from JustOff/PR_nsis_warnings (d41b540) - Work around some more issues with broken Apple fonts. (7121f53) - Merge branch 'master' of https://github.com/MoonchildProductions/Pale-Moon (c97789a) - Update to latest libhyphen code from upstream. (61e3f2c) My changes since my last build: - Change zlib crc32.c to use PCLMULQDQ (mostly from https://github.com/fhanau/Efficient-Compression-Tool/blob/master/src/zlib/crc32.c , with some changes preventing crash when buf is nullptr) 32bit: https://o.rthost.cf/palemoon/palemoon-27.6.0a1.win32-git-20171004-61e3f2cfb-xpmod.7z 64bit: https://o.rthost.cf/palemoon/palemoon-27.6.0a1.win64-git-20171004-61e3f2cfb-xpmod.7z
  34. 2 points
    ... Just go to Pale Moon localization and save to disk latest language pack v27.5.0_RC8 that suits you (this is an .xpi file, i.e. a .zip file); modify the install.rdf file inside it (e.g. with 7-zip) and change maxVersion from 27.5.* to 27.6.* ; save your changes and then install modified language pack in PM 27.6.0a1 (install from file in the add-ons manager or simply by drag-n-drop in a tab). This is how I got the Greek locale myself on PM unstable in the screenshot posted previously So, you can easily enjoy PM 27.6.0a1 in German, if you so wish! PS: After installing the LP, you'd have to go in about:config, filter general.useragent.locale and modify the default en-US to the language of choice, e.g. de; restart PM for the change to take effect; tada!
  35. 2 points
    September Update has left Windows 8.1 users unable to sign into their Microsoft Account: https://mspoweruser.com/september-update-left-windows-8-1-users-unable-sign-microsoft-account/ Besides this, for me, it has broken DISM and SFC. DISM reports now that the Component Store is corrupted and /ScanHealth /RestoreHealth do not work. I hope Microsoft Windows gets irrelevant and more unpopular and that gets the satanic management fired. I am so sick of updates screwing up working systems. We desperately need new leadership at Microsoft that does not have a mental illness about pushing new features at the cost of breaking things that came before it.
  36. 2 points
    For those having palemoon.exe/mozglue.dll crashed, please try this build. Cloudflare's zlib uses SSE4.2 CRC32 instruction unconditionally. I made modifications to its hash function to use original zlib's hash function for processors that has no SSE4.2 instructions support by runtime CPUID detection. Disclaimer: I only made some limited testing with snail-slow QEMU for emulating processor without SSE4.2, so please test with care! 32bit: http://o.rthost.cf/gpc/files1.rt/palemoon-27.6.0a1.win32-git-20171002_2-e68ab5b3d-xpmod.7z 64bit: http://o.rthost.cf/gpc/files1.rt/palemoon-27.6.0a1.win64-git-20171002_2-e68ab5b3d-xpmod.7z
  37. 2 points
    Clamwin + Clam Sentinel gets you real time scanning, and its still lightweight.
  38. 2 points
    Looks like we can have our cake and eat it too We got symbols today and therefor transparency. -DW Win10 16296 w/ Aero Glass 1.5.6
  39. 2 points
    Time for my next complaint! Even Google can't seem to answer this one. This is another one that follows the mobile trend. I'm very much aware this "word", or abbreviation, has existed way before mobile technology really even became a thing. But for the love of God, why do people absolutely LOVE saying the word "app" so much? This is a word I feel like people get ultimate pleasure in saying, particularly out loud. Listen to just about anything anymore, "blah blah blah......and DOWNLOAD OUR APP!!!" Okay, I get it, you want people to download your free program because it makes your content better for them or something. But do you have to say it constantly, over and over again? I'm sorry, but the word isn't cool anymore. I never thought it was anyway, but now it's the most overused and abused word in technology. I think it's just one of those words though that people who know next to nothing about technology or how it works to sound hip. It's kind of like 4G LTE. I hear that all the time, even out of the mouths of regular people. Exactly how many people even know what LTE means or stands for? Probably nobody. But to get back to what I was originally talking about. Until smartphones became a thing, I almost never heard people call something an app. When referencing something on the computer, it was either an application, a program, or web browser, a word processor, well you get the idea. Things used to differ from each other. Games used to be games. Now everything is all consolidated into one term, app. Even Microsoft wasn't happy until they cashed in on that word. Programs was used for many, many years in Windows. But what happens once it moves into the mobile era? "That no longer works.....All Apps...yep, sounds good." So the too long, don't read version. I'm tired of that word, no it doesn't sound hip, and no, it doesn't make you sound like a tech professional. No wonder new technology is so boring now. Now I feel better!
  40. 2 points
    https://doc.qt.io/qt-5/qtwebengine-webengine-quicknanobrowser-example.html I have downloaded and installed Qt 5.9 on my build environment (8.1x64 on my same xp pc just for running vs 2013 ) I am trying to build my own browser namely dragonzilla . I wish to make it very simple,fast,lightweight and sse compatible.
  41. 2 points
    Microsoft released new Insider build of Windows 10.... I have tested it , more craps are added with more bloatware.. When Microsoft will listen to its customer ? here their major improvements but where is performance improvements ... I am wondering how many days these things will go on. When Microsoft will wake up? We fixed an issue resulting in the Facebook Messenger app failing to accept the enter key when sending messaging in recent flights. We fixed an issue where the “New” text displayed under the names of newly installed apps in Start wouldn’t go away after launching the app. We fixed an issue where using the letters in Start to jump to different locations in the alphabet wasn’t consistently working in the last few flights. We fixed an issue where local app search in Cortana failed to return the expected app if the user profile directory contained non-ASCII characters. We fixed an issue where pressing WIN + X would sometimes not show the accelerator key underlines. We fixed an issue where when the People button was present in taskbar, and toast-only banners (for example from ******* 2016) were sent, the Action Center badge counter would become inaccurate. We fixed a bug from recent flights where upon unlock you’d be bombarded with any notifications that occurred while your PC was locked. If you’d like to review notifications received while your PC was locked, they can be found in the Action Center
  42. 2 points
    I don't know. BTW the project is still alive, I haven't done much this summer but now I have came back from holiday, I will work on it again
  43. 1 point
    well the point of him is to say that his upgrading is gone WTF. and well I think it's certainly intresting reading all the fails of w10.
  44. 1 point
    I have no words to describe the mess Microsoft created in the font rendering in Windows 10. Just look at this explorer window. Some elements like title bar and address bar have a grayscale antialiasing, the rest has cleartype enabled. Ok, let's open ClearType Tuner and select a third option on a third page which is a grayscale cleartype. And guess what, it's still the same! This tool has no effect at all on the cleartype's color settings. Disabling cleartype is no option, as the text becomes a total mess. So the question is: How can I force Windows to use that grayscale cleartype smoothing method on all of the GUI elements? If this is some kind of a new font used on the titlebars, can I use it on the other elements by editing aero.msstyle or shellstyle.dll? p.s. The reason of my post is that I use one display with RGB matrix and the other with BGR, So I have to constantly switch the cleartype's sub pixel matrix to get rid of blurred fonts.
  45. 1 point
    > Testing it so far, the chrome frame linked by sdfox claims to require Windows 2000 SP4 after testing it on Windows ME. Try temporarily changing the compatibility mode on the installer (Msiexec.exe). Else mod the MSI file.
  46. 1 point
    Use HIMEMX, it can make system more stable above 512MB. Never install 98SE using ACPI. There's a reason IBM officially(!) says to install 98SE on my ThinkPad T40 in APM mode and not ACPI. Do you have DMA enabled? Do drivers work in 32bit protected mode (no errors in the last tab in System properties about compatibility mode?) Can you try different graphic drivers? I use Omega Drivers too, but you can try official T40 ones: https://www.techspot.com/drivers/downloadnow/3415/?evp=248e71de1f89703e55b98a0dba7e16bc&file=1 Try removing modules from laptop one by one (wifi card, modem, bluetooth, what can you) and see what removal makes system snappier. Try changing every BIOS option you can, especially disabling all modules you can (serial, parallel, infrared, wifi, ethernet, among others).
  47. 1 point
    ARM-based laptops with Windows, again! The first attempt at ARM PCs, which ran on Windows RT, was an unmitigated disaster, and it left many users skeptical of the idea. But Microsoft hasn’t given up, especially as 5G starts to become a reality and cellular connectivity in PCs becomes essential. Microsoft announced that next year PCs will be available with Qualcomm’s ARM-based Snapdragon 835, which is primarily for smartphones. Super-thin laptops will get integrated modems and a long battery life with the chip. The ARM-based PCs will run Win32 applications that run on regular x86 PCs via emulation. For now, no PC maker has announced ARM-based Windows PCs—manufacturers may be cautious in light of the Windows RT fiasco. There are also many challenges. Snapdragon isn’t as fast as high-end x86 Intel or AMD chips, and won’t support 64-bit applications initially. Also, emulation may limit the ability to exploit hardware acceleration.
  48. 1 point
    I'm looking at getting my Ryzen system working with Vista. Getting the USB 3.x drivers in is probably gonna be the biggest hurdle. It runs 7 like a charm, but for a friend of mine who likes Vista, I'm looking to test Vista on it too. AMD uses ASMedia for a lot of their chipset, and ASMedia is known to support Vista to an extent, so we could get lucky.
  49. 1 point
    When will Microsoft actually start listening to the people? Guess never, at this rate. Windows 10 is designed to be a dumbed down, cash cow for folks who just want the latest stuff and trust MS to keep things in check. Good luck with that!
  50. 1 point
    NEWS: I was able to load windows media player 10.... It's a little buggy because there are some missing functions I have not added yet, but now it loads