Jump to content
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. ×

Leaderboard

Popular Content

Showing content with the highest reputation since 07/29/2020 in all areas

  1. Yes, I would appreciate it too so it will be released when it is ready. Current status is that it does not work correctly yet. On the other side, I doubt that someone needs to upgrade to new builds immediately when it is released, especially when some needed software is not compatible with it.
    16 points
  2. To prevent user confusion, I strongly recommend disregarding the tutorials and contacting me directly instead about the extended kernel. The original post was removed as it was continuing to confuse users. There will be further discussion about the evolution of the extended kernel in the coming pages. If you are interested in making a monetary contribution for this and my other projects (such as minor extensions for Windows 2000, 7, 8.1 and time zone updates targeting NT 5.x), please visit this page: http://paypal.me/win32420.
    14 points
  3. Hello Windows XP gaming community. I have what i believe are good news for you, if you are into emulation. I'm a developer and i've recently modified the latest version of the popular PCSX2 PlayStation 2 emulator to make it run again under the Windows XP operating system, since they removed that compatibility by 2016. The development to my modified version of PCSX2 started in May 2020, just when the latest stable official release was made public (v1.6.0), confirming it wasn't indeed compatible with XP. I wanted to do something about it, so i started peeking the code and considering the options i had. Well, after months of testing and patience, i got the latest v1.6.0 stable release from May 2020 running perfectly fine under XP. This project is called "PCSX2 XP" and is been made available from my website: http://neonfloppy.sytes.net/projects/pcsx2-xp/ and there is also a github repository: https://github.com/blueclouds8666/pcsx2_XP You may also join to my discord server, where you can find about my other projects and chat with other xp fans: https://discord.gg/KXKXcs4 I will be answering any questions you have regarding my project down below. I hope you all find this useful. Thanks for your attention.
    13 points
  4. (Sorry, didn't have time to respond to this before.) I agree with your general point, but I'm not sure how much Google is to blame in this particular case. The thing is, programmers often tend to be pretty lazy when having to do maintenance tasks, because these aren't seen as "cool" and "innovative"... And this bug is a bit of a special case, because it takes almost 30 min to run a single test case, whether you're trying to track down where the regression originated, or trying to fix it. Let me give you a rough rundown of the process I went through with this (let's skip this long story for them normal people ; and this isn't about me looking for extra credit, honest! ) OK, so now consider that during virtually every step of this, you have to run a whole lot of 30 min (or longer) tests to make sure of your guesses or fixes. I am, of course, a great guy and all , but even with my highly vested hobbyist interest in solving this issue it took me several months to get through this all. Obviously not months of straight work on this alone, and obviously I didn't just sit around gaping at the screen every time I ran a test, but started the test and then did something else while it ran, but the whole thing still took time. Now, imagine I was an elite coder working at Mozilla , and generally supposed to work on some other stuff besides this. And, let's say you were my manager. Are you sure you'd let me spend all this time on this one, apparently (but really not) intermittent issue that seems to be affecting only a few people (really affecting all, but 99.99% of those people wouldn't put 2 and 2 together and notice the very specific interval and would instead write these freezes off as internet issues or whatever else) on a "legacy" OS that doesn't have that long to live anyway (or so you think, not knowing about POSReady, and MSFN )? And would I, an elite Mozilla engineer , want you to make me spend my precious time on something like this? I mean, even without the whole Windows driver dive and leak hunting thing they obviously wouldn't get into (the leak hadn't happened yet, either), it's a lot of work that isn't "cool", nor "innovative"! This is not to say that I excuse the fact that they don't even run tests for longer playback, etc., etc. We all know Mozilla has lots of problems with their attitude and policies, and there are many things they aren't doing that they should be doing (and vice versa). I definitely do blame them for letting this fall through the cracks and not doing more to fix this. But as far as Google goes, since they probably weren't using cubeb, maybe they themselves never ran into this bug (at least its more obvious, 2x:xx version), and since this isn't an issue specific to Youtube, I think I wouldn't blame them too much for this one. But there is Microsoft, who introduced this bug in the first place with that pretty dumb coding error...
    12 points
  5. 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.
    11 points
  6. I'd rather recommend than listening to the FBI but to upgrade your very unique Brain.exe instead. It's the best anti-virus out there. The only downside is, that Brain.exe can't be bought for money and downloading it is impossible, too. It must be fed proper knowledge to grow. And then one day, you will be capable of using the old operating systems online without running into a wall. Would I recommend to average users who use their brain on other things than computers to use Windows XP and Windows 7 for example? No, because that would put them easily in danger. But if you know, what you are doing, then you'll be able to avoid the problems. Use a hardware firewall, that you can configure. Block unwanted Javascripts. Block everything, you didn't ask for. Don't click on everything that sounds like a promising help to your problems. Learn to read links before clicking on them. These things. Also consider that something like Windows XP got more secure over time, as less and less people were using it. Windows 7 is still a very attractive target for mean hackers with circa 15% market share (2020).
    11 points
  7. Hello to all, Since late 2020 I have been searching for a relatively new browser that could run on Windows XP because I have an old but very nice laptop that I want being functional. In my quest I found the Firefox based browsers (K-meleon, Mypal, etc.) but they were a little heavier for my laptop. I then searched if there was a Chromium based browser and I found out the thread below and started testing the 360 Extreme Explorer (the Russian Repack version). https://msfn.org/board/topic/182304-extreme-explorer-360-chromium-78-86-general-discussion/ Other interest links: http://retrobrowsers.com/windowsxp https://retrosystemsrevival.blogspot.com/2019/05/360-extreme-chrome-browser.html https://msfn.org/board/topic/182794-updated-browser-list-for-windows-xp/ The main issue was the connections that the browser made with servers in China. I thought that I could bypass that issue by using a firewall with a lot of rules, but I changed my mind later because that was not a proper way to fix this problem. Then I discovered from some websites and users in this platform (thanks for that) that those connections could be erased through modifications in the browser files. I tested this discovery a little, and got really good results. In order to deal with the original source, I downloaded the browser directly from the chinese page and started modifying the corresponding files. I do not know exactly what the RuRepackers did to their version of the browser and I really do not want to get involved in knowing it. The RuRepackers made some of the changes to the browser through the "User Data" folder. That folder appears only when the browser is executed once. I did not wanted to follow that approach because if you lose or delete the folder for whatever reason, the browser will launch with the default settings like if it were downloaded directly from the original chinese page. Through some files (being "chrome.dll" one of the most important) I managed editing those default settings and made them work to not depend on a single run of the browser to be able to modify it. All the changes I followed comply with the following conditions: 1) Remove every chinese unwanted connection. 2) Delete unnecessary files. 3) Translate and correct text to English. If 1) is not satisfied, a modified version of this browser should not be posted (security is first). In my experience, after all the changes related to 1) were made, I did not find chinese connections when using the browser. Please tell me if you find any chinese connection. However 2) and 3) may not be totally achieved due to the large number of files related with this browser. A partial achievement of 2) and 3) may be enough for the browser to work properly. I could add more conditions to the list above but only if the corresponding modifications can be made in the original files that come with the browser installer. The intention that I have with this browser is to provide a secure, well translated and without bloatware browser based on a relatively new version of Chromium that anyone can use to keep using their older OS (Windows XP), without having security worries and with the capacity of navigating through the web without much difficulty. The above conditions are based on a Chromium based browser called "Ungoogled Chromium" 84.0.4147.125 (Official Build) (32 bits) on Windows 7 SP1 x86. Most of the removed 360EE files do not appear in the Ungoogled Chromium browser and some translation work was based on this browser as well. Link to Ungoogled Chromium downloads (there are several pages that provide builds of this browser, this is from which I downloaded the version I use): https://ungoogled-software.github.io/ungoogled-chromium-binaries/ I also deleted everything related to the 360 account (it is not possible to login) since I do not think anyone want to use it. Compatibility: This browser works on Windows XP SP3 and Windows 7 SP1 as far as I could test (the SSE2 instruction set is required). If there are problems in the execution of this browser on other OSes, I do not think it is possible to modify the files in order to make it work. Performance: The older versions of this browser run better on older and low resources computers. With v9 and v11 you can use the web pretty decently. However with v12 and v13, it starts behaving more slowly. Extensions recommended: - Ublock Origin --> https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm?hl=es - I don't care about cookies --> https://chrome.google.com/webstore/detail/i-dont-care-about-cookies/fihnjjcciajhdojfnbdddfaoknhalnja (If you want to add more, be aware that the more extensions you have, more resources the browser will use) Programs used: - 7zip ---> https://www.7-zip.org - HxD Hex Editor ---> https://mh-nexus.de/en/hxd/ - TCPLogView ---> https://www.nirsoft.net/utils/tcp_log_view.html - Resource Hacker ---> http://angusj.com/resourcehacker/ - Chrome PAK Customizer ---> https://github.com/myfreeer/chrome-pak-customizer - grepWin (Windows 7) ---> https://tools.stefankueng.com/grepWin.html - Diff Checker ---> https://www.diffchecker.com/diff - Online Unicode Tools ---> https://onlineunicodetools.com/convert-code-points-to-unicode - Deepl Translator ---> https://www.deepl.com/translator - Google Translate ---> https://translate.google.com/ - WinMerge ---> https://winmerge.org/ - LiveTcpUdpWatch ---> https://www.nirsoft.net/utils/live_tcp_udp_watch.html - Wireshark ---> https://www.wireshark.org/ Modified Version download links: v9 --> (Updated 29/07/21) Version: 9.5.0.138 Based on Chromium: 63.0.3239.132 Browser --> https://www.mediafire.com/file/g2u94jz35ig3vmr/360EE_9.5.0.138_Modified.7z/file Modification notes --> https://www.mediafire.com/file/k3ff8a98daj6iok/360EE_9.5.0.138_Modified_Notes.txt/file v11 --> (Updated 29/07/21) Version: 11.0.2251.0 Based on Chromium: 69.0.3497.100 Browser --> https://www.mediafire.com/file/cx7tav03pme37f2/360EE_11.0.2251.0_Modified.7z/file Modification notes --> https://www.mediafire.com/file/i1higd31up6r42r/360EE_11.0.2251.0_Modified_Notes.txt/file v12 --> (Updated 29/07/21) Version: 12.0.1592.0 Based on Chromium: 78.0.3904.108 Browser --> https://www.mediafire.com/file/wpy8ldkev4nijul/360EE_12.0.1592.0_Modified.7z/file Modification notes --> https://www.mediafire.com/file/c7jig98agjszarf/360EE_12.0.1592.0_Modified_Notes.txt/file v13 --> (Updated 29/07/21) Version: 13.0.2250.0 Based on Chromium: 86.0.4240.198 Browser --> https://www.mediafire.com/file/725uk7bsck3x3ku/360EE_13.0.2250.0_Modified.7z/file Modification notes --> https://www.mediafire.com/file/toqee19btkil8h0/360EE_13.0.2250.0_Modified_Notes.txt/file Note: The changes I made are so many that maybe some little errors related to translation and/or the building of the modification notes can be present so please tell me if you find any. Also, if you want to propose something else, please be aware that I do not have a lot of free time and that at any moment, I could be gone for a while for whatever reasons (I do not intend to be rude with this comment, feel free to speak yourself). If anyone wants to help, it will be truly appreciated. Themes: If you want to change the browser's theme at any moment, you can access the URL shown below. However, I am not sure if it is a safe direction since it is from the chinese company. There are many themes that can be added through this URL but it is not a secure option (I think this functionality is broken). https://skin.chrome.360.cn/new/index.php If you want to do it the secure way, you can only change the theme for v11 and v12 and only to the "Classic", "Chrome" and "Dark" themes. The steps involve the file "Preferences" in the User Data/Default path. Open it with a text editor and search for the "jisu9" entry and modify the original line you will see, to --> "id": "jisu9" --> Classic theme to --> "id": "jisu9_chrome" --> Chrome theme to --> "id": "jisu9_dark" --> Dark theme Original download links (do not install directly on your computer, unzip with 7zip) (if someone wants to test or make its own modifications): v9 --> https://down.360safe.com/cse/360cse_9.5.0.138.exe v11 --> https://down.360safe.com/cse/360cse_11.0.2251.0.exe v12 --> https://down.360safe.com/cse/360cse_12.0.1592.0.exe v13 --> https://down.360safe.com/cse/360cse_13.0.2250.0.exe Some stuff I remember that I left behind (could not find the source of the problem and they are not a big issue): v9 - If you put the mouse over a tab that is reproducing audio, chinese text will appear (indication that the tab is playing audio) (could not find the source). - Adfilter option button on the browser preferences can not be removed since some modifications break the browser preferences page (this happens to all versions). v11 - Cannot modify the "chrome_elf.dll" file (specifically "crash.browser.360.cn" and "pvstat.qihoo.com" entries) (happens on v11 and v12). - At first run the browser shows a "select theme" window. There are images that display chinese text so it is not translatable (directly). I left it like that because it is not that annoying. v12 - Remnant of login popup only on first run (press Escape to interact with the browser) (happens on v12 and v13). - New search-box style option displays some chinese text when it is checked and the "Settings" button (on the drop-down menu of the search-box) does not display the word "Settings" (could not find the source) (happens on v12 and v13). Thanks to all the following for the information I could gather for the modification of this browser: @Windows 2000, @VistaLover, @Sampei.Nihira, @win32, @DragonSC7601, @redapple0204, @blackwingcat, @404notfound, @Cixert, @thebuildone, @ArcticFoxie, @Dixel, The Russian Repackers, @dmiranda, @we3fan, @athlonxpuser and @Greyfox77 I really hope this can help someone. Cheers. Humming Owl
    10 points
  8. I guess this is my cue to stop procrastinating and finally post the fix I made for this I've had a few people test it for 4 months now on all kinds of sites on both XP x86 and x64, and the jury says this indeed fixes the 2x:xx video stoppage issue and doesn't seem to introduce any new problems. I honestly didn't intend for the testing period to be quite this long, but summer heat can have a detrimental effect on one's brain and thus plans. Since my own browser builds are based on Centaury, but I still consider myself a (lurking) MSFN patriot and this is the home of @roytam1's Serpent, I'm just going to post the fixed media/libcubeb/src/cubeb_winmm.c on Pastebin to avoid playing favorites (and signing up on Github ) I'm not sure how often @feodor2 visits here these days, so maybe someone on Github could mention this in https://github.com/Feodor2/Mypal/issues/1 if he doesn't pick this up soon enough. What has been tested: MP4/VP9/VP8 (and plain audio MP3/etc) streaming/local chunked/single-file sped-up/slowed-down 27+ hrs long playback (see the technical details for why) Youtube/Twitter/Facebook/Instagram/TV station streams/etc/etc (nor did we forget p0rn/pirate sites, which of course are no different from a technical POV... ). Among other things, a 75-year old lady watched the entirety of Prince Philip's funeral with this fix in effect and had no complaints. What has NOT been tested: Pale Moon-based builds (as opposed to Basilisk), because I don't use NM or Mypal. Since this is a UXP platform level fix, the front-end should have no effect. I obviously don't have access to every sound card out there, but since the MS driver causing these problems should be common in all configurations, I'd expect the fix to work with pretty much every card. new-fangled formats like AV1 (I'd expect them work, though). DRM-ed streams, since no Widevine on XP (but again, this should work with those as well if DRM itself worked). @roytam1, @feodor2 I didn't create a preference for turning this fix off, because it turned out the normal pref system is no longer compatible with C code, and once it became evident enough that the fix was pretty solid, I didn't feel like hacking something together to make preffing work for a library-level change like this. You're welcome to pref it, of course, but based on the length of testing with no issues discovered, I dare claim it's safe to include without a pref. Here's a general overview of why this problem was happening (you may be surprised ): And, some more technical specifics, incl. about where the 2x:xx times come from (this is also included as a comment in the source code): EDIT: Writing this up amply reminded me how much I LOVE making long posts using this board's post editor... BBCode FTW!
    10 points
  9. I think there is more to the old operating systems than just internet. These machines are resources of creativity with the tools, that run on them. Writing programs, graphic programs, music programs, programming tools... even if there would be no internet at all, the old computers are capable of plenty of things. I can work best with the tools that I know best, which are the old tools. Okay, the resolution may not be the highest. But as long as the hardware runs (whose spare parts cost 0 money on the scrapyard)... it would be an uneconomic choice to switch. Consider the time you need to learn new programs! Speaking of Linux? Fantastic for modern internet browsing, but not if you need special tools. Sometimes, the Linux counterparts are poorly designed, too. LibreOffice will never perform as good as Word 97. In fact it performs worse every year! On limited hardware we have to add. My decision is set in stone. Windows XP until repairing the hardware gets expensive. On to the future with Windows XP!
    10 points
  10. The staff is aware that there are currently spambots sending out private messages to random members here on the forum. We are actively dealing with the situation but if you happen to get one of those spam messages, please do not simply ignore or delete it but use the report system so that we can permaban every account responsible for these messages. Thank you for your patience!
    10 points
  11. (Note: this text is written for and directed at Big Muscle. Just pointing it out in case that the "you"s looks a bit wierd to you (the person reading this text)) Let me first get the most important thing out of the way: You CAN make money with open source software. In many ways actually: You can charge for the convenicance of auto updates You can charge for direct support (for example, via email or via a private discord chat) You can charge for the convenicance of having an already compiled binary version (which is especially true on windows; on linux for example, you usually git clone the repo, cd into it and type `make && sudo make install` and that's it. On Windows though...) You can make (optional) donations Speaking of donations: what you offer on your website, those are NOT donations. Those are payments. It is NOT freeware. You just get a free demo version. A donation is something optional. The point of a donation is not to get something back from it (besides maybe the knowladge of having helped someone/-thing or maybe getting a "Thank you" mail from them), but purely to support someone/-thing. And I want to mention that that is the only reason why I actually paid 5 bucks for it: not because I care about the watermark (if that would be my only reason, I could have just used a cracked version, and yes, I DID have a working one back then, but I didn't use it), but because I want this project to stay alive. In other words: I am pretty shure that a lot of peole donated just for support, or at least partially. Anyways, I of course know that there are not only positive things about open sourceing this software, namely: You may not make the exact same amount of money from "donations"* You may unveal your secrets* However, both of these arguments are very weak. The first one I already talked about above. For the second one: opening this app would mean that a lot more developers could integrate it (as in making their app compatible with it, not as in stealing your code; the only app I know of that supports aero glass is Winstep Nexus, and that one only works when it really wants to, which, as a dev explained to me, is not their fault). It would allow other people to learn about windows from (because, as described on glass8.eu, it uses undocumented windows features). TL;DR both arguments are... bad. Now let's finally get to why I think it should be open sourced: You (Big Muscle) are not able to maintain this on your own, or at least not in a way that I would concider acceptable for a paid app. Often times, this app gets a fix about 1-2 months before the next major update comes out, which will break it again. And again. And again. This app would be accessable to a lot more people. It would improve the user experiance since it will allow updates to be completed much, much faster. You would not have to stem this project all on your own anymore, which, again, you're not able to. Almost the entire forum is just "It doesn't work" posts. As described previosly, third party compatibility could also be improved massively. A concern you may have is others missusing your code to make money on. This is actually not a problem. You can either use the GNU GPL (or similar), which will technically not prevent your code from being commericallized, but since every modification that is being made availably has to also be opensourced under the same license (or a newer version), it is very unrealistic to think that someone would actually do it, exept maybe in those ***** bundles. While some apps (like OpenOffice or 7-zip, see here ) do suffer from this problem, I, again, don't think that such a tool like AeroGlass would really suffer from this. Alternatively, you can also write your own license, for example like this (this is not legal advaise): Of course, the above mentiond "license" is only one of many ways it could be done (and, again, it is not legal advise). I hope that you will change your mind about this program and it's licensing and distribution, as it would gain both you and even more so it's community. Cheers.
    10 points
  12. Finally got the time to create the much requested Update Repository for Vista. I've collected these updates a year ago, but only recently took the time to put them on my Mega account and organize them. It has roughly the same format as my post-EOL repositories, with x86 and amd64 versions. A few highlight points: Most updates come in ".cab" format, because at the time it was easier to manage bulk installations in this format (I was trying to update offline images) Includes hotfixes not distributed through Windows Update. These were collected through a mix of the now defunct MS Hotfix service and the website "hotfixshare". There's some interesting fixes in there. While most of the updates are language agnostic, some are specific to the language I use, Portuguese of Portugal (like the IE9 installer). If you'd like to provide a version for your language, please contact me. To install a ".cab" format update, just run the following command: start /w pkgmgr /ip /m:<path to updates> /s:<temp path for extraction> /l:<path for log files> /norestart To bulk install updates, I usually run the following set of commands: forfiles /p <path to update folder> /m *.cab /c "cmd /c mkdir @fname" forfiles /p <path to update folder> /m *.cab /c "cmd /c pkgmgr /ip /m:@file /s:@fname /norestart" The first command creates a folder for each individual update and the second one installs each update and extracts onto each created folder. Here's a practical example. Say, I have all of the updates from the repository located in my Downloads folder inside my user profile. In this case, I want to install every update in the "General" folder. I'd use the commands above like so: forfiles /p "C:\Users\greenhillmaniac\Downloads\General" /m *.cab /c "cmd /c mkdir @fname" forfiles /p "C:\Users\greenhillmaniac\Downloads\General" /m *.cab /c "cmd /c pkgmgr /ip /m:@file /s:@fname /norestart" I'd recommend you install no more than 200 updates at a time. This can also be used to create an updated Vista ISO for later use (tutorial coming soon™) Anyway, here's the link for the repository
    9 points
  13. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210605-e29e57e-uxp-7f6f1c664-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210605-e29e57e-uxp-7f6f1c664-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.8.win32-git-20210605-e29e57e-uxp-7f6f1c664-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.3a1.win32-git-20210605-411f285e0-uxp-7f6f1c664-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210605-411f285e0-uxp-7f6f1c664-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210605-411f285e0-uxp-7f6f1c664-xpmod.7z Official UXP changes since my last build: - Revert "Issue #21 - Remove TelemertyVFS" (349346d0b) - Issue #1772 - Stop using legacy code page conversion for file paths on Linux. (c921ad59d) - Issue #1774 - Make menulist-button visible again in gtk3 (0a0830ba8) - Merge pull request 'Issue #1774 - Make menulist-button visible again in gtk3' (#1775) from jobbautista9/UXP:master into master (27e7b312a) - Revert "Issue #1774 - Make menulist-button visible again in gtk3" (6272d48e8) - Issue #1774 - Add metrics to the editable menulist-button for GTK3 (42cf1ad41) - [toolkit] Exclude printer spew from troubleshooting information. (ce71c0fe3) - [js] Fix invalid early return in BaselineFrame::trace. (9acd98298) - [js] Fix porting typo (7f6f1c664) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Back-end branch pointer update. (c9f73ec3f) - Rename "Web Developer" menu entries to "Developer Tools" (29908be27) - Issue #1870 - Add try/catch and console logging for failing autocomplete popup. (411f285e0) My changes since my last build: - skipped "Rename "Web Developer" menu entries to "Developer Tools" (29908be27)" - update NSS builtin certstore to May 2021 version from mozilla upstream. (6026e19d2)
    9 points
  14. ... And the rift between @JustOff and his ex-associates within MCP grows wider and wider... ; the screengrab below is from NM27's add-ons manager (AOM): Thank you JustOff for standing up against authoritarian oppression...
    9 points
  15. Well now you'll never get that username change. I recommend you do not try to register more accounts, otherwise we will report you to the spam service.
    9 points
  16. LGTM will commit it in short period. EDIT: committed in goanna3 and 4 repo, other repos will be followed later. https://github.com/roytam1/UXP/commit/85149582f1000cd801350ebaa73151872c521d4f https://github.com/roytam1/palemoon27/commit/2d96070f5334a82b3cb3133c822b8ae5a372c411 https://github.com/roytam1/mozilla45esr/commit/bf2771bde24a18e3ab13ead251befca1ac630d7b https://github.com/roytam1/basilisk55/commit/6fd60b08fe3f33fc0c7245427a25251dd6008690 https://github.com/roytam1/palemoon26/commit/a66d2e44121f0684044f86abed116dc1d686d17f
    8 points
  17. - Windows NT 5.x family windowsupdate.com links for available languages, including all (any?) Custom Support Updates - The updates links are grouped for each build, slightly sorted, and ordered lexicographically per update number or file name as possible - Superseded (replaced) updates are not filtered or excluded - The dump is available as csv files containing updates name and url, or plain text files containing updates url - It's recommended to use CSVFileView to check the csv files https://www.nirsoft.net/utils/csv_file_view.html - You can filter or extract updates for certain language using findstr (Vista or 7) e.g. findstr /i \-enu NT_5.2.3790-x64-Custom.csv > NT_5.2.3790-x64-Custom-enu.csv however, few update have different language identifier or none, so it's best to review the whole file first - NT_5.1.2600-x86-SP2-Custom and NT_5.1.2600-x86-SP2-Custom-IE are ment for the EOS Windows XP SP2 x86 only - NT5-ia64 is for Itanium-based Server 2003 / Windows XP - .NET Framework packs and updates for NT 5.1/5.2 are in a separate list files, likewise Windows Media Player and some eXtra updates # P.S. Maybe it's best not to post the links explicitly in the forum replies or text sites (pastebin, txtuploader..), and share them in the txt/csv files # Download https://gitlab.com/stdout12/adns/uploads/9ca06a12dd08c06edd889e65afa637fa/NT5_WU_URLs_csv.7z https://gitlab.com/stdout12/adns/uploads/33fcfd0b0f6c1a0cb74472cb8407800d/NT5_WU_URLs_txt.7z
    8 points
  18. Many thanks, indeed! palem's post there is, I think, highly representative/reflective of the major part of Moonchild browsers' userbase, and should also encompass users of Roytam1 forks here... The actual URI of the post (by M.A.T.) quoted is: https://forum.palemoon.org/viewtopic.php?p=211976&sid=0181647fb5c2204a1c681cd16e21004d#p211976 ... As far as I know, no-one here has already gone/will go nuts over it, all is needed is to keep a vigilant eye on UXP+PM issue trackers/UXP+PM master branches and selectively revert/omit what is deemed unneeded for our tree... Even if that, eventually, will just buy us more time (hopefully lots of it...), it would be highly worth it! E.g., I have already warned readers here of the new plan (envisioned by M.A.T.) to move to an install.json based extension ecosystem (deprecating the install.rdf one), I think these developments should be dealt with on a case-by-case basis/when they present themselves... OT: To Sampei and to all observing Easter tomorrow, may you have a very Happy Easter Sunday (... Unfortunately, divisions between communities of the same Faith mean that over here Easter Sunday won't "arrive" until May 2nd ) ...
    8 points
  19. But Sombady Can Get Mad At You For Spamming The Forums With Useless Topics This Here Is Just Bragging Unless You Provide Details On The Process
    8 points
  20. @Dixel Excuse me, but I would like to ask who D.Draker is.
    8 points
  21. I wouldn't touch that. There's an EOL timestamp in recent versions of Flash Player. It can be altered so latest Flash Player continues to work as usual. Find a hexadecimal string 000040463E6F7742 in NPSFWXX_32_0_0_465.dll (XX = bitness, either 32 or 64) with a hex editor, replace it with eg. 0000C02055148042, that will just change the year from 2021 to 2040. It's a unique string, so only one will be found as long as you got the right file. The string represents time elapsed since Unix epoch in milliseconds, stored as 64-bit double precision float number (no fractional part). The DLLs are in: C:\Windows\System32\Macromed\Flash - 64-bit Flash on 64-bit OS or 32-bit Flash on 32-bit OS C:\Windows\SysWOW64\Macromed\Flash - 32-bit Flash on 64-bit OS This is for NPAPI version, but should be doable with PPAPI and ActiveX versions as well, though I haven't tried those. Doing this obviously invalidates the digital signature on the DLL. Pale Moon (and probably other browsers) doesn't mind. I wonder if Flash app could check it. Also, PE checksum is invalidated, but that can be fixed with certain tools. I think there's a high probability that altering Flash binaries doesn't cause any side effects beyond what modifications you did achieve.
    8 points
  22. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201226-97b3dce-uxp-62568d94d-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201226-97b3dce-uxp-62568d94d-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-20201226-97b3dce-uxp-62568d94d-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-20201226-78b687d98-uxp-62568d94d-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201226-78b687d98-uxp-62568d94d-xpmod.7z Official UXP changes since my last build: - Issue #1695 - Add clamping to websocket polling timeouts. (2fa993b56) - [network] Update port blacklist. (3c0236666) - Issue #1696 - Propagate flex sizes to the table wrapper (ac4c22f09) - [toolkit] Handle corner case confusion of downloaded files without extension. (78f114fc4) - Issue #1695 - Restore Sleep/Wake timer that was erroneously removed. (da0c073a7) - Revert "Issue #1695 - Add clamping to websocket polling timeouts." (408477a87) - Issue #1697 - Reinstate the performance timing code removed in error. (0187d3e4e) - Merge pull request 'Reinstate the performance timing code removed in error' (#1698) from adesh/UXP:fix-performace-api into master (8500ebf53) - Revert "Issue #1686 - Align a keybinding definition with the others" (05569cb6d) - Issue #1700 - Apply background color instead of inset shadow for findbar input. (911cbcd1a) - Issue #1701 - Implement Intl.PluralRules API (25b6703e9) - Issue #1693 - Update NSPR to 4.29 (149d2ffa7) - Issue #1693 - Update NSS to 3.59.1.1 (029bcfe18) - Issue #1693 - Additional configuration for NSS lib update. (ae775e493) - Clobber for NSS update. (6ae313b51) - Issue #1681 - Hard-code FLAC and AAC media type associations for .flac and .aac (a8e90975d) - Revert "Issue #1681 - Hard-code FLAC and AAC media type associations for .flac and .aac" (837432de6) - Issue #1681 - Hard-code FLAC media type association for .flac (62568d94d) Official Basilisk changes since my last build: - Update back-end branch pointer. (2e26040) - Explicitly disable the legacy DBM format. (97b3dce) Official Pale-Moon changes since my last build: - Issue #1854 - Account for users disabling off-line and memory caching. (5b38337f5) - Back-end branch pointer update (Unstable 2020-12-21) (f4ace7065) - NSS update, clobber and version bump (0388d9143) - Explicitly disable the legacy DBM format. (78b687d98) My changes since my last build: - Reverted "Reverted Issue UXP#1694 and Basilisk#31 related changes" - Reverted Issue #1693 related changes since I'll maintain my own NSS and NSPR - Reverted "Explicitly disable the legacy DBM format" changes since I want to keep using DBM
    8 points
  23. 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 points
  24. Here, you will find a list of software compatible with Windows Vista, after installing the new extended kernel by Win32. As this project is very new, this list will remain quite short for the time being. List: BeamNG.Drive 0.16 and later Chromium versions 53-73 beta (later versions currently do not work) Firefox "classic" versions 53-56 Firefox Quantum version 57 and later GIMP 2.10.18 Google Earth 7.3.3 and later Interlink Mail client Logitech Gaming Software 9.02 Opera 44 (later versions currently do not work) Palemoon 28.x Rocket League Thunderbird versions 53 and later Waterfox Classic Waterfox Current Whatsapp I will continue to update this list as more software is made compatible. Feel free to contribute your own additions in the form of a reply to the topic, and I will add them ASAP.
    7 points
  25. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210626-e29e57e-uxp-a0461e377-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210626-e29e57e-uxp-a0461e377-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.8.win32-git-20210626-e29e57e-uxp-a0461e377-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.3a1.win32-git-20210626-c9bf62e0b-uxp-a0461e377-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210626-c9bf62e0b-uxp-a0461e377-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210626-c9bf62e0b-uxp-a0461e377-xpmod.7z Official UXP changes since my last build: - Issue #1783 - Part 1: Move GetNodeDepth to ResizeObserver.cpp (22a75217e) - Issue #1783 - Part 2: Update ResizeObserver and resizeObserverSize. (6f7dd6fd9) - Issue #1783 - Part 3: Remove ResizeObservation's BroadcastSize. (cfdfbcf05) - Issue #1776 - Support detecting bool preferences in chrome stylesheets (4dac05e0e) - Merge pull request 'Support detecting bool preferences in chrome stylesheets' (#1785) from athenian200/UXP:bool-chrome-stylesheets into master (2c626f604) - Merge branch '1783' (014fdd052) - Bump platform version (8689ac630) - [whitespace] Fix CRLF line endings. (5afcb4a09) - Issue #1751 - Remove Mac code behind MOZ_WIDGET_TOOLKIT == 'cocoa' (1fe9c1930) - [Toolkit] Attempt to initialize DownloadTaskbarProgress when onDownloadWindowLoad() is called so that DownloadTaskbarProgress from the Downloads Manager window works when the application doesn't explicitly invoke onBrowserWindowLoad(). (4490f61f5) - Issue #1784 - Add -moz-dark-theme media query and allow prefers-color-scheme to follow it. (a0461e377) No official Basilisk changes since my last build. Official Pale-Moon changes since my last build: - Back-end branch pointer update. (c9bf62e0b)
    7 points
  26. A big thank you to all parties involved... However, seeing MSFN down for more than 5 days (the longest since the time I registered), without any clues as to what was going on, "member flags" was the least of my worries...
    7 points
  27. And why is this certificate expiry the death of Windows XP? (hint - it's not - almost nothing will change)
    7 points
  28. Here's the thread on it. https://forum.palemoon.org/viewtopic.php?t=26204&p=208720
    7 points
  29. No, you can't. Did you ever read the rules or are they like stop signs to some people? Here's a piece of advice, never engage in criminal activity. Loose lips sink ships.
    7 points
  30. Thus far.. @roytam1 has done our community an enormous service with his proficient browser builds. So, between Firefox 52.9.1 ESR; Serpent, and New Moon, I'm able to do everything I need to. When I do have to use Chrome, regrettably, Vivaldi/Opera/Iron are all only based on 49, so I only use it when I truly need to because of 5 years of gaping security holes. Otherwise.. I'm basically on a 'Rickroll'
    7 points
  31. For me using xp is not just the internet. It is lot more too. I got adobe photoshop, gimp2, paintdotnet, illustrator for photo editing. Then pinnacle 12, adobe premiere, avidemux for video editing. For listening radio/scaning radio freqs I got SDRsharp with RTL-SDR dongle. For tv I got happauge wintv soloHD DVB-C/DVB-T/DVB-T2 tuner that I use with DVBviewer to watch/record free tv channels. Then I got lot of films/videos/music/other contect on my hdd and windvd to play ones I got on dvd. For remote management of computers I got putty (latest build). Then I got old visual studio, pythonXP, microsoft XDX, symbian SDK for coding. For web I use mypal browser by Feodor2 and for email mailnews and for chatting escargot msn messenger 7.5 trough httpsproxy. I am sending this post from that xp system. For word editing office xp and openoffice. For pdf view sumatrapdf, then to sync data off phone nokia pc suite Then got plenty of games (half-life 1, 2, ms flight sim 2004, sims3, toca 3, quake 3, doom3, gt legends, dirt for starters) and all of my games controllers works on xp. I cannot see lot more things I would have to do on pc. So no XP is not going anywhere soon on me. And for some claims I found online. 1. XP will get flooded with viruses when connected to internet: well possibly will get attacked if connected to internet directly with public IP like ADSL broadband did back in 2005 here. 80% of computers are not connected to internet rather to lan that redirects requests to gateway on router and to internet. I got NAT and proper network level firewall (no upnp) and did not have that issue. I also use up to date browser with noscript 2. XP cannot support sata hdd or over 137gb hdd: yes xp cannot see more than 137gb if you got pre sp1 xp and no services packs at all. For sata if on achi mode need have sata controller driver I got 2x1tb hard drives on xp at SATA mode (both formatted at setup) and zero issues 3. XP cannot utilise multicore cpu: XP home edition is limited to 2 physical cpu/cores and pro to 4 physical cpu/cores. Multi cpu and core systems were out way before even vista came out. I have seen xp workstation with 4x pentium 3 xeons long ago. I got quad core phenom x4 945 and all cores works well on multicore enabled application. 4. XP is not optimised to fast computers: how do you define fast system? And it is not xp that utilises all system resources to it own use. Apps do and I have used lot of cpu intensive apps without notable slowdown compared win10 for example on same pc if no sure test it and do not believe all FUD they spread online.
    7 points
  32. I wouldn't consider myself to be a hardcore diehard; I just enjoy it, and for me, it's a challenge to keep it running. When somebody says you 'can't' do something, that makes me want to prove them wrong even more! I intend to hold on to it so long as my aging hardware continues to grow old gracefully :)
    7 points
  33. for people who can't register here, there is another place you can create post for asking/help besides in github and blog: https://forum.eclipse.cx/viewforum.php?f=33
    7 points
  34. 7 points
  35. I was under the impression that this topic is about using software that requires Win7 or above on Vista with the aid of win32’s extended kernel. It has become clear to me that you are not particularly interested in security software, and therefore see no reason why others wouldn’t be content with a legacy version of Malwarebytes. Personally, I am not very interested in gaming, but I would never presume to declare all discussion of PC games as being OT in someone else’s thread.
    7 points
  36. That's *NOT* the right attitude at all: when one posts something one deems useful, but then nobody else seems to notice it nor react to it, that content ought to be let stand, nonetheless. We here post to help others, even if we never get any feedback on it, let alone any kudos. To delete the content out of spite for being ignored is very much frowned upon here (even if it's quite typical of the worst the 21st century has brought us: an oversensitive generation).
    7 points
  37. Thank you for the kind words about my father. Rudy has two sons. Jason loew is his blood son and we have the same mothers and I am Tony Sotomayor. Rudy was my step dad. I miss him so much.And Im glad to see how he impressed his fellow programmers on this thread and how much they respect his work. I knew as a child Rudy was very intelligent and a gifted programmer. If anyone would like to download a picture of Rudy when he was in his last year in College at University of Oklahoma 1970(Sooner 1970). I have a pic of him that was taken of him at the Engineers Club Engineers week party pic. Maybe someone can put it on this thread or something? He was young fresh leaving college and healthy. Picture is how I like to remember him. You can email me direct for that pic or anything else you want to know about my dad at jasongeo2@aol.com
    7 points
  38. Upstream support forum thread: https://forum.palemoon.org/viewtopic.php?f=70&t=25435 Workaround, that will restore ~ 95% of GitHub's lost functionality: Install github-wc-polyfill-1.0.3.xpi from: https://github.com/JustOff/github-wc-polyfill/releases/tag/1.0.3 All credit goes to (upstream) Ukrainian developer @JustOff ; however, that extension was created with official Pale Moon in mind, hence its install.rdf file has: <em:minVersion>28.14.0</em:minVersion> Should install as is on Mypal 28.14.x (if that's what you want it for ), but to install on latest New Moon 28, one has to edit that line to read: <em:minVersion>28.10.2a1</em:minVersion> The add-on itself has been probably inspired by the WebExtension add-on Polly, that was created for Waterfox Classic users to mitigate GitHub's breakage on Oct 14th 2020... Polly targets a Firefox 56 fork, which has a lot more WebExtension APIs than either Serpent 52.9.0 or Centaury; as a result, Polly will install on Serpent/Centaury, but won't work as designed... Additionally, Waterfox Classic users can (mostly) fix GitHub by toggling dom.webcomponents.enabled to true but, while the same pref does exist in UXP browsers, Web Components support in UXP is extremely unripe/at a very early stage... FYI, github-wc-polyfill extension embeds a base64encoded copy of https://unpkg.com/browse/@webcomponents/webcomponentsjs@2.4.4/webcomponents-bundle.js https://github.com/webcomponents/polyfills/tree/master/packages/webcomponentsjs#using-webcomponents-bundlejs ======================================= Some background: Before the Microsoft buyout () , GitHub would support the latest version of major browsers like Google Chrome, IE/old Microsoft Edge, Safari, Firefox, and care would be taken to not break the current ESR version of Firefox; additionally, "legacy" browsers like Pale Moon, Basilisk, Waterfox (Fx56-based) were "whitelisted" and treated in a special manner so as to remain compatible, but still on a best-effort basis... It well appears that now the "old" team of GitHub developers, the ones sympathetic to "legacy" browsers, have been set aside by the new management, which is hardly any surprise as Microsoft have colluded with evil Google, the net effect being that currently GitHub only caters to the four iterations of Chromium that dominate the browser market (Google's Chromium=Chrome, Microsoft's Chromium=[New] MS Edge, Apple's Chromium=Safari and Mozilla's Chromium-wannabe=Firefox [Quantum] ) ...
    7 points
  39. One year ago today... Rudy, you are sorely missed!
    7 points
  40. W2k3_SETUPLDR_SP2_to_SP1.xdelta3Most of us don't really need/use the WAIK to build our custom WinPE's. So there were always a problem to get the few tools like wimgapi, imagex or the WIM filter drivers. Attempts were made to use httpdisk to download files from inside the WAIK iso, but it was not a good solution as you still need to load hundreds of MB and it requires to install an unsigned driver. You even had to set your x64 Windows in testmode ... But now we came with a good solution: Our tool uses cURL winhttp functions provided by Homes32 to download only the needed bytes for the hugh WAIK ISO's. There is no need for admin rights and you only need to download 4-6 MB per choosen WAIK. For command line: GetWaikTools -? W2k3_SETUPLDR_SP2_to_SP1.xdelta3 GetWaikTools.zip
    6 points
  41. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20210320-86023e9-uxp-d249dd517-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20210320-86023e9-uxp-d249dd517-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.8.win32-git-20210320-86023e9-uxp-d249dd517-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.3a1.win32-git-20210320-bb6dab5c5-uxp-d249dd517-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.3a1.win32-git-20210320-bb6dab5c5-uxp-d249dd517-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.3a1.win64-git-20210320-bb6dab5c5-uxp-d249dd517-xpmod.7z Official UXP changes since my last build: - Issue #1746 - Update pkix code with later NSS code. (005d9c42d) - Issue #1746 - Revert "Additional configuration for NSS lib update." (0038394c3) - Issue #1746 - Revert "Update to NSS 3.59.1.1" (52d5ff242) - Issue #1746 - Revert "Update NSPR to 4.29" (dc468397f) - Revert "Issue #1743 - Update CK_GCM_PARAMS use for PKCS11 v3.0 in WebCryptoTask" (d830832cb) - Issue #1693 - Update NSS to 3.52.1-RTM (fd9fc4ea6) - Issue #1693 - Update NSPR to 4.25-RTM (a9a050901) - Issue #1743 - Update CK_GCM_PARAMS use for PKCS11 v3.0 in WebCryptoTask (4397303e5) - [NSS] Implement constant-time GCD and modular inversion (2642a2150) - [NSS] Prevent slotLock race in NSC_GetTokenInfo (156287f0d) - [NSS] Update root certificates. (c46598c11) - Issue #1693 - Update NSS to 3.52.2-UXP (958eb2936) - Clobber for NSS update (494718c32) - [NSS hotpatch] Hard disable AVX2 in NSS Build System (29a5601f3) - [Toolkit] Update TwemojiMozilla font to 0.5.1 (Twemoji 12.1.6) (6a6772f48) - Issue #1744 - Remove the ability to accept Firefox GUIDS (remove the dual system) (3aa334d0b) - Merge pull request 'Remove the ability to accept Firefox GUIDS (remove the dual system)' (#1748) from athenian200/UXP:phoenix_extensions into master (3064ad3ef) - [CSS] Enable scrollbar-width keyword by default. (d249dd517) Official Basilisk changes since my last build: - Back-end branch pointer update (2ccf2a7) - [SSUAO] Update UA override for YT studio (86023e9) Official Pale-Moon changes since my last build: - Issue MoonchildProductions/UXP#1744 - Remove the ability to accept Firefox GUIDS (remove the dual system) (86e5b48c5) - Merge pull request 'Remove the ability to accept Firefox GUIDS (remove the dual system)' (#1864) from athenian200/Pale-Moon:phoenix_extension into master (bb6dab5c5) My changes since my last build: - Skipped NSS and NSPR changes since I want to keep using NSS 3.48.x in the moment - Skipped Issue #1744 related changes - update TwemojiMozilla.ttf to v13.0.2 based build. (af8585d4f)
    6 points
  42. I recently started a separate site with more details on the extended kernel. You can find it by searching "eclipse" and the TLD for Christmas Island. But yes, I am trying more invasive methods of version spoofing, which have worked for the .NET Core 5.0 installer, but make Steam think it's offline, while Office has yet to be tested.
    6 points
  43. To each their own, but since you bring it up and seem to be requesting feedback -- my feedback is this, I DON'T GIVE A RATS ARSE ABOUT "UPDATES". The very FIRST thing I do whenever I install ANY operating systems is to DISABLE UPDATES !!! !!! !!! However, I do SLIPSTREAM updates before every installation - so I do "update". And one of the things I *LOVE* about Win XP is that I don't have to WASTE THE TIME slipstreaming MORE updates. I stopped slipstreaming and patching SO-CALLED "risks" in June 2017 on this computer (WinXP x64) and in January 2018 on my SIX computers running WinXP x86. I do NOT run antivirus - haven't for a good 15 years or so. If you know "how" to use a computer and know when to click and when not to click and if you do NOT let your software "phone home" and if you only allow WHITELISTED javascript, then "you'll do just fine". And make sure your hardware firewall (I also no longer waste my time with software firewalls) is set up properly. "You'll do just fine". WITHOUT concerning yourself with HYPOTHETICAL "so-called" 'security risks' propegated by an industry perpetuated as "needed" only when you allow 12 year olds to install "games" or when grandma installs some "coupon app". But anywhoo...
    6 points
  44. This is one of the worst threads I could think of to have pinned. Pinned threads are reserved for important information that generally affects everyone using the OS. If there was a crucial fix that applied to everyone or just about everyone, then it warrants a pin. But pinning a thread will not give it more attention. I don't even know what the original post said but even then, this is more of a per user basis issue and not a widespread problem. I mean, you don't even have much explanation about what's so slow about it or when it occurs so how does that help anyone?
    6 points
  45. Hi everyone, My name is Ricardo and I'm 25 years old. I am a big collector of vintage hardware and software and have been for about half of my life. My daily occupation is IT support for other companies and mainly with Windows client/server networks. Besides this I have always been a big fan of social events, tinkering, cars and I have a big general interest towards fascinating things.
    6 points
  46. New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20210102-6d7bb9f-uxp-0bb464bfc-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20210102-6d7bb9f-uxp-0bb464bfc-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-20210102-6d7bb9f-uxp-0bb464bfc-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-20210102-ddf403cf3-uxp-0bb464bfc-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20210102-ddf403cf3-uxp-0bb464bfc-xpmod.7z Official UXP changes since my last build: - Issue #1053 - Part 1c: Remove references to mobile/android targets and paths (9f004841a) - Issue #1053 - Part 2a: Remove android from /layout (partial) (ae2a16034) - Issue #1053 - Part 3a: Remove Android conditionals from /gfx (8d4456c79) - Issue #1053 - Part 3b: Remove AndroidSurfaceTexture and Android media decoder interface. (e011a048e) - Issue #1053 - Part 2b: Remove android from /layout reftests (0bb464bfc) Official Basilisk changes since my last build: - update link to new repo (dec2340) - Merge pull request 'Update link to new repo' (#35) from micwoj92/Basilisk:master into master (6d7bb9f) Official Pale-Moon changes since my last build: - [SSUAO] Add netteller to UA overrides. (ddf403cf3)
    6 points
  47. Merry Christmas to all of you wise folks on this wonderful forum and Happy New Year 2021!! Let's hope for the best and prepare for the worst. Stay safe, stay online and have a wonderful time!! (BTW, I'm a Hindu so I don't celebrate Christmas myself)
    6 points
  48. 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
    6 points
  49. 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 points
  50. With all due respect, probably because the older software still performs perfectly and is licensed for life, while an upgrade would require a new and expensive license just for show purposes, since it adds nothing really needed. Do you think people are made of money? Moreover, you yourself told he's gotten his clinic renovated... for normal human beings, there's only so much money (more so in times of covid-19, on top of it)!
    6 points

×
×
  • Create New...