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 11/02/2020 in all areas

  1. 11 points
    Hi Just made an account here, I have been following threads on this forums ‘anonymously’ for quite some time now, and wanted to share a few words about this. Nothing makes him special, really. For what is worth, I do not like that he did not open source the project. I mean, I don’t know, from my philosophy and point of view, you shouldn’t charge for projects like this, but whatever, that does not matter, I myself ‘donated’ (read: paid) for this software a good few years back as well. Thing is, it takes a lot of time to research these kinds of projects, and yeah, it teaches you a lot, but there is no financial incentive to doing it. Not short term, not long term. So you need to have some spare time which a lot of people do not have much. Like, take security researchers, that do a similar thing, they play around looking with whatever tools they have available to the inner workings of various pieces of software. BigMuscle here did the same for DWM. Yet, security researchers have the incentive that if they find some critical vulnerability, they get paid by Google etc. Hacking DWM serves no one’s business interest, so... you get what I mean. Anyway, developing this kind of software is pretty hard and becomes tedious and boring easily. You work only with closed source code, you have access only to binaries you can disassemble to various degrees and fortunately, for Windows files, Microsoft offers you symbols, which are little pieces of information that augment the binary ‘code’. That’s it, from there on, you have to look and understand all their architecture, how things piece together and so on. This is tremendous work, and even with financial incentives, it takes time, sometimes you get it wrong etc. Also, the appeal to doing this gets even lower because once you publish it, you have to support it, people will like it and demand it gets ‘updated’ with every release of the Windows OS, and in a timely manner of course. And this complicates the initial problem: you have to find ways to patch it in a way that is less likely to break on newer versions, so that you minimize your work when a new update comes. That again, it consumes a few resources, and especially a lot of time. And also, what programmers try to do when they encounter projects like this, is try to reuse old dormant code that’s still in the binary from previous versions, by maybe also looking on binaries from older versions of the software that had what they wanted. It is pretty hard to develop new stuff for a closed source binary with hardly any public interfaces... Now, regarding DWM, it changed quite a bit in Windows 10 2004. A good couple of the methods BigMuscle hooked in pre-2004 are simply not there in the new DWM. Microsoft actually changed a lot of the underlying architecture. What exactly, for what purpose, what is the high level meaning behind it? I did not have time to look enough at it to figure it out. Also, I had a try at this myself as well. I disassembled BM’s Aero Glass a while ago and looked a bit on it a while ago and gathering a few ideas from there, I coded a utility that changed the title bar text in Windows 10 to be centered. “Version 1” was pretty future proof, but had some edge cases which were still problematic, plus it did not do it quite like Windows 8 did it. I researched a lot more and was able to now fix my main issue with it, namely centering the text between the window borders, not the icon and minimize button. But it took considerably more time and effort and hooking to achieve this minor effect. I looked on DWM a bit more (BigMuscle did the same, but probably on way more of it then I did until now) and could ‘easily’ do a lot of stuff. You know acrylic (aka blur behind)? I enabled that on all title bars via DWM, it looks pretty awesome, I’d daily drive that. Imo it looks even better than Aero Glass, but that’s not the point. Point is it can be done, I relatively easily have done it myself, there were some rough edges of course, but I played with it. Some other stuff came up, did not really had time to work on it anymore, at least for the moment. But maintaining the kind of hacks required for releasing a public version of this is insane. People want UIs, configuration etc, for a niche and specialized thing like this, even command line arguments are too much, I’d rather DEFINE some stuff and compile it for each user’s taste. And there also is not a community keen on developing this. A one man army on this is not feasible, but maybe a team, on a public Git could each member write small bits and get somewhere. That’s why I believe, for e.g., that BM better open sourced it. Even in its now broken state with a lot of the code not that useful on newer Windows builds, still, it is a starting point. In a closed binary, without even symbols, it is uselessly lost knowledge, unfortunately, as no one has the time and incentive, as I said, to take a look at it. There are brilliant programmers out there, but this does not pay off that much. Anyway, I write this on mobile. Maybe when I open the PC I could upload a screenshot of my ‘Aero Glass’, but I don’t want to needlessly tease. Because this probably will never ship. An optimistic plan is to integrate this with my previously mentioned tool, but in the state of mess (coding wise) it is at the moment, it may take a while, especially not having a lot of time to work on this. What I can do in the mean time, is leave you a link to WinCenterTitle (https://github.com/valinet/WinCenterTitle), this software I mentioned that centers your title bar text. If you go to releases to download binaries, the latest modifications are in a pre releas version situated there. So that’s the story of it, at least how I see it. Edit: Yeah, also, forgot to say, what is pathetic here is that DWM is closed source, especially considering that third parties cannot really do compositors for Windows. I mean, I blame Microsoft here, it would be so cool to have official, powerful mechanisms to hook into it and do cool stuff. With that, I tell you, in 2 weeks someone will implement, for e.g., the genie effect when minimizing windows and all sorts of crazy stuff. It is pretty much a shame they also have this mess lately (some stuff that should be in DWM is in Explorer for some reason, like Win Tab, Alt Tab, Snap Assist etc) and also do not realistically look forward to collaborating with the enthusiasts; DWM is actually a pretty decent compositor and window manager.
  2. 6 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201121-ffb32e0-uxp-a89597b5d-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201121-ffb32e0-uxp-a89597b5d-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201121-ffb32e0-uxp-a89597b5d-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201121-86b6cb4c2-uxp-a89597b5d-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201121-86b6cb4c2-uxp-a89597b5d-xpmod.7z Official UXP changes since my last build: - Issue #1280 - Follow-up: Get rid of HPKP pinning mode. (5ef801fdc) - Issue #1391 - Disable DOM Filesystem/dirpicker APIs by default. (5262e01a4) - Issue #1682 - Remove vibrator DOM interface and support code. (13f505539) - [libjar] Fix inflation logic. (870fd86e1) - Issue #1683 - Update Brotli lib to 1.0.9 (d86f49ba5) - Issue #1683 - Update libjar module. (2d8013526) - [packager] Optimize archive accesses. (6d2e301d9) - [toolkit] Add optimized UI code format option (511ac54ca) - Revert "[toolkit] Add optimized UI code format option" (8aa935553) - Issue #1684 - Remove global UA override preference and supporting code. (18df01eb5) - Revert "Issue #1684 - Remove global UA override preference and supporting code." (3abb8e28a) - [UA] Change default compatibility mode version to 68.0 (6bc5748b0) - Issue #1667 - Part 1: Define _pthread_self if it is not already defined in jemalloc (b6d909ad1) - Issue #1667 - Part 2: Add MacOS 11.0 Big Sur widget compatibility This involves refactoring the vibrancy and OpenGL/Pixel rendering changes contained in the following Mozilla meta bugs: 1496823 and 1491445 Also add Big Sur to the features tests and update popup menu look and feel based on Mozilla bug 1656301. (fa5aba4c0) - Issue #251 - Move chrome packaging options to ac configure (ecb827c5c) - Merge pull request 'Get rid of HPKP pinning mode leftovers' (#1680) from adesh/UXP:cleanup-hpkp-pinning-mode into master (241f06bc5) - Issue #1667 - Part 3: Fix OpenGL load and runtime issues on Big Sur This fix is included in NSPR 4.27 and Mozilla bug 1652330. Also put a main thread check in the cocoa draw callback. (2f3cf3c8c) - Issue #1686 - Align a keybinding definition with the others (85dc118aa) - [gfx][Skia] Hold mutex while accessing shared SkImage data. (31a64578e) - [xpcom] Fix GetWindowsFolder storage (bd061ac04) - [parser] Make the refcount of nsHtml5OwningUTF16Buffer atomic. (4782e8dfa) - [xpcom] Don't use realloc for shrinking nsTArrays when allowRealloc is false. (887fface5) - Merge pull request 'Resolve various issues on Big Sur' (#1685) from dbsoft/UXP:master into master (577148710) - [http] Use a copy of nsHttpConnectionInfo. (1864bbec2) - [dom] Remove attributes from descendants when setting sanitized style. (eefaee906) - [sfnt] Fix heap buffer overflow. (76d62cfc3) - Merge pull request 'Align a keybinding definition with the others' (#1687) from vannilla/UXP:align-key-definition into master (074d19477) - [webrtc] Only init WebRtcAec callbacks once (a89597b5d) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Back-end branch pointer up date (Unstable 2020-11-02) (75097f19e) - Back-end branch pointer update (Unstable 2020-11-14) (07d3f0a17) - Update back-end branch pointer and leverage libjar improvements. (86b6cb4c2) My changes since my last build: - skipped Pale-Moon changes about libjar for better compatibility on hacking around for users
  3. 6 points
    So, as requested, I am back with an update: I have pushed modified code in a new branch of my WinCenterTitle project: https://github.com/valinet/WinCenterTitle/tree/glass . Feel free to have a look (“aero” stuff is in dllmain.c). I have not polished it, but it is not gigantic, so it is straightforward to understand. I hook functions and mess a bit with DWM. To understand how I came up with those things, there are some comments, but you can also disassemble uDWM.dll using IDA or Ghidra and start with checking the functions I hooked. At the moment, there are obviously issues: window borders overlap the “1px thin” borders in Windows 10, as in previous versions of the OS, all windows are “glassed”, even child windows and popups, which should be excluded, the frame color gets out of sync with the stuff behind when rearranging windows. That’s what I found out from my testing. Anyway, maybe this is a starting point. Let’s work there. I attach a small screenshot to have a visual representation of what I am talking about. Lastly, thanks for the kind words, I am glad my message was well received, and also I as well hope maybe we gather a few people who are interested in developing this a bit more, in the open, so we can all benefit. Thank you. P.S. Is MSFN blocked in Europe or something like that, because of GDPR compliance or...? I am from Romania, we do not have any internet censorship laws, so this is definitely weird: I keep getting a timeout when attempting to access the web site. It happens both at home and at work, different ISPs, tried with Google’s DNS, no dice. It always “takes too long to respond”. For now, I have installed a free VPN on my phone and I write these messages on my phone, but I was wondering if you have any idea why this might happen.
  4. 5 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201114-ffb32e0-uxp-4aeaea919-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201114-ffb32e0-uxp-4aeaea919-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201114-ffb32e0-uxp-4aeaea919-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201114-fcd19efc9-uxp-4aeaea919-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201114-fcd19efc9-uxp-4aeaea919-xpmod.7z Official UXP changes since my last build: - Issue #1677 - Part 3: Create shim definitions for V8-specific code in new regexp implementation (cb0208163) - Issue #1677 - Part 4: Implement shim for regexp (77746f1d9) - Issue #1677 - Part 5: "Simplify" regexp re-import process (and re-import from later revision) (51468e998) - Issue #1677 - Part 6: Implement NativeRegExpMacroAssembler for new regexp import based on irregexp/NativeRegExpMacroAssembler.cpp (c732425e1) - Issue #1677 - Part 7: Add unicode/uniset.h to check_spidermonkey_style.py for some reason (74ebcea40) - Bug 1328948 - Add is(), as() to Cell. (4694c6096) - Bug 1466909 - Use AddLvalueReference for UniquePtr's operator*(). (e8a6ee355) - Issue #1679 - Part 1: First pass account for some of the refactoring differences in regexp-shim.h (0ba1d49ae) - Issue #1679 - Part 2: Some small issues to address buildability. (4aeaea919) No official Basilisk changes since my last build. No official Pale-Moon changes since my last build.
  5. 5 points
    I miss those days when the tech industry had quality control, the user had more control of things, and everything was well-designed, well-tested, stable and bug-free. And there were actual improvements without horrible regressions, without the "modern" redesigns i.e. skins with reduced functionality.
  6. 5 points
    What part of me says "I play Roblox"?
  7. 4 points
    I am offended that I was born at the wrong moment and at the wrong time. I want to see the internet from 2005-2009, I don't want to see the current situation with the unnecessary staff and dull interface. I want to see the complete openness of people on the Internet and their kindness to me. I want to see how Windows was made lovingly and stable, not 10, which is filled with surveillance and unnecessary services. I want to see the past of the internet and what it was like.
  8. 4 points
    I got the COD Modern Warzone "sort of working". https://prnt.sc/vpeur2 Textures are black and kinda glitchy. Also random freezes. But it actually launches now! Any tips for fixing the textures problem? Oh I forgot I'm using this: https://github.com/HansKristian-Work/vkd3d-proton/releases This was only d3d12.dll to properly launch the game
  9. 4 points
    For those with access to the MEGA folder, you will notice two .7z files: vistaexkernsetup_11222020.7z is an installer for the newest set of extended kernel files. Must be run as admin. One improvement in the new files is the removal of subsystem version checking, so you don't have to change Firefox's Subsystem version from 6.1. SetWaitableTimerEx has been added as well, which allows Office 2019 setup to run, but its version check is very complicated. Another function needs to be added for Office Click-to-Run components to run anyway: mfplatsetup.7z is an installer for Windows 7's Media Foundation files, which are used by recent Firefox-based browsers.
  10. 4 points
    This is the original version of Teardown, which uses a Windows 10 exclusive API function, SetProcessDpiAwarenessContext, running on Windows Vista with an upcoming update to user32.dll: Later versions of the game no longer use this function and as such will work normally on Windows 7, 8.x and 99.9% sure, Vista, though I have no proper way of testing DX11 games on Vista due to the age of my GPU. There are also other games known to use this function, so even though the developers of Teardown realized the demand for their games on older platforms, others may take a different attitude and force users onto the latest versions of Windows 10 to use their products. So, this will allow Vista/7/8.1 users to be prepared for such a future event. Since some interest has been shown in donations for my work, I have set up a method for users to contribute financially for this and some of my other works: https://www.patreon.com/win32
  11. 3 points
    I have installed the extended kernel on a Vista x64 VM last night, and I tried running the latest Firefox ESR (78.5), and I got the same error as @jns629 at first. Looking at @tamarindojuice's response, I decided to follow his advice to jns629 and patch firefox.exe. And it worked! However, I'm a little concerned that firefox.exe needs to be patched like this with every update, which can get annoying. So, with that in mind, is there a way I can automate the process somehow? I mean, it's of course not hard to do manually, but I'm nevertheless curious. c
  12. 3 points
    Summary: For a long time, there have been 2 choices for extended kernels and both of them have their exclusives that aren't present in the other extended kernel. WildBill's extended kernel has many exclusive ntdll functions, SxS support, and a few exclusive functions in other files. BlackWingCat's extended kernel has many exclusive kernel32 functions (and some in other files). The big issue is that ntdll and kernel32 cannot be mixed, forcing people to choose between a better kernel32 or a better ntdll. The main goal of KernelXE is to eliminate this issue. Beta 3 (v0.2.3) Information: General: KernelXE will have a new versioning system. KernelXE R2 Beta 3 will be v0.2.3 and newer versions will exclusively use the new versioning system. KernelXE v0.2.3 and newer versions will have a digital signature. XMNTCert is required for any of my digital signatures to work and the installer is available to download right now. Expected release date range: 12/3/2020 to 12/8/2020 W.I.P. stuff that may be added to v0.2.3: PAE Support [NEW] halmacpi: Source: KB2479629-v3 Additions: HAL timer fix for Intel Skylake and newer systems More info here. This file is in the private dev folder on mega.nz. Direct message me if you want access to the private dev folder. kernel32: New functions: SetUserGeoID, EnumSystemGeoID (requested by piotrhn) Cleaned up a few functions (more will be done in v0.2.3.1 or v0.2.4) ntdll: Development completely reset from "scratch" (WildBill's ntdll). Added functions: NtLockProductActivationKeys RtlLogStackBackTrace NtDeleteBootEntry NtModifyBootEntry NtAddBootEntry NtEnumerateBootEntries NtQueryBootEntryOrder NtQueryBootOptions NtSetBootEntryOrder NtSetBootOptions NtEnumerateSystemEnvironmentValuesEx NtTranslateFilePath NtQuerySystemEnvironmentValueEx NtSetSystemEnvironmentValueEx RtlDllShutdownInProgress RtlInterlockedCompareExchange64 RtlInterlockedPushListSList RtlIsCriticalSectionLockedByThread RtlNewSecurityObjectWithMultipleInheritance RtlGetLastNtStatus RtlGetLastWin32Error EtwEventRegister EtwpCreateEtwThread RtlRunOnceComplete Nt/ZwReleaseKeyedEvent (Code redirection to ntoskrnl) RtlInitializeConditionVariable RtlInitializeSRWLock RtlRunOnceInitialize RtlWakeAllConditionVariable RtlWakeConditionVariable NtCommitTransaction NtRollbackTransaction NtSetInformationTransaction _CIcos _CIlog _CIsin _CIsqrt _alloca_probe_16 _alloca_probe_8 _swprintf ntoskrnl: Added functions: ExfAcquirePushLockExclusive ExfAcquirePushLockShared ExfReleasePushLock ObSetSecurityObjectByPointer SeTokenObjectType (Nt/Zw)ReleaseKeyedEvent (Not exported, added to KiServiceTable) (Nt/Zw)AssignProcessToJobObject (Nt/Zw)CreateJobObject (Nt/Zw)OpenJobObject (Nt/Zw)QueryFullAttributesFile (Nt/Zw)QueryInformationJobObject (Nt/Zw)SetInformationJobObject (Nt/Zw)TerminateJobObject NtQueryInformationThread NtOpenThread Added custom boot screen with KernelXE info on bottom left: Downloads: KernelXE R2 Public Beta 2 XMNTCert Future Plans: Documentation for each file included in the update package Complete cleanup of all functions in all files. Fix for Dependency Walker and CFF Explorer crashes Full & working CreateActCtxW intelppm.sys from Windows XP Changelog: Public Beta 1: Initial Public Release Public Beta 1 rv2: Added relocations to kernel32 and ntdll (messed up other parts of file) Public Beta 2: Exported real CreateActCtxW as CreateActCtxB to prevent explorer.exe crashing. Added CreateActCtxW stub to take care of programs that call it while fixing the real function. Moved QueryUnbiasedInterruptTime, SetThreadStackGuarantee, K32EmptyWorkingSet, and GetNativeSystemInfo to .text Added idndl.dll, normaliz.dll, and the nls files normaliz.dll uses to the update package. Other information: Programs I use: Relocation Section Editor - Only one that handles huge relocation tables like the one in ntoskrnl. Executable | Source Code Beyond Compare - Super useful and feature rich comparison tool. Paid software. CFF Explorer - Useful for editing headers. PEMaker - Good import and export table editor. Also expands sections. Usenti - Only bitmap editor I can find that doesn't recreate the color pallette. Important for bootscreens. Information: Expanding .patch in ntoskrnl: Since .patch is not directly above .rsrc and .reloc, it cannot directly be expanded. The only section in between is .skin, which is empty space used for boot skin data. It can be expanded, then the header can be changed to make .patch bigger and .skin the original size. Staying consistent when modifying all 4 ntos files: Since there are 4 ntos files, any changes must be made 4 times, and it may be hard to remember everything done. I write instructions for every modification I make as I do them, so I know exactly what I did. This also helps when writing documentation.
  13. 3 points
    @we3fan currently has Chrome 49 on Windows XP, 49 being (as you might already know) the last version to support that OS... Chrome 49 only supports the deprecated CRX2 type of Chromium extension packaging ; however, evil Google have stopped publishing new and updated extensions in the Chrome Web Store (CWS) in that package (.crx) format since the end of last May 2020, making only available the newer format package CRX3, which isn't supported by old Chrome versions (NB: Chrome v64.0.3242.0 is the first one with CRX3 support). The following is an excerpt from an unpublished article of mine: The following depicts what happens when one attempts to install GOYT 1.16.0 on Chrome 49: Previously installed versions won't auto-update, either... SSUAOs in Chromium browsers can be enabled via, e.g. User-Agent Switcher for Chrome : https://chrome.google.com/webstore/detail/user-agent-switcher-for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg 1. First set a Custom UA and add it to the "Chrome" category (under default, this assumes the newly created UA impersonates some other form/version of Chromium), then 2. Permanent Spoof List => domain => youtube.com => choose the previously set custom UA =>add 3. When you load yt, the extension's tab icon will alert you a SSUAO is being used... DISCLAIMER: This was obviously OFF-TOPIC, as it doesn't pertain to any of Roytam1's browsers...
  14. 3 points
    Yeah I bought Curtains. Definitely a worthy purchase. I just played around the titlebar texture I wanted to use in Photoshop to make a blurred transparency and that was it. It works great for me. Sadly, I dont think we'll ever see a real update to this project anymore and can only hope that folks get it going on something open source, as it should have been in the first place.
  15. 3 points
    Matt Oudenhoven (AF's original author) has read and replied:
  16. 3 points
    NM27 is based on firefox(gecko) 38, while NM28 is based on firefox(gecko) 52. it is hard to tell which is "better" since results may vary when you have different point of view to review both of them. NM28 supports more newer features so it can survive in current internet environment but it is more laggy when comparing with NM27.
  17. 3 points
    Yeah, Windows 10 is so bad that I cannot describe my experience in sufficient number of words. I actually wonder what Vista haters think of Windows 10. People called Vista bloated when Windows 10 is 1000x more bloated than any Windows version People called Vista unstable and slow when in reality, Windows 10 runs S L U G G I S H L Y even on systems as powerful as yours, just like Windows ME (Memory Eater) and when those people actually ran Vista on slow XP systems with only 256-512 megs of ram! True, Vista had its issues such as an improper WGA, but yeah, everything was fixed by April 2009 when SP2 came out. What will M$ do to fix Windows 10?
  18. 3 points
    uhjuju! Thank you very much, it has worked! What would be of us without this magnificent forum! about:config media.gmp-manager.url https://aus5.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml Replace %VERSION% by 51.0 leaving it like this... https://aus5.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/51.0/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml Go to Tools + Add-ons + Plugins In the Primetime Content Decryption Module provided by Adobe Systems, Incorporated go to options. On automatic updates mark no. Exit the plugin menu and re-enter. Now next to "no" appears "check for updates". Press and the problem is solved.
  19. 3 points
  20. 3 points
    I hate when people use that responsive web design with some heavy java script on their websites..
  21. 3 points
    Features: Current Youtube-dl and Youtube-dlc executables compiled on Python 2.7.17 with py2exe. Almost all Youtube-dl/Youtube-dlc helper applications (only PhantomJS has been omitted). Easy switch between Youtube-dl and Youtube-dlc. Youtube-dl/Youtube-dlc GUI frontend. Special desktop icon. 3DYD YouTube Source and LAVFiltersXP DirectShow filters. Two media players, MPC-HC and PotPlayer, making use of the above filters for streaming YouTube content. Silent VBS/BAT construct making use of Youtube-dl/Youtube-dlc and easy to configure on a per domain-basis to extract stream adresses from web pages. Five (six) media players, GPAC (Osmo4 & MP4Client), MPlayer, MPV, VLC and QMPlay2, making use of the above construct for streaming video from YouTube and many other sites. One audio player, Winamp 2 for streaming audio from Bandcamp. Google-powered and easy to modify search page to find videos on a per-domain basis. Easy integration in Opera 12 and Firefox (as well as other Gecko browsers). Preconfigured portable Opera 12.02 with some extras thrown in. Minimal trimmed-down Python 2.7.17 environment for easily compiling Youtube-dl/Youtube-dlc executables from python source yourself (including optional experimental OpenSSL 3 (TLS 1.3) files for python 2.7.17 courtesy of fellow MSFNer cmalex). Screenies: Download: https://www.mediafire.com/file/rem5dmuvbu8m8ob/Youtube-dl_4_98SE-ME_Megapack.7z/file Unpack preferably in C:\Program files and follow instructions in youtube-dl\stuff\setup. Any question, please ask but make sure you've read info.txt in the root folder before. Related topic that might be useful: Have fun!
  22. 3 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201107-ffb32e0-uxp-19499014a-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201107-ffb32e0-uxp-19499014a-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201107-ffb32e0-uxp-19499014a-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201107-fcd19efc9-uxp-19499014a-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201107-fcd19efc9-uxp-19499014a-xpmod.7z Official UXP changes since my last build: - Issue #1673 - Part 1: Allow tab-size to accept <length>. (49765b53a) - Issue #1673 - Part 2: Make tab-size animatable and fix typos. (7c2bcc48c) - Issue #1673 - Part 3: Bring minimum tab advance up to spec. (a2c26490b) - Issue #1673 - Part 4: Unprefix -moz-tab-size. (9ffc5e6c9) - Issue #1673 - Part 5: Fix brace style and missed -moz-tab-size reference. (d22717ff9) - Merge pull request 'Fix up -moz-tab-size and unprefix it.' (#1674) from athenian200/UXP:tab-size-length into master (9b1406f18) - [devtools] More gracefully (than a crash) handle stack capture failures. (bb4e9ad1c) - Issue #1676 - Part 1: Split MozTesting directives out of js/src/moz.build (395ef79b9) - Issue #1676 - Part 2: Split CFLAGS and CXXFLAGS directives out of js/src/moz.build (5bf19933d) - Issue #1676 - Part 3: Split DEFINES out of js/src/moz.build (0cdd39ff1) - Issue #80 - De-unify js/src (ec13658ab) - Issue #1676 - Part 4: Split builtin sources out of js/src/moz.build (24a5a7f7c) - Issue #1676 - Part 5: Split devtools sources out of js/src/moz.build (24b835f0a) - Issue #1676 - Part 6: Split ds sources out of js/src/moz.build (eedfa63a1) - Issue #1676 - Part 7: Split frontend sources out of js/src/moz.build (1396383ae) - Issue #1676 - Part 8: Fix up include for selfhosted.out.h (bc450dab4) - Issue #1676 - Part 9: Move DIRS down in js/src/moz.build (957f19d2b) - Issue #1676 - Part 10: Split gc sources out of js/src/moz.build (65eac50e2) - Issue #1676 - Part 11: Split irregexp sources out of js/src/moz.build (3d9bf5d7a) - Issue #1676 - Part 12: Split jit sources out of js/src/moz.build (95e057e73) - Issue #1676 - Part 13: Split perf sources out of js/src/moz.build (383bc182e) - Issue #1676 - Part 14: Split proxy sources out of js/src/moz.build (6f76f1cb3) - Issue #1676 - Part 15: Split threading sources out of js/src/moz.build (2f50f543a) - Issue #1676 - Part 16: Split WASM sources out of js/src/moz.build (1abc696f8) - Issue #1676 - Part 17: Put remaining source files which have debug code ifdef'd behind MOZ_DEBUG (ff355fe9a) - Issue #1676 - Part 18: Move and separate top level sources from vm sources in js/src/moz.build (59511eb8d) - Issue #1676 - Part 19: Split ctypes sources out of js/src/moz.build (cdf46e803) - Issue #1676 - Part 20: Split vtune sources out of js/src/moz.build (fd1b2dc2b) - Issue #1676 - Part 21: Use js-cxxflags.mozbuild in testing code and js shell (d2b6975eb) - Merge branch 'jsbuild-work' (2e0719919) - Issue #1677 - Part 1: Import new V8 regexp code with Mozilla's header modifications (78b3a722b) - Issue #1677 - Part 2: Add build files (19499014a) No official Basilisk changes since my last build. No official Pale-Moon changes since my last build.
  23. 3 points
    can someone try this? I wrote that in 15 minutes. http://o.rthost.win/gpc/files1.rt/oldtube-xul.xpi
  24. 3 points
    OK the youtube crash bug is fixed and commited by backing out a patch that is backed out in mozilla.
  25. 3 points
    Something else: I wanted to thank you, Roytam, for making the New Moon browser available on Windows XP. It expands the lifespan of thousands of computers on this planet. This picture shows a 19 year old P3 with a weak 1 GHz processor running Windows XP, playing a Youtube video in 2020. Hopefully, people from countries with a less developed economy discover this, so they can use their XP machines much longer. Thanks to Roytam!
  26. 2 points
    Hi , first off , I'm sorry to remind : this top is : Share your Windows >Vista< experience! and not about "the look of 7". There's too much to write about the differencies . Some of the ugliest things about Win 7 are : fonts (yes that "true" type ones) - washed out and blurry , oversaturated UI colours , like for ravers at the acid party. I always had the best monitors available , so I can tell. Also , sound , oh boy. It's nowhere near Vista's punchy and sharp audio quality . I have Asus D2 , so I can also tell the difference . Win 7 has fat , thick , flat , ugly taskbar . etc , etc , etc . P.S. Compare Vista's wonderful orb and Win 7 (I don't even know how to name that "acid something").
  27. 2 points
    Good day, I have good news - I was able to get the broadcast on Twitch and the video on Twitter to work on latest versions of Firefox or Pale Moon! Before running the latest browsers, you need to install the extended kernel from @win32 As we know, initially on newer versions of Firefox and Pale Moon, some built-in codecs in Windows Vista do not work, since the Firefox development team simply removed some of the Windows Vista codecs part of the code from the browser. As a result, some sites (including Twitch, Twitter) stopped displaying videos. To fix this, download this archive and extract it to your Firefox or Pale Moon root folder. It simply replaces two files, thanks to which videos or broadcasts will work on those sites on which it did not work.
  28. 2 points
    Do you plan to upgrade to Windows 10 in the next 12 months? No, I have no plans to downgrade to Windows 10, before or after I am in the casket. Nor do I have plans to downgrade from Office 2010. Windows 7 Enterprise/Ultimate x64 and Office 2010 x32 are where it's at! Are you paying for extended support? No, I am not paying for extended support What is the main reason you haven't upgraded? I guess because there isn't any upgrade path from Windows 7. There's only a downgrade path. OK, you want the real reasons... here they are, Microsoft! You shamelessly advertise it as the "latest and greatest Windows ever", when, in actuality, most people either love it or hate it. I'm talking, of course, about Windows 10. As of today, the homepage of windows.com informs us that "the best Windows keeps getting better", when, in fact, it would be more accurate to reword it "the worst Windows keeps getting worse". On the surface, you promise a slew of never-ending better and better enhancements to your posterchild operating system. Yet, you have consistently failed to deliver. Windows 10 launched on July 29, 2015, and few of what you've promised in the years before and since has materialized. Sure, specific one-liners in the update KBs have, but not the overall promised experience. Nearly four years after you launched Windows 10 still unfinished under the hood, your newest operating system has failed to win over the hearts of your longtime customers and loyal fans. It is with a heavy heart that I write this, because I used to be Microsoft's #1 fan. It seemed, for a while, as if they would be the world's most infallible software giant, a corporate legend for the years to come. Well, that time has now come and passed. Your glory days are now over, and the most unfortunate part is that it's all completely your own doing. Talk about a tragedy! We can't call Windows 10 a complete failure. It's a step up from the Windows 8x disaster, albeit a very small one. You've clearly renewed your commitment to security, even if that means aggressively coercing consumers and businesses like sheep in a pen. But apart from that, the truth is that you have let us down, your core longtime customers. As a reward for our loyalty, you have all but abandoned us and left us out to dry. It has become clear to us that you no longer care about listening to your customers, and arrogance and ignorance are now steering the Windows development ship. No doubt, you know that people don't like change. That's been the history of software since there was software. You know we don't look forward to Patch Tuesday and you know we don't like upgrading when told to do so. And we know you don't like that some of us are still running Windows XP. That's why it astounds me why you've tweaked and changed Windows 10 so much that it's now completely different from any of its predecessors. Sure, your investors are happy. Scratch that, they're enthralled. Your stock is undeniably performing better, perhaps, than it has ever before. But you have sold yourself out to investors at the price of your product. For the sake of jumping on the bandwagon and doing what "looks good" — pushing "cloud first" like everybody else, you've ruined what made Microsoft special and different — its commitment to advanced, powerful, professional computer systems. Your niche was the professional world — and your latest operating system caters exclusively to consumers (at least those that are easily satisfied), leaving everyone else behind. You have left your loyal, longtime customers more or less in the dust. Shame on you, Microsoft! People used to give you "M$" crap back in the days for antitrust and standardizing the computer landscape, but this is small potatoes compared with how you have now criminally derailed the Windows operating system. Windows (and even Office, to some extent) used to be a high-quality, reliable, well-packaged series of operating systems. There were a few hiccups over the years (and you know what they were), but by and large, you have produced some of the most rock-solidsoftware, ever. Microsoft was a highly respected software manufacturer, the name in software. Why did this have to change? For years, you were a monolithic software giant, truly a force to be reckoned with. Your software dominated, and you know it. But times have changed. Face it: Windows is losing steam. You're losing market share. And you are expediting it, not slowing it down! People are leaving the Microsoft ecosystem left and right, in drones, faster than ever before. People can see through your façade, and come to the heartwrenching conclusion that you've stopped trying, or at least, stopped caring about us — us, the core users of your products. Your new commitment to what's shiny and fashionable, rather than what's durable and practical, repulses and revolts us all. You have alienated and aggravated so many of us who have been with you since the beginning. There are those who like the flashy consumer craft that's typical of Apple and Google products. But for years, we could count on Microsoft for dependable, practical software. Now, you, the last company we could have predicted would do so, have jumped on the "pop" bandwagon, joining the likes of Apple and Google, and begun embracing consumer fads and trends, with a "want-to-please" mentality that has eaten the company from the inside out. In so doing, you've let down all of us who have come to depend on the old standard of service and quality for which you were known. The old, practical Microsoft has given way to the new, "hip" Microsoft. We realize that you're trying to appeal to young, inexperienced computer users. But you're doing so at the expense of pushing away all your old, traditional computer users, and the sad part is you don't seem to care. Screw all of us traditionalists, you say. Either get with the program, or migrate to Linux, you say. Well, that's exactly what's happening. It's amazing, don't you think, how many people have stuck with Windows for decades — only to come this far and then decide to migrate, not to Windows 10, but to Linux. Indeed, that's exactly what the South Korean government has chosen to do. Perhaps, Microsoft, this should tell you something. At least, it would, if you cared to listen. But you don't — this has sadly become obvious to those of us who have patiently waited for the metro, modern era to end. It's a rude, cold slap in the face, but we can't deny it any longer — it's been the better part of a decade now since you cared to do anything much for your loyal customers, and you don't seem to mind trying to please a few wandering computer users at the expense of alienating your established base. Some people say you've always been arrogant. If this is true, in the old days, this was okay. Maybe you never were the most approachable company, but you made rock solid software. In some ways, you were reminiscent of the old Bell System, a highly structured, monolithic corporate giant that was second to none in quality, durability, and reliability. But now your arrogance is a real problem. Today, you ship crap in a box, and while your customer service has actually improved of late in some respects, it's hardly consolation that that seems to have happened only to handle the increased amount of disgruntledness. In short, the old venerable software giant, once a champion of the business world, has sold itself out and sunk to the level of Google and Apple — trying to please consumers on a whim with poorly executed and fatally flawed products. The result, as we've seen with Windows 8x and Windows 10, has been one embarrassing disaster after the other. It's no wonder, then, that with just 7 months left until the end of extended mainstream support for Windows 7, there are still, according to various browser use stats aggregators, between 30% and 40% of Windows PCs continue to run Windows 7. Given that the free upgrade period has long passed and we're so close to the end of mainstream support, of those that are consumers, many are probably determined to stick with the OS as long as they can. We hardily commend them for this responsible decision. As we saw with the end of Windows XP support, people don't like being told they shouldn't use their favorite Windows OS anymore. And given that Windows 7 is the last in a long line of similar and familiar "tried and true" Windows operating systems, the holdout with Windows 7 is likely to exceed even that which Windows XP experienced. In line wit this, there are even reports that Windows 7 usage has occasionally increased during certain months in the past year. According to ComputerWorld, it's possible Windows 7 will go out of mainstream support with 35% of Windows PCs still running the well-established operating system. While running an unpatched operating system is generally not recommended, it really can't be helped anymore. Windows 10 is such an impediment to the sensible computer user that any self-respecting PC user should seriously consider whether he ought to consider remaining behind. You, doubtless, disagree. In all your infinite wisdom, you think we should mindlessly keep buying your products without reassessing if they truly continue to meet our needs or not. But tell me, Microsoft — why should I upgrade my PC if it will lead to a downgrade in its usability? Why should I make myself suffer? Software is supposed to make my life easier, not harder, is it not? Having used Windows 10 now for a couple years, I've had the privilege of experiencing living computer hell for an extended period of time. There are numerous reasons why Windows 10 takes the cake for some of your worst negligence ever. Days where Windows 10 is not aggravating and counterproductive are few and far between. A laundry list of fatal problems with Windows 10 that is driving your traditional base of customers away is not hard to come up with. If you want to listen, Microsoft, and you want to continue to earn our business, as you have for the past two, three, or more decades, maybe you should reevaluate your current course of action and pursue one that would put your objectives more in line with ours. Don't forget: the customer is always right (you seem to have forgotten). You have reached a critical point in your company's history. You have forgotten about us, the "neglected majority" for too long now. Your support is teetering and waning daily. You can oblige us by fixing the fatal problems that plague the Windows 10 operating system, or you will soon become irrelevant and fade into oblivion. There are many things you would do well to fix in Windows 10 to appease your traditionalist base of users. Here are some of its most critical problems, in no particular order: Unfinished — As it was released in the most unfinished condition in which a Windows OS has ever been released, evidence of tweaking is still under the hood is everywhere. Although Windows 10 places a new emphasis on continous development, which no doubt lends Windows 10 to an ongoing feeling of experimentation, the entire operating system is unusually riddled with "works in progress". Customers are now constant guinea pigs and can never enjoy the stability of a consistent user experience and user interface as with previous releases of Windows. Reliability — Reliability is a major problem with Windows 10. Similar to Windows ME, Windows 10 has numerous quirks that lead to unreliable performance and unexpected activities. When things go wrong in Windows 10, they don't go wrong the way you would expect them to from previous versions of Windows. Windows can unexpectedly overlay on top of the taskbar. The GUI can crash in a way that leaves you with no alternative but doing a hard reboot. Right-clicking zipped folders can cause File Explorer to hang for more than a dozen seconds. These are just the first few of a long list of reliability problems experienced with Windows 10. Given its tendency to fault without warning, it would be idiotic to deploy Windows 10 on any mission-critical system — it's simply not designed for that. Thank goodness for Windows 7 and Windows XP! Bloatware — Windows 10 is full of bloatware, as a quick glance at the default Start Menu on a new consumer build of Windows 10 Home will show. GPOs can be used, of course, to lock all this down, but this should hardly be necessary in the first place. In addition to the kiddy games with which you junk up our PCs, there are a bunch of useless metro apps included in your builds. While a few of your included UWP apps like "Voice Recorder", we admit, can be useful (though we still prefer Audacity), the vast majority of them, like your useless 3D Printer app, for instance, are not of interest to 99% of PC users. If you're going to include default system applications or "apps", at least make them useful, please. Heavy Integration with the Cloud — The "cloud" is one of those overused buzzwords in society today, much like "ecommerce" and "paradigm" once were. Windows 10 takes integration with the cloud to a whole new level. From no integration with the cloud in Windows XP to essentially still none in Windows 7, this is a huge shift, which actually started with Windows 8x. Still, you vigorously encourage consumers to sign in with a Microsoft account, set up their OneDrive accounts, and use Office 365. Clearly, you have caught the "cloud bug", and embraced the "consumer cloud fad", but power users are not interested in the cloud and never will be and have to disable and remove all this unfunctionality. Why not make cloud integration an add-on, as in Windows 7, rather than something that those of us at the top of the PC hierarchy find irksome have to remove? If we wanted to fully embrace the cloud, we'd be using Chromebooks, not Windows PCs! Simplistic Task Manager By Default — The first time you open Task Manager, you'll see a completely useless window listing the programs open on your computer. Thanks, Microsoft, I can surmise as much by looking at the taskbar. To actually use Task Manager like in previous versions of Windows, you have to click "More details". Thankfully, once you do this, you probably won't have to do it again. Still, why is this unnecessary hassle even required? Those of us who are constantly using different PCs in an IT environment can't deal with this type of stuff. Start Menu — The Start Menu in Windows 10 is not a significant improvement over the one that shipped with Windows 8x. It remains a largely elusive, unusable menu based around fancy "metro" tiles that everyone hates. Perhaps this is the biggest "screw you" to corporate users, in an attempt to placate consumers, even though they don't really like them either. You just can't let go of this concept, can you? They say that insanity is doing the same thing over and over again and expecting a different result seems to me like you're trying to push the same dysfunctional interface on users, with a slight tweak, and expecting them to like it. Apart from the fact that it's no longer possible to pin items in an organized linear fashion as in Windows 7, the convenient menu shortcuts to "Computer", "Control Panel", and "Run", among other things, are no longer. Yes, you have small icons on the lefthand column that are all two lines and a circle away from each other — completely useless. Furthermore, the "All Programs" view in Windows 10, which is now what appears in the middle pane in the newest editions, is incredibly bulky. Your aggravating insistence on breaking up programs by letter and showing a large icon for each program makes so much more scrolling necessary than in any prior version of Windows. Way to break a huge UX rule: less scrolling is definitely more! A menu that might not have required any scrolling on a Windows 7 PC requires a crap ton of scrolling in Windows 10. This makes for a terrible user experience! Classic Shell can fix some of your screw-ups, though it's no longer actively in development. What's more, an interface that requires third-party patching to restore lost previous functionality is fundamentally flawed. The Windows 7 start menu was tons more functional — even the Windows XP start menus were way more functional. Like many other things, you had it right before. Your insistence on screwing up something perfectly good that was working well and replacing it with an abomination is frustrating beyond words. All Programs — I already covered how the All Programs view is next to useless, considering how sprawling it now is. But with regards to the actual contents themselves, Microsoft has screwed this up as well. It's hard to say whether it's Windows or Office that screwed up here, but previously Microsoft Office applications all appeared in a single folder (titled "Microsoft Office"), and now, each individual application is lonesomely sitting by itself in the menu. This means "Excel" is nowhere near "Word" anymore. Considering that it made sense for Office applications to all appear together, in their own folder, this move is quite aggravating. Power Options — This is part of the Start Menu, but such a major flaw that it really stands on its own. In Windows 7, the power options were stuck all together, making it very easy to shut down, restart, logoff, etc. Perhaps Windows+Right+Enter shutting your PC down was undesirable, and subject to pranks, but the default power action could easily be configured to something else, like "Lock". In Windows 10, you've split this up again — one to perform power cycling events and another to logoff, lock, or use fast user switching. What's more, the important menus on Windows 10 consist purely of icons (unless you manually expand the hamburger menu each time). While the "Power" menu is at least half-intuitive, what dimwit thought that clicking on your username would be an intuitive way to logout? In Windows 7, clicking your name on the Start Menu would do something completely different — open up a user profile panel in the Control Panel, as one might expect. Why completely rework this? And yes, we know that Windows XP didn't have the unified power menu, either. But it did have clearly marked "Shut down" and "Logoff" buttons that had a clear purpose and were as straightforward to use as could be. Windows 10's power options are neither straightforward nor unified. Microsoft Edge — Yes, we know that Internet Explorer 11 is still there. A good thing, too, for Edge has proved to be even worse than Internet Explorer. It's far slower and proves not to have any special reason to use it — at least IE will work when no other browser does, like when viewing legacy web applications or PSR recording files. Edge is slow, bulky, and altogether limited in what it can do compared to other modern browsers. Edge is an even worse choice for a default browser than IE. Also, the Edge logo is, quite frankly, bug ugly. The Project Spartan logo, at least, was somewhat elegant and appropriate — the actual final Edge logo is, instead, another reminder that Edge is just what IE never should have been. Removal of Classic Theme — The Classic theme, which has been with Windows since the first GUI-based versions of Windows, is no more with Windows 10. This whopper of a neglect is right up there with the disastrous Start menu! This plain but usable theme/scheme has long been the workhorse of Windows in the workplace. Its mere presence is indicative of a straightforward, professional user experience. Furthermore, since Windows XP, it's been a way to "opt out" of the flashy, colorful UIs that Microsoft has introduced since, whether they be the Luna theme typical of consumer installations of Windows XP or the glassy "Aero" theme typical of consumer installations of Windows 7. With Windows 10, the Classic theme is all but gone. I say "all but" only because when explorer.exe crashes, as it frequently does in Windows 10, pressing ALT+TAB to cycle through open programs will — until explorer.exe is restored (which may or may not happen on its own) — bring up the Windows 7 "no themes style" interface exactly (disabling themes in Windows 7 yields a "white" interface that was similar to, but not the same as, the Classic theme). Yet, this interface exists nowhere else in the OS, and only goes to show that Windows 10 is a deplorable mess of inconsistency even in its implementation of unworkable themes. Furthermore, there is no way to opt out of the default flashy themes as, not only is the Classic theme gone, and not even possible to get back by any third-party hack or patch, but disabling themes altogether is not even possible anymore, in the sense of what it accomplished in previous versions of Windows. Terrible Default Theme & Color Scheme — The default theme in Windows 10 is terrible, to put it mildly. The only thing we've nothing against is the default wallpaper, which is decent. But the black color scheme makes the entire operating system gloomy and difficult to use, and the new white theme is equally ridiculous. The contrast is starkly different from the norm in previous versions of Windows. Furthermore, by default, the "accent color", as you call it, is not shown on either the start, taskbar, and action center surfaces or the title bars and window borders. Previously, this is fundamentally how color schemes in Windows operated. Yes, these can be enabled or configured, but why would your default settings suck so badly? Less Control — Windows 10 gives less control to the end user, putting Microsoft in the driver's seat, rather than the customer. So many options in the OS, you take the liberty of tweaking for us as you see fit, even resetting options that we have already set. Furthermore, fewer useful personalization tweaks are available and the overall look and feel of the operating system is restricted to the modern look you want to push on everyone. Control Panel vs. Settings — Here's more evidence of Microsoft's ignorance of user experience. Seriously, what the heck? This is right up there with the Start Menu and removal of the Classic theme as one of your top screw-ups with Windows 10. First of all, the Settings app is a complete joke. The powerful Control Panel has slowly given way to a "modern" Settings app that offers a simplistic interface allowing tweaking of only a small subset of what could previously be tweaked. And, as a UWP app, Settings takes forever to load, while Win32 components of the operating system, like Control Panel, loads almost immediately. UWP apps like Settings are, instead, stuck on a pointless splash screen for seconds. Not only that, but many settings, rather than being migrated from the former to the latter, have instead been dropped and have disappeared altogether. Come on, Microsoft! If you're too lazy to make the switch, then why did you even try? There's not even a good way to predict what might be in the Control Panel and what might be in Settings (or what's no longer in either). Specific options in either can instantly take you to the other one. Pardon our French, but this is a super half-assed job. The only good thing about your inability to follow through with what you started is that some things still are in the Control Panel. But the Settings app was a terribly idea, an attempt to conform with other mobile platforms' conventions, rather than the business and desktop world. Control Panel was great, and the new Settings app is a wash. More Work For IT — Windows 10, in contrast to what you claim, is a complete nightmare for IT. Previous Windows releases allowed IT departments to manage their network in a fairly straightfoward manner. Windows 10 adds so much more chaos to the already hectic mess that is computer management. Now, we have to disable and remove the Windows Store, make sure all your preinstalled rubbish games have been removed, disable Cortana and all your "smart" features, etc. If only all these things didn't ship with the costlier versions of Windows. Inconsistent — This is a huge UX flaw and a moderate impediment to usability. Windows 10, as a whole, is riddled with incoherencies. The incongruity between Control Panel vs. Settings. is the biggest example of this, but such inconsistencies riddle the entire operating system. For example, the volume control in Windows 10 uses the "new" Windows 10 style interface, as opposed to the older Windows 7 style one, by default. At least, it sort of does. If you right-click this and then click "Open Volume Mixer", the old Windows 7-style Volume Mixer instantly appears, which uses the old Windows 7 style volume control completely. Here and there in the operating system, there are these constant reminders that pieces of Windows 7 are still here. While these older interfaces are far more usable than the newer ones, and you would do well to just discard the new ones and put the old ones back where you've replaced them, this makes for a lot more confusement in the daily user experience. I haven't verified recently whether this still works, but Tip #3 of this article explains how to bring the old-style volume control slider back. Thank goodness for registry fixes to patch up your mistakes. Time Consuming — I thought computers were supposed to make life easier. Windows 10 just makes it harder. Things that took a split second to do in Windows 7 take much more effortful thinking and clicking in Windows 10. And the "time-saving" features you introduced are next to useless and only get in the way. For instance, in Windows 7, a quick click on Start → Devices & Printers would take you there. Now, numerous clicks are required: first to the Settings app, which takes an eon to open, then to Devices, then to Printers & Scanners. But wait! If you click "Devices and Printers" on the right-hand side, then you get taken to the old "Devices & Printers" in the Control Panel! (Again, reiterating the gross inconsistency in Windows 10 as exemplified by Settings vs. Control Panel). Considering "Devices & Printers" still (thankfully) exists in the Control Panel, it's not even clear what the point of the "Printers & Scanners" page in the Settings app is for; it's completely useless. Ridiculous Naming Conventions — A lot of things in Windows 10 are poorly named. Names in Windows 7, for the most part, made perfect sense. Sure, there were some initial resistance to changing "My Computer" to "Computer" and "My Documents" to "Documents", but it wasn't the end of the world. Windows 10 is chock full of stupid naming choices. For instance, take the Devices section in the Settings app. The first page that pops up is titled "Bluetooth & other devices". Looking at this page right now, I can't help but wonder what id*** named this page:The logic used to name this "Bluetooth & other devices" makes zero sense. For one, there are zero Bluetooth devices on this page and everything that appears, I suppose, would be a "other device". I see here a keyboard, a mouse, the computer's line in/out and headphone/microphone jacks, the monitor, and an external floppy disk reader, none of which have anything to do with Bluetooth. What on earth caused you to give this page such a stupid name? For one, Bluetooth has absolutely no role in the professional computing world. It's a flashy consumer technology with no role in the corporate world, and using consumer terminology in a business operating system makes very little sense. Beyond that, considering the popularity of things like "Bluetooth monitors", naming this page as if Bluetooth devices take center stage is a sore delusion. To your credit, you've so far left "Devices & Printers" in Control Panel intact, which is the rightful home of these peripherals. This is further evidence of the alienation between you and us. Any computer peripheral found in the workplace is just an "other device", much like how we, your longtime loyal customers, are now just your "other users". Senseless Renaming — Beyond entirely new dumb names that have appeared in Windows 10, like "Bluetooth & other devices", several things have been renamed for no real reason. "Computer" is now "This PC" by default, which makes absolutely no sense. Considering that I currently have 11 mapped network locations, none of which, of course, are physically located on "This PC", calling it this makes no sense at all. This name might have made some sense for the also awkwardly named "Devices and drives" section of "This PC". This is where local media appears, but wouldn't a network location also count as a "drive"? And what's with "Favorites" being renamed to "Quick Access"? Isn't any location that appears on the left pane of Windows Explorer (oops, File Explorer) quick to access? It's no quicker to access any of these locations than it is to access a mapped network drive. The name "Favorites" made logical sense; the name "Quick Access" makes none. And in your attempt to be "hip" and everything we don't want you to be, you've also renamed logon/logoff to signin/signout, which breaks a longstanding Windows naming convention and just makes Windows 10 look more like the dumb service it is rather than the great product it was, or could've been. Your naming strategy seems to have been to make everything as confusing as possible. Evidently that's why you you purposely took perfectly fine names and convoluted them. Clutter — Windows 10 is extremely cluttered. Simply opening up File Explorer to "This PC" reveals a nightmarish mess. At the top, we see 6 or 7 "Folders", a completely useless section that clutters up this view. For one, Desktop, Documents, and Downloads are already accessible through your ill-renamed "Quick Access" section. The Music, Pictures, and Videos folders are next to useless, and, in any case, have no business cluttering up the "This PC" page. For the two in a thousand people who need this, they can navigate to their user profile directory, which can be pinned to "Quick Access", and access these from there. Why clutter up "This PC" with annoying shortcuts to folders that 99.97% of computer users will never use and do not want? "This PC" is not the place for computer shortcuts. You've broken your own longtime rule of only showing actual devices and drives on this page. Yes, there's a registry fix to remove these folder shortcuts, but that's one more hassle for IT departments to deal with. Furthermore, this registry fix isn't perfect. When navigating to one of the folders which was previously shortcuted to from This PC, it will temporarily show up under the This PC umbrella in the lefthand navigation pane. Please, just remove these shortcuts altogether. They have no place in "This PC". For users who want a shortcut to one of these locations, they can easily Favorite it, er, "Quick Access" it. Double Drives — Am I seeing double? Nope, you actually just screwed up again. For some reason, you thought it would be a good idea to duplicate all removable drives in the lefthand pane:AskVG provides much needed instructions on how to remove these for consumers, another in a long line of registry fixes people have had to come up with to fix the numerous problems with Windows 10. Imagine having 4 USB devices connected and seeing not 4, but 8, of them in the navigation pane. This is a poor UX modification without any actual apparent reasoning behind it. I can't imagine why anyone would find seeing double drives remotely helpful or useful. While you're at it, Microsoft, why not duplicate our mapped network drives, too? It seems like increasing the clutter in the navigation pane has been one of your prime goals with Windows 10. Preview & Details Pane — You really gave us the middle finger with this one. In previous versions of Windows, the preview pane, if enabled, appeared on the right, and the details pane, if enabled, appeared on the bottom. Now, in Windows 10, they both appear on the right. So, how do you enable them both at the same time? Oh, yeah, you can't! In all your infinite wisdom, you've clearly assumed that nobody in the world cares to preview a file while also viewing its metadata details. This is such a straightforward bad move on your part that I wonder if you're purposely trying to make Windows less usable. This can be enough of an impediment to some power users of Windows that, along with your other screw-ups, will send them scrambling back to Windows 7 in a heartbeat. Simplified Error Reporting — When you screw up, it helps to have information to help us remediate that. In Windows 7, a blue screen yielded a several paragraph dump of computer jargon. In Windows 10, it yields Something happenedor Sorry, something went wrong :(. Wow, thanks, Microsoft, for all the helpful debug information! :( Dumbed Down, Condescending Language — Windows 7 and prior versions of Windows used somewhat loftier, but professional, language. In Windows 10, you've attempted to try to be more personal, but really, all you've done is make it seem like we're total morons. Everywhere in the OS, you've dumbed down the language. Some are as minor as changing "Please do not power off or unplug your machine. Installing update 2 of 7" to something that says "Don't turn off your PC" plus some more. Others are as condescending as the new welcome messages, like "We're setting things up here" or "We've got some new features for you to be excited about" (oh, really?) or "This won't take long". Really? Stick to the facts, please. Windows 10 is a computer operating system, not a person. Take the emotion out of your verbiage. Invasive Login Screen — This is a huge out of bounds step on your part. In previous versions of Windows, you typed your username and password, hit ENTER, and had the pleasure of watching the lofty verbose status messages roll by, beginning with "Please wait for the User Profile Service" to "Preparing your desktop" (I'll admit, it's always given me great satisfaction to watch these). Thankfully, you haven't done anything as dumb as removing verbose messaging, and consumers can even tweak Windows 10 to do this. But in addition to this, you now also display the full name of the user during the login process in huge text! Have you no notion of a user's right to privacy? Perhaps this caters to consumers, making them feel so hunky dory with their personalized operating system, but this is a huge annoyance to professional customers. It's not at all like bginfo, which is something IT administrators configure and have complete control over. The Windows 7 login process is completely anonymous, giving onlookers no clue as to who you are. With Windows 10, everyone in the room can figure out who you are just by looking at your monitor from the other side of the room. Nice going, Microsoft. Favoritism and Magical Resets — Amazingly, Microsoft's invisible helping hand seems to permeate the operating system. Users everywhere report logging in after an update and seeing that their default programs have all been reset. What's more, throughout the operating, subtle hints are given that push users towards using its products, like the warning that appears when manually changing it away from Edge. This is another radical shift from Windows' long practice of neutrality to aggresively promoting and pushing its own software to a new extent. Come on, Microsoft, we all know you want everyone to use Edge, but this is most unbecoming. Play nice. Prioritization of UWP apps — You've replaced solid, dependable built-in Win32 apps with laughably mediocre UWP apps. For example, Windows Media Player has been disfavored in favor of the "Videos" app. the reliable Windows Photo Viewer has seemingly disappeared in favor of the modern "Photos" app. Here's a hint, Microsoft. Nobody in the professional world is interested in your dumbed down, god-awful UWP apps. Maybe you won't help customers use Photo Viewer again, but third-parties, thankfully, recognize its importance and provide instructions. Default Programs — Ironically, in Windows 10, you've given yourself the liberty to change customers' default programs for them whenever you feel like it. At the same time, you've made it harder for customers to change their default programs themselves! In previous versions of Windows, changing a default was often a one-step click. Now, manually changing a default almost always means a trip to the Settings app, which, considering how well that plays with the user, makes it far more painful to change defaults. Privacy, Spying, Advertising, etc. — This is an issue that irks businesses and consumers alike, but Windows 10 takes data collection to a whole new level. I won't bother getting into this in detail, as the privacy nightmare also known as Windows 10 is already well-documented elsewhere. Login and Lock Screens — Since Windows 2000, logon to Windows workstations on a domain has looked relatively the same. The overall design was overhauled in Windows 7, but it was otherwise consistency with a decade long tradition of computer login. With Windows 8x, this all changed, and it's not been changed back with Windows 10. Yes, you can still require Windows Secure Logon, but everything about the logon process is different. First off, the Windows Secure Login prompt doesn't appear in the center of the screen anymore — oddly enough, it appears in the corner. Next, all of the pre-login text appears in an altogether different font that is much larger in size. Then, there's the splash screen, and the fact that one background appears at the login screen and, potentially, another while logging in. And in consumer builds, there exists the option to customize the login screen, a personalization option that did not exist before and one that, ironically enough, we don't wish existed now. A highly standardized and controlled login process has now devolved into a decentralized logon nightware. The entire experience is inconsistent and IT can no longer control every aspect of this process. Need any more be said? Daylight Savings Reminder — This is one of the top fatal flaws in Windows 10. In no version of Windows 10 are Daylight Savings reminders provided. You've refused to comment on this situation, and this is an incredibly precarious problem. Many people have come to rely on Windows providing advance notification of impending time zone changes (i.e. from standard time to daylight time, or vice versa). The modern clock in Windows is already a piece of junk, considering it dumped the analog clock for a repetitive digital display of the time and blew up the calendar so it takes up half the screen. But, despite invading a quarter of your monitor with a non-intuitive clock and calendar, you still don't warn us about daylight savings. The one helpful nudge that Windows featured, and you removed it! Shame on you. Deprecation — This is another one of those huge problems with Windows 10. Your insistence on deprecating all the old Win32 components of the operating system and replacing it with UWP apps is akin to slowly dismantling my desktop PC and replacing it with a tablet — no thanks! Rumors have had it that both Paint and the Snipping Tool were destined to die, and though newer rumors have it that, at least for now, the Snipping Tool is safe, this is hardly an isolated incident. The old calc.exe has been replaced by a UWP app that is far less usable. Picture Manager was removed from Office with Office 2013. Windows XP Mode is no longer included with Windows 10. Movie Maker is not even officially available for download anymore. You seem to have a liking for deprecating software that works and works well. Windows Briefcase — With build 14942, you have completely removed Windows Briefcase from Windows 10! Your rationale is easy to surmise: you think it's a legacy feature, and thus, you'd like to kill it off. Just what is your obsession with killing off legacy applications and features? You already put the work in years ago in creating the feature. It requires positive work to strike the feature from Windows 10. In other words, you spent time purposely removing functionality from Windows! Now, why would you do that? Is it possible you don't want people to upgrade to Windows 10??? True, this is somewhat of a niche feature these days, but it's important enough for some people that it's a make it or break it feature. Tell me, how else do I automatically synchronize files with a Windows 98 desktop with no network card? You load Windows 10 up with bloatware that nobody wants, and then you take away actually useful features. Most aggravating, to say the least! DVD Support — Windows 10 has no native DVD playback support. On account of trying to save a few bucks on licensing, you've also made the Windows 10 operating system a hindrance to media playback. It is now impossible to play DVDs using Windows Media Player. Yes, we can use the free VLC Media Player (I highly doubt anybody is dumb enough to pay for your $14.99 DVD playback app), and though Windows Media Player is buggy in a number of ways, it was nice to at least have the option of using it to play DVDs. Windows Media Center — I suppose Windows 8x doesn't have it, either, but the fact that Windows 7 includes it and Windows 10 doesn't makes one the obvious choice for media enthusiasts. To be fair, GPOs and registry fixes can be used to fix a lot of what we've pointed out above but not all of it. There is no GPO to make the Classic theme come back. It's gone, and there's no way to get it back. Perhaps this is the ultimate "screw you" to business customers, who've had the door slammed rudely in their face and made starkly aware that Microsoft is no longer on their side. The list above is by no means exhaustive. There are numerous other petty things I could've lashed out about as well, like the mysterious occasional disappearance of the battery indicator on Windows 10 laptops. Undoubtedly, countless other people have countless other complaints about your failure of an OS, an insult to the Windows brand name. But I've done enough disparaging for today. I have written this as bluntly as possible, for your situation is dire. The clock is ticking to 2020 and the end of Windows 7 support. I have, quite honestly, little faith that you will change direction and rectify your mistakes. But if you think I'm going to buy a copy of Windows 10 for my next PC, you are sorely mistaken. I will join the rebels whom you hate so much — the outlaws running the likes of Windows 7, Windows XP, and Windows 2000. They are remnants from the glory days of your company, and they are excellent operating systems. Two of them you have already left to whither and die. You are not always as foolish as your software makes it seem — you've already recognize that Windows 10 just doesn't cut it for some folks, and you've agreed to offer additional paid support until January 2023. But frankly, I don't know if that will be enough. If you fail to fix what's fundamentally wrong with Windows 10, some of us may very well be running Windows 7 for the rest of our lives. I hope, very much, that you find this greatly disconcerting. Though here, I must commend you for at least having the heart to patch Windows XP against WannaCry in 2017 and, just recently, BlueKeep as well. You want the transition from Windows 7 to Windows 10 to be smoother than the transition from Windows XP to Windows 7, but you have failed to deliver. Windows 7 was a fundamentally sound operating system, with a few UI changes, but otherwise solid all around. Considering how much larger the discrepancy is between 7 and 10 than between XP and 7, good luck with that. The resistance to Windows 10 is likely going to prove larger than any Windows upgrade resistance you've encountered so far. And a word to the wise: stop blaming your customers for remaining on outdated Windows versions. You have made them obsolete by your own doing, and you have failed to deliver an adequate successor to the Windows 7 operating system. Security is the only issue possibly preventing people from sticking with Windows 7 and Windows XP. A great many of these machines aren't networked, in which case there's absolutely no reason to "upgrade". And of the many that are, it's, as with anything, a cost/benefit or pro/con analysis. For many people, the downsides of "downgrading" to Windows 10 far outweigh the risk of remaining behind on a less secure operating system. https://blog.interlinked.us/44/an-open-letter-to-microsoft-why-windows-10-sucks
  29. 2 points
    Based on further review of Chromium behaviour, it seems that on both Vista and 7 it does the same procedure to check for locales, using functions introduced in Vista or earlier. The error message indicates that the default locale is defined, but default data is not, presumably referring to the manifest data for the extensions. The nuclear solution would be to modify ntoskrnl and set its RtlGetVersion (also PsGetVersion to be sure, even though it is obsolete as of XP) to 6.1.7601, thus everything in kernel mode would think they are running on Windows 7. Personally I connect my GPU to my 15 year old monitor with DVI, and use Realtek onboard HD audio. On another note, the user-mode version check bypass in ntext is not as effective as possible, as I realized that VerifyVersionInfo functions call RtlVerifyVersionInfo which is presently only in ntdll, and thus uses ntdll's RtlGetVersion. However, RtlVerifyVersionInfo is a bit of a handful, and with the limitations on implementing ntext functions, it will take awhile.
  30. 2 points
    Status Update: I am mostly ready to release Beta 3 of KernelXE. Here is what I have done so far: kernel32: Removed "mov edi, edi" from the beginning of some functions. ntdll: I reset development for ntdll and started from "scratch" (WildBill's ntdll). Added exports for: NtLockProductActivationKeys RtlLogStackBackTrace _swprintf Added functions: NtDeleteBootEntry NtModifyBootEntry NtAddBootEntry NtEnumerateBootEntries NtQueryBootEntryOrder NtQueryBootOptions NtSetBootEntryOrder NtSetBootOptions NtEnumerateSystemEnvironmentValuesEx NtTranslateFilePath NtQuerySystemEnvironmentValueEx NtSetSystemEnvironmentValueEx RtlDllShutdownInProgress RtlInterlockedCompareExchange64 RtlInterlockedPushListSList RtlIsCriticalSectionLockedByThread RtlNewSecurityObjectWithMultipleInheritance RtlGetLastNtStatus RtlGetLastWin32Error EtwEventRegister EtwpCreateEtwThread RtlRunOnceComplete Nt/ZwReleaseKeyedEvent (Code redirection to ntoskrnl) RtlInitializeConditionVariable RtlInitializeSRWLock RtlRunOnceInitialize RtlWakeAllConditionVariable RtlWakeConditionVariable _CIcos _CIlog _CIsin _CIsqrt _alloca_probe_16 _alloca_probe_8 ntoskrnl: Added functions: Nt/ZwReleaseKeyedEvent (Not exported, added to KiServiceTable) ExfAcquirePushLockExclusive ExfAcquirePushLockShared ExfReleasePushLock Added exports for: ObSetSecurityObjectByPointer SeTokenObjectType NtAssignProcessToJobObject NtCreateJobObject NtOpenJobObject NtQueryFullAttributesFile NtQueryInformationJobObject NtQueryInformationThread NtSetInformationJobObject NtTerminateJobObject ZwAssignProcessToJobObject ZwCreateJobObject ZwOpenJobObject ZwQueryFullAttributesFile ZwQueryInformationJobObject ZwSetInformationJobObject ZwTerminateJobObject NtOpenThread To-do before release: kernel32: Try a few things to maybe fix CreateActCtxW ntkrnlmp, ntkrnlpa, ntkrpamp: Everything done to ntoskrnl Plans for future: Fix Dependency Walker and CFF Explorer crashes (this one has been around since the original KernelXE and I still haven't figured out why they happen) Add PAE through "/PAE" in boot.ini
  31. 2 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201128-11839e2-uxp-a8a397fbc-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201128-11839e2-uxp-a8a397fbc-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201128-11839e2-uxp-a8a397fbc-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201128-86b6cb4c2-uxp-a8a397fbc-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201128-86b6cb4c2-uxp-a8a397fbc-xpmod.7z Official UXP changes since my last build: - Issue #1676 - Follow-up: Put js/src (including vm), jit, and wasm back into unified sources. (a8a397fbc) Official Basilisk changes since my last build: - Update back-end branch pointer (11839e2) No official Pale-Moon changes since my last build.
  32. 2 points
    Same thing happens with official Pale Moon. Any Ideas on that ? PS. It involves lists that I already had imported without any problems, then removed them, plus a couple of new ones. @Tangy : If the issue you're experiencing happens on the very popular https://filterlists.com/ site, then that site had a recent revamp/redesign (default dark theme), which might have contributed to the issue... I conducted some short tests with New Moon 28 + uBO-legacy, here's what I found: When loading a selected list's own page, e.g. https://filterlists.com/lists/1hosts-mini then, when clicking the "Subscribe" blue button/bar in the right sidebar, try to avoid clicking directly on the literal word, rather aim at an empty spot within that button; then, hopefully, the "add-to-custom-filterlists" dialog will pop-up: Take care...
  33. 2 points
    So you can't even mention you're using a custom OS? Looks like I'm going to be banned for using my own custom copies of Windows then
  34. 2 points
    Yeah at first I installed Windows 10 and oh boy. I absolutely HATE when operating system is doing something I did not asked it to do (like forcing Windows defender down my throat..) Windows defender consumed 2-3gb of my ram, constantly crashed vmware, because it was checking the virtual machine harddrive. Then I disabled it, but next windows update enabled it again. I disabled Windows update via the service. Windows somehow enabled the service again. I downloaded winaero tweaker and finally diabled it. windows then worked for like a month. Then nvidia told me that drivers are no longer compatible with this build of windows 10. I updated to then newest 1709 and windows ENABLED DEFENDER AGAIN!!!! IT did corrupt my work vm and that was the point I decided to install Windows 8.1. Since december 2017 my Windows 8.1 copy is running reliable, fast and nothing has gone wild. Windows update has toggle for manual search and install, window defender can be turned on/off and the UI looks way better than Windows 10 crap. I never fully understood why users agreed with such bul*****. Windows 8.1 was hated for metro, but Windows 10 is 900% worse and nobody cares
  35. 2 points
    The browser is the most important component of the security configuration. The first door to access to internet and therefore the first door for any malware. I am grateful for the work that Roytam1 does every week. Not only does using an updated browser allow you to enjoy the web in the best way, but the new added code, at least statistically, can prevent any OS compromises if we browse malformed web pages. Using an efficient adblocker allows you to browse faster. Even better with the use of eMatrix or Noscript but not with the default settings. It is useless to use browsers with the support terminated for years to navigate faster, then if the PC has other ballast such as the antivirus active in real time, etc. This is my thought. Others obviously do what they think is best for them.
  36. 2 points
    You should direct some (most) of this displeasement to lazy web devs that insist on using bloated JS frameworks for everything on a simple page.
  37. 2 points
    Please, do not post the Extended Kernel binaries on MSFN, with the exception of my own original creations, which are the NTEXT wrapper, the registry keys and the installer script (which I plan to post in one of the code example threads soon, as it serves as a good template for a script to replace in-use system files on NT 6.x).
  38. 2 points
    someone over there https://forums.mydigitallife.net/threads/restore-windows-update-for-vista.82336/ made a WU patcher to enable its function again. you can get it from here https://1drv.ms/u/s!AubsH71V5bOkkmIPXEQi0fbX_45f?e=5KEwYg i canconfirm that it works for me.
  39. 2 points
    Not on play store but Youtube Vanced is worth trying for a better Youtube experience.It's good, free and no ads at all
  40. 2 points
    Just thought the following would interest people using the UXP forks: It is the personal goal of upstream developer M.A.T. (but also backed-up by Moonchild himself) to completely debilitate all Firefox-targeting "legacy" extensions from being installable in official UXP browsers like Pale Moon/Basilisk... Already, unstable Pale Moon 29.0.0a6 official builds come without the buildconfig option "--enable-phoenix-extensions", which means already installed compatible Firefox XUL extensions will be disabled , with no option to re-enable , while "new" ones (e.g. from CAA) can no longer be installed ... One way to circumvent that artificial block is to manually edit the add-on's install.rdf file to include a Pale Moon specific <em:targetApplication> section... Or, for a more automated/user-friendly procedure, install and use JustOff's MTT: https://github.com/JustOff/moon-tester-tool/ A confrontation between M.A.T and JustOff has been brewing for some months now (on several levels), let's just say that M.A.T wasn't enthused by the CAA extension nor the recent update of the MTT one ... In a recent post: What future M.A.T. refers to is tracked in official UXP issue #1659 and work on it has already started: https://repo.palemoon.org/MoonchildProductions/UXP/commits/branch/xpiprovider-work I'm not implying, though, that official devs have any ill intent; their view on things is that they should (forcibly) migrate their users from long-deprecated, "insecure", no-longer-maintained Firefox specific legacy extensions (e.g the ones provided by CAA) - despite the fact they are currently working OK - to PM-exclusive format and extensions, forks of the original ones, with current maintainers sourced from the UXP communities (and elsewhere) ... Lofty as it may sound, the net result is yet another wave of plain user inconvenience... Should we be concerned? I'm not yet sure... I don't know what fate awaits the --enable-phoenix-extensions buildconfig flag; if the supporting code stays put, then we should be OK with regards to Fx XUL add-ons; however, in due course, upstream extensions and their repositories will move to the new format, which we'll have to somehow support too, if we are to make use of (or abuse of, as upstream claim ) ... Is supporting both formats (old: install.rdf, new: install.json) in the core browser a possibility, even? I'm no coder, so can't say myself... But, definitely, this part of the official UXP development is one our maintainer @roytam1 should keep a close eye on... Best wishes, stay safe
  41. 2 points
    @Valentin Radu. Good post. I also agree with the reactions on your post. Share your knowledge, pictures and code. There are many out here that can do some of the work. You can mention that it is an unfinished product without user support. We do not expect a full end-user application. Obviously, you have already done a lot of work on DWM. Please share it because there is a serious interest and there are no serious alternatives, not now and not to be expected in the future either.
  42. 2 points
    Maybe it is more a problem of making it known. There are bigger communities for Windows customization like MSFN here, Wincustomize... If you would share what you have found out and request help, maybe some people will step up and play around with DWM code to achieve even more. Not talking about a competitive product to AeroGlass, maybe just concentrate on that acrylic effect for title bars? Why not give it a try?
  43. 2 points
    Authy is working with kernelex, thanks so much!
  44. 2 points
    a workaround has been pushed to repo.
  45. 2 points
    This topic was moved into funny farm and was originally about something else. I don't remember what it was about. But that is not important anymore. Now this thread is about:
  46. 2 points
    And here it is: https://mega.nz/file/Bt9kWboR#slwDoaAQfBPOU8prjytUddjMLk0QYNgWxC1RAR59G2Y
  47. 2 points
    Nah, WindowBlinds is just too buggy to my taste. You can tell that WB is just a software running on top of your Windows 10. Unlike Glass8 which feels native part of the O.S.
  48. 2 points
    I agree, nobody knows how to make a website anymore. Everybody uses a template and the end product looks awful. I use mainly HTML + CSS3 and my policy is no JS unless absolutely necessary. Mainly advanced dropdowns and necessary logic. Most of my pages don't have any site JS. Thus, my website loads quickly and is accessible. Also, I code every line myself. All the PHP, all the CSS, and most of the JS... (sometimes, I do use a small library for a specific task, b/c I hate JS).
  49. 2 points
    On Facebook, people do not delete or remove messages, they "unsend" them now. This is English, not Newspeak. Or is it?
  50. 2 points
    Hi, if anyone is interested, I got VMware Player 16.0 "official" release working on Windows 7. Download: This is still largely untested, especially the VMware installer is flaky, but VMware itself works very well on my main Win7. You're supposed to reboot right after the installation and then put contents of vmware16_win7 folder in VMware\VMware Player\x64. The video: Edit: Added the VMware Workstation installer. If license key registration fails, try to install VMware Workstation 15.x first, and then directly upgrade to 16.
  • Create New...