Leaderboard

v13.5-3 regular. have added this to the loader.ini : DirRemove=%Profile%\Default\Feature Engagement Tracker folder was somehow created ... https://source.chromium.org/chromium/chromium/src/+/master:components/feature_engagement/README.md;l=1?q="feature engagement"&ss=chromium

I've been using this and having good results

Enabling Aero in Windows Vista 50xx+ x86 (VMware) This is a small tutorial for enabling Aero Glass in most post-reset Vista Builds, namely the builds from the 50xx range onwards. This tutorial was tested with the following builds: (Professional/Ultimate unless otherwise noted) 5048 5219 5231.0 (by ovctvct) 5231.2 (Ultimate & Enterprise Server) 5259.0 (also by fred30w and ovctvct) 5259.3 (by ovctvct) 5270 (Ultimate & Enterprise Server) (Ultimate also by ovctvct) 5381 (Home Premium) 5384 (Enterprise Server) 5456 (Home Premium & Ultimate) (Ultimate also by ovctvct) 5472 (Ultimate & Home Premium) (Ultimate also by fred30w) 5536 (Business & Ultimate) (Ultimate also by ovctvct) 5552 (Home Premium) 5600 (Datacenter Server & Ultimate) (Ultimate by ovctvct and Arths) 5728 5754 (Home Premium & Ultimate) 5757 (Datacenter Server) 6001.16406 (Enterprise Server) 6001.16510 (Web Server) 6001.17051 (x64 Web Server) You will need the following items: 1. A relatively recent version of VMware Workstation. (10 or 11 will work) 2. The WDDM Display Drivers from Workstation 11. You can get an ISO that has them here: Download - MEGA If you are using an AMD64 (x64) build, you can get the x64 drivers here: MEGA 3. The install DVD of your desired build. Builds 5381 & later: 1. First, start creating your VM, but make sure to select Custom in the first screen. 2. Set the HW compatibility to Workstation 10.0 (for 11 users). You do not need to change the compatibility in earlier versions. 3. Set the Guest OS option to 'Windows Vista'. 4. Install the build as normal, including setting the BIOS Date. 5. After installing, open regedit and browse to Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM. 6. Over there, create a DWORD key named CompositionPolicy and set its value to 2. 7. Open Device Manager, browse to the 'Display Adapters' section, and right-click on the name of your display adapter. Select 'Update Driver Software' on the menu that comes up. 8. Select 'Browse my computer for driver software' and mount the ISO containing the display drivers from the 'Items you need' section. Builds 5048, 5219-5270: (Thanks to fred30w and ovctvct!) 1. Follow Steps 1-4 of the previous guide. NOTE: For 5231.X, use 'Workstation 6.0' as the compatibility mode! 2. After installing, open regedit. From here, it branches off into two different paths, depending on which build you want to use: Builds 5048, 5219 & 5231.X: Browse to HKEY_LOCAL_MACHINE\Software\Microsoft\DWM. (if the key does not exist, create it.) Over there, create a DWORD key named EnableMachineCheck and set its value to 0. Builds 5259.X & 5270: Browse to HKEY_CURRENT_USER\Software\Microsoft\DWM. (if the key does not exist, create it.) Over there, create a DWORD key named UseMachineCheck and set its value to 0. 9. Point the installer to the 'video_wddm' folder of the root of the ISO and click 'Next'. After the display driver installs, reboot the VM. 10. Aero Glass should be automatically enabled. It will be a bit slow, but it works. 3. After this, open Device Manager, browse to the 'Display Adapters' section, and right-click on the name of your display adapter. Select 'Update Driver Software' on the menu that comes up. 4. Select the options required to choose your driver manually. (Sorry, but there is no screenshot for this one as these builds use different interfaces. 5048 & 5219 use the XP-style interface while the later builds use the Vista-style.) 5. When you have to install the driver, mount the ISO you downloaded way back in the beginning and point it to the 'video_xpdm' in the root directory of the ISO. 6. You will receive an error about the drivers not being signed. Ignore it. 7. After the driver installs, reboot the computer. You should have Aero Glass enabled unless if you use 5048. 8. (Thanks to ovctvct!) If you use 5048, open services.msc and enable the 'User Experience Session Management' service by setting it to automatically start on start up. 9. After you reboot, you must log off and log on again on every startup to enable Aero. All other builds: (ones which are not listed at the top, that is) I don't know whether they work with these methods or not, as I don't have the builds themselves or they do not work for me. (5112, 5308.60 and 5365 are applicable for the second category.) If someone can provide a conclusion, I'd gladly provide credit for them. (PS: This started out as an experiment for lulz on 5456, but it turned into a reliable way to enable Aero Glass.) For more topics follow me on Microsoft Community Youssef Pro - Microsoft Community + Good luck to all

I use a dumb mobile for day-to-day use, and it goes with me everywhere. It's a Nokia C2-01, which I keep in Silent mode, unless I'm waiting for a call or want to be reachable to the wife (say when at the supermarket/grocery/bakery/etc.). For banking and analogous things, and what'sapp (for work mainly) I've got a very plain-vanilla Samsung J2 Prime (Android 6), which never leaves my office-cum-workshop... for uses like these, I'd suggest nowadays the cheapest possible Samsung which comes with Android 9, not degoogled nor rooted and with just the needed banking applications, maybe what'sapp if unavoidable, cpu-z, total commader and a full-fledged blocker application called Mr. Number. Nothing more. And to move around the city, a good old city map/guidebook (which, for São Paulo reaches 450 pages!) remains the best option and never fails one! Of course, I'm a brontosaur who thinks gaming means playing cards or shooting biliards or pool, with real balls, cues and table! So, YMMV.

As earlier posts in this thread suggest that Haswell+ and Ryzen problems are caused by the same bug in HAL, I decided to test if the issue was solved in the 6003 version of hal.dll (see this: https://msfn.org/board/topic/181612-wip-windows-vista-extended-kernel/page/106/?tab=comments#comment-1206074) I installed KB4474419 and hal.dll was upgraded to version 6003. Result: Nothing changed, BSODs are still occurring as they were. This means that the article on Beta Wiki was indeed a fake news or (less likely) that Haswell+ and Ryzen problems are in fact unrelated. PC specs: AMD Ryzen 5 1600AF, B350 MB with April 2018 BIOS version, Nvidia 1050TI, Windows Vista x64

Pressed discs are rare to show up as blank in a PC CD drive but there are reasons for it. Primary is any CD that has a "rot" issue, such as some damage to the reflective layer in just the right spot may lead to a disc being unreadable. Another possibility is that if the disc is "Enhanced CD" but the data portion is not compatible in some way. Since on a PC, it will try to read the data content before audio content in Explorer. Then there are discs that are just bad altogether, it is rare and I'd say you're more likely to run into this than incompatible Enhanced CD discs. I also just looked up Wii discs, it seems concensus is that they are based on DVD format, not CD and the filesystem used isn't something Windows can recognize. There have been some advancement as now there are PC emulators for Wii so someone must have come up with a way for a standard DVD drive to read that kind of disc. In the early days of Wii, you apparently needed some specific LG/Hitachi DVD drive in your computer to read them normally... or say like how you can see what is on a PlayStation disc anyways. For the Wii discs if you are going to move those, just note that they are untested. There is even a market for defective game discs (on any system) for some reason, but "untested" games is common to see.

That is not a recommendation, that is vague, generic advice. When (if) "they" will give you a small list of suitable devices and tested, easy to follow specific instructions, then it will become a recommendation. About "alternative" Operating Systems they tend to be - usually - "poor", i.e. their functionality is severely reduced on most (of the very few supported[1]) phones. So you have to choose (on trust only) one of these alternate OS's, then choose among the list the specific device that is reported to be the most functional, then procure the specific device. At this point you have good probabilities (but NOT certainty) that you'll manage to root/sideload/whatever the chosen OS on the specific device you have following a complicated sequence of steps (usually very poorly detailed, contradicting or however very much NOT clear for anyone already familiar with the processes involved), with the concrete risk of bricking the device unintentionally. And once you hopefully succeed you will have a smartphone with quite a few missing capabilities. The above is not at all to put you down, but you need to be aware of the limitations and possible caveats, this is something (IMNSHO) that you should take as a (fun) project to learn new, strange things rather than a sure path to google-freedom. jaclaz [1] LineageOS namely has a long list of devices that are not supported anymore (why?) and for which you need to build yourself the OS (what?), given the amount of these devices you have no guarantees whatever that the specific device that you choose and are able to procure today won't be "abandoned" tomorrow.

I have been using this compiler successfully for several hobby things, and thought it was worth a try to tackle its issues with the "\include" header-files folder. Using the command "cpp.exe -v" gives the list of search directories for header files. The result of which show again that it is overlooking it's MinGW include folder, and only looking in the more nested GCC system include folder. I found several messages on the internet reporting the same issue with certain MinGW/GCC homemade builds. The usual answer is to build GCC again properly, not as easy as it sounds. Instead, I tried several hex edits, and settled for this one: cc1.exe at offset E73C23 cc1plus.exe at offset F8B203 original string "i686-w64-mingw32/include" is to be replaced by just "include". The now unused characters need to be zeroed out. Then things work properly. Note that the search-order if the three header folders is a bit different, with the MinGW include folder now being 3rd instead of 1st. (Besides the ReactOS build environment package I also found this one GCC_8.4.0_for_MSYS2 . I only tried its cc1/cc1plus files, they have the exact same behaviour: WinXP compatible but include dir issue. The executables in this package are UPX compressed.) Edit: looking some more at that GCC_8.4.0_for_MSYS2 package. It is a much better example of how the folder structure was originally intended compared to the special purpose ReactOS package. It has a populated ".\i686-w64-mingw32\include" folder, and an empty but still present ".\include" folder. So instead of hex editing one can use ".\i686-w64-mingw32\include" and disregard ".\include". I will see what works better...

FWIW, the company in question is Roxio. Distributed in DVD style cases. Legit looking cases, very nice looking printed labels. But quite obviously CD-R or DVD-R if you inspect the discs. Which is kinda throwing me. Discs are readable, save that Disc 2 I referred to, which reads as a blank CD-R. Roxio Creator 2010 and Easy Media Creator 10 Suite. I heard Amazon distributes CD-R discs themselves for music now (burn a copy, send it out), which basically makes that junk media in my view. So had to wonder if the trend carries to all physical media or not in trying to figure out if all this stuff I ended up with is legit or not. As for the Wii discs, figured out they're a totally different format the PC doesn't understand, so I'm likely out of luck verifying those are still good.

@ilkertezcan One and Two will be added to next version. For Three, don't know if there is a need for drive letter on the VHD internal boot partition. WinNTSetup always create boot files on this partition. This is to make sure the VHD is boot able if you attach it to a virtual machine. If you don't want to physical boot this VHD on real hardware, just select any partition as boot drive and set BCD to NONE. As for the command line that will be fixed. FOUR: I'll think about it, but after 5.1 release I have no new features in mind.

There are certainly some instances where a small company may have made a run of discs themselves and used CD-R and then put a label on it, I have seen it before. There are also times where a contracted company may have used CD-Rs in order to send media to companies, contractors for large companies who could afford pressed discs like Sony. The main issue with CD-R is that they do not stand the test of time as the organic dyes will degrade after many years, so it is not uncommon to find 20 year old CD-R not readable in a drive. But also consider that CD-R from that long ago used to have issues with how they were "mastered" or created that could effect how they could be read. The primary example was that sometimes CD-R could not be read in a CD player outside of a computer, but I do recall some other instances where some CD-R could not be read on a computer that didn't have (for example) Adaptec EZ CD Creator installed. I have never tried a Wii disc in a computer.

Someone living in Eastern Europe can only tremble watching phenomenons, known from the times of communist takeover, creep back into mainstream politics. The restriction of open debate , but most importantly the restriction of the right to participate in a debate.

29.5.0 doesn't come, and 29.4.2 came instead. pure-tracking repo is updated. https://github.com/roytam1/palemoon-source-tracking/compare/fc493cf6d5bcc710eb196d8ec801e0c8eea1cea3...97c43630eaee79a34ba78a8c318fcf59700d1eba and cherry-picking will be done later.

With the large amount of interest in custom web browsers recently, we have created a new sub-forum specifically for topics about web browsers and the customisation and development of them. https://msfn.org/board/forum/200-web-browsers/

For me it will not end in 2025, only 4 years to change from an operating system to a super demanding one in hardware, it is very expensive for some people and especially companies. For me, what happened with Windows 98 or XP will happen, which extended support for a few more years. Or the last one left is to install unofficial updates of LTSB / LTSC / Server 20xx, as happened with embedded versions of Windows XP.

The drifting bug is even worse with Vista RTM. I don't understand what you mean by "how do you explain", the drifting bug is a byproduct of cheaper clock circuitry in Haswell and newer CPUs and Windows Vista's lack of correction re: timing drift. If you want a more in-depth explanation, @Ximonite would be able to provide it. But this is the gist of the bug and why it happens.

Care to elaborate ? I use DX11 Nvidia drivers and play DX11 games with zero bugs on 64-bit Vista. Hardware : GTX Titan , CPU Quad Xeon x3370 , 16GB DDR3 RAM , Fujitsu-Siemens motherboard . You mean I would see the bugs if my mobo had USB 3.0 ? Yet another PC with the dreaded haswell , but in this case it's running x86 Vista , also : no bugs with DX11 Nvidia (zero). Driver version 373.06. USB 3.0 controller is on , but no drivers installed , the mobo treats all USB inputs as 2.0 and they work at ordinary USB 2 speeds.

I'd like to give my input on the USB situation. It's required to disable the on-die usb3 controller on your ryzen CPU for stability under Windows Vista. In my case it was dev_149c. With a USB driver loaded for that device, I would get random lock-ups and BSODs. However, said issues no longer occur. That being said, Windows Vista does have the same issue that affects Haswell+ Intel CPUs on Ryzen, just without the logon/lock screen bugs. The bug occurs with nvidia drivers and DX11 support. It has been found out by @Ximonite that this is due to a "drifting" bug in the Vista HAL which is yet to be fixed.