Leaderboard
Popular Content
Showing content with the highest reputation on 12/17/2020 in all areas
-
Now that I'm revisiting 32 bit components, I'm wondering where this came from? It's not in my One-Core-Api binaries or 7 or 8.1. I am having serious thoughts about putting it into ntk32 to make as portable as kernel32/ntdll components, especially if somehow I have to use the 7 implementation. ntk32 also has the advantage in that I can properly expand the import table as it's in the "right place" (bottom of reloc section - weird but it works). I found that certain functions are perfectly importable by my new functions, but others like NtQueryInformationProcess and RtlSetThreadErrorMode are not.2 points
-
For people who enjoy testing. I would like to express my thanks for the work. Jumper, I know you've spent endless hours with the further development of KernelEX. I'm able to run Firefox 35 and even 52.9 and see almost the whole contents of the web on Windows Millennium again. Versions 24 up to 35.0.1 are still usable for some websites. However, these versions are no longer up to today's requirements. There is a workaround to run higher versions up to 52.9 as well as RT's Serpent 55/52, NewMoon 28 and others - see below. ftp.mozilla.org/pub/firefox/releases Firefox Portable: sourceforge.net - FirefoxPortable Firefox 24.0 - 35.0.1 Requirements: KernelEx: KernelEx.dll 4.5.2016.25, Kexbasen.dll 4.5.2016.25, Kexbases.dll 25, Core.ini 25h with Kexcom.dll 18, Sheet.dll 19, verify.exe 18 and VKrnlEx.vxd of 18 Set Firefox.exe, Xul.dll and furthermore for portables the FirefoxPortable.exe to Windows XP SP2 or higher. Otherwise you get an error "Couldn't load XPCOM". Explanation: Xul.dll is set to 2k in the Registry (HKEY_LOCAL_MACHINE\SOFTWARE\KernelEx\AppSettings\Configs). This string entry *\XUL.DLL="NT2K" can be deleted to get the file in follower mode (default). Reboot required. 2k mode was set on Xul for older FF versions like 9.0.1. Don't choose Legacy WinXPSP2! Firefox will be very unstable. Recommended Hardware: Pentium 4 or newer processor that supports SSE2 512MB of RAM 200MB of hard drive space After version 48, SSE2 CPU extensions are going to be required on Windows. Improved version 31.8 for ME/98: Details: Download: Firefox 31.8esr portable Extensions: Compatibility PlainOldFavorites 1.3.1 Firefox 3.0 - 56.* QuickJava 2.0.5 Firefox 20.0 - 36.* QuickJava 2.0.6 Firefox 33.0 - 36.* ClassicThemeRestorer 1.5.3 CTR Firefox 29.0 - 50.0 Newer Versions and Forks: Firefox 42.0 - 48.0.2 Additional requirements: SeaMonkey Thunderbird Cyberfox, GNU IceCat Light Browser NewMoon 27 Firefox 49 - 52.9, Mypal 28/29, Centaury and SeaMonkey 2.46 - 2.49.5 , IceDragon Requirements: Extensions: Classic Add-ons Archive (Firefox 45 - 56). It is a very large collection of extensions and is almost indispensable. FF43 - 47 and 52 ESR: "xpinstall.signatures.required" => false to install unverified add-ons (already set in RT's builds). A workaround is required for versions 48: Override the Firefox Add-on Signing enforcement This is usually also necessary for higher versions, but not in every case. Firefox extensions on archive.org/WaybackMachine Firefox Legacy Collector Serpent/NewMoon 28/IceApe... - Testers are welcome. Short summary to run these browsers: Screenshot with add-ons Plain Old Favorites, Get Archive, Free Memory Button and Classic Add-ons Archive: Note: There is still no known workaround to run FF 36 - 41 (crash on start) and the corresponding forks with the exception IceCat 38. Versions 12 - 23 are freezing after some seconds and are useless in today's internet anyway. These are therefore no longer of priority interest. Limitations, issues, solutions, other settings and recommendations: Limitations: WebGL and Direct2D! Blocked for graphics card because of unresolved driver issues. Limited WebGL support with adequate graphics driver and graphics card: WebGL 1.0 based on OpenGL ES 2.0 and requires OpenGL 2.0 graphics driver support. 1. Nvidia Geforce 7 (full support OpenGL 2.0) 2. Drivers NV81.85 and higher 3. Settings: webgl.force-enabled => true and webgl.disable-angle => true Browser crashes or freezings are possible and are probably caused by graphics drivers infirmities. So turn it on only when necessary. WebGL-Renderer ANGLE: 1. It needs at least hardware providing DirectX VertexShader 2.0 and PixelShader 3.0 (vs2.0 ps3.0), DirectX 9c. (graphics cards Nvidia Geforce 6 and 7 series - Shader Model 3.0) 2.Setting: webgl.force-enabled => true It doesn't cause any crashes or freezings. It can be switched on permanently. D3D11 compositing: There is simply neither OS/Software support nor a DirectX11 capable graphics driver for ME/98. First Nvidia graphics cards with DX11 support come with GeForce 400 series. Direct2D requires Direct3D 11 compositing. There is no workaround. Common issues: * It is becoming more and more common that some web pages no longer open. For this reason an user agent switcher addon like User-Agent Switcher 0.7.3.1 (Firefox 1.0 - 56*) is increasingly important. First certificates may also have expired. The cert file is nssckbi.dll (NSS Builtin Trusted Root CAs). Replace the file by a newer one of Firefox 52 or higher. * Sound/audio doesn't work with vxd sound drivers (see topic). Use a WDM driver. The support for vxd sound drivers has been removed with version 15. Issues all versions 24 - 52 and forks on ME/98SE: * Adding bookmarks doesn't work (also the popup - dialog window doesn't occur). Recently visited addresses aren't saved. Partial solutions: The History and the Bookmarks created on XP+ can be used on ME/98. Copy the file places.sqlite of your Firefox profile on XP+ into the profile folder of Firefox on ME/98. And there is the bookmark extension PlainOldFavorites. * Firefox crashes with Adobe Flash plug-in activated. Make sure that this plugin is disabled. If it is still needed, deactivate the plugin container: dom.ipc.plugins.enabled;false and dom.ipc.plugins.timeoutSecs;-1. The boolean "dom.ipc.plugins.enabled" has been removed with version 43. * Own fonts of pages can be blurred or unreadable. Recommended: Uncheck "Allow pages to choose their own fonts". Tools > Options > Content > Advanced * The popups for installing addons, saving passwords and such have big black lines around them. * The button on the download popup "open containing folder" has no function. * Printing doesn't work. * Squares and boxes instead of icons: Install suitable fonts - Awesomefont (version 4.7 tested) for this Site and and see Workaround Possible setting (You can even see the "search magnifier" and the "Rate stars"): browser.display.use_document_fonts;1 gfx.downloadable_fonts.enabled;false Note, older versions, like 4.7, have recently been removed from GitHub, but are available on archive.org or fontawesome.com/versions. * Last character of the URL in address bar is missing - The search bar can also be affected: Different solutions are possible. * Possible: Second process "Explorer" remains after close. Open the Taskmanager and close the lower (second) "Explorer" process. * Cookies may not be saved correctly and aren't recognised after browser restart. There is no workaround. * Download list in Library is empty after browser restart. * If you can't set Firefox as default browser: Start=>Run > ...\uninstall\helper /SetAsDefaultAppGlobal Install version: C:\Program Files\Mozilla Firefox\uninstall\helper.exe /SetAsDefaultAppGlobal Portable version e.g.: H:\Programme\Firefox\52.9.1\App\Firefox\uninstall\helper.exe /SetAsDefaultAppGlobal Note, that the used profile isn't the portable one initially. Usually "C:\WINDOWS\Application Data\Mozilla\Firefox\Profiles", if not changed. * NewTabPage doesn't work. You can set an url with an extension like ClassicThemeRestorer or newtab.url or others. FF49 - 52.9 and forks: * Slipped letters. Open about:memory and press "Minimise memory usage". The addon FreeMemoryButton allows to minimise memory with one click only. Mypal 28/29 and NewMoon 27/28: * Input in address bar doesn't work on second browser start anymore and Search Engine List is empty. Problem solving: With the first run you can remove search engines you don't want from the Search Engine Manager list and then set the search.json file in the profile folder quickly to read only. After that add your favorite engines and set a Home Page. Restart FF and check the functionality. If the first attempt fails, delete "search.json" and "searchplugins", restore the original state (Restore Default Search Engines ...) and try it once more. If you despair, delete (or rename) search.json , create an empty text file, rename it to search.json and set it to read-only before you start the browser. Mypal 28/29: * Low GDI resources - Possible problems with programs starting/running at the same time. Open about:memory and press "Minimise memory usage". The addon FreeMemoryButton allows to minimise memory with one click only. * Sometimes I can't close Tabs after a while. Restart Mypal when it annoys. * Sometimes - Error in Xul (browser restart required) Spoiler - issues FF 24 - 51 on ME/98: All significant issues should be ascertained. Other settings: * FF24 - 26: "security.tls.version.max" should be set to 3 (TLS 1.2 enabled). TLS 1.2 is enabled since version 27 by default. * Youtube: Note - The button "Remind Me Later" on request page for Browser update doesn't work anymore. This means that youtube no longer works. Now also version 52 and Mypal 29.3 are affected. One solution is to change the useragent (Firefox 68 or higher). Or you can use RT's forks like Serpent or Newmoon anyway. Another possibility seems to be to set in options "Limit Cache to MB of space" to 0. This disables disk caching. FF33 - 35: Set "media.mediasource.enabled" to true. (probably obsolete) It's possible to enable "media.mediasource.enabled" on lower versions, but it's quite likely useless. FF42: Set "media.mediasource.webm.enabled" to true. (probably obsolete) It should run on FF43 and higher by default. In case the player doesn't run on FF43+, set "media.mediasource.webm.enabled" to true, too. (probably obsolete) Settings not needed, but interesting - matter of taste: * "browser.tabs.onTop" => false to move the Tabs toolbar below other toolbars (FF24/27). FF 29 and higher: You can move the browser tabs with the extension ClassicThemeRestorer. * "browser.search.showOneOffButtons" => false to restore Firefox's classic search where you could see the favicon for the current search engine (FF33 - 42). However, the new search should be a bit faster. * "browser.urlbar.trimURLs" set to false to see protocol / scheme in URL (http/https...) * "browser.tabs.closeWindowWithLastTab" => false avoids browser exit and can show the homepage Recommendation for testing: Use portable versions or create different profiles for the installed. In the second case call the Profile Manager (Start > Run > ..../firefox.exe -P) or open "about:profiles" (Firefox 46+ only) and start the Profile Wizard. A note about my test environment: All my observations, tests, and findings were on real machines and not on a VM. All processors (Intel) meet SSE2 or higher and memory sizes are 2 and 3.5 GB RAM. The graphics cards are NV GF7800GT, NV GF7900GS, NV GF6600GT(AGP) and NV GF5900XT(AGP). And my OS is Windows Millennium. Recommended versions for use on ME/98: Update cert file nssckbi.dll by a newer one of Firefox 52.9 or higher For troubleshooting see issues KernelEx Core Updates only: Version 27.0.1 (Tab bar glitch easy to solve) or better Improved 31.8esr CPU Instruction Set SSE (Pentium 3 / AthlonXP) only systems: KernelEx Core Updates and some dll files required Version 45.9esr or 48.0.2 CPU Instruction Set SSE 2 and higher (Pentium 4 / Athlon64 and newer) systems: Note additional requirements Version 52.91 point
-
Hi this forum post is to share your experiences with windows 8.11 point
-
Hello , I really want you to share your Microsoft Windows Vista updates' experience ! I've never installed any updates on my Vista , and I'm still alive and well , no "evil viruses" during all these years (since approx. 2008) , when I first started to use Vista . Yes , I have Framework 4.0 installed , but that's pretty much it . Please stay on topic and try to include your hardware config , also KB number and you service pack , which was installed at the time of the mentioned update , this is a must . The description may be short , for example : "My PC started to freeze after the installation of KB x.x.x.x.", "My boot time increased by xx milliseconds , after KB x.x.x.x. The initial time was xxxx ", thank you very much. The idea is to create a database of the most successful / needed updates for each service pack !1 point
-
Hello all. Of course my user name is 704Mainman. I live in Greenville,SC and could be considered a "novice" when it comes to many areas involving Windows XP. Ah heck, Windows 7 and Windows 10 for that matter. Anyway, I know Microsoft has ceased support for Windows XP way back in 2014. Yet, I still like Windows XP and continue to use it although the issues I am presently experiencing have become a real hassle. As of the present, many of the video clips I attempt to play come with the caveat, "No compatible source was found for this media." And believe me, this is a bummer. I am 73 years old thus my computer skills has waned somewhat. Therefore, it my hope that with the knowledge the individuals on this forum possess I will be able to take away the knowledge each of you possess and discover adequate solutions to my issues.1 point
-
It's from BlackWingCat's extended kernel, but it calls ole32.CoTaskMemAlloc directly instead of calling a function that calls it with LoadLibraryA and GetProcAddress. Also, here's the matching implementation of GetCurrentProcessExplicitAppUserModelID: mov edx, [esp+AppID] test edx, edx jz short loc1 mov eax, lpString test eax, eax jz short loc_7D04A866 push eax ; lpString call ds:lstrlenW inc eax add eax, eax push eax call ds:CoTaskMemAlloc mov [edx], eax mov eax, lpString push eax ; lpString2 push dword ptr [edx] ; lpString1 call ds:lstrcpyW xor eax, eax retn 4 loc1: mov eax, 80004005h retn 4 GetCurrentProcessExplicitAppUserModelID.hex1 point
-
Windows 8.1 is a SFF/tablet/emerging market SKU, which could only be the reason why it was installed on that HP. As an example, in the US, that OS would not be allowed to be put on that hardware, as can be seen in the specs which primarily shows Windows 7. https://support.hp.com/us-en/document/c03364089 If you had purchased this PC new from HP and it came with this OS, then you would need to get the recovery media from HP. Otherwise, you'd need to get a new license for an OS, Windows 8.1 or otherwise for reinstall. Because Windows 8.1 with Bing is not a retail edition, the installation media is not made available to the public.1 point
-
Yeah, it's very sad. As I said, Microsoft has forgotten about its longtime loyalist corporate and power user base and moved on to another market - the fickles who can't tell a computer from a hard drive from a tablet. Very sad.1 point
-
Your SSD is corsair, right? I think Corsair offers an SSD toolbox that performs manual trim and supports Windows XP through 10 Otherwise, you can use SSD tweaker pro (that's what I use)1 point
-
1 point
-
Well I randomly ran into this thread so why not to share my desktop too https://prnt.sc/w4n5am1 point
-
Now I will definitely NOT misspell your name ))))))))))))))))))))))1 point
-
1 point
-
It's 8.1.1.0, works FINE with Vista ! Pitch works too and very well . Hey , where's my upvote ?1 point
-
Installed just for you to see the option ! Yep , I was right ! Nero has "pitch tuning" option right in the Wave Editor !1 point
-
Have you ever heard of KB977675 ? "The issue occurs because of a deadlock between a thread in Windows NT File System driver (Ntfs.sys) and a thread in the Autochk.exe program." I have something similar (from time to time) with Haswell and SP1/SP2 , I can summon task manager and just start the explorer , though. I wouldn't say it bothers me a lot , but sometimes it just hangs up or shows this "famous" logon failure. I'd like to add , RTM is much less affected. https://www.thewindowsclub.com/microsoft-releases-fix-for-windows-vista-black-screen1 point
-
Warmest greetings from Europe ! Do you have experience with .lua coded games too ? Thanks1 point
-
Because it's intended to work on XP, which is a feat already, and 2k with KEx 28c ain't XP.1 point
-
A very strange situation on the x86 side of things; it appears that in general for some imported ntdll functions on x86, they crash when being imported. Forward exporting functions doesn't seem to work either. But replicating the ntdll function in kernel32 works fine (in the case of RtlSetThreadErrorMode). But what about NtQueryInformationProcess and the like? You can't put stuff that interacts with ring-0 all over the place! I'm not sure what exactly is wrong, but it may be some strange artifact of WOW64 switching/thunking. I have yet to test any kernel extensions on a pure Vista x86, but I did make an attempt at kernel extensions on XP x86 for a specific purpose and did not have issues with import calls failing much like on Vista WOW64. With these discoveries in mind, my solution to this problem is to take one of the components of the x86 ntdll wrapper, ntnew, which was to house the code for the new x86 ntdll functions, and add the new x86 kernel32 functions to it, thus it will now be known as ntk32.dll. This is how this wrapper will be structured: Programs needing new ntdll functions: call ntext.dll instead, which will forward new functions to ntk32.dll. Programs needing new kernel32 functions: call kernel32.dll, which is the existing one augmented with an expanded export table, which in turn will forward new functions to ntk32.dll. Hopefully this should maximize portability of the x86 extended kernel components between WOW64 and pure x86 Vista. I just hope that calling the Nt/Zw* functions will be successful as that has yet to be tested and I wonder if it will be possible from ntext as opposed to ntdll. That will be a major setback if it cannot. UPDATE: NtQueryInformationProcess called through ntnew (have yet to implement kernel32 stuff in there yet), is working.1 point
-
Well that's true, but there are plenty of workarounds for Windows 8.1. Windows 7 does not work curiously enough. No missing api error, but photoshop will not open.1 point
-
About the same as with windows 7 and its d3d12on7. getting 60 - 70 fps with rtx 2060 on medium. On windows 10 You can expect high at 60-80 fps. But this is just the beginning, I'm glad it started and runs reasonably ok. I don't have to use crapdows 101 point
-
if you don't have driver success with the Quadro NVS you can swap it out for a Dell 7800GTX 256mb. Bluetooth? absolutely- Dell 355 bluetooth module and D00748-001-002.exe (license will be an issue) Wireless? yes, if you can find Gigabyte GN-WS30N 802.11n mini WLAN Card, a 9x driver does exist if your dock device is flagged in system devices, Intel ICH2 has the driver I went through all this when I had my Precision M901 point
-
Wanted to addon even more: I can't believe that Microsoft, William Henry Gates the Third's large software company created the crap that is Windows 10 when I know that they have created wonderful stuff in the past such as Windows Vista, 7, XP, 2000, Office 2003-2010 etc.. I'm sure all of you retro Windows diehards share my opinions about Windows 10 and the MS of today. I want to conclude this post here by saying that Windows 10 is just crap with nothing very useful added to it (Task View is a new feature but I never used it and have never found it to be user friendly) and that Windows 95, 2000 and Vista are the gods of Windows OSes.1 point
-
I'm planning a clean install of 32 bit XP, and was wondering now that XP is out of updates what is the best way to go for internet security that still supports XP. The hardware is from the XP era, and wouldn't run win7 well AntiVirus: apparently comodo now has min win7 requirements; avast is still providing virus updates for XP Firewall: is windows firewall OK or is there something better that I should look at. Sandbox: Is it worth adding an extra sandbox like sandboxie? Browser: chrome and firefox are out. I have issues with both opening and displaying pages, though in different ways. Basilisk is now win7. I like UR-browser but Adaptive Bee claim it is min win7, however I've seen plenty of people who claim it still runs on XP. Has anyone got a recent version of UR running on XP? Or is there something else I should be looking at? Malware checker: I think malwarebytes still runs on XP. Are there any other must haves I should be looking at? I know I'm going over the top a bit, but with no more updates from MS and what ever I choose to install is not likely to be supported much longer I feel I should do my best to take a long term view with security. Thanks, for any advice you can give.1 point
-
Same here. Got about 12-14 units around me in this room, most of which might still work if provided proper peripherals and power. Scarce physical space though, and not enough peripherals. Ranging from my first computer ever - a 486DXII-66MHz IBM PS/ValuePoint - to some Intel dual core or so (that one I actually bought at the flea market). There are old archived third-party Pale Moon builds for early generations PentiumII/III and AMD Duron/Athlon lacking SSE2 and even for non-SSE CPUs. Unfortunately they only work in XP and later. Courtesy of user Mercury: - IA-32 (non-SSE) builds are here. Forum discussion (locked) here. - SSE-only builds are here. Forum discussion (locked) here. There is also a SSE-only Linux version here. Courtesy of user Walter Dnes. Forum discussion (locked) here. At the same archive location one may also find old versions for Raspberry Pi 2, Slackware, and maybe others. Please check the Pale Moon forum board for topics related to these versions. Nice find, it's been a long long time since I last visited their site, used to dabble with the BASS plug-in in AutoHotkey. I wonder if all additional plug-ins are also compatible with Win9x without requiring KernelEx. Trying it under Wine first, just for kicks. Requires at least one change in winecfg: comctl32.dll set as native, otherwise the Preferences panel will be empty. Same goes for Winamp 2. However, after finishing with the settings comctl32 must be set back to built-in and XMPlay reloaded, otherwise it will crash when trying to add a file/URL to playlist. For now it failed with UK BASS RADIO and s2.stationplaylist links but does play The HUM and most others (from links somewhere above). Will try to add some plug-ins, see if that fixes those stations. EDIT: added a few plug-ins including the one for AAC and now both previously failing stations are working.1 point
-
I dunno. I'm kind of neutral on this particular topic of file hosting sites. However, I will agree that there's lots wrong with the modern internet, particularly the (in my opinion) overemphasis on security. I can understand the need for good security for important things like online shopping, banking, and other such things. But why does every single website need to be forced to use protocols and cipher suites that only a few of the newest browsers (namely Chrome and its derivatives) support?! It's not like they're ALL dealing in sensitive info! For example, I don't see the point in Wikipedia using strict TLS1.2 and 1.3 (at least for the public side); for users logging in to create/edit pages, I suppose it's fine. c1 point
-
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-sucks1 point
-
Additional requirements for FF 42 - 48 and KM 76: Dll's from XPSP2 or SP3 (or ReactOS) (Activeds.dll, adsldpc.dll, apphelp.dll, authz.dll, dbghlp.dll, dnsapi.dll, mprapi.dll, netrap.dll, netui0.dll, netui1.dll, ntdsapi.dll, ntlanman.dll, rasdlg.dll, rasman.dll, regapi.dll, rtutils.dll, samlib.dll, utildll.dll, w32topl.dll, winscard.dll, winsta.dll), MDAC2.8SP1 (Odbc32.dll, Odbcbcp.dll), GDIPlus.dll (for KM76) and Kext (latest Kstub823, ini file here). The names of all missing files were found with the DependencyWalker (DW). To do this open the Xul.dll with the DW. Missing modules are marked with a question mark in yellow circle. To get all names you must refresh or restart DW after adding files. New (missing) files will appear. The new files bring up new dependencies. You have to repeat the procedure several times. I have these files, XPSP2/SP3 and some from ReactOS 0.4.0, in the system folder. You also can try to paste them in the KernelEx folder, or KernelEx Subfolders like ROS, as KernelEx-KnownDll's. In this case (KernelEx-KnownDll's) is the registry entry in the Key [HKEY_LOCAL_MACHINE\SOFTWARE\KernelEx\KnownDLLs] necessary. Or paste them into the program folder, when you're afraid. To bear in mind pdh.dll, psapi.dll, userenv.dll, uxtheme.dll and wtsapi32.dll are already supported by KernelEX (KernelEX-KnownDll's). Don't merge LZDLL_ME.reg or LZDLL.reg for Win98 of KernelEx update18 into the registry! Firefox will crash immediately on start . The portable Installer requires the apphelp.dll. It make sense to install the WindowsInstaller 12.0.2600.2, but I haven't testet it as requirement. Direct3D9 (OMTC): 1. Install DirectX 9c 2. "layers.acceleration.force-enabled" => true - OMTC requires hardware acceleration! 3. "layers.offmainthreadcomposition.enabled" => true (default value) I did all the tests with the portable versions and I only testet with NV7800GT and NV7900GS cards and drivers 82.16 and 82.69 on WinME This may not work with other hardware.1 point
-
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).1 point
-
[had to correct this, the "listdevices.txt" was misleading, only exactly ONE driver supports GTX 970 and GTX 980. Other GTX 9x0 / Titans were mentioned in later drivers, but were not in the inf files.] Interesting find while explicitely searching for drivers older than those on the NVidia-Site, but after the launch, on www.forum-3dcenter.org http://uk.download.nvidia.com/Windows/344.11/344.11-desktop-winxp-32bit-international.exe More infos: https://www.forum-3dcenter.org/vbulletin/showthread.php?t=556959 I tried it, and my GTX 970 was detected and runs fine (no SLI, though, even though it is active, and detected on W10 64bit). Excerpt from ListDevices.txt: NVidia mostly lists drivers AFTER this one on their site (there may be one or two more inbetween containing the 970+, but i did not detect any more. Jaclaz?). Oh, and one further insight: There exist inf-files for OEM cards (i.e. nvmii.inf for MSI) that indicate later drivers (347.25, 347.88) support these cards as well, as long as they are from said OEM. (look i.e. here: https://forums.laptopvideo2go.com/topic/30969-modding-nvidia-oem-inf-files/ ) Using these may be possible, but as these may have other settings (assuming OC, requiring better cooler, etc.), it is always a bit risky. If they can be used for your card without inf-modding, you just pinpointed a driver tailor-made for your card, congrats... Starting with version 350.xx, 970+ are neither mentioned in the listdevices.txt, nor in inf-files. I suspect, this has something to do with XP 32bit dropping out of support with Microsoft on April the 8th 2014, so NVidia possibly joined the bandwaggon here... or was "encouraged" to do so by Microsoft, and only OEMs that were complied to deliver drivers for a certain time got some support. But thats just guesswork... For modding inf-files to have 970+ GPUs use the GTX 960 drivers, which seems to be working well, search on MSFN (maybe later i'll link to those threads - give me some time...). According to an analysis of the later drivers, of which the 368.91 (iCafe) seems to be the latest, while 368.81 is the latest generic, remember, that there exists more than one GTX 960, so choose well: NVIDIA_DEV.1401 = "NVIDIA GeForce GTX 960" NVIDIA_DEV.1406 = "NVIDIA GeForce GTX 960"1 point
-
1 point