Leaderboard


Popular Content

Showing content with the highest reputation since 03/25/2017 in all areas

  1. 9 points
    TL;DR, there's now an easy way to enable MP4 (H.264 + AAC) HTML5 video support in Firefox on Windows XP using the Primetime Content Decryption Module plugin by Adobe (distributed by Mozilla). Meaning, you could get rid of Flash (with some caveats). The irony of course being that you'd have to use another thing by Adobe , but at least it's something not as prone to security problems. IMPORTANT: If you're here because MP4 video has stopped working after you upgraded to Firefox 52.0, see this post. If you still have problems, make sure you have all of the required preferences listed below and their values are set correctly. (EDIT March 6, 2017) If you're here because MP4 video has stopped working after you upgraded to Firefox 49.0 or higher, that happens because 49.0 introduces a new pair of preferences. You now need to set media.gmp-eme-adobe.visible and media.gmp-eme-adobe.forceSupported to true; media.gmp-eme-adobe.forcevisible is no longer used. Toggle the Primetime plugin to Never Activate and back or restart Firefox for the pref change to take effect. (EDIT September 7, 2016) NEWS July 26, 2016: Unfortunately, but maybe not all that surprisingly: Primetime CDM will not be getting official support on Windows XP after all. Says a Mozilla developer: Not to worry though, this does not appear to have any near/medium-term (at least <=FF51) effect on forcing the plugin to work with the same workarounds we've been using all this time. However, just in case Adobe compiles some XP-incompatible Windows APIs into future plugin updates, you may want to save a copy of the gmp-eme-adobe folder from your FF profile or download the v.17 distribution package. ( @sdfox7has kindly archived a copy.) Technically, this plugin has been added to FF for DRMed HTML5 video, but it can be used to play non-DRM as well. It's not officially supported on XP, but hey, neither is XP itself, right? I've been trying it out with FF 46 (later also confirmed with 45, 52 ESR and 47-52) on XP Pro SP3 x86 (with POSReady updates, though I doubt that matters any) for about a week now, and the experience has been pretty encouraging. The vast majority of HTML5 videos have worked without a hitch; ~5% have had 1-2 temporary freezes (the video stops, the audio continues with some crackle), which can be easily worked around by moving the video position slider back a bit and then forward again to where the freeze happened. I've seen only one (1) case of a show-stopper error message about "corruption or unsupported features in video" (quote not verbatim) that couldn't be worked around by jiggling the slider (not a crash, just an error message and the video stopped). You may not necessarily be as lucky, though, as the reason the plugin is not included by default by Mozilla is its reported crashing on some high profile sites. (If you're interested in getting this to work on Windows 2000, be sure to read @blackwingcat's post below in addition to this one, and why not his blog posts (1, 2) as well (in Japanese, but with screen shot images).) The way to force the installation and operation of Primetime CDM is to add/set the following preferences in about:config : media.gmp-eme-adobe.enabled (boolean, true) media.gmp-eme-adobe.forceSupported (boolean, true; FF 49.0+) media.gmp-eme-adobe.forcevisible (boolean, true; FF 45-48, no longer used in 49.0+) media.gmp-eme-adobe.visible (boolean, true; FF 49.0+) media.gmp.decoder.enabled (boolean, true) media.eme.enabled (boolean, true; defaults to false if you downloaded a DRM-free version of FF; thanks @heinoganda for pointing this out) 45.x.x ESR users: also change media.gmp-manager.url or the Primetime plugin won't get downloaded for you. The default value is "https://aus5.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml", change only the bolded portion as follows: "https://aus5.mozilla.org/update/3/GMP/46.0/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml". The host in your default may be something other than aus5.mozilla.org, you only need to change the %VERSION% part. 52.x.x ESR users starting with a clean profile (or any other profile without an already installed Primetime plugin) should do the same, only replace %VERSION% with 51.0 instead. After this, when you check your Plugins list, you should see a notice about the Primetime plugin getting downloaded shortly. If you don't want to wait, check for updates manually (from the gear button dropdown menu). The plugin files will be placed in the gmp-eme-adobe subfolder under your FF profile. Once it has downloadedd, set the Primetime plugin to Always Activate, Flash to Never Activate (not strictly necessary, but better for testing), and go to Youtube HTML5 video player check page. Both H.264 and MSE & H.264 should have blue checkmarks. You may want to try this test page (kindly suggested by @dencorso) or some Twitter videos to quickly make sure H.264 really is working (with Youtube you can get fooled by WebM getting played instead). In theory, you could uninstall Flash at this point, but realistically it's probably wiser for now to leave it installed and disabled in the browser. Personally, I installed the FlashDisable extension to quickly toggle Flash on some of the sites I frequent that don't support HTML5 video. Some of those insistently serve Flash video to desktop FF without even checking if it can do HTML5 video or not. That can be worked around by faking a different user agent string, but for now I've found it more convenient to just temporarily toggle Flash back on for them. FlashDisable supports the Ask to Activate setting, so you don't have to worry about other sites if you forget to turn Flash off again. Based on what Mozilla devs have been saying on Bugzilla (Unhide Adobe GMP on Windows XP, Hide Adobe GMP on Windows XP in Firefox 46 and 47, Make Adobe GMP available to Windows XP users in Firefox 45 and later) it seems quite possible that this plugin could soon (FF 48+) be made available without having to use any tricks (or pre-release versions), but I suppose it's also possible that the current situation will continue indefinitely (or even that the plugin will eventually be made more difficult to access under XP). Still, why not make use of it while we can, right? Note that HLS streaming is not natively supported with this plugin. It does work on sites coded to use some JS library or player to work with HLS, but not for directly playing .m3u8 video sources. You may want to keep an eye on developments with hls.js in general and firefox-hls in particular if a favorite site of yours falls into the latter category.
  2. 7 points
    Remember all the doom and gloom announced by tech sites all over, that Kaby Lake processors would be incompatible with Windows 7 and 8.1? http://www.makeuseof.com/tag/windows-7-wont-work-intels-current-next-gen-cpus/ http://www.pcworld.com/article/3112663/software/microsoft-made-em-do-it-the-latest-kaby-lake-zen-chips-will-support-only-windows-10.html Well... I managed to get my HP laptop with an Intel Core i7 7500U and Intel HD 620 GPU working, without a single warning symbol on Device Manager. It was a bit tricky though... I had to install the Kernel Mode Driver Framework and User Kernel Mode Driver Framework v1.1 updates, along with a pretty obscure hotfix released by Microsoft, to make Windows 7 support TPM 2.0. http://download.windowsupdate.com/msdownload/update/software/updt/2012/11/windows6.1-kb2685811-x64_191e09df632b70fd4f4b27d4cb9227f7c5a1c98c.msu http://download.windowsupdate.com/msdownload/update/software/updt/2012/11/windows6.1-kb2685813-x64_22a969bada171678b0936bb320e6a7778e8adc07.msu https://support.microsoft.com/en-us/help/2920188/update-to-add-support-for-tpm-2.0-in-windows-7-and-windows-server-2008-r2 There was no USB support after the fresh install, so I had to put the essential USB 3.0 drivers on a CD-RW I had laying around. Aside from that, Intel also really doesn't want you to install Windows 7 on their new platform... The GPU drivers were compatible with 7, but the HW IDs for the new iGPUs were exclusive to the Windows 10 part of the file. All I had to do was copy paste them to the 7/8.1 section, and it installed without any problem. Also, the Intel Dynamic Platform and Thermal Framework drivers were only available for 10... Had to search the HW IDs on google to find older compatible versions. Now I should finish setting up the system, and see if I can get updates. Will report back
  3. 6 points
    Blurred fonts problem in FF 52.x ESR can be easely solved: type about:config in address bar, press Enter, press "I'll be careful, I promise!" button, search for gfx.content.azure.backends variable and change it from direct2d1.1,skia,cairo to direct2d1.1,cairo (remove skia). Then restart Firefox.
  4. 5 points
    Special Thanks to Russian Guys of Driver Pack Team ,BlackWingCat, Four Finger,IVAN Intel HD 4200\4400\4600\P4600\ P4700\5000\5100 Iris DRIVER :: 32BIT LINK :: http://drivers.drp.su/Video_Intel-XP/Intel/FORCED/5x86/Haswell_6.14.10.5445/Intel-FORCED-5x86-Haswell_6.14.10.5445-drp.exe 64BIT LINK :: http://drivers.drp.su/Video_Intel-XP/Intel/FORCED/5x64/Haswell_6.14.10.5445/Intel-FORCED-5x64-Haswell_6.14.10.5445-drp.exe 32Bit Leaked :: https://web.archive.org/web/20131108095246/http://downloadmirror.intel.com/22875/a08/WinXP32.zip Intel Skylake Graphics :: Intel LAN Latest :: 32Bit :: http://drivers.drp.su/LAN_Intel/Intel/FORCED/5x86/OLD/Intel-FORCED-5x86-OLD-drp.exe 64Bit:: http://drivers.drp.su/LAN_Intel/Intel/FORCED/5x64/OLD/Intel-FORCED-5x64-OLD-drp.exe Management Engine Interface :: 32bit:: http://drivers.drp.su/Chipset/Intel/WinAll/Chipset/9.4.0.1007_HECI/Intel-WinAll-Chipset-9.4.0.1007_HECI-drp.exe intel(R) Display Audio 32Bit:: http://drivers.drp.su/Sounds_HDMI/Intel/FORCED/Audio/5x86/2807/Intel-FORCED-Audio-5x86-2807-drp.exe Bluetooth Hands-free Audio Device 32bit :: http://drivers.drp.su/Bluetooth/CSR/Allx86/CSR-Allx86-drp.exe Bluetooth Stereo Audio http://drivers.drp.su/Bluetooth/CSR/Allx86/CSR-Allx86-drp.exe More will be added soon Please stay tuned
  5. 5 points
    StartIsBack++ 2.0.2 http://www.startisback.com/StartIsBackPlusPlus_setup.exe (Not marked as beta since apparantly nobody installs beta versions) This version addresses all feedback received since 2.0 release.
  6. 5 points
    Well that didn't take too long to fix! I now have version 9.4.49 running quite happily on XP, and the only thing you have to do to make it communicate with the Dropbox servers is run the executable in compatibility mode for Windows 2000! So, it looks as if it looks specifically for XP and blocks it, but an even older OS is perfectly acceptable! Go figure! I found that with a bit of research of course, I didn't find the answer all by myself! It won't let you in with an old version of the client, so what I had to do was uninstall my version 2.10.52.0, and then find a copy of 3.18.1, which may well be the last that will install on XP from my researches. It installed fine, but still wouldn't let me in because it still said it was an old version, but then, lo and behold, it updated itself to 9.4.49 (the current version) and just carried on working. So, normal Dropbox service resumed, at least for the moment! As always, there's no way of knowing how long this will last for, but I'm very pleased that it's OK again for the moment!
  7. 4 points
    You won't even have to do that apparently. I've been doing some searching, and all you have to do is edit wuaueng.dll so that IsCPUSupported always returns true. Here's some information I found on it: https://github.com/zeffy/kb4012218-19 Edit: I just tried this myself, I have a newer update that changed the patch, so I made a patch myself. I can see Windows Update again and get any update I need again. Can confirm this works.
  8. 4 points
    I think a lot of varying opinion could be traced back to two facts: No two folks do quite the same things with Windows. Everyone customizes it differently to suit their needs and tastes. Some don't customize it at all and some turn it into something that only vaguely resembles what Microsoft delivered. Most of us have been through using some newer operating system releases since XP, and in each case we likely found the transition disruptive. But then we got used to the new system and learned to run it adeptly. Personally, I tweak my OS quite a lot, and I have found Windows 8.1 - heavily tweaked and augmented with 3rd party software - to be the best so far at what *I* need Windows to do. I've done the same amount of tweaking (and RE-tweaking) of Windows 10 on a test system, and I have it set up very nearly as well (most of the same techniques and software effective on earlier versions work on Win 10)... The biggest problem I see is that Microsoft no longer WANTS us doing this sort of thing, so it's a PITA to re-tweak over and over again, every time they release (or even update) it. Trying to use a customized Win 10 is akin to paddling against a rising current. I have better things I'd rather worry about. Yes, I know about the CB vs. CBB vs. LTSB and that I could probably use one Windows 10 release for longer than 8 months if I were to want to, but it's just not the same as having Microsoft fully support it for a period of years. Years are what it takes to stabilize something as complex as Windows fully, so that it can run for months under hard usage. But it's all good - I have Windows 8.1 that way; Well-tuned, running smoothly for as long as I care to run it, and it still does everything that the parts of Windows 10 I would care to run can do. For what it's worth, I have the new release of Windows 10 all tuned up with the exception of Aero Glass for Win 8+, which isn't yet released in a version compatible with Win 10 version 1703 build 15063. Overall it's a little slower, a little more bloated, and from what I can see without ANYTHING new that improves on what I use Windows for one bit. In a way I'm happy Microsoft has failed to implement any new "must-haves"... It leaves my current system stable for me to just work with. -Noel
  9. 4 points
    Big Muscle, I was just thinking people would like hearing any thoughts you have about the new version. I know I would. I was just dropping a hint that folks, myself included, really like your software and hope you'll continue to develop it (though I wouldn't blame you if Microsoft has made you tired of having to re-develop it). You've done such good work in the past people are hoping you'll continue, that's all. I had build 1607 build 14393 running (and looking) very nice, in no small part because of your fine work. I've been using - trying to use - the Windows 10 out-of-box UI while testing version 1703 build 15063 and frankly it sucks pretty hard. And of course I'm indebted to you for making my Windows 8.1 set up the system I can count on continuing to use on my real hardware. Thank you! -Noel
  10. 4 points
    Sounds like a good idea to me. Perhaps a way to help keep this thread focused would be to open a new topic on version 1703 build 15063.xxx. -Noel
  11. 4 points
    If you'd like I can also create a Server 2008 updates for Vista repository on my Mega account... I think it will be more useful for Vista users, since 8.0 users have the Monthly Rollups, whereas Server 2008 still delivers updates the old fashioned way (that is, seperate KB for each update).
  12. 4 points
    I have been using linux since last year, and it not bad. Slackware Linux in case someone asks. Its nice for the most part. Win 7 is the end of the line for me. I still use Win98/WinXP but not as much.
  13. 3 points
  14. 3 points
    Winaero covered about April 2017 updates in this article: http://winaero.com/blog/new-cpu-lock-windows-restrictive/ I guess every rollup from Microsoft will include this artificial "lock" to break updating functionality so you can just turn off updates entirely for Windows 7/8.1 if running these 7th gen or later CPUs. I would still choose to run unpatched Windows 7/8.1 than to use the malware called Windows 10!
  15. 3 points
    Hi Guys! When I mean official I mean I am making it official that I think it is the worst ever... While I can understand that Microsoft want a OS that works on all platforms - they fail to recognise the genuine complaints of long term users! Computers are getting more powerful every day, screens are getting larger and more advanced. and yet we are given a OS that is basically designed for a telephone screen. What happened to nice gradient colours etc? It is so **** boring? Your general users do not care what improvements are made to the engine...they want it to look and feel good as well! A telephone is a telephone in my opinion and I want an OS that looks good on the ever increasing sizes of desktop screens! The start menu is a mess! Once again nothing is logical about the setup of things.... If this is the best they can come up with I will keep one computer as Windows for my customers and then the others as Linux.
  16. 3 points
    Some news on telemetry we have now at least some data (hoiw much reliable it's a whole different thing): https://www.theregister.co.uk/2017/04/06/microsoft_windows_10_creators_update/ jaclaz
  17. 3 points
    The BIOS maps PCI, AGP, and PCI-E Configuration and Devices to Memory Mapped I/O Space. Normally these are mapped downward from the APIC and BIOS area at the top. Due to PCI alignment restrictions there are often fairly substantial gaps in these allocations. This area is not available for System RAM. Most, not all, Motherboards can remap the Physical RAM, that would otherwise be useless, up into the 64-Bit Address Space so that it can be used by 64-Bit Software. For example, if you have 8GiB of RAM and 1GiB of Memory Mapped I/O Space, the RAM would be mapped as follows: 0-3GiB -> 0-3GiB (32-Bit Space) 4-8GiB -> 4-8GiB (64-Bit Space) 3-4GiB -> 8-9GiB (64-Bit Space) or 0-3GiB -> 0-3GiB (32-Bit Space) 3-8GiB -> 4-9GiB (64-Bit Space) depending on architecture. Large Video Cards can put a serious dent in the available 32-Bit RAM. Having PCI-E also takes up a large block for it's Extended Configuration Table.
  18. 3 points
    When did capitalism need a reason to sell anything? If the trend will keep, not for better. Major systems will be more like smartphones, if I can take a guess. According to netmarketshare, not really. I has grown 1/3 of its current state within 2 years, but consumed Mac users instead of Windows share. Actual 2,05% Is pretty close to the third sigma. See above, It's actually getting better ^^.
  19. 3 points
    Well, make sure you do provide us with a good how-to, when you consider it good enough, so that we can learn from your hard work. This sure is an important step into ensuring a long life for Win 7 Ultimate SP1 (the last decent NT-OS in the family). Keep on the great work!
  20. 2 points
    That's definitely the right way to do, no chopping i use similar approch i can actually "prevent" installing most of "unneeded" system apps with deleteing one registry key for each prior installation (or during setup pass specialize) set key=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\InboxApplications FOR %%i IN ( holocamera holoitemplayerapp HoloShell PPIProjection AppRep.ChxApp ContentDeliveryManager CortanaListenUIApp Cortana Holograms HolographicFirstRun ParentalControls SecHealthUI SecureAssessmentBrowser XboxGameCallableUI ) DO ( FOR /F %%a IN ('reg query %key% /s /f %%i /k 2^>nul ^| find /i "InboxApplications"') DO IF NOT ERRORLEVEL 1 (reg delete %%a /f 2>nul) ) note: in ver 1703, preventing Cortana will make Start Menu greyed (functional but not clickable)
  21. 2 points
  22. 2 points
    If you're looking for an alternative, Burp Suite Free Edition proxy works splendidly for me with Opera 12.02 on Windows ME.
  23. 2 points
    Yeah, my CompSci instructor jeers at me for using 8.1! I finally installed a sandboxed Windows 10 VM to appease him I don't care if people disagree that I'm running outdated operating systems (although 8.1 is anything but old); If it works and does what I need, so be it. I will only upgrade if I either see a quantifiable and/or beneficial improvement (and, with Windows 10, I haven't, and probably never will), or I am forced because of new hardware (when my current hardware dies/becomes too old to be useful, I'll be stuck with Windows 10 and macOS 10.12+, and I'm not looking forward to it). There is the matter of safety, but I feel that at least 75% of that is FUD 50% of the time, and with that, I figure that with good browsing habits and a well configured firewall, it shouldn't be too big a problem. c
  24. 2 points
    Maybe bigmuscle can adapt Aero Glass to provide glass and stripes on accented windows. That would solve problems without kludging. In other news, 2.0.6 is out:
  25. 2 points
    Let's say that it is unusual to have a Facebook page for an OS in development, it must be a sign of the time . jaclaz
  26. 2 points
    Since Microsoft decided to include the CPU blocking patch on all Security Only and Monthly Rollups for Windows 7 and 8.1, once again Windows 8.0 is verified as a great choice, free of meddling, as Microsoft proves it just doesn't care about its failed OS (in this day and age, that's a good thing).
  27. 2 points
    well thats universal rule if you use garbage, you end up in garbage
  28. 2 points
    Well, just for the record a related thread with some actual info for the Registry needed modification and the patch to NTLDR (reboot.pro is half down right now) via Wayback Machine: https://web.archive.org/web/20170324081949/http://reboot.pro/topic/9474-busting-the-myth-about-ramdisksys-xp2003/ but WinvBlock is still a "better" solution IMHO. To have a "tamper proof" system is also possible to use the ETBOOT project, and run XP from CD (JFYI): https://web.archive.org/web/20170224121218/http://reboot.pro/topic/3890-project-etboot/ https://web.archive.org/web/20150401052002/http://erwan.labalec.fr/ETBoot/ jaclaz
  29. 2 points
    Running XP (the whole C drive) in RAM makes it much faster. RAM disks are volatile/non-persistent so all changes to the C drive are "forgotten" after reboot, and the system stays "freshly installed" virtually forever. My machine boots a 700 MB image file that contains a heavily customised nlited XP SP3 system in RAM disk mode using the free WinVBlock driver. Some profile folders like the desktop are residing on other partitions, but basicly the whole C drive lives in RAM. When I need to install apps or modify system settings I boot up in File disk (persistent) mode in order to save the changes I make to the system. (changes are written directly to the image file in this mode) Using RAM disk my ultra slow underpowered 2010 netbook feels a lot snappier and malware can not set up camp because a simple reboot flushes all changes made to the C drive. I'm always running as admin, always months behind on security updates and never had problems with malware infections since I use this system (for 8 years now!). No antivirus installed, but using anti-executables and sandboxie for enhanced security. Sandboxie's sandbox folder contents; Pale Moon browser and The Bat email client (all running sandboxed in RAM) No need to use a third party RAM disk driver when using image sizes <470 MB. XP's ramdisk.sys driver works just fine. Only needs a registry entry modification to make the driver start at boot time. There is a check in ntldr that stops bigger images from loading. If someone patches ntldr 2GB+ images will be no problem at all. I think RAM disks and image files are the way to go if one wants enhanced performance, stability and security. Personally I will never go back to a conventional Windows installation...
  30. 2 points
    Are you referring to what @sanszajnrege said? I'm not trying to be rude, but I wouldn't take someone saying that one update works (and without even elaborating on what specific update they tried) as confirmation that Server 2008 security-only updates work in Vista. Otherwise, the only update I tried (at first) was Powershell 3.0 for Server 2008, but from my understanding (according to a knowledgeable source that greenhill consulted), Powershell 3.0 is completely incompatible with Windows Vista, for some reason. However, I did some more searching on the Microsoft Update Catalog site, and tried several different Server 2008 security updates on Vista, and they all installed just fine, oddly enough. Here's a link to the updates I tried (excluding the Server 2008 R2 updates, the Sharepoint services update, and some outdated security updates for IE8. Also, I only tried those on page 1 of the search results): https://www.catalog.update.microsoft.com/Search.aspx?q=security update server 2008 x64 This is a good sign that May 2017 (and beyond) Server 2008 security-only updates will work in Vista. However, it should be noted that most if not all of the updates I tried have Vista-only versions too, so Microsoft could decide to change something regarding the compilation of future Server 2008 security-only updates (when Vista is no longer supported) that prevents them from installing under Vista. Retracting my last statement about April 11th, it will be the next patch Tuesday that excludes Windows Vista that will give us answers, so make that... May 9th, IIRC? After this finding, my outlook on the situation has changed. I believe that Vista users will be set until 2020, as far as security-only updates go, as long as Microsoft doesn't get any ideas (and at this point, that seems unlikely, given that Server 2008 is no longer in mainstream support). I also doubt that we'll have to worry about incompatible updates, since Microsoft didn't include Server 2008 support in newer .NET framework updates (4.6.1 requires 2008 R2 or later). The only updates I'd imagine wouldn't work would be anything to do with Powershell 3.0. But does that component even get updated at all? I hope I didn't sound rude (that was certainly not my intention), I just don't want people to get their hopes up and then just get hit with disappointment come Vista's EOL. However, like I said, I believe we'll be fine, but I like to take everything into consideration before I jump to conclusions, because Microsoft can be pretty unpredictable sometimes. Best regards.
  31. 2 points
    And - to be fair to the good MS guys - some of the requests/reports may well be exaggerated, and - just as an example - the fact that Geek Squad could not restore operation of the computer and a new one was needed is not proof of anything, actually WHEN someone will report that Geek Squad did actually fixed properly *anything* THEN it will be IMHO worth the news . If the point is that the whole "upgrade" process was done in a reckless and irresponsible way, it has however a lot of merits. jaclaz
  32. 2 points
    Sure, I'd be happy with that, and to return test info to you. -Noel
  33. 2 points
    Would you care to elaborate...? Windows 10 is a long way from being a worthy OS nevermind one that is to replace XP.... bookie32
  34. 2 points
    Poking around the forum, I find there are more compatibility layer projects than I thought. So I make this thread in attempt to keep track of them. It makes sense that at one point efforts be united. List: *VAIO/AlkyForApplications by Falling Leaf Systems This project is long abandoned. Source released. http://alkyforapplications.net/ https://github.com/callen/Alky-Reborn http://demoseen.com/blog/2009-12-27_Alky_Postmortem.html *Extend Kit by BlackwingCat This project replaces OS files directly and comes as an update. Use with care. Closed source. http://blog.livedoor.jp/blackwingcat/archives/1706829.html *Extended XP by Dibya This project also replaces OS files directly and comes as update. Use with care. Closed source. http://www.msfn.org/board/topic/176005-creating-a-full-blown-compatibility-layer/ https://ryanvm.net/forum/viewtopic.php?f=25&t=10631&p=142341 *DllCompat by MySoft Binaries in GIT. Open source. http://www.msfn.org/board/topic/176604-dllcompat-vista-api-extensions-in-xp/ https://github.com/MyTDT-Mysoft/DllCompat *One-Core-API by Skullytrail192 Binaries where? Open source. https://github.com/Skulltrail192/One-Core-Api *XomPie by tumagonx Binaries included in GIT. Open source. https://github.com/tumagonx/xompie/ ---------------------------------------------------------- *Wine3D for Windows This is wrapper of Directx 1 - 11 API to OpenGL. Based on Wine project, open source. http://fdossena.com/?p=wined3d/index.frag ---------------------------------------------------------- If anyone fancies, MySoft and I have a chat on Freenode themed on compatibility layers. See above "uniting efforts" thing. https://kiwiirc.com/client/irc.freenode.net/?#AppCompat
  35. 2 points
    Crap, good or not good, your choice. Both the MacBook and the Dell laptop installed the Cumulative Updates of 15063.13 and 15063.14 with no problems. Time will tell if the April RTM Windows 10 will be stable and usable by the current installed user base. Many current users have already been updated to 15063.13 whether they want it or not. That is the real crap. Windows 7 Pro and Apple OS X are looking better all the time.
  36. 2 points
    @perfecthog05 A good, simple, lightweight browser that works just fine in XP is QTweb (JFYI): http://www.qtweb.net/ jaclaz
  37. 2 points
    Firefox, obviously, will always be the recommended choice. Especially considering that 1. Internet Explorer 8 is a completely outdated (HTML4 only) browser with outdated SSL technologies. At the same time, it will be supported all the way until April 2019 (for a systems with POSReady tweak, of course). 2. Chrome for XP is slightly outdated (49.0.2623.112) but unsupported browser with known security issues, and with outdated SSL technologies (just like IE8 in this aspect). 3. Firefox (current version 52.0.2 ESR) released a week ago and is still the latest version until April 18. Sadly Firefox 53 and later will not work on Windows XP but Firefox 52.X ESR branch will still be supported until June 2018 (hope that for Windows XP too). And, unlike other browsers, it has its own built-in SSL mechanism with certificates management.
  38. 2 points
  39. 2 points
    I would like to highlight that this topic is about Aero Glass for Windows 10 build 10.0.14393. Any discussion out of this topic might be deleted to keep the thread clean to read.
  40. 2 points
    http://win10epicfail.proboards.com/thread/100/interested-participating-tweaker-development-test Please make sure to read about what it does; it cuts deep in some ways. You might need some of the things I disable. Note that some have reported that the App removal process doesn't go as smoothly as I see it go; it might be a matter of timing. -Noel
  41. 2 points
    Down to 77 processes to support an idle desktop, with most of the services running in separate svchost processes. My Windows10ReTweaker.bat file is updated, and as you can see from screen grabs above does a pretty dandy job of removing all the Apps except what's required to support the Settings panel. Aero Glass of course isn't out in a compatible version, but I am hopeful that Big Muscle will get around to updating it for the new version of Windows. I wouldn't be surprised if he's getting tired of having to play catch-up with Microsoft all the time, though. -Noel
  42. 2 points
    Hai guise, https://github.com/MyTDT-Mysoft/DllCompat This is an opensource project meant to make dll wrappers for Vista+ APIs in Windows XP, not unlike the old project AlkyForApplications. Currently provided dlls are: advapi3x, kernel3x, msvcrx, opengl3x, powrprox, shell3x, vcruntime140, ws2_3x Usage: Firstly, put dlls in your windows folder. Next, your application will likely be NT6 app so you need to patch exe header with CFF Explorer, to allow it to run in XP. This patching is not needed for any dlls. Currently, there is no fancy patcher or compatibility settings mode. You have to manually inspect your application exe and dlls it depends on with DependencyWalker. Next, you take all exes and dlls with missing imports and import them into CFF Explorer. Go to Import Directory and replace bad dll import with our version. Check edited exes/dlls against DependencyWalker again. Contributions and reports are most welcome.
  43. 2 points
    I tried only one, but if you look at the files at Microsoft Catalog, they are the same for Vista/Server 2008, so yeah it has got files for both client and server. You're right, if they delete the client files from cab inside the msu, our only hope is to switch tokens.dat to Server 2008, so it is nothing more than using Server 2008 (without MCE for example). If they didn't remove the client files from updates for 8/2012, they shouldn't do that in Vista/2008. You know, Server 2008 gets only security updates, so it is not edition specific. Apparently the applications are checking some licensing values. I'm not a hacker, so I can only guess, but there is a Kernel-ProductInfo entry in tokens.dat which specifies edition (e.g. 1=Ultimate, 7=ServerStandard). We have to just wait, it's only few days remaining.
  44. 2 points
    Probably not, at least not significantly. My excuse for running latest Windows version is that it usually runs the widest collection of software/games. Unless you're fan of UWP apps, I don't see any advantage. Sure, there are some small nice things there and there, but are they really worth it? My main Windows 10 installation decided to crap itself, update KB4014329 just refuses to install with ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE. Usual remedies don't help, neither sfc /scannow nor Dism /Online /Cleanup-Image /ScanHealth find any corruption, tried with /RestoreHealth anyway and specified good install.wim from fresh ISO image, still no go, Windows Update troubleshooter supposedly found and fix some corruption in Windows Update database, nope, still won't install, manually cleaned Windows\SoftwareDistribution after stopping Windows Update, no, that's not it neither. Needless to say, I did reboot between each troubleshooting step and ruled out hardware failures. At this point, who knows if it would even upgrade to 1703 without some fail in the middle of the process. Might just disable Windows Update completely and stay with the current build. Or I could go back to Windows 8.1, that option would also work well for me, it just takes time to set everything back to the way I like it. Either way, the OS should be transparent and not stay in the user's way. Windows 10 seems to be exceptionally good at doing the exact opposite. Now, you're excepted to fight the OS every few months. Not in Microsoft's opinion, you're supposed to take it as it is.
  45. 2 points
    I still use Windows 2000 and Windows 98 on a daily basis. I'm in full agreement that new interfaces just plain suck. I hate the new interfaces where things have to be flat and boxy. Even the Google logo had to go from a nice looking depth to just a plain old flat color. BORING! I still use Office 2000 on both my computers, in the exception for Outlook 2003 on my Windows 2000 machine. We have Office 2013 via Citrix at work and I hate it. Not only does Citrix make Office sluggish, but Office itself is just so much harder to use. Word does have some cool new features to it for designers but there's no reason for the new interface. It's terrible and I have a hard time figuring out how to do familiar tasks. I was a whiz in Office, now I almost have to relearn everything. Another thing I hate that it seems everyone loves using is what they call the "hamburger" button for your menu options. Why? Why does three stupid lines represent your menu? Don't get me wrong, I'm not necessarily against change, but I want to see improvements, not back tracking. Not only has Windows gone backwards, but so has web design as a whole. I used to pride myself in webpage designs and layouts and now all you get are generic colors, flat of course, with bulky looking boxes, and I hate tablet optimized websites, those are just plain stupid. I'm looking to start using Linux and learning it. I've used it before but never truly engaged in the learning curve of it. If Microsoft can't get their act together, which I'm sure it never will, and when my computers stop doing what I need them to do, I'm off to Linux land. I really can't believe with all the outrage in these new OSes that they really take feedback seriously. They collect what we think, and then build what they want.
  46. 2 points
    Hi all I got as far as File Version 15.010.20060.43353 of the "Continuous Track", which was released one year ago (March 8th 2016) and has the tabbed interface: I think people will find valuable Adobe's own ftp links: ftp://ftp.adobe.com/pub/adobe/reader/win/AcrobatDC/ Open the "1501020060" directory and download "AcroRdrDC1501020060_en_US.exe". As per the instructions previously in this thread, unpack (I used 7-zip) into a folder and patch "AcroRead.msi". A free alternative to Orca is Superorca, but be cautious because Superorca instantly modifies .msi installers; there's no "Save" option, only a "Save as" one, which allows for saving the modified file under a new name... To install base version 15.007.20033 on Vista, I changed "Not((VersionNT<601))" under "LaunchCondition" to "Not((VersionNT<600))". "AcroRdrDCUpd1501020060.msp" (windows installer patch) is the file that will update your initial installation from 15.007.20033 to 15.010.20060. My aged memory fails me at this point, what I think I did was to "cheat", so to speak: I installed "AcroRdrDC1501020060_en_US.exe" directly onto a Win7SP1 laptop (without a prior Adobe Reader installation), and (before it got updated further) I copied over the whole installation dir to a USB stick; this was then used to overwrite the initial 15.007.20033 Vista installation... I don't remember whether file "AcroRdrDCUpd1501020060.msp" runs on Vista or not, (Super)Orca can't inspect it... Last stage is to hex-edit DLLs "AcroRd32.dll", "AGM.dll", "AdobeLinguistic.dll" (read previously in this thread) and add "kernel33.dll" and "user33.dll" kindly and selflessly compiled and provided by @smeezekitty (...huge belated thanks ) The next update Adobe issued to 15.010.20060 was 15.016.20039, released on May 4th 2016. Most sadly, @smeezekitty's fixes cease to work at this point, because the devs introduced another Vista kernel incompatibility: I don't possess the knowledge to tell whether this error could be still fixed by another "redirection" DLL by @smeezekitty or someone else... Version 15.010.20060 is already one year old, superseded by many others in between (from 15.016.20039 to latest 15.023.20070). I would be very keen on having one of those later versions made to run on Vista, since they implement the new "DarkTheme.acrotheme", a dark UI which is much softer on the eyes, especially during the night... If I understood right, @Dibya works on XP and has modified the XP kernel accordingly... Can a solution be worked out on Vista OS, too? Please do share here if anyone's managed to have a recent version of Reader DC run on Vista... EDIT1: To prevent your Vista installed version (15.010.20060) from auto-updating to a non-compatible newer version, rename or delete the "Updater.api" file inside "plug_ins" folder. EDIT2: Acrobat Reader DC needs files msvcp100.dll, msvcp110.dll, msvcp120.dll, msvcr120.dll to be present inside app's root installation folder; the "110" flavours belong to MSVC++2010 (should be already present in Vista SP2) and the "120" ones belong to MSVC++2013. If not already present in your system (e.g. via another app or via Windows Update), look for them in Microsoft Download Center: https://www.microsoft.com/en-us/download/developer-tools.aspx Best regards
  47. 2 points
    I've been a Windows Vista fan since day one and i never absolutely never had any problems with it. My first Vista PC was actually a laptop! It was a HP Pavilion dv6000 and it ran the OS just fine. Sure, RTM was kinda buggy but since SP2 it's just like Windows 7.. just better. Yes, i'm still using Windows Vista today, even though my current PC is meant for modern OS like Windows 8.1/10. Most of the modern games released in 2013-2015 run just fine on Vista but since Windows 7 got the DX11.1 update and game developers just started to use this instead, vista is no longer capable of running it. Which is sad because theoretically it could be possible to backport the DX libraries but since no one cares about it.. it might never happen. Now we have to find out (or maybe someone already found out) how to get server updates on vista (using Windows Update) since it's still suported until 2020. I already tried using the server version as a workstation which was fine for the most part but some programs like Steam and other game launchers have problems with the builtin web browser. web browsers are also a big problem on Vista because developers treat the OS like XP now.
  48. 2 points
    No, I liked interface of Vista/7. In fact, when I saw Vista, I understood that this is BEAUTIFUL!! And they had the best Start Menu ever. How could MS drop Aero and Start menu in 8 and 10?! That's when I was angry. Still using 7 at home. "2. RAM Patches still won't be free." :))) "5. Microsoft is going to care even less." Doubt it. Competition from Linux is growing, I think.
  49. 2 points
    What's going to change in 2020? 1. You will probably need a 2160p monitor. 2. RAM Patches still won't be free. 3. Browsers will perform even worse. 4. UEFI will be even more pervasive. 5. Microsoft is going to care even less. USB 3 has proven difficult to debug so no guarantees there. I have no opinion on NVMe as I have no hardware, so it is a maybe.
  50. 2 points
    Hello, I am proud to announce (an unofficial) version 2.0 of Universal Extractor. About It all started about 3 years ago, when I took a look into Universal Extractor's source code to improve some parts of its behaviour for personal usage. Over time more and more features were added, including batch and scan only modes as well as support for password lists for protected archives. After lots of positive feedback from a private group of testers I decided to release my work to the public. As a short overview, here are some key features, which are new in this release: Batch modeSilent mode, not showing any promptsScan only mode to determine file types without extractingIntegrated updater100+ new supported file typesAudio and video extraction for multimedia filesCascading context menuSupport for password list for common archivesImproved optional status box with progress indicatorNew detection methods + more detailed output and error messagesSupport for some extractors not shipping with UniExtract as pluginsResource usage/speed improvements, lots of fixesFirst start assistant instead of installerFull functionality available in no-install versionAuto-using 64 bit versions of extractors if supported by OSA full list of changes can be found here. There are already several inofficial versions scattered around the internet, but this one is by far the most advanced I know of - hence the version jump to 2. As the only modified UniExtract version centrally hosted on GitHub it is easy to file bug reports as well as feature requests, find new releases or get the source code. Alternatively, an auto-updater and a built-in feedback GUI have been implemented. If you want to try out the new version and help to fix bugs, feel free to download it using the links below. Notes If you use an older version of Universal Extractor, do not replace it with version 2.0 as there are some changes, which can probably result in incompatibilities. You do not have to uninstall any previous version, it works along with this. The context menu entries of the new version may not work if an older version's context menu entries already exist, depending on your system. The beta version does not come with an installer, the official release version will do. Just unpack all files, start UniExtract.exe and a first start GUI will help you on your next steps. Some features are experimental, which means that they probably do not work like intended. If there is a problem, feel free to contact me. See the changelog for more information about experimental features. The translations have to be updated. At the moment, there is only a full translation for English and German. If you are able to translate to any other language and if you want to support Universal Extractor, feel free to send me any translations you can do or check existing ones for mistakes. And most important: It is a beta release. There can be some errors, bugs, etc. Use it at your own risk. No warranty for any demages resulting of the use of this software. If you want to share Universal Extractor 2 with someone, always warn about the beta state (or include this text). Download Beta 1 here. Source code can be found at GitHub. More information about UniExtract 2