Leaderboard

It is fine to point out that something doesn't work as advertised, but removing the content (as well as the reply about how reliable the information is) wouldn't do anyone any good. As then it could just be posted by someone else again. Leaving it the way it is now leaves it "on the record" in case anyone else happens to find it. Especially anyone who finds the post from a search engine. We are in the minority by posting on this site. Many more people use MSFN for info and never register or even post. I know many people in the local IT community who use this site but do not have accounts.

Firefox's libcubeb has been updated and the "Youtube video freeze" fix is now officially part of mozilla-central: https://hg.mozilla.org/mozilla-central/rev/c7768090c505715c543b2a71e42b07fcb905d7a9. Thanks again @roytam1 for submitting it! Let it not be said that MSFN hasn't contributed to upstream!

This information was added on 31 August 2021 https://betawiki.net/index.php?title=Windows_Vista_build_6003&oldid=153735 I understand that it might look suspicious when someone's first post looks like mine . In my opinion the extended kernel should target Windows Vista with 6003 and SHA-2 updates but without KB4341832, KB4090450 and KB4089229 - meltdown/spectre patches that slow down the CPU. Also, I have an AMD Ryzen PC so if @win32 decides to make a patch for Ryzen problems I can test it and send some logs.

Your skepticism is perhaps not unwarranted. I couldn’t help noticing that the BetaWiki link currently says “Last edited 5 days ago,” which was the same day the “news” appeared in this thread. Where did BetaWiki learn about this “new version of the HAL driver which fixes the corruption bug that affects Intel CPUs based on the Haswell and later microarchitectures”? Obviously not from the Microsoft link provided under References, which does not mention HAL at all. You also have a valid point that this discussion is rather OT here in the extended kernel thread. It might have been better to resurrect Server 2008 Updates on Windows Vista. (My link leads to the point where contemporaneous discussion of build 6003 began, but you wouldn’t find anything about Haswell+ issues there. Personally, I was rather concerned about 6003’s potential to break software that worked on 6002, and there were a few such instances.) Or perhaps Compatible hardware with Windows Vista, which AFAIK was where Haswell+ issues were first documented. On the other hand, I would very much like to hear what @win32 has to say about this HAL discussion. Your forum style is perhaps overly aggressive. I wouldn’t be surprised if TSNH feels offended, because I was once offended by one of your attacks. Let’s seek the facts without any flame wars.

4e is in relation to a user who is posting about a project they have created or is involved in, that is vaporware, or that the person is making promises about accomplishing something in the future but doesn't live up to the promises. So it is not relevant here, since the entity that made this so-called Vaporware is Microsoft and not the person who posted a link to it. Since Microsoft doesn't have an account, they can't get banned for posting about vaporware or have their posts deleted.

With the Covid-19 pandemic still smoldering, and occasionally flaring up, many of you may be working from home, and using Microsoft's Remote Desktop or something similar to access your work PC. I've been doing that for a year and a half now, although since getting vaccinated I do occasionally go to the office. One major nuisance I kept running into was that, when using any Firefox-derived browser (I generally use @roytam1's Serpent but they were all affected), certain Web sites would freeze Remote Desktop up. The only thing I could do was click to hide the browser window, disconnect, reconnect, and hope that it wouldn't lock back up again as soon as I brought the window back. A very frustrating way to work, and forcing me back to the office more than I'd like. The other day I found a solution. I was in the office, and experimenting with the setting layout.frame_rate in the about:config page. It had somehow gotten set to 240 on my Serpent browser, I think as a result of the "UOC Patch". I reduced that to 60, my monitor's actual refresh rate, and got a noticeable performance improvement at work (where I was not running Remote Desktop, of course). But once back home, I still had problems with Remote Desktop. Apparently too high a setting overloads the Internet connection, causing the desktop to slow down or even stop for long periods. And Remote Desktop has no way to "dump the queue" other than disconnecting and reconnecting. So I decided to try reducing it further. When I went down to about 12, my Remote Desktop problems went away! Animations started looking pretty jerky, though, so I did some more experimentation: in my case, 20 was still too high, but 15 was just right, giving animations that didn't look too jerky without Remote Desktop freezing up. I'm guessing the ideal setting depends on many factors, with the speed of your Internet connection probably being the most important. So if you're in the same situation, you'll need to experiment to find the best setting of layout.frame_rate for your environment.

Everything is in HKEY_CURRENT_USER\Software\StartIsBack. Doesn't even require admin rights if you use reg.exe import/export.

I'm running vmware workstation 10.0.7 just because a discussion a few months ago in the ex kernel thread lead me to believe that this is the best version (I know I can get newer versions running) Updates up to Apr. 2017, KB4474419 v4, KB4493730 and rootsupd. That's all

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211023-06f122f42-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211023-06f122f42-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20211023-06f122f42-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20211023-06f122f42-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: - fix assertion (528f0d0b2) - fix assertion (8ca4607ca) - fix broken assertions (8c64c1865) - fix debug code (6e37f6aa7) - remove broken assertion (090f9987d) - fix assertion according to bug Bug 1328251 (b3835e0c5) - fix debug code (f7a2841e6) - Bug 1226241 - Use a #define instead of a magic number for self-hosted function name accesses. r=jandem (01e2ec474) - Bug 1235656 - Part 1: Set canonical name in self-hosted builtins. r=till (43cbd7cb9) - Bug 912701 - When removing Unicode extension sequences from a locale, ignore similar syntax that might be found in a privateuse component. r=abargull (1524a8b48) - remove broken assert (a93490758) - remove broken assert (0ddc7e143) - fix missing bracket (c4f524729) - Bug 1179924 - Create a more modern JS object holder for cross-thread references to JS objects. r=smaug (0804d24cf) (27926d796) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1176004 - Make jstest's unix task runner a generator; r=sfink (03def3308) - Bug 1175708 - Followup to fix windows jstests.py bustage on a CLOSED TREE; r=meow (b291f8cd0) - Bug 1175636 - Do not spawn a watchdog for each test on Windows; r=sfink (c87370ba8) - Bug 1141283 - Compensate for stackwalk duration and sleep overhead when determining sampler sleep time. r=BenWa (cf155667f) - Bug 1172186 - Make the profiler build standalone. r=mstange (324ec7283) - Bug 1176028 - Use the jstest's task generator directly; r=sfink (6dac9eb7a) - Bug 1176064 - Do processing of the jstest's skiplist inline; r=sfink (af6dd9d06) - Bug 1165054 - Fix inbound bustage due to missing explicit on single arg constructor r=me (b29da4afe) - Bug 1182092 - Try harder to filter out template shapes with indexed properties when making unboxed objects, r=jandem. (2540ff768) - Bug 1180299 - Implement ScopeExit for running actions at the end of a scope, r=Waldo (dd40bb356) - Bug 1180536 - Use mozilla::ScopeExit to clean up Debugger::addDebugge#eGlobal's consistency on failure; r=sfink (3bec89179) - Bug 1170216 - When using the slow-and-standard path in js::SetIntegrityLevel, don't manually call setNonwritableArrayLength afterwards. r=Waldo. (563a26f28) - Bug 1171036 - Change GetLengthProperty slow path to use ToLengthClamped instead of ToUint32. r=Waldo. (c0431c393) - Bug 1170307 - Inline the common path of NonNullObject; use it instead of ReportObjectRequired in the Debugger. r=shu. (ff70c4e1c) - Bug 1167883 - Avoid huge stack frames and stack overflow issues with MSVC PGO builds. r=nbp (a02cdc599) - Bug 1181063 - Use mozilla::IsNaN and mozilla::IsInfinite in Simulator-vixl.cpp. r=Waldo, r=sstangl (552a22923) - Bug 1181152 - Make Trampoline-mips.cpp compile with clang. r=rankov (d3308f445) - Bug 1181581 - Fix some typos in comments. r=jandem (79c5de477) - Bug 1175714 - Watch for baseline frame values with nursery types during OSR, r=jandem. (765346890) (06f122f42)

I admire your zeal to investigate something that was reported April 25, 2019 by one member who now runs Windows 8.1. Are you thinking this report was “fake news” as Dixel might say? I was a little suspicious at the time, if only because no one else ever reported a VMWare issue whereas Avast/AVG users with exactly the same BSOD were posting far and wide. (The member lives in the Czech Republic, where Avast/AVG is based - possible motive?) But in fairness to a member in good standing, he posted some clarification about affected and unaffected versions on September 6, 2019 in a short thread that might interest you. While searching for that, I went back too far and found something else that might interest you: Windows Vista + Intel Haswell issues: Documentation.

Version 3.0

KB4489887 was a March 2019 Preview in which build 6003 was first introduced. For those actually running Server 2008 SP2, such Previews were Optional updates. I don’t think any MSFN member running Vista installed it at the time, since the build number change was not noted here until April 2019. About your BSOD: AFAIK those Win32k.sys BSODs were all attributable to applications that depended on version string “6002.” Even if you don’t use Avast/AVG, antivirus would still be my first guess. One MSFN member traced his BSOD to VMWare (see my link and read a few pages). If you can identify another program that was broken by 6003, I would be as interested as anyone. Since this seems to be the only Vista thread that new members want to read, I’ll mention that Avast solved their issue with a microupdate in June 2019. To install Avast 18.8 on 6003, I would try an online installer because the offline installer is older than the microupdate.

I suggest using a PORTABLE LOADER even with all of Roytam releases (similar to how my 360Chrome releases use a portable loader). For all of Roytam releases, use the official portable version from here -- http://archive.palemoon.org/palemoon/28.x/28.2.2/ I personally use only the 32bit version even on my 64bit systems. Do not "exectute" the file after you download it (the file name is Palemoon-Portable-28.2.2.win32.exe). Do not download the "latest and greatest" (it will not work on XP, if I recall, unsure). Extract the file into its own folder using 7zip or similar. Delete all of the files in the Bin folder and replace with your Roytam files for whichever browser you wish to run as portable. If it's a Basilisk or BNav browser, just rename the executable to palemoon.exe or dig through the .ini and edit accordingly. You'll have to learn a new portable loader .ini format but well worth it - I always run all of my browsers using a loader and .ini. You can copy your existing profile into the portable loader file structure, the default profile for a NM/PM is in User -> PaleMoon -> Profiles -> Default. I also do this for added security, my OS doesn't have a "default browser" and the OS can't open what it thinks is the "default browser" because the executable file no longer exists.

I am inclined to agree with that. Reports of limited improvement could be an example of the placebo effect.

Is a very bad driver , in my personal experience. Would you consider trying out 347.25? One of the best drivers for XP ! 347.09 is very good too.

I do not recommend UEFI multi-booting Windows Vista, 7, and 11. I tried so last night and while 7 and 11 loaded up just fine, Vista Blue screened with 0x01E. Keep in mind I was doing this on Ivy Bridge with a Windows 10 ISO that had 11's Install.wim. I suspect it might have something to do with 11's UEFI files. Regardless, I reinstalled the Vista and 7 dual-boot I had and am fine (this also allowed me to use a different extended kernel compatible/Vista ISO that actually had nothing broken or missing). So, let this be your warning to not multi-boot Vista and 11 with UEFI unless you know of a way to make it work without a 0x01E BSOD when booting into Vista. I should clarify that BIOS (MBR) multi-boot works just fine. I currently have a multi-boot of Vista, 7, 8.1, and 11 on an Acer Aspire A315-21 and nothing is wrong with it so far.

Hi, 1. As you may know Microsoft doesn't always document what they do. For example Microsoft articles about this update say nothing about files that this update changes. If we trust only the Microsoft's official statements than we should follow the guidelines showed here: https://support.microsoft.com/en/help/22882/windows-vista-end-of-support :) 2. 2 users have already tested this and said that this update (partially) solves Haswell+ problems. 3. I said "According to" meaning I don't know if that information is correct. I posted it here to encourage someone to verify it (as i cannot do it myself). 4. If this information turns out to be fake anyway, I'll do this and i don't need moderator's help. I really don't want to argue here.

You can actually change the audio backend in current Firefox versions by setting the media.cubeb.backend (string) pref. If you set it to winmm and restart the browser, about:support should show it under Audio Backend. At least it does on Windows 7, haven't tried on later versions. But since they rewrote the drivers after XP, the fix would be superfluous even when using WinMM. But it's still nice that it'll now be part of modern Firefox, considering the "MSFN hackers" meme, etc.

In User Data folder (same directory of 360chrome.exe), create a new folder ..rename it LuxLOL for example.. Send two shorcuts of 360chrome to the desktop... one for the default profile and the other for your new profile Right click on each shortcut, click on properties..shotcuts.. in taget, add at the end: (space)--profile-directory="Default" (space)--profile-directory="LuxLOL" it looks like that for example: "C:\Programs\360 browser\Chrome-bin\360chrome.exe" --profile-directory="Default" "C:\Programs\360 browser\Chrome-bin\360chrome.exe" --profile-directory="LuxLOL"

StartAllBack 2.9.95 (RC6) Available only if you check for updates I really want to finish with RCs, so please curb your enthusiasm

some 6th gen cpus matches performance of 8th gen intel cpu and that requiment is artificial by for needing that TPM chip for no good reason. I know Windows 11 been running fine on 2007 dual xeon board since @Dave-H mentioned from it on another topic. Whole system requiment thing is to milk off more from users

Do you really need Doom updated to enjoy it? The work of GZ was complete when the game was ported. Original games don't receive many patches and can continue to be played. Problems sometimes arise if you want to run them on very new systems, which XP is not. I don't understand the hatred expressed towards older Windows by developers who work on even more obsolete games. They wouldn't appreaciate posts on their forum saying how Doom sucked.

I would probably phrase it as, a developer un-crippling newer versions of Flash. It's still Adobe releasing them, but they're region-restricted to only run in China, and of course they have all the China-mandated spyware. Darktohka is stripping all that out so the rest of the world can use the updated (and presumably more secure, although who really knows) versions. But it's still Adobe's copyrighted product, and legally, they have the right to say "no" to what darktohka is doing. You'd think they wouldn't care - if folks are that determined to keep using their free product, why not let them - but maybe they made an agreement with the other members of the "Anti-Flash" consortium (chiefly Google, I suspect) to do everything they can to keep this old, not particularly secure, but popular browser plug-in dead & buried outside of China.

Microsoft’s article on KB4493471 (April 2019) and associated links don’t appear to mention Hardware Abstraction Layer at all. Since it was a monthly rollup, any subsequent monthly rollup would presumably include the undocumented changes and perhaps even undocumented bug fixes related to those changes (but the Security Only updates might not include anything of the sort). If one were to install e.g. KB4499149 from May 2019, they should be able to duplicate your results and would also be patched against the once-infamous BlueKeep vulnerability. It might be worth noting that the SHA-2 update KB4474419 was not a monthly rollup, although installing it would change the build number to 6003.

@win32, wait a minute ... I'm stunned , it's a legit win10 driver ported to Vista !!! This driver exists out there in the wild ... but for Win10 only !!! Just search for "nvidia driver 373.19" yourself . So the Fujitsu Siemens staff ported a win10 driver !??! And look at the date added "November 2017". https://drivers.softpedia.com/get/GRAPHICS-BOARD/NVIDIA/Acer-Aspire-TC-730-NVIDIA-Graphics-Driver-373-19-for-Windows-10-64-bit.shtml

New regular/weekly KM-Goanna release: https://o.rthost.win/kmeleon/KM76.4.5-Goanna-20211023.7z Changelog: Out-of-tree changes: * update Goanna3 to git f355dbe3d...06f122f42: - import changes from `dev' branch of rmottola/Arctic-Fox: - fix assertion (528f0d0b2) - fix assertion (8ca4607ca) - fix broken assertions (8c64c1865) - fix debug code (6e37f6aa7) - remove broken assertion (090f9987d) - fix assertion according to bug Bug 1328251 (b3835e0c5) - fix debug code (f7a2841e6) - Bug 1226241 - Use a #define instead of a magic number for self-hosted function name accesses. r=jandem (01e2ec474) - Bug 1235656 - Part 1: Set canonical name in self-hosted builtins. r=till (43cbd7cb9) - Bug 912701 - When removing Unicode extension sequences from a locale, ignore similar syntax that might be found in a privateuse component. r=abargull (1524a8b48) - remove broken assert (a93490758) - remove broken assert (0ddc7e143) - fix missing bracket (c4f524729) - Bug 1179924 - Create a more modern JS object holder for cross-thread references to JS objects. r=smaug (0804d24cf) (27926d796) - import changes from `dev' branch of rmottola/Arctic-Fox: - Bug 1176004 - Make jstest's unix task runner a generator; r=sfink (03def3308) - Bug 1175708 - Followup to fix windows jstests.py bustage on a CLOSED TREE; r=meow (b291f8cd0) - Bug 1175636 - Do not spawn a watchdog for each test on Windows; r=sfink (c87370ba8) - Bug 1141283 - Compensate for stackwalk duration and sleep overhead when determining sampler sleep time. r=BenWa (cf155667f) - Bug 1172186 - Make the profiler build standalone. r=mstange (324ec7283) - Bug 1176028 - Use the jstest's task generator directly; r=sfink (6dac9eb7a) - Bug 1176064 - Do processing of the jstest's skiplist inline; r=sfink (af6dd9d06) - Bug 1165054 - Fix inbound bustage due to missing explicit on single arg constructor r=me (b29da4afe) - Bug 1182092 - Try harder to filter out template shapes with indexed properties when making unboxed objects, r=jandem. (2540ff768) - Bug 1180299 - Implement ScopeExit for running actions at the end of a scope, r=Waldo (dd40bb356) - Bug 1180536 - Use mozilla::ScopeExit to clean up Debugger::addDebugge#eGlobal's consistency on failure; r=sfink (3bec89179) - Bug 1170216 - When using the slow-and-standard path in js::SetIntegrityLevel, don't manually call setNonwritableArrayLength afterwards. r=Waldo. (563a26f28) - Bug 1171036 - Change GetLengthProperty slow path to use ToLengthClamped instead of ToUint32. r=Waldo. (c0431c393) - Bug 1170307 - Inline the common path of NonNullObject; use it instead of ReportObjectRequired in the Debugger. r=shu. (ff70c4e1c) - Bug 1167883 - Avoid huge stack frames and stack overflow issues with MSVC PGO builds. r=nbp (a02cdc599) - Bug 1181063 - Use mozilla::IsNaN and mozilla::IsInfinite in Simulator-vixl.cpp. r=Waldo, r=sstangl (552a22923) - Bug 1181152 - Make Trampoline-mips.cpp compile with clang. r=rankov (d3308f445) - Bug 1181581 - Fix some typos in comments. r=jandem (79c5de477) - Bug 1175714 - Watch for baseline frame values with nursery types during OSR, r=jandem. (765346890) (06f122f42) * Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses. A goanna3 source tree that has kmeleon adaption patch applied is available here: https://github.com/roytam1/palemoon27/tree/kmeleon76

-1 = runs at default 60 FPS.

@SuperKolobok I hope i have now fixed all relative paths. WinNTSetup_v5021 will run a ScanFiles.cmd if exists. You could use something like the following to recreate WinNTSetup_mru.txt before it will be loaded: @echo off title Scan for files ... pushd %~dp0 >WinNTSetup_mru.txt echo [Source_NT6] for /f %%c in ('dir /b Sources\*.wim Sources\*.swm Sources\*.esd Sources\*.iso') do ( >>WinNTSetup_mru.txt echo Sources\%%c ) >>WinNTSetup_mru.txt echo [Drivers_NT6] for /f %%c in ('dir /b /ad Drivers') do ( >>WinNTSetup_mru.txt echo Drivers\%%c ) >>WinNTSetup_mru.txt echo [RegTweaks_NT6] for /f %%c in ('dir /b /ad Tweaks') do ( >>WinNTSetup_mru.txt echo Tweaks\%%c )

awesome, man. but can you make this also for control center icon? i personally hide the volume and network icon and use the new control center one only.

No, I said I won't do randomly customizable right-click taskbar menu. Policy fix was done the moment you reported it and is not worth discussing at all.

for the minibrowser, disabling the flag about USB stopped the crash when connecting mem usb sticks, justed tested, i guess that feature is for win7/10 about certificates, for example, in this site: hxxps://www.cine-calidad.com/blog/venom-2-se-acerca-a-cinecalidad/ 360 extreme explorer read the certificate as invalid, with minibrowser all ok... so i don't think is a matter of invalid windows config or bug, i already updated days ago certs with one of those links, actually 1.6 cert package

The update to remove Flash is KB4577586: http://download.windowsupdate.com/c/msdownload/update/software/updt/2020/10/windows8-rt-kb4577586-x64_3dde08cdb47cb317ba47a9181fceee09951c614c.msu

Thank you Andrey !

I'm sorry , I didn't notice you earlier , must have been the generic profile name , like Jonny88 , you know. So yeah , you have a Dell mobo , I see . I too like some of Dells , but there's no OC capabilities , sadly. Unfortunately anything below or even Haswell is too weak for my gaming needs , so I'm thinking maybe I need to purchase ryzen or pentium GOLD.

it depends from age of equipment. Caps from that era could dry out sometimes if been used but age did not always mean no drying. PS3 for example had issue with capasitors drying out despite being from 2007. And generally if under 10 years between use times it will be ok. Mostly seen dried caps on original Macintosh (before Macintosh was fancy cult symbol) that had been last turned on in 1992 and was turned on after 30ish years. So as long as you wont leave them stay there for 2040 without ever testing there should be no worries. Also solid state capasitors do not try out. This was more to your old capacitors.

Yes, I did get one digitally signed set working at USB 3 speeds. I don't believe they are posted in the forum however. I will send them if needed.

Oh , and I tried Win 7 Beta build 7000 , and it's the first beta to not have the logon bug on newer mobos. Earlier 6xxx builds will definitely have that bug.

Guys , I'm sorry to point that out to you , I understand you can't remember such things due to your age (5-7 years at that time?). Windows Vista Logon failure started to happen long before haswell or ryzen , It started right after SP1 came out , with it. It was Core Quad Era . Q6700 and the such . I had a Siemens PC with q6700 and Vista RTM didn't have that logon failure (we called it "Black screen of death") , but SP1 did ! If you have some time , scroll the ex-kernel topic back , somewhere closer to Dec. 2020 , I think . I'm sure you will find some links that I posted (from 2008 or so) , perhaps they are still alive . My guess : the culprit is the new activation they implemented in SP1. Where did you get that information about HAL ? Win32 told you so ?

+ to this issue i also have came across another one, its explained in screenshot reg entry was: REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Chat" /f /v ChatIcon /t REG_DWORD /d 3 OR can we have an options to edit taskbar rightclick context menu? for startisback and startallback? because on windows 10 we also have bunch of stupid things there such as: windowsINK and contacts. that i already removed as component as i did to widgets and chats. and they are still there? this feature for both products would be necessary don't you think? after all we are making taskbar configurable and easy to use without unnecessary things via your tools. and afaik they can't be edited via reg file they are inside dll?

Tahnks! That was it, I didn't expected for info about update in notifications area, I thought it will pop up some window within an app itself. But right I had my notifications turned off, now it's working

== Custom userContent.css == A custom userContent.css file (3 KB) can be downloaded below (login required). It enhances the default stylesheet used by RetroZilla and other browsers that support a custom userContent.css file (eg. Firefox, K-Meleon, Netscape Navigator). Only tested on one system, one monitor resolution and two browsers (K-Meleon, RetroZilla). Place the file in the 'chrome' subdirectory (create if not present) of the browser's profile. In RetroZilla the default path is: C:\WINDOWS\Application Data\RetroZilla\Profiles\default\your_profile\chrome\userContent.css The first section is a code snippet from @Siria that displays sometimes hidden webpage output. This occurs on occasion, you will see a block of webpage surrounded by a two pixel thick dashed red line. The second section helps view and utilize this MSFN forum, entries are commented for editing, modify as desired. Just a hack so the forum works a bit better, it won't fix everything. MSFN forum enhancements: - Prevent off-screen text output. - Gray background to visualize white text, change lightgray to darkgray for nightmode. - Box forum categories for better visualization (default blue). - Box forum thread topics for better visualization (default green). - Box member quotes for improved thread readability (default blue). - Box member signatures for improved thread readability (default yellow, must be logged in). - Shrink stretched/oversized member avatar images. - Remove duplicate member avatar images in thread posts. - Remove not useful mobile navigation clutter. - Display member menu when logged in, log out without toggling browser's Style to None. Note: It is still necessary to manually disable all 'style' to best visualize many problematic web pages. This often provides a cleaner layout and uncovers otherwise hidden text, pictures and hyperlinks. In RetroZilla toggle View -> Use style -> None and in K-Meleon use @siria's StyleKill macro (stylekiller.kmm). Review 'Vanilla Windows 98 Web Browsing Summary' for more Windows 9x web browsing information. https://msfn.org/board/topic/177106-running-vanilla-windows-98-in-2020-and-beyond/page/33/?tab=comments#comment-1189203 userContent.css

Yes, you can install Windows 7 in Ryzen computers. The problem is UEFI, there's a thread for installing it with UEFI. It works with windows 7

That fetches a .CSV file, inside which: ia64 Windows Server 2008,,,,,,, File name,File version,File size,Date,Time,Platform,SP requirement,Service branch Hal.dll,6.0.6003.20489,"428,264",21-Mar-19,1:32,IA-64,None,Not applicable File name,Ia64_hal.inf_31bf3856ad364e35_6.0.6003.20489_none_0726f69c1b902d52.manifest,,,,,, File version,Not applicable,,,,,, File size,"1,655",,,,,, Date (UTC),21-Mar-19,,,,,, Time (UTC),3:40,,,,,, Platform,Not applicable,,,,,, x86 Windows Vista,,,,,,, File name,File version,File size,Date,Time,Platform,SP requirement,Service branch Halacpi.dll,6.0.6003.20489,"137,960",21-Mar-19,1:53,x86,None,Not applicable Halmacpi.dll,6.0.6003.20489,"169,704",21-Mar-19,1:53,x86,None,Not applicable File name,X86_hal.inf_31bf3856ad364e35_6.0.6003.20489_none_072552a61b922456.manifest,,,,,, File version,Not applicable,,,,,, File size,"2,244",,,,,, Date (UTC),21-Mar-19,,,,,, Time (UTC),3:57,,,,,, Platform,Not applicable,,,,,, x64 Windows Vista and Windows Server 2008,,,,,,, File name,File version,File size,Date,Time,Platform,SP requirement,Service branch Hal.dll,6.0.6003.20489,"230,632",21-Mar-19,1:41,x64,None,Not applicable File name,Amd64_hal.inf_31bf3856ad364e35_6.0.6003.20489_none_6343ee29d3ef958c.manifest,,,,,, File version,Not applicable,,,,,, File size,"1,656",,,,,, Date (UTC),21-Mar-19,,,,,, Time (UTC),4:15,,,,,, Platform,Not applicable,,,,,, So, though not specifically mentioned, the KB does update HAL related files to v6.0.6003.20489

Well yeah, if it hurts when you do that, don't do that

Yes I can confirm. Connect To item has no display as a link option. Also right click on it -> Open does nothing.

I dont think any official statement was there, but they quietly fixed the HAL timings on a patch tuesday, which did help quite a bit.

I noticed that too, I made a fixed version of the start button a couple days ago. You can download it here: https://www.mediafire.com/folder/qj6ey33bayme7/unnamed

In most cases, yes, but there may be issues with temp-folder based installers that are spawned from another installer. By the end of September. I have close to enough new features to justify a new release, but I think I can stuff some more in. And I also need to test. I have every K32 function implemented for both architectures, SetDefaultDllDirectories fixed on both archs, ResolveLocaleName (basic implementation) and soon some other things. I hope to get many basic x86 applications running. The kernel32 wrapper itself is probably more compatible than it was at another point in the extended kernel's existence, as it doesn't rely on the original kernel32 having SetDefaultDllDirectories (which was added to Vista in 2013). But that will soon not be the case, as it will call functions from my NTDLL wrapper, and that will need a modified ntoskrnl to work.

That depends on personal preference and nobody can answer it. If you want to be guinea pig for Microsoft and do QA team work without payment on production system then go ahead and use Windows 11. If you want stable OS without constant changes use anything but Windows 10 or 11 (unless LTSB).

Here ya' go: Changes and download My pleasure, don't mention it. Any time. Oh c'mon you didn't have to; they are so nice. They smell nice too, almost like bits. Updates: 09.12.2008. - 1.2 Final